Designing controlled openings and operational workflows.

Enable responders without weakening protection. We translate blue-light requirements into clear openings, staging, and turning geometry, then compare removable vs automatic HVM bollard solutions (124, 821). Call points, overrides, and fail-safe/secure behavior tie to control logic (342, 355) and EFO (354). Markings (357) and regular drills feed acceptance scripts (636–638) and O&M (734, 737). 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.

233.1 Blue light requirements

Adopt turning, width, and staging rules for emergency vehicles. HVM bollard openings must meet keepered dimensions; where a crash rated bollard is removable, specify locking and re-seat checks (626).

Confirm local emergency override expectations and responder vehicle envelopes early. Document “response window” targets and any requirements for escorted access or radio/auth credentials. For HVM openings, define keepered opening geometry so adjacent posts or walls prevent unsafe widening in the field.

Where crash-rated elements are removable, specify who holds keys, how spares are controlled, and what “ready state” looks like post-incident. Cross-reference turning & service access and blue-light corridors for geometry checks.

AspectWhat mattersWhere to verify
PerformanceTested system (bollard + footing)Global crash ratings
OperationsDuty, fail-state, safety factorInstallation Guide
AccessLatched logic, audit trailModes of Operation

233.2 Removable vs automatic choices

Low-frequency access suits removable units; high-frequency needs automatic. HVM bollard drive choice aligns with duty (341); a removable crash rated bollard requires certified insert/foundation (415, 332).

Removable (passive) posts minimise CAPEX and maintenance where access is rare and supervised; they demand strong procedures for keys, keepered gaps, and re-seat checks. Automatic (active) units fit daily operations, integrate with interlocks, and support EFO logic. Tie the choice to power/HPU and controls availability.

For certified inserts and sockets, confirm the as-tested configuration in product families/variants and foundation class in foundation types. If authority approvals apply in the UAE, include a short note and link to SIRA Bollards (UAE).

233.3 Clear opening targets

State minimums for single vehicle and two-way access. HVM bollard gaps open under controlled logic (525); when a crash rated bollard is extracted, provide temporary barriers to hold risk (239).

Define “clear gap” under normal and emergency modes. For single vehicles, specify an effective width considering mirrors and turning clearance; for two-way, include a marshal plan or sequencing. When a removable is lifted, use cones, a stewarded gap, or a temporary barrier until re-seated.

Coordinate targets with clear-gap calculations and people-flow & egress so pedestrians remain safe around vehicle openings.

233.4 Call points & overrides

Locate protected call points, with latched logic and audit logs (342, 544). HVM bollard EFO rules apply (354); a crash rated bollard manual release is documented and drilled (637).

Place call points on the safe side, sheltered from impact and weather. Use a latched state in the state machine so a single valid action (e.g., responder key) moves the lane into a time-bound “Access Granted” mode. Log every action to the operational dashboard for traceability.

Test manual releases on a set schedule and confirm interlocks with modes of operation and the interlock matrix. Where fire/BMS links exist, align the override philosophy with Fire/BMS interfaces.

233.5 Staging/turning areas

Reserve clear pads near openings (325). HVM bollard posts form edges for backing; protect a nearby crash rated bollard from tire rub with sleeves (313).

Provide a staging pad for emergency vehicles to queue, turn, or reverse without striking posts. Use contrasting surface finishes and edge bollards to guide approach vectors. Where posts sit within the turning path, specify durable sleeves and sacrificial rub guards.

Verify geometry with turning & service access and check that staging does not block sightlines & signage for other users.

233.6 Fail-safe vs fail-secure

Match site philosophy (355). HVM bollard lanes might fail-secure at night; a crash rated bollard near fire routes must not trap egress.

Decide when to use fail-safe vs fail-secure states by time of day, threat level, and occupancy. Pair with illuminated safety signage and audible alarms so users understand the current mode.

Document scenarios in the alarm philosophy and test transitions during EFO & failure modes commissioning.

233.7 Incident access protocol

Script comms, roles, and interlocks (547, 352). HVM bollard states are annunciated (353); any crash rated bollard removed is reinstalled and inspected.

Create a concise runbook with roles (security, facilities, responders) and the escalation path. Include pre-arrival lane prep, steward positions, and safe reset steps. Annunciate lane state via beacons and text displays, and capture a timestamped evidence pack for audits.

After any removable is lifted, reinstall with a Go/No-Go gauge check of seat depth and lock engagement; log in the asset register & serials.

233.8 Marking & signage

High-contrast ground legends and arrows (357). HVM bollard openings are obvious in low light; mark the crash rated bollard socket cover.

Use high-contrast legends, chevrons, and arrows coordinated with safety signalling. Fit reflective markers to posts framing the opening and specify an anti-slip finish on the removable socket cover with “KEEP CLEAR” text where permitted.

For UAE projects requiring security approvals, ensure markings and signage align with site standards; include the compliance note and link to SIRA Bollards (UAE) in the submission pack.

233.9 Test & drill notes

Run quarterly drills; record times and resets (636). HVM bollard logs capture events; verify the crash rated bollard keeper/lock function post-drill.

Drill both normal access and EFO scenarios. Record cycle times, alarms, and any degraded state actions. After drills, re-seat removable posts, confirm lock engagement, and update health pings & counters baselines.

Feed results into performance & duty tests and capture evidence in the evidence capture standards pack.

Related

External resources

233 Emergency/service access with HVM Bollards — FAQ

How wide should an emergency access opening be through an HVM bollard line?
Set a keepered opening based on the largest attending vehicle envelope plus turning clearance. For single vehicles, allow effective width for mirrors and safe approach; for two-way, add sequencing or stewarding. Confirm against clear-gap calculations and update the interlock logic accordingly.
When are removable (lift-out) bollards better than automatic ones?
Choose removable where access is rare, supervised, and keys can be tightly controlled. Use automatic where daily or time-critical operations, integration with signals, or EFO are required. Always verify the tested insert/foundation and document re-seat checks after removal.
How do EFO and overrides interact with safety devices & measures?
EFO shortens normal delays to meet the response window but must respect core safety interlocks (e.g., vehicle detection, photo-eyes) unless a protected emergency override is used. Log all actions, annunciating lane state to avoid conflicting movements.
Should the lane fail-safe or fail-secure during power loss?
It depends on occupancy, time of day, and threat posture. Critical egress routes often require fail-safe; high-risk perimeters may prefer fail-secure at night. Define the philosophy in the alarm/control narrative and test transitions during commissioning and quarterly drills.