When MES should open the job vs when the line button should
The MES already knew the station was about to starve. Nobody pressed the button. The truck sat idle while the countdown ran out on a screen logistics never saw.
Two honest sources of the same need
A line button is the right trigger when the operator sees a shortfall the system does not yet know, a missing sequenced rack, a damaged cage, or a pull that lives outside the model. An MES or other machine signal is the right trigger when the system already owns the countdown, kanban quantity, or station state and waiting for a finger only adds delay and blame.
twinzo AOS (commonly known as FGS) can turn either into a claimable work order for a driver group. The management decision is which source is allowed to open which job class and which ordering shape. A machine signal into a milk-run loop often opens supermarket prep, then tugger delivery. A station button for a pallet swap usually opens a direct forklift job. Mixing sources and shapes without rules creates double calls and wrong-vehicle claims. The shapes are under milk-run orders vs direct forklift orders. How templates map those sources is under request triggers in the workflow editor.
How to choose without fighting over ownership
Production owns the need. Logistics owns the claim. MES should open the job when the event is already structured in production software and the material ID, quantity, and destination can pass cleanly. The button should open the job when the need is local, visual, or exception-based. For the same station, pick one primary path and keep the other as a backup with a clear label so drivers do not see twins. If both fire, merge into one open work order instead of two trucks.
e-Kanban and digital pull cards often sit between the two: a system event that still represents a visual empty. Those can feed AOS the same way a button does once the card state flips. That path is under e-Kanban cards that become claimable work orders. Offer scope stays group broadcast, not nearest-truck routing.
Where milk runs and theoretical consumption mislead the trigger
A milk run sized to theoretical consumption assumes the line burns at plan and that supermarket prep will feed the tugger train. When the line slows, that is the common case, MES may correctly delay the next auto call while the tugger still arrives on the clock with spare capacity elsewhere in the hall. Scrap or defective material that spikes demand is rare. For that exception, the button or a quality signal often knows before the average model does, and the next action is often a direct forklift job, not another trolley on the milk-run sheet. Do not force every SKU onto MES countdown just because a milk-run route exists. Use system triggers where consumption is measured cleanly. Keep human triggers for visual and exception needs. Dynamic pull across that slack is under milk runs on theoretical consumption vs dynamic pull across lines.
A typical double call that burned trust
MES opened a material pull job at low buffer. The operator also mashed the button. Two work orders hit the line-feed group. Two drivers rolled. One returned empty. After the plant made MES primary for that SKU, turned the button into an exception-only template, and suppressed a second open job for the same station and material, the doubles stopped. The group still claimed one job. The record stayed clean for later review in the spatially oriented dataset when paths were stored.
How teams decide the trigger owner
1. Ask who first knows the need for each job class - System countdown versus human eyes.
2. Make one primary trigger per SKU or station loop - Backup must be labeled as exception and must merge duplicates.
3. Require clean material and destination fields from MES - Free-text at claim time recreates radio.
4. Review duplicate opens for two weeks - Doubles mean ownership is still split badly.
Trigger and ordering setup sits under material order automation and production monitoring, with depth on the features overview. Pricing is under pricing.
Get in touch if you want to walk which of your loops should open from MES, and which still need a station button.