Productivity & Best Practices 3 min readORG-F23

Site Acceptance Test Checklist for Automation Systems: Readiness, Tests, and Evidence

Share

SAT proves that the installed automation system works in its real site interfaces, infrastructure and operating context. It must begin from an accepted baseline and a readiness gate, then preserve results, constraints, defects, retests and handover decisions.

The short answer

Confirm installation completion, power, grounding, networks, field terminations, utilities, permits, simulation strategy, safe test conditions and authorized people before starting. Reconcile the delivered hardware, software, configuration and FAT punch list. Test site-specific I/O, communications, interfaces, alarms, sequences, access, time synchronization, failover and recovery against approved cases. Record restrictions and actual plant conditions. Every deviation receives an impact, owner, disposition and retest; acceptance states exactly what is complete and what remains.

  • SAT tests the installed site context, not a repeat of FAT alone.
  • Safety and operational authorization precede testing.
  • Temporary bypasses and simulation are visible and controlled.
  • Acceptance lists residual scope and conditions explicitly.
SAT starts only when the site and baseline are ready.
Text-free automation SAT readiness gate linking site completion, safety, utilities, baseline and authorized roles

SAT starts only when the site and baseline are ready.

Decision guide

GateQuestionEvidence
Site readinessCan the work be performed safely and meaningfully?Completion, permits, utilities and test boundary
BaselineIs the installed system the approved deliverable?Manifest, checksums and FAT reconciliation
ExecutionDo field paths and site interfaces meet requirements?Witnessed results and attachments
AcceptanceWhat is complete, conditional or open?Signed status, punch list and handover action

A practical workflow

  1. 01

    Approve SAT scope, procedure, roles, constraints and hold points.

  2. 02

    Verify installation, safety, site services and the delivered baseline.

  3. 03

    Execute field, interface, sequence, fault and recovery tests.

  4. 04

    Control deviations, fixes, regression and retest through revisions.

  5. 05

    Reconcile cases and punch items, then issue conditional or final acceptance.

Conditional acceptance must make every remaining obligation visible.
Text-free SAT evidence flow from field test through deviation, revision, retest, punch and acceptance

Conditional acceptance must make every remaining obligation visible.

Evidence and acceptance

Retain SAT procedure, requirement links, readiness sign-offs, permits and boundaries, installation checks, calibrated equipment, hardware/software/configuration manifest, FAT carryover, test inputs and outputs, field observations, screenshots and logs, temporary forces and bypasses, deviations, fixes, retests, residual punch items, training and signed acceptance.

Common mistakes

  • Starting before utilities and field installation are stable.
  • Testing an unverified software baseline.
  • Leaving temporary forces or bypasses undocumented.
  • Recording pass without actual value or witness.
  • Signing acceptance without listing residual conditions.

Responsibility boundary

Primary sources

Technical claims and product boundaries were checked against these primary sources. Fact-checked

  1. IEC 62381 — Factory acceptance, site acceptance and site integration testsInternational Electrotechnical Commission
  2. IEC 62337:2012 — Commissioning of electrical, instrumentation and control systemsInternational Electrotechnical Commission

Frequently asked questions

Is SAT just FAT at site?

No. SAT concentrates on the installed configuration, field paths, site interfaces and real infrastructure.

Can SAT use simulation?

Yes when the scope, limitations, temporary connections and remaining real-world verification are approved.

What is conditional acceptance?

A formal acceptance of stated scope with explicit residual obligations, owners, dates and verification.

Does AutoNexit perform SAT?

No. It preserves the controlled record while authorized teams perform the work.

Related articles

ORG-F22

PLC and SCADA FAT Checklist: Tests, Evidence, Defects, and Acceptance

A factory acceptance test should prove an agreed automation baseline against traceable requirements before site work begins. The checklist must connect prerequisites, test cases, expected results, evidence, deviations, retests and approval without confusing witnessed execution with final project acceptance.