PLC/SCADA FAT Checklist: What Industrial Buyers Should Verify Before Shipment

  • Home
  • Blog
  • VFD
  • PLC/SCADA FAT Checklist: What Industrial Buyers Should Verify Before Shipment
PLC SCADA FAT checklist

A PLC SCADA FAT checklist helps industrial buyers verify that a programmable logic controller (PLC), supervisory control and data acquisition (SCADA) system, or integrated control system meets the approved project requirements before shipment. The factory acceptance test (FAT) should cover the applicable hardware, input/output (I/O) behavior, control logic, interlocks, alarms, HMI functions, communication interfaces, and test records. However, FAT only demonstrates the functions and interfaces included in its approved scope. Field wiring, installed instruments, actual site networks, and site-specific operating sequences may still require verification during the site acceptance test (SAT).

What Is a PLC/SCADA Factory Acceptance Test?

A Factory Acceptance Test is a structured verification activity performed before equipment is released for shipment. In industrial automation projects, it checks whether the supplied control hardware, software configuration, interfaces, and specified functions correspond to the approved engineering documents and contractual acceptance criteria.

A PLC factory acceptance test may focus on controller hardware, I/O modules, programmed logic, and panel-related checks. A broader control system FAT may also include SCADA screens, alarm handling, communication interfaces, data exchange, and defined abnormal-condition responses.

The exact scope depends on the project specification, equipment supply boundary, approved test procedure, and agreement between the relevant project parties.

Typical responsibilities include:

  • Supplier or system integrator: prepares the test environment, demonstrates the agreed functions, records results, and documents deviations.
  • Buyer or owner’s engineer: reviews the acceptance criteria, witnesses agreed tests, and evaluates the evidence against the project requirements.
  • Engineering team: confirms that the functional description, I/O list, control logic, and interface definitions are aligned.
  • QA/QC team: reviews inspection records, document revisions, nonconformities, and the completeness of the acceptance package, as applicable.

FAT should be planned around approved requirements rather than an informal demonstration of the equipment. The objective is to produce traceable evidence showing which functions were tested, what results were obtained, and which issues remain unresolved.

PLC SCADA FAT checklist
What FAT Can and Cannot Prove

Factory testing can demonstrate functions that can be safely reproduced using the available hardware, software, test instruments, and simulation arrangements. For example, engineers may simulate an input, verify the corresponding PLC response, and confirm that the expected alarm or status appears on the HMI.

However, a simulated input does not automatically prove that the installed field instrument, cable, terminal connection, or final control element will behave correctly at the plant. Site-dependent functions may require loop checks, field inspections, network verification, operational testing, and other approved SAT activities.

Therefore, the FAT plan should explicitly identify its scope, exclusions, simulation assumptions, and the activities reserved for site verification.

Documents to Approve Before Starting FAT

A reliable FAT begins with an agreed document baseline. If engineers use outdated drawings, incomplete signal lists, or unapproved functional descriptions, a test may pass against the wrong requirements.

Before testing begins, confirm the applicability and revision status of the following documents:

  • Approved control philosophy or functional description.
  • PLC and SCADA functional requirements.
  • Digital and analog I/O list, including signal descriptions and tag references.
  • Cause-and-effect matrix, where applicable.
  • Interlock and permissive descriptions.
  • HMI screen layouts, alarm requirements, and operator functions.
  • Communication interface lists and data-mapping documents.
  • Approved panel drawings, wiring diagrams, and terminal schedules.
  • FAT procedure, individual test cases, and acceptance criteria.
  • Document register showing revisions, approval status, and applicable software versions.

The required document set depends on the contract, system architecture, engineering design, and equipment scope. A project involving a standalone machine may require a different level of interface documentation from a project integrating several PLCs with a plant-wide SCADA or DCS.

Document What to Verify Why It Matters
Functional description Operating sequences, commands, permissives, and expected responses Defines the behavior that test cases must demonstrate
I/O list Tags, signal types, descriptions, and channel assignments Establishes traceability for signal verification
Cause-and-effect matrix Applicable initiating conditions and expected actions Supports verification of defined interlocks and responses
HMI and alarm specification Screen content, tag mapping, alarm descriptions, and priorities Confirms that operator-facing functions match approved requirements
Communication documents Interfaces, mapped data, dependencies, and expected status indications Clarifies what must be tested between connected systems
FAT procedure Test steps, expected results, acceptance criteria, and witness points Creates a consistent and auditable test process

The PLC/SCADA FAT Checklist: Essential Tests Before Shipment

The following automation FAT checklist provides a practical framework for reviewing the supplied system. Every item should be marked as applicable, not applicable, passed, failed, or otherwise classified according to the approved project procedure. Project-specific acceptance criteria take precedence over generic examples.

1. Hardware and Panel Inspection

Begin by comparing the supplied hardware with the approved equipment list, drawings, and technical specifications. The inspection should cover the equipment included within the supplier’s scope.

  • Confirm equipment identification and installed module types against the approved configuration.
  • Check the arrangement of panels and components against the applicable drawings.
  • Review terminal labels, wiring identification, and relevant wiring inspection records.
  • Verify the supplied PLC CPU, I/O modules, communication modules, and interface components against the approved design.
  • Review applicable power supply, grounding, and bonding arrangements within the inspection scope.
  • Record missing components, physical damage, incorrect identification, and outstanding hardware issues.

Inspection results should reference the relevant drawing or equipment identifier. A visual inspection alone should not be presented as proof of electrical performance or compliance with a requirement that needs a separate test.

2. I/O Simulation and Signal Verification

I/O verification checks whether the control system processes defined input and output signals as expected. Use the approved I/O list to establish test coverage and identify any excluded points.

  • Digital inputs: verify the expected status changes when the corresponding test condition is applied.
  • Digital outputs: confirm the expected output state under the approved test conditions.
  • Analog inputs: verify applicable scaling, engineering units, and expected displayed values using an appropriate test method.
  • Analog outputs: verify the commanded output behavior where included in the FAT scope.
  • Tag identification: check that signal names and descriptions correspond to the approved documentation.
  • HMI indication: confirm that the simulated or tested signal is represented correctly on the relevant screen.
  • Alarm response: verify alarm generation where the signal and functional specification require it.
  • Test records: record the test input, expected result, actual result, and final status.

For example, a simulated high-level switch may be used to verify the corresponding PLC input status and the associated HMI indication. If the approved functional description requires an alarm or interlock, that response should also be included in the applicable test case.

Do not assume that the test proves the field instrument’s calibration or the integrity of its installed cable. Those items require the relevant inspection, calibration, or site test evidence.

3. PLC Logic, Interlocks, and Permissives

Control logic testing should demonstrate that the programmed functions behave according to the approved functional description. Testing should cover normal sequences as well as relevant abnormal conditions defined in the project scope.

  • Verify normal operating sequences and transitions between defined states.
  • Confirm that specified permissive conditions are evaluated correctly.
  • Verify applicable interlock responses against the approved cause-and-effect documentation.
  • Check the expected output states for each test condition.
  • Review reset and recovery behavior where specified.
  • Test defined fault and abnormal-state responses in the approved test environment.
  • Confirm that applicable cause-and-effect relationships match the approved documents.

For every test, document the initial conditions, applied input or simulated event, expected response, and observed result. A passing test should be traceable to the requirement it verifies.

Tests involving safety-related functions must follow the relevant approved procedures and validation requirements. Routine FAT activities must not be treated as a substitute for formal safety validation, nor should personnel bypass safety functions to force a test result.

4. HMI Screens, Alarms, and Operator Functions

SCADA and HMI testing checks whether the operator interface presents information correctly and supports the functions included in the approved design.

  • Verify tag mapping between the control system and the displayed objects.
  • Check equipment status indications and relevant operating states.
  • Confirm that specified commands and feedback indications are represented correctly.
  • Verify alarm generation and acknowledgment behavior where required.
  • Check alarm descriptions and priorities against the approved alarm specification.
  • Review trends, historical data, and event displays where included in the project scope.
  • Verify screen navigation, equipment identification, and consistency across related displays.
  • Check operator permissions and access restrictions where specified.

When reviewing SCADA and HMI systems, the important acceptance question is whether each required operator function has been tested and documented, not simply whether the screens look complete.

A graphic that displays a simulated motor-running status does not, by itself, prove that the installed motor starts correctly or that field feedback is wired properly. Actual equipment behavior must be verified through the appropriate site tests.

5. Communication and System Interfaces

Where the project includes communication between PLCs, SCADA/HMI, DCS, or third-party systems, FAT should verify the interfaces included in the agreed test scope.

  • Confirm the interface list and relevant data-mapping documents.
  • Check that required signals are mapped to the correct tags or data points.
  • Verify communication status and diagnostic indications where specified.
  • Confirm expected data exchange between connected systems using the available test setup.
  • Test loss-of-communication indications and recovery behavior where required and safely reproducible.
  • Document interfaces that cannot be fully tested before installation.
  • Record external dependencies, exclusions, and responsibilities for remaining integration work.

Do not assume that a particular protocol, redundant network, or third-party connection is included simply because it is common in industrial automation. The approved interface specification determines what must be tested.

Where a DCS interface is part of the project, review the applicable integration boundary and data exchange requirements for the relevant distributed control systems (DCS).

6. Fault Recovery and Abnormal Conditions

Where required by the approved FAT procedure, test defined abnormal conditions to establish how the system detects, indicates, and recovers from them.

  • Simulated loss of an input signal, where applicable.
  • Communication interruption in a controlled test environment.
  • Invalid or out-of-range input handling where specified.
  • Controller restart or recovery behavior where approved for testing.
  • Alarm response to defined abnormal conditions.
  • Recovery to the intended operating state after the test condition is removed.

The test procedure should define safe preconditions, expected responses, and recovery steps. Not every failure scenario is applicable to every project, and factory simulation does not necessarily reproduce the complete behavior of installed equipment or a live plant network.

7. Test Evidence and Record Keeping

A completed test sheet should provide enough information for another qualified reviewer to understand what was tested, how the test was performed, and why the result was accepted.

Depending on the project requirements, record the following information for each test case:

  • Unique test case identification.
  • Reference to the approved requirement, drawing, I/O point, or functional document.
  • Test preconditions and initial system state.
  • Test input or simulated condition.
  • Expected result and applicable acceptance criterion.
  • Actual observed result.
  • Pass, fail, or not-applicable status.
  • Defect, deviation, or punch-list reference where relevant.
  • Retest result and closure evidence where necessary.
  • Tester and witness identification where required.
  • Test date and applicable software or document revision.

Illustrative FAT test-record template: Adapt the following example to the approved project procedure rather than using it as a substitute for project-specific acceptance criteria.

Field Illustrative Entry
Test ID FAT-DI-001
Requirement reference Approved I/O list and functional description
Test condition Apply the approved simulated input condition
Expected result Correct input status and associated indication
Actual result Record the observed behavior
Status Pass / Fail / Not Applicable, as defined by the procedure
Evidence Test sheet, relevant observation, or permitted screenshot
Defect or retest reference Enter the applicable register reference, if any

Evidence should be consistent with the project’s documentation and information-security requirements. Screenshots may support a result, but they should not replace the required test record or sign-off.

FAT Witness Points, Defects, and Punch-List Management

FAT planning should identify which activities require buyer attendance, formal witnessing, or a designated hold point. These arrangements should be agreed before testing so that the required parties have sufficient notice and the correct documents are available.

During the test, the project team should:

  • Record attendance and witness sign-offs where required.
  • Identify failed tests and deviations from approved requirements.
  • Assign each issue a unique reference and responsible party.
  • Define the corrective action and required retest.
  • Retain the original result and the evidence supporting the retest.
  • Update the punch-list register and document any approved deviation.
  • Record unresolved issues and their impact on shipment, installation, or SAT.

An open punch-list item does not automatically mean that shipment must be stopped in every project. Its disposition depends on the contractual acceptance criteria, the technical significance of the issue, the approved risk assessment where relevant, and the decision of the authorized project parties.

Shipment authorization should follow the contractually defined acceptance process. It should not be inferred solely from a verbal statement that the FAT is complete.

FAT vs. SAT: What Still Needs to Be Verified at Site?

FAT and SAT are complementary activities. FAT evaluates the agreed functions under factory test conditions, while SAT verifies the relevant system functions after installation and connection to the actual site environment.

Verification Area FAT SAT
Hardware configuration Inspect supplied equipment against approved documents Verify installed configuration and site integration
I/O behavior Use defined simulations or available test arrangements Verify field signals and connections as required
Field wiring Review supplied panel wiring within the test scope Verify installed field wiring and termination
Instruments and actuators Use simulation or connected devices where available Verify actual installed devices and operating responses
Network interfaces Test available interfaces in the factory environment Verify actual site networks and required end-to-end communication
Third-party integration Test available interfaces and agreed simulations Verify integrated operation with installed third-party equipment
Operating sequences Verify functions reproducible under factory conditions Verify applicable site-specific sequences and operating conditions
Defects and handover Record defects, retests, exclusions, and open items Close or manage remaining site issues and complete required handover

The division of work varies by project. Some integration tests may be performed during FAT when the required interfaces are available; others may be reserved for SAT. The approved test strategy should identify these responsibilities clearly.

Common Mistakes in PLC/SCADA FAT

Several recurring weaknesses can reduce the value of factory testing and leave important acceptance questions unresolved.

  • Starting before documents are approved: the team may test against obsolete requirements or incomplete drawings.
  • Testing without traceability: a successful demonstration may not prove that a specific contractual requirement was met.
  • Checking hardware only: correct component installation does not prove the required control logic and operator functions.
  • Confusing HMI display with field functionality: a simulated indication does not establish that the installed instrument or actuator operates correctly.
  • Omitting alarms or interlocks: required abnormal responses may remain unverified if the FAT procedure focuses only on normal sequences.
  • Ignoring communication recovery: interface behavior after a defined interruption may remain unknown when it is part of the approved scope.
  • Recording only “pass”: a result without the expected response, actual result, and supporting evidence is difficult to audit.
  • Skipping retests: correcting a defect does not establish closure until the required verification is completed and recorded.
  • Losing revision control: unclear software and document versions can create uncertainty about what was actually tested.
  • Treating FAT as proof of site readiness: installation, field wiring, and site-dependent functions still need the required verification.

These issues can be reduced by agreeing on test coverage early, linking each test to an approved requirement, maintaining a controlled document baseline, and retaining evidence throughout the acceptance process.

What Should Buyers Request in the Final FAT Package?

Before completing the acceptance review, compare the submitted FAT package with the contract and approved project documentation. The applicable package may include:

  • Approved FAT procedure and test cases.
  • Completed test sheets and results.
  • Supporting test evidence and inspection records.
  • Defect, deviation, and punch-list registers.
  • Retest records and closure evidence.
  • Approved deviations and their documented dispositions.
  • Final hardware configuration and applicable software version information.
  • Relevant panel drawings, wiring documents, and revision records.
  • A list of test exclusions and unresolved items.
  • A clear list of remaining SAT activities and responsible parties.
  • Required witness sign-offs and formal acceptance records.

The final FAT report should distinguish completed tests from tests that were not performed, excluded, or deferred. If an activity was not tested because the necessary site equipment was unavailable, that limitation should be visible in the report and assigned to the appropriate later verification stage.

How to Prepare for a Successful PLC/SCADA FAT

A structured preparation process helps the project team establish the test scope and reduce ambiguity during acceptance.

  1. Confirm the document baseline. Verify the approved requirements, drawings, I/O list, and software or configuration revisions.
  2. Agree on acceptance criteria. Define what constitutes a pass, fail, deviation, or not-applicable result.
  3. Review test coverage. Confirm that the FAT procedure addresses the applicable requirements and interfaces.
  4. Confirm the test environment. Identify the equipment, simulations, resources, and safe test arrangements needed.
  5. Map tests to requirements. Establish traceability between test cases, I/O points, functional requirements, and relevant drawings.
  6. Record actual outcomes. Complete test records during execution rather than reconstructing them later.
  7. Manage defects and retests. Assign issues, retain evidence, and verify corrections according to the approved procedure.
  8. Review the final package. Check the test results, open items, revisions, deviations, and required sign-offs.
  9. Plan the remaining SAT work. Identify site-dependent checks, owners, prerequisites, and required completion evidence.

This sequence is a general planning framework. The approved project procedure, applicable safety requirements, and contractual acceptance process remain controlling.

How PLC, SCADA/HMI, and DCS Engineering Support Relates to FAT

FAT quality depends on more than the test session itself. The engineering documents, configuration baseline, interface definitions, and commissioning plan must be sufficiently developed for the required tests to be meaningful.

For projects involving PLC systems and solutions, the acceptance plan should connect the supplied controller and I/O configuration to the approved functional requirements. Where the scope includes SCADA and HMI systems, it should also cover applicable displays, alarms, operator functions, and data interfaces. If the architecture includes distributed control systems (DCS), the relevant integration boundary and interface tests should be documented as well.

Before agreeing on a test scope, buyers should clarify which engineering, testing, documentation, and commissioning activities are included in the proposed service. No specific test facility, authorization, certification, or acceptance guarantee should be assumed without supporting documentation.

PLC SCADA FAT checklist
Request a PLC/SCADA FAT Scope Discussion

Industrial buyers, EPC teams, and project engineers can use the PLC SCADA FAT checklist to identify gaps in test coverage before shipment. A technical discussion can help clarify the applicable acceptance criteria, I/O and logic verification, HMI and alarm testing, communication interfaces, FAT reporting, and outstanding SAT requirements.

When requesting a review, prepare the available functional description, I/O list, cause-and-effect matrix, interface documents, draft FAT procedure, and current punch list. These records help define the actual project scope without assuming that every function can be verified in a factory environment.

To discuss the project requirements, contact the technical team and identify the PLC/SCADA configuration, required acceptance evidence, and commissioning activities that need clarification.

Discuss Your PLC/SCADA FAT Requirements

Frequently Asked Questions About PLC/SCADA FAT

1. What Is a PLC/SCADA Factory Acceptance Test?

A PLC/SCADA Factory Acceptance Test is a structured test performed before shipment to verify the functions covered by the approved project scope. It may include hardware inspection, I/O simulation, control logic, interlocks, alarms, HMI functions, and communication interfaces. The results should be documented against defined acceptance criteria. FAT does not automatically verify installed field wiring, actual instruments, or every site-dependent function; those may require SAT and other commissioning activities.

2. What Should a PLC/SCADA FAT Checklist Include?

A practical PLC SCADA FAT checklist should include the approved document baseline, hardware and panel inspection, I/O verification, control logic, interlocks and permissives, HMI and alarm functions, communication interfaces, applicable fault-recovery tests, and test records. It should also cover witness points, defect management, retesting, punch-list closure, and the final FAT report. The specific test coverage must match the project’s approved requirements and acceptance criteria.

3. What Is the Difference Between FAT and SAT?

FAT is performed before shipment under factory test conditions, using the supplied equipment and any agreed simulations or available interfaces. SAT takes place after installation and verifies the applicable functions in the actual site environment. SAT may cover field wiring, installed instruments, site networks, integrated equipment, and site-specific sequences. Some integration tests can be included in either stage, depending on the approved project test strategy.

4. Which Documents Should Be Approved Before FAT?

The applicable documents usually include the functional description, PLC/SCADA requirements, I/O list, relevant cause-and-effect matrix, interlock descriptions, HMI and alarm specifications, communication interface documents, approved drawings, and FAT procedure. Document revisions and acceptance criteria should also be clear. The exact document set depends on the system scope, project contract, and engineering design. Any unresolved document issue that affects test validity should be addressed before the relevant test proceeds.

5. How Are PLC I/O Points Tested During FAT?

PLC I/O points are tested against the approved I/O list using an appropriate test arrangement. Depending on the signal and project scope, engineers may apply simulated digital states or suitable analog test values, then verify the expected controller response and relevant HMI indication. The test record should include the input condition, expected result, actual result, and status. Simulated I/O testing does not by itself prove field wiring integrity or instrument calibration at the installed site.

6. Should Alarms, Interlocks, and HMI Screens Be Tested During FAT?

Yes, when these functions are included in the approved FAT scope. The test plan should verify applicable alarm generation, descriptions, priorities, acknowledgment behavior, interlock responses, permissives, and operator interface functions against the approved documents. The test method must be suitable for the function being verified. Factory simulation can demonstrate defined logic and display behavior, but it does not replace field verification or formal safety validation where required.

7. What Records Should Be Included in a FAT Report?

A FAT report should contain the completed test sheets, test identifiers, requirement references, expected and actual results, test status, relevant evidence, defects, deviations, retest outcomes, and applicable witness sign-offs. It should identify the tested hardware and software revisions and list exclusions or outstanding activities. The required format and level of detail should follow the contract and approved project procedure so that acceptance decisions remain traceable and auditable.

8. Can Equipment Be Shipped If Some FAT Items Remain Open?

Possibly, but the decision depends on the contract, approved acceptance criteria, technical significance of the open items, and authorization process. Some items may be accepted as documented punch-list actions, while others may affect safe operation, functional compliance, or shipment authorization. Each open issue should have a clear description, responsible party, disposition, and closure requirement. The project team should not treat FAT completion as automatic approval to ship.

Conclusion

A well-prepared PLC SCADA FAT checklist links every applicable test to approved requirements and produces evidence that can be reviewed before shipment. Buyers should verify hardware, I/O behavior, logic, interlocks, alarms, HMI functions, communication interfaces, and fault-recovery behavior within the agreed test scope. They should also review defects, retest records, software revisions, exclusions, and required sign-offs.

Just as importantly, the FAT report must identify what remains to be checked during SAT. A clear boundary between factory-tested functions and site-dependent verification gives engineering and procurement teams a more reliable basis for acceptance, shipment planning, and commissioning readiness.