Acceptance is prepared before the first tests. It defines which functions will be checked, on which parts, under which conditions and by whom. The record should let the customer and integrator establish the same facts and then address remaining reservations.
Define the project stages
FAT here means acceptance testing at the supplier’s premises. SAT means testing at the installation site. The contract defines their content and participants. A function dependent on the customer’s machine may not be verifiable under the same conditions at both stages.
The public abstract of IEC 62381:2024 describes FAT, FIT, SAT and SIT for process-industry automation systems. It refers to agreed specifications and responsibilities. This reference does not establish applicability to every robotic cell; the full standard is not reproduced here.
Connect each requirement with evidence
Assign an identifier to each requirement to verify. For each one, specify the method, prerequisites, acceptance criterion and result location. A requirement such as handling format A should identify the part, its presentation and intended destination.
Criteria may concern a dimension, sequence, alarm or delivered document. Avoid wording such as satisfactory operation without a defined observation. Items still open at quotation stage should be agreed before the relevant test.
Agree measurement conditions
Define the parts and formats, their variation and the campaign duration or number of cycles. Specify available resources, equipment state and permitted operator interventions. Results are tied to that configuration.
For throughput, agree measurement start and end points, included pallet changes or changeovers, waits and rejects. Retain counts and observed events. Measuring an isolated sequence does not automatically establish production throughput.
Specify whether an adjustment during the campaign requires all or part of the measurement to restart. The result should identify adjustments and their effect on the protocol.
Verify recovery situations
The test list should cover interruptions and faults relevant to the cell. Consider a missing part, absent vision result or unavailable peripheral. Describe preparation and the expected state for each case.
Tests take place under controlled conditions without bypassing required safeguards. Distinguish functional recovery checks from safety-function verification. Define the responsible person and expected evidence for each.
Record what changes on site
The FAT record identifies completed tests, results and items deferred to SAT. Describe simulated or absent interfaces. Changes between the stages should appear in a version record and in preparation for subsequent testing.
SAT verifies the agreed functions with site equipment and constraints. Suva’s work-equipment acceptance checklist addresses safeguards and available documentation. CE marking alone does not replace these acceptance checks.
Close each test with its status
The record identifies the requirement, tested version, date, participant, observation and retained evidence. Separate accepted, rejected, accepted with reservation and not tested according to agreed rules. A blank field is not a positive result.
Each reservation receives an owner, an action and a verification method. Acceptance signatures, production authorisation and commercial closure follow their own responsibilities and conditions as defined for the project.
Common questions
Points to clarify.
Does FAT replace SAT?
The project defines their scope. Actual site interfaces and conditions may require tests that cannot be performed at the supplier’s premises.
What document should be prepared before testing?
A requirements and test matrix with prerequisites, criteria, owners and expected evidence, followed by a results record template.
Can a reservation remain open?
Treatment depends on the agreed conditions. Document its effect, owner and any restrictions.
