A leveled schedule still fails if the aisles run in waves

The mix board shows a leveled sequence. By 10:00 the milk run and aisle still look like a batch wave. Planning calls it heijunka. Logistics calls it the same Monday flood.

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. Production leveling is only real when movers, buffers, and call-offs stop running in waves after the mix looks right on paper.

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 claim rules stay batchy. Changeovers that still favor long runs push work upstream into 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.

Heijunka on the board is a Plan claim. The aisle is the customer of that claim. 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. Volatile transportation demand creates capacity bottlenecks and late drops unless the system absorbs short-term order swings. That is the floor proof that schedule leveling and logistics leveling are not the same Check. 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.

Demand-driven planning research notes the gap between tactical plans and operational disturbances, and uses digital twins for dynamic feedback. That matches the principle here: the board is a Plan artifact. The hall is the Check. 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 does not own simulation procedure or SMED method. It owns live verification of heijunka.

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 Act from logistics Act - Mix sequence owners fix 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 Tuesday.

A typical moment: 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 until 10:30 and idle tugger time after lunch. Leveling on paper failed the logistics Check. The Act is retiming pitch and claim rules, 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 the Monday flood.