Performance-first, dependency-safe specs.
Write specs that preserve outcomes, not just part numbers. Start with performance clauses and rating strings, then lock product families/variants and rating-critical dependencies. Define foundations, controls/safety, QA/ITP, commissioning, O&M, and substitution/equivalence rules with required evidence. Clear sections prevent downgrades and keep crash rated bollard intent intact from tender to SAT. 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.
852.1 Section map
Organize by performance, products, execution, QA, handover. Map to 433 and 714.
Use a five-part layout: (a) performance outcomes (ratings, scope, and interfaces), (b) acceptable product families/variants, (c) foundations and execution methods, (d) controls, safety devices & measures, and (e) evidence, QA and handover. Cross-reference the 433 Specification template for clause language and the 714 ITP for inspection/witness points.
This structure keeps the rating string central, so the selected system remains equivalent from tender through SAT. Add a short “Reader guide” line at the start of the section listing the linked documents the contractor must consult (433, 421, 714, 638, 736).
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Crash Ratings Explained |
| Operations | Duty cycles, fail-state, safety | Installation Guide |
852.2 Performance clause
State required standard and rating string (411–414, 413). Locks HVM bollard outcomes.
Write the performance clause first. Name the standard (e.g., IWA 14-1 or ASTM F2656) and include the full rating string with vehicle class, speed, impact angle and penetration. State any equivalency mapping if you’ll accept more than one standard.
Clarify scope boundaries: defend line, required penetration distance, debris acceptance, and orientation dependency. Link to 413 How to read ratings and 414 Standards equivalency so reviewers can check consistency.
852.3 Acceptable families/variants
Define families, allowable options (415). Protect crash rated bollard pedigree.
List acceptable product families/variants by certificate scope and allowable variants. Require the bidder to prove the proposed variant sits within the published family window (geometry, materials, drive type) and preserves the as-tested configuration.
Where multiple finish or sleeve options exist, warn that sleeve-only upgrades do not change the underlying rating. Tie back to 435 Anti-Downgrade so substitutions can’t erode penetration or debris criteria.
852.4 Foundations/execution
Reference 332–336 methods. Execution preserves certification (421).
Specify the foundation class (e.g., Deep-Socket or Shallow-Rail) and set out methods per 332 Foundation types, 334 Drainage, and 421 Rating-critical dependencies. Call out datum/benchmarks, alignment tolerances, grout beds and curing protection; these preserve the certified performance.
Include checks for utilities conflicts and groundwater (243, 614), and require a pre-pour hold point in the ITP. Link execution to the commissioning plan so foundation drainage and ducting are verified before power-on (631–633).
852.5 Controls & safety parts
Cite 341–347, 352–357. Safe behavior equals HVM bollard compliance.
List mandatory control architecture elements (panel type, PLC/Controller, I/O list), required interlocks and safety devices & measures. Reference 340 Electrical & Controls, 352 Interlock matrix, 353 Safety signalling, and 524 HMI & local controls.
Define fail-state philosophy (secure vs safe), EFO behavior, annunciation priorities and test points. Require that any change to devices that affect safety or detection sensitivity is controlled through the change-control process and re-verified during SAT (638).
852.6 Evidence & submittals
Certificates, ITP, SAT scripts (431, 714, 638). Reviewer-ready.
Demand an evidence pack with authenticated certificates (431), the project-specific ITP (714), SAT/witness scripts (638), and as-built/O&M handover items (730–736). Specify page-ID references in file names and a 911 File index & naming rules compliant transmittal.
For third-party equivalence submissions, require unedited test footage, report numbers and laboratory accreditation details. Include a submission checklist and a witness booking window so reviewers can plan site attendance where needed.
852.7 Equivalence rules
Proof demands per 414 and anti-downgrade 435. No brochure swaps.
Make equivalence a process, not a brochure swap. State that proposed alternatives must meet the exact rating string and as-tested configuration, with evidence as defined in 414 Equivalency and controlled via 435 Anti-Downgrade.
Require an Equivalence Evidence Pack with comparability notes, test IDs, and orientation match. If a bidder cannot prove family-window and base equivalence, reject or escalate for engineering review.
852.8 Warranties & spares
Tie to 854 and 842 availability. Lifecycle secured.
Reference warranty term, response windows and availability targets. Align with 854 Warranty & Spares Policy and ensure maintainability per 842 Lifecycle & maintenance. Define critical spares, reorder points and training deliverables for client teams (737–738).
Make warranty contingent on use of approved consumables, adherence to the preventive maintenance plan, and evidence logging in the CMMS. Specify a defects-liability period and service credits for missed availability targets where applicable.
852.9 Record language
Mandate Page IDs in contractor submittals (911). Keeps crash rated bollard lineage clear.
All submittals must carry the page code and live link for traceability (e.g., “852 Specification Sections”). Use the 911 rules for filenames, include transmittal logs, and maintain a superseded-file list. This preserves the evidence chain if products change or clarifications arise.
Include a short “record language” paragraph inside each clause stating where data lands (drawing, schedule, checklist, or photo log) so reviewers can find it quickly and maintain self-consistent archives at closeout.
Related
External resources
- BSI – Impact Test Specifications for VSBs
- ASTM F2656 – Standard for Vehicle Crash Testing
- NPSA – Hostile Vehicle Mitigation Guidance
852 Specification Sections — FAQ
Where exactly should the rating string appear in my spec?
Place it in the lead performance clause (852.2), together with the named standard and acceptance limits. Repeat the same rating string in the BOQ item description and in the SAT acceptance criteria so the required outcome is consistent end-to-end.
Can I name a specific manufacturer while still allowing equals?
Yes—list acceptable families/variants (852.3) and state that equals must match the rating string and the as-tested configuration with a complete Equivalence Evidence Pack. Use the Anti-Downgrade clause so superficial brochure matches are rejected.
What evidence is acceptable for equivalence?
Authenticated certificates with report numbers, lab accreditation details, unedited test videos, and documentation proving family-window and base equivalence. Summaries or marketing sheets alone are not sufficient.
How do I stop substitutions during procurement?
Anchor the project to performance first (852.2), lock families/variants (852.3), and enforce change control via the ITP and SAT scripts (852.6). Require the anti-downgrade clause and reject any proposal that lacks full evidence.