What information should flow between ERP, MES, and an operations platform for work order control?

In regulated and complex manufacturing, effective work order control depends on clear, structured information flow between ERP, MES, and any operations platform that orchestrates shop floor execution. The goal is a closed loop where planning, execution, quality, and completion status stay synchronized.

Typical information from ERP to MES / operations platform

ERP is usually the system of record for commercial demand, planning, and inventory. For work order control it commonly sends:

• Work order header data: order number, product or material number, revision or version, order quantity, priority, required dates, customer or project references.
• Routing and operations: operation sequence, work centers or resources, planned cycle times, setup times, and any special routing variants selected by planning.
• Bill of materials (BOM): component list, quantities, units of measure, substitutes or alternates, and any constrained or serialized components that must be tracked.
• Planning and allocation details: planned start and finish dates, planning status, reserved materials or batches, and links to purchase orders or customer orders.
• Costing and accounting keys: cost centers, order types, WBS or project codes, and other references needed for posting labor and material usage.
• Compliance and traceability flags: indicators that the order is regulated, requires specific traceability depth, or must follow controlled procedures.

Typical information from MES / operations platform back to ERP

MES and operations platforms are usually the systems of record for detailed execution. They provide ERP with the actual results of work orders, including:

• Execution status: order released, in progress, on hold, complete, or cancelled; percentage complete; operation-level status.
• Production quantities: good quantity, scrap or rework quantity, and yield at each key operation or at order close.
• Material consumption: actual component lots or serial numbers consumed, backflushed versus manually issued quantities, and substitutions used.
• Labor and machine time: actual run time, setup time, indirect time where relevant, and resource usage against cost centers or work centers.
• Inventory and movement data: finished goods or intermediates produced, storage locations, and any transfer postings between locations or plants.
• Quality and nonconformance summaries: inspection results, accepted or rejected quantities, holds, and high-level nonconformance or deviation records linked to the order.

Information shared between MES and an operations platform

When MES is focused on core execution and an operations platform provides workflows, work instructions, and operational intelligence, they typically exchange:

• Work context from MES: active work orders, operations, operators assigned, equipment and line context, and current execution state.
• Digital work instructions and content: versioned procedures, checklists, SOP references, and change-controlled instructions applied to specific products, revisions, or operations.
• Task and step-level execution data: completion of checks, sign-offs, parameter entries, measurements, and exception flags that augment MES records.
• Exception handling and escalation: deviation reports, electronic logbook entries, operator comments, and triggers to create nonconformance or CAPA records in MES or quality systems.
• Operational analytics: near real-time KPIs such as OEE components, bottleneck indicators, and adherence to standard work that are fed back to MES or other systems for visibility.

Closed-loop work order control

For robust work order control, the information flow should be bidirectional and consistent:

• ERP drives planning, order creation, and commercial commitments.
• MES manages detailed sequencing, enforcement of routings, and collection of production and quality data.
• Operations platforms orchestrate operator tasks, digital work instructions, and local decision-making, while feeding structured evidence back into MES and ERP.

Aligning identifiers and versions across systems (order numbers, material numbers, revisions, and lot or serial numbers) is critical to maintain traceability and to avoid conflicting records of work order status.