MCT Nexus ENGINEERING RESOURCE
Planning a Factory Acceptance Test
Plan a factory acceptance test around machine requirements, representative conditions, documented results and a clear path for open items.
Treat FAT as a requirements review with evidence.
A factory acceptance test is an agreed opportunity to check equipment before it moves to the installation site. Its value comes from the connection between the requirements and the tests actually performed. A machine running for a demonstration is useful, but it is not automatically evidence that every requirement has been satisfied.
The scope of FAT varies with the equipment. A control panel, a standalone machine and a production subsystem have different available interfaces and test conditions. MCT Nexus’s commissioning and FAT services establish the checks, responsibilities and records appropriate to the agreed project scope.
Establish what can be tested at the build location.
List the available utilities, process materials, sample parts, connected devices and operating conditions. Identify equipment or interfaces that will not be present. If a signal or process condition will be simulated, record that limitation and define the remaining site test.
For example, a machine may be able to demonstrate its internal sequence while its upstream conveyor is represented by a test interface. That checks part of the control behavior. It does not prove the mechanical transfer or the full handshake with the installed conveyor. The acceptance record should preserve that distinction.
Representative parts matter. A test with one product type may not demonstrate changeover or the range of presentation expected in production. Agree on the sample set and the conditions under which any performance measurement will be made before the test date.
Organize the checks from components to the system.
Documentation and build review
Review the issued drawings, equipment identification and the agreed build package. Record discrepancies that need resolution before functional testing or shipment. The purpose is to establish which revision and configuration are being tested.
Electrical and I/O verification
Complete the required electrical checks using the appropriate plan and qualified personnel. I/O checkout confirms the relationship between devices, wiring and controller information. These checks prepare the equipment for functional testing; they do not replace the machine’s required protective-system verification.
Functional sequence testing
Check modes, permissives, normal cycles, recipes, equipment interfaces and operator information. Define expected results before observing the machine. Include the relevant response to a missing device condition, timeout or interrupted operation.
Production and process checks
Where the necessary parts and process conditions are available, verify the agreed production behavior. State the conditions and measurement method behind any result. Process capability or quality claims need evidence appropriate to the application, not a general declaration that the machine “passed FAT.”
Include the conditions that cause support calls.
Normal operation is only one part of a useful acceptance plan. Review what happens when the machine stops mid-cycle, loses a required interface, sees an invalid recipe or receives an unexpected part condition. The relevant tests depend on the equipment and should be established through the engineering review.
Recovery deserves attention because physical equipment may be left between states. A part may remain in a fixture, a valve may have changed position or material may span a transfer. Define the conditions required to resume or reset. The operator should not need an undocumented workaround to restore the agreed operating state.
Protective functions, access and stopping behavior have their own requirements and validation responsibilities. A production sequence test must not be used as a substitute for the required safety verification. Identify who performs and approves those activities within the overall project plan.
Use a test record that supports decisions.
A practical test record identifies the requirement, test setup, expected result, observed result and disposition. Add the equipment revision, software version and any relevant configuration. Evidence may include recorded observations, measurements or controlled supporting files, depending on the requirement.
Not every incomplete item is a failed test. Distinguish a requirement that was tested and failed from one that could not be tested because the necessary condition was unavailable. Both need a clear next action, but they have different implications for acceptance.
Open items should have an owner, planned resolution and approval path. The customer and supplier should agree which items must be closed before shipment and which can proceed under a documented arrangement. Avoid using an informal list that has no relationship to the acceptance decision.
Connect FAT to installation and site acceptance.
The site plan addresses the actual utilities, field wiring, line interfaces and operating environment. Identify the checks that must be repeated after shipment and the requirements that can only be verified at the installation location. Transportation, disassembly and reconnection can affect previously tested interfaces.
Plan for the people and materials needed at site. Operators, maintenance, process engineering, quality and other equipment suppliers may all be required for particular checks. A startup schedule that includes only the controls engineer can overlook important dependencies.
The final handover should align the accepted machine revision with the drawings, PLC/HMI files, device configurations and operating information. Review the PLC handover checklist when software is part of the delivery.
Prepare the acceptance discussion early.
Begin the FAT plan while the requirements are being defined, then refine it as the design develops. This gives both teams time to identify missing test material, unavailable interfaces and ambiguous acceptance criteria. It also prevents the final test from becoming the first detailed review of how the machine should operate.
Questions to settle before the test
- Which requirements will be checked and by what method?
- What parts, utilities and process conditions will be available?
- Which interfaces will be simulated, and what remains for site?
- Who witnesses, records and approves each type of check?
- How are exceptions resolved and acceptance decisions recorded?
- Which released files and records are included in the handover?
For a new machine or a significant upgrade, MCT Nexus can help connect the requirements, controls development and verification work. Start with the equipment scope and the production conditions you need to demonstrate.
Discuss your project with MCT Nexus.
Share the equipment, production requirement and target timing. We will review the scope, interfaces and next steps with your team.