Skip to content
Operating model

Value stream map

Where does the time actually go?

SupplierStores cage
  1. Record the promiseHelen Ward
    C/T n/a
  2. Release the lotMara Ellison
    C/T n/a
  3. Issue the materialAndre Pell
    C/T n/a
  4. 11 h queue
    Machine the seat faceDevon Cho
    C/T 46 min
  5. Inspect the seatPriya Shah
    C/T n/a
  6. Kit and packLuis Ortega
    C/T n/a
  7. 16 h lag
    Confirm the shipmentLuis Ortega
    C/T n/a
CustomerHartwell Process Equipment18 bodiesTakt 25 min
Touch 46 minWait 11 h before the cell and 16 h after the truck
The seven steps as a time survey on one spine. Machining is marked: 46 minutes of touch under 11 hours of queue, and 46 is over the 25-minute takt.
How this sheet sits with the others

Almost all of the lead time is wait. The median queue before machining is 11 hours, and the posted touch time is 46 minutes, which is already over the 25-minute takt. The revision that lives in email, and the 16-hour lag from truck to Ledgerline, are delays in the record rather than in the metal. No touch or wait is stated for the other steps.

What it makes visible
Touch, wait, and where the record lives, including the delays in the record itself.
When it is useful
When the argument is about lead time rather than about who moves the lot.
Who uses it
Mara Ellison sees the queue. Devon Cho sees the touch time. Luis Ortega sees the confirm lag.
What it takes
The seven steps, and the times already known for queue, touch, and confirm lag.
What it leaves
Machining marked because 46 minutes of touch sits under 11 hours of queue, and because 46 is already over the 25-minute takt. The email revision and the 16-hour confirm lag marked as information delay.
The underlying record
Touch and wait on those same seven steps, the queue under Devon Cho's seat-face work, the revision that stays in email, and the lag from the dock back to Ledgerline are the time the path sheets share.

Where these facts go next

What this sheet still leaves out

It has no cause and no specification.