Calls and micro-stops before a location grid
The line micro-stops. Drivers still learn the next job by phone. A location quote for the whole roof arrives in the same meeting. The calls are the cost you can remove this quarter. The roof grid is a different project.
When pull is the combination that fits
If the counted waste is operator-to-driver calls, purposeless patrol, and minutes the line waits for material, AOS (commonly known as FGS) is the combination to fund first. A button, scan, or MES link becomes a claimable work order. The fleet does not have to be large, and the hall does not have to carry a locator in every bay, for that change to pay.
A documented 55,000 m² (about 592,000 ft²) white-goods plant invested €100,000. Unnecessary patrol fell by about 95%. The plant recovered about 20 minutes of production every day. Micro-stops at the lines were removed. First-year increased production was €5,080,000. A documented 30,000 m² (about 323,000 ft²) Tier-2 hall cut operator-to-driver calls by about 90% and patrol by more than 95% on the same class of pull, with no euro figure published for that change. Both are coordination results. The production result is described in twenty minutes of production back every day. The call result is described in phone calls still coordinate most internal moves.
When location is the next purchase
Pull removes the search between shouts. It does not draw the path the truck still drives empty after the job is claimed. When that remaining empty travel is large enough to release trucks, add the location combination that matches the building: inverted BLE for a small hall, a pack on the truck for a small fleet in a large hall, a shared grid for one large roof and a large fleet. Those choices are described in the six-month return depends on the combination.
Do not use the €5,080,000 production figure to justify a 100,000 m² (about 1.08 million ft²) location grid. That euro belongs to the pull case. A combined customer often runs both. A single payback cell has to keep them apart. How the two run together is described in when pull and path share one hall.
What the claims are worth after the calls drop
Closed work orders are already a record of who needed material and who accepted. When positions arrive later, they join the spatially oriented dataset on the same hall. Correlation and causality analytics can then ask which request gaps keep preceding a micro-stop. Until the locations exist, the claim log is still enough to judge the pull investment. Live dispatch is part of material order automation. The hall view is part of internal logistics optimization and production monitoring.
How teams sequence the spend
1. Count calls, patrol share, and line-wait minutes on one peak week - If those dominate, fund AOS.
2. Hold the location quote until empty travel is the leftover - Match it to hall size and fleet size, not to the pull euro.
3. Judge ROI within six months on the module you installed - The €100,000 white-goods case is a pull reference. It is not a roof-grid reference.
4. Add locations as their own test when the fleet cut is the remaining benefit - What the product can do is on the features overview. How a rollout is priced is on pricing.
Get in touch if a roof-wide location quote is attached to a problem your calls and micro-stops already explain.