Required movements: emergency, service, VIP, and daily operations.
Good circulation avoids unsafe workarounds. Define users and modes so HVM bollard lanes (821) and pedestrianized streets (822) remain legible. Bake emergency/service access into the geometry (233, 326), manage queues and crossings (231, 237), and specify signals/markings (353, 357). This page ties policy to arrays/spacing (321–325, 232) and to controls logic (342, 525–526). 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.
215.1 User types and flows
List staff, public, service, emergency, and mobility users with peak/off-peak profiles. Map desire lines and conflict points (231, 237). HVM bollard layouts must not block wheelchair paths; where certification is required, place each crash rated bollard so approach vectors remain controlled (225, 321).
Start with a people-first map: entrances, refuge spaces, and the busiest egress widths (231). Note crossings used by mobility aids and deliveries. Then overlay the approach vectors (225) that create conflicts. Mark any “must-keep” wheelchair and stretcher routes, and keep clear-gaps consistent to avoid informal bypasses.
For each user type (staff, public, VIP, service, emergency), capture peak profiles and dwell areas. Where flows intersect, prefer islands or chicanes (324) over ad-hoc cones. If a certified crash-rated line is needed, show it explicitly on drawings and maintain sightlines to keep movements legible.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Crash standards overview |
| Operations | Duty cycles, fail-state, safety devices & measures | Installation Guide |
215.2 Vehicle classes & permits
Define allowed classes (223) and credentials (534). Segment lanes and opening sizes to stop tailgating. HVM bollard lanes use scheduling and interlocks (525, 352); a crash rated bollard line at frontages preserves security when lanes are closed (374).
Use the vehicle classes (223) to set who may enter and how. Tie entry to credentialed access (534) and physically segment lanes to prevent tailgating. Lane modes of operation (525) and the interlock matrix (352) should enforce one-at-a-time movement through the throat, with loops/photo-eyes supervising the gap.
215.3 Peak vs off-peak modes
Set timed modes: day throughput vs night security. HVM bollard logic changes cycle times and signals (342, 353). Off-peak, retain a crash rated bollard perimeter with compliant clear gaps (232).
Define time-based lane states (e.g., Day/Trade, Night/Secure, Event). In Day mode, optimise cycle time and queue clearance; in Night mode, bias to a closed, clear-gap-compliant perimeter (232). Document the control logic (342) so operators know what changes between modes, and mirror it in signal heads and HMI prompts (353, 524).
215.4 Emergency/service access
Pre-assign keepered openings, turning radii, and staging (233, 325). HVM bollard overrides must be auditable (354). Removable crash rated bollard inserts require tolerance checks after drills (626).
Mark dedicated turning & service access (325) and any keepered openings for blue-light vehicles. Emergency overrides (keys, EFO) must log who/when/why (354). Where HVM vs low-speed differs by time of day, show both states in drawings. After drills, re-verify alignment and tolerances (626) before returning to service.
215.5 Pedestrian priority & crossings
Align crossings to natural routes and maintain sightlines (237). HVM bollard arrays frame islands/chicanes (321, 324). A crash rated bollard near crossings must meet height/contrast cues (312, 366).
Put crossings on desire lines with good inter-visibility. Use bollard arrays to form islands or chicanes (321, 324), never to create hidden corners. Near crossings, set bollard height (312) and finishes/contrast (366) so canes and low-vision users can detect them; avoid reflective glare at night.
215.6 Signals, signage, markings
Combine beacons, arrows, and surface legends (353, 357). HVM bollard lanes need clear “request/execute” feedback (524). Mark any crash rated bollard nose clearly to prevent trip hazards.
Each lane should present the same cues: STOP/WAIT, REQUEST RECEIVED, BOLLARD MOVING, PROCEED. Pair signal heads with HMI prompts (524) and ground markings (357). Where bollards sit within pedestrian reach, chamfer or sleeve noses and add contrast bands to reduce trip risk.
215.7 Queuing & back-of-kerb issues
Design queue spillback space, lane bypasses, and refuge pockets. HVM bollard cycle times (636) and queue length inform capacity. Keep a crash rated bollard set outside pedestrian pinch points (323).
Estimate peak queue length by cycle time × demand (636) and provide reservoir space that doesn’t block crossings or doors. Where queues risk tailbacks, add a bypass or stewarded pocket and keep the certified line outside pinch points (323). Use refuge pockets for deliveries so public flows remain clear.
215.8 Mixed modes & conflicts
Model deliveries vs public peaks. HVM bollard modes (525) and interlocks (352) prevent unsafe overlaps. Place a crash rated bollard line to segregate service edges from public routes.
Plot deliveries against arrival peaks and event modes. If overlaps are unavoidable, use stronger segregation: a fixed/passive line protecting the public edge, with the mode setting temporarily closing public access until service vehicles clear.
215.9 Access policy into design
Translate rules into arrays, openings, and schedules (339). HVM bollard logic and signage become specification clauses (433). A crash rated bollard perimeter is referenced in approvals (717, 938).
Write the access policy as design objects: lane sets, opening widths, certified lines, and a time-of-day schedule (339). Turn HMI messages, signal states, and interlocks into spec clauses (433). For UAE projects, reference approvals workflows and keep a clean submission index (717, 938); see SIRA Bollards (UAE) for context.
Related
External resources
- NPSA: Hostile Vehicle Mitigation (HVM)
- FEMA 426 / DHS: Reference Manual to Mitigate Attacks
- ASIS: Security Risk Assessment Standard
215 Access & Circulation — FAQ
How wide should a bollard lane be for mixed cars and pickups?
For typical mixed light vehicles, design the usable throat at 3.2–3.6 m with supervised clear-gaps. Confirm with site-specific swept-path checks and align with the chosen vehicle class and credentialing approach.
How do we prevent tailgating through an automatic bollard lane?
Combine physical throat control with logic: a one-vehicle window, interlock matrix rules, and supervised loops/photo-eyes. Use clear “request/execute” signalling and alarms if a second axle is detected without a new credential.
What changes between day and night modes?
Day mode prioritises throughput (shorter cycle times, visible prompts). Night mode prioritises a closed, clear-gap-compliant perimeter with restricted credentials. Document the differences in your lane’s modes of operation.
When is a crash-rated line needed instead of low-speed storefront bollards?
Use a crash-rated line where the VDA indicates credible higher-energy impacts or targeted threats. Low-speed options (441/442) suit accidental strikes and low approach speeds; see Selecting Low-Speed vs HVM.