Production orders should usually be created in the ERP or MRP system, not directly in the MES, when “production order” means the formal manufacturing order that commits demand, material, costing, and planning records. The MES should normally receive the released order and control execution against it on the shop floor. Exceptions are possible, but they need explicit governance because they affect traceability, inventory, cost, and quality records.
Common ownership model
In a typical regulated manufacturing environment, system ownership is split for a reason:
- ERP or MRP usually owns planned and released production orders, material demand, inventory reservations, costing, order status, and financial closure.
- PLM usually owns engineering definition, product structure, approved revisions, and sometimes manufacturing process planning inputs. It should not normally create live production orders.
- MES usually owns execution: dispatching work, enforcing routings and work instructions, collecting labor and machine data, recording genealogy, capturing inspections, and managing shop-floor holds or deviations.
- QMS usually owns nonconformance, MRB, CAPA, and quality disposition workflows. It may authorize rework or repair activity, but that does not automatically mean it should create the production order.
- EAM or CMMS owns maintenance work orders, not production orders, unless the site has deliberately combined those processes for MRO or overhaul work.
What MES can create
MES can often create execution-level records derived from an ERP order. Examples include dispatch records, operation instances, serial-specific travelers, sublots, split quantities, operator assignments, electronic batch or device history records, and local rework steps.
Those records should remain traceable to the formal production order unless the site has a validated alternative model. If the MES creates records that behave like independent production orders, the integration must reconcile demand, inventory, status, and completion back to ERP. Otherwise, the plant may end up with two systems claiming different versions of the same production reality.
When exceptions may be justified
Some environments do allow production-order-like records to originate outside ERP. This is more common in repair, overhaul, urgent rework, engineering trials, low-volume custom work, or plants with older ERP systems that cannot represent shop-floor reality well.
Those exceptions should be controlled by procedure and system design. The important question is not whether the MES is technically able to create an order. The question is whether the resulting record is controlled for numbering, revision, material allocation, quality status, inventory movement, cost collection, closure, and audit trail.
Common failure modes
Creating production orders in the wrong system can create avoidable risk. Common failure modes include:
- duplicate or hidden demand between ERP and MES;
- inventory reservations that do not match actual shop-floor consumption;
- work released against the wrong part revision, routing, or effectivity;
- quality holds or MRB dispositions bypassed by local workarounds;
- incomplete genealogy or serial traceability;
- labor, material, and cost records that cannot be reconciled at closeout;
- audit trail gaps when order creation, release, changes, and cancellations are not consistently recorded.
Brownfield reality
In brownfield plants, the clean textbook answer is often constrained by legacy ERP, MES, PLM, QMS, spreadsheets, custom middleware, and long-qualified equipment. Full replacement is usually unrealistic in aerospace-grade and similarly regulated operations because of qualification burden, validation cost, downtime risk, integration complexity, traceability obligations, change control, and long asset lifecycles.
The practical approach is usually to define one authoritative system for the formal production order, then integrate the execution layer around it. If a site chooses MES-based order creation, that choice should be deliberate, validated, and reconciled back to ERP rather than treated as a convenient workaround.
Practical rule
Use ERP or MRP to create the formal production order. Use MES to execute, record, and control the work. Allow exceptions only where the process owner, quality, operations, finance, and IT agree on how order identity, revision control, material movement, traceability, status, and closeout will be governed.