353.1 Signal priorities & colors

Define R/Y/G meanings; reserve red for stop/unsafe. Clear priorities prevent driver error around an HVM bollard and a crash rated bollard portal.

Adopt a simple, unambiguous priority scheme: Red = Stop/Unsafe, Amber = Caution/Prepare, Green = Proceed. Keep meanings identical at every lane and portal so drivers never “learn” exceptions. Where an EFO condition exists, red aspects and audible alarms must dominate all other signals. Tie priorities to the site’s alarm philosophy and the control logic so states and transitions are testable.

Color coding should extend to signal aspects, message stacks, and indicator LEDs on panels/HMIs. Use consistent placement (e.g., R-Y-G top-to-bottom) to avoid mode error. For mixed-purpose sites, add a lane status repeater where downstream visibility is limited (turning & service access).

353.2 Sounders/beacons placement

Place audible/visual alerts within approach cones, not behind posts (237). Alerts must cut through ambient noise near HVM bollard lanes.

Mount beacons and sounders where they are visible/audible in the driver’s driver cone. Avoid shadowing behind posts or signage. For multi-lane portals, angle fixtures to cover the design approach angles without dazzling adjacent lanes. Add a secondary beacon on the non-preferred approach side if sightlines are constrained (sightlines & signage).

Keep sound pressure level 6–10 dB above ambient at the hold line, but below nuisance thresholds for nearby uses. Where background noise varies (e.g., loading yards), specify adaptive sounders that sense ambient SPL. Use weather-sealed, high-IP housings and proper glanding & cabling to resist dust and spray.

353.3 Messaging for operators

Use plain text/icons for states and faults (524). Messages guide safe recovery around a crash rated bollard.

Operator messages should be short, specific, and action-oriented: “Gate inhibited — vehicle detected” beats cryptic fault codes. Pair text with a clear icon and color state. Map every message to a cause, a required action, and a local control that resolves it where appropriate (e.g., “Clear vehicle from loop; press Reset”). Keep vocabulary consistent with your modes of operation and interlock matrix.

For safety-critical alerts, use latched messages that require deliberate acknowledgment to clear. Log each change-of-state to support KPI tracking and incident review.

353.4 Road markings & signs

Stop bars, arrows, lane IDs, and clearance lines align with movements (325). Markings keep HVM bollard portals legible.

Paint a high-contrast hold line ahead of the portal, with lane identifiers and directional arrows that match the permitted movement. Where queues form, add “queue safety” markings and conspicuous “No Tailgating” signs to address access control risks. Use reflective paints/granules suited to local weathering and heavy turn-in.

Coordinate signs with the site’s wayfinding and desire lines so drivers read the right message at the right time. For UAE projects that require authority review, align legends and positioning with the submission pack and note SIRA where applicable (SIRA Bollards (UAE)).

353.5 Human factors basics

Large fonts, contrast, and short dwell times. Good HF reduces mistakes at an HVM bollard interface.

Design for glanceability: use large, legible fonts; plain language; and high luminance contrast. Limit dwell time per message to ~2–3 seconds; cycle longer texts only when the lane is inhibited, never while granting proceed. Position HMIs within ergonomic reach for stewards and within the driver cone for vehicle users.

Reduce cognitive load by grouping related signals (e.g., RYG stack with message display immediately adjacent). Avoid mixed conventions across lanes. Where pedestrians and vehicles intermix, add pedestrian repeaters and clear egress cues to preserve the egress cone.

353.6 Night/low-visibility rules

Anti-glare lighting, reflective bands, and consistent luminance (316, 366). Night cues protect a crash rated bollard approach.

Provide even, non-glare lighting across the approach, hold line, and portal face. Avoid hotspots that wash out signals. Add retro-reflective contrast bands or sleeves on fixed posts to increase conspicuity, and ensure beacon intensity auto-dims at night to prevent dazzling. Verify color rendering so red/amber/green remain distinct under installed luminaires.

In dusty, coastal, or fog-prone sites, spec sealed lenses, wipers or easy-clean covers, and a cleaning interval in the maintenance plan. Align finishes and colors with aesthetic finishes without compromising conspicuity.

353.7 Maintenance/testing

Log lamp tests, buzzer checks, and lens cleaning (734). Upkeep sustains HVM bollard safety.

Build a simple routine: (a) weekly lamp-test and buzzer check; (b) monthly lens/hood cleaning; (c) quarterly verification of message lists against the current software version; and (d) annual illumination and SPL spot checks at the hold line. Record results in the asset register and witness/inspection forms.

Include spares for lenses, LED modules, and sounders in the site’s spares policy. Where message stacks are CMS-driven, apply change control & versioning so wording updates remain traceable.

353.8 Fail indications

Default to safe: lamp fail → flash+message; detector fail → inhibit (536). Failsafe protects a crash rated bollard lane.

Define clear fail behaviors: (1) Lamp failure → switch to alternating flash plus “Lamp fault — Steward Only Operation”; (2) Loop fault → inhibit raise and show “Vehicle detect fault — Lane Inhibited”; (3) Beacon fault → transfer indication to message display and remote repeater. All faults should raise an alarm in the supervisory system (SCADA/BMS signals) and log to the COS history.

Design for diagnostic clarity: use watchdog timers, error codes that map to SAT steps, and on-panel labels referencing the ITP section for quick isolation. Where a bypass key switch is fitted, show a persistent “Bypass active” indicator and auto-timeout.

353.9 Examples & layouts

Show a typical portal stack: RYG + messages + beacons. Layouts standardize HVM bollard sites.

A proven stack from top to bottom: (a) R-Y-G traffic aspects; (b) message display (two-line, high-contrast); (c) blue beacon pair for EFO/priority override; (d) lane ID panel. Repeat a compact indicator set at the far post for bi-directional approaches. Add pavement hold lines and arrows, plus a steward call point on the safe side of the portal. Mirror this arrangement across similar entrances so stewards and drivers don’t relearn layouts at each site.

Document the layout in CAD with mounting heights, offsets, and cable/gland references, and include the drawing in the signage, markings & schedules pack. Reference it in the SAT / witness procedure so evidence is straightforward.

353 Safety Signalling — FAQ