How a floor request becomes a work order
A floor material need only helps when it opens a claimable work order for the stage and vehicle class that own the next action. Radio habits alone leave that request sitting in someone's pocket.
Two order templates, not one radio habit
Internal logistics is not one marketplace with one vehicle. A milk run is usually a fixed loop run by a tugger pulling multiple trolleys. Industry milk-run design treats that tour as multi-stage: stations or machines fire need into a supermarket, people prepare the load onto trolleys, then a tugger driver delivers the prepared train on a planned circuit sized to theoretical consumption. Some plants couple picking and driving in one person. Others decouple supermarket prep from the delivery lap so the tugger spends the circuit on delivery instead of supermarket pick.
A forklift order is usually direct. The station asks a forklift driver group to bring a full pallet-size load, remove an empty, or do both. There is no supermarket prep between the ask and the mover. Plants often collapse both shapes into one radio habit, so dock forklifts take line-feed jobs and milk-run trains get treated like one-off pallet jobs. The full distinction sits under milk-run orders vs direct forklift orders.
From floor trigger to the right work-order stage
A material call-off can start as a button press, a barcode or RFID scan, a touchscreen tap, an e-Kanban flip, or a signal from MES. twinzo AOS (commonly known as FGS) should turn that event into a claimable work order for the stage that owns the next action. On milk-run material that may be a supermarket prep job first, then a tugger delivery job once the trolleys are ready. On forklift material that is one direct job to the forklift group.
Classic FGS stacks usually open the same kind of claimable jobs from transport order states in ERP or warehouse systems. twinzo AOS starts from floor events and still keeps an open pool drivers can accept. Either path beats push and radio when the open list shows origin, destination, load type, and which vehicle class may accept, without a dispatcher re-keying the ask. Trigger and stage mapping live under request triggers in the workflow editor. How e-Kanban flips must still open a claimable job is under e-Kanban cards that become claimable work orders. How quiet milk-run laps free capacity for other pulls is under milk runs on theoretical consumption vs dynamic pull across lines.
What tugger and forklift drivers each see
Tugger drivers in the milk-run group see delivery jobs for prepared trains, not raw machine signals that still need supermarket pick. Forklift drivers see pallet-size brings, empty removes, or combined swaps. A driver taps to accept. That order leaves the open list so a second driver cannot claim it. Acceptance is the marketplace match inside the group. Offer scope stays group broadcast, first accept wins, not nearest-truck assignment. That boundary is under group broadcast vs nearest-truck myths.
Keeping vehicle classes apart is how lean manufacturing pull and industrial fleet management share the same hall without mixing job types. One shared group turns every open job into a fight over machine type. On a documented 30,000 m² (about 323,000 ft²) automotive Tier-2 hall that moved internal moves to this pull approach, operator-to-driver phone calls fell by about 90% and forklift patrolling dropped by more than 95%. Those numbers measure coordination load when jobs stop living only on the radio. Impact framing sits under phone calls still coordinate most internal moves.
The trail that starts at acceptance
The moment someone accepts a stage, the platform should record who requested, which person took it, the acceptance location and time, then route, duration, and distance when movers are tracked. Multi-stage milk-run orders keep supermarket prep and tugger delivery on the same family of records so engineers see the full handoff. Direct forklift orders keep a single claim-to-complete trail. On the shift, live claim and execution both depend on that record.
Those closed trails also land in the spatially oriented dataset when positions share the hall frame. That stored place-and-time history is what later correlation and causality analytics need when asking which request patterns keep preceding a starve. Live moves, the spatiotemporal record, and pattern work sit on equal footing. How that trail begins as a call record is under the call that starts the record.
How teams decide pull is ready
1. Split today's radio traffic into milk-run multi-stage vs direct forklift - Count each template separately.
2. Wire one supermarket-to-tugger loop and one station-to-forklift loop end to end - Prove the stages before expanding.
3. Keep tugger and forklift driver groups apart - Vehicle class is scope control, not a soft preference.
4. Recheck call volume and empty patrol after two weeks on both templates - If neither moves, templates or groups are still misconfigured.
That sequence is a practical smart manufacturing join: demand becomes claimable work, not another dashboard tile. Product depth sits on material order automation and internal logistics optimization, with capabilities on the features overview. How event-driven AOS differs from SAP-state FGS is under AOS on tracked forklifts vs SAP-state forklift guidance. How a rollout is priced is on pricing.
Get in touch if you want to walk how a request on your line should become a supermarket prep stage, a tugger delivery, or a direct forklift work order.