Client, consultant, vendor, contractor roles across lifecycle with RACI hints.
Clear ownership prevents drift on HVM bollard and crash rated bollard projects. This page assigns who leads risk/requirements (221–229, 371–374), who makes product/rating choices (432–435), and who executes QA/ITP (714) and submissions (717, 938). Use the RACI snapshot to align client, consultant, contractor, and vendor, then set escalation paths that keep permits (134) and programme (855) on track. For orientation, see this section and the chapter hub. When UAE approvals are in scope, align with SIRA Bollards (UAE).
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.
131.1 Client & end user
Define protection purpose, service levels, and acceptable modes (525). Confirm when HVM bollard is mandatory and when a crash rated bollard certificate is required for approvals (717, 431).
Clients set the Operational Requirements and success criteria: target threats, permitted penetration distance, allowable throughput for access lanes, and acceptable modes. The client also defines life-cycle obligations (spares, SLAs) and signs off the KPI set that will be monitored in operations.
On projects that require formal approvals, the client confirms whether HVM is mandatory, when a crash-rated certificate is required, and what constitutes acceptable evidence in the submission pack. They remain the accountable owner for scope and budget changes.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing), rating & P-value | Crash standards overview |
| Operations | Duty cycle, fail-state, safety devices & measures | Installation Guide |
131.2 Consultant & designer
Own VDA (221–229), spacing/arrays (232, 321–326), and specs (433). Ensure HVM bollard intent survives cost/VE (338) and that any crash rated bollard selection matches tested configuration (421).
The consultant leads the Vehicle Dynamics Assessment, converts threat-led decisions into spacing rules and array patterns, and authors a specification that locks rating, foundation class, and rating-critical dependencies. During value engineering, they protect security outcomes and document any allowable substitutions via anti-downgrade/equivalence clauses.
131.3 Main contractor & civils
Deliver foundations, set-out, and drainage (611–629, 331–334). Protect HVM bollard tolerances (626) and preserve crash rated bollard dimensions/cover (421).
The main contractor coordinates utilities, dewatering, and civils sequencing so bollard pits, conduits, and drainage sumps meet design. They maintain datum control and alignment within the tolerance checks and pour to the specified depth class and cover so the certified configuration is preserved.
131.4 Specialist vendor & installer
Provide certificates (431), variant limits (415), and method/ITP inputs (714). Commission automatic HVM bollard lanes (631–639) and prove crash rated bollard dependencies onsite (421).
The specialist vendor confirms model selection and variant family limits, supplies installation/commissioning method inputs for the ITP, and executes pre-commission, safety proving, and SAT/witness. They furnish the certificate pack and evidence photos showing that the installed state matches the tested configuration.
131.5 Security operator & FM
Define SOPs, alarms, and KPIs (524, 536, 542). Maintain HVM bollard availability (842) and track crash rated bollard inspections after incidents (547, 735).
Operations teams agree HMI layouts, alarms, and SOPs; configure counters/health pings; and track KPI thresholds. FM plans preventive maintenance and spares, keeps availability targets, and triggers post-incident inspections per Emergency Modes & Incident Response and Post-Incident Inspection.
131.6 Authorities & reviewers
Set evidence format (717, 938) and witness points (638). Expect clear HVM bollard logic and complete crash rated bollard certificates (431).
Reviewing authorities specify submission format and review gates (e.g., submission-pack guidance), name witness/hold points during SAT, and verify the evidence establishes site comparability to the tested case. Where applicable, coordinate early with SIRA (Dubai) to avoid late redesigns.
131.7 Who owns which decisions
Matrix ties decisions to roles: rating/tier (432), foundations (332), controls (342–345). This prevents HVM bollard drift and orphaned crash rated bollard claims.
Typical allocations: (a) Client is accountable for purpose/tier and availability; (b) Consultant is accountable for rating choice and foundation class via foundation types and clear-gap calculations; (c) Vendor is responsible for model/variant and proving dependencies; (d) Contractor is responsible for set-out/tolerances; (e) Operator/FM is accountable for SOPs and KPIs.
131.8 RACI snapshot
Responsible/Accountable/Consulted/Informed for each table row in 135 and each ITP line (714). Aligns HVM bollard delivery and crash rated bollard approval path.
Create a one-page RACI aligned to the Required Documents Map and the ITP steps (pre-commission, safety proving, performance tests, SAT). Use the same role names across the programme and submissions to avoid ambiguity.
131.9 Escalation path
Escalate via documented NCRs/changes (719, 537). Use evidence (716) to resolve HVM bollard spacing or crash rated bollard equivalence disputes (414).
When coordination stalls, escalate with a formal NCR or change request referencing the affected requirement, drawing, or test. Attach photos and measurements that demonstrate site comparability per equivalency rules and your evidence capture standard. Name decision owners and timescales in the escalation note.
Related
External resources
- NPSA: Hostile Vehicle Mitigation guidance
- ASIS: Security Risk Assessment Standard
- FEMA 426 / DHS: Building Security
131 Stakeholders & Responsibilities — FAQ
Who decides whether a site needs HVM or a crash-rated solution?
The client is accountable for the decision, advised by the consultant’s VDA and purpose/tier matrix. Where approvals apply, reviewers may require crash-rated evidence and certificates.
What proves that a selected model is acceptable for our site?
A complete certificate pack plus installation evidence that the installed configuration matches the tested system (foundation class, spacing, height) and is comparable to the certified test.
How should responsibilities be recorded across contractors and vendors?
Use a one-page RACI aligned with the Required Documents Map and ITP. Keep role names consistent across drawings, submissions, and the programme.
What happens if build conditions force a change from the specified foundation or depth?
Raise a change with evidence. Re-check rating-critical dependencies and obtain designer/vendor approval; reviewers may require updated calculations or equivalency justification.