Twinzo Wiki ·

when-pull-and-path-share-one-hall

A plant can kill phone traffic and still leave empty corridors on the map. Another plant can map every truck and still dispatch by radio. The strongest impact stories show up when claimable jobs and live paths share the same hall view.

Two half-fixes that leave money on the floor

Pull without location turns requests into work orders, yet supervisors still argue about who was free and which aisle burned empty kilometres (miles). Location without pull shows spaghetti and dwell, yet the next job still arrives as a shout. Industry stacks that cut empty travel usually combine demand signals with vehicle location for the same reason: task assignment and path waste are one material-flow problem.

twinzo's AOS (commonly known as FGS) owns the claimable loop under material order automation. Logistics RTLS owns the path under internal logistics optimization. Most customers run them in conjunction. This page is the joint impact, not a repeat of either alone.

What pull removes from the shift

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. 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, and recorded €5,080,000 increased production value in year one against €100,000 invested.

Those are coordination and line-time impacts. The voice-only framing sits under phone calls still coordinate most internal moves. Production minutes sit under twenty minutes of production back every day.

What path adds once jobs are claimable

On a documented 30,000 m² (about 323,000 ft²) Tier-2 RTLS deployment, fleet fell from 36 to 20 forklifts and drivers from 108 to 60, with €120,000 invested and €960,000 first-year OPEX saved. On a second Tier-2 RTLS case of the same size band, productivity rose from 63% to 75%, two forklifts and four FTEs left the roster, and €81,000 returned €179,000 OPEX in year one.

Pull stops purposeless circulating between calls. Path proves residual empty share, shift imbalance, and whether another lease is still justified. Fleet-cut framing sits under when buying more forklifts is the wrong first answer. Productivity framing sits under forklift productivity from 63% to 75%.

One hall, one record, three readers

When acceptance trails and positions land on the same map, the plant builds a spatially oriented dataset. Live logistics owns search and fleet load. Continuous improvement owns layout updates. Correlation and causality analytics owns which pairings keep preceding a starve. That equal weight is why the stack outlasts 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.

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 production waits on the same review - Line minutes recovered under pull still need hall context under production monitoring. Capability depth sits on the features overview. Rollout shape is under pricing.

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.