Normal, maintenance, lockdown, and event modes.
Name modes, define transitions, and remove ambiguity. This page formalizes Automatic, Manual, Maintenance/Bypass, and Emergency/EFO modes (354), plus event and night modes (239, 327). We state power-fail behavior (518, 355), transition rules, and how mode is displayed/logged (544, 542). These definitions anchor interlocks (352), HMI design (524), and commissioning checklists (631–636). 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.
525.1 Automatic
Normal traffic control with interlocks (352). Auto keeps a crash rated bollard predictable.
Automatic means the lane runs on predefined logic using the interlock matrix, safety devices, and lane permissions. In this mode, a certified crash-rated system remains predictable: requests are evaluated (e.g., loop detect, credential, signal), then the controller executes open/close with timeouts, obstruction checks, and fail-state handling. Use this as the default for day-to-day operations and for acceptance testing.
Design notes: bind Automatic mode to a clear alarm philosophy, and publish lane timings, KPI targets, and reset steps in the O&M.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Crash Ratings Explained |
| Operations | Duty cycles, fail-state, safety | Installation Guide |
525.2 Manual
Local jog/step with safeguards. Manual helps HVM bollard maintenance (633).
Manual (safe-local) mode allows controlled “jog” or “step” commands at a local station for testing, alignment, or fault recovery. Guard it with a LOTO process, deadman/hold-to-run inputs, reduced speed, and enforced hazard analysis. Limit who can enter Manual via key switch and role-based permissions, and auto-revert to Automatic after a timeout or positive reset.
Commissioning tip: pair Manual steps with your loop & sensor proving and commissioning tools.
525.3 Maintenance/bypass
Explicit inhibits and signage. Bypass protects crash rated bollard users (343, 353).
Maintenance/Bypass is a controlled inhibit of movement (or of selected safety inputs) to allow safe servicing. It must be clearly indicated on the HMI and at the lane, with physical signage and barriers. Use keyed bypasses, latched messages, and an audit trail. Never allow a bypass to mask a critical safety circuit without a formal Permit to Work and time-boxed override.
Good practice: when a bypass is active, set the lane state to “degraded” and publish a dashboard warning to prompt reset.
525.4 Emergency/EFO
Fast, auditable sequence with logging (354, 542). EFO is critical to HVM bollard safety.
EFO is a priority sequence that overrides normal queuing and executes within a defined response window. Specify initiators (fire/BMS, guarded button), confirmation steps, and post-event cooldown. Log every EFO with timestamp, operator/initiator, lane IDs, and outcomes to support incident review and incident response. For UAE sites, align triggers and signage with SIRA expectations.
Power note: hydraulic systems may rely on accumulators or reserved energy for EFO; verify in the ITP/SAT.
525.5 Event/temporary modes
Preset flows for events (239, 327). Modes maintain crash rated bollard intent.
Event modes apply predefined lane states/timings for matches, VIP visits, or roadworks. Examples: stewarded open periods, one-way flows, or temporary reconfiguration. Preserve the clear-gap rule and HVM defend line while improving throughput. Time-box the mode and publish a Reset-to-Normal checklist.
525.6 Night/quiet mode
Reduced speeds/alerts within safety rules (546). Quiet mode preserves HVM bollard neighbors.
Night mode adjusts behaviors that affect neighbors and wildlife: reduced actuator speeds, softer alarm tones, and acoustic limits. Keep all safety measures intact, and ensure visibility with dimmed indicators, reflective bands, or beaconing that respects local lighting policies.
525.7 Power-fail behavior
Document ride-through and recovery (518). Behavior keeps crash rated bollard safe.
Define how lanes behave during power events: ride-through targets, protection, volt-drop, and restart sequencing. State the fail-safe/secure philosophy and when manual recovery is required (e.g., hand pump, safe-local command). Test these scenarios in SAT and log outcomes for future drills.
525.8 Mode transition rules
Permissions, timers, and confirmations (342). Rules prevent HVM bollard race conditions.
Transitions follow Request→Authorize→Execute with clear state machine guards. Typical guards include: lane clear, no EFO pending, operator role, key present, two-hand control, and cooldown met. Add anti-bounce timers, mutual exclusions for conflicting commands, and visible confirmation prompts on the HMI. Always provide a reversible path or safe stop if a mode error is detected.
525.9 Display & logging of mode
Always show/log current mode (544, 541). Visibility strengthens crash rated bollard audits.
Show the active mode at all times on the local panel and central dashboard, with color/shape coding, plain-language text, and a health ping. Log every mode change with who/what, when, why (source), affected lanes, and duration. Expose these logs as exportable records for SAT witness packs and after-action reviews. Use alerts when a non-normal mode exceeds its allowed window.
Related
External resources
- NPSA: Hostile Vehicle Mitigation
- FEMA 426 / DHS Reference Manual
- ASIS Security Risk Assessment Standard
525 Modes of Operation — FAQ
What’s the difference between Automatic and Manual modes?
Automatic runs predefined logic using the interlock matrix and safety devices; it’s the day-to-day default. Manual is a guarded, local mode for tests and recovery with hold-to-run controls, time limits, and LOTO applied.
When should we use Maintenance/Bypass?
Only during controlled servicing with a Permit to Work. Show clear indications on the HMI and on site, use keyed bypasses, and keep an audit trail. Time-box the bypass and require a verified reset to return to Automatic.
What must be logged during an EFO?
Log initiator and operator, timestamps, affected lanes, sequence steps, any faults, cooldown completion, and the final state. These records support incident reviews and compliance reporting.
How do we prove power-fail behavior before handover?
Include brownout, phase-loss, UPS/generator switchover, and controlled recovery in SAT scripts. Verify fail-safe/secure philosophy, restart sequencing, and evidence logs against the ITP and acceptance criteria.