Work Order Management in Manufacturing: MES Guide 2026

What is work order management in manufacturing?

Work order management — German Fertigungsauftragsverwaltung or Auftragsmanagement — is the process of creating, releasing, executing, tracking and confirming production work orders across the ERP, MES and machine layers. It covers the full life cycle: a commercial order becomes a planned work order in the ERP, is released to the MES, executed at the machine, and confirmed back with actual quantities, times and reasons.

The textbook definition is easy. The practice is not. In 30+ years of connecting machines to higher-level systems — from Simatic S5 and COROS visualisations in 1991 to OPC UA and cloud MES today — the hard part of work order management has never been the order itself. It has been the return path: getting reliable, timestamped confirmations from a mixed machine park back into the ERP, without manual Excel sheets, without end-of-shift reconciliation, and without touching the PLC program of a 1995 press.

Production work orders vs. maintenance work orders

The term "work order" is used in two different worlds, and conflating them causes procurement mistakes. A production work order is a manufacturing instruction — make part X, quantity Y, on machine Z. A maintenance work order is a service instruction — inspect, repair, or replace on equipment Z. Both can be digitised, but they live in different systems and follow different logic.

This article focuses on production work orders. Maintenance work orders are covered separately under CMMS and TPM.

How a production work order flows through ERP, MES and the machine

The life cycle is the same in every discrete and batch plant I have implemented in, whether the ERP is SAP R/3 with IDoc, InforCOM with file interface, or Navision with REST. What differs is only the adapter. The steps themselves are:

1. Creation in the ERP. A sales order or planning run generates a work order with BOM, routing, target quantity and due date.
2. Release to MES. Once the material is committed and the start date is reached, the ERP releases the order. The MES receives the order header, operations, material list and machine assignment.
3. Dispatch to the shop floor. The MES shows the order on the shop-floor client at the right machine. Setup sheets, drawings and work instructions are delivered digitally at the workstation.
4. Setup and first piece. The operator confirms setup, runs a first piece, triggers first-piece approval. The order status moves to "in production".
5. Execution with automatic data capture. The MES maps every machine cycle to the active work order. Cycles, stops, reasons, scrap and quality events are timestamped in real time — no manual counting.
6. Confirmation back to the ERP. Quantities, setup time, run time, stop time and reasons flow back automatically. The ERP sees actuals, not estimates.
7. Closure. The order is closed in the MES when the target quantity is produced or released early; post-calculation is done against real data.

The hard part: mapping machine cycles to the correct work order

Everyone demos step 7. Almost nobody demos steps 4 and 5 honestly. The real engineering problem in work order management is making sure that every good part, every scrap part and every stop gets attributed to the order that actually produced it — on a mixed machine park, across shift changes, across setup periods, and across operators who forget to log out.

Three concrete failure modes show up repeatedly:

• Orphan cycles. The machine runs before an order is logged on, or after it is logged off. Those cycles land nowhere, quantities drift, the ERP sees fewer parts than the machine produced.
• Wrong-order attribution. Operator forgets to end order A before starting order B. Cycles of B land under A. Cost accounting is wrong for both.
• Setup counted as production. Trial runs during setup get counted as good parts. Target quantity is met on paper, short on the pallet.

The fix is not discipline. The fix is architecture: automatic order context at the machine (barcode, RFID, operator login tied to machine ID), first-piece approval gating, and machine-state detection so that setup cycles are separated from production cycles in the MES, not at the end of shift by hand.

Hard-earned lesson from 30+ years of machine-to-MES integration: at a metalworking customer we connected a press line running three shifts. The ERP-side numbers and the machine-side numbers disagreed by about 6 %. Everyone assumed a data bug. It was not. The machine was producing for roughly 40 minutes each morning before the day shift formally "started" the order — the morning setter ran parts to warm the dies. Those parts were good, went to the customer, but were never attributed to any order in the ERP. The fix was not a report. The fix was a rule at the gateway: if the machine is producing and no order is active, hold the cycles in a buffer and assign them to the next order started on that machine, with a flag for review. Lesson: work order management is not about capturing data at the MES. It is about making sure every machine cycle has a home, even when humans forget.

What MES adds to a work order that an ERP alone cannot deliver

Every ERP already has a work order module. The question is not whether the ERP can store work orders — it can. The question is whether the ERP can execute and confirm them without a layer in between. In any plant with more than a handful of machines, the answer is no.

The MES delivers four things the ERP cannot: real-time order status at the machine (not at end-of-shift), automatic cycle-to-order mapping via PLC signal and operator context, stop-and-scrap capture with reason codes while they happen, and bidirectional confirmation that lets post-calculation run on actuals instead of estimates. The result is a work order that closes with real numbers — not numbers reconstructed from shift logs.

What work order management looks like in the SYMESTIC deployment pattern

Schmiedetechnik Plettenberg is the textbook case. ERP is InforCOM. Work order release, routings and master data flow from InforCOM into SYMESTIC via a dedicated interface. On the shop floor, operators see the order on digital clients; cycles, stops and quality events are mapped automatically to the active order. Quantities, times, stop durations and status flow back to InforCOM — no parallel Excel, no manual reconciliation. Meleghy runs the same architecture against SAP R/3 across six plants with ABAP IDoc: machine cycles mapped to production orders, confirmations written back bidirectionally, result 10 % less downtime and 7 % more output in six months. Klocke, in a GMP-regulated packaging environment at Weingarten, pulls order status and master data from Navision via a file interface and maps machine cycles and stops to work orders across the whole site.

The common thread is not the ERP. It is the discipline of closing the loop automatically — order in, cycles mapped, confirmations back — so the ERP sees production reality instead of a reconstruction.

FAQ

What is a work order in manufacturing?
A production work order is a formal instruction to manufacture a defined quantity of a specific part, using a defined routing, on a defined machine, by a defined date. It is created in the ERP from a customer order or planning run, released to the MES for execution, and closed once the quantity is produced and confirmed back.

What is the difference between a production work order and a maintenance work order?
A production work order instructs the manufacture of a part; it lives in the ERP and is executed through the MES against a machine. A maintenance work order instructs the service, repair or inspection of equipment; it lives in a CMMS or the maintenance module of an MES. Both are digitised work orders, but they follow different systems, triggers and data requirements.

Why do ERP and shop-floor numbers not match?
Almost always because cycle-to-order mapping is manual or incomplete. Typical causes: operators start or end orders late, setup cycles are counted as production, scrap is not logged, or the machine runs without an active order (e.g. trial parts during setup). Automatic machine-signal capture combined with rule-based order attribution closes the gap.

Do I need an MES for work order management, or is ERP enough?
ERP alone works for small, stable shops with few orders per day. For anything larger — multi-shift, mixed product mix, automatic equipment — the ERP cannot see the shop floor fast enough. You need an MES to execute, track and confirm work orders in real time, and to feed actuals back to the ERP. Without that layer, post-calculation is done in Excel.

How are work orders dispatched to operators?
Through a shop-floor client at each workstation. The MES shows the active order, the target quantity, the routing step, the setup instructions and any linked documents. Operators log on via barcode, RFID or login, and first-piece approval gates the release to full production. No paper, no printed travellers that go missing.

Can work orders be tracked on brownfield machines without modern controls?
Yes. Digital I/O gateways tap existing machine signals — cycle, stop, good/bad — without any PLC change. The gateway forwards the signals to the MES, which combines them with operator and order context to map cycles to the active order. Most machines built since 1990 can be connected within hours; even older ones are usually solvable with a relay module and a little engineering.

What is the difference between a work order and a production order?
In most ERP and MES contexts the two terms are used interchangeably. Some ERPs (SAP in particular) formally distinguish "planned order" (a suggestion from MRP) from "production order" or "process order" (the released, executable object). The work order in MES terminology corresponds to the released production order in the ERP.

How does SYMESTIC handle work order management?
SYMESTIC integrates bidirectionally with the ERP — SAP R/3 via ABAP IDoc, Infor and InforCOM, Microsoft Dynamics and Navision, proAlpha and others via REST or file interface. Work orders and master data flow in; cycles, stops, reasons and quantities flow back automatically, mapped to the active order. See production control and production planning, and the ISA-95 reference for the integration pattern (ISA-95).

Related: MES: Definition, functions & benefits · OEE: Definition, calculation & practice · Make to Order · Machine data collection (MDE) · Production data collection (BDE) · Digital workflow · ISA-95 · CMMS · Production control module · Production planning module.

About the author

Martin Brandel

MES Consultant and Project Lead at SYMESTIC. 30+ years in industrial automation — connecting machines to higher-level systems since 1991 (Simatic S5, COROS visualisation, warehouse and material-flow control). Former Head of Automation at ODEVIS/SYMESTIC (11 years), large-scale automation projects in Eastern Europe and China at Hermos AG (paint lines, conveyors, process technology). Dipl.-Ing. Nachrichtentechnik. Expertise: MDE/BDE, machine connectivity, Simatic S5/S7/TIA, retrofit, OPC UA, IoT gateway integration, brownfield connection, process control, MES project delivery. · LinkedIn