Four questions, one for each lesson in Part VIII. Work them without your notes. These are judgment questions: there's a right way to think about each one, not a sentence to memorize.
CHECKPOINT
L32 The HandoffYou're preparing to release an installation drawing package. The mechanical installer has reviewed it and signed off. The controls team hasn't answered your two emails, and mobilization is in four days with the project manager pushing you to release. What do you do, and what's the failure mode you're trying to avoid by not simply releasing on schedule?
L33 Execution SupportMidway through installation the mechanical installer says a structural column is in the way, and moving the conveyor eighteen inches to the left would clear it. He wants your approval to make the move. What is your process before you say yes or no, and what is the difference between evaluating that change locally and evaluating it at the system level?
L34 Commissioning and AcceptanceThe system hits the customer's rate target for a clean two-minute demo, and the customer wants to sign acceptance on it. Their real volume arrives in compressed wave releases. What do you require before you call the system accepted, and why is a sustained statistical run against the design target a different proof than the demo?
L35 Becoming the EngineerA customer's stated rate feels aggressive for the product mix, and this is your first project in a vertical you've never worked in. Two do-not-run-alone triggers just landed on the same project. What do you do before the proposal goes out, and who do you call for each concern?
YOUR RIVERSIDE DELIVERY FOLDER
Deliverable
Quality Criteria
Handoff package checklist
The drawing released as the plan, reviewed with every trade before mobilization
Every trade interface named with an owner, every vendor's scope confirmed against the released drawing
A cutover phased by flow, the manual path kept open as rollback
Change-impact evaluation and as-built
Every field change run through the change-impact matrix before yes or no, documented, and traced to the Tall Case tumble limit before approval
Redlines collected at every visit, the as-built matching what was actually built
The project folder closed so another engineer can read the full history without asking a question
The commissioning plan
A FAT our firm runs, scripts exercising every path including the WMS timeout
SAT criteria that are the customer's: sustained 20 CPM under real load, misdirects down from the roughly three percent Dana described, one-second latency proven under peak
A service model designed to Michael's team of one: SLA, warranty boundary, remote-diagnostics owner, spares by criticality, and O and M docs
Readiness map and first-90-days plan
A readiness self-assessment against the five observable criteria, honest about where you'd still ask
An escalation map with the four categories filled in with your organization's real names
A first-90-days plan, and the eight habits built in from the first project