VO handling, approvals, and traceability.
Control change, keep proof. Define what constitutes a variation, route requests through approvals, and bump versions with clear rules (see 537 Change Control & Versioning and 115 Versioning & Numbering). Update evidence and assess cost/time/risk (see 841 Cost ranges, 855 Programme & Phasing, 351 Hazard analysis). Archive superseded items and communicate changes so automatic HVM bollard behavior, crash ratings, and 638 SAT / Witness Procedure stay aligned with what’s actually installed. This page sits within this section and the wider chapter hub. For UAE authority reviews, see 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.
718.1 Change triggers
Utilities finds, scope clarifications, or authority notes (617, 717). Triggers formalize HVM bollard changes.
Typical triggers include confirmed utility clashes (617 Utility Conflicts), reviewer requests from 717 Authority Submittals, vendor anti-downgrade/equivalence clauses, and site constraints uncovered during 631 pre-commission checks. Any trigger should be logged, referenced to drawings/specs, and raised as a Change Request (CR).
Define what is a Variation Order (VO) versus a minor editorial change. Use a simple triage: (a) safety or rating-critical, (b) cost/time impact, (c) documentation only. Escalate (a) and (b) via CR→VO; process (c) via controlled versioning with release notes.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system alignment (bollard + footing) | 421 Rating-critical dependencies |
| Operations | Modes, fail-state, safety devices | 355 Fail-safe/secure states |
| Evidence | Before/after photos, timestamps, chain of custody | 716 Evidence standards |
718.2 Impact assessment
Cost/time, safety, rating, and aesthetics (841, 445, 316). Assessments protect crash rated bollard intent.
Evaluate cost (materials, rework, commissioning), programme impact (855 phasing), and operational risk using the site hazard analysis. Confirm whether the change affects the tested product family/variant or dependencies (depth, reinforcement, drainage).
Check user-facing impacts: colour/finish, heads & attachments, and streetscape cues. Document the assessment in the CR form with a clear recommendation (proceed/decline/defer).
718.3 Approval workflow
CR form, reviewers, and SLA (537). Workflow prevents ad-hoc HVM bollard edits.
Use a single CR template with IDs, originator, affected documents, and an approver SLA. Route to design lead, Owner’s Engineer, and client PM. Where certification or authority posture is in scope, include 717 submittals and note whether a re-submission is required before works proceed. Maintain a configuration baseline and freeze changes before SAT booking.
When a CR is approved and impacts cost/scope/time, issue a VO and update the master log with a Release ID and sign-off matrix.
718.4 Documentation updates
Rev drawings, specs, ITP lines (931, 433, 714). Updates keep crash rated bollard packs aligned.
Apply controlled version bumps across drawings (931 CAD/BIM Standards), specs (433 Specification template), and test points (714 ITP). Update the Photo/Redline Logbook (937) and record deltas in release notes. Keep a superseded file archive (939) with checksums.
718.5 Communication plan
Brief trades and stakeholders (247). Comms avoid HVM bollard site surprises.
Issue concise change briefs to site, MEP, and controls teams (247 Trade Coordination) with what/why/when and a clear “effective from” date. For UAE projects, record any authority feedback and link to SIRA correspondence. Include a “reset-to-normal” checklist for operators if modes or signage change.
718.6 Implementation controls
Hold points and pre-start checks (611, 714). Controls ensure crash rated bollard build quality.
Set hold points before excavation, reinforcement, pour, and energization (611 Pre-works & permits). Update ITP witness/inspection lines (714) and ensure NCR routes are ready (719 Nonconformance & Defects). Only proceed when the baseline documents match what’s on the ground.
718.7 Evidence & records
Before/after photos, logs (716). Records justify HVM bollard variations.
Capture wide→detail photo sets with timestamps and geotags per lane/device. Keep CR/VO forms, reviewer comments, and updated calculations in a single submission pack (938). For SAT changes, append an addendum to the witness pack (638).
718.8 Risk register
Update residual risks (351). Register maintains crash rated bollard vigilance.
Re-score hazards after each approved change and update mitigations, e.g., signage, annunciation (353), or operational KPIs (542). Tie residual risks to the handover and training plan (737).
718.9 Post-change review
Check KPIs and lessons (542, 118). Reviews refine HVM bollard practice.
After implementation, verify that KPIs (ops/hour, cycle time, alarms) remain within alert thresholds (542). Record wins and pain points in the project 118 Change Log and feed improvements back into the next change-control release.
Related
External resources
- ASIS Security Risk Assessment Standard
- FEMA 426 / DHS Reference Manual
- NPSA — Hostile Vehicle Mitigation
718 Variations & Change Log — FAQ
What’s the difference between a Change Request (CR) and a Variation Order (VO)?
A CR starts the evaluation and approval process for any change. A VO is issued after approval when the change affects cost, scope, or programme. Editorial/document-only changes use controlled versioning without a VO.
Do I need to resubmit to authorities after an approved change?
If the change alters certified performance, safety devices, or the as-tested configuration, yes—update drawings/specs and resubmit per 717 Authority Submittals. Minor documentation edits usually do not require resubmission.
How do we keep the team in sync after a change?
Issue a concise change brief with what/why/when, “effective from” dates, and updated file links. Update the ITP lines, set hold points, and record before/after evidence per 716 Evidence standards.
What should be checked after implementation?
Verify KPIs (ops/hour, cycle time, alarms), confirm signage/annunciation, close any NCRs, and log lessons in the project 118 Change Log. Update the risk register and training materials if operations changed.