719.1 When to raise

Any breach of spec, drawing, or certificate dependency (421). Early NCRs protect HVM bollard compliance.

Raise an NCR the moment you detect a deviation—whether discovered during ITP checks, material inspections, or SAT witnessing. Triggers include out-of-tolerance set-out, wrong component variants, missing certificates, or evidence gaps. Early capture reduces rework, controls risk, and prevents misalignment with rating-critical dependencies.

Classify severity (e.g., safety/rating-critical vs cosmetic) to set containment timing and approval levels. Minor issues may be corrected by the installer with supervisor sign-off; rating-critical nonconformance needs client/authority visibility and may require a VO or concession route.

719.2 Containment actions

Make safe, isolate, and document. Containment reduces crash rated bollard exposure.

Containment is the immediate “make-safe” step: isolate affected bollards or lanes, revert to a fail-safe/fail-secure state as designed, and post temporary signage. Record photos and state logs per Evidence Capture Standards. For rating-critical defects, suspend SAT steps and escalate to the lead witness/client.

• Isolate energy sources (LOTO) and secure the exclusion zone.
• Record “as-found” condition, then apply temporary fixes only if approved.
• Annotate ITP line items as “contained—awaiting RCA/CA”.

719.3 Root cause analysis

5-Why or fishbone with evidence (716). Analysis prevents repeated HVM bollard issues.

Use structured evidence to drive the RCA: verify component identity (heat numbers/serials), cross-check drawings, and review commissioning logs. 5-Why exposes process gaps; a fishbone (people, methods, materials, environment, measurement, machines) avoids tunnel vision. Tie each factor back to the FDS, ITP, and approved submittals to confirm whether the deviation is a build error, a document mismatch, or a design oversight.

719.4 Corrective actions

Define rework/retest steps (714, 626). Correctives restore crash rated bollard conformity.

Specify exact rework (parts, torque, alignment, firmware), the who/when, and the retest path (ITP line, pre-commission checks, interlock verification, or SAT rerun). Update drawings if geometry changes (e.g., sleeve levels or anchor details) and re-issue to the site. For logic fixes, update the Change Control & Versioning register and distribute the new build.

719.5 Preventive actions

Training, checklist, or design tweak (545, 537). Preventives harden HVM bollard systems.

Convert the RCA into prevention: add a focused toolbox talk, extend checklists (e.g., Go/No-Go gauges for clear-gap), or refine the FDS acceptance criteria. Where patterns emerge, publish a short “lesson learned” and update supplier QA (e.g., pre-shipment verification photos). Validate effectiveness at the next suitable hold point.

719.6 Approvals & verification

Engineer/client sign-off and proofs (638). Verification legitimizes crash rated bollard fixes.

All corrections must be verified by tests aligned to the original acceptance path: ITP checks first, then witnessed SAT steps if applicable. Capture signatures in the witness/inspection forms and add them to the NCR pack. If the fix changes scope or baseline, route a concession or VO per Variations & Change Log. For UAE authority contexts, coordinate submission expectations (see Authority Submittals and SIRA Bollards (UAE)).

719.7 Traceability

Link to lot, drawing, and photo IDs (731, 911). Traceability secures HVM bollard records.

Each NCR record should reference component batches (heat numbers), drawing/version IDs, and a geo/time-stamped photo set (File Index & Naming Rules). Use consistent filenames, capture locations, and a traceability index so reviewers can replay the story without ambiguity.

719.8 Closure criteria

All tests passed; documents updated. Closure confirms crash rated bollard status.

Close the NCR only when (a) containment lifted, (b) corrective works completed, (c) retests passed and signed, and (d) as-builts/O&M updated. Archive superseded files and record the final status in the as-builts and handover index. Note any residual risks and add them to the site’s risk register (351) and Closeout Checklist & Retention.

719.9 Trend reporting

Monthly Pareto, repeats flagged (544). Trends drive HVM bollard improvement.

Publish a monthly defects dashboard: counts by type, severity, trades, and locations. Use a Pareto chart and repeat-issue flags from the operational dashboards. Feed outcomes into training, checklists, and design baselines so the same defect does not recur on later sites.

Nonconformance & Defects (NCRs) — FAQ