Milk runs on theoretical consumption vs dynamic pull across lines
Milk runs sized to theoretical consumption still keep the tugger backbone. Dynamic forklift pull reuses the slack those loops leave when real consumption runs below plan.
What a milk run is sized to
A milk run is a planned internal supply tour. In most halls it is a tugger pulling multiple trolleys on a fixed loop, not a one-off pallet hop. Industrial engineering and logistics size stops, quantities, and intervals from theoretical or standard consumption. Orders for that loop are usually multi-stage: stations or machines fire into a supermarket, people prep trolleys, then the tugger delivers. That template is under milk-run orders vs direct forklift orders.
Classic tugger-train planning, including methods in the VDI 5586 family, often assumes relatively steady throughput and sizes route frequency, train count, and buffers from planned unit-load demand. That is a push-style backbone: the tour is built so the line can be fed at standard rate when the process is stable. On a stable process it is hard for a line to consume faster than that plan for long. Extra demand usually means defective material, scrap, or a plan that was wrong. Everyday reality runs the other way. Changeovers, micro-stops, quality holds, and thin staffing cut real consumption below standard. The milk run still rolls with the theoretical load. Tugger capacity reserved for that lap can sit idle while another hall needs a direct forklift hop now.
Push on the tour, pull on the exception
Lean manufacturing replenishment draws a sharper line. A fixed milk-run timetable can still move material on a clock. True pull waits for actual need. Plants signal that need with Kanban, e-Kanban, a station button, or a MES message that opens a material call-off. Industry guidance on consumption-oriented tugger systems makes the same point: when demand is not deterministic, moving only what was theoretically scheduled leaves either under-loaded trains or starved stations unless buffers and the delay between signal and delivery are sized for real consumption.
That is why many halls keep both shapes. Steady small-container feed stays on the supermarket-to-tugger milk run. Irregular pallet brings, empties that cannot wait for the next lap, scrap exceptions, and dock-to-line hops stay on direct forklift call-offs. Collapsing both into one radio habit breaks line-side inventory management: trolleys arrive with parts the station did not need, while a pallet wait never becomes a claimable job.
Where fixed tours lock fleet capacity
If the only answer is more milk-run frequency or more dedicated tuggers per loop, the plant staffs for theoretical peaks on every route. Average reality is lower. Tuggers and drivers stay tied to a clock even when their stations are quiet. Cross-line waits still open because free capacity is locked inside the wrong tour and the wrong vehicle class. That is how milk-run-only management grows headcount and machines without matching live need, and how industrial fleet management spends seats on under-loaded laps instead of claimable work.
Dynamic call-offs into twinzo AOS (commonly known as FGS) change the management job without deleting the milk run. Keep the multi-stage supermarket prep and tugger delivery path for baseline trolley feed. When a station needs a pallet-size bring, empty remove, or irregular hop, open a claimable work order to a forklift driver group. Quiet milk-run periods free drivers and hall capacity so those forklift groups can answer across lines. Offer scope stays group broadcast: the first accept wins, and the system does not route to the nearest truck. Do not permanently shrink the milk run to average slow days and then fail when the line returns to plan.
What efficiency looks like when pull uses the slack
Plants that keep milk runs as the tugger baseline and AOS as the live forklift layer measure fewer dedicated seats per theoretical loop. Supermarket prep and tugger delivery stay staged. Irregular pallet pulls and empties stop waiting only for the next full tour clock. How a floor request becomes either shape of work order is under how a floor request becomes a work order. How groups are split by vehicle and stage is under how to size and split driver groups. Group broadcast versus nearest-truck myths is under group broadcast vs nearest-truck myths.
When movers are tracked, paths and idle time land in the spatially oriented dataset under the live hall view. Live logistics still sees which loops ran light and which forklift claims absorbed the slack. Continuous improvement uses the same stored place-and-time record. Correlation and causality analytics can ask which slowdowns keep freeing capacity that never reached the waiting station. Live shift operations, the stored spatial record, and pattern work share one twin stack. Sharing one twin stack is practical smart manufacturing for internal logistics and production on the same floor.
How teams decide the mix is right
1. Keep milk runs on theoretical consumption as the tugger backbone - Multi-stage supermarket prep stays in place for steady container feed.
2. Treat slower-than-plan as normal, faster-than-plan as rare - Defect and plan error are the usual exception cases for sustained extra demand.
3. Fund direct forklift AOS so freed drivers can claim work across lines - Do not dump pallet jobs into the tugger delivery group.
4. Review under-loaded milk-run laps beside aged forklift jobs weekly - Slack that never moved is still waste, whether you see it as empty seats or as line wait.
Ordering and fleet use sit under material order automation and internal logistics optimization, with depth on the features overview. Production waits on the same hall are under production monitoring. Pricing is under pricing.
Get in touch if you want to walk through whether your milk runs still lock tugger capacity to theoretical clocks, or already free the hall to pull with forklifts across lines when consumption runs slower than plan.