Lesson 28 opens Part VII, where the engineering stops living in the student's head and becomes a document other people build from. The one thing every student must leave with: the drawing is the plan, and the pre-release call to every trade is how you find out what's missing while it still costs nothing to add. If a student can't name a specific callout when you ask what a trade needs, the lesson hasn't landed yet. Drive them to the specific missing item every time.
| Segment | Min | What happens |
|---|---|---|
| The phone that starts ringing | 6 | Open on the hook. Steel bolts down, wire gets pulled, every trade works from the drawing the student produced. Put the principle on the board and leave it there: the drawing is the plan, not a starting point. Set up the whole hour against it. |
| Callouts by trade | 14 | Walk the what-belongs-on-the-drawing table as callouts by trade. For every item, ask the room: who needs this, and what happens on the floor without it? Land that each callout is the answer to a question a trade would otherwise phone in. Flag that the speeds and guarding were engineered upstream; this lesson places them, it doesn't re-derive them. |
| The pre-release interview, taught then run live | 16 | Teach the discipline: call every vendor before release and ask what they need to see. Then run it. Assign three students the three trades on the Riverside system and have them tell you what they need on the drawing. The gaps they surface are the lesson. This is the heart of the hour. |
| Vendor RFQ completeness | 12 | Vendors price what they're told. Walk the margin-loss gaps: pull cords not in the electrical RFQ, VFDs not specified per motor, the Aux I/O list and WMS interface missing from the controls RFQ. Land that the gap comes out of the engineer's margin because the engineer owns the scope. |
| Riverside RFQ-gap hunt | 10 | Hand out the three Riverside vendor RFQs. Run the completeness check as a hunt: which one is missing the pull cords, which is missing a VFD, which is missing the Aux I/O list. Do not tell them. Ask. Steer them to discover the gaps. |
| Forest and close | 2 | Fold in the close. Return to the driving question: can every trade build their scope from this drawing without calling you? That's the test for every line on the sheet. |
| Total | 60 | Baseline session. Expand with the stretch option below if you have a longer block. |
Hand the room a drawing that's missing three things: the speed callouts, the pull cord E-stop path, and the accumulation zone release modes. Tell them: "you are the controls team, what do you do?"
They will do one of two things. Either they invent a workaround and program to a guess, or they call the engineer. Both answers open the real conversation, which is that the drawing has to be complete before execution begins. A guessed speed misses rate on the first test. A missing release mode runs a zone the wrong way. Neither one is the controls team's fault; both trace back to a sheet that didn't answer the question.
Then run the pre-release interview as a live exercise. Pick the Riverside system, assign three students the three trades, and have each one tell you what they need to see on the drawing to execute their scope without ambiguity. Write their asks on the board. The gaps they surface are the lesson. Do not fill the gaps for them; make them name the specific callout.
Hand out the Riverside setpoints and geometry: belt speeds by section, the decline VFD ramp rate, scan and sensor locations, PLC delays at the transfers, accumulation release modes, the pull cord path and reset locations, the Aux I/O locations, and the disconnects at the two 480V panels. The student assembles these onto the drawing. They don't re-derive them. The gap and sorter math is done.
Run the RFQ-completeness check as a hunt. Give them the three vendor RFQs and let them find the holes: which RFQ is missing the pull cords, which is missing a VFD, which is missing the Aux I/O list. Do not tell them. Ask. The discovery is worth more than the answer.
Hold the line on scope. If a student starts running the handoff meeting where every trade walks the drawing together, or starts reviewing field redlines, redirect. That work is Part VIII. Lesson 28 completes the drawing and the RFQs before release. The walkthrough and the execution support are named there and taught there.
Question 1 (release with controls silent). You don't release to the field on the strength of silence. Silence isn't sign-off. The controls team owns the items most likely to be missing from the sheet, so those are the ones at risk: belt speeds by section, the decline VFD ramp rate, the PLC delays at the transfers, the accumulation zone release modes, the Aux I/O count and zones, and the WMS interface scope. Get the controls team on the phone, not on email. If you genuinely can't reach them before the mobilization date, take the gated move: document each controls-dependent callout as a known open item with a risk and a plan, and either hold the release or release with those items flagged as not yet released for construction. The four-day pressure is the project manager's schedule. The correctness of the drawing is yours, and a guessed speed that misses rate on the first test costs more than the four days.
Question 2 (pull cord E-stops as a post-award change order). It happened because the pull cord E-stop runs weren't on the drawing and weren't itemized in the RFQ that went to the contractor. Vendors price what they're told, and this one priced exactly their RFQ. The pull cord E-stop path is an electrical callout, so whichever vendor flags it, the failure is the same: the scope handed out didn't include the runs. The gap is the engineer's, because the engineer owns the scope definition. The step that prevents it: the pull cord runs with dimensions belong on the installation drawing and explicitly in the electrical RFQ, and vendor quotes get reviewed against the design scope with every gap documented before award. The pre-release call is the early catch; the quote-against-design review is the last one before it becomes an 800-foot change order.
The installation drawing, the pre-release call notes, and the vendor RFQs are all project-folder artifacts. The student who kept the Riverside folder organized from Lesson 1, dating every note and saving every calculation, is assembling this drawing package from work already in hand. The setpoints are in the folder. The guarding audit is in the folder. The geometry is in the folder. This lesson is where the folder habit starts paying off in earnest.
Don't announce it. The payoff belongs to the students who kept the folder without being told why, and it lands hardest for them when they reach the proposal and find most of the package already built. Keep reinforcing the habit as normal professional practice and leave the reason for them to discover.