Lesson 24 turns the program from designing to proving. The one thing every student must leave with: a calculator output is a perfect-world baseline, not a specification, and their job is to find where the real world bends it and how much margin it needs before they sign. If they walk out still treating a number off the calculator as the answer, the lesson didn't land. Teach the mechanisms of the bend, slippage, inertia, and load shift, don't slogan them, and keep the two gap-check and final-engineering runs for Lesson 25 where they belong.
| Segment | Min | What happens |
|---|---|---|
| Hook: the perfect world | 6 | Read the hook cold: every formula in the program produced a result for a perfect world, rigid box, new belt at commanded speed, all rollers spinning. Put the principle on the board, the calculator gives you the baseline, not the ceiling, and frame the part: from here on you prove the design, you don't just draw it. |
| Slippage and the shrinking gap | 12 | Teach slippage: the belt runs faster than the package, so the gap that forms is smaller than the calculated gap. Run the belt-slip demo (below). Land the design response, never design to the minimum gap, carry margin, and scope-guard that the gap check itself is Lesson 25. |
| Inertia and load shift | 14 | Static tumble angle versus the dynamic moment. Run the stack-of-books demo (below). Draw the thirds method in CAD or on the board and shift the load. Establish the rule: incline tips backward at belt start, decline tips forward at belt stop, always check the worst-case shifted load. |
| Solutioning vs final engineering | 10 | Same calculators, two stages. Approximate inputs and plus or minus ten percent in solutioning; confirmed inputs and tight tolerance in final engineering. Land the point: Part VI is the crossing. They did solutioning in Part III; now the numbers become specs. |
| Peer-review triggers (round-robin) | 10 | Run the triggers as a quick round-robin: call the manufacturer, call the controls engineer, ask a peer, and what each is for. Push the culture point hard, the call is professional practice, not an admission you don't know. |
| Riverside decline and Forest close | 8 | Re-check the mezzanine decline for the Tall Case at belt stop. Students commit the worst-case validation note to their Riverside file. Close on the Forest: the calculator was never the answer, judgment is. |
| Total | 60 | Baseline session. Expand with the stretch option below if you have 90 minutes. |
Two quick demonstrations, run back to back, build the whole margin habit in one class.
The slippage demo. Give the room a 25 CPM target and a product mix. Have them calculate the required belt speed with no margin. Then ask what happens if the belt slips 5 percent, then 10 percent. Walk them to the finding: a system calculated to exactly hit its rate misses it in the field, because slippage means the package never gets full belt speed. The fix isn't a faster belt they hope holds, it's margin they designed in.
The inertia demo. Ask what happens to a stack of books lying on a belt when the belt starts suddenly. They'll tell you the top books slide back and the stack leans. Then tell them: that's exactly what happens inside a carton at incline start, and it's why the static tumble angle isn't the whole safety check. Tie it straight into the thirds method and the shifted-load case.
Every one of these is the same failure wearing a different shirt: treating a calculator output as a final answer instead of a baseline for judgment. Drive each back to two questions, what could the real world do to this number, and who would tell you before it's built.
Re-run the mezzanine decline worst case as the beat's spine. Do not tell them the answer, ask for it. Steer the room to discover on their own that the belt-stop moment on the decline is the danger, and that the Tall Case with a shifted load, a 14-inch height on an 8-inch base with apparel contents that slide forward, is the carton that finds it. If someone re-checks the centered case, hand them the shifted one.
Then have them name the two peer-review triggers out loud and defend each one: the manufacturer call about the decline belt surface and whether the calculated angle suits this product, and the controls-engineer call about the VFD ramp time and a possible speed mismatch downstream. Hold the line on scope: they don't re-derive the Lesson 14 geometry and they don't set the drive values here. The grade is the reasoning and the margin decision, not a single angle.
Question 1 (two factors that tip a package that passed the static check). The two are inertial energy and load shift. Inertial energy: a belt start or stop adds energy the static calc ignores, so on a 15-degree incline the dangerous moment is belt start, inertia pushes the load toward the trailing edge and the carton tips backward. Load shift: the contents move, so the center of mass leaves the geometric center, and a package that passed centered can tip once shifted. Design responses: carry angle margin below the static limit, check the worst-case shifted load with the thirds method, and use VFD ramp-rate control to soften the start. Strong answers name belt start as the incline's risk moment and refuse to grade on the centered case.
Question 2 (the gap calc sitting right at the minimum). What to check about how the number was produced: whether slippage margin was added or the gap was designed right to the minimum, whether the inputs were confirmed (product envelope, finalized rates) or still approximate, and what belt and product surface the gap was figured for. The condition that eats the margin first is slippage, the belt outrunning the package so the formed gap is smaller than calculated. The tell that the engineer was still in solutioning: a plus-or-minus-ten-percent output being treated as a spec, an average package instead of the confirmed envelope, and no slippage-adjusted gap. Final engineering needs confirmed inputs and a margin above the minimum, not a raw minimum that "checks out."
This lesson opens the validation package, and it feeds the project-note habit that pays off at the capstone. The worst-case validation note a disciplined student writes today, the margin decision plus the two peer-review triggers, is a real capstone artifact they'll arrive already holding, the first piece of the Part VI validation deliverable. Most of them won't realize it yet.
Never announce it. The payoff belongs to the student who kept the note without being told why. Your job is only to make the habit feel normal, one file, added to every session. If they built it, the reveal is theirs at the capstone.