Driver Group

A driver group is a configured set of movers or operators who share a claimable pool of internal logistics jobs. In twinzo [AOS](https://www.twinzo.com/glossary/aos-automated-ordering-system) (commonly known as [FGS](https://www.twinzo.com/glossary/forklift-guidance-system)), an open [work order](https://www.twinzo.com/glossary/work-order) is shown to everyone in the assigned group. The first eligible driver who accepts owns the job. Location is recorded at acceptance and along the path when movers are tracked. Location does not currently decide which drivers may see the offer. Plants get the best results when groups follow physical limits: load weight, mast height, attachment, aisle fit, and vehicle class such as [tugger](https://www.twinzo.com/glossary/tugger) milk-run delivery versus direct [forklift](https://www.twinzo.com/glossary/forklift) pallet work. Splits by wing, dock ownership, or "expected" designation often lock quiet capacity away from busy areas. A shared capable fleet balances saturation and absorbs illness, vacation, and staff cuts without starving one territory. How to size those pools is under [how to size and split driver groups](https://www.twinzo.com/wiki/how-to-size-and-split-driver-groups). ## Key Components **Membership**: Which drivers or vehicles belong to the pool. **Capability filter**: Which loads and machines that group can physically handle. **Broadcast offer**: All members see the open work order until one accepts. **Acceptance record**: Who took it, when, and where they stood if tracking is live. ## Applications in Manufacturing and Logistics Internal logistics keeps [milk-run and direct forklift shapes](https://www.twinzo.com/glossary/milk-run-orders-vs-direct-forklift-orders) in separate capable pools, then shares forklift work across the hall so peaks pull capacity from quieter zones. Continuous improvement reviews aged jobs beside idle trucks in the same group. If idle sits next to age inside one capable class, the pool is still too territorial. ## Benefits and Challenges Group broadcast is simple to explain and run. A shared capable pool raises average utilization a bit when headcount drops, while production keeps getting fed. The challenge is resisting org-chart territories that look tidy and create single-point failures. Nearest-truck routing is a different product promise and should not be assumed from live map locations alone. ## Related Terms [AOS](https://www.twinzo.com/glossary/aos-automated-ordering-system), [work order](https://www.twinzo.com/glossary/work-order), [material call-off](https://www.twinzo.com/glossary/material-call-off), [milk-run orders vs direct forklift orders](https://www.twinzo.com/glossary/milk-run-orders-vs-direct-forklift-orders), [RTLS](https://www.twinzo.com/glossary/rtls-real-time-location-system). ## Frequently Asked Questions **Does AOS send the job only to the nearest free truck?** No. It broadcasts to the configured driver group. Anyone in that group can accept. **Why track location at all then?** For acceptance place, path, travel time, empty share, and later pattern work, not for today's offer scope. **Should every hall wing have its own forklift group?** Usually no. Prefer one shared forklift-capable pool unless a physical limit blocks cross-help. Territorial walls leave quiet trucks idle while peaks starve. **Can one driver sit in two groups?** Yes when capability overlaps and operations wants broader claim rights. Avoid territorial double membership that recreates walls.