532.1 Required behaviors

Define global drop/raise, inhibit, or safe state for the HVM bollard per site policy (525, 355).

Start by declaring a single source of truth for emergency behavior in your Modes of Operation and the Interlock matrix. For automatic lanes, the minimum requirement is a deterministic response to fire: either fail-state philosophy set to “safe raise” (protecting egress) or “safe drop” (guaranteeing blue-light access), as justified by the site’s evacuation model. Declare how local keys, HMIs, and EFO coexist with the fire input to avoid ambiguous states.

Document per-array behavior: e.g., frontage arrays remain up to preserve pedestrian protection during a building evacuation while service-lane bollards drop to admit responders. Record any timed inhibits (e.g., 20-minute fire override) and the reset-to-normal path after the event.

532.2 Alarm priorities

Fire trumps normal operations; log overrides (542). Priorities avoid crash rated bollard conflict.

Implement a clear alarm philosophy with a priority matrix: Fire ≥ Life-safety inhibits ≥ EFO ≥ Security ≥ Routine. When fire is active, suppress non-critical alarms, present a single latched banner on the HMI, and create a Change-of-State log entry with time sync. This prevents operators from seeing conflicting instructions (e.g., “Gate closed for security” alongside “Fire route open”).

532.3 Global drop/raise

Specify which arrays/lanes react and how. Consistency preserves HVM bollard evacuation intent (353).

Map the fire trigger to named groups (frontage, perimeter road, sally-port, service yard). Use a single “Fire Master” input to set group actions via the PLC, not ad-hoc relays per panel—this keeps logic auditable and aligns with the Control architecture. Where networks span buildings, carry the command over supervised links and provide manual fallbacks (local EFO station) if comms fail.

532.4 Emergency egress logic

Guarantee pedestrian/blue-light access (233). Logic must not weaken the crash rated bollard perimeter elsewhere.

Protect evacuation corridors by ensuring arrays adjacent to exits raise or remain raised to block hostile approach, while designated responder lanes drop under Emergency/service access. Add safeguards: pedestrian presence devices near exits, timed hold-open for stretcher routes, and conspicuity cues. Validate that opening one lane does not create a drive-around defeat—use chicanes or keepered gaps if needed.

532.5 Wiring & isolation

Use supervised circuits and isolators. Supervision prevents silent HVM bollard failures.

Interface using clean, supervised dry contacts between the fire panel and the bollard controller. Apply line monitoring (EOL resistors or polling) so open-circuit faults alarm. Electrically isolate with relays or opto-isolators, and route in segregated cables per Cables & Routing. For multi-building sites, prefer fiber for immunity; where copper is unavoidable, add SPDs and bonding consistent with Electrical Supply & Protection.

532.6 Test & witness plan

Script cause–effect and evidence capture (638). Tests prove crash rated bollard behavior to reviewers.

Write a concise cause-and-effect table: inputs (Fire, EFO, local key), pre-conditions, expected states, HMIs, and annunciation. Execute during SAT / Witness Procedure with time-synced video, COS logs, and signed checklists from the ITP. Include power-event drills (generator start, brownout) to prove ride-through for the fire path.

532.7 Fail conditions

Define comms loss and device-fault response. Fail plans keep HVM bollard safe (518).

Declare actions for communication loss between the fire system and the controller: e.g., local watchdog enforces “safe local mode” with site-specific default positions. Treat stuck inputs, IO module failure, or power failure modes in the same way—prefer designs that default to life-safety, while avoiding broad perimeter downgrades. Expose all fail states to SCADA/BMS as explicit alarms.

532.8 Documentation

Provide signal lists, drawings, and SoO (539). Docs speed crash rated bollard acceptance (938).

Deliver an Interface Control Document covering tag names, terminal mapping, cable IDs, supervision method, and a step-by-step Sequence of Operations. Update the Integration Documentation pack and index it in the submission per Submission-Pack Guidance. Keep redlines current and issue a snapshot PDF for reviewer markup.

532.9 Authority approvals

Record approvals and periodic drills (547). Approvals legitimize the HVM bollard interface.

Log design approvals, SAT sign-offs, and drill records in the project’s Authority Submittals. In the UAE, coordinate early with SIRA where scope intersects their remit, and retain evidence that the interface does not breach the certified boundaries of the crash-rated system.

Fire Alarm Interface — FAQ