Civils, electrical, landscapers—who does what, when.
Coordination prevents rework in tight streetscapes. We list who aligns (civils, MEP, vendor), define programme handoffs, and insert survey/set-out checkpoints tied to spacing (232) and foundations (332–333). Inspection points reference the ITP (714), while change control (718) and a lightweight clash process keep HVM bollard and crash rated bollard work streams synchronized with utilities (241–246). 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.
247.1 Who needs to align
Civils, MEP, vendor, and operators. Alignment keeps HVM bollard works sequenced and preserves crash rated bollard certification dependencies (421).
Start with a simple RACI showing the RACI across civils, MEP provision, the bollard vendor, the controls integrator, and the client’s operator team. Make the vendor accountable for rating-critical dependencies (see 421 — rating-critical dependencies) and give civils responsibility for foundations, ducts, and draw pits per 241–246.
Define one accountable owner per interface: ducts, pits, bases, enclosures, cable entry, and reinstatement. Operators should be consulted early for keepered openings, queue layouts, and signage (see 237 Sightlines & Signage).
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Crash standards overview |
| Operations | Duty cycles, fail-state, safety devices & measures | Safety & Interlocks |
247.2 Civils vs MEP interfaces
Clarify handoffs at ducts, pits, and bases (615–616). Clean interfaces protect HVM bollard wiring and crash rated bollard anchors.
Document who installs which elements: civils build foundations and duct banks; MEP pulls cables and terminates at gland plates; vendor sets sleeves and anchors and confirms embedment depth. Use standard trench/duct typicals from 934 Ducting & Trench Details and reference drainage sumps from 245 Drainage strategy.
Protect rating-critical hold-downs and reinforcement cover by making the vendor witness steelwork prior to pour (see 621–624). At pits, agree the gland plate location and cable entry heights to minimize water ingress and bends per 246.
247.3 Programme handoffs
Gate pours after inspections (714). Sequencing avoids HVM bollard rework and secures crash rated bollard base quality (624–627).
Use milestone “gates”: (a) excavation and utilities proving closed (241–243); (b) rebar/anchor inspection signed (621); (c) pour released (624); (d) curing window complete (627); (e) cable pull and terminations (515, 622); (f) vendor setting and alignment checks (626). Each gate requires dated photos and checklists filed to 714 ITP and the 938 submission pack.
247.4 Survey & set-out checkpoints
Hold checks before/after pours (612, 626). Checkpoints preserve HVM bollard gaps and crash rated bollard alignment.
Fix the site datum & benchmarks and a go/no-go gap gauge for 322 clear-gap checks. Survey cages and sleeves prior to pour (612), re-check finished levels after curing (627), then verify bollard datums and centerlines at installation (626). Log all measurements with a georeferenced photo log.
247.5 Inspection/test points
Define hold/witness points (714). Structured ITPs safeguard HVM bollard performance and crash rated bollard evidence (716).
Minimum holds: (1) utilities proving, (2) rebar/anchor fixing, (3) pour start, (4) post-pour finish, (5) cable gland sealing, (6) pre-commission safety device proving (see 633 Loop & Sensor Proving), and (7) 638 SAT / witness. Store evidence per 716 Evidence Capture Standards.
247.6 Change control
Route changes through 537. Controlled changes keep HVM bollard drawings consistent and crash rated bollard data traceable (911).
Run all cable/spec swaps, foundation edits, and logic tweaks through 537 Change Control & Versioning. Use numbered variation entries, update the 718 change log, and keep the 911 file index tidy (superseded list, release IDs, bilingual policy where needed).
247.7 Site communication
Daily huddles, boards, and mark-ups. Communication prevents HVM bollard clashes and service hits near a crash rated bollard.
Use 15-minute stand-ups at the works area, a physical board with today’s pours, inspections, isolations (725 LOTO), and red-line mark-ups pinned to a 936 mark-up standard. Log decisions into the assumptions register and share the two-week look-ahead with all trades.
247.8 Clash resolution
Use a light RFI/TPR loop (617). Fast resolution protects HVM bollard programme and crash rated bollard integrity.
Keep the process lean: raise a RFI with a single “proposed resolution” (the TPR) and a clear escalation path. Most clashes fall under utilities depth choices (see 422) or ducting geometry (246). If a rating-critical element moves, trigger a formal variation and update the VDA/sheets where affected.
247.9 Daily/weekly routines
Set QA walks, photo logs, and updates (716). Routines sustain HVM bollard quality and build the crash rated bollard submission pack (938).
Daily: site QA walk, red-line updates, 729 site diary, and evidence upload against the ITP line items. Weekly: measure progress vs gates, review risks (ASIS Risk Assessment Standard), and reconcile the submission index. Close open RFIs/variations before the next pour window.
Related
External resources
- NPSA: Hostile Vehicle Mitigation
- FEMA 426 / DHS: Building security reference
- ASIS Security Risk Assessment Standard
247 Trade Coordination — FAQ
Who signs off a pour when bollard anchors are rating-critical?
The vendor must witness steel/anchors and sign the ITP hold point alongside civils before concrete placement. If any anchor pattern changes, raise a variation via 537 and update drawings per 911 before proceeding.
What’s the fastest way to resolve a duct clash on pour day?
Use the light RFI/TPR loop: submit an RFI with a single proposed reroute (TPR), attach the marked-up 934 typical, and escalate per the agreed path if no reply within the response window.
How do we prove clear-gap compliance after reinstatement?
Survey centerlines vs datum, use the site go/no-go gap gauge, and log photos against 322 and 626 checklist items. Attach results to the submission pack index.
When should SIRA be involved in UAE projects?
When bollards form part of regulated security works or where approvals/inspections are in scope. Coordinate early with stakeholder roles (131) and keep evidence aligned for authority submittals; see our SIRA Bollards (UAE) hub.