A control system can pass every test in the integrator's shop and still not work when it is bolted to the plant, because the shop test used simulated inputs and the plant uses real transmitters, real wiring, and a real process. The site acceptance test is where the system meets that reality. It is the on-site verification, after installation, that proves everything works end to end with the actual field devices, and its completion is what lets the project hand the system over to operations. This guide explains what a SAT covers, how it differs from the shop test, what loop-checked I/O means, and the sign-off that triggers handover.
Site Acceptance Test (SAT) in one line: A site acceptance test, or SAT, is the formal on-site verification of a control system after it has been installed, confirming that it works correctly with the real field wiring, instruments, and process rather than the simulated inputs used at the shop. It typically includes loop checks that trace each I/O point from the field device through the wiring to the system, verification of control and alarm behavior in place, and demonstration that the whole installed system performs as specified. A passed SAT is the sign-off that the system is ready to be handed over to operations.
The SAT happens after the system is physically installed at the site - panels mounted, field devices connected, wiring pulled and terminated, network in place. Its whole reason for being is that the earlier shop test could not prove the things that only exist once the system is installed. At the integrator's shop the inputs were simulated, so the shop test showed the system responds correctly to given signals but could say nothing about whether the field wiring delivers the right signal from the right instrument to the right point. The SAT closes that gap by exercising the system with the real field, so the proof is end to end rather than bench-bounded.
This makes the SAT the first time the system is verified against actual process conditions and real hardware in the field. Errors that a shop test structurally cannot catch - a transmitter wired to the wrong terminal, a signal with the wrong polarity, a valve that strokes the wrong way, a grounding or noise problem particular to the site - surface here, because here the real wire is carrying the real signal. Finding them at the SAT, before operations relies on the system, is exactly the intent.
The SAT is also a commissioning activity, closely tied to bringing the plant into service. It usually runs during or just before startup, when instruments are calibrated and connected and the process is ready or nearly ready to operate. In that sense the SAT is not an isolated test but the verification layer of commissioning - the structured confirmation that the installed system is correct and ready to be trusted with the running plant.
The heart of a SAT is loop checking. A loop check verifies a complete signal path from end to end: for an input, a technician applies a known value at the field instrument - simulating a level, stroking a valve, closing a switch, injecting a known signal - and confirms that the correct value appears at the right tag in the control system and on the operator display. For an output, the system commands the field element and someone at the device confirms it actually moved. Every point is traced this way, which proves that the physical wiring, the point assignment, the scaling, and the display are all correct together, for the real instrument that is actually connected.
That is precisely the scope the shop FAT could not cover, and the two tests divide the work cleanly. The FAT proved the system is internally correct - the logic, alarms, displays, and I/O response to simulated inputs are right - in the favorable environment of the shop. The SAT proves the installation is correct - the right instrument is wired to the right point with the right scaling and behavior - in the environment that actually matters. There is deliberate overlap in that both confirm alarms and control behave correctly, but the SAT does it with real signals flowing through the real installation, which is the only way to catch installation and wiring errors.
Beyond loop checks, a SAT confirms the installed system as a whole: network communications between controllers, servers, and operator stations in their real locations; alarms triggered by real conditions and annunciated correctly; control sequences run against the real process where it is safe to do so; and the operator interface exercised in the actual control room. Site-specific realities that never appeared on the bench - electrical noise, grounding, communication distances, environmental conditions - get their first real test here, which is another reason the SAT is indispensable no matter how thorough the FAT was.
A SAT ends in a formal sign-off against agreed criteria, and that sign-off is the pivot from project delivery to operations. The SAT is run against a written procedure, much like a FAT, with each item verified and recorded and remaining issues logged as punch items to be closed. When the agreed acceptance criteria are met and the punch list is cleared or dispositioned, the customer signs off, which formally accepts the installed system. That acceptance is what triggers handover: responsibility for the system passes from the project team and integrator to the operations organization that will run it day to day.
The SAT is also the moment the people who will live with the system converge on it together. Field technicians who pulled the wiring and calibrated the instruments, the integrator's engineers who built and configured the system, and the operators who will run it are all present as the loops are checked and the system is exercised. That convergence has value beyond the test itself: operators see how the system behaves and where things are, technicians confirm their field work against the live system, and the integrator transfers practical knowledge. A well-run SAT doubles as the operations team's first hands-on familiarity with the system they are about to own.
When the SCADA layer is a cloud platform such as Merobix, the SAT verifies that the real field data is flowing all the way through to the platform where operators will actually watch it. Loop checks confirm not just that a point reaches a controller but that the value arrives at the correct cloud tag, appears on the right dashboard, and trends and alarms as configured - the genuine operator view, checked at site with real signals. Because the platform is reached through a browser rather than a control-room server, the SAT can also confirm that operators can see the live plant from wherever they need to, which for distributed field operations is often the whole point. Passing the SAT then means the field, the wiring, the instruments, and the cloud view have all been proven together, and operations can take over a system they have seen working end to end.
A factory acceptance test (FAT) verifies the system at the integrator's shop before shipment, using simulated inputs, to prove it is internally correct. A site acceptance test (SAT) verifies the same system after installation at the actual site, connected to real field wiring and instruments, to prove it works end to end. The SAT catches installation and wiring errors the FAT structurally cannot, because only the SAT uses the real signals flowing through the real installation.
A loop check verifies a complete signal path from the field device to the control system and display. For an input, a technician applies a known value at the instrument and confirms the correct value appears at the right tag and on the operator screen; for an output, the system commands the device and someone confirms it actually moved. It proves the wiring, point assignment, scaling, and display are all correct together for the real connected instrument.
Sign-off of the SAT formally accepts the installed system and triggers handover: responsibility passes from the project team and integrator to the operations organization that will run the system. Any remaining punch items are tracked to closure, and the operators - who typically attend the SAT - take over a system they have seen working end to end with real field signals. It is the transition from project delivery to day-to-day operation.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.