The call that starts the record
When a material move starts on radio, no permanent dispatch trail forms. A structured material call-off should open that record from the first ask through acceptance and travel.
What the line-to-driver loop is called
Inside the plant, the job is a structured handoff from the station that needs material to the driver who will move it. That is not a yard management system. Yard tools orchestrate trailers, gates, and dock appointments at the perimeter. Industry names for the same class of system include forklift guidance system (FGS) or forklift control system, material call-off or call-for-parts at the station, and e-Kanban when the pull signal is digital. Vendor pitches often call the same idea Uber for intralogistics: demand appears in a shared pool, free capacity claims it. twinzo's product name for that intralogistics marketplace is AOS (commonly known as FGS).
Classic FGS stacks usually turn ERP or warehouse transport order states into ranked jobs on a terminal. twinzo AOS starts from floor events and holds the same claimable pool idea. Both families beat voice and sticky notes, which never leave a durable trail. The record this page cares about runs from the first ask through acceptance and travel, not only a closed booking stamp.
What the structured call stores first
A material need should enter AOS the moment it exists. Triggers include a station button, a barcode or RFID scan, a touchscreen tap, an e-Kanban flip, or a signal from MES or IoT. AOS turns that need into a claimable work order and holds it open until a driver accepts. From that first action the platform stores who requested and what material or load was asked for.
A radio ask can move a load once, but it does not leave a permanent dispatch entry. In AOS, the structured request itself becomes the first permanent entry in the dispatch trail. Plants that keep internal logistics on voice can move cages and stillages all day without ever proving who asked. How a floor trigger maps into milk-run stages or a direct forklift job is under how a floor request becomes a work order.
Acceptance locks requester, driver, place, and time
When a driver accepts, four facts write together: who needed the material, which driver took the job, the driver's location at acceptance, and the exact timestamp. Those fields stay fixed. Acceptance is the hinge between the ask and the move. After that moment the work order is bound to a named person and a place on the hall, not floating in a radio channel.
Voice coordination loses that hinge every time. Two drivers can both believe they own the same load. Nobody can later prove where the accepted truck stood when the station started waiting. Once those tasks are digital, plants can measure how long a request sat unclaimed and how long it took a driver to accept, the same gap that stays invisible on radio. How voice still runs most halls is under phone calls still coordinate most internal moves.
Path, duration, and distance while the task is open
Once the driver is under way, the same record should keep the path actually driven, the time from acceptance to completion, and the distance covered. The route is not a planned line on a layout drawing. It is the sequence of positions the vehicle occupied while the task stayed open. Medium-precision forklift tracking around 1–3 m (3–10 ft) is usually enough to make that path honest for logistics review. Continuous real-time location system (RTLS) samples turn empty travel versus loaded travel into measured distance, not master-data guesses.
Those samples also feed the spatially oriented dataset under the live hall. Closed calls side by side are what correlation and causality analytics later use when the same wait keeps preceding the same empty loop. Live logistics search, stored spatiotemporal history, and pattern work share that trail on equal footing. How event-driven AOS on tracked movers differs from SAP-state FGS is under AOS on tracked forklifts vs SAP-state forklift guidance.
How teams decide the trail is worth funding
1. Ask whether last week's waits can be reconstructed without radio folklore - If not, the call never started a record.
2. Require the same fields on every finished move - Requester, acceptor, acceptance place and time, path, duration, distance.
3. Keep yard scope off this purchase - Gate and trailer calling stay in yard management. Hall call-off and driver acceptance are AOS / FGS.
4. Connect MES and location feeds after intake is structured - Structured call-off first. Enrichment second.
twinzo's AOS workflows sit under material order automation and internal logistics optimization, with the live hall on the features overview. How a rollout is priced is on pricing.
Get in touch if you want to walk through whether your material moves already start a record in AOS, or still disappear after the load arrives.