Lane control design, logic, and safety devices.
Design lanes that stay safe at peak and practical off-peak. Choose lane types/counts from access needs (215), then define mode schedules (525) and credentialing with ANPR/loops/call points (534, 344–345). Interlocks and safety circuits protect people and assets (342–343, 353). Track throughput with KPIs (542), plan EFO/overrides (354), and verify via SAT (631–638). Tie geometry to clear-gap rules (232, 322) and foundations to crash rated bollard requirements (331–333, 421). 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.
821.1 Lane types & layouts
Single, twin, and bi-directional geometries. Tie layouts to HVM bollard cycle times and queue storage (636, 215).
A bi-directional lane is compact but demands tight logic to prevent conflicts at the defend line. Twin lanes (in/out) simplify signaling and reduce queue spillback risk. For each geometry, relate keepered clear width to spacing rules (232) and clear-gap calculations (322).
Size lane count from access demand in Access & Circulation (215), then check bollard cycle times and duty tests (636) to ensure green time is sufficient. Where turning or oversize vehicles are expected, coordinate geometry with Turning & Service Access (325).
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Crash Ratings Explained |
| Operations | Duty cycles, fail-state, safety | Installation Guide |
821.2 Throughput & duty
Set ops/hour targets; size drives accordingly (341, 513). Metrics justify crash rated bollard choices (542).
Start with target ops/hour per lane. Map that to drive selection—hydraulic vs electromechanical drives (513)—and confirm heat rise and duty cycle limits in Drive systems (341). Track KPIs (542) during commissioning to prove capacity before handover.
Throughput influences selection of rating-critical dependencies (421) and even bollard families (e.g., stroke time vs mass). If queues regularly exceed the holding pen, reconsider lane count or add an upstream metering strategy.
821.3 Mode schedules
Automatic, night, maintenance, event (525). Schedules prevent unsafe HVM bollard transitions.
Use the Modes of Operation (525) as a weekly calendar: normal automatic, night/quiet (night mode), maintenance windows, and event modes. Each mode should map to a state transition diagram and a simple operator label on the HMI (524).
Mode changes are gated by the interlock matrix (352) and safety circuits (343). Avoid “forbidden” transitions (e.g., raising when a vehicle is detected on top) using a fail-state philosophy and stop categories.
821.4 Credentialing & ANPR
Reader placement, whitelist logic, fallback (534). Credentials mustn’t bypass crash rated bollard interlocks (352).
Blend ACS/ANPR coordination (534) with induction loops (344) and field devices (345). Mount ANPR where stopping sight distance is adequate and glare is controlled. Implement whitelist ownership with clear audit trails.
Provide at least two fallbacks—e.g., a guarded bypass route for failures and a staffed stewarded gate. Never permit credentials to override the interlocks. Where inter-agency or blue-light access is required, document the authorization hierarchy in the ICD.
821.5 Safety zoning
Beam/loop positions, stop lines, beacons (343–345, 353). Zoning protects users at HVM bollard heads.
Create inner/outer safety zones with beam sets and loops, referenced to the defend line and hold line. Use safety signaling (353)—beacons and traffic aspects—to communicate when the lane is safe to proceed. Document device IDs in the I/O list (523).
Mitigate tailgating using loop logic (pre-presence, on-top, post-clear) and a short marshal line ahead of the readers. Add audible cues (audible beacons) where sightlines are limited.
821.6 Keepered openings
Width, guard plates, markings (325, 357). Openings must retain crash rated bollard intent.
When bollards are lowered, the opening is “keepered” by fixed neighbors. Keep effective width within the keepered dimensions in the design. Add high-contrast edge markings & signage (357) and specify skid-resistant guard plates to bridge sockets if required by the product family.
Check turning paths with Turning & Service Access (325). For vulnerable frontages, coordinate with door/frontage arrays (323) to avoid creating a new drive-around defeat.
821.7 EFO behavior in lanes
Authorize, sequence, timeouts (354). EFO must keep HVM bollard safety intact.
Define who can trigger EFO (two-person rule preferred) and how it interacts with active signals. Enforce incident modes (547) and log each event in an EFO evidence log.
Sequence: (a) annunciate; (b) arm; (c) execute; (d) verify up/down limit; (e) begin cooldown. Protect against race conditions through mutual exclusion in the PLC and movement timeouts.
821.8 Drainage details
Gullies, trench falls, anti-ponding (334, 245). Dry lanes protect crash rated bollard gear.
Keep the lane dry to protect equipment and maintain friction. Use trench falls toward gullies or a sump calculator (927). Reference drainage guidance (334) and project drainage strategy (245). Where utilities clash, consider depth/utility choices (422) or alternate foundations (332).
Specify anti-ponding details at keepered edges and ensure covers don’t snag wheels or trap debris. In flood-prone sites, add breather drains and check uplift on chambers.
821.9 SAT proofs
Lane scripts: cycle time, alarms, interlocks (638). Proofs secure HVM bollard acceptance.
Build clear lane scripts using the SAT/witness procedure (638) so witnesses can confirm: cycle-time targets (636), loop/sensor proving (633), interlock truth table (634), and EFO & failures (637).
Capture results in the FDS/SAP/ITP/SAT suite (710), including a witness evidence pack (716). Use SAT forms (918), and record KPI thresholds (542) as acceptance bands for ongoing monitoring.
Related
External resources
821 Vehicle access lanes with automatic HVM Bollards — FAQ
How many lanes do we need at peak times?
Start from observed demand in Access & Circulation (215) and model lane throughput using KPIs (542). If queues exceed the planned holding pen or spill back, add capacity or change the mode schedule.
Where should we mount ANPR and readers?
Place ANPR to avoid sun-glare, within stopping-sight distance, and pair it with loops for presence/clear signals (344). Keep credentials behind the interlock matrix (352) so they cannot force unsafe raises.
What safety devices & measures are essential?
At minimum: inner/outer safety beams, three-position loop logic, traffic beacons/aspects, and audible cues. Document IDs in the I/O list (523) and verify in 634 and 635.
How should EFO interact with normal operations?
Restrict EFO to authorized operators, annunciate clearly, and enforce cooldowns. Ensure EFO cannot be triggered during unsafe states using mutual-exclusion logic and movement timeouts, with each use recorded in the EFO evidence log and reviewed after the incident.