The whole lesson turns on one thing students miss: after a ninety-degree transfer the package travels hard-way even though it never rotated, because they think about the conveyor instead of the package. Don't lecture the orientation change off a slide. Make the room answer the question that makes it real, then run the merge-jam diagnostic and let them find the air-feed root cause themselves. If they leave able to say why air feeding a merge is an uncontrolled induction condition, not just that it's bad, the lesson landed.
| Segment | Min | What happens |
|---|---|---|
| Hook: the package that never turned | 6 | Read the hook aloud. Draw a ninety-degree transfer on the board and divert one carton off the trunk. Ask the room whether the package rotated. Sit in the wrong answer for a beat before you correct it. The package is the same way around it always was; the takeaway just runs the other direction. |
| The transfer: strands, hard-way centers, frame gap | 16 | Key teaching moment, below. Strand spacing, then the takeaway roller-center recompute from the hard-way dimension, then the frame gap and the transition roller. Read THINK LIKE THE PACKAGE aloud and let the carton's questions drive the design points. |
| Transfer controls: the delay that drifts | 12 | Photoeye upstream, PLC delay, O-ring degradation, stopping-position drift. Land the fix: clearance-by-design, not a tighter delay. Work the Common Mistake as a live correction. |
| Merges: three types, the zipper, the air rule | 14 | Straight, spur, sawtooth. The zipper release as the one control principle. Then run the merge-jam diagnostic below and make the room reach the air-feed root cause and the belted-section fix on their own. |
| Riverside: the merge and the transfer | 10 | Design the merge feeding the sorter with Michael's first failure in the room. Then catch the hard-way takeaway recompute and the Small Case frame-gap check. Facilitation below. Hold scope: no dead-time math, no sorter pick. |
| Forest, close, CONTROLS CORNER preview | 2 | Tie the two moves back to the package. Preview the CONTROLS CORNER: the transfer PLC delay and the merge zipper release both land on the installation drawing, and Part V, Lesson 20 is where they get programmed. |
| Total | 60 | Baseline session. Expand with the stretch option below if you have 90 minutes. |
Draw the transfer. Put a carton on the trunk easy-way, long side leading, and divert it ninety degrees onto the takeaway. Then ask the room one question and wait: after the transfer, which dimension of the product is now in the direction of travel? That question is the whole moment. Students who think about the conveyor will say the package turned. It didn't. It's the same way around it always was, and because the takeaway runs the other direction, its short side is now leading. It's traveling hard-way.
Once they see it, the design falls out. Ask what that does to the takeaway roller centers, and let them reach tighter centers off the hard-way dimension. Ask what happens at the seam where two conveyors butt together, and let them find the frame gap and the transition roller. The orientation change unlocks every other point in the transfer, so don't hand it to them. Ask the question and let them turn it.
Present it as a field call, not a quiz. Two or three lanes of air-based accumulation feed a merge. It jams two or three times a shift, but only during wave releases, and maintenance finds no mechanical problem. Ask the room to diagnose it before touching a single PLC parameter.
Steer with questions. What's feeding the merge? What does air do when the compressor is loaded during a wave? What's the PLC counting on at the release point, and what happens to the zipper if the reaction time of one lane wanders? The answer they have to reach themselves: air feeding a merge is an uncontrolled induction condition, because the release timing the PLC depends on is only as repeatable as the air, and air isn't repeatable. The fix is a belted conveyor section at the end of the accumulator, upstream of the merge, for positive control. Make them explain why the belt fixes it, not just that it does.
Four failure modes to catch in the room. In every case, drive them back to the why, not just the correction.
This lesson teaches the physical design and the control reality of transfers and merges. It doesn't run the final-engineering arithmetic. Hold two lines.
Two flows have to become one before the sort: Zone A coming down the mezzanine decline from Lesson 14, and Zone B running along the ground floor. Have the room design the merge that combines them. Ask what type of merge they've got, what's feeding it from each side, and what that means for the accumulation upstream. Do not tell them; ask. Then put Michael's first failure back on the table, the pneumatic accumulation system that died when the compressor dropped pressure during peak, and make them address the air-feed risk explicitly for this building.
Then flip to the transfer side. A Standard Case or a Small Case diverting to a dock-door takeaway is riding hard-way. Steer them to discover the orientation change themselves and recompute the takeaway roller centers from the hard-way dimension. Then hand them the Small Case, 8 by 6 by 4, and ask whether it clears the frame gap. That one is small enough to hang up, and the student who checks it against the gap without being told has internalized the lesson. Grade the reasoning. The deliverable is a merge configuration with the air-feed risk addressed, plus a transfer note with hard-way centers and a frame-gap treatment.
The merge configuration and transfer design note the students write today is a project-folder artifact, not a throwaway exercise. Its controls timing, the transfer PLC delay and the merge lane-switching sequence, feeds straight into the controls architecture summary later in the Riverside thread, where every machine-level setpoint has to appear on the installation drawing. Keep reinforcing the project-note habit: date it, keep it organized, file it with the rest of their Riverside work.
Don't explain where the habit leads. The payoff is theirs to find when these scattered notes turn out to be exactly the inputs the controls summary needs. Your job is only to make filing the design note feel like normal professional practice.