How should ERP and MES share production status?

ERP and MES should share production status through a defined state model, clear system ownership, and controlled event exchange. ERP usually owns the business view of the production order: demand, planned dates, material requirements, costing, inventory movements, and order closure. MES usually owns the execution view: operation start, progress, completion, labor or machine actuals, consumption, scrap, rework, holds, and traceability evidence. The two systems should not freely overwrite each other’s status fields.

The practical rule is simple: ERP should know enough to plan, procure, promise, and account for production. MES should know enough to control and record what actually happened on the shop floor. Trying to make both systems the real-time system of record for the same production state usually creates reconciliation problems, audit ambiguity, and unreliable schedules.

Use events, not vague status synchronization

A durable integration usually exchanges named events with agreed meanings, timestamps, identifiers, and error handling. Common examples include:

• ERP to MES: released production orders, order quantities, part and revision references, routing references, planned dates, approved BOM references, material allocations, and priority changes.
• MES to ERP: order started, operation completed, quantities good or rejected, material consumed, labor or machine actuals, nonconformance flags, rework indicators, production hold status, and completion or receipt readiness.

These events need precise definitions. For example, “operation complete” may mean the operator finished work, inspection passed, all required records were signed, or the ERP backflush can occur. Those are not the same condition in regulated production.

Separate execution status from quality disposition

Production completion should not automatically imply quality acceptance unless that is explicitly defined, validated, and allowed by the site’s process. In many regulated environments, MES can report that an operation is complete while QMS, MRB, or inspection workflows still control whether the item is accepted, rejected, reworked, or held.

This matters because ERP may use status to drive inventory availability, shipment planning, cost collection, or supplier demand. If MES sends a “complete” signal too early, ERP can make material appear available before required evidence, inspection, or disposition is finished.

Define one owner for each status

Good integrations assign ownership at the field or state level. For example, ERP may own whether a work order is planned, firmed, released, closed, or financially settled. MES may own whether the order is queued, in process, paused, held, partially complete, complete at operation level, or awaiting inspection. QMS may own nonconformance disposition and CAPA-related states.

Brownfield environments make this harder. Legacy ERP, older MES modules, PLM revision control, QMS workflows, maintenance systems, and custom spreadsheets often hold overlapping versions of status. Full replacement is usually unrealistic in aerospace-grade and similarly regulated plants because of qualification burden, validation cost, downtime risk, traceability obligations, integration complexity, and long equipment lifecycles. A controlled coexistence model is usually more realistic than declaring a new single source of truth without changing the surrounding process.

Minimum controls for a reliable interface

At minimum, ERP-MES production status sharing should include:

• a documented status model with allowed transitions;
• clear ownership for each status, quantity, and timestamp;
• common identifiers for order, operation, part, revision, lot, serial number, and resource where applicable;
• handling for partial completions, reversals, scrap, rework, split lots, and holds;
• idempotent messages so retries do not double-post completions or consumption;
• interface monitoring, exception queues, and reconciliation reports;
• audit trails showing what changed, when, by whom or by which system;
• change control and validation appropriate to the regulated process.

The failure modes are familiar: ERP shows work as complete while MES still has open operations, MES shows a hold that ERP cannot represent, backflush posts the wrong material revision, partial quantities are rounded or lost, or a retry creates duplicate labor or inventory transactions. These are not edge cases in complex plants. They should be designed for before go-live.

How real-time should it be?

Not every status needs real-time integration. Line-side execution, operator prompts, equipment state, and inspection steps often need near-real-time handling inside MES or adjacent shop-floor systems. ERP may only need milestone events, material movements, and completion signals at agreed points.

More frequent updates can improve visibility, but they also increase interface load, exception volume, validation scope, and operational dependency on integration uptime. The right frequency depends on production tempo, inventory risk, planning needs, batch or serial traceability, and how mature the plant’s data governance is.

The safest design is not “sync everything.” It is to define which system owns each production state, exchange only meaningful status events, preserve traceability, and make reconciliation a normal operating control rather than an afterthought.