Prepare a SAT package.
From the FAT-verified system to a site acceptance test (SAT) package keyed to field installation
Preparing a site acceptance test (SAT) package is the engineering process of restructuring the FAT-verified system documentation for verification against the as-installed condition on site. SAT is the second formal acceptance milestone: the system shipped from FAT must be re-verified after field installation, after cable termination, after loop check-out, and after the field-engineering punch-list closure. SAT failures most commonly stem from cable misterminations, JB labeling errors, and field-installed instruments that differ from the FAT-witnessed configuration. SAT-readiness drives the mechanical completion (MC) declaration.
Inputs.
- +FAT-verified system documentation
- +As-installed cable schedule (field-verified)
- +As-installed JB schedule (field-verified)
- +Per-loop check sheets (FAT-witnessed)
- +Site punch list to date
Outputs.
- →Per-loop SAT walk-down check sheet (sensor through final element with field-verified columns)
- →Per-system SAT punch list
- →MC declaration cover sheet per system
- →RFSU declaration cover sheet per system
- →Closeout report ready for the owner-engineer sign-off
| Aspect | FAT | SAT |
|---|---|---|
| Location | Vendor / integrator facility | Project site |
| Focus | Functional verification per spec | Field verification per as-installed |
| Cable terminations | Simulated at I/O | Field-verified at JB and termination strip |
| Loop walks | Logic only | Sensor through final element on site |
| Punch list | Vendor punch | Site punch + field-engineering punch |
| Sign-off | FAT witness procedure | MC and RFSU declarations |
Step by step.
- 01
Reconcile FAT scope to as-installed
Differences between the FAT-witnessed configuration and the as-installed configuration surface row-by-row. Field-installed substitutions get flagged for engineering review before SAT.
- 02
Build the per-loop SAT walk-down
Per-loop check sheet from the loop folder index populates with the field-verified columns blank. The commissioning electrician walks each loop on site.
- 03
Cable termination verification
Per-cable run-out walks: cable tag, JB terminal block, wire color, and termination strip number verified against the as-installed cable schedule.
- 04
JB labeling verification
Per-JB walk: terminal block labeling verified against the JB schedule. Mislabeled terminals are the most common SAT punch item.
- 05
Per-system punch list
Open punch items collect per system. MC declaration cannot be issued with open critical punch items; the punch tracker drives the closeout sequence.
- 06
Issue MC and RFSU declarations
Per-system MC declaration when critical punch items close. RFSU declaration when the system is ready for energization. Owner-engineer sign-off follows.
Common questions.
Why does SAT need separate documentation from FAT?
Field installation introduces failure modes that FAT cannot test: cable misterminations, JB labeling errors, field-installed substitutions for spec items, and integration with the actual process equipment. SAT is the formal acceptance against the as-installed condition; without it, mechanical completion cannot be declared.
Can the SAT walk-down sheet capture field-engineering punch items?
Yes. Field-engineering punch is distinct from vendor punch (which closes against vendor work) and from operations punch (which closes against operating procedures). The per-loop walk-down sheet carries a punch column scoped to the loop.
Start a workspace.
Upload the source documents, run the workflow, ship the document in the column shape the next consumer expects.