Line walks
A walk is a route with clocks, not a tour of the whole hall
This page is the service-model map for the flagship study: where we stand, what we write, and when the crew sees the list. It is the page to read before you call about a plant day.
Before the visitor badge
The host names the line, the count point, and the person who can stop us if a lockout starts. We ask for two weeks of existing shift counts if they exist. We do not need a historian export. If the only record is a whiteboard photo, that is enough to start arguing about names.
The route
Inbound buffer, the machine or station that the crew blames, the outbound chute, and packing’s accept point. Quality holds are a side loop: ticket pad, first-pass check, hold cage. We do not wander into unrelated cells “while we are here.” That wandering ruins the clock.
What gets written on the card
Unit marks at a fixed interval. Stop tallies against the agreed dictionary. Three clocks around any changeover that lands during the visit. A crude high/medium/low mark for the inbound buffer. None of this is entered into a plant system. Transcription into a local desktop record, if the host wants one, happens after the shift and stays on a local machine.
Close-out
The ranked stop list is drawn at the line board before we leave, even if the written pack follows days later. Crews who only see a tidy document the next week will not recognize their Tuesday. If you want the visit itself, start with the throughput and downtime study. For letters, use contact details.