SOPs, checklists, and defenses against misuse.
The safest HVM bollard systems guide operators to do the right thing. Map routine tasks and embed checklists, prompts, and confirmations into the HMI (524) backed by interlocks (352). Provide on-screen training, define escalation paths, and catalogue error traps seen during commissioning (631–636). Tie actions to KPIs (542) and require post-incident reviews (547) so improvements stick. 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.
545.1 Task mapping
List routine, exception, and emergency tasks. Mapping clarifies HVM bollard responsibilities (525).
Start by inventorying lane-level actions (raise/lower, EFO), status checks, and resets. Tag each task with the actor (operator, supervisor), required permissions, and preconditions. Express the flow in a simple SoO aligned to 525 — Modes of Operation so responsibilities are unambiguous.
Use a swimlane diagram or RACI to capture handoffs and decision points: e.g., when a gatekeeper must authorize a raise in event mode. Reference the HMI & Local Controls page for button/indicator conventions that reduce hesitation.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Global Crash Ratings |
| Operations | Duty cycles, fail-state, safety devices | Control Logic |
545.2 Checklists & prompts
On-screen prompts for mode changes and resets. Prompts prevent crash rated bollard mis-steps (536).
Embed short, context-aware checklists directly on the HMI. For example: before switching to “Delivery” mode, verify stewarded gap, clear-ground loop, and reader whitelist state. Use concise language, progressive disclosure, and highlight the primary action with clear verbs (“Authorize raise”). Tie prompts to the Alarm Philosophy to avoid alarm floods.
Keep lists under seven items and add a “Reset-to-normal checklist” after incidents. Store confirmations in a COS log for audit and training replay.
545.3 Interlocks/user guidance
HMI shows why actions are blocked (352). Guidance reduces HVM bollard workarounds.
When an action is inhibited by the interlock matrix, the HMI should explain the “inhibit reason” in plain language and suggest the next best step (“Clear photo-eye obstruction” or “Wait for EFO cooldown”). This discourages unsafe bypasses and speeds recovery.
Surface recovery hints, show the active mode banner, and expose pending conditions (loops, readers, alarm class). Cross-reference 352 — Interlock Matrix for detailed logic.
545.4 Confirmation & undo
Require confirmations with safe undo paths. Confirmations protect crash rated bollard safety (342).
Use confirmations for high-consequence actions (raise in mixed pedestrian flow, emergency drop cancel). Pair with a “safe undo” window where feasible—e.g., within two seconds before bollard motion starts, allow cancel without creating a forbidden state. Where motion has started, use a defined stop category and recovery path.
Log each confirmation with user, time, and context to support evidence capture and KPI reviews.
545.5 Training within HMI
Embed short “how-to” panels and fault tips. Training stabilizes HVM bollard operations (631–633).
Provide bite-sized help: a 30–60 second micro-guide for common tasks (normal raise/lower, Safe Local Mode, post-power-recovery checks). Link each help card to the relevant client training plan item and SAT scripts so content remains consistent.
Include annotated screenshots, a glossary popover for local jargon, and a “practice” lane on the HMI simulator during commissioning (631–636) to build muscle memory before go-live.
545.6 Common error traps
Highlight queue pressure, rushed EFO, or bypass misuse (354). Awareness prevents crash rated bollard incidents.
Typical traps include “queue pressure” leading to rushed EFO triggers, ignoring photo-eyes, and manual bypass keys left enabled. Design countermeasures: rate limits on repeated EFO, first-out annunciation to show the root-cause alarm, and latched messages when bypass is active.
Add lane sitemaps and conspicuity cues at portals, with alarm shelving policies. Review traps during Loop & Sensor Proving and EFO & Overrides.
545.7 Escalation paths
Define who to call and timelines. Escalation reduces HVM bollard downtime (536).
Publish an on-screen escalation path with MTTA targets and who owns the next action. Example: Operator → Facilities Duty Eng. (5 min) → Controls SME (15 min) → Vendor Hotline (30 min). Use colored timers and a “handover” button to acknowledge ownership changes.
Integrate with CMMS to auto-create tickets when alarms persist beyond thresholds defined on the KPI Set & Thresholds page; align priorities with Alarm Philosophy.
545.8 Post-incident review
Template to capture events, actions, and lessons (547). Reviews harden crash rated bollard practice.
After any incident or near-miss, run a structured after-action review using a simple template: line-up of events from the COS log, alarms, EFO initiators used, human decisions taken, and environmental factors (crowd, glare). Avoid blame; focus on system improvements (prompts, signage, dwell timers).
Record actions, owners, and due dates. Feed outcomes into Emergency Modes & Incident Response (547), training updates (737), and dashboard KPIs (544).
545.9 KPI linkage
Tie operator actions to KPIs and recognition (542). Linkage sustains HVM bollard performance.
Surface simple, role-based KPIs on the HMI and dashboards: Ops/hour, cycle-time stability, first-out acknowledgments, and time-to-clear inhibits. Celebrate good behavior (steady cycle times, low alarm latency) and spotlight coaching opportunities.
Ensure KPI formulas and thresholds match the KPI Set. Use operational dashboards to trend improvements over time.
Related
External resources
- NPSA — Hostile Vehicle Mitigation guidance
- FEMA 426 — Reference Manual to Mitigate Potential Terrorist Attacks
- ASIS — Security Risk Assessment Standard
545 Operator Workflows & Error-Proofing — FAQ
What should be on an operator’s pre-raise checklist?
Keep it short: verify mode, clear loops and photo-eyes, no pedestrians in the defend line, no active inhibits, and authorization confirmed. Log the confirmation to the COS log for audit.
When should I require a confirmation dialog?
Use confirmations for any high-consequence action such as raising in mixed traffic, canceling an EFO, switching modes during peak, or disabling a safety device. Provide a safe undo path where possible.
How do we prevent “queue pressure” mistakes?
Rate-limit repeated EFO triggers, show first-out alarms to reveal the true cause, use conspicuity cues, and enforce escalation timers so operators don’t bypass interlocks under pressure.
What metrics link operator behavior to availability?
Track Ops/hour, cycle-time variance, MTTA for critical alarms, inhibit clear times, and first-out acknowledgement rate. Review them in weekly dashboards and use them for coaching and recognition.