Library groups and what counts on an event site

The content library is one library in three groups — 🏘 Residential, 🛒 Retail and 🎪 Events — and about fifty of the original 3D objects (the porta-potty, the generator, the bell tent, every Temp Works item) now count on an event site: toward provision, in the hire and objects schedules, the budget, the walking routes and the Event Safety Plan appendix. Events mode is in Beta.

The group select, search and the twin chip

• Group. A select at the top of the library picks the group; the categories and cards under it belong to that group. An estate opens on Residential, a retail site on Retail and an event site on Events. Your own choice is remembered per site kind on this device, never in the design. Only the groups your workspace can use are listed; with only one, the select is hidden.
• Events off an event site. On an estate or retail site Events is greyed — event objects are for event sites; set the site to Events in Site settings. On an event site, Residential and Retail drop Playground and Buildings, as the library always has there.
• Retail is Residential without the camping and leisure kit a supermarket scheme never places: the bell tent, camping tent, glamping pod, hot tub, festival stage and garden-waste wheelie bin. They are still under Residential, which a retail site can pick.
• Search. The box under the group matches every word you type against object names across the group's categories; each result shows its category. Tick All groups to search every group the select lists.
• ⇄ chip. Where two objects are one concept, a group lists one of them. The other is never removed: it is offered from the listed card's ⇄ chip, found by search, and still listed in any other group it belongs to. Placed ones count the same.

The WC block (4 cubicles) and the shower unit (3 showers) are listed beside the toilet trailer and shower block: they are the only way to place those counts.

📹 Site Security (the CCTV tower and the portable CCTV sentry) is listed under Residential and Retail as ordinary objects. Select one and press 📹 Camera view to set what it sees — the view angle, range and direction — and tick Camera view splays in a sketch view's style to draw it (see Camera view splays). An event site lists its own 📹 Site security category instead, holding the same two models as event objects in the security layout — hidden from review and share links, the quote request and any appendix or DXF you export without its security tick, and removed from a copy to send — so the residential pair is not offered there. A residential or hire-brand camera that does reach an event site (a copied design, the Hire brands library) is in the security layout too: every camera is.

What counts on an event site

On an event site each of these takes an event category, Build · Live · Derig phases and a mark, and is drawn on its EVT_* DXF layer. Counts that a fixed model cannot show honestly — a generator's kVA, a WC block's cubicles, a tent's beds, a cabin's toilets — are data parameters: set them under ⚙ Parameters; the model does not change. Fixed objects are hired at their drawn size × scale. On an estate or retail site none of this applies: the objects behave exactly as before.

• Beds. Tents and pods count their beds against the campers in Attendance & demand: more beds than campers, or beds with camping off, is a warning.
• Walking routes. Objects block the walking graph, except gates, wheelie bins, cones and other flat kit, and sleeping kit inside a campsite zone. Heras, crowd, pit and water-filled panels arrayed along a road walk as one line, not one obstacle per panel.
• Barrier runs. Panels inside a drawn barrier run stay the run's: they are priced per metre with the run and never counted twice.
• Barrier gate. A lifting arm where a barrier run crosses the emergency route serves the fire-gate check at its drawn width × scale. It is never a pedestrian exit.
• Object data. A field scoped to a category follows the object's original category: a field scoped to Amenities applies to a placed porta-potty, one scoped to Welfare does not.

What changes on an existing event design

A design that already holds these objects starts counting them the next time it opens. Nothing is migrated: every object keeps its id and its look.

• The hire total rises: the originals now have hire lines.
• Objects on site in fewer than three phases now disappear from the other phase views: Pedestrian Barrier (Live), Pit barrier (1.0 m) (Live), Trench Box (Build and Derig), 360 Excavator (Build and Derig), Excavator (Build and Derig), Telehandler (Build and Derig), Site Dumper (9t) (Build and Derig), Wheel Loader (Build and Derig), Concrete Mixer Truck (Build and Derig), Piling Rig (Build and Derig), Tower Crane (Build and Derig), Crawler Crane (Build and Derig).
• An original object arrayed along a fence takes its own phases instead of the run's.
• The originals move to the EVT_* DXF layers and to the Event objects sketch toggle.
• The helipad clearance finding names objects ("nearest Site Generator") instead of printing ids.
• A barrier gate at a fire-route crossing now passes the fire-gate check there.
• A scaled original panel or stage is hired at its scaled size.
• A retail site's library opens on the Retail group, without the six cards above (they are under Residential).