FAT — prove the configured system
Test the specified functions at the supplier or integrator site using controlled conditions. Agree on what can realistically be simulated and record deviations.
SAT — prove operation at the customer site
Retest relevant functions with real traffic, wireless infrastructure, doors, control integrations and operators under agreed conditions.
Use traceability rather than generic checks
Link each test step to one requirement, acceptance criterion, owner, evidence artifact and pass/fail decision.
Handle exceptions explicitly
Separate blockers from minor defects, assign owners, establish retest criteria and document the conditions for provisional acceptance.
Operational handover is a separate gate
Confirm training, service access, spare-part information, recovery instructions, software versions, backups and support escalation.
Acceptance is not a ceremonial signature. It is documented evidence that the agreed system works in its intended environment.
← Engineering Insights Library