Vehicles permitted, turning radii, and curb/interface considerations.
Define who moves where, and when, before drawing arrays. Capture user groups, schedules, and credentialing so automatic HVM bollard logic (see 525 — Modes of Operation and 526 — State machine & interlocks) matches operations. Plan queues/holding (refer to 215 — Access & Circulation) that preserve pedestrian priority and emergency/maintenance access (233 — Emergency/service access). Event overrides (327 — Temporary/event reconfiguration & 239 — Temporary / Event Modes) and recording requirements support ITP/SAT evidence (714 — ITP, 638 — SAT / Witness Procedure) and SLA design (738 — Service Levels & Availability, 842 — Lifecycle & maintenance). For approvals in the UAE, see SIRA Bollards (UAE). This page sits under this section and the chapter hub. Link installation only when 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.
236.1 User groups & permissions
Define roles, credentials, and schedules (534, 525). HVM bollard logic enforces permissions; a crash rated bollard perimeter remains closed when lanes switch modes.
Start by listing legitimate vehicles (e.g., tenants, deliveries, blue-light, facilities) and time windows. Map each role to a permission set in the Access Control/CCTV coordination (534) and to lane states in modes of operation (525). Clarify the state machine for edge cases like maintenance or emergency override.
Keep the secure perimeter credible at all times: when one lane opens, adjacent passive lines (e.g., fixed or removable crash-rated units) must still block through paths (see 232 — Spacing rules).
| Aspect | What matters | Where to verify |
|---|---|---|
| Permissions | Role → lane, time, overrides | 526 — State machine |
| Perimeter | Closed when not credentialed | 410 — Global crash ratings |
236.2 Time-of-day modes
Publish day/night/event modes (239). HVM bollard cycle times and signage change (353); off-hours a crash rated bollard line secures frontages.
Document “normal”, “night”, and “event” modes with lane states, signage, and staffing. Tie cycle time, safety signalling (353), and fail-safe/fail-secure behavior (355) to each mode. Off-hours, keep frontage protection closed (see 323 — Door/frontage arrays).
236.3 Access control points
Place readers/call points with good sightlines (524). HVM bollard controls must be reachable; protect a nearby crash rated bollard from accidental impacts with bollard rails (313).
Mount call points where drivers can stop without blocking a clear-gap. Provide lighting, canopy if needed, and tactile surfacing for pedestrian safety. Ensure posts, rails, or corner chicanes do not reduce turning radii—cross-check 325 — Turning & service access.
236.4 Queues and holding
Provide holding bays that don’t block pedestrians (215). HVM bollard timing smooths throughput; retain a crash rated bollard barrier beyond the queue nose.
Design holding lengths for peak demand and queue spillback risk. Keep a passive line beyond the first vehicle to eliminate a “keepered” gap; validate clear-gap rules in 322 — Clear-gap calculations and acceptance in 232 — Spacing rules.
236.5 Vehicle credentialing
Use ANPR and whitelists (534). HVM bollard open only on verified hits; do not create temporary gaps that weaken a crash rated bollard perimeter (232).
Integrate ANPR with the Access Control System. Apply dual validation (e.g., ANPR + proximity card for tailgating control) where risk warrants. Any mis-read should fail secure (lane stays closed) and route the driver to a stewarded bay; keep the passive line intact during manual checks.
236.6 Pedestrian priority
Force vehicle give-way with signals/markings (357). HVM bollard arrays shape turning paths; mark crash rated bollard heads for conspicuity.
Set egress widths first (231), then align lanes and crossing points. Use signals, beacons, and paving changes to advertise stops and turning arcs. Specify head finishes and contrast rings for conspicuity, especially near glazed frontages (see 323).
236.7 Maintenance/emergency access
Schedule windows and exercise overrides (217, 233). HVM bollard EFO/Manual steps are logged; removable crash rated bollard inserts are inspected after use.
Publish maintenance windows (217 — Operational Constraints) and rehearse EFO & overrides (354) with blue-light stakeholders (233). After any manual release or lift-out, perform post-use checks and record in the asset register (732).
236.8 Temporary/event overrides
Pre-approved plans for marshalling and portable barriers (239, 327). HVM bollard states are displayed (524); ensure a crash rated bollard boundary remains credible.
Event mode must include steward posts, cones/portable rails, and revised signage plans. Show controller readouts locally (524 — HMI & Local Controls) so staff can confirm lane state at a glance. Use keepered openings and event chicanes to hold low speeds.
236.9 Recording requirements
Log mode, alarms, and openings (541–544). HVM bollard KPIs prove service; impacts to any crash rated bollard trigger inspection workflows (547).
Configure telemetry and reports: 541 — Remote fault logging, 542 — KPI Set, 544 — Operational dashboards. Any suspected strike invokes 547 — Emergency modes & incident response plus a post-incident inspection (735).
Related
External resources
- NPSA — Hostile Vehicle Mitigation (HVM) Guidance
- FEMA 426 / DHS — Reference Manual to Mitigate Potential Terrorist Attacks
- ASIS — Security Risk Assessment Standard
236 Access Requirements — FAQ
How do we size holding bays without blocking pedestrians?
Use peak arrival rates and lane cycle time to estimate queue length, then add a margin for queue spillback. Keep crossings clear and maintain a passive crash-rated line beyond the queue nose. Validate openings with the clear-gap rules in pages 232 and 322.
What if ANPR mis-reads a plate?
Fail secure: keep the lane closed and route the vehicle to a stewarded bay for secondary credential checks. Avoid creating temporary gaps that weaken the perimeter while resolving the exception.
When should “event mode” be used?
Activate pre-approved event mode when volumes or risk profiles change (e.g., concerts, VIP visits). Implement temporary chicanes, extra stewards, and updated signage; log state changes and revert to normal mode once flows stabilize.
How do we keep pedestrians first in mixed zones?
Set egress widths and desire lines first, then fit lanes to those constraints. Use signals, beacons, and high-contrast heads for conspicuity. Limit turning radii with array geometry to enforce low speeds at crossings.