How to size and split driver groups
When you size driver groups, follow what the machine can physically do, not hall territories drawn on a map. Territory splits lock quiet capacity away from busy demand and waste trucks you already own.
What a driver group controls
In twinzo AOS (commonly known as a forklift guidance system / FGS), a driver group is the set of operators who may see and claim a class of work orders. The offer is a broadcast inside that set. First accept wins. Live location does not currently remove farther members from the list. Group design is therefore the main scope control plants have today.
Industry FGS stacks usually gate work by resource group, equipment type, and load-handling class before any distance rule runs. Some products also let plants assign vehicles to control areas. That option exists for hard aisle, safety, or vehicle-fit limits. Using area walls as the default for every capable forklift is a different choice. It keeps quiet trucks from covering peaks elsewhere. The ordering goal for internal logistics is a balanced fleet with almost no production idle from late delivery. Capability is a hard filter, while geography is usually a soft habit that plants keep after radio-era crew maps.
Split on what the machine can do
Best results come from groups based on physical limits: load weight or height that only certain trucks can handle, mast height, attachment type, aisle width that a standard counterbalance cannot enter, and vehicle class that cannot run the same hop, such as milk-run tugger delivery versus direct forklift pallet bring. Those splits protect safety and equipment. They also match how milk-run orders vs direct forklift orders already differ in stage and load unit.
Area walls and paper designations do the opposite. When you limit where a capable forklift may operate, quieter zones cannot cover peaks elsewhere. A longer empty or loaded route is often cheaper than a line stop. Peak coverage without disruption beats short territorial hops that leave half the fleet locked in a quiet wing. How templates bind capability classes is under request triggers in the workflow editor. Offer scope stays group broadcast, not nearest-truck routing, as under group broadcast vs nearest-truck myths.
Shared fleet is the resilience model
The end state is a shared fleet that can claim any job its machine can physically do. Fleet saturation then balances across the hall: busy stations draw free capacity, quiet stations stop sitting on protected idle. Dispatch research on pooled versus dedicated movers shows the same trade-off plants already feel. Sharing raises travel a bit and cuts wait when demand is uneven across zones. When one driver is out for illness, vacation, or a headcount cut, the rest of the capable group absorbs the list. Saturation on the remaining trucks rises. Production still gets fed. Under territorial rules the same missing driver leaves a dead zone. Others could help but the group design forbids it. That single-point failure is what a shared capable group is meant to remove.
Milk runs still keep their own multi-stage path through the supermarket onto tugger trolleys. Direct forklift pallet work stays in forklift-capable groups. Do not merge tugger trains and pallet forks into one claim list. Do merge forklift territories that only exist on the org chart. When milk-run laps run quieter than theoretical consumption, freed people and planning headroom should strengthen the shared forklift pool that can answer real material call-off pull, not draw new walls. That mix is under milk runs on theoretical consumption vs dynamic pull across lines. Fleet load patterns sit under balancing forklift fleet saturation.
What territorial splits cost in the record
Territorial groups create a measurable pattern. Aged open jobs stack in the busy wing while capable trucks sit idle in the quiet wing. Average travel per job may look shorter on paper while waits for late material rise. The ordering goal was never shortest path alone. It was balanced saturation and continuous delivery. That is the same industrial fleet management problem lean manufacturing teams already hunt as uneven utilization: hot movers and cold movers in one capable class.
When movers are tracked at medium precision around 1–3 m (3–10 ft), acceptance place and paths land in the spatially oriented dataset. Live logistics then sees whether free capacity can reach the aged list. Continuous improvement and correlation and causality analytics can ask whether territorial groups still create idle clusters beside aged jobs, or whether the shared pool already moves capacity before the line stops. Those three reads sit on equal footing: shift coverage, the place-and-time record, and the pattern work that later proves which group walls keep preceding waits. Forklift tracking that only feeds a map without that stored trail still leaves the design debate in opinion.
How teams decide group design is healthy
1. Split only on physical limits - Load weight, height, attachment, aisle fit, tugger vs forklift. Not wing ownership.
2. Prefer one shared pool per capable vehicle class - Longer routes that cover peaks beat idle trucks behind a territory line.
3. Stress-test one absence - If one sickness starves a zone while capable trucks elsewhere cannot see the jobs, the group is still territorial.
4. Watch saturation balance and aged jobs together - Hot and cold trucks in the same capable class mean the pool is still too sliced. Uneven crew load on one hall is covered under hot crew quiet crew on the same hall.
Group and workflow setup 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 driver groups still protect territories, or already share a capable fleet so peaks get covered without production idle from late delivery.