Scripted SAT, roles, evidence, and punch lists.
Independent witnessing confirms readiness. Build a clear SAT (Site Acceptance Test) script with roles and prerequisites (see this section and the chapter hub) so the live sequence mirrors interlocks and modes. Standardize evidence capture, manage NCRs, handle queries with supporting certificates, and secure sign-offs. Post-SAT, close punch items, update as-builts, and compile the final report pack. When projects in the UAE involve approvals, align your documentation with SIRA Bollards (UAE) submission practices.
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.
638.1 SAT script & roles
Publish steps, roles, and stop criteria. Structure keeps HVM bollard SAT efficient.
Start with a concise witness script that lists prerequisites, the test order, and clear Go/No-Go criteria. Assign a lead witness, test operator, safety spotter, and document controller using a simple RACI. Define stop conditions for unsafe behavior, uncontrolled faults, or repeated failures.
Cross-reference each script step to the approved interlock matrix (row IDs) and the state machine. This ensures testers are proving the exact behavior that was reviewed and signed off in design. Keep the script version-controlled with change notes (see Change Control & Versioning).
Where possible, stage a dry run without witnesses to de-risk the day. Capture timings from dress rehearsal to set realistic expectations in the formal session (e.g., number of cycles, KPI snapshots).
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Global Crash Ratings |
| Operations | Duty cycles, fail-state, safety | Installation Guide |
638.2 Pre-witness prerequisites
Close defects; freeze versions; assemble packs (631–637, 539). Prereqs protect crash rated bollard credibility.
Confirm all prior tests are complete and signed: Pre-Commission Checklist, Power-On & Controls Health, Loop & Sensor Proving, Interlock Matrix Verification, Obstruction & Intrusion Tests, Performance & Duty Tests, and EFO & Failure Modes.
Freeze software and configuration baselines (controller firmware, HMI), record versions, and print a documentation pack (I/O list, drawings, certificates, evidence standards). Prepare witness forms and a site PTW/Toolbox. Schedule observers and confirm authority submittals where applicable (e.g., SIRA).
638.3 Live test sequence
Run from safe static to dynamic tests. Sequence showcases HVM bollard behavior.
Begin in Safe Local Mode with barriers down and area secured. Verify annunciation, alarms clear, and safety circuits healthy. Step through Normal raises/lowers, then advanced modes—Modes of Operation—including Lockdown and EFO timing checks.
Prove signage & markings, operator workflows, stopping distances during obstruction tests, and behavior under simulated power events (Power Failure Modes). For multi-lane sites, include sequential and staggered operations to verify throughput.
638.4 Evidence capture
Photo/video, logs, and signed forms (716). Evidence convinces crash rated bollard reviewers.
Apply the site’s Evidence Capture Standards for photo angles (wide→detail), timestamps, and unique IDs. Record controller logs (cycle counts, health pings, first-out alarms) and attach to test steps. Annotate witness forms and collect signatures in real time.
Store media using the agreed file index & naming rules and update the photo/redline logbook. For UAE projects, keep a clean chain of evidence that aligns to what authorities expect in close-out submissions (see Submission-Pack Guidance).
638.5 Nonconformance process
Record NCRs, actions, retests (719). Process stabilizes HVM bollard closeout.
Log each failure as an NCR with photos, exact step reference, and a proposed corrective action. Assign owners and deadlines; plan a controlled retest path. Track NCR status in the submission index so outstanding issues are visible to the whole team.
Where a defect suggests deeper risk (e.g., repeated sensor faults), escalate via the change process (Change Control & Versioning) and brief stakeholders. Update the change log so the witness pack and script remain synchronized with the installed configuration.
638.6 Witness queries
Answer with certificates and data (431, 444). Answers cement crash rated bollard acceptance.
Anticipate evidence requests: certificates & reports, evidence & documentation, ITP/SAT cross-references, and controller logs. Keep originals and snapshot PDFs ready and ensure traceability (serials, firmware, panel IDs) matches the asset register.
Respond in plain language, then point to the governing requirement in the script or ITP row. For standards questions, provide the clause/source rather than paraphrasing; if an authority (e.g., SIRA) is present, log their clarifications and add to the final report pack.
638.7 Sign-off forms
Use standardized acceptance sheets. Forms finalize HVM bollard SAT.
Issue pre-filled acceptance sheets mapped to script steps and ITP hold points. Include space for remarks, NCR references, and deviations. Capture names, roles, signatures, and timestamps; align sheet IDs with the submission index and witness & inspection forms.
Where third-party agencies attend, add their sign-off lines and badges (see Third-Party Acceptance Tests). Publish a compact sign-off matrix alongside the forms to avoid end-of-day surprises.
638.8 Post-SAT actions
Close punch, update as-builts (731), train ops (737). Actions protect crash rated bollard handover.
Convert open items into a dated punch list with owners and target dates. After fixes, run targeted retests, update the photo log, and re-issue acceptance sheets for the affected steps only. Confirm spares/tools handover and record final KPIs (cycle time, ops/hour) as a baseline for O&M.
Update as-builts, the O&M manuals, and schedule client training & sign-offs. If UAE approvals apply, ensure the final submission pack aligns with SIRA expectations before final handover.
638.9 Final report pack
Bundle scripts, results, media (538). Pack completes HVM bollard approvals (938).
Deliver a single indexed ZIP or folder with: approved script, signed forms, NCR log, retest evidence, controller logs, and the media set. Include a short reader guide and a delta highlight summarizing differences from FAT or earlier versions (if any). Reference related third-party notes (Third-Party Acceptance Tests).
Use the Submission-Pack Guidance and Handover Pack Index to keep structure consistent across projects. Archive to the site’s Final Archive & Retrieval location with a stable path and version tag.
Related
External resources
- NPSA — Hostile Vehicle Mitigation (HVM) guidance
- ASIS — Security Risk Assessment Standard
- FEMA 426 / DHS — Reference Manual to Mitigate Potential Terrorist Attacks
638 SAT / Witness Procedure — FAQ
What’s the difference between SAP and SAT for bollards?
SAP is an internal Site Acceptance Procedures dry-run proving the system against specifications and interlocks without formal witnessing. SAT is the formal, observed test with a defined script, sign-offs, and authority/client presence before handover.
Which documents do witnesses usually ask to see?
Expect requests for manufacturer certificates and test reports, ITP rows linked to the script, controller logs (first-out alarms, counters), as-built drawings and the asset register, plus the evidence pack (photos, videos, signed forms).
How do we handle failures during the SAT day?
Pause the sequence, record an NCR with photos and step ID, agree corrective actions and a retest path, and update the punch list. Resume only when the Go/No-Go criteria are met and safety devices & measures are confirmed healthy.
What goes into the final SAT report pack?
The approved script, signed acceptance forms, NCR & retest log, controller logs, and a structured media set with timestamps. Include a concise reader guide, delta highlights from pre-witness tests, and links to the submission and handover pack indexes.