← SCADA & Industrial Controls
🧪

FAT / SAT Checklist

Factory & Site Acceptance Testing Tracker

When to use: Tracking Factory Acceptance Testing (FAT — logic and HMI verified at the integrator's shop, before shipment) and Site Acceptance Testing (SAT — physical wiring and full-system integration verified on-site) for a PLC/SCADA control system. Click each item to cycle Pending → Pass → Fail.

FAT — Factory (Shop)0/8
SAT — Site (Field)0/6
FAT
PLC logic — core start/stop sequence, forced I/O
Target: Matches control narrative / sequence spec exactly
Confirms core control logic before any field device exists — cheapest place to catch a logic error.
FAT
PLC logic — simulated I/O forcing for fault conditions (jam, stall, etc.)
Target: Correct stop/alarm response on every forced fault input
Proves fault-handling logic before real product or field devices are involved.
FAT
Interlock logic (no-part, guard, permissive conditions)
Target: Station halts on each forced fault, no false interlocks
Interlock logic is cheapest to correct as a program edit at the shop, not a field change.
FAT
Cycle timing and sequencing on forced I/O
Target: Full cycle completes within design cycle time
Validates timing logic independent of real servo/actuator behavior.
FAT
HMI navigation — all screens reachable within 2 clicks
Target: Every screen passes navigation test
Usability and navigation are far cheaper to fix on a bench than after operator training on-site.
FAT
HMI live data — tag updates against forced/simulated I/O
Target: Every screen tag reflects forced value within 1 sec
Confirms HMI-to-PLC tag mapping before real sensors are wired.
FAT
I/O point-list cross-check — tag name, terminal, PLC address agree
Target: 100% of point list
A mismatch here is a 5-minute fix at the shop; the same mismatch found on-site can mean a field re-wire.
FAT
Panel power-up and wiring integrity (megger/continuity)
Target: No faults, no cross-wired circuits, all panels
Verified before shipment, when panel access is unrestricted.
SAT
Physical I/O verification — each field device signal traced to correct PLC point
Target: 100% of point list
The physical counterpart to FAT's symbolic point-list check; confirms real wiring matches the list.
SAT
Sensor mounting and alignment check
Target: Reliable detection across full range of real product/process variation
A class of problem FAT structurally cannot catch, since no real product exists on the bench.
SAT
Network latency under full production load
Target: Within design tolerance under real VFD/motor electrical noise
Requires real cable runs and real plant-floor electrical environment; unmeasurable at FAT.
SAT
SCADA polling and OEE/alarm data integrity, all stations live
Target: No dropped tags, no stale data, under full network load
Tests the real network under real simultaneous multi-station polling.
SAT
Alarm flood test — verify one fault does not cascade downstream alarms
Target: Only the originating alarm displays, per suppression logic
The definitive test of alarm suppression design, only provable with a real fault on a running line.
SAT
Full line/system integration run — real product, all stations, production speed
Target: Sustained run at target rate with no unplanned stops
The system's actual commissioning milestone — the first time every step operates together as one system.
Note: This checklist is a generic FAT/SAT structure — always substitute this project's actual point list, sequence narrative, and alarm philosophy for the specific pass/fail criteria before use.

About the FAT / SAT Checklist

Factory Acceptance Testing (FAT) and Site Acceptance Testing (SAT) are the two commissioning gates every PLC/SCADA control system passes through before going live. FAT verifies logic, HMI, and panel wiring at the integrator's shop, where a defect is a program edit; SAT verifies the same system against real field devices, real cabling, and real process conditions on-site, where a defect can mean a field re-wire. This tracker separates the two phases so nothing gets tested at the wrong stage.

Why FAT and SAT Test Different Things

FAT uses simulated or forced I/O on the bench — there is no real product, no real sensors, no real plant-floor electrical noise. It is the cheapest place to catch a logic error, an interlock that doesn't fire, or a mismatched I/O point, because fixing any of those at the shop is a program edit or a panel correction, not a field trip. SAT happens after the panels are installed and wired to real field devices — it tests exactly the things FAT structurally cannot: sensor alignment against real product variation, network performance under real electrical noise, and whether the full system holds together running at production speed.

Reading a Failed Item

A failed FAT item is nearly always cheaper to fix than the same failure found at SAT — a forced-I/O logic test that fails at the shop means editing the PLC program before it ever ships. The same failure, if missed at FAT and only caught in the field, can mean diagnosing it through real wiring, real cable runs, and reduced access — often under schedule pressure with the line already staged for startup. That cost asymmetry is the core reason FAT exists as a distinct, mandatory gate rather than skipping straight to on-site testing.

Frequently asked questions

What is the difference between FAT and SAT?

FAT (Factory Acceptance Testing) verifies PLC logic, HMI functionality, and panel wiring integrity at the integrator's shop using simulated/forced I/O, before the system ships. SAT (Site Acceptance Testing) verifies the same system on-site with real field devices, real wiring, and real process conditions, culminating in a full-system integration run at production speed.

Can SAT be skipped if FAT passes completely?

No — FAT cannot test anything that requires real field devices, real cable runs, or real process/product variation. Sensor alignment, network performance under actual plant-floor electrical noise, and full-system integration at production speed are only provable on-site, regardless of how thoroughly FAT was executed.

Who typically witnesses FAT and SAT?

FAT is commonly witnessed by the end client or their engineering representative at the system integrator's shop before shipment. SAT is typically witnessed by the same client representative, plant operations staff, and often the integrator's commissioning team, on-site as the system goes live.

🎓

Try our SCADA Studio

More calculators, simulators, and guides for this discipline.

Related tools & guides

Safety Integrity Level (SIL) EstimatorPLC Power Supply SizingRS-485 Network Sizing