Sequencing works without disrupting operations.
Sequence work so security isn’t broken mid-project. Plan phases around long-lead items (415, 516), enabling works and utilities (241–246), and explicit gates tied to ITP holds and SAT readiness (714, 638). Use temporary/event modes to keep access safe (239, 327), coordinate parallel trades, and book testing windows. Maintain risk registers and practical recovery plans to protect HVM bollard and crash rated bollard availability during delivery. 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.
855.1 Master schedule
Tie permits, utilities, civils, controls, SAT (134, 241–248, 632–638). End-to-end for HVM bollard delivery.
Build a single master schedule that connects permits (see Permit & Inspection Timeline), utility proving (Utilities search methods, 241), civil pours and cure (Curing & protection, 627), panel/enclosure works (516, 528), power-on checks (632) and witness testing (638). Keep a visible chain from design to SAT / Witness Procedure so everyone knows the finish line.
Define early which parts of the system are rating-critical dependencies (421) versus logistics choices. That separation helps protect the as-tested configuration while you phase work around live operations.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) and global crash ratings | HVM Ratings & compliance |
| Operations | Duty cycles, fail-state, safety devices & measures | Installation Guide |
855.2 Critical path
Utilities proofs, concrete cure, SAT windows (243, 627, 638). Manage float.
In most HVM programmes the critical path runs through service detection & proving (241–243), first pours and cure (624–627), energization (632), interlock verification (634), and SAT booking (638). Hold a small authority float around inspections, and track “soft” blockers like panel access rooms and traffic permissions. A weekly look-ahead should call out any upcoming concrete or SAT windows that cannot slip.
855.3 Long-lead items
Drives, panels, sleeves, coatings (341, 347, 362). Secure early orders.
Place early orders for drive systems (341, 513), control panels/enclosures (520–528), cable sets (515), sleeves and transit hardware (622), and duplex/coating systems (362–366). Record serials into the Asset Register as items land. Where heat or marine exposure is expected, align coatings with environmental durability factors and coatings pages to avoid rework later.
855.4 Weather & heat
Derating and hot-concrete rules (337, 624). Protects crash rated bollard quality.
Hot climate rules affect both electrical and civil tasks. Enclosures may need sun-load control and derating curves applied to drives and electronics (516, 546). Concrete pours (624) require adjusted water/cement ratios, vibration, and curing regimes; see Hot Climate Design and Curing & Protection. Build weather downtime into the programme and add a simple “go/no-go” pour checklist at daily huddle boards.
855.5 Access & traffic
Phasing around live sites (215, 826). Keep operations safe.
Sequence excavation and reinstatement in short, well-signed phases to preserve egress width and emergency access. Use temporary/event reconfiguration (327) and perimeter roads & drop-off loops (826) to keep legitimate vehicles flowing while works proceed. For the UAE, coordinate temporary PTW and inspection windows; note any SIRA touchpoints here and link readers to SIRA Bollards (UAE).
855.6 Inspection hold points
Embed ITP milestones (714). Quality gates visible.
Make hold points visible on the master bar chart and in the Inspection & Test Plan (ITP) (714). Typical holds: rebar and sleeves/penetrations before pour, first-off alignment (first-off inspection), pre-concealment inspection, and energization readiness (632). Pair each hold with the required evidence type and witness level so the team knows what to capture without delay.
855.7 Commissioning runway
Plan FAT→SAP→SAT (715, 713, 638). Avoid last-minute churn.
Protect a clean runway from FAT to SAT readiness (715), through Site Acceptance Plan (SAP, 713) and into witnessed SAT (638). Time-box sub-phases: power-on & health (632), loop/sensor proving (633), interlocks (634), obstruction/intrusion (635) and performance/duty tests (636). Keep a witness booking log and a witness procedure script to reduce resets on the day.
855.8 Recovery plans
Alt crews, shallow options (244), resequencing. Maintain HVM bollard dates.
Pre-agree practical fallback paths: alternate crews, off-hour shifts, shallow foundations for conflict zones (Shallow foundations, 244), or temporary arrays (239) that preserve security until the permanent works land. Keep a concise risk register & governance (846) with clear Go/No-Go criteria and triggers for resequencing.
855.9 Reporting
Weekly look-ahead and risks (846). Transparent control.
Adopt a simple cadence: weekly look-ahead (next 2–3 weeks), rolling risk review (top 5 with owners), and a short progress reporting & controls (859) snapshot (RAG, decisions, blockers). Link evidence to your evidence capture standards (716) so field teams know exactly what to upload for each gate.
Related
External resources
855 Programme & Phasing — FAQ
What sits on the critical path for an HVM bollard programme?
Typically utilities proving and diversions (241–243), first pours and concrete cure (624–627), energization and controls health (632), interlock and safety tests (634–637), and the SAT booking and witness (638). Protect these steps with clear float and Go/No-Go criteria.
How do we phase works on a live site without blocking access?
Use short phases with reinstatement, stewarded temporary routes, and temporary/event modes (327). Keep egress widths and emergency access clear, and coordinate with perimeter roads & drop-off loops (826) where available.
Which long-lead items should we order first?
Drive systems (341/513), control panels and enclosures (520–528), cable looms and ducts (515–516), sleeves and transit parts (622), and coating systems matched to the environment (362–366). Add receipt evidence to the Asset Register (732).
What’s a good weekly reporting cadence?
A concise look-ahead (2–3 weeks), a top-five risk review with owners, and a one-page RAG status including blockers and decisions. Tie each gate to required evidence via your Evidence Capture Standards (716).