Phone calls still coordinate most internal moves
Most internal logistics moves still begin as a phone or radio message. That voice start drives interruptions and empty search between jobs that a claimable pull can cut.
What voice coordination still means on the floor
Many plants still treat voice as the default for routine station supply, even when a forklift guidance system is already licensed or listed in the plant stack. An operator or lead tells a driver what to move, where it sits, and where it should land. The driver may already be mid-trip, already loaded, or waiting between jobs with no open list to read. Radios stay useful for safety, congestion, and exceptions. They stay expensive when they own every ordinary material transfer.
That pattern creates two measurable costs. First, both ends lose attention: the station pauses to find capacity, and the driver answers while steering or waits for the next shout. Second, the gap between verbal jobs becomes empty travel and forklift patrolling: drivers circulating unloaded while the next task lives only in someone's memory. Neither cost shows cleanly as a single KPI line, so plants often fund more trucks instead of fixing how demand is offered.
Why the cost stays hard to see
Voice waste is scattered across short conversations and short empty runs. Talk time, wrong accepts, double-booking, station wait, and empty search after a call rarely share one report. Supervisors hear the noise. Finance sees fleet OPEX and overtime. Continuous improvement may sketch a spaghetti diagram once a quarter and still miss the voice request that launches most moves.
Lean manufacturing already names empty motion as muda. Without a claim record and a path record, that waste stays hard to prove. The same waste framed as an unpaid internal call center sits under the unpaid call center inside internal logistics. This page stays on the coordination impact: what changes when the request itself stops depending on a live conversation.
Turning the need into a claimable work order
Classic FGS stacks and twinzo's AOS (commonly known as FGS) reframe the same need as pull. A material call-off opens a work order in an open pool. Eligible drivers see origin, destination, load type, and priority. One driver accepts. The order leaves the pool so a second truck cannot claim it. Creation can start from a button, a barcode or RFID scan, a touchscreen, an e-Kanban flip, or a MES event. For industrial fleet management of internal movers, that is how demand finds free capacity instead of hunting it by voice.
Acceptance should record who requested, who took the job, acceptance location and time, then route, duration, and distance when movers are tracked. Live shift work uses that trail to know the job is owned. The same closed events land in the spatially oriented dataset under the hall view. Later correlation and causality analytics need those place-and-time pairings as much as the logistics desk needs fewer empty loops. Live moves, the stored spatiotemporal record, and pattern work stay equal readers of the trail. How the floor event becomes the right order stage is under how a floor request becomes a work order. How acceptance starts the audit trail is under the call that starts the record.
What one documented hall measured when pull replaced voice
A documented 30,000 m² (about 323,000 ft²) automotive Tier-2 facility moved internal moves from push phone traffic to this pull approach. Operator-to-driver phone calls fell by about 90%. Forklift patrolling dropped by more than 95%. Those two figures measure the same coordination load: effort spent keeping material moving when every transfer still depended on a live conversation or on drivers hunting for the next task.
No euro investment or saving was published for that specific change, so the impact stays in operational terms. Fleet-size and annual OPEX results from separate RTLS deployments belong on path pages such as real travel paths on the floor. Recovered line minutes from a larger white-goods AOS case sit under twenty minutes of production back every day. Keep those euros on the halls that earned them. This page stays on call volume and empty patrol.
How teams decide voice is no longer acceptable
1. Count operator-to-driver calls on one normal peak shift - Informal tallies are fine. Get a number before you buy software.
2. Estimate empty search share between those calls - If trucks look busy while lines wait, voice is hiding the gap that forklift tracking later has to prove on paths.
3. Pilot one claimable loop before a hall-wide cutover - Prove acceptance and trail quality under material order automation on one template and one driver group.
4. Keep path analytics as a sibling, not a substitute - Pull cuts coordination waste. Location cuts residual empty travel after jobs are claimed. 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. Keeping demand, acceptance, and place under one operating rule is practical smart manufacturing.
Capability depth sits on the features overview. How a rollout is priced is on pricing.
Get in touch if you want to walk through whether current call volume and empty loops still justify a voice-first dispatch habit on your hall.