How does a remote factory acceptance test work?
Test scripts and a simulation of the plant are prepared in advance, the client witnesses the tests over video with screen sharing, and each result is signed off against the script. Checks that need physical hardware, wiring or panel inspection still need people on site.
Send us one work packageWhat a factory acceptance test proves
A factory acceptance test (FAT) shows that the automation system does what the specification says before it ships to site. IEC 62381 is the international standard that describes FAT, site acceptance tests and integration tests for automation systems in the process industry, and it is a useful checklist even when the contract does not require it.
A remote FAT changes where the witnesses sit, not what is proven.
Preparation is most of the work
A remote FAT only works if the preparation is thorough. That means: test scripts written from the functional specification, IO list and alarm list, with a step, an expected result and a sign off field for every test; a simulation that drives the inputs and responds to the outputs, so motors report running, valves travel and levels move; and a dry run by your own team before the client joins.
Send the scripts to the client in advance and agree the order of tests and the sign off method.
How the session runs
The test lead shares the HMI and, where useful, the controller or simulation screens. A second camera can show any hardware on the bench. The client’s witness follows the script, asks for faults to be triggered, and watches the response. Each result is recorded against the script as it happens, with punch items logged on a shared list. At the end, both sides sign the record, electronically or on paper, as the contract requires.
What still needs people on site
Remote witnessing does not cover everything. Panel build quality, wiring and labelling, physical IO checks with real field devices, network hardware, and anything involving safety systems that the client or the standard requires to be witnessed in person usually stay on site. Many projects split the test: software and sequences remotely, hardware and safety in person.
Where a partner fits
Script writing, simulation and the traceability sheet that links requirements to tests are well suited to a remote partner, because they are document and software heavy. The integrator keeps the client, runs the witnessed session and signs off.
Practical setup for the session
Test the video platform, screen sharing and audio with the client’s own network the week before, because corporate firewalls block some tools. Use a second screen or camera for the simulation console so the witness sees both the HMI and what is being simulated. Keep a shared, live punch list that both sides can see. Book shorter sessions across several days rather than one long day; attention drops after a few hours on a video call, and missed details become punch items at site.
Record who witnessed each test and when, in the same record that holds the results.
Related questions
Ajinkya Technologies works behind US control system integrators on HMI, SCADA, MES, testing and documentation, under the integrator’s brand and NDA. Questions: bdo@ajinkyatechnologies.in.
References and scope
External references explain the underlying technology or regulatory context. Ajinkya pricing, schedules and project results are company provided estimates or examples, not independently audited industry benchmarks. Confirm scope and current requirements before making a purchasing decision.
Have a work package in mind?
Send us one defined package and your NDA. We sign it, reply with a fixed scope and quote, and deliver under your name.
Reviewed by Amey Kadle, Founder, Ajinkya Technologies. Last reviewed: .