Best MES Software in 2026: Compared by Plant-Floor Integration and Deployment Model
Eight MES platforms compared by machine connectivity, ERP integration, cloud vs. on-prem deployment, and what happens when the plant loses its WAN.
An MES rollout rarely fails on its feature list. It stalls at the PLC on one end or at the ERP interface on the other. Every vendor in this guide dispatches work orders, records part history, holds bad product and tracks OEE. The differences that decide a rollout sit at the edges.
I compare eight MES software platforms with four criteria: machine-side connectivity, ERP-side integration, deployment model, and behavior when the plant loses its WAN. The last criterion matters most. A line that keeps running while the MES stops recording turns a network fault into a traceability gap.
Downtime is expensive enough without that gap. Siemens' True Cost of Downtime 2024 report estimates that the Fortune Global 500 lose about $1.4 trillion a year to unplanned downtime. That is 11% of their revenue, up from 8% in 2019.
My recommendation is simple. Choose the deployment type first. Test WAN-loss behavior in a disconnected demo second. Compare features last.
IT Leaders Report 2026
What are your IT peers investing in 2026?
We spoke to about 1,300 IT leaders from various organisations to understand what they're evaluating. Most of it is the kind of thing you'd only hear from a peer you know well enough to ask, so we've put it in one place.
Read the report
What MES software does and where it sits between ERP and the plant floor
MES software is the execution layer of a plant. The ISA-95 standard places it at Level 3, between ERP planning at Level 4 and the control systems at Levels 0 to 2. The ERP decides what to build. The MES releases that work to the floor, records what happens, and enforces the rules while it happens.
A manufacturing execution system does five core jobs:
- Dispatch: release work orders to lines and stations in the correct sequence.
- Part history (genealogy): record which materials, lots and serial numbers went into each unit.
- Quality holds: stop the next operation when a check fails.
- Labor: record who did each step and whether that person had the right qualification.
- Performance: track counts, scrap and OEE against the order.
Siemens' Opcenter reference architecture shows the mechanism well. Its Automation Gateway binds PLC tags to data collection fields on active work order operations. That binding gives a machine value its production context.
OEE and machine-monitoring tools read the same tags but stop there. I call this the dashboard trap: the screen shows downtime, but the tool cannot dispatch, hold or trace. A later section covers when that lighter tier is enough.
How to compare MES vendors: integration and deployment criteria
I judge every MES vendor on the same four criteria. Each one maps to a failure I have seen stall a rollout.
1. Machine-side connectivity. The MES must read PLC counts and states, and sometimes write setpoints. The paths are native drivers, OPC UA, MQTT with Sparkplug B, or a third-party gateway such as Kepware, Litmus or HighByte. Find out which part is a separate product with its own license, patch cycle and owner.
2. ERP-side integration. Orders come down and confirmations go up. The options are a prebuilt connector, ISA-95 messages in the B2MML format, or a custom interface. Ask who maintains the field mapping after the ERP changes.
3. Deployment model. The MES runs at each site, in the cloud with an optional plant edge, or as pure SaaS. This choice sets your upgrade model and your dependence on the WAN.
4. WAN-loss behavior. When the plant loses its link, the MES does one of three things. It keeps executing locally, it queues transactions and forwards them later, or it stops recording while the line keeps running.
The research changed my weighting. Vendor labels now overlap: Plex sells an edge execution product, SAP Digital Manufacturing has an edge runtime, and Critical Manufacturing runs on Kubernetes anywhere. The deployment label tells you less than it did. The fourth criterion, and the product that delivers it, tells you more.
Cloud MES vs. on-prem vs. composable: three MES deployment models
The three deployment models differ in one place: where the transactional record lives during an outage. Everything else follows from that.
Site-installed suites keep the MES database and application servers at or near the plant. Opcenter, AVEVA MES, Proficy and Apriso document Windows servers with SQL Server or Oracle databases. High availability comes from SQL Server clustering or Always On groups. A WAN outage cuts the ERP link and nothing else. These suites fit regulated process plants and 24/7 operations with local IT staff.
Cloud MES tied to an ERP runs as multi-tenant SaaS. The vendor pushes every release. SAP Digital Manufacturing and Plex MES both sell a plant edge layer for continuity, and that layer is a separate deployment. This cloud based manufacturing execution system model fits multi-site discrete manufacturers that already run the same ERP.
Composable platforms split the MES into apps or containers. Tulip is a cloud app platform with no local runtime. Critical Manufacturing ships Kubernetes containers that run anywhere. I found no definition of a composable manufacturing execution system from ISA or MESA, so I treat the label as a vendor term. Judge each composable product by its architecture.
One engineering detail supports the edge pattern. Critical Manufacturing's engineering blog explains that synchronous database replication needs sub-100 millisecond latency between nodes. A plant cannot stretch that across a WAN, so the record of truth must stay close to the line.
The best MES software vendors in 2026
The eight MES software vendors below cover the three deployment types. I checked each one against its own technical documentation. Where a claim appears only on a product page, I mark it vendor states. Where the documentation is silent, I say so.
The gaps are information too. Before you read the profiles, see how much each vendor publishes about the four criteria.
Site-installed suites
Siemens Opcenter Execution: site-installed MES with a separate edge and integration layer
Architecture and deployment. Opcenter Execution comes in Discrete, Process, Pharma, Electronics and Semiconductor editions. It runs on premises or in your own cloud account. AWS publishes reference architectures that include a multi-zone SQL Server design and an AWS Outposts option for on-site hardware. Opcenter X is a separate SaaS line, announced in May 2024 for small and midsize manufacturers.
Machine-side integration. Siemens Industrial Edge supplies connectors for PROFINET, S7, OPC UA, EtherNet/IP and Modbus TCP. The Automation Gateway binds OPC UA nodes to work order data collection.
ERP integration. Opcenter Connect MOM receives SAP work orders through REST or IDoc adapters and returns confirmations.
When the WAN drops. Execution runs at the site, so only the ERP link stops. Connect MOM queues messages and replays them when the network returns. Siemens does not publish the buffer duration.
Best fit. Complex discrete assembly, electronics, and regulated process plants. The Pharma edition is the former SIMATIC IT eBR product.
The catch. Connectivity and queuing live in separate Siemens products. Plan for a multi-product bill of materials and .NET and SQL Server skills.
AVEVA MES: site-installed MES built around AVEVA System Platform
Architecture and deployment. AVEVA MES runs on Windows with SQL Server and a middleware tier. AVEVA supports MES 2020 and MES 2023. A hybrid add-on publishes on-premises MES data to AVEVA CONNECT.
Machine-side integration. AVEVA states that the MES has native integration with AVEVA System Platform, a separate product. The MES documentation I reviewed does not describe its own drivers, OPC UA role or MQTT support.
ERP integration. AVEVA Enterprise Integration, also separate, exchanges plans and results with business systems. An AVEVA product manager names SAP as the most common target. I found no S/4HANA-specific connector.
When the WAN drops. The MES runs on site, so execution continues. AVEVA states that Enterprise Integration keeps operations going when the ERP is offline. That queue covers the ERP side only.
Best fit. AVEVA states batch and hybrid process manufacturing.
The catch. A working deployment usually means three products: MES, System Platform and Enterprise Integration. Scope licenses and skills for all three.
Proficy Plant Applications: process-heavy MES under new ownership
Architecture and deployment. TPG completed its purchase of Proficy from GE Vernova on March 2, 2026, according to GE Vernova's SEC filing. Plant Applications runs on Windows, IIS and SQL Server. The Proficy 2025 release adds a containerized component and a read-only GraphQL connector.
Machine-side integration. An integrator, E Tech Group, describes data collection through OPC and Proficy Historian. Proficy's public docs list no native drivers.
ERP integration. The same integrator describes SAP integration through Proficy Workflow. I found no connector matrix.
When the WAN drops. Execution is local. GE's knowledge base documents SQL Server Always On for version 8.x. Behavior under loss of an enterprise link is not publicly documented.
Best fit. Proficy states process, discrete and mixed manufacturing, including food and beverage.
The catch. A new owner and a pre-2024 compatibility matrix. Get current version support and the lifecycle policy in writing.
DELMIA Apriso: multi-plant MES for process standardization
Architecture and deployment. Apriso runs on premises. The 2021 installation guide lists Windows, IIS and ASP.NET with Oracle or SQL Server. Dassault states that customers run as many as 150 plants on it.
Machine-side integration. The Machine Integrator component handles equipment data and fails over to a secondary server. Supported driver families are not publicly documented.
ERP integration. Business Integrator ships SAP Business Connector, SAP PI, webMethods and BizTalk adapters over SOAP, REST, HTTP, file and MSMQ.
When the WAN drops. The 2021 high-availability guide uses Windows clustering and warns of a minute or two of downtime during failover. Offline work is documented only for an iOS maintenance app. Plant behavior after loss of a central server is not publicly documented.
Best fit. Global multi-plant discrete manufacturers.
The catch. The technical docs I could reach date from 2021. For a central multi-plant design, ask for current HA and WAN guidance before you shortlist.
Cloud MES tied to an ERP
SAP Digital Manufacturing: cloud MES with a documented offline edge
Architecture and deployment. SAP Digital Manufacturing is multi-tenant SaaS on SAP Business Technology Platform, and SAP pushes the releases. An optional edge runtime runs on Kubernetes at the plant. One edge device can serve one plant or several.
Machine-side integration. The Production Connector reads OPC UA servers and connects to MQTT brokers with certificate trust. Sparkplug B is not documented.
ERP integration. S/4HANA and SAP ERP (ECC) both connect over HTTPS through SAP Cloud Integration and the SAP Cloud Connector.
When the WAN drops. SAP's edge setup guide states that the edge caches orders, SFCs and recipes, runs offline transactions, and replays them to the cloud. SAP publishes no maximum offline duration. Without the edge, SAP documents no offline execution.
Best fit. SAP ERP shops, especially plants that leave SAP ME and MII.
The catch. Offline resilience means a Kubernetes edge at every plant. A Production Connector edge also needs a new device registration instead of a reinstall.
Rockwell Automation Plex MES: SaaS MES on the same platform as Plex ERP
Architecture and deployment. Rockwell describes Plex MES as a single-instance, multi-tenant, edge-to-cloud SaaS platform. Plex ERP runs on the same platform.
Machine-side integration. I found no public technical documentation on drivers, OPC UA or MQTT. Ask for the connectivity guide.
ERP integration. With Plex ERP, there is no connector to maintain. Third-party ERP connectors are not publicly documented.
When the WAN drops. Rockwell states that FactoryTalk ResilientEdge, a separate product, gives continuous local execution and syncs with the cloud. Queue size and reconciliation rules are not public.
Best fit. Rockwell states discrete, hybrid and regulated manufacturing.
The catch. Resilience depends on a product with no public admin guide. Get its sync and reconciliation specification before you shortlist a 24/7 plant.
Composable and modular MES
Tulip: composable frontline operations platform with no offline mode
Architecture and deployment. Tulip is multi-tenant cloud on AWS, AWS GovCloud or Azure. Tulip ended its on-premises and private cloud options in April 2022. An optional On-Premise Connector Host runs as a Docker container and connects outbound.
Machine-side integration. OPC UA and MQTT connectors, plus Edge IO and Edge MC devices and Node-RED. Tulip documents no native Rockwell or Siemens PLC driver, so expect Kepware or SCADA in the path. Unified namespace publishing needs Connector Host LTS13 or later.
ERP integration. Generic HTTP and SQL connectors. No prebuilt ERP connector.
When the WAN drops. Tulip documents no offline mode. Its troubleshooting guide states that the platform does not retry a failed connector call.
Best fit. Frontline apps, guided work and quality checks. The e-signature widget supports 21 CFR Part 11 but needs SAML for the two-component rule.
The catch. No local execution path exists. A 24/7 plant must engineer redundant connectivity.
Critical Manufacturing MES: containerized, modular MES on Kubernetes
Architecture and deployment. Critical Manufacturing, an ASMPT subsidiary, ships containers for Kubernetes on premises, hybrid, or in Azure AKS and Amazon EKS. Its DevOps Center deploys them. Production clusters use SQL Server Always On with synchronous commits.
Machine-side integration. Connect IoT is the equipment layer. Its driver list is not in the public docs I reviewed.
ERP integration. Not publicly documented.
When the WAN drops. The v11.3 documentation states that cloud installations have no offline capability. On-premises installs run locally.
Best fit. Semiconductor, electronics and medical device plants.
The catch. Local resilience means you run a Kubernetes cluster in the plant. Budget for platform engineering skills.
MES software comparison table: list of MES software by integration and deployment
The table puts all eight manufacturing execution system vendors on one page. Filter by deployment type, or show only vendors with documented local execution. Every cell comes from the profiles above, so the same caveats apply.
Stress test 1: what happens to your MES when the plant WAN goes down
The WAN-outage test separates these products more clearly than any feature list. Here is the scenario I use. At 10:40 p.m. on second shift, a carrier cuts the plant's fiber. The link stays down for three hours. The line keeps running.
What the MES does next depends on where it executes.
- Site-installed MES. Operators keep dispatching, scanning and holding. Only the ERP link stops. Siemens Connect MOM and AVEVA Enterprise Integration queue the outbound messages and send them when the link returns. The ERP sees stale inventory for three hours, and nothing else breaks.
- Cloud MES with a plant edge. The edge keeps running the orders, SFCs and recipes it cached before the cut. Work released after 10:40 p.m. never reaches the floor. On reconnect, the edge replays its transactions to the cloud, and someone must check for replay failures.
- Cloud MES with no local runtime. The operator screens stop. The line runs on paper for three hours. Every serial number, lot and check from that window needs manual entry the next morning.
In a regulated plant, a three-hour genealogy gap becomes a deviation report. In an automotive plant, it can mean a containment action on every unit built in that window.
The cost of a stopped line keeps climbing. Siemens reports that one hour of downtime in a large automotive plant now costs $2.3 million. That is more than $600 a second.
Stress test 2: manufacturing execution system and ERP migration
Plants on SAP ECC face an ERP change under a live MES before 2031. SAP's maintenance strategy ends mainstream maintenance for SAP Business Suite 7, which includes ECC, at the end of 2027. Optional extended maintenance runs from 2028 through 2030.
SAP also offers a transition option. Its October 2026 update and SAP Note 3591251 allow subscriptions to run until December 31, 2035, with prerequisites. One prerequisite is a move to SAP ERP, private edition, on SAP HANA before the end of 2030. Older guides cite 2033, and that date is out of date.
SAP's own on-premises MES has the same clock. An SAP architecture article states that SAP ME and MII 15.5 leave mainstream maintenance in 2027, extended to 2030, with no further releases.
The question for your MES is simple. When the ERP changes, which layer breaks? SAP Digital Manufacturing connects to both ECC and S/4HANA through the same SAP Cloud Integration path, so the MES side stays stable.
Third-party MES products carry more risk. Junot Systems, which sells an SAP connector, describes an AVEVA MES site whose IDoc interface failed on the S/4HANA upgrade. The legacy integration tool did not support an RFC client connection. The same logic applies to any ERP move, such as Dynamics AX to Dynamics 365. Our NetSuite vs. SAP S/4HANA vs. Dynamics 365 guide covers the ERP side of that decision.
MES security: where the MES sits in your OT network
The deployment model also sets your firewall rules. An on-premises MES sits at Purdue Level 3, and its ERP traffic crosses the industrial DMZ at Level 3.5. NIST SP 800-82 Rev. 3 recommends a DMZ that prevents direct traffic between corporate and OT networks.
A cloud MES needs outbound connections from the plant instead. Tulip documents outbound TCP 53, 80, 123 and 443 for its edge devices. Its Connector Host makes an outbound connection, so no inbound rule is needed. SAP Digital Manufacturing reaches the ERP over HTTPS through the SAP Cloud Connector.
Use IEC 62443 as the frame for the review. I found no published IEC 62443-4-1 or 4-2 certificate for any of the eight MES products, so ask each vendor for the certificate itself. Our guides on ICS and SCADA security, OT/IT convergence and Claroty vs. Nozomi vs. Dragos vs. Armis cover the monitoring layer around it.
When you need OEE software instead of a full MES
A single plant that only wants machine visibility often needs OEE software. Machine-monitoring and OEE tools read machine states, counts and downtime reasons. They show where the line loses time, and they stop there: no dispatch, no part history and no enforced holds.
That is the dashboard trap in reverse. Some plants buy a full MES to get a downtime chart, then spend a year on interfaces they did not need. Tulip's Machine Monitoring module is one documented example of this lighter tier inside a broader platform. Our guide to IoT and edge computing solutions covers the sensor and gateway layer underneath it.
The upgrade trigger is clear. You need an MES once you must record part history, produce electronic batch records, capture Part 11 signatures, or enforce quality holds that block the next step. If you are adding automation first, read why cobots won't fix your factory before you size the data layer.
Manufacturing execution system requirements: questions to ask in your PoC
A proof of concept should test the four criteria. Send these ten questions before the PoC starts. Ask the vendor to back each answer with documentation or a live test.
Question 7 matters most. If the vendor refuses to pull the cable, you have your answer.
Use the selector below to see which deployment types your constraints rule in or out. It works at the category level and points you to a deployment type to shortlist.
Building an MES shortlist?
Tell TechnologyMatch about your plants, your ERP and your OT network, and meet MES vendors that fit. It's private, there's no sales pressure, and it's always free to you.
FAQ
What is MES software?
MES software is the execution layer of a plant. It sits at ISA-95 Level 3, between ERP and plant controls. It releases work orders to the floor, records which materials and people built each unit, and enforces quality and process rules while production runs.
What are the top MES software companies?
The main MES software vendors fall into three groups. Site-installed suites include Siemens Opcenter, AVEVA MES, Proficy Plant Applications and DELMIA Apriso. Cloud MES tied to an ERP includes SAP Digital Manufacturing and Rockwell's Plex MES. Composable platforms include Tulip and Critical Manufacturing. Choose the group first, then compare vendors.
Does SAP have an MES?
Yes. SAP Digital Manufacturing is SAP's cloud MES on SAP Business Technology Platform. An optional plant edge runtime runs transactions offline and replays them to the cloud. SAP's older on-premises products, SAP ME and MII 15.5, leave mainstream maintenance in 2027, with extended maintenance to 2030.
What is the difference between MES and ERP?
ERP plans and accounts for production: orders, materials, costs and finance. MES executes and records production on the floor, in minutes and seconds. In a typical flow, the ERP sends production orders down to the MES. The MES sends confirmations and goods movements back up.
Is cloud MES reliable for 24/7 plants?
Only with a local execution layer. SAP documents an edge runtime that caches orders and recipes and replays offline transactions. Critical Manufacturing states that its cloud installations have no offline capability, and Tulip documents no offline mode. For a 24/7 plant, require an edge tier or redundant links, and test both.
How much does MES software cost?
The vendors in this guide do not publish prices in their technical documentation. The main cost drivers are the number of plants and edge devices, separately licensed connectivity and integration products, the number of ERP interfaces, and validation work for regulated lines. Ask each vendor to quote every component it needs.
How long does an MES implementation take?
I found no independent, sourced range for MES implementation time. Duration depends on the number of plants, the PLC and ERP interfaces you need, and validation for regulated lines. Ask each vendor for reference projects with a similar scope, and talk to those customers directly.
