What continuous spaghetti buys back in analyst hours
The kaizen board still says Act. The analyst's calendar says another walked shift, because Tuesday's spaghetti diagram died when overflow parking took the north aisle on Thursday.
Collection is a recurring cost, not a one-time study
Industrial engineering time is operating cost whether or not it sits in a project code. A walked spaghetti, a stopwatch logistics study, or a clipboard value-stream day spends skilled hours on collection: standing in the aisle, tracing routes, redrawing, and then defending the picture in a review. That work is honest for the hours observed. It becomes expensive when kaizen needs the picture again after the layout, the mix, or the overflow habit changes. The Act column waits on the next observation window. Check has consumed the people who were supposed to change the aisle.
The method for why the floor walk eats time sits under the floor walk still eats time. The principle that a rare logistics audit is not a meter sits under a logistics audit is not continuous measurement. This page is the hours arithmetic: people times hours times how often you restudy, and what those hours are worth if they move from drawing to Act. It does not teach anyone how to draw spaghetti.
Price one restudy, then multiply by the year
A typical restudy is not a single afternoon. Someone books the window with the shift, walks a representative slice, redraws trails, and sits in the review where half the room argues the day was unusual. Two analysts, a full shift of observation, a day to draw, and a meeting is a normal shape. If that cycle runs every other month because kaizen is real, you have six collection bills a year before anyone moves a rack. Direct time study has the same shape and a known weakness: it is slow, sensitive to the day you happened to watch, and easy to dispute. Plants that cannot repeat it often enough do not have a stable standard. They have a poster.
Do not invent a salary saving from a brochure. Multiply your own loaded analyst hour by the hours in one restudy and by the number of restudies you actually ran last year. Add the kaizen delay: weeks a known loop stayed in place because the picture was stale and nobody would Act on it. That delay is not analyst payroll. It is the waste the study was meant to remove, still running. Calendar snapshots of a value stream have the same stall. How a scheduled Check throttles the loop sits under scheduled checks still throttle the kaizen loop. Paper versus a living stream is a different decision under paper VSM versus a living value stream. Neither page is this hours bill.
What continuous paths change in the cost structure
A real-time location system (RTLS) on the movers you argue about feeds paths into an operational digital twin. The collection step stops being a booked walk. Any past window can be replayed: yesterday's overflow, last night's milk run, the hour the aisle jammed. Indoor-positioning work aimed at digital lean makes the same shift. Positional data becomes lean measures without a fresh multi-day stopwatch study each time the question returns. Medium precision around 1–3 m (3–10 ft) is enough for aisle and buffer trails. Exact floor position, about 3 ft, is a different spend and is not required to see a loop family.
The benefit is analyst capacity, not a nicer poster. The same people spend the hours on Act: which corner to change, whether the change held on the next three shifts, and which empty trails are still non-value-added. That test is under pinpointing non-value-added travel on the floor. Stored trails are also the record later questions need. Which corners keep preceding a starve is a pattern question on history you no longer have to recapture by hand. Internal logistics optimization is where those paths should be readable by the people who will move the rack, not only by the analyst who drew last quarter's sheet. PDCA speeds up when Check is cheap. It does not speed up when Check is a prettier backlog of drawings nobody has time to finish.
When paper is still the cheaper buy
One baseline, on a stable loop, for a decision you will make once, can still be a clipboard. If you will not restudy, continuous trails are a meter you will not read, and the license is waste. Paper is also enough when the argument is a single workstation's hand motion inside a bench, where a location tag on a vehicle will not see the wrists. Buy continuous spaghetti when the trails change often enough that collection hours are repeating, or when meetings still reopen with 'does this waste even exist' because the last picture is two layout tweaks old.
Gemba does not disappear. People still walk to ask why a loop exists and to confirm what a map cannot feel. The paid change is that Thursday's walk starts from a trail that already flagged the aisle, instead of starting from a blank sheet because the old sheet died. Lean manufacturing still owns the waste language. The twin owns the cheap remeasure.
Count restudies before you fund the meter
1. Count logistics restudies and spaghetti redraws last year - People, hours, and how often the picture was stale before Act.
2. Count debates that reopened because nobody trusted the last walk - Those meetings are collection cost too.
3. Keep paper if the cycle is truly one baseline - Do not buy a continuous meter for a decision you have already made.
4. If the cycle is ongoing, compare analyst hours moved to Act with the cost of continuous paths - Your hours, your quote. How a rollout is priced sits on pricing. What the hall can show sits on the features overview.
A rare audit that cannot be rerun is theater with a timesheet. Get in touch if analyst weeks are still going into redraws, and the kaizen that needed those weeks is still waiting.