PART VIII | LESSON 34: COMMISSIONING AND ACCEPTANCE MATERIAL HANDLING ACADEMY
DRIVING QUESTION How do we prove it works, and who keeps it running after we leave?
Acceptance to service pipeline: gate one is the FAT at our firm over a factory icon, we run it and the scripts exercise every path. An arrow labeled ship carries the system to gate two, the SAT on the customer floor over a building icon, drawn in gold, customer criteria and sustained rate under real load, where the customer accepts. Three stations continue: punch list, customer training, go-live. The line then opens into a navy service-model band with four chips: SLA, warranty boundary, remote-diagnostics owner, and spares by criticality tied to Lesson 26 plus O and M docs.

Two gates, two owners. We prove it at the FAT. The customer accepts it at the SAT.

Two Tests, Two Owners

FAT

We own it · at our shop

Test scripts exercise every routing decision, every handshake, every exception path, on purpose, before it ships.

SAT

Customer owns the criteria · on their floor

Sustained rate against the design target, under real load. The WMS handshake confirmed at real volume. Then sign-off.

The Service Model

SLA

To the customer's real maintenance capability.

Warranty boundary

Stated cleanly, before a failure, not after.

Remote diagnostics

Who reaches it. Assigned here; the network is L21.

Spares + O and M

By criticality (L26), docs, every serviceable part reachable.

DESIGN PRINCIPLE Prove it sustained, then design what keeps it running.