A leveled schedule still fails if the aisles run in waves
Heijunka on the schedule board can look level while movers, buffers, and call-offs still arrive in waves. Board leveling is not aisle leveling until those flows stop bunching.
What heijunka is supposed to absorb
Heijunka levels volume and mix over a planning window so the plant does not swing between overload and idle. In lean terms it attacks mura (unevenness) so muda and muri do not follow. A smoother sequence protects people, machines, and suppliers from peak-and-valley strain. Classic TPS framing keeps the same intent: make what is needed in a steadier pattern, not in heroic Monday batches and quiet afternoons.
Leveling is hard under uncertain demand because plants trade inventory against capacity flexibility. That difficulty does not excuse calling a smooth board a leveled hall. A smooth mix sequence is only half of leveling. Volume and mix on the board still leave mura in place if material flow keeps peaking and idling in the same window.
Why the schedule can look level while the hall does not
A leveled mix sequence can still release material in clumps if supermarket pitch, milk-run timing, and the rules for who accepts open material jobs stay batch-oriented. Changeovers that still favor long runs keep production in large batches, so material demand still hits the aisles in the same morning flood. Overflow staging and radio habits recreate the wave even when the heijunka board looks disciplined. Planning sees a smooth plan. Logistics sees aisle congestion, starved stations later, and tuggers that sprint then wait.
After those mechanisms, the board still only states intent. Logistics still has to prove on the same day that movers, buffers, and call-offs stayed level. If material call-offs still bunch into the first hours, movers still flood shared corridors, and buffers still swing from empty to overflowing, mura has only moved from the mix sheet into internal logistics. Teams that argue only about the sequence miss the wave the hall already shows.
In-plant milk-run research treats delivery peaks as a real operating problem even when routes are defined. Shared tracks and loading areas create dependencies between trains. Volatile transportation demand creates capacity bottlenecks and late drops unless the system absorbs short-term order swings. That is the floor proof that a leveled mix sequence and leveled material flow are different checks, even when both sit under the same heijunka program. Internal logistics optimization that only celebrates a smooth mix board still fails when the aisle runs in waves.
Live spatial check for leveling
Simulation answers what-if before racks move. An operational digital twin verifies the day that ran. Live locations show whether movers still surge, whether buffers fill and empty in waves, and whether material call-offs clump after the mix board claimed smoothness.
Tactical mix plans still drift under short-term floor disturbances. An operational twin closes that gap by feeding live hall evidence back into the leveling check. That matches the principle here: the board is a planning artifact, and the hall is where you check whether leveling held. In PDCA terms, the mix sequence is Plan and the aisle replay is Check. Medium-precision location around 1–3 m (3–10 ft) is usually enough to see corridor waves and buffer swings. Exact floor position is a different accuracy job. What-if layout trials sit under simulate the kaizen before you move the racks. Changeover time that unlocks finer mix sits under SMED with timed changeovers on the twin. This page covers live verification of heijunka, not simulation procedure or SMED method.
How teams decide whether leveling held
1. Define the wave signal - Morning mover density, buffer occupancy swing, or call-off clumps against the leveled pitch.
2. Compare board claim to hall replay - Same day type, before and after a mix or milk-run change.
3. Separate schedule fixes from logistics fixes - Mix sequence owners change the board. Logistics owners retune routes, pitch, and drop rules when the aisle still floods.
4. Keep thin standards - A red wave means a named countermeasure, not another poster that freezes one lucky day.
When the heijunka sequence interleaves high and low option content, yet the milk run still leaves the supermarket with a front-loaded cart every hour, replay shows aisle congestion in the morning and idle tugger time after lunch. Leveling on paper failed the logistics check. The fix is retiming pitch and the rules for accepting open material jobs, not reprinting the board.
Store that place-and-time evidence in the spatially oriented dataset so continuous improvement can ask which mix days still create waves. Later correlation and causality analytics sit on equal footing with today's aisle recovery. A lean manufacturing leveling program that only audits the board has not finished the principle.
Where twinzo sits
twinzo shows whether movers and buffers still surge after the mix looks smooth, under internal logistics optimization and production monitoring. Capability depth sits on the features overview. Get in touch if planning still calls the board heijunka while logistics still runs in waves.