Lesson 8 taught flow before equipment and produced a confirmed Layer 1. This lesson teaches the method that turns that Layer 1 into a design map. The one outcome every student must leave with: the diagram grows in rounds without ever changing format, and by Layer 4 it carries enough to drive every downstream decision. Don't lecture the four layers off a slide. Build them live, on the board, from a confirmed Layer 1, and make the room watch a concept turn into a specification. Two disciplines carry the whole session: write requirements that are specific and measurable, and plant the three data questions without answering them.
| Segment | Min | What happens |
|---|---|---|
| Recap the confirmed Layer 1 | 4 | Put Riverside's Layer 1 back on the board: two zones, merge, sort, three doors. Confirm the room agrees it's the story. Make the point that layering starts here and never before. You don't layer a flow the customer hasn't signed off. |
| The layered method, live build | 14 | Key teaching moment, below. Take the same diagram and add volume, then a delay note, then a buffer requirement, in front of the room. Bring up the buildup graphic and let them watch a concept become a specification without the format ever changing. This is the center of the lesson. Do not skip it. |
| Layer 2: volume and rate | 7 | Work the 20 CPM combined backward to 55, 35, 10 at the doors, then back through the merge to each zone line. Land the deferral hard: Layer 2 sets the rate target, it doesn't calculate belt speed. That's Lesson 10. Anyone reaching for feet-per-minute is a lesson ahead of the room. |
| Layer 3 and the three data questions | 10 | Mark the sort as a smart decision point. Write the three data questions on it as a class. Then stop. Coaching note below: they plant, they don't solve. Note Ray's unconfirmed latency as an open item on the diagram, not as a fact. |
| Layer 4: buffers and people | 10 | Buffer notes as explicit requirements, then the operator-symbol pass. Watch-for below. Force every student to drop operator and maintenance-access symbols onto a diagram they thought was finished, and have them report what it changed. |
| The diagram governs the quote | 5 | Read the Field Insight aloud. Land the close from the Quoting Standards Guide: a quote with no flow diagram behind it isn't a quote, it's an estimate with a BOM attached. The four layers are the foundation the quote stands on. |
| Riverside and close | 10 | Run the Zone A / Zone B split debate below. Collect each student's four-layer diagram and hold it to the standard: could a knowledgeable person read it without asking a question? Grade the reasoning and the specificity, not neatness. |
| Total | 60 | Baseline session. Expand with the stretch options below if you have 90 minutes. |
Teach the layered method step by step with a real example, on the board, not off a slide. Draw the blocks and arrows. Then add volume. Then add a delay note and a buffer requirement. Show how the diagram grows from a concept into a specification without ever changing format. Bring up the buildup graphic on the assets, lesson-09-flow-layers, and use it as the live prop while you build. The same Riverside flow sits there in four states, so the room can see the destination while you draw toward it.
The moment that lands the lesson is the one where a student realizes they didn't start a new document. They deepened the one they already had. Say it out loud: agreement on Layer 1 is what earns you the right to layer at all, and the format staying constant is what keeps the customer, the controls team, and the install crew reading the same page.
The failure this lesson is built to prevent is the people-in-the-layout miss. Students design material flow and forget operator access, maintenance clearance, and safety paths. Force the operator-symbol pass and drive these back to the board:
This is the single most important boundary in the lesson. At each smart decision point the room writes three questions and stops: what decision gets made here and what does the system need to know; who or what makes it and where does the information come from; what happens if the answer doesn't arrive in time. That's the whole job for now.
If a student starts designing the handshake, the query, the payload, the timeout, the retry, the fallback, redirect immediately. That's Part V, Lesson 22. The discipline in this lesson is describing the decision point completely, not answering it. A student who wants to solve the controls is a student who's confident, and confidence pointed a lesson early creates a diagram that looks finished and skipped the questions. Praise the instinct, hold the line, and tell them exactly where they'll get to do it.
Dana gave the door splits, 55, 35, 10, but never the split between Zone A and Zone B. That gap is the teaching moment. Give the room a few quiet minutes to complete Layer 2, then open the floor on the zone split. Expect guesses at an exact number. That's the wrong instinct to reward.
The standard is a defensible, labeled assumption with an open-item flag, not a confident exact number pulled from nowhere. A student who assumes a 50/50 split, labels it as an assumption, and flags it to confirm with Dana has done it right. A student who writes "60/40" as if it were fact has learned nothing from the safe-and-unsafe habit. Make that explicit before they hand anything in: on Layer 3, the same rule governs Ray's latency estimate. It's an open item on the diagram until the confirmed number arrives, and the diagram should mark where that number turns into a design constraint.
The Riverside four-layer diagram is a real deliverable, and it goes into the same running project note the students have kept since Lesson 1. Have them date the entry and file the completed diagram where they can find it. Frame it as what professional engineers do with a document this load-bearing.
Don't explain where the habit leads. The payoff is theirs to find later, and it lands hardest for the students who kept their notes without being told why. This is the lesson where the note stops being a scratchpad and starts holding the document the rest of the program builds on.