How a Floor Request Becomes a Work Order
Material needs on the floor rarely wait for a planned route. An operator at a line station presses a physical button, scans a barcode or RFID tag, taps a touchscreen, or the MES itself fires a signal. Any of those actions creates a work order inside the AOS logistics-management module. Twinzo describes the module as an internal logistics marketplace similar to a ride-sharing app: demand appears, available capacity responds.
The system moves the plant from a push model, where drivers circle or wait for radio calls, to a pull model. The request itself pulls the resource. No dispatcher has to re-key the order. No one has to shout across the aisle. The work order simply appears in the open pool with origin, destination, and task details already attached.
What the Driver Sees and Accepts
Drivers carry devices that show the open work orders. They see where the material is needed, what has to move, and roughly how far the trip is. A driver taps to accept. Once accepted, that order leaves the open list so no second driver can claim it. The acceptance is the marketplace match.
The old pattern of empty patrols and competing radio traffic disappears because the system already knows who is free and who is already loaded. Drivers stop hunting for the next load; the load finds them.
The Data Trail That Starts at Acceptance
The moment a driver accepts, the platform begins recording the full sequence. It logs who requested the movement, which driver took it, the driver’s location at the instant of acceptance, the exact time stamp, the route actually driven, how long the task took, and the distance covered. All of that history stays available for later review by engineers who want to see real material flow instead of assumed routes.
Because the request originated from the station or the MES, the hand-off no longer depends on a phone call. One documented case in a 30,000 sqm automotive Tier-2 plant that moved to this pull approach recorded roughly a 90 percent drop in those operator-to-driver calls and the near-elimination of purposeless forklift patrolling.
Why the Marketplace Changes Daily Floor Rhythm
The mechanical loop is short: trigger creates the order, driver accepts, movement happens, data is captured. Supervisors no longer spend time coordinating by voice. Drivers no longer burn fuel and time looking for work. Engineers gain a continuous record of who moved what, when, and by which path. That record is the practical difference between a push schedule that hopes the right truck is free and a pull marketplace that matches capacity to demand as it appears.
The workflow editor inside AOS lets plants shape the exact steps that sit between trigger and acceptance, but the core sequence stays the same. Button, scan, touchscreen, or MES signal in; driver acceptance out; full movement history retained. That is the ride-sharing analogy applied to internal logistics, executed one work order at a time.