Value Stream Map Data Worksheet (Process Box Data and Lead Time)
A value stream map is only as good as the data in its process boxes. This worksheet gives you one row per process step, calculates wait time from inventory, and rolls it up to lead time and process cycle efficiency. Collect the numbers on the floor, paste them in, and export to Excel for your map.
| Process step | Cycle time (sec) | Changeover (min) | Uptime (%) | Operators | WIP in front of step (pcs) | Wait time from WIP (sec) | Labor seconds per piece (sec) | |
|---|---|---|---|---|---|---|---|---|
15,200 | 38 | |||||||
44,400 | 74 | |||||||
13,500 | 45 | |||||||
18,000 | 0 | |||||||
10,400 | 104 |
Wait time here is WIP times the downstream cycle time, a common VSM approximation. Use a true bottleneck-paced time if your line is not balanced. Cycle time should be observed at the gemba, not copied from routings.
Baseline your value stream from ERP data
Optional: we can pull routings, WIP and lead times from your ERP to pre-fill a current-state view.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Walk the flow from shipping back to receiving and record each step as you see it. For every step enter observed cycle time in seconds, changeover in minutes, uptime as a percent, operators, and the count of pieces sitting in front of the step. The sheet multiplies WIP by cycle time to estimate waiting time and sums everything into lead time. Take at least ten cycle time readings per step and use a typical value, not the best one. Edit the five example rows or delete them and add your own.
- Walk the process yourself; do not rely on routings or ERP standards
- Count WIP physically on the day of the walk
- Record changeover as the last good piece to first good piece
- Use the same unit of measure (pieces, kits or lots) across all rows
The math behind lead time and process cycle efficiency
Production lead time is the sum of processing time and the time material waits between steps. A simple way to estimate waiting is inventory divided by demand rate, or pieces in queue times the cycle time of the step that consumes them. Process cycle efficiency, often called PCE, is value-added time divided by total lead time. In the example, processing is under four minutes while inventory adds close to a week of waiting, so PCE is well under one percent. That gap is the typical picture in batch machining and is the target of flow improvements.
Reading the result
Low PCE does not mean the people are slow. It means material waits. Look at the rows with the largest wait time from WIP first, since those queues point at batching, long changeovers or unreliable machines. High changeover with low uptime suggests SMED and TPM work. Compare the total labor seconds with your takt time to see how many operators the demand actually needs. Once you draw the future state, repeat the worksheet with target WIP and compare lead times.
Common mistakes
Mapping a product family that does not share the same steps produces a map no one can act on. Another frequent error is measuring cycle time on a perfect run and ignoring minor stops. Mixing hours and minutes between rows is also common. The worksheet is a data tool; the map itself still needs customer demand, takt, information flow and the push or pull arrows that explain why the inventory exists.
Frequently Asked Questions
What data goes in a VSM data box?
Typical boxes hold cycle time, changeover time, uptime or availability, number of operators, batch size, shifts and scrap rate. This worksheet covers the core fields that drive lead time and PCE, and you can extend it in Excel with scrap and batch size after export.
How do I convert inventory to days of wait?
Divide the pieces in the queue by the daily customer demand. For example, 600 pieces with demand of 200 per day is three days. The worksheet uses WIP times cycle time, which suits a line paced by that step.
What is a good process cycle efficiency?
Traditional batch operations are often below five percent. Lean flow lines may reach 25 percent or more. Use PCE to compare your own before and after maps rather than chasing a universal number.
Should I use ERP data or measured data?
Use measured data for the current-state map and compare it with ERP routings afterward. Differences between the two are findings in themselves and usually show outdated standards or unrecorded waiting.
If your routings, WIP and work center data live in an ERP, we can help pull them into a baseline value stream view so the walk only has to confirm them.
Related Tools
Standard Work Combination Sheet Worksheet
Record each work element with manual, machine and walk times and get the operator's total cycle time to compare with takt.
Supply Chain & InventoryKanban Card Size Calculator
Calculate how many kanban cards or bins a part needs from daily demand, replenishment lead time, container size and safety factor.
Discrete ManufacturingSpaghetti Diagram Distance Calculator
Convert the distance you measured on a spaghetti diagram into walking time and annual cost, and compare it to an improved layout.
Discrete ManufacturingTakt Time Calculator
Compute the takt time your line must hit to meet customer demand, plus the required hourly rate for supervisors and schedulers.
More Discrete Manufacturing tools
See all- Manufacturing KPI Dashboard Template
- Manufacturing KPI Formula Reference
- Changeover Reduction (SMED) Savings Calculator
- SMED Changeover Element Analysis Worksheet
- 5S Audit Checklist
- Kaizen Event Charter Template
- Gemba Walk Checklist
- SMED Changeover Reduction Savings Calculator
- EPEI Every Part Every Interval Calculator