Emergency fast operation, priorities, and lockouts.
Emergency Fast Operation must be fast, safe, and auditable. Define triggers, authorization, and exact sequences with timing and energy needs tied to drives/HPUs (341) and power budgets (517, 349). Ensure safety interlocks persist during EFO (343), and specify reset/cooldown behavior (355). Log events for KPIs (542), run drills (547), and package evidence for SAT and authorities (716, 638, 717). Include one-sentence context that naturally links upward to the parent hubs (this section and the chapter hub). Add SIRA context with a link to SIRA Bollards (UAE) when relevant. Link installation pages only if helpful: What to Expect and Installation Guide.
Important: This is a general guide. For live projects we develop a tailored
Method Statement & Risk Assessment (MS/RA) and align with authority approvals (e.g., SIRA) where in scope.
354.1 When EFO is required
Define credible scenarios and authority signals (133, 547). EFO ensures an automatic HVM bollard clears/blocks fast, preserving crash rated bollard intent.
EFO is a defined mode in the modes of operation where speed and priority are elevated to protect the secure area. Typical triggers include blue-light access for responders, hostile-vehicle alerts, or site evacuation patterns. Use the site’s Vehicle Dynamics Assessment to identify credible worst cases and where a faster raise or lower is mission-critical.
Document who can request EFO and through which channel (local station, SCADA/BMS, or field devices). Tie the need to a clear alarm philosophy so EFO use is consistent across all lanes (821) and audit-ready (716).
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | HVM crash ratings |
| Operations | Duty cycles, fail-state, safety | Installation Guide |
354.2 Trigger devices & authorizations
Keyed buttons, guarded touch, or remote SCADA (533). Authorization prevents accidental EFO at an HVM bollard lane.
Choose robust HMI devices for EFO: latched, guarded pushbuttons; dual-action key-switches; or dual-channel inputs via PLC/Controller. Define an emergency override hierarchy so accidental or unauthorized activation is blocked by role-based authorization and physical separation.
Remote commands via SCADA/BMS signals & reporting must be authenticated and logged. Use a state machine & interlocks design that treats EFO as a higher-priority request, while still honoring safety devices & measures (343, 353).
354.3 Sequence & timing
Document ms→s-level timings for request, interlock check, motion, confirm. Timings prove a crash rated bollard lane meets safety goals.
Write a precise Request→Authorize→Execute timeline: input validation (tens of ms), interlock status check (loops/beams), command issue, motion start, and end-position feedback. Include watchdogs and movement timeouts so a stalled move fails safe with a clear operator recovery hint.
In your interlock matrix, add timing tolerances and acceptance bands that commissioning can verify (634–636). Surface timing KPIs (542) so operations can detect drift (e.g., slower raises under heat load; see Hot Climate Design).
354.4 Energy & power implications
Size accumulators/UPS for EFO duty (512, 517). Energy sizing keeps HVM bollard EFO reliable during outages (518).
Hydraulic systems may require an HPU with energy budget and accumulators sized for worst-case EFO sequences. Electromechanical drives should specify UPS autonomy for at least one full EFO cycle per lane, plus control hold-up for logging and alarms.
Coordinate with Energy Budget, Power Failure Modes, and Accessory power so beacons/traffic signals remain visible throughout the EFO window (353, 517).
354.5 Safety interlocks in EFO
Retain beams/edges where feasible (343). Don’t bypass critical HVM bollard safeties.
EFO elevates priority but should not blindly bypass safety devices & measures. Keep photo-eyes, loop inhibits, and safety edges active where compatible with the threat scenario. If a temporary bypass is justified, require a two-hand/dual-action enable and a timed window, with visual/audible signalling per Safety Signalling (353).
Use a documented state transition diagram and safety circuit category that still achieves the intended Performance Level during EFO (343).
354.6 Reset & cooldown
Define post-EFO reset, latch clear, and cooldown delays. Reset protects drives and a crash rated bollard mechanism.
After EFO, require an explicit latched access state clear and a reset-to-normal checklist. Add thermal cooldowns (337) for HPUs/motors to protect equipment life and prevent nuisance trips. All resets should be role-restricted and logged.
Publish the reset workflow on the Operator Workflows page and reference it in SAT scripts (638) so witnesses see the exact steps and evidence captured (716).
354.7 Evidence & logging
Log initiator, times, and outcomes (541–542). Logs support approvals and HVM bollard investigations.
Every EFO should write a complete change-of-state (COS) log: initiator, authorization source, timing stamps, interlock status, motion duration, and end-state. Forward summaries to remote logging and expose counters/KPIs (542) on the operational dashboard.
Package EFO records in the Evidence Capture Standards so authorities or client reviewers can audit the trail (717). For SAT, include an EFO witness script with measurable acceptance bands (638).
354.8 Drills & training
Rehearse scenarios with measurable objectives (636, 547). Drills validate EFO readiness at a crash rated bollard site.
Create drill scenarios covering day/night operations, outage cases (518), and partial system degradation. Specify measurable objectives (time-to-secure, false-trigger rate, operator errors). Log results as part of the site’s training plan & sign-offs and feed improvements back to the change control & versioning register.
354.9 Risks & mitigations
Tailgating, sensor blind spots, and operator panic. Mitigate with signage, beacons, and confirmations (353, 524).
Common risks include tailgating, mode error, or blind spots if loops/beams are poorly placed (344, 345). Mitigate with conspicuous safety signalling, dual-confirm EFO actions at the HMI, and clear mode indicators near lane entries (821).
Where approvals apply (e.g., Dubai), align EFO rules and evidence with SIRA Bollards (UAE) submission expectations and coordinate signage/markings with Signage & markings around HVM Bollards.
Related
External resources
354 EFO & overrides for HVM Bollards — FAQ
What is EFO and when should I use it?
EFO (Emergency Fast Operation) is a high-priority mode that rapidly raises or lowers automatic HVM bollards during an emergency. Use it only for defined scenarios (e.g., blue-light access or credible vehicle threats) and with authorized operators.
Does EFO bypass safety devices like loops or beams?
No. EFO should retain critical safety devices & measures wherever feasible. Any temporary bypass must be deliberate, time-limited, and clearly signalled, with dual-action enables and full logging.
How do we ensure EFO works during a power outage?
Size hydraulic accumulators or UPS capacity to complete at least one full EFO cycle per lane. Keep controls alive long enough to log the event and signal alarms, per your Energy Budget and Power Failure Modes plans.
What happens after an EFO event finishes?
The system enters a latched state until an authorized operator performs the reset-to-normal checklist. Apply any required cooldowns to protect HPUs or motors, then verify interlocks before returning to Normal mode.