Oldest open job vs local preference inside a group
When AOS broadcasts open work to a driver group, claim order has to be a written management rule. It is not a free driver habit, and it is not nearest-truck auto-assignment.
What the shared list forces you to decide
twinzo AOS (commonly known as a forklift guidance system (FGS)) turns a floor material call-off into a claimable work order shown to a configured driver group. Every eligible member sees the same open pool. The first accept wins. Live location does not currently shrink that offer to the nearest truck. Someone still chooses from the list, or rules still rank what appears first. That choice is a management rule the plant has to write down.
Keep the pool inside one order template. Direct forklift pallet brings compete with other direct forklift jobs. Tugger milk-run delivery jobs compete with other prepared trains, not with supermarket prep still unfinished. Mixing templates in one list invents unfair claims that vehicle class should have blocked. The templates are described in milk-run orders vs direct forklift orders. How group broadcast differs from nearest-truck myths is under group broadcast vs nearest-truck myths.
Age-first versus distance-first as single rules
Dispatch studies on forklifts and guided vehicles keep finding the same tradeoff. Distance-first rules cut average empty travel and often cut average wait. They also let remote stops age badly when nearby hops keep winning, especially when vehicle utilization is high. Waiting-time-first and strict oldest-open rules protect the longest wait and raise travel. Multi-attribute rules that blend distance with a wait threshold usually beat either extreme. Plants that never write the rule mix distance-first and age-first failure modes in the same hour and argue about fairness without a shared standard.
That research describes automatic assignment stacks as well as ranked open lists. twinzo AOS today still leaves acceptance inside the group. The same tradeoff applies to how the list is sorted, coached, and audited. A UI that always surfaces the nearest open job recreates distance-first failure modes. A UI that always surfaces the oldest job recreates travel penalties. Priority bands sit above that blend so a true line stop outranks a normal replenishment of any age. Harder priority stacks for busy hours are under priority rules that survive a busy hour.
How plants set the blend without nearest auto-routing
Most halls need a default of oldest-first inside the group for jobs of similar priority, with a short list of priority exceptions for proven or imminent line stops. Local preference is fine when two calls have similar age, or when priority already ranks the nearer job above the older one. Coaching should still stop a long starve from losing to a short convenience hop. Write the age window in training and in how the list is shown, not only as verbal coaching. Configuration for request types and groups sits under request triggers in the workflow editor.
This is a practical lean manufacturing rule for internal logistics: one shared pool, one ranking policy, one acceptance trail. It is also a usable smart manufacturing rule when the open list replaces radio habit. Offer scope stays group broadcast. Location beside the offer can show free capacity on the map at medium precision around 1–3 m (3–10 ft) for aisle and buffer work. It does not currently decide who may see the job. Forklift tracking and broader industrial fleet management still earn their keep as proof of idle trucks, paths, and later pattern work.
Where milk-run slack changes the fair claim
When a milk-run lap is quieter than theoretical consumption, forklift capacity freed by that afternoon may sit near a new call while an older call waits farther away. Local grab looks efficient for that truck and unfair for the hall. Keep the age default inside the forklift group, then let that freed capacity take the next ranked open job. Do not treat proximity as permission to ignore age, and do not dump those pallet jobs into the tugger milk-run delivery list. How that slack should move across lines is under milk runs on theoretical consumption vs dynamic pull across lines.
What acceptance trails prove for later review
A settled claim-order rule does three equal jobs. On the shift it ranks open work so convenience hops do not quietly starve remote waits inside the same group. In storage, acceptance identity, time, and place land in the spatially oriented dataset when movers share the hall frame, including path history and how much of the travel was empty under the live view. For later review, those accepts are what correlation and causality analytics use when newer-before-older claims keep preceding the same line wait. Live logistics, the stored place-and-time record, and pattern work share that trail. How the call starts the record is under the call that starts the record.
Weekly logistics review should sample accepts where a newer equal-priority job beat an older one by more than the written age window. That audit is continuous improvement work on the same dataset, not a separate spreadsheet argument. Production waits on the same hall sit under production monitoring.
How teams decide the claim order is fair
1. Default to oldest open job inside the group for equal priority - Write it into training and into how the list is shown.
2. Allow local preference only when ages are close or priority already ranks the near job - Convenience must not beat a long starve.
3. Review accepts where a newer job beat an older one beyond the age window - Pattern work belongs in weekly logistics review on the stored record.
4. Do not pretend nearest auto-routing fixed fairness - Offer scope is still the group.
Ordering behavior sits under material order automation and internal logistics optimization, with depth on the features overview. Pricing is under pricing.
Get in touch if you want to walk through whether your group lists reward oldest waits, or only the nearest convenience hop.