Lesson 23: Recovery, Diagnostics, and the Operator | Slides

MATERIAL HANDLING ACADEMY

Part V. Lesson 23. Recovery, Diagnostics, and the Operator.

DRIVING QUESTION When it jams, stalls, or goes dark, how does the system recover?

PART V | LESSON 23: RECOVERY, DIAGNOSTICS, AND THE OPERATOR

It Will Jam

Everything across this part designed the system for the day it works: the scanner reads, the WMS answers in time, the divert fires, the carton lands at the right door. This lesson designs it for the day it doesn't, and that day always comes. A photoeye stays blocked and a zone jams. A lane fills during a wave. A barcode won't read. The WMS drops for ninety seconds at the worst moment. None of those are exotic. They're Tuesday.

What separates a system an operator trusts from one they fight is whether every failure has a designed destination and a designed recovery, or whether it stops the whole line and waits for someone to figure out what happened. Recovery is engineering, not improvisation.

PART V | LESSON 23: RECOVERY, DIAGNOSTICS, AND THE OPERATOR

Give Every Failure a Destination

A jam is detected when a photoeye that should clear inside a defined time window stays blocked past it; the PLC stops that zone and alerts the operator. That response is deliberately blunt, because a jam that keeps feeding is a jam that grows.

A lane-full condition is detected when the photoeye at a sort lane's entry stays blocked, so the lane can't take more product. The carton headed there has nowhere to divert, so the system sends it elsewhere: a backup lane, recirculation on a loop, or the destination of last resort, the hospital lane.

PART V | LESSON 23: RECOVERY, DIAGNOSTICS, AND THE OPERATOR

COMMON MISTAKE

Designing the hospital lane as a placeholder rather than a throughput element. It's easy to draw the exception box at the end of the sorter and move on, because during initial sizing it never seems to matter. Then the no-reads and rejects show up at the rate they always do, the placeholder can't clear them, and it backs up into the sorter and creates a secondary jam that stops everything.

PART V | LESSON 23: RECOVERY, DIAGNOSTICS, AND THE OPERATOR

Every no lands on one rail and ends at the hospital lane. The throttle valve and the WMS-down branch are the two ideas the rest of this lesson builds.

PART V | LESSON 23: RECOVERY, DIAGNOSTICS, AND THE OPERATOR

Size the Hospital Lane to the Exceptions

WHYThe hospital lane is where every unroutable carton ends up. If it can't clear them as fast as they arrive, it backs up into the sorter and stops the whole system. It's a throughput element, sized to the exceptions.

WHENSized during design, from the expected no-read rate and reject criteria, not left as a placeholder box at the end of the sorter.

WHEREAt the exception destination, with its operator workstation and its own re-induction path back onto the line.

NOT WHENDon't size it to total system volume, and don't drop it in as a placeholder at the end of the drawing. It doesn't need to handle every carton, just the exceptions, faster than they arrive.

FAILURE IF IGNOREDThe lane fills during the first real peak, exceptions have nowhere to go, and the backup climbs into the sorter. Now a lane meant to protect the system is the thing stopping it, because the exception path was an afterthought.

PART V | LESSON 23: RECOVERY, DIAGNOSTICS, AND THE OPERATOR

A Controls Rule and a Mechanical Runway

Anti-gridlock control prevents it by correlating induction rate to clearance rate. If the lanes are filling and the loop is loading up, the system throttles or stops new induction before it runs out of path. The PLC watches lane status and loop load continuously. That's the controls half, and it's where most engineers stop.

Here's the half they miss. The PLC can only throttle if the layout gave it enough physical buffer to absorb product while the throttle takes effect. Leave no runway between the induction gate and the loop, and no PLC logic prevents gridlock under heavy load. That buffer is floor space, not code.

PART V | LESSON 23: RECOVERY, DIAGNOSTICS, AND THE OPERATOR

FIELD INSIGHT | MICHAEL COLLINS

The way the controls interact with incoming product on a sorter has to be directly correlated to the rate at which the sorter can get rid of product or divert product. If you are inducting faster than the sorter can clear, you will fill the loop, fill the lanes, and have nowhere for the product to go. That is gridlock. The controls must throttle induction based on what is happening downstream, not just run at maximum speed because product is available upstream.

PART V | LESSON 23: RECOVERY, DIAGNOSTICS, AND THE OPERATOR

ILLUSTRATIVE SIZING FIGURE

Example only. The percentages below are placeholders to show the method, not measured rates for any real system.

System throughput: say 1,200 cartons per hour at the sort point.
Expected exception rate: say 1.5% no-read + 0.5% reject = 2% routed to the hospital lane.
Exception volume: 1,200 × 0.02 = 24 cartons per hour the lane has to clear.
Design check: the operator and the re-induction path have to move at least 24 an hour, plus margin for a peak burst, or the lane backs up into the sorter.

PART V | LESSON 23: RECOVERY, DIAGNOSTICS, AND THE OPERATOR

THINK LIKE THE OPERATOR

It's 2 AM. A zone's stopped and the HMI is stacked with alarms. You don't want a wall of red; you want one line naming which photoeye stayed blocked and where, so you walk to it, clear it, hit a reset you can find, and watch the zone come back without anything lurching. Design for that person on that shift, not for the demo where nothing goes wrong.

PART V | LESSON 23: RECOVERY, DIAGNOSTICS, AND THE OPERATOR

DESIGN PRINCIPLE Every failure gets a destination and a recovery.

Next: Where does the calculated answer stop being true, and how much margin does it need?