547.1 Emergency identification

Define triggers: alarms, sensors, operator calls. Identification accelerates HVM bollard response (536, 345).

Establish clear triggers and confirmation rules: first-out critical alarms (per alarm philosophy), life-safety signals (e.g., fire alarm interface), and operator reports via radio or HMI. Use a concise decision flow that distinguishes genuine incidents from faults and defines who can escalate to an emergency mode. Include a time-sync policy so logs from PLC/SCADA/BMS correlate during reviews.

Add simple operator cues on the HMI: red banner for “Emergency Mode,” latched message with the inhibit/interlock implications, and visible “who called it” data. For physical triggers (panic/EFO initiators), label and test during SAT (638) so stewards and security recognize them under stress.

547.2 Roles & command

Name incident lead and comms tree. Clear roles keep crash rated bollard actions coordinated (131).

Adopt a simple incident command with an Incident Lead (duty security supervisor) who authorizes mode changes and a deputy responsible for crowd and traffic management. Publish the escalation path and on-call roster; pin it inside the control room and within the HMI “Help” panel. Use a RACI grid covering operators, stewards, facilities, and blue-light agencies so tasks are unambiguous during and after incidents.

547.3 EFO/override use

Authorize, execute, and log EFO sequences (354, 542). Controlled EFO protects HVM bollard intent.

Define when EFO is allowed, the authorization hierarchy, and how to initiate it (HMI button with confirm, guarded key switch, or physical call-point). EFO should set the lane to a pre-tested state and record an EFO evidence log (time, initiator, state achieved, cooldown). To avoid equipment damage and unsafe re-entry, specify an EFO cooldown and the interaction with overrides & interlocks.

547.4 Safe states & evacuations

Document fail-safe/secure and pedestrian routes (355, 353). Safe states preserve crash rated bollard boundaries.

Map which lanes go fail-safe vs fail-secure, and how that supports evacuation and blue-light ingress. Coordinate egress cones, marshal lines, and pedestrian wayfinding with safety signalling. Document cross-system priorities (e.g., fire master), and test them during SAT (638) so the intended defend lines are maintained without trapping people.

547.5 Communications & signage

Use pre-scripted messages and wayfinding (357). Comms prevent HVM bollard confusion during events.

Prepare message templates for public address, VMS boards, and radios. Keep phrasing short and unambiguous; pair messages with visual cues (beacons, traffic aspects) to reduce mode error. Place site maps at steward posts and update “you are here” wayfinding around controlled lanes. Where authority coordination applies (e.g., Dubai), align terminology with SIRA submission language and keep a bilingual set if required by client policy.

547.6 Drills & scenarios

Quarterly drills with measurable objectives (636). Drills validate crash rated bollard readiness.

Run quarterly drills that stress different failure paths: communication loss, power events, and conflicting commands. Set objectives and KPIs (e.g., response time KPI, operator MTTA). Capture timings, clips, and operator feedback; then log NCRs and close them with evidence before the next drill. Keep a scenario library and rotate daytime/nighttime exercises to expose signage and lighting gaps.

547.7 Post-incident inspection

Check heads, sockets, foundations, and devices (735, 333). Inspection ensures HVM bollard fitness.

After any impact or suspicious event, inspect the bollard head, sleeve/core, socket, keepered covers, and surrounding paving. Verify alignment, projected/clear gap, and any change in capture height. For crash-rated arrays, add foundation checks (333), drainage (334), and device tests (loops, photo-eyes). Record serials, take a wide→detail photo set, and update the asset register before authorizing a controlled recovery to normal operations.

547.8 Reset & evidence

Follow reset scripts; capture logs/photos (716, 444). Evidence supports crash rated bollard reviews.

Use a reset-to-normal checklist with a clear reset hierarchy: field devices → lane controls → panels → HMI/SCADA. Export logs (change-of-state and EFO evidence), annotate photos, and tag video snippets. Store everything in the submission/incident pack (444) and cross-reference any NCRs (719). If temporary cones/barriers were used, document removal and reinstate wayfinding before reopening.

547.9 Lessons learned

Record actions, owners, deadlines; update docs (537, 118). Lessons strengthen HVM bollard resilience.

Hold an After-Action Review (AAR) within 72 hours. Document root causes, assign accountable owners, and set dated actions. Update change control items (537), training materials, and SOPs; then post a brief delta highlight to the project change log (118). Where approvals apply, include a short authority briefing note and file it alongside the evidence pack.

547 Emergency Modes & Incident Response — FAQ