An ERP manages the customer order, releases the production order, triggers procurement. But between the moment a production order leaves the ERP and when the finished product comes back as a closure confirmation, hours or entire days pass in a blind spot. That is where the Manufacturing Execution System (MES) operates.
Every operations director at a mid-sized industrial company faces the same question: should you use the native production module in your existing ERP (SAP PP, Dynamics 365 Manufacturing, Infor LN Production), or invest in a dedicated MES? The answer differs depending on whether you run a food processing plant with 40 active recipes or a discrete assembly line with 2 product variants.
This guide compares the leading MES solutions in 2026 — both ERP-integrated and standalone — and offers an actionable decision framework for choosing between them.
Why the ERP vs MES debate is back in 2026
The promise of “all-in-one” ERP for production
ERP vendors have massively expanded their production modules over the past five years. SAP S/4HANA now includes SAP Digital Manufacturing (formerly SAP ME/MII). Infor CloudSuite Manufacturing ships with a native MOM (Manufacturing Operations Management) module. Dynamics 365 Supply Chain Management offers production tracking connected to Azure IoT Hub.
These ERP modules cover the most common use cases: production order tracking, operation-by-operation reporting, aggregate OEE calculation, lot traceability. For a plant with stable processes and few variants, this is often sufficient.
The limits of native ERP production modules
The problem surfaces as complexity grows. An ERP thinks in transactions: it records that an operation started, when it ended, and how much was produced. A specialised MES thinks in real-time shop floor terms: it knows that machine 4 has been in a micro-stoppage for 7 minutes, that the operator flagged a non-conformance on lot 2847-B, and that the next operation’s queue will overflow in 22 minutes if nothing changes.
This difference in temporal granularity is fundamental. An ERP works in hours or days. A dedicated MES works in seconds and minutes. For complex manufacturing processes — pharmaceutical, fine chemistry, food production with traceable batches, aerospace assembly — this precision is a regulatory or operational requirement, not a luxury.
A second issue: proximity to automation equipment. A standalone MES speaks OPC-UA natively with Siemens, Schneider or Rockwell PLCs. It reads machine data directly without an intermediate middleware layer. Native ERP modules rely on additional integration layers to reach that level of connectivity — which adds latency and fragility.
The MES landscape in 2026 — mapping the players
The global MES market, estimated at $15.9 billion in 2024 and projected to reach $32.4 billion by 2033 according to Business Research Insights (CAGR 7.2%), is structured around two distinct camps.
ERP-integrated MES: SAP Digital Manufacturing
SAP Digital Manufacturing is the successor to SAP ME (Manufacturing Execution) and SAP MII (Manufacturing Integration & Intelligence). Since 2024, SAP has confirmed that ME and MII version 15.5 represents the final release of those products. SAP customers still running ME/MII are in end-of-life territory.
SAP Digital Manufacturing (SAP DM) is a cloud-native solution that integrates directly with SAP S/4HANA via SAP Cloud Integration. It includes a configurable Production Operator Dashboard (POD), native OEE calculation, automated material flow management (Material Flow System) and operator skills tracking. Its positioning: SAP S/4HANA environments looking for application continuity in the cloud, with no break in the data model.
One notable limitation: customisation is more constrained than with the old SAP MII, which was toolkit-oriented. SAP DM is a standardised SaaS solution; integrators who built bespoke MII extensions will need to migrate or rewrite their customisations.
ERP-integrated MES: Infor CloudSuite Manufacturing
Infor CS Manufacturing integrates a MOM module that covers production order management, shop floor sequencing, traceability and quality control without a separate MES. Advantage: a single master data repository, no ERP-MES interface to maintain. Limitation: lower MES functional depth than specialised standalone solutions, particularly for process industries.
Standalone MES Tier 1: Siemens Opcenter Execution
Siemens Opcenter Execution is the successor to Camstar MES, acquired by Siemens in 2014 and rebranded under the Opcenter umbrella. It comes in several industry-specific variants: Opcenter Execution Discrete (electronics, aerospace, industrial equipment), Opcenter Execution Process (chemicals, pharma, food & beverage), Opcenter Execution Semiconductor.
Key strength: native integration in the Siemens ecosystem (NX, Teamcenter) and digital twin capabilities via Siemens Xcelerator. Opcenter Execution relies on OPC-UA for connectivity to Siemens S7 and third-party PLCs. In 2026, it is among the solutions featured in the Gartner Market Guide for Manufacturing Execution Systems for manufacturers with complex processes.
Do not confuse it with Siemens Opcenter Intelligence (formerly Preactor), which is an APS (Advanced Planning & Scheduling) tool. The former executes production in real time; the latter optimises the production schedule. These two tools are complementary, not interchangeable.
Standalone MES Tier 1: Dassault Systèmes DELMIA Apriso
DELMIA Apriso is Dassault Systèmes’ MOM solution, integrated into the 3DEXPERIENCE platform. Its distinguishing strength is multi-site positioning: standardising manufacturing processes across an industrial group, consolidating production data from multiple plants in real time, and centralising quality governance.
DELMIA Apriso covers both discrete and process industries: automotive, aerospace & defence, food & beverage, life sciences, consumer goods. It bundles Production, Quality, Maintenance, Internal Logistics and Workforce Management modules in a single platform. Its competitive advantage: companies already on 3DEXPERIENCE (CATIA, ENOVIA) get a native digital thread from design to production.
Standalone MES Tier 2: Rockwell, Aveva, GE Proficy
Rockwell FactoryTalk Production Centre, Aveva MES (formerly Wonderware) and GE Proficy Plant Applications complete the picture. These solutions are historically stronger in continuous process industries (petrochemicals, energy, large-scale food manufacturing) than in discrete assembly. They build on proprietary SCADA/DCS installed bases.
The rise of MOM platforms as an ISA-95 abstraction layer
The international ISA-95 standard (IEC/ISO 62264) structures manufacturing systems across 5 levels: levels 0–2 (field and automation), level 3 (MES/MOM), level 4 (ERP). This standard defines the data objects exchanged between ERP and MES, enabling heterogeneous solutions to interface through a stable contract. Emerging MOM platforms (Sight Machine, Critical Manufacturing, Tulip) position themselves as ISA-95 orchestration layers for manufacturers with a historically heterogeneous application estate.
Comparison table: 6 solutions across 10 criteria
| Criterion | SAP Digital Manufacturing | Infor CS Mfg (native MOM) | Siemens Opcenter Exec. | DELMIA Apriso | Rockwell FactoryTalk | Aveva MES |
|---|---|---|---|---|---|---|
| Shop floor real-time | Minutes (cloud) | Minutes | Seconds | Seconds | Seconds | Seconds |
| Native ERP integration | SAP S/4HANA | Infor only | Multi-ERP | Multi-ERP (3DS) | Multi-ERP | Multi-ERP |
| Native OPC-UA support | Via connector | Partial | Yes (native) | Yes | Yes | Yes |
| Target industries | All (SAP shops) | Heavy industry | Discrete, process, semi | Discrete, process, multi-site | Continuous process | Continuous process, discrete |
| SaaS deployment | Yes (cloud-first) | Yes (cloud) | Yes (Xcelerator) | Yes (3DEXPERIENCE) | Partial | Yes |
| Estimated project cost | €150–500K | €200–600K | €300K–1.5M | €400K–2M | €200–800K | €200–800K |
| EU/Global support | Yes | Yes | Yes | Yes | Yes | Yes |
| 21 CFR Part 11 certified | Yes | Yes | Yes | Yes | Yes | Yes |
| Native AI/ML | Yes (SAP Analytics) | Limited | Opcenter Intelligence | Yes (3DEXPERIENCE) | Limited | In progress |
| Deployment complexity | Medium | Medium | High | High | Medium | Medium |
Indicative ranges depending on functional scope, number of lines and ERP integration depth.
When the ERP module is enough — 4 profiles
Profile 1: SME with fewer than 200 employees and stable, low-variant processes
An SME manufacturing 15 product references with stable routing operations, on 2 or 3 production lines, does not need a standalone MES. Its ERP production module (Sage 200, Dynamics 365 SCM, Odoo) covers the requirements: production order release, operation-by-operation reporting, batch management, actual cost calculation. A minimum €300K Tier 1 MES project would be disproportionate.
Profile 2: Single site already running a well-configured SAP S/4HANA
If the company runs SAP S/4HANA with a well-parameterised PP module, migrating to SAP Digital Manufacturing is a natural evolution within the SAP ecosystem. Production data, bills of materials, routings and work centres stay in the S/4HANA master data model. SAP DM adds the shop floor execution layer in real time without introducing a technological break.
Profile 3: Simple discrete manufacturing — manual assembly without mandatory serial traceability
A manual assembly workshop with no mandatory serial-level traceability, no critical process parameters to record, and no FDA or EMA qualification required: the added value of a standalone MES remains low. ERP production reporting is sufficient, complemented optionally by lightweight collection tools (tablets, barcode scanners connected directly to the ERP).
Profile 4: Short budget constraint (< €500K for the full project)
A Tier 1 standalone MES costs at a minimum €200–300K in licences, plus ERP integration, training and go-live. Below a €500K total project budget, the ROI of a dedicated MES is hard to justify. The native ERP module, augmented with targeted custom developments, is a more reasonable alternative.
When to invest in a standalone MES — 4 profiles
Profile 1: Process industry with traceable batches and strict regulation
Pharmaceutical (GMP, 21 CFR Part 11, GAMP5), fine chemistry, food & beverage (IFS, BRC, FSSC 22000): these sectors require exhaustive batch-level traceability, real-time process parameter management (temperature, pressure, pH), inline quality controls integrated into the production workflow, and an audit trail capability that meets regulatory inspections. No native ERP module covers this scope at this depth. A standalone MES such as Siemens Opcenter Execution Process or DELMIA Apriso is the industry standard for these cases.
Profile 2: Multi-line site with high recipe or formula variation
A cosmetics workshop managing 400 active formulas, with component substitutions based on supplier availability and recipe-specific in-process controls, needs a Recipe Management engine that standard ERP modules do not provide. DELMIA Apriso and Siemens Opcenter Execution Process embed this kind of engine, which can be validated in line with GAMP5 good practice guidelines.
Profile 3: Mandatory real-time serial-level traceability
Aerospace (AS 9100), automotive (IATF 16949), defence: traceability must go down to serial number level. Which component, which material batch, which operator, which tooling, which operation sequence for each serial number produced. This requirement is incompatible with batch declaration in the ERP. It requires real-time collection at every operation, linked to the serial number and stored in an auditable system. A standalone MES is the industry standard for these use cases.
Profile 4: Multi-site industrial group requiring central production consolidation
An industrial group with four plants across the UK, Germany, Poland and Spain wanting to standardise its manufacturing processes, consolidate OEE metrics in real time on a group dashboard, and roll out the same production best practices across all sites: DELMIA Apriso and Siemens Opcenter were designed for this use case. Multi-site governance is their primary differentiator versus native ERP modules, which struggle to aggregate heterogeneous production data in real time.
Hybrid architecture: ERP core + MES connected via OPC-UA and REST API
ISA-95 as the interface standard
In a hybrid architecture, the ERP remains the system of record: master of items, bills of materials, routings, production orders, and costs. The MES is the execution system: shop floor real time, machine data collection, quality control management. Exchanges between the two levels follow the ISA-95 Level 3–4 model.
Objects flow down from the ERP to the MES: production orders, manufacturing bills of materials (mBOM), operation routings, quality specifications, production priorities. They flow back up from the MES to the ERP: operation confirmations, quantities produced, scrap, actual material consumption, quality control results. The frequency of these exchanges — from a few seconds to a few minutes — is agreed during integration design.
ERP–MES middleware examples
SAP S/4HANA + third-party MES: SAP Integration Suite publishes standardised REST APIs for production data exchange. Third-party MES solutions (Siemens Opcenter, DELMIA Apriso) have SAP-certified connectors for this scope.
Microsoft Dynamics 365 + Azure IoT Hub: machine data flows through Azure IoT Hub, is transformed in Azure Event Hubs and feeds both the Dynamics 365 Manufacturing Execution module and Power BI shop floor dashboards. This is the recommended architecture for manufacturers in the Microsoft ecosystem who do not have the complexity to justify a Tier 1 standalone MES.
OPC-UA as the universal protocol: OPC-UA has become the Industry 4.0 communication standard between PLCs, SCADA, MES and ERP. All Tier 1 MES solutions mentioned in this guide support OPC-UA natively. For the full technical architecture of this connectivity, see our guide ERP and IIoT: connecting your shop floor in real time via OPC-UA and MQTT.
Budget, typical ROI and real-world results
Cost ranges by MES type
A Tier 1 standalone MES project represents a significant investment:
- Software licences: €100–500K depending on the number of lines, modules and deployment model (cloud or on-premises)
- ERP integration: €80–300K for connector development and interface testing
- Training and change management: €20–80K depending on site size and operator digital maturity
- Total project: €200K (limited scope, single plant, core modules) to over €1.5M (multi-site group, full module suite, complex ERP integration)
For an ERP-integrated MES (SAP Digital Manufacturing, Infor MOM module), the licence cost is often included in the global ERP contract or billed as a modest add-on. The main saving is on integration: zero ERP–MES interface to design and maintain. The trade-off is reduced functional customisation.
Typical ROI and measured benefits
Field studies document consistent gains after MES deployment. According to an analysis by Industry EMEA consolidating multiple industrial cases:
- Production efficiency improvement: 10 to 20% on average
- Scrap rate reduction: up to 40%
- Inventory cost reduction: up to 30%
- Compliance cost reduction: up to 50% in regulated sectors
A Tier 1 automotive supplier recorded a 15% increase in production efficiency and a 25% reduction in defect rates in its first year after MES deployment. An electronics manufacturer reduced scrap by 20% and improved OEE by 12% following go-live.
These figures vary considerably depending on the site’s initial digital maturity. A workshop that was still reporting production manually on paper will see far greater gains than a site that was already partially automated.
The 3 most common deployment mistakes
1. Too broad a scope at launch. Trying to deploy the MES across all lines with every module (production, quality, maintenance, WMS) in a single wave is the classic mistake. A phased deployment — one pilot line, a scope of 3 to 5 operations — allows ERP interfaces to be validated, operators to be trained, and early results measured before scaling.
2. Incomplete master data in the ERP. The MES depends on the quality of routing operations, bills of materials and standard times in the ERP. If these data are incomplete or incorrect, the MES cannot sequence correctly. Updating ERP master data is a non-negotiable prerequisite, consistently underestimated in project timelines.
3. ERP interface not load-tested. The ERP–MES integration may work fine in testing with 10 production orders. It can generate errors or timeouts in production with 200 concurrent orders. Load testing the ERP–MES interface with volumes representative of actual production must be part of the acceptance plan before go-live.
For broader manufacturing context, read our manufacturing ERP guide: MES, IoT and Industry 4.0 and our article on ERP–PLM integration and the industrial digital thread.
