Use-cases by risk level; low-speed vs HVM tiers and examples.
Map protection purposes to performance early. We contrast low-speed protection with HVM bollard requirements, outline SIRA (Dubai) tiers, and cross-reference global crash rating systems. Avoid mis-matches that fail reviews by using the decision tools in 432 Design selection guide: HVM vs Low-Speed Bollards and spacing rules in 232 Spacing rules for HVM & Crash-Rated Bollards. See sector contexts via 370 The Four HVM Bollard Purposes and log your evidence for 938 Submission-Pack Guidance and 431 Documentation & certificates. Where approvals apply in the UAE, review the SIRA Bollards (UAE) hub.
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.
123.1 Purposes mapped to risk
Define what you’re protecting (people, assets) and credible approach (221–229). HVM bollard use is justified when hostile impact is plausible; a crash rated bollard is specified when certification is required for acceptance (411, 717).
Start with a concise VDA that identifies likely approach vectors, run-up distance, and target vulnerability. If the credible scenario is accidental (e.g., parking bumps), low-speed measures may suffice; if deliberate intent or higher speeds are possible, you are in HVM territory.
Tie purpose to the four contexts in 370. For example, Public Safety near pedestrian areas may push towards tighter clear-gaps, while Vehicle Access & Traffic Control balances throughput with security. Document your purpose in the VDA and cross-reference it in your submission pack (938).
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Crash Standards Overview |
| Operations | Duty cycle, fail-state, safety devices & measures | Installation Guide |
123.2 Low-speed vs HVM in practice
Low-speed controls daily bumps and parking conflicts; HVM mitigates deliberate impacts. If run-up and vectors exist (222, 225), prefer HVM bollard arrays. Where approvals demand proof, choose a crash rated bollard with matching rating string (413).
Use PAS 170-1 or ASTM F3016 for storefront-type risks; they are not substitutes for HVM crash ratings such as IWA 14-1 or ASTM F2656. If your VDA shows ≥20–30 m run-up or heavy-vehicle access, escalate to HVM with certified products and arrays that satisfy 232 spacing rules.
123.3 SIRA tiers (light/average/heavy) basics
Map site category to tier and standoff (133, 213). HVM bollard selection follows tier outcomes; crash rated bollard ratings should equal or exceed tier expectations and evidence (431).
Within UAE projects in scope, use the SIRA hub to align with Dubai’s light/average/heavy tiers. Select arrays and certified models that meet or exceed the tiered requirement, keeping practical depth classes and drainage strategies in mind.
123.4 Global ratings at a glance
Summaries of vehicles/speeds/penetration (411–414) convert into design inputs. Use them to compare HVM bollard options and shortlist a crash rated bollard family that fits constraints (415, 332).
Use how to read rating strings (vehicle mass, speed, penetration) to filter products. Check equivalency guidance and confirm rating-critical dependencies (soil, footing, array spacing) before shortlisting.
123.5 Matching tier to use-case
Frontages, lanes, and perimeters differ (371–374). Combine people proximity (231) with run-up (222) to pick tier. HVM bollard arrays must still meet clear gaps (232). A crash rated bollard must be viable with local foundations (332–334).
For frontages, use tighter spacing and near-door arrays (323). For corners/pinch points, adjust patterns (324). For service access, balance turning needs with protection (325). Verify the chosen model’s foundation class (332).
123.6 Common mis-matches & risks
Too-low tier, ignored angles, or utilities blocking depth (243, 422) lead to rejection. HVM bollard arrays fail if gaps drift (232). Crash rated bollard claims fail if variants deviate from the certificate (415, 421).
Typical red flags: assuming low-speed measures deter hostile threats; using non-certified variants (different sleeves, embedment, or foundation cage) then claiming certified performance; letting clear-gaps creep during construction. Prevent these with pre-construction checks (631) and setting-out controls (612).
123.7 Upgrade paths from low-speed
Triggers: new threats, incidents, or authority direction (446). Convert layouts to HVM bollard arrays (321–326) and replace units with a crash rated bollard model that fits depth/drainage realities (244, 245).
Prioritize frontage hotspots, then integrate lanes or perimeters. Where depth is constrained by utilities, evaluate shallow foundations and confirm rating applicability via 421. Record the rationale and phased plan in your upgrade paths document.
123.8 Evidence you need for selection
VDA summary, drawings with clear-gap calcs, and rating/certificate excerpts (229, 322, 431). This proves HVM bollard suitability and anchors the crash rated bollard choice in your submission pack (938).
Minimum evidence: (a) VDA (run-up, vectors, standoff), (b) array drawings with clear-gap calculations, (c) Product rating string and certificate scope, and (d) foundation details consistent with the tested configuration. Use 917 Submission covers and 916 Evidence templates.
123.9 Real-world examples
Door arrays with near-door spacing (323), corner chicanes (324), and service access (325) show outcomes. Each pairs an HVM bollard pattern with a crash rated bollard certificate note and foundation sketch (331–334).
(a) Retail frontage door set: 1.2–1.5 m standoff, near-door array per 323; HVM model with IWA 14-1 rating and matching footing (332). (b) Corner chicane: deflect vector then capture (324). (c) Service access: integrate turning envelopes (325) and verify drainage (245).
Related
External resources
123 HVM Bollards & Low-Speed: Purposes & Performance Tiers — FAQ
How do I decide between low-speed and HVM bollards?
Use a VDA to check run-up distance, likely approach vectors, and target proximity to people. If deliberate impact or higher speeds are credible, specify HVM with certified ratings; if risks are accidental and slow, low-speed standards like PAS 170-1/ASTM F3016 can suffice.
Do SIRA tiers replace global crash ratings?
No. SIRA tiers frame local protection levels (light/average/heavy). You still select certified products with global crash ratings (e.g., IWA 14-1 or ASTM F2656) that meet or exceed the tier’s expectations and site conditions.
What evidence must be in my submission pack?
Include the VDA summary, array drawings with clear-gap calculations, the product’s rating string and certificate excerpt, and footing details consistent with the tested configuration, plus any SIRA-specific requirements if in scope.
What causes review rejections?
Common issues: underspecified tier, missed impact angles, utilities limiting depth without an approved shallow footing, clear-gap drift during installation, or product variants deviating from the certificate.