Boilerplate clauses aligned to ratings and dependencies.

Write specs that lock in performance, not just part numbers. Start with a performance clause referencing standards (411–414), then identify acceptable families/variants (415) and rating-critical dependencies (421). Define foundation/installation (332, 611–629), controls/safety (341–355), and documentation/QA (714, 716). Add substitution/equivalence rules (414, 435), commissioning requirements (631–638), and O&M/warranty expectations (733, 854) for HVM bollard systems. 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.

433.1 Performance clause

Reference the standard, vehicle/speed, penetration, and acceptance. Performance-first writing safeguards HVM bollard outcomes (411–414).

State performance using the target standard and rating string, not brand names. Example: “Provide bollard system certified to IWA 14-1 or ASTM F2656 with maximum P-value of … and penetration line at the defend line.” Clarify as-tested configuration bounds, orientation, and allowable tolerances.

Include acceptance language: the installed system shall meet the specified rating with documented comparability to the certificate test article; deviations require prior written approval. Cite both standard overviews (411) and terminology (412) to guide submittals.

AspectWhat mattersWhere to verify
PerformanceCertified system (bollard + footing + array)Read rating strings (413)
OperationsDuty, fail-state, safety devicesInstallation Guide
ComplianceLimits, orientation, comparabilityCertificates & evidence (431)

433.2 Product identification

List allowable families/variants and certificate IDs (415, 431). Identification blocks off-spec crash rated bollard swaps.

Specify by family and allowable variant window: height, diameter, sleeve/finish, and foundation class must match the certificate or an approved allowable variant. Require the certificate ID, lab accreditation, and family/variant matrix (415).

Disallow “sleeve-only upgrades” that alter geometry/mass without evidence. Cross-check scope using our certificate scope checklist and acceptance pack (431).

433.3 Foundation & install requirements

Specify base type, depth, rebar, concrete, and tolerances (332–333, 612). Install fidelity keeps HVM bollard performance intact.

Define the foundation class (e.g., Deep-Socket vs Shallow-Rail), embedment, concrete grade/cure, and rebar cover. Tie to site constraints via depth & utilities choices (422) and utility proving (241). State alignment and clear-gap rule tolerances.

Installation clauses should reference setting-out & benchmarks (612), curing & protection (627), and drainage strategy (334). Where groundwater is present, include sump/NRV and buoyancy checks (see groundwater/soil effects, 423).

433.4 Controls & safety devices

Define drives, interlocks, detectors, and signage (341–345, 353). Clear controls protect a crash rated bollard lane.

Call up drive type (hydraulic or electromechanical), control architecture, and interlock matrix. Specify safety devices & measures: induction loops, photo-eyes, signals, and EFO triggers. Reference safety signalling (353) and state machines (526).

Include fail-safe/secure states, local/remote modes, and alarm/SCADA/BMS signals. For UAE approvals, note any SIRA-specific interfaces and submit to SIRA Bollards (UAE) where required.

433.5 Documentation & QA

Require ITP lines, cube tests, surveys, and photo logs (714, 716). QA makes HVM bollard evidence review-ready (938).

List submittals: certificates with unedited footage, drawings, ITP, ITP points (714), and evidence capture standards (716). Require surveys & alignment checks with geo-tagged photos and marked array centreline.

Provide a structured submission pack (938) and transmittal log. Specify bilingual policy if the client requires Arabic/English deliverables.

433.6 Substitution/equivalence rules

Set strict proof for any change (414–435). Rules prevent hidden downgrades of the crash rated bollard.

Include an anti-downgrade clause and an equivalence clause. Require energy parity, comparable orientation, and foundation/array equivalence per standards equivalency (414). Changes must be evidenced by certified variants or accepted modelling correlated to tests (416), with reviewer right of rejection (435).

433.7 Testing & commissioning

Cite FAT/SAT steps and pass/fail bands (715, 631–638). Testing proves HVM bollard readiness.

Define FAT vs SAT readiness (715), pre-commission checks (631), loop/sensor proving (633), interlock verification (634), intrusion and obstruction tests (635), duty tests (636), and EFO/failure-mode drills (637). Include witness procedure steps and acceptance bands for times, movement, and safety inhibits.

433.8 O&M & training

Mandate manuals, spares, and drills (733, 737). O&M sustains crash rated bollard availability.

Require structured O&M manuals (733), a preventive maintenance plan (734), and operator training with reset-to-normal checklists. Include emergency response playbooks and post-incident inspection steps (735). Specify minimum toolkits and documentation of MTBF and counters where telemetry exists.

433.9 Warranty & spares

Define durations and minimum kit lists. Warranty ensures long-term HVM bollard serviceability (854).

State coverage for structure, drive, controls, coatings, and consumables, with response SLAs aligned to site criticality. Call up a common spares policy sized to duty, plus replenishment timelines. Reference Warranty & Spares Policy (854) for standard kit lists.

Related

External resources

433 Specification template for HVM/Crash-Rated Bollards — FAQ

What must a performance clause include for crash-rated bollards?
Reference the governing standard (e.g., IWA 14-1 or ASTM F2656), vehicle class and speed band, penetration limit and defend line, orientation, and any tolerances. Require comparability to the certified as-tested configuration and define the acceptance evidence to be submitted.
How do I prevent “look-alike” substitutions that downgrade performance?
Use an anti-downgrade clause coupled with an equivalence clause. Demand energy parity, foundation/array equivalence, and documentation (certified variant or correlated modelling). Reserve the right to reject if evidence is incomplete or non-comparable.
Which installation details are rating-critical?
Foundation class and depth, rebar and concrete grade/cure, alignment and clear-gap, and drainage/groundwater measures. These must match the rating-critical dependencies and tolerances documented in the certificate and installation drawings.
What tests prove readiness at handover?
Pre-commission checks, loop/sensor proving, interlock verification, obstruction/intrusion tests, performance/duty cycles, and EFO/failure-mode drills. Witnessed SAT should document pass/fail bands and evidence per the commissioning script.