Model, scope, compliance, and SLAs.
How you buy determines whether performance survives into installation. We compare contracting models, clarify scope boundaries, and embed compliance rules so substitutions cannot erode rating or safety. You’ll plan warranty/SLAs, programme commitments, and evidence gates that keep HVM bollard and crash rated bollard outcomes aligned with the tested configuration from tender to handover. 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.
847.1 Contracting model
Supply-only, supply-install, or turnkey. Model affects HVM bollard risk allocation.
Choose a model that preserves the as-tested configuration and defines who owns coordination, testing, and authority submissions. In supply-only, the client carries integration risk; in supply-install, the vendor assumes installation quality; in turnkey, a single party is accountable for performance, programme, and closeout. Match model to the site’s risk management appetite and internal capabilities.
Where approvals apply (Dubai projects), state early that the contractor must manage SIRA processes and deliver evidence that maps to 638 SAT / Witness Procedure and 710 FDS / SAP / ITP / SAT. This keeps accountability clear for SAT readiness and demonstrations.
A practical rule: the more interfaces (civil, MEP, controls), the stronger the case for a turnkey or supply-install route to control interface risks and maintain 421 rating-critical dependencies.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | How to read ratings |
| Operations | Duty cycles, fail-state, safety | Installation Guide |
847.2 Prequalification
Experience, certificates, SAT record (431, 638). PQ filters crash rated bollard vendors.
Request vendor evidence that aligns with 431 Documentation & certificates, including laboratory accreditation, crash rating certificates, and unedited test footage links. Score prior projects with witnessed 638 SAT and provide contactable references.
Prequal questions should probe foundation options, 338 Value Engineering approach, and controls integration (Fire/BMS/SCADA at 346). Evidence reduces downgrade risk during tender.
847.3 Scope definition
Clear boundaries across trades (247, 433). Scope clarity protects HVM bollard outcomes.
Write a responsibility matrix that splits civil works (excavation, foundations, drainage), power/controls, and bollard supply. Reference 247 Trade Coordination and embed the project’s specification using 433 Specification template. Call up drawings, ITP, and commissioning artifacts from 630 Commissioning & safety tests.
Define interfaces explicitly: utilities relocation, ducting, sumps, and panel locations. Where authorities are in scope (e.g., Dubai), include SIRA submittals as a deliverable with time allowances in programme.
847.4 Technical compliance
Mandatory rating dependencies (421). Compliance locks crash rated bollard performance.
State that any change to footing geometry, reinforcement, or installation method is rating-critical (see 421). Require an evidence pack that ties the proposed product to its tested configuration, including foundation typicals and standards equivalency where needed (e.g., IWA↔ASTM).
Enforce a formal anti-downgrade clause and require supplier sign-off that the installation will meet the rating string for the defined layout and soil conditions.
847.5 Alternates & VE rules
Allow evidence-based VE (338, 414, 435). Rules avoid HVM bollard downgrades.
Allow alternates only with a complete Equivalence Evidence Pack referencing 338 VE, 414 Standards equivalency, and the contract’s 435 anti-downgrade clauses. Specify like-for-like proof on orientation, footing class, and penetration band.
Value engineering must not touch rating-critical dependencies. Savings should target non-critical finishes, access covers, or controllable OPEX (e.g., energy budget at 517).
847.6 Warranty & SLAs
Availability, response, spares (738, 733). Terms sustain crash rated bollard uptime.
Define availability targets aligned to operations (see 738 Service Levels & Availability) and bind them with an SLA: response window, restoration targets, and service credits. Require a 733 O&M manual, CMMS-ready asset register (732), and a critical spares kit.
For automatic lanes, call up KPI reporting (ops/hour, cycle time) per 542 KPI Set. This allows SLA audits using objective data rather than subjective impressions.
847.7 Programme commitments
Milestones, liquidated damages (134, 855). Commitments keep HVM bollard on track.
Build a milestone ladder tied to design freeze, procurement, civil works, power-on, SAP execution, SAT, and handover. Coordinate authority float against 717 Authority Submittals. For complex sites, align with the permit timeline in 134 and phasing rules in 855.
Use liquidated damages sparingly but clearly for critical dates (e.g., SAT window) to protect operational go-live, without incentivizing corner-cutting on ITP hold points.
847.8 Payment milestones
Evidence-based stages (716, 736). Milestones align crash rated bollard cashflow.
Stage payments on evidence, not elapsed time: (a) submittals approved (716 Evidence Capture Standards), (b) factory ready (FAT, where applicable), (c) foundations cast and inspected, (d) power-on/controls health, (e) SAT pass, (f) handover pack acceptance per 736 Handover Pack Index.
Each claim should attach a mini evidence index with filenames that match the site’s 911 file naming rules.
847.9 Post-award onboarding
Kickoff, submittal calendar, SAP/SAT plan (713, 717). Onboarding accelerates HVM bollard delivery.
Hold a structured kickoff to confirm roles (RACI), submittal index, and a dated calendar for drawings, SAP, and SAT. Use the guidance in 713 SAP vs SAT and ensure authority submissions per 717 are booked with realistic review windows.
Agree how variations will be handled (718 Variations & Change Log) and establish a running decision gate cadence tied to the programme’s look-ahead.
Related
External resources
- NPSA — Hostile Vehicle Mitigation overview
- ASTM F2656 — Crash test standard (overview)
- ASIS Security Risk Assessment Standard
847 Procurement Strategy — FAQ
Which contracting model best protects the crash rating?
Turnkey or supply-install usually protects rating-critical interfaces because one party owns civil, power/controls, and commissioning. Supply-only can work if you add strict anti-downgrade clauses, a complete evidence pack, and witnessed SAT obligations.
Can we accept alternates during tender without increasing downgrade risk?
Yes—if the bidder submits an Equivalence Evidence Pack that proves the same rating string, footing class, orientation, and penetration band. Map proofs to standards equivalency and keep hold points in the ITP.
What documents should we request up front to speed approvals?
Ask for certificates and unedited test videos (431), a filled specification template (433), a dated SAP/SAT plan (713/638), and an evidence capture index (716). This reduces rework and clarifies responsibilities.
How should SLAs be written for automatic HVM bollard lanes?
Set an availability target (e.g., 99% per lane), define response and restoration windows, require KPI telemetry (542), include a critical spares kit, and align service credits to impact severity.