The main point
The FAT should confirm the machine built against the agreed requirement before dispatch. It should not become the first time the customer and supplier agree what success means.
Lancing UK Machinery
See the machinery and application options most closely matched to this production question.
1. Freeze the test scope
Reference the approved requirement and drawings. This should be recorded in the customer requirement so it can be tested rather than assumed.
- Reference the approved requirement and drawings
- List products, packs and quantities
- State test duration and pass criteria
2. Check functions
Verify guards, controls, alarms, recipes and changeovers. This should be recorded in the customer requirement so it can be tested rather than assumed.
- Verify guards, controls, alarms, recipes and changeovers
- Challenge no-product, no-pack and fault conditions
- Check documentation and supplied parts
3. Check performance
Measure sustained good output. This should be recorded in the customer requirement so it can be tested rather than assumed.
- Measure sustained good output
- Sample accuracy and finished-pack quality
- Record stops, adjustments and unresolved actions
4. Agree closure
Classify actions before dispatch or after installation. This should be recorded in the customer requirement so it can be tested rather than assumed.
- Classify actions before dispatch or after installation
- Retain settings and test records
- Confirm the SAT scope
Customer comparison table
| FAT evidence | What it should show |
|---|---|
| Performance record | Good output, rejects and interventions over the test |
| Quality samples | Measured results from start, middle and end |
| Function checklist | Controls, alarms, safeguards and changeover |
| Action list | Owner, due date and retest requirement |
Relevant Lancing routes
Use the guide to prepare the requirement, then continue to the specialist routes below.