Controlled entry lanes, sally ports, and vehicle screening.
This page focuses on lane performance and safety with crash rated bollards. Configure lanes and schedules (821, 525), integrate credentialing/ANPR (534), and accommodate emergency access (233). Queue and holding geometry draw on circulation rules (215) and signage/markings (353, 357). Interlocks and safety (342–345) are verified during commissioning/SAT (631–638). Track throughput, cycle time, and availability (542) to prove value. For broader context see this section and the chapter hub. If authority approvals apply in the UAE, review SIRA Bollards (UAE). When delivery considerations matter, see What to Expect and the 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.
374.1 Lane configurations
Single, twin, or bi-directional lanes with keepered openings (325). Configs define how a crash rated bollard portal performs daily.
Start by mapping desire lines and the turning/envelope needs for legitimate vehicles. Single lanes concentrate control and simplify interlock design but can cap throughput. Twin lanes split entry/exit or segregate staff vs visitors. Bi-directional lanes require wider turning & service access (325) and stricter matrix logic to prevent mode conflicts.
Use keepered openings to hold a defined clear-gap under load and after impacts. Coordinate the physical portal with reader pedestals, signals, and egress cones to avoid pinch points. Where geometry is tight, consider a short island or chicane (324) to control approach angle.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Certified lane (bollard + footing + keepered geometry) | Crash Ratings & Compliance |
| Operations | Duty cycles, fail-state philosophy, safety | Automatic HVM Bollard Controls |
| Maintainability | Access, drainage, spares | Preventive Maintenance Plan |
374.2 Modes & scheduling
Program Auto, Night, Event, and Maintenance modes (525). Scheduling keeps automatic HVM bollard behavior predictable.
Define modes in the control philosophy and implement them through Modes of Operation (525). Use calendars for peak/off-peak timing and add a reset hierarchy to avoid unsafe transitions. Night/Event modes may relax credentialing but should keep safety devices active and preserve fail-state rules.
374.3 Credentialing & ANPR
Integrate readers and whitelists; manage exceptions (534). Strong flows prevent tailgating through a crash rated bollard lane.
Coordinate access control with ACS/CCTV (534) and ANPR. Keep the whitelist clean, handle visitors with supervised release, and add anti-tailgating checks via loops and beams. Where SIRA applies, align data retention and monitoring practices and note this in the submission pack.
374.4 Emergency/blue-light access
Provide overrides and geometry for responders (233). Overrides must respect HVM bollard fail philosophy (355).
Define EFO & overrides (354) with triggers, priority, and cooldown. Provide turning space and hold lines per Emergency/Service Access (233). Test responder entry with a timed drill and capture evidence (638). Ensure overrides don’t defeat safety devices or violate fail-safe/secure selections (355).
374.5 Queue & holding design
Size approach lengths and turn pockets (215, 325). Queues must not spill into HVM bollard sweep zones.
Use site circulation (215) to size approach lanes, refuge pockets, and holding pens. Keep queue tails outside sweep zones and pedestrian desire lines; add “Queue here” markings (357) and conspicuous signals (353). Where space is limited, consider sally-port operation (one vehicle per chamber) to stop spillback.
374.6 Interlocks & safety
Bind detectors, signals, and E-stops in the matrix (352–353, 343). Interlocks protect users around a crash rated bollard.
Document a full interlock matrix (352) covering loops, photo-eyes, safety edges, and safety circuits (343). Include forbidden states, stop categories, and priority. Verify signals and alarms via Safety Signalling (353) and keep latched faults visible until acknowledged.
374.7 Human factors at lanes
Readable HMIs, messages, and countdowns (524, 353). HF lowers error at automatic HVM bollard portals.
Apply clear HMI & local control patterns (524): short messages, distinct signal aspects, and audible beacons for low-visibility periods. Place devices in the driver cone with adequate stopping sight distance; mirror key messages to steward repeaters where crowds gather. Use bilingual labels per project policy and night auto-dimming to prevent glare.
374.8 Evidence & testing
Commission with loop/beam proving and SAT scripts (633–638). Evidence secures crash rated bollard approvals.
Run the commissioning chain: pre-commission (631), power-on checks (632), loop & sensor proving (633), matrix verification (634), obstruction/intrusion (635), duty/performance (636), EFO & failure modes (637), and SAT/witness (638). Package an evidence pack with photos, logs, and signed scripts for authority/file records.
374.9 Performance metrics
Track ops/hour, cycle time, and availability (542). Metrics justify HVM bollard investment.
Instrument the lane via counters & health pings (541) and report a KPI set (542): operations/hour, average cycle time, availability, and MTBF. Alert on slow cycles and missed pings; review “bad actor” devices and refine schedules and interlocks to reduce stops without eroding safety.
Related
External resources
- NPSA — Hostile Vehicle Mitigation (HVM)
- ASTM F2656 — Crash testing for vehicle security barriers
- BSI — Impact test specifications (VSB systems)
374 Vehicle Access & Traffic Control with Crash-Rated Bollards — FAQ
What’s the difference between a single lane and a sally-port configuration?
Single lanes process one queue through one portal. A sally port uses two portals (entry and exit) forming a holding chamber. The chamber prevents tailgating and supports screening, but increases space and controls complexity. Choose it where security priority outweighs throughput.
How do we stop tailgating without slowing the lane too much?
Combine credentialing (ANPR/reader), well-placed loops/beams, and clear signals. Use timed “one-vehicle” windows and interlocks that re-close on second detections. Keep messages concise and conspicuous; validate settings during duty and SAT tests.
Which metrics prove the lane is performing?
Track operations/hour, average cycle time, availability, and MTBF. Add alert thresholds and a weekly report. If cycle times drift or availability dips, review failure logs, maintenance actions, and mode schedules.
Do emergency overrides disable safety devices?
No. EFO/overrides should retain safety devices & measures and follow the agreed fail-state philosophy. Test overrides in drills and keep cooldown/reset steps in the runbook so the lane returns to a safe normal state.