327.1 Event scenarios

List sales, match days, VIP arrivals. Each alters vectors and crowd density (239). Adjust HVM bollard states accordingly; never misrepresent a temporary item as a crash rated bollard.

Start by mapping credible scenarios for the site (e.g., weekend markets vs. stadium event surges). Each scenario shifts approach vectors, queue lines, and the mix of legitimate vehicles vs. general traffic. Agree the intended mode of operation for each event window and who is accountable for switching states.

Where temporary retail or VIP loops introduce new run-up corridors, add geometry-based calming (e.g., short chicanes) that do not create unsafe pinch points for pedestrians. If any removable units are lifted for throughput, the remaining HVM boundary must continue to meet the clear-gap rule.

327.2 Rapid change options

Use portable rails, cones, and staffed portals. HVM bollard openings become managed gates; protect removed crash rated bollard sockets with covers.

Rapid reconfiguration relies on a pre-approved kit: numbered cones/rails, lane banners, and “credentialed access” signs. Where a removable unit is lifted, fit a rated socket cover immediately to prevent trips, water ingress, and tampering.

Automatic lanes can serve as temporary portals: widen the stewarded cone, add a stop/advance beacon, and publish a simple runbook card for operators. Keep changes reversible within the defined response window.

327.3 Portable elements

Specify weight, footprint, and storage. Portable HVM bollard items must not exceed allowed gaps (232). They provide guidance only, not crash rated bollard performance.

Portable items (rails, belt barriers, cones) are for guidance and queuing—not impact resistance. Define maximum spacing so the effective opening never exceeds the allowed clear gap. Store kits close to use points (lockable cabinets), with counts logged pre/post event to avoid missing components.

If using “surface-mount light” devices, label them clearly as wayfinding only. Never describe any portable as “anti-ram”. That misrepresentation creates liability and undermines the integrity of the certified rating-critical dependencies.

327.4 Staffed vs automated modes

When staffing is high, simpler layouts suffice; off-peak, rely on logic (525). HVM bollard indicators clarify mode (353). Keep any nearby crash rated bollard closed when unattended.

Define two primary modes: “Stewarded Gate” (visual checks; cones/rails; handheld radios) and “Automated Access” (ANPR, induction loops, traffic lights). Publish who authorizes the switch. In unattended periods, automatic bollards should default to the safe state (see fail-safe/secure states) with clear red/green indications per 353.

For automated windows, confirm the state machine includes temporary-event branches and timeout rules. Nearby removable/passive elements should remain in the closed/installed configuration unless actively stewarded.

327.5 Wayfinding & barriers

Deploy bold lane IDs and directional beacons (544, 357). HVM bollard portals anchor routes; sign any crash rated bollard removal clearly.

Wayfinding must be unmistakable under crowd pressure. Use high-contrast lane identifiers, consistent iconography, and beaconing aligned with your operational dashboards (e.g., to display lane status). When lifting a removable unit, add temporary signage at eye level: “Security barrier temporarily removed—stewarded access only.”

Keep sightlines clear to reduce hesitation and driver confusion. Avoid creating bicycle handlebar traps; maintain legible desire lines and accessible turning spaces around any ad-hoc barriers.

327.6 Risk controls

Define crowd and vehicle controls, and fallback if devices fail (355, 547). HVM bollard states fail to safe; crash rated bollard boundaries remain intact.

List specific controls for each scenario: steward positions, queue pens, blue-light access, and the fallback path if a device faults. Your interlock matrix should enforce lock-outs that prevent openings beyond your clear-gap limit. Emergency overrides must be auditable and time-bounded (see EFO & overrides and incident response).

In the UAE, confirm event modes in your authority submissions and site MS/RA. Link any SIRA-relevant devices to the site’s approved scope; if in scope, reference SIRA Bollards (UAE) in the cover memo.

327.7 Reset plans

Checklist to remove temporary gear, restore gaps, and verify interlocks (633–635). HVM bollard logs capture reset; reseat any crash rated bollard inserts (626).

Create a one-page reset-to-normal checklist: remove cones/rails, reseat lift-outs, confirm beacon status, run loop & sensor proving, and re-verify obstruction/ intrusion tests as needed (635).

Log the reset in the panel and in the site diary. Take quick “wide→detail” photo sets to confirm correct reinstatement and document any deviations for the next event plan.

327.8 Evidence & records

Store photos, timings, and incidents (716, 542). Evidence proves HVM bollard safety and documents any temporary crash rated bollard changes (938).

Use your KPI set and dashboard timestamps to demonstrate compliance: mode start/stop, steward counts, gate throughput, alarms. File an evidence pack with photo logs and annotated key plans; reference any temporary deviations from the as-tested configuration and how they were controlled.

327.9 Lessons learned

After-action reviews feed design tweaks (339). Adjust HVM bollard patterns or signage and, if needed, upgrade a crash rated bollard location (446).

Hold a short after-action review within 48 hours. Capture queue spillback points, unclear signs, and any near-misses. If a temporary opening was constantly stewarded, consider a permanent array pattern tweak or upgrading a weak spot per Upgrade paths to HVM. Feed agreed changes into drawings and the interlock/state-machine version log.

327 Temporary/event reconfiguration — FAQ