Lesson 17: The Automation Landscape, Instructor Session Plan

This is the forest-through-the-trees lesson of the part. Six lessons taught the room to design conveyor well; this one teaches them to zoom out far enough to ask whether conveyor was the right tool at all. The outcome every student must leave with is the honest question, said out loud before a line gets drawn. Don't lecture the landscape off a slide. Have the room take a conveyor design they built earlier, argue the case for a non-conveyor alternative, then argue why it does or doesn't win. Reinforce the elegant-simple standard the whole way, the minimum necessary solution that solves the real problem and nothing more.

Run of Show (60-minute baseline)

Segment	Min	What happens
The question you should have asked	6	Read the hook aloud. Put the standard on the board: the elegant, minimum-necessary solution. Ask whether the conveyor they spent six lessons on was even the right tool, and let the room sit in the discomfort. That discomfort is the lesson.
The landscape	14	Survey level, no deep dives. AS/RS, goods-to-person, AMR and AGV, robotics, print-and-apply. Each is a category with a fit, not a product. Show the figure. Land the Lesson 7 rule: when the operation is really a platform, the manufacturer's sizing tool is the authority. No platform sizing, no payback.
Specialty conveyors	12	Close the Part II specialty scope guard. Garment-on-hanger and overhead, tire handling, and other products a standard bed can't carry cleanly. Drive the five-versus-twenty-percent judgment: specialty share decides exception path or different system. Keep it category-level.
Environments and when conveyor is not the answer	14	Washdown, freezer, dusty as selection drivers that eliminate technologies early. Then the honest close: the situations where conveyor is the wrong tool. Run the Three W's card. Hold scope: guarding is Lesson 27, harsh-environment reliability is Lesson 26.
Should Riverside even be conveyor	10	Run it as a real debate, below. Steer the room to the conclusion on their own and to name what would have changed the answer. Grade the reasoning, not the label.
Forest, and the controls-brain handoff	4	Close the whole part. Then the Controls Corner: every platform brings its own control brain, and the interface is the job at the boundary, not the internals. Hand forward to Part V by name.
Total	60	Baseline session. Expand with the stretch option below if you have 90 minutes.

Stretch option (for a 90-minute block):

Catch the goods-to-person operation (add 12 min): hand the room a facility whose real problem is clearly a goods-to-person one, dense slow-moving SKUs, a lot of pick travel, a tight-but-tall building, and a request for a long conveyor line. Don't tell them what it is. Watch who catches that the elegant answer isn't conveyor, and make the student who catches it defend the call and name what they'd need from the manufacturer's sizing tool to size it. That catch is the whole competency of this lesson.

KEY TEACHING MOMENT | ARGUE THE WRONG TOOL

Have the room take a conveyor design they built earlier and argue the case for a non-conveyor alternative against it. Assign one student the alternative (a goods-to-person grid, an AS/RS, an AMR fleet) and have them make the honest case for it; then have the room argue why it does or doesn't win. A student who can make the honest case for the wrong tool and then explain why it loses understands the right tool better than one who only ever defends conveyor. You're not grading the label. You're grading whether they can place conveyor next to the alternatives and reason across the whole landscape without falling in love with the steel they already know how to draw.

WATCH-FORS

This lesson exists to build the honest question. Watch for the students who can't ask it:

Can't zoom out from the conveyor they just designed. Send them back to the whole operation and ask what the real problem is before any equipment.
Treat the alternatives as competitors to dismiss rather than tools to place. Every category is a tool with a fit, not a threat to conveyor.
Forget the environment as a selection driver. Put washdown, freezer, or dusty back on the table and ask what it eliminates.
Would force conveyor onto a storage-density or a specialty-product problem. That's the exact failure the lesson is built to prevent.
Quote a made-up automation-adoption or payback number. Those figures live in Lesson 3 and Lesson 29 with corrected framing; Lesson 17 stays category-level. Correct it on the spot.

RIVERSIDE FACILITATION | SHOULD RIVERSIDE EVEN BE CONVEYOR

Run this as a real debate, not a rhetorical one. Give the room a few quiet minutes to test the design they built against the alternatives, then open the floor. Don't tell them the answer. Ask.

Steer them to the conclusion on their own. Riverside's problem is outbound sorting to three doors at a 20 cartons-per-minute target, with a manual misdirect problem, a mezzanine feed, and a maintenance team of one. That's sortation and routing at the dock. It isn't a storage-density problem an AS/RS solves, and it isn't a pick-travel problem a goods-to-person grid solves. Volume and destination count fit conveyor and sortation well, so conveyor is the right tool here, and the value is being able to say why. Make them name what would have changed the answer: much lower volume, a dense slow-moving storage problem, or a floor too tight for the footprint. Hold scope hard: no platform sizing (Lesson 7), no payback (Lesson 29), no guarding depth (Lesson 27).

CHECKPOINT ANSWER KEY

Question 1. Pauses on three signals: low volume that may not justify fixed steel, dense slow SKUs where travel time dominates picking cost, and the tight-but-tall footprint. Categories on the table: goods-to-person (travel-dominated pick) and AS/RS (storage density in a tall building); the sharpest answers flag that jumping straight to conveyor-and-sortation is itself the thing to question. To decide without a conveyor calculation, get the manufacturer's platform sizing tool for each candidate and choose on the real problem, footprint fit, service life, and maintenance reality. Payback is Lesson 29, not run here. Don't accept a bare technology label with no reasoning.

Question 2. Separates two drivers. The environment (washdown) demands corrosion-resistant materials and designs that drain and clean, and rules out mechanisms that trap water; the small reactive team pushes toward simpler, more durable equipment even at higher up-front cost. The specialty product (bagged apparel) is bag-hostile, fights a flat bed and a standard shoe sorter, and likely needs its own path. The majority carton doesn't decide alone: the environment eliminates technologies for the whole building, and the specialty's volume share can force an exception path or a different system. Washdown compliance is Lesson 27, reliability is Lesson 26, not run here. The grade is holding both drivers at once.

INSTRUCTOR ONLY | DO NOT SHARE WITH STUDENTS

The automation-landscape review the Riverside strip asks for is a project-folder artifact, not busywork. The "why conveyor fits Riverside" reasoning the student writes here becomes part of the proposal's justification later. When the customer asks why the answer is conveyor and not something else, the honest written comparison is already done. Keep reinforcing the running-note habit without explaining where it leads. The students who kept an organized Riverside note and wrote this review into it will have their justification half-written before they start the proposal. Don't tell them that. Just make the habit feel like what professionals do.