Naming schema: mechanism, rating, size, finish, operation, and options.
A consistent name compresses the spec into a single, unambiguous string: diameter × height × rating (for crash rated bollard models) + operation/power + finish/sleeve + foundation class. Use it on drawings, BOQs, and submittals to prevent substitutions. Tie naming to rating pages (411–416), selection (432–435), and documentation rules (911, 938). Template and checklist included for quick reuse. 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.
125.1 The naming pattern explained
Format: Ø×H × Rating [+ operation/power] [+ finish/sleeve] [+ foundation class]. This compresses HVM bollard requirements and the exact crash rating into one string used on drawings/BOQs (931, 938).
The point of the convention is speed and clarity. Anyone reviewing a BOQ can confirm the rating string, the operating mechanism (manual vs automatic), the finish/sleeve, and the footing class without jumping across documents. It also supports procurement controls (433) and blocks unintended “equivalent” swaps (435). Use the same pattern on drawings, model names, and filenames (911).
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Crash ratings overview |
| Operations | Duty cycles, fail-state, safety devices & measures | Automatic controls |
125.2 Mandatory fields (size, height, rating)
Diameter, effective height (312), and rating string (413) are mandatory. Without the rating, an HVM bollard claim is weak; a crash-tested bollard without penetration/speed data is not reviewable (431).
Size is written as “Ødiameter×height” in millimetres unless otherwise noted. The rating string must match certificates (e.g., IWA 14-1 or ASTM F2656) and include vehicle class, speed, impact angle, and penetration (P-value) where applicable. Cross-check the geometry against height setting and diameter & section to avoid conflicts.
125.3 Optional fields (finish, sleeve, LED)
Add sleeve/finish (366), illumination (313), and reflectors if specified. Confirm optional items don’t breach crash rated bollard family limits (415, 421).
When adding finishes, use precise terms (e.g., “Duplex stainless sleeve, bead-blast”) rather than vague “stainless finish.” Where illumination is required, specify type (LED ring, top beacon), voltage, and any accessory power draw so electrical design (514) and corrosion strategy remain aligned.
125.4 Operation & power in the name
Append “Auto-Hyd” or “Auto-EM,” voltage/phase, and EFO note (341, 354). This ties HVM bollard controls to power design (511, 514). For a crash rated bollard, ensure automatic variant is covered (413).
Example suffixes: “Auto-Hyd, 3-phase 400 V, EFO 1.5 s,” or “Auto-EM, 230 V, fail-secure (down).” Always confirm the duty cycle, fail-state (fail-safe up / fail-secure down), and safety devices & measures (343) match the intent of operations (525) and emergency modes (547).
125.5 Foundation depth & class tags
Tag “Deep-Socket” or “Shallow-Rail” with drawing ref (332–334). This keeps HVM bollard arrays buildable and aligns a crash rated bollard with tested foundations (421).
Depth and foundation class depend on utilities, soil, and rating-critical dependencies (421, 422). Reference typical details (933) and design checks (333). If you must switch class (e.g., conflicts at shallow depth), revisit the spacing rules and structural capacities (331) before approving the change.
125.6 Examples: correct vs incorrect
Correct: “Ø273×900 P-XX Auto-Hyd, Duplex SS, Shallow-Rail (332-D05).” Incorrect: missing rating or vague “stainless finish.” HVM bollard clarity speeds approvals; crash rated bollard ambiguity triggers NCRs (719).
- Good: Ø219×900 ASTM F2656 M30-P1, Auto-EM 230 V, LED ring, Deep-Socket (333-S02).
- Bad: “219×900 stainless bollard, automatic”—no standard, no vehicle class/speed, no footing tag.
125.7 How naming helps procurement
Exact strings block substitutions (435), preserve HVM bollard performance, and keep the crash rated bollard within its certified family (415). Use the name in RFIs, quotation lines, and purchase orders so all parties mirror the same requirement.
Pair the naming string with the evidence pack (431) and an anti-downgrade clause (435). If a vendor proposes an alternative, they must supply equivalent tested performance (same rating string & footing class) and supporting documentation.
125.8 How naming helps drawings
Names embed acceptance parameters for spacing/height checks (232, 312) and foundation details (331–333). SAT witnesses can trace a crash rated bollard quickly (638, 431).
On plans and schedules, keep the name, tag, and detail reference together (e.g., “B-12: Ø219×900 M30-P1 Auto-EM, Shallow-Rail (933-T03)”). This reduces markup churn and improves handover accuracy (736). If layouts change, verify that the naming string still matches the final detail and rating documents.
125.9 Template & checklist
Use the naming checklist and BOQ template (912–919). They capture HVM bollard dependencies and required crash rated bollard evidence (421, 444).
- Download: Handover pack indexes & checklists (919)
- Download: Submission indexes & covers (917)
- See also: Specification template (433)
Related
External resources
125 Structured Bollard Name — FAQ
What fields are mandatory in the structured bollard name?
Diameter, effective height, and a full rating string (e.g., IWA/ASTM vehicle class, speed, angle, and penetration) are mandatory. Without the rating, reviewers can’t confirm performance.
Should I include operation and power in the name?
Yes when automatic: append “Auto-Hyd” or “Auto-EM”, voltage/phase, and any EFO, duty-cycle, or fail-state notes to align with electrical and controls design.
How do I tag foundations in the name?
Add a footing class (e.g., “Shallow-Rail” or “Deep-Socket”) plus the drawing reference so the named product matches a tested foundation type.
What common mistakes should we avoid?
Vague finishes (“stainless”), missing standards, omitting penetration/speed, or leaving out the footing class. These cause substitutions, RFIs, or NCRs during approvals.