What These Systems Actually Do
Each one has a distinct job, a distinct time horizon, and a distinct owner.
An enterprise resource planning system, or ERP, manages the business of manufacturing. It holds demand signals, bills of materials, purchase orders, inventory balances, financials, and standard operating procedures. Much of its functionality is prompted by financial transactions such as sales orders and supplier invoices. Its planning horizon can stretch from hours to years.
A manufacturing execution system, or MES, orchestrates actual production in real time. It manages work orders, operator assignments, material delivery to the line, equipment performance, and work-in-progress status.
A warehouse management system, or WMS, tracks receipts, putaway, picks, transfers, and shipments. Its records reflect what is physically present and where.
ISA-95, the international standard for the integration of enterprise and control systems, has defined the relationship between ERP and MES since the 1990s. MOM software bridges enterprise-level ERP information to the automation and control systems on the manufacturing floor.
How Data Moves Between Them
Data shared between ERP and MES flows in both directions. The MES sends back order status, actual material and labor consumption, scrap, completions, and machine throughput.
AWS prescriptive guidance on MES architecture describes this boundary directly. MES sits at the edge of operational technology and information technology. Depending on the organizational solution landscape, MES can interact with ERP to get production and purchase order information, master data about parts and products, inventory availability, and bill of materials.
MES would also report back to ERP for the status of orders, actual material and labor consumption during production, and machine status.
When a product lifecycle management system, or PLM, is present, the interface extends further. MES can interact with PLM to get a detailed bill of process, work instructions, and in some cases the bill of materials. MES would also report to PLM about process execution information, non-conformances, and BOM variations.
Material receipts feed into production readiness. Finished goods completions from the MES update inventory positions. Shipment confirmations close the fulfillment record in the ERP.
The Ownership and Governance Questions
Who owns the production order record? The ERP creates it. When the two versions diverge, which one governs?
Who owns the inventory record? When they disagree, who reconciles them and on what schedule?
Who owns the quality record? If that record does not reach the WMS before a pick is released, a shipment can go out against a held lot.
NIST's work on supply chain traceability addresses a related design principle. Granular internal data managed by ERP, MES, and QMS is typically not shared with external parties. Organizations can selectively extract and transform internal activities into shareable supply chain event data, filtering out proprietary manufacturing details to protect intellectual property. The distinction between what stays internal and what crosses a boundary is a governance decision, not a default system behavior.
Individual traceability records should be structured to support supply chain risk management decisions, including procurement requirements and regulatory obligations.
What Breaks Without Governed Connections
Manufacturing companies that successfully integrate their ERP and MES systems can achieve benefits including increased overall equipment efficiency, reduced cycle times, reduced data entry, data consistency, leaner manufacturing, and more on-time delivery, among others. The inverse is also true. When the connection is ungoverned, specific failure modes follow.
A quality hold entered in the QMS may not block a WMS pick in time.
These are not system failures. They are ownership and interface failures. The systems are doing what they were configured to do. The gap is in the definition of which record is authoritative, who updates it, and when the update must cross the boundary.
The design for the MES-to-enterprise interface varies based on the systems MES interacts with. There is no single correct architecture. The right design depends on which systems are present, which records each one owns, and which events need to cross which boundaries in near real time versus on a schedule.
Controls to Establish Before Connecting Systems
The reader decision here is practical: which data ownership and integration controls belong in place before the interfaces are built?
Start with record authority. Document that ownership before designing the interface.
Define the crossing events. Not every update needs to cross every boundary in real time. Identify which events require near-real-time exchange and which can tolerate a scheduled transfer. A quality hold that affects a live shipment needs a different latency requirement than a monthly cost variance report.
Set reconciliation rules. When two systems hold the same record, define how and when they reconcile. Who initiates the reconciliation? Who resolves a discrepancy? What is the escalation path when the systems disagree?
Control what crosses the external boundary. Internal operational data and shareable supply chain event data are different things. Define which records can be shared with suppliers, partners, or customers, and under what conditions.
Monitor the interfaces. An integration that runs without monitoring is an undetected failure waiting to surface. Define what a healthy interface looks like, what a failed transfer looks like, and who is responsible for recovery.
Integration of MES and ERP systems enables their complementary functionality to bring greater benefit to a manufacturer than siloed systems. That benefit depends on the governance underneath the connection, not on the connection itself.