Productivity & Best Practices 3 min readORG-F22

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

Share

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.

The short answer

Freeze the hardware, software and document baseline; approve the FAT procedure and requirements traceability; confirm simulation, test equipment, roles, safety and data readiness; and record one result per test step. Every case needs preconditions, input, expected behavior, acceptance criterion and evidence. Classify deviations by impact, assign owners and decide whether a failed item blocks continuation. Retest against a new controlled revision, preserve both results, and issue a signed report listing passed, failed, deferred and excluded scope.

  • Test an identified baseline against approved requirements.
  • Make expected results measurable before execution.
  • Preserve failures and retests instead of replacing history.
  • Separate FAT completion, punch acceptance and authorization for site use.
Readiness prevents expensive witnessed testing of an unstable baseline.
Text-free PLC and SCADA FAT readiness and execution checklist from frozen baseline to witnessed results

Readiness prevents expensive witnessed testing of an unstable baseline.

Decision guide

GateMinimum evidenceDecision
ReadinessApproved documents, software, simulation and calibrated equipmentStart, conditionally start or postpone
ExecutionStep result, actual value, timestamp, witness and attachmentPass, fail, blocked or not applicable
DeviationImpact, owner, disposition and affected requirementsFix now, defer with approval or reject
CloseoutRetest, residual punch list and signed reportAccept FAT scope or require further work

A practical workflow

  1. 01

    Approve scope, responsibilities, baseline, procedure and traceability matrix.

  2. 02

    Complete readiness review and controlled test-environment setup.

  3. 03

    Execute in sequence, capture contemporaneous evidence and log deviations.

  4. 04

    Analyze fixes, issue revisions and perform targeted regression and retest.

  5. 05

    Reconcile every case and deviation, approve the report and protect the released package.

A retest adds evidence; it never erases the original failure.
Text-free FAT defect lifecycle showing failure, impact, correction, revision, regression, retest and acceptance

A retest adds evidence; it never erases the original failure.

Evidence and acceptance

Retain requirements and traceability, FAT procedure revision, participant and witness authority, hardware/software/document manifest, checksums and backups, simulation and instrument status, test environment, case results, screenshots and files, event/alarm logs, deviations, impact decisions, corrected revisions, retests, residual punch list, exclusions, meeting record and signed acceptance.

Common mistakes

  • Testing against an unrecorded software build.
  • Writing expected results during execution.
  • Deleting failed evidence after a successful retest.
  • Leaving interfaces and failure modes until SAT.
  • Treating a signed attendance sheet as technical acceptance.

Responsibility boundary

Primary sources

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

  1. IEC 62381 — Automation systems in the process industry — Factory acceptance test, site acceptance test, and site integration testInternational Electrotechnical Commission
  2. ISA-TR84.00.04 Part 1 — Guidelines for the Implementation of ANSI/ISA-84.00.01International Society of Automation

Frequently asked questions

When is a FAT ready to start?

When the agreed baseline, procedure, requirements, environment, simulation, people and evidence tools pass the documented readiness gate.

Can open defects remain after FAT?

Only through an explicit disposition that states impact, owner, due date, verification and acceptance authority.

Should every retest repeat the full FAT?

Use impact analysis to define the corrected case and necessary regression scope.

Does AutoNexit perform FAT?

No. It preserves the controlled test and acceptance record while qualified teams execute the work.

Related articles

ORG-F04

PLC Code Review Checklist Before Factory Acceptance Testing

A pre-FAT code review finds ambiguous ownership, unsafe state transitions, hidden bypasses, weak diagnostics, and untestable interfaces before the factory floor becomes the test environment. The review should connect each finding to a requirement, revision, risk, owner, and FAT case.