Differences, sequencing, and evidence requirements.
Understand the difference between Site Acceptance Plan (SAP) and Site Acceptance Test (SAT). SAP sets scope, roles, and evidence before anyone witnesses. SAT executes structured scripts to prove HVM bollard behavior and crash rated bollard safeguards. This page links to ITP (714), commissioning pages (631–637), evidence standards (716), and witness pack structure (638) so approvals land first time. For UAE authority contexts, see SIRA Bollards (UAE). Upward reading: this section hub FDS / SAP / ITP / SAT (710) and chapter hub HVM Bollards Documentation (700). Link installation only when needed: 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.
713.1 Definitions & objectives
SAP = plan/readiness; SAT = witnessed execution. Both prove HVM bollard compliance for crash rated bollard systems.
The SAP is a planning package: it fixes scope, responsibilities, scripts, prerequisites, and the evidence model before testing starts. The SAT is the formal, witnessed execution that demonstrates the installed lane meets the specification and safety devices & measures. Together, they reduce rework and keep acceptance objective.
Keep definitions consistent with the Third-Party Acceptance Tests (538) page and ensure traceability to the modes of operation (525) and interlock matrix (352).
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing + controls) | Global crash ratings |
| Operations | Duty cycles, fail-state, safety measures | Installation Guide |
713.2 Who prepares each
Vendor drafts SAP; contractor/consultant validate; client witnesses SAT (631–638). Roles prevent HVM bollard gaps.
Typically, the vendor prepares the SAP because it reflects product specifics and controls logic, while the main contractor integrates it with the Inspection & Test Plan (ITP). The consultant verifies coverage against the change control & versioning (537) baseline, and the client (or Owner’s Engineer) acts as lead witness at SAT.
713.3 Pre-requisites
Close ITP holds, finalize FDS, and freeze firmware (714, 711, 537). Prereqs protect crash rated bollard tests.
Before SAT, ensure all ITP hold points are cleared, the FDS (711) is approved, and the controls build is locked under versioning (537). Commissioning pages 631 to 637 should be complete with evidence suitable for SAT packs.
713.4 Test environments
FAT benches vs live lanes. Environments de-risk HVM bollard commissioning (715).
Factory testing proves core functions on benches or rigged arrays (715 FAT vs SAT Readiness), while SAT proves end-to-end behavior in live lanes with real devices and traffic management in place. Use FAT to de-risk firmware, I/O, and interlock matrix logic; use SAT to confirm site-specific dependencies (drainage, utilities, signage) and human factors.
713.5 Typical scripts
Cause–effect, interlocks, EFO, failure modes (352, 354, 518). Scripts validate crash rated bollard safety.
At minimum, include: (a) normal raises/lowers across modes, (b) interlock row-by-row checks per 634 Interlock Matrix Verification, (c) EFO timing and safeguards, and (d) failure modes such as power-fail (518) and comms loss. Reference 638 SAT / Witness Procedure for script format.
713.6 Evidence required
Photos, logs, KPIs, signatures (716, 542). Evidence anchors HVM bollard acceptance.
Define evidence up front: annotated wide→detail photo sets, PLC/HMI COS logs, KPI snapshots (542), calibration notes, and signed witness sheets. Follow 716 Evidence Capture Standards to keep an auditable evidence chain.
713.7 Witness roles
Lead, recorder, approver, safety officer (538). Roles streamline crash rated bollard sign-off.
Separate duties: a lead witness runs the agenda, a recorder captures results, an approver signs per sign-off matrix, and a safety officer controls the exclusion zone and stop-work triggers. These roles and a prepared witness pack (638) reduce delays.
713.8 Pass/fail criteria
Published thresholds and remedies (714, 719). Criteria keep HVM bollard decisions objective.
Use objective thresholds in the ITP (714): cycle time limits, EFO timing windows, annunciation behavior, stopping distances, and acceptable defect classes. Remedy paths and NCR management (719) must be stated so failures don’t stall the programme. Protect rating-critical dependencies with quick, controlled retests.
713.9 Handover of records
Pack to archive and submit (538, 938). Records finalize crash rated bollard approvals.
On completion, compile a signed pack: scripts, filled forms, logs, photos/video, submission-pack guidance (938), and links to as-builts (731), O&M (733), and training (737). Keep a searchable index and file IDs aligned to the project’s transmittal log.
Related
External resources
- NPSA — Hostile Vehicle Mitigation (overview)
- ASTM F2656 — Crash testing overview
- BSI — Impact test specifications for VSBs
713 SAP vs SAT — FAQ
What’s the practical difference between SAP and SAT?
The SAP is the planning/readiness package—scope, roles, sequence, prerequisites, and evidence. The SAT is the witnessed execution on the installed lane, producing signed results tied to the SAP and ITP.
Do we still need SAT if we pass FAT?
Yes. FAT proves functions in a controlled environment; SAT proves the installed system with real devices, site dependencies, and human factors under live conditions.
Who signs off the SAT?
Signatories follow the project’s sign-off matrix—typically the client/Owner’s Engineer as lead witness, with contractor and vendor representatives. The consultant confirms compliance to the approved spec.
What evidence must be in the witness pack?
Scripts, filled forms, photos/video, PLC/HMI logs, KPI snapshots, calibration notes, certificates, and signatures—indexed per the evidence standards and submission guidance.