Buyer Brief
A factory acceptance test should verify the agreed conveyor scope before shipment, not introduce new requirements after assembly. The checklist should trace to approved specifications and cover dimensions, workmanship, representative products, normal sequence, cycle performance, interfaces, safety functions, faults, documentation, and open items.
In This Guide
Freeze the test basis before the FAT
Use the approved layout, functional description, I/O list, product data, acceptance criteria, and change log as the test basis. Identify any site-only equipment or utilities that cannot be reproduced at the factory.
Agree on who attends, which tests require witnessing, what evidence is recorded, and how deviations are classified. This prevents the FAT from becoming an unstructured demonstration.
Test with representative loads and realistic sequences
Run the smallest, largest, heaviest, least stable, and other worst-case products or approved test loads. Verify starts, stops, accumulation, curves, transfers, lifts, rotation, positioning, and line rate under defined conditions.
Challenge blocked downstream, missing products, sensor failures, drive faults, low air pressure, communication loss, emergency stops, guard opening, and power recovery where applicable.
Close the FAT with evidence and ownership
Record test conditions, results, measurements, alarms, software versions, photos or video, and agreed deviations. Every punch item should have an owner, required action, due date, and verification method.
The shipping release should state what passed, what remains open, and which site-acceptance tests still depend on installation, facility utilities, or connected equipment.
FAT test groups
| Group | Examples | Evidence |
|---|---|---|
| Mechanical | Dimensions, alignment, guards, finish | Inspection record and measurements |
| Product flow | Transfers, curves, accumulation, stability | Representative-load run |
| Performance | Cycle time, speed, repeatability | Timed and measured results |
| Controls | I/O, sequence, alarms, interfaces | Test sheet and software version |
| Safety | Stops, interlocks, reset, restart | Approved validation record |
Recommended Project Workflow
Write a traceable protocol
Link every test to an approved requirement or drawing.
Prepare samples and utilities
Confirm products, loads, power, air, networks, tools, and calibrated instruments.
Execute normal and fault tests
Record conditions and results rather than relying on visual impressions.
Issue a closure report
List passes, deviations, punch items, evidence, and remaining site tests.
Frequently Asked Questions
Is a no-load conveyor run enough for FAT?
No-load checks are useful, but product handling should be tested with representative loads whenever the scope permits.
Should cycle time be tested?
Yes, when it is an agreed performance requirement and the factory setup can reproduce the defined operating conditions.
What if connected machines are not available?
Use agreed simulators or temporary interfaces and identify the remaining integrated site tests.
Can punch items remain open at shipment?
Only with buyer approval, documented ownership, due dates, risk review, and a verification plan.
What documents should be checked?
Review approved drawings, schematics, I/O, BOM, manuals, spare parts, certificates actually required, software backup, and test records.
Planning a Conveyor Project?
Send the product, load, throughput, layout, environment, controls, and destination requirements for an engineering review.
