Real-time value stream mapping
Real-time value stream mapping turns continuous location and process events into handling cost and flow conformance. Relayout and automation then rest on measured paths, not a one-day workshop drawing.
What real-time value stream mapping is
Real-time value stream mapping rebuilds the material journey from continuous location and process events. Classic value stream mapping (VSM) inside lean manufacturing still does useful workshop work: process boxes, inventory triangles, and a lead-time ladder drawn from interviews and a few timed observations. Industry practice treats that picture as a snapshot. It ages fast in high-mix halls, understates layout and material-handling routes, and rarely prices multi-building hops as a margin item.
Real-time VSM keeps measuring how tagged SKUs, lots, or returnable carriers actually move across stations, buildings, and sites, then compares that path cost with the process flow engineering expected. Digital lean and VSM 4.0 programs use the same idea: feed dynamic maps from live systems rather than wait for the next annual sticky-note refresh. twinzo names that living loop real-time value stream mapping when the comparison runs on an operational digital twin.
That matters when the designed flow looks linear and the real route is a web. Separate processes that branch, return, and cross yards create handling between hops that a static VSM refresh often leaves off the cost sheet. The paper-versus-live decision sits under paper VSM versus a living value stream on the twin. This page owns the costing method and the capital decisions that follow.
MES events versus real movement
A MES records process-flow steps: start weld, complete wash, book to assembly. Those events describe the intended process graph. They do not prove how far the lot traveled, how long it sat between books, or whether one shift took a different building-to-building path than another. An real-time location system (RTLS) stream fills the gaps between scans with real movement, dwell, and empty or loaded travel.
Research on indoor positioning for digital lean shows the same split: process mining on MES events discovers the booked flow, while positional samples expose transport length, temporary buffers, and hidden queue time that bookings never name. Medium-precision location around 1–3 m (3–10 ft) is enough for hall-to-hall path cost and honest spaghetti diagrams. Sub-meter (~3 ft) exact floor position is not required for relayout-scale handling cost.
The useful comparison is conformance over time. Does live movement match the process-flow description this shift, this week, and after a layout change? When paths diverge, the plant sees either a documentation lag or a real workaround: a blocked aisle, a preferred side buffer, or a second-site hop that planning never costed. Slice the same SKU across days and weeks so a one-off Tuesday detour does not set policy, while a stable night-shift variant does. That is the same honesty used for unknown processes on the live floor, applied to the full value stream instead of a single side job.
Costing material handling per SKU across halls and sites
Real-time VSM turns path length, handoffs, and dwell into a handling cost per SKU or family. Distance inside one building is only the start. Multi-building and multi-site hops add yard moves, trailer waits, and double handling at each door. Pair those minutes and path length, reported in both meters and feet, with labor or fleet rates and the plant can say what material handling actually costs versus the expectation in the process sheet or the last classic VSM.
Expectation comes from the designed route: station sequence, standard travel, planned buffers. Reality comes from tagged movement on the twin used for internal logistics optimization. The gap between expected and measured handling is the margin argument the plant can take into a capital meeting. Extra loops, return trips to a previous hall, and long WIP waits between non-linear processes show up as cost that speed projects never touch if they only optimize cycle time inside each cell. Spaghetti diagrams and heat maps make the waste visible. The SKU cost roll-up makes it negotiable in a relayout meeting.
Under the same hall view the plant also stores a spatially oriented dataset: place-and-time history of the paths just costed. Continuous improvement can replay weeks instead of one workshop day. Correlation and causality analytics can later ask which detours keep preceding stops or starves. Live logistics cost, the stored spatial record, and hall-wide pattern work are equal reasons to keep the stream, not three afterthoughts behind a nicer wall chart.
Relayout, speed, and AGV or AMR decisions
Relayout calculations need more than a cleaner drawing. They need proof that moving a wash cell closer to welding, or staging a satellite buffer by the pack hall, cuts handling cost enough to pay for the civil work. Real-time VSM supplies before-and-after path cost on the same SKUs. Teams compare lead time and the handling-cost gap, not only walking intuition from one gemba tour.
The same evidence supports automated guided vehicle (AGV) and autonomous mobile robot (AMR) decisions. Stable, repeated corridors with high handling cost are automation candidates. Chaotic, low-frequency hops across sites may stay on manned trucks. If the live stream shows one shift already running a tighter path than the map assumes, automate that path, not the outdated wall version. Throughput and bottleneck talks then rest on measured travel and wait, not on the process-box sequence alone. Corridor choice after a live value-stream picture also sits next to why many RTLS projects start with logistics.
How teams run a live VSM loop
1. Pick SKU families with heavy handling - Multi-process, multi-building, or multi-site flows first. Tag the lots or returnable carriers that actually travel the hops. Do not tag every SKU on day one.
2. Capture the expected process flow - Station sequence and planned moves from MES, process sheets, or the last classic VSM. That baseline is the contract the floor is supposed to keep.
3. Measure real paths over shifts, days, and weeks - Compare live movement to the expected graph. Flag stable variants by shift. Ignore one-off detours until they repeat. Medium-precision RTLS at about 1–3 m (3–10 ft) is enough for this comparison.
4. Price material handling and test layout or automation options - Roll distance, dwell, and handoffs into cost per SKU. Use the gap to rank relayout moves and AGV or AMR corridors, then re-measure after the change. Keep the spatially oriented dataset so the next comparison does not start from a blank clipboard.
Matched stream versus drifted stream
When live movement matches the process description across weeks, the classic VSM was honest enough for that family. Invest in speed inside the cells and keep the living comparison as insurance when mix or layout changes. When the stream drifts by shift or by day of week, fix the flow geography before buying more station capacity. A stable overflow hop on the order of 200–300 m (650–1,000 ft) plus a trailer wait that MES never books is a margin fact, not a sticky-note footnote.
Either restore the intended flow or document the workaround on purpose and staff it. Leaving the wall map and the floor to drift means continuous improvement plans around a flow the plant no longer runs. Related WIP search and put-aside capital sit under search and find with RTLS. For how RTLS works on the floor, see what RTLS is. For when continuous location helps versus when a workshop map is enough, see when RTLS makes sense for material. A longer logistics analysis path is in logistics analysis with a digital twin.
Map the cost the wall chart missed
If material handling across buildings and sites still hides inside a linear VSM, instrument the moving lots and compare live paths to the MES story until relayout and AGV choices rest on measured handling cost. The digital twin pays when someone changes the geography, stores the place-and-time record those changes need, and supports correlation work on repeating detours, not when the dashboard only redraws the old sticky notes. Pair the same hall with production monitoring when process events and movement must share one picture. Get in touch if you want to walk the same real-time value stream on your own facility model.