ERP and MES are complementary, not competing, in most industrial and regulated environments. The distinction is mainly about scope and level of detail.
What ERP does
Enterprise Resource Planning (ERP) systems coordinate the business side of operations across the enterprise. Typical ERP responsibilities include:
- Customer orders, contracts, pricing, and invoicing
- Master data for parts, customers, suppliers, and cost structures
- Material Requirements Planning (MRP) and higher-level capacity planning
- Purchasing, inventory valuation, and warehouse movements
- Finance, general ledger, and cost accounting
- High-level production orders and due dates
ERP answers questions like: “What should we build, by when, for which customer, using what materials, and at what expected cost?” It rarely manages the second-by-second reality of the line or cell.
What MES does
Manufacturing Execution Systems (MES) operate at the plant and line level. They translate ERP-level plans into executable work, and collect detailed production and quality data. Typical MES responsibilities include:
- Dispatching operations to specific lines, machines, or work centers
- Sequencing and scheduling at the shift or hour level
- Operator guidance (e.g., digital work instructions) and data collection
- Enforcing process steps, routings, holds, and approvals
- In-process quality checks and nonconformance capture
- Traceability and genealogy of lots, serial numbers, and components
- Real-time status for WIP, machines, and OEE-related metrics
MES answers questions like: “What is happening right now on the line, what exactly was done to this unit, by whom, using which materials, tools, and parameters?”
How ERP and MES typically work together
In a brownfield, regulated environment, neither ERP nor MES is realistically the single system of record for everything. Coexistence and integration are the norm:
- Order flow: ERP creates production orders based on demand and MRP, then passes them to MES for detailed scheduling and execution.
- Execution feedback: MES reports completions, scrap, rework, and consumption back to ERP so inventory, cost, and delivery promises stay accurate.
- Traceability: MES usually holds the fine-grained genealogy and process history, while ERP may store summary batch/lot info for commercial and logistics use.
- Change control: Engineering changes and master data typically originate in PLM or ERP, and must be synchronized carefully into MES under formal change control.
The quality of this integration strongly affects performance. Poorly integrated ERP/MES setups often result in duplicate data entry, mismatches in BOMs and routings, and gaps in traceability that are problematic in audits.
Why not just use ERP instead of MES (or vice versa)?
Vendors sometimes position ERP or MES as capable of doing “everything.” In high-complexity, regulated manufacturing, there are real constraints:
- ERP as MES: While some ERPs offer shop floor modules, they often lack the depth needed for detailed routing control, enforcement of work instructions, parameter capture, or unit-level genealogy that regulators and customers expect.
- MES as ERP: MES is not designed for financials, taxation, revenue recognition, or multi-plant aggregated planning. Using MES for these roles usually breaks down at scale or under audit.
- Regulatory expectations: For aerospace, medical, defense, and similar sectors, auditors expect clear traceability, validated systems, and consistent master data. Stretching either ERP or MES far beyond its core role increases validation burden and risk.
Full replacement strategies (for example, trying to retire ERP and do everything in MES, or forcing all shop-floor execution to happen only in ERP) often fail because:
- Qualification and validation costs for a single mega-system become very high.
- Downtime needed for cutover is unacceptable on critical assets.
- Integration complexity with existing PLM, QMS, SCADA, historians, and custom tools is underestimated.
- Traceability and change-control requirements are harder to meet in one large, frequently changing platform.
Key tradeoffs when defining ERP vs MES boundaries
In practice, each plant draws the line between ERP and MES slightly differently. Typical boundary decisions include:
- Where MRP lives: Material planning usually stays in ERP, but short-horizon sequencing and dispatch often belong in MES.
- Where WIP is tracked: ERP typically tracks WIP at coarse levels (operation or work center), while MES handles exact units, stations, and timestamps.
- Where quality data lives: MES often stores in-process checks and equipment parameters; QMS or ERP may hold final disposition, complaints, and cost of poor quality summaries.
- How master data is governed: BOMs and routings may be mastered in PLM or ERP, then replicated into MES. Good change control and version governance are critical to avoid divergence.
The “right” split depends on your existing stack, data quality, validation constraints, and the cost of disturbing qualified processes.
Implications for regulated and long-lifecycle operations
For plants with long equipment lifecycles and strict regulation:
- Expect to keep both ERP and MES for many years and evolve interfaces rather than replace core systems outright.
- Any shift of functionality across the ERP/MES boundary should be treated as a controlled change, with impact assessment, re-validation where necessary, and clear migration of historical data and evidence.
- Traceability design should assume that auditors may request cross-system evidence trails that span ERP orders, MES execution records, SCADA/historian data, and QMS cases.
In summary, ERP plans and accounts for the business of manufacturing, while MES executes and records the physical reality on the shop floor. In real plants, they are tightly coupled systems with overlapping edges, not interchangeable platforms.
