Phone calls still coordinate most internal moves
The line needs a stillage. The operator calls a driver who is already mid-trip. The driver finishes, then waits for the next shout. Both people lost focus. The truck burned an empty loop between the two conversations.
Why voice coordination stays expensive
In a typical plant the request for material still travels by phone or radio. An operator needs a part, calls a driver, and hopes the message lands at the right moment. Drivers answer while already moving, or they finish a trip and then wait for the next call. The pattern feels ordinary, yet it creates constant small interruptions and a steady volume of empty travel between jobs.
That friction is hard to see on a dashboard because it lives in the coordination itself rather than in a single KPI. Every call pulls attention from the production station and the forklift seat. Over a full shift the interruptions accumulate, and so does time spent waiting for the right material or the right truck. Supervisors notice the noise. The cost is scattered across dozens of short conversations and short empty runs.
Turning the request into something drivers can claim
twinzo's logistics management layer, AOS (commonly known as FGS), reframes the same need as a pull request inside an internal marketplace, the plant form of a forklift guidance / Uber-for-intralogistics loop. The work order appears for available drivers the way a ride request appears in a consumer app. Creation can happen through a button, a barcode scan, a touchscreen, a material call-off, or a connection to MES.
When a driver accepts, the platform records who requested, who took the job, acceptance location and time, the route driven, duration, and distance. Engineers later have the data without reconstructing the shift from memory. Drivers stop circulating in search of the next verbal instruction. The request becomes visible and claimable. How that sequence is wired is under how a floor request becomes a work order.
What one plant measured when voice stopped owning the loop
A documented 30,000 m² (about 323,000 ft²) automotive Tier-2 facility moved from the old push habit to this pull approach. Phone calls between operators and drivers fell by roughly 90%. Forklift patrolling, the empty circulating that fills gaps between verbal instructions, dropped by more than 95%. The two results measure the same cost: effort required to keep material moving when every transfer still depends on a live conversation or on drivers hunting for the next task.
No euro figure was attached to this particular change, so the impact stays in operational terms: fewer interruptions and far less purposeless travel. Fleet-size and annual OPEX savings from separate RTLS deployments belong in those stories, including real travel paths on the floor. This page stays on the coordination layer.
How teams decide voice is no longer acceptable
1. Count operator-to-driver calls on one normal peak shift - Informal is fine. Get a number.
2. Estimate empty search share between those calls - If trucks look busy while lines wait, voice is hiding the gap.
3. Pilot one claimable loop before a hall-wide cutover - Prove acceptance and trail quality under material order automation.
4. Keep path analytics as a sibling, not a substitute - Pull cuts coordination waste. Location cuts empty-mile waste. Both feed internal logistics optimization and the stored spatial record for later pattern work. Joint impact sits under when pull and path share one hall. Production minutes from the same pull habit sit under twenty minutes of production back every day.
Capability depth sits on the features overview. How a rollout is priced is on pricing.
Get in touch if you want to walk whether your current call volume and empty loops still justify a voice-first dispatch habit.