Closeout, defects, spares, and training readiness.
Hand over a system that will keep its rating in service. Structure snag lists with clear ownership and priorities, attach close-out evidence, and bundle O&M manuals and training (733, 737). Confirm spares/warranty (854), deliver final drawings/models (731), and demonstrate operation. Define retention/defects periods and capture lessons to improve future HVM bollard and crash rated bollard projects (844, 739). This page sits under this section and the broader chapter hub. If your project requires authority closeout in Dubai, also 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.
639.1 Snag list structure
Categorize safety, functionality, cosmetic. Structure speeds HVM bollard fixes.
Keep the NCR stream separate from the snag list, but cross-reference items so owners can track risk and schedule impact. Group snags into safety (anything affecting protection or safety devices & measures), functionality (operations, alarms, modes), and cosmetic (finishes, labels). Use clear, testable acceptance criteria and link each item to evidence in your submission/hand-over packs.
Each line should show a unique ID, location (lane/array/panel), description, acceptance criteria, owner, target date, and evidence link. Tie safety and functionality snags back to commissioning results in 630 Commissioning & safety tests so retests are easy to schedule and verify.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Global crash ratings |
| Operations | Duty, fail-state, safety interlocks | Automatic HVM Bollard Controls |
| Documentation | Traceable evidence & sign-offs | Handover Pack Index |
639.2 Priority & ownership
Assign P1–P3 with owners/dates. Priority keeps crash rated bollard risks visible.
Define a simple matrix: P1 (safety/operation-blocking), P2 (function affected but safe workaround), P3 (cosmetic/admin). Give each item an accountable owner and due date, and escalate P1s through the project Nonconformance & Defects process if they threaten programme or acceptance. Show status (Open/Blocked/Ready for Retest/Closed) and retest witness requirements.
639.3 Close-out evidence
Attach before/after photos and tests (716). Evidence proves HVM bollard closure.
Use the Evidence Capture Standards for image framing, timestamps, and geo-tagging. For functional snags, attach the retest clip or log extract (e.g., interlock row retest, EFO timing). Keep an evidence chain so reviewers can follow requirement → test → sign-off without ambiguity.
639.4 O&M & training bundle
Provide manuals, SOPs, training records (733, 737). Bundles sustain crash rated bollard uptime.
Bundle approved O&M manuals, the preventive maintenance plan, spare parts list, and the signed training attendance with competency checks. Include operator quick-guides for modes of operation and a laminated reset-to-normal checklist at each panel.
639.5 Spares & warranty
List part numbers, quantities, terms (854). Spares reduce HVM bollard downtime.
Reference the project’s Warranty & Spares Policy and confirm lead times and storage conditions (e.g., seals/fluids). Tie warranty terms to maintenance evidence—missed inspections can void cover. Provide a small “event kit” for incident response (cones, signage, basic tools) and ensure it aligns with the SLA.
639.6 Final drawings & models
Deliver as-builts and data (731). Drawings preserve crash rated bollard traceability.
Issue the as-built drawings & models with updated asset register and serials (732). Confirm model parameters match installed equipment (drive type, HPU/EM), interlock diagram IDs, and cable schedules. Include a concise reader guide and a transmittal log.
639.7 Client demonstrations
Show modes, resets, and EFO (525, 354). Demos build HVM bollard operator confidence.
Run a short demonstration script covering normal operation, queued vehicles, mode changes, EFO, and recovery from common faults. Capture sign-offs and ensure video/photo evidence meets the evidence standard. Add a brief note about authority witnessing where applicable.
639.8 Retention & defects period
State durations and response times. Clarity protects crash rated bollard service.
Record the retention schedule, defects-liability period, and response windows (e.g., P1 within 4 hours). Align these with your Service Levels & Availability target and note any requirements for authority sign-off in the UAE. Provide contact channels and escalation paths for out-of-hours issues.
639.9 Lessons learned
Record improvements into 118 and 537. Lessons elevate HVM bollard practice.
Summarize what slowed acceptance (e.g., unclear acceptance criteria, missing labels, unclear alarm philosophy). Add concise deltas to the site Change Log (118) and Change Control & Versioning (537) so the next project benefits immediately.
Related
External resources
- ASIS Security Risk Assessment Standard
- NPSA — Hostile Vehicle Mitigation guidance
- FEMA 426 / DHS reference manual
639 Snagging & Handover — FAQ
What’s the difference between a snag and an NCR?
A snag is a fix needed before handover but not necessarily a formal nonconformance. An NCR records a failure against a requirement and must be cleared through a defined review and sign-off path. High-risk snags often become NCRs.
Which evidence closes a functionality snag?
Provide before/after photos plus a retest artefact that proves behavior—e.g., interlock row pass sheet, EFO timing video, or controller log extract—following the site’s Evidence Capture Standards.
What must be inside the O&M and training bundle?
Approved O&M manuals, a preventive maintenance plan, spare parts list, training attendance with competency checks, and quick-reference operator guides (including reset-to-normal steps and contact/escalation details).
How do retention and defects periods link to SLAs?
Retention ensures funds until defects are resolved; the defects-liability period defines how long issues are rectified at no cost. Both should align with your availability/response targets in the SLA so service levels remain achievable.