Phone Calls Still Coordinate Most Internal Moves
In a typical plant the request for material still travels by phone or radio. An operator on the line 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 is a decision that pulls attention from both the production station and the forklift seat. Over a full shift the interruptions accumulate, and so does the time spent waiting for the right material or the right forklift to appear. Supervisors notice the noise more than the cost, because 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 module, called AOS, reframes the same need as a pull request inside an internal marketplace. The work order appears for available drivers the way a ride request appears in a consumer app. Creation can happen through a simple button, a barcode scan, a touchscreen, or a direct connection to the existing MES or other plant systems.
When a driver accepts the order the platform records the essential trail: who requested the material, who took the job, the location at acceptance, the route driven, the duration, and the distance. Engineers later have the data for review without having to reconstruct the shift from memory or radio logs. The same record also removes the need for drivers to keep circulating in search of the next verbal instruction. The request itself becomes visible and claimable instead of remaining locked inside a phone call.
One Plant's Measured Drop in Coordination Load
A 30,000 sqm automotive Tier-2 facility moved from the old push habit to this pull approach. Phone calls between operators and drivers fell by roughly 90%. At the same time forklift patrolling—the empty circulating that fills the gaps between verbal instructions—dropped by more than 95%.
The two results belong together. They measure the same underlying cost: the 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 reported for this particular change, so the impact remains expressed in the operational terms of fewer interruptions and far less purposeless travel. The plant did not need a new fleet model or a new cost study to see the difference; the difference showed up in the daily traffic of calls and empty loops.
Looking at the Same Pattern on the Floor
The practical question is how often operators and drivers still exchange calls or radio messages during a normal shift, and how much of the forklift movement is still spent searching rather than delivering. Those two observations sit inside most plants already, even if they are only informal. Making the request visible and claimable simply turns the activity into structured records that can be examined the next day without adding a new layer of process overhead.
Because the measured outcomes for fleet size and annual OPEX savings come from separate RTLS deployments, this view stays deliberately limited to the coordination layer. The decision that matters here is whether the current volume of voice traffic and empty travel is still acceptable, or whether the plant is ready to move the request itself into a shared, visible system. That keeps the conversation focused on one controllable friction rather than on a broader transformation story.