When pull and path share one hall
Claimable pull and live path analytics each cut a different internal logistics waste. The strongest impact shows when both share one hall record.
What each layer owns
Pull turns a material need into a claimable work order. An operator, button, scan, material call-off, or MES link raises demand, a driver accepts in a group, and acceptance, place, route, and completion leave a trail. That loop is twinzo's AOS (commonly known as a forklift guidance system, or FGS) under material order automation.
Path is the location layer. A logistics real-time location system (RTLS) places movers on the hall map at medium precision around 1–3 m (3–10 ft), which is enough for aisle, buffer, and bay decisions. The same feed shows empty travel, dwell, and fleet load under internal logistics optimization. Pull without location still leaves supervisors arguing about who was free. Location without pull still leaves the next job as a radio shout. Most twinzo customers run both layers together. This page is the joint impact, not a repeat of either alone.
What documented pull removes
On a documented 30,000 m² (about 323,000 ft²) automotive Tier-2 hall, moving from push phone traffic to pull cut operator-to-driver calls by about 90% and eliminated over 95% of forklift patrolling. Those numbers measure coordination load once jobs no longer live only on the radio. Voice-only framing sits under phone calls still coordinate most internal moves.
On a documented 55,000 m² (about 592,000 ft²) white-goods plant, the same class of AOS change cut unnecessary patrolling by about 95%, recovered about +20 minutes of production every day, eliminated line micro-stoppages tied to late material, and recorded €5,080,000 (about $5,588,000) increased production value in year one against €100,000 (about $110,000) invested. That figure is production uplift from recovered line time. Keep it on that plant class. Depth on those minutes sits under twenty minutes of production back every day.
What documented path adds after jobs are claimable
Pull stops purposeless circulating between calls. Path proves residual empty share, shift imbalance, and whether another lease is still justified. Industry practice treats empty runs and low productive utilization as common drains on fleet spend once motion is measured. Plants that cannot see loaded versus empty share tend to oversize the fleet because busy-looking trucks still fail to protect the line.
On a documented 30,000 m² (about 323,000 ft²) Tier-2 RTLS deployment, the fleet fell from 36 to 20 forklifts and drivers from 108 to 60, with €120,000 (about $132,000) invested and €960,000 (about $1,056,000) first-year OPEX saved. On a second Tier-2 RTLS case in the same size band, productivity rose from 63% to 75%, two forklifts and four FTEs left the roster, and €81,000 (about $89,100) returned €179,000 (about $196,900) OPEX in year one. Daily reports included spaghetti diagrams and continuous forklift tracking instead of a stopwatch sample. Fleet-cut framing sits under when buying more forklifts is the wrong first answer. Productivity framing sits under forklift productivity from 63% to 75%.
Why demand and location belong in one stack
Classic FGS and dynamic dispatch stacks reduce empty runs by pairing transport demand with vehicle location for the same reason: task assignment and path waste are one material-flow problem. A clean claim queue without place still hides residual empty returns. A live map without claimable jobs still leaves dispatch on the radio. Lean manufacturing already names waiting and unnecessary motion as waste. The joint stack makes both measurable on the same hall instead of hunting them in separate meetings.
When claimable jobs and live paths share one frame, industrial fleet management stops guessing which trucks are free and which corridors stay empty. Putting demand and location in one stack is a practical smart manufacturing move because they stop living in separate apps. Capability depth for both modules sits on the features overview. How a rollout is priced is on pricing.
One hall, three equal readers
When acceptance trails and positions land on the same map, the plant builds a spatially oriented dataset, the plant form of spatiotemporal data. Live logistics owns search, fleet load, and residual empty corridors. Continuous improvement owns layout and sequence updates from that same place-and-time history. Correlation and causality analytics owns which request gaps and empty pairings keep preceding a starve. Those three jobs stay equal. A stack that only celebrates fewer phone calls or fewer leased trucks still leaves the stored record and the root-cause work unfinished.
Production waits recovered under pull still need hall context under production monitoring. An operational digital twin is the shared frame when claimable jobs and live paths are meant to outlast a single Kaizen week.
How teams decide both layers belong
1. Measure calls and empty patrol share on one peak loop - High numbers point to pull first.
2. Measure empty travel and fleet saturation after pull stabilizes - Residual waste points to RTLS analytics on the same hall.
3. Attribute euros to the case that earned them - Do not paste white-goods production uplift onto a Tier-2 fleet cut, or the reverse.
4. Keep logistics, continuous improvement, and analytics on the same review - Live operations, the spatially oriented dataset, and correlation work are equal readers of the joint record.
Get in touch if you want to walk a joint pull-and-path pilot on one high-traffic hall before treating either module as the whole answer.