Manufacturing Execution Systems (MES) and Enterprise Resource Planning (ERP) systems address different levels of the manufacturing stack, even when vendors market them as overlapping solutions.
Core purpose
ERP is the business system of record. It focuses on:
- Customer orders, contracts and sales
- Master data (materials, BOMs, routings) and planning
- MRP and capacity planning at a rough-cut level
- Purchasing, inventory valuation and cost accounting
- Finance, invoicing and sometimes HR/timekeeping
MES is the plant-floor execution and traceability layer. It focuses on:
- Dispatching work to specific lines, cells, machines and operators
- Capturing operational data in real time (who/what/when/where/how)
- Enforcing process steps, e-signatures, holds and approvals
- Tracking product genealogy, lot/serial history and as-built vs as-planned
- Integrating with equipment, test stands, tools and data historians
Typical data and workflows
In a regulated manufacturing environment the split usually looks like this:
- ERP: sales order, planned order, planned BOM and routing, purchase orders for materials and outside processing, inventory movements at a summarized level, cost rollups.
- MES: work order execution, operation sequencing, operator assignments, in-process inspections, deviations/nonconformances, detailed material consumption, machine states, and full traceability records.
ERP knows that 10 units of a part were produced and booked to inventory. MES knows which operator, which machine, which lots and serial numbers, which test results, and which approved procedure versions were used to make each unit.
Time horizon and granularity
ERP works in days, weeks and accounting periods. It optimizes capacity and materials at an aggregate level. Data is often posted in batches and backflushed.
MES works in minutes and seconds. It captures every key step in the routing, including holds, rework loops and failures. It is the main source for detailed evidence during audits and investigations.
System-of-record boundaries
For traceable, regulated operations, it is important to define which system is the system of record for each data class:
- ERP as system of record for: customers, vendors, contracts, financial postings, high-level inventory balances, and often the released BOM and routing.
- MES as system of record for: production execution history, as-built configuration, detailed genealogy, electronic batch records, in-process quality results and equipment usage history.
These boundaries are not universal. Some plants hold master routing or certain specifications in PLM or QMS, or run “light MES” features in ERP. When that happens, integration and change control become more complex and must be designed and validated carefully.
Brownfield coexistence and integration
In most established plants, MES and ERP must coexist with legacy systems (homegrown production trackers, spreadsheets, point solutions, LIMS, QMS, SCADA, historians). Full replacement of ERP or MES is rare due to:
- Qualification and validation burden: Any replacement can trigger revalidation of processes, reports and interfaces.
- Downtime risk: Core ERP or MES changes can affect order promising, shipping and shop-floor continuity.
- Integration complexity: ERP and MES typically sit at the center of many interfaces (PLM, QMS, WMS, finance, equipment, portals).
- Asset and process lifecycles: Equipment and certified processes may run for decades; IT systems must adapt without invalidating them.
Because of this, the usual pattern is:
- ERP remains the commercial and planning backbone.
- MES is layered in or upgraded to handle plant execution, traceability and enforcement gaps.
- Interfaces are built so ERP sends orders and master data to MES, and MES returns good/defect quantities, confirmations and sometimes detailed genealogy references.
Where MES and ERP both support similar features (e.g., basic work center dispatching, simple quality screens), plants typically standardize on one system for that function and treat the other as a consumer of summary data to avoid duplication and reconciliation headaches.
Tradeoffs when deciding what to put in MES vs ERP
Key considerations include:
- Regulatory and audit requirements: Detailed execution, signatures and evidence usually belong in MES or a tightly integrated eBR/eDHR solution, not only in ERP.
- Real-time control: If you need step-by-step enforcement and equipment connectivity, ERP alone is rarely sufficient.
- Master data governance: BOMs, routings and item masters are often managed in PLM and synchronized to ERP and MES; duplicating maintenance in both ERP and MES tends to fail over time without strong governance.
- IT ownership and skills: ERP teams and MES/OT teams are often different groups with different change-control cultures; architecture should respect that reality.
- Validation scope: Pushing execution logic into ERP can expand the validated footprint of ERP changes; pushing business rules into MES can expand MES validation. The split should minimize overall validation and regression risk.
Summary
ERP plans, accounts and reports at the business level. MES executes, enforces and records what actually happens on the shop floor. In regulated, long-lifecycle environments they are complementary systems that must be integrated, with clear and documented roles, rather than interchangeable products that one can safely collapse into the other without significant risk and revalidation effort.
