Legible symbols, aligned meanings.
Clear symbols and schedules make drawings self-explanatory. Standardize legends for power, I/O, safety, comms, and road markings; align tags with I/O lists and interlock matrices; and map sign types/locations to human-factors guidance. Consistent visuals help operators and reviewers understand how HVM bollards behave and are controlled. 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.
935.1 Sign family index
Regulatory, warning, guidance sets. Families keep HVM bollard lanes legible and crash rated bollard zones respected (353, 357).
Start with a short “family index” so every plan sheet reuses the same symbol sets: regulatory (must/shall), warning (hazard), and guidance (wayfinding). Map each family to where it appears: approaches to automatic lanes, defend lines, steward points, and pedestrian routes. Keep one master legend keyed to the I/O list template and the interlock matrix so tags and symbols stay in sync from CAD to commissioning.
Use consistent line weights and symbol scales in CAD (refer to CAD/BIM Standards). For hazard communication near crash-rated arrays, reference your safety signalling plan (353 Safety Signalling) and the public-realm signage around arrays (357 Signage & Markings).
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Symbols reflect tested system intent | Crash standards overview |
| Operations | States, duty cycles, fail-state wording | Acoustic limits & operations |
935.2 Placement rules
Heights, offsets, repetition. Proper placement reduces HVM bollard incidents and crash rated bollard misuse (237).
Apply clear mounting heights and offsets for each sign type relative to kerb and carriageway. Repeat key messages before the hold line and again at the device. Keep signs outside the driver cone clutter zone and maintain sightlines per 237 Sightlines & Signage. For UAE projects, confirm bilingual positioning and reflectivity with the reviewing authority; where SIRA applies, insert a brief note in the drawings and link to SIRA Bollards (UAE).
935.3 Surface markings
Stop lines, hatch, arrows. Markings organise HVM bollard approaches and protect crash rated bollard fronts (821, 323).
Use high-contrast stop lines at the device face, directional arrows upstream, and hatching to protect the bollard front. Keep markings aligned to the vehicle access lane geometry and any frontage protection arrays. Specify minimum retroreflectivity and maintenance thresholds so markings remain legible through the lifecycle (see Preventive Maintenance Plan).
935.4 Beacons & signals
States, priorities, night modes. Signals communicate HVM bollard status and crash rated bollard hazards (546, 342).
Define signal aspects and priorities in the controls package so field beacons mirror PLC states. Tie each aspect to a named state in the state machine, the interlock matrix, and the safety signalling plan. Include night auto-dimming and a maintenance flash code in the HMI to reduce nuisance alarms.
935.5 Accessibility cues
Tactile, contrast, audible. Cues align HVM bollard arrays with inclusive access and crash rated bollard safety (238).
Pair high-contrast lane edges with tactile paving and, where needed, audible beacons at pedestrian conflicts. Keep cues consistent with the streetscape palette set in 238 Streetscape Integration. Avoid handlebar traps and protect refuge islands with clear wayfinding and lighting.
935.6 Multilingual policies
Arabic/English symbol sets. Policies prevent HVM bollard confusion and crash rated bollard errors (133).
Adopt bilingual (Arabic/English) symbol sets with a defined portal language for primary calls-to-action. For each sign family, keep one translation master and a change-control log. Where country requirements vary, cross-reference 133 Country & Authority Variations and record the reviewer’s acceptance in the submission pack.
935.7 Maintenance schedule
Clean/refresh cycles and criteria. Upkeep sustains HVM bollard readability and crash rated bollard compliance (733, 734).
Write a simple schedule: weekly visual checks, monthly cleaning, quarterly luminance/retroreflectivity sampling, and annual refresh where thresholds are not met. Log tasks in the O&M manuals and plan periodic works in the Preventive Maintenance Plan. For automatic lanes, coordinate with operations to avoid peak windows and note any night/quiet mode adjustments.
935.8 SAT verification list
Photos, luminance, positions. Verification proves HVM bollard readiness and crash rated bollard acceptance (638, 716).
Before sign-off, capture a wide→detail photo set, measure luminance/retroreflectivity samples, and confirm beacon aspects per the SAT / Witness Procedure. Store evidence following Evidence Capture Standards, with file naming and reviewer traceability linked to the drawing index.
935.9 Schedule fields
ID, legend, location, fixings. Structured schedules simplify HVM bollard procurement and crash rated bollard auditing (851, 911).
Include fields that downstream teams actually use: sign ID, family/type, legend text, bilingual requirement, mounting height, offset, substrate/fixings, location reference, night mode, maintenance threshold, and drawing cross-reference. Make it exportable to the BOQ Skeleton, and align filenames to the File Index & Naming Rules. Keep tags consistent with the I/O list and terminal maps.
Related
External resources
- BSI — Impact test specifications (VSB systems)
- ASTM F2656 — Crash test standard (overview)
- NPSA — Hostile Vehicle Mitigation guidance
935 Signage, Markings & Schedules — FAQ
What’s the fastest way to standardize symbols across drawings?
Create a single “family index” block and reference it on every sheet. Keep IDs aligned to the I/O list and interlock matrix so control states and field symbols never drift.
How do we choose mounting heights and offsets?
Follow your roads/streets standard and the project’s sightline study. Repeat key signs before the hold line and at the device, and keep signs out of the driver’s critical cone. See 237 Sightlines & Signage.
What needs to be in the signage schedule?
At minimum: ID, family/type, legend text, bilingual requirement, mounting height/offset, substrate/fixings, location reference, night mode, and maintenance threshold—exportable to the BOQ and consistent with the file naming rules.
How is compliance verified at SAT?
Use a checklist: daytime/night photos, luminance/retroreflectivity samples, position checks against the CAD baseline, and signal aspect tests mapped to PLC states. File evidence per Evidence Capture Standards and the SAT / Witness Procedure.