How requirements differ (UAE focus), common overlaps, red flags.
Ratings are global; approvals are local. We summarize UAE/SIRA expectations for HVM (Hostile Vehicle Mitigation) bollard and crash rated bollard submittals, compare GCC practices, and map global ratings (411–416) to local tiers (123). You’ll see documentation and witness differences that affect the ITP (Inspection & Test Plan) and SAT, plus language/formatting rules and lead times that inform your submission-pack strategy.
For context and deeper pathways, see this section and the chapter hub Basics of HVM bollards. If your project is in Dubai, review the dedicated SIRA Bollards (UAE) notes.
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.
133.1 UAE focus and SIRA notes
Expect emphasis on evidence, clear-gap acceptance, and documented witness steps (232, 638). HVM bollard submissions must use tidy packs; a crash rated bollard certificate must align to local tier language (123).
In the UAE, reviewers typically look for three things: (a) a standards-based rating string that clearly states vehicle class, impact speed, and outcome; (b) proof that the as-tested configuration matches the proposed works (foundation class, spacing, depth); and (c) a clear demonstration that clear-gap rules are preserved in-situ. Where Dubai SIRA is involved, add bilingual labels, consistent photo evidence, and a witness plan tied to your ITP.
Keep your index tight using the Submission-Pack Guidance (938) and match terms to Documentation & Certificates (431). For SAT, align with witness procedure (638) and pre-declare hold/witness points in the ITP (714).
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Rated system (bollard + footing) | Crash standards overview |
| Operations | Duty cycle, fail-state, safety devices & measures | Safety & Interlocks |
133.2 GCC contrasts to expect
Documentation style and witness frequency vary. Plan float for reviews (134) and tailor HVM bollard packs accordingly. Crash rated bollard terminology should remain standards-based (411–413).
Across GCC authorities, differences appear in reviewer checklists, bilingual requirements, sign-off formats, and whether SAT is witnessed on every site or by sampling. Build programme float using Programme & Phasing (855) and surface authority-specific needs in your Authority Submittals (717). Keep rating terminology (411–413) intact to avoid specification drift.
133.3 Global ratings vs local tiers
Bridge rating strings to tier tables (235). This defends HVM bollard selection and clarifies a crash rated bollard’s sufficiency for local approvals.
Use global standards (e.g., IWA 14-1 / ASTM F2656) as the evidence base, then map the selected rating to your local Purpose/Tier Matrix (235). This shows reviewers that the proposed solution is “fit for purpose” under the local tier framework, not just nominally “crash-rated.” Where tiers differ by frontage, approach vector, or site comparability, annotate the matrix and cite the VDA (220–229).
133.4 Documentation variances
Language, stamping, and photo rules differ. Use 716 for evidence standards and 938 for index formats. Applies to both HVM bollard and crash rated bollard submissions.
Common variances: official language, certification stamps (engineer’s seal, chamber stamp), photo EXIF/time-stamps, and how evidence is captured (716). Keep one bilingual “Reader Guide” page in your pack, follow index & covers (938), and reference certificate scope (431) so reviewers can trace each claim to a document or photo.
133.5 Inspection and witness points
Book early; align ITP (714) and SAT (638). HVM bollard arrays may require live gap checks; a crash rated bollard may need dependency verification (421).
Declare witness points in the ITP and cross-reference the SAT plan. Many authorities request a live clear-gap check and verification of rating-critical dependencies (421)—for example, confirming actual foundation depth class, reinforcing, grout beds, and control interlocks. Align inspection forms with Witness & Inspection Forms (918).
133.6 Language & formatting requirements
Adopt dual-language labels and symbol policies (357). Keeps HVM bollard signage coherent and crash rated bollard documentation readable.
Apply a consistent bilingual policy to covers, drawing notes, signage & markings (357), and SAT forms. Keep filenames versioned per File Index & Naming Rules (911) and use a stable self-canonical target in your pack metadata to reduce duplicate-content ambiguity during multi-party submissions.
133.7 Lead times & review cycles
Allow for holidays/coordination. Build time into programme (855) so HVM bollard milestones and crash rated bollard approvals don’t slip.
Plan at least one consolidation cycle on your side before submission, and a formal response window on the authority side. Add float for holidays and cross-discipline coordination (security, electrical, civil). Use Programme & Phasing (855) to stage SAT windows, and keep change logs (718) short and traceable.
133.8 Local sourcing considerations
Validate material grades/coatings (361–366) and service support. HVM bollard reliability and crash rated bollard spares must be available (842).
Authorities may ask for proof of local support, spare parts, and documented maintenance plans. Reference materials selection (361), coatings (362), and lifecycle & maintenance (842). If proposing alternatives, protect intent with anti-downgrade/equivalence clauses (435).
133.9 Example variations table
Provide a simple matrix: requirement → evidence → authority note. Use it to tune HVM bollard packs and to present crash rated bollard certificates cleanly.
| Requirement | Evidence to attach | Authority note |
|---|---|---|
| Crash rating proof | Certificate + test report; highlight product family/variant | Use standard rating string |
| Clear-gap compliance | Layout with dimensions; calc per clear-gap calculations | Live check during SAT (638) |
| Foundation match | Section & rebar details per foundation type | Declare as rating-critical dependency |
| Controls & safety | ITP steps for loops/photo-eyes; interlock matrix | Include bilingual labels (357) |
Related
External resources
133 Country & Authority Variations Overview — FAQ
What does SIRA typically require beyond the crash certificate?
SIRA commonly expects bilingual labels, tidy evidence packs, and a witnessed SAT tied to your ITP. Show that clear-gap rules are met on site and that foundations and controls match the as-tested configuration.
How do I map a global rating to a local performance tier?
Use the Purpose/Tier Matrix (235). Start with the rating string (vehicle, speed, outcome) and cross-reference the site’s purpose and approach speeds from the VDA to justify the selected tier.
When is a witness point mandatory?
Authorities vary, but most require witnessing for SAT and any rating-critical dependency checks (e.g., foundation depth class, interlocks). Declare these in the ITP and book early.
Which documents belong in a country-specific submission pack?
Include the crash certificate/test report, layout and clear-gap calculations, foundation/controls details, bilingual signage plans, an ITP with witness points, and a concise Reader Guide that explains the pack.