Why empty forklift rounds still drain a white-goods plant
The 55,000 m² (about 592,000 ft²) white-goods hall looks busy. Trucks keep moving. Lines still micro-stop because the next pallet was never on a claimable call. The busy picture was empty patrol.
What empty rounds cost when the plant looks occupied
Drivers circulate looking for the next job. They check boards, wait for radio calls, or drive the familiar loop until someone flags them down. Each empty kilometre (empty mile) costs battery or fuel and keeps the vehicle out of productive service. When the next pallet or component does not arrive on schedule, the station micro-stops. Those interruptions are short, yet they accumulate across shifts and stations. In a plant this size the distance between storage, staging, and assembly makes empty travel even more expensive. A driver who spends half a shift searching rather than delivering is effectively half a resource missing from the material flow.
That habit rarely appears as a clean line item. It shows up every day in lost output minutes and in stressed drivers who look busy while lines wait. How non-value-added travel becomes countable on a map is under pinpointing non-value-added travel on the floor.
What one AOS installation recorded
In one documented case the plant invested €100,000 (about $110,000) in twinzo logistics management through AOS (commonly known as FGS). Operators or systems issue a material request through a button, scan, touchscreen, or MES connection. Drivers accept on a device. The model shifts from push to pull. Once accepted, the system records who needed the material, which driver took the job, acceptance location, route, duration, and distance.
The recorded outcome for that white-goods site was about a 95% reduction in unnecessary patrolling rounds and about +20 minutes of production time recovered every day. Micro-stoppages at the lines were eliminated. Driver workload balanced instead of some operators staying constantly busy while others continued empty circuits. This is a logistics-management case, not an RTLS fleet-cut case. Keeping those stories distinct prevents mixing module benefits. Path and fleet-size impacts sit under real travel paths on the floor.
What the recovered twenty minutes represent
Twenty minutes of additional production time each day is a concrete operational gain, not a derived percentage. It is the difference between a line that waits for material and a line that receives the next delivery because the request was issued and accepted without the intermediate patrol step. Over a production week those minutes compound into hours of output that would otherwise have been lost to waiting. The plant did not need a complex simulation to see the effect. The daily recovery appeared once the calling system replaced circulating until a task appeared.
The same closed calls also feed the spatially oriented dataset when positions share the hall, so correlation and causality analytics can later explain which request gaps keep preceding a micro-stop. Recovered minutes, stored history, and pattern work belong in the same benefit story.
How teams check the same trade-off
1. Time minutes drivers spend without an accepted task - On a normal peak, not a quiet weekend.
2. Count station stops caused by late or missing material moves - Short stops still count.
3. Price a pull calling setup against that baseline - Compare investment to recovered minutes and patrol share, not to a borrowed RTLS fleet-cut number.
4. Pilot one hall loop before claiming plant-wide success - Wire triggers under request triggers in the workflow editor, then measure again.
Product scope sits on material order automation and internal logistics optimization, with depth on the features overview. How a rollout is priced is on pricing.
Get in touch if you want to walk whether empty rounds on your hall are still the invisible operating cost the white-goods case removed.