When MES should open the job vs when the line button should
Some material needs should start from MES, others from a line button at the station. Pick the primary material call-off trigger from who first knows the need, not from which device is easiest to wire.
What each trigger is for
An MES (or another machine signal) should open the logistics job when production software already owns the countdown, kanban quantity, or station state, and can pass material ID, quantity, and destination cleanly. Waiting for a button press in that case only adds delay. A line button, scan, or Andon-style call-for-parts panel should open the job when the need is local, visual, or outside the model: a missing sequenced rack, a damaged cage, a shortfall the system has not measured yet, or a pull that never lived in the BOM backflush.
twinzo AOS (commonly known as a forklift guidance system (FGS)) can turn either source into a claimable work order for a driver group. The management decision is which source may open which job class and which order template. 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 templates without rules creates double calls and wrong-vehicle claims. The templates are under milk-run orders vs direct forklift orders. How those sources map in setup is under request triggers in the workflow editor.
Ownership, primary path, and duplicate merge
Production owns the need. Logistics owns the claim. For each SKU or station loop, name one primary trigger and keep the other as a labeled exception path so drivers do not see two open jobs for the same need. If both fire for the same station and material, merge into one open work order instead of two trucks. MES opens should already carry clean material and destination fields. Human opens should use a template that fills those fields from the button or screen map, not from free text typed under pressure.
That rule is a practical lean manufacturing move for internal logistics: one demand event, one claimable job, one acceptance trail. Offer scope stays group broadcast. Location beside the offer can show free capacity on the map. It does not currently shrink the offer to the nearest truck. How group broadcast differs from nearest-truck myths is under group broadcast vs nearest-truck myths.
Where e-Kanban sits between MES and the button
e-Kanban and digital pull cards often sit between the two. The card flip is a system event that still represents a visual empty. Once the card state flips, that signal can feed AOS the same way a button does, as long as the flip becomes a logistics mission with status and priority, not only a board color. Plants that deduct line-side stock from MES output reporting often create replenishment automatically when stock crosses a reorder point. If scrap and defects are under-reported, the backflush drifts, which is why many halls still keep a physical or labeled exception trigger beside the auto path.
Map each card loop to the right stage and vehicle. A supermarket e-Kanban flip often opens prep first, then tugger milk-run delivery. A station e-Kanban for a pallet-size need usually opens a direct forklift job. Wiring the flip into a claimable order is under e-Kanban cards that become claimable work orders.
Milk runs, theoretical consumption, and rare spikes
A milk run sized to theoretical consumption assumes the line burns at plan and that supermarket prep will feed the tugger train. Industry planning for tugger loops often starts from that average throughput. Real halls usually run slower than plan because of changeovers, micro-stops, quality holds, and thin staffing. In that common case, MES may correctly delay the next auto call while a clock-based tour still arrives with spare capacity elsewhere in the hall. Scrap or defective material that spikes demand is the rare case. For that exception, the button or a quality signal often shows the spike before the consumption average 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.
What a clean trigger choice leaves behind
A settled primary trigger does three equal jobs. On the shift it opens one claimable work order so the need is no longer handled by radio or by two trucks racing the same ask. In storage, acceptance place and path land in the spatially oriented dataset when movers share the hall frame. For later review, closed calls are what correlation and causality analytics use when the same dual-open pattern keeps preceding a wait or empty return. Live logistics, the stored place-and-time record, and pattern work share that trail. How the call starts the record is under the call that starts the record.
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 destination fields at claim time recreate the old radio habit.
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 the wider hall job on internal logistics optimization and 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.