Executive Summary
Three questions decide most MES shortlists: what kind of production the plant runs, where the software may run, and how much the plant wants to build for itself.
A manufacturing execution system (MES) runs and records production on the plant floor. It takes the orders planned in the ERP, guides operators and machines through each step, and records what was made, from which materials, by whom and on which equipment. ISA states that level 3 describes manufacturing execution systems (MES) and other systems such as SCADA that manage manufacturing operations, and that the ISA-95 standard primarily deals with the interface between levels 3 and 4.
The products differ in shape. Velotic states that Proficy Smart Factory MES can be deployed as SaaS or on premises with cloud-native Kubernetes support. Siemens offers separate Opcenter Execution products for discrete, process, electronics, medical device and diagnostics, pharma and semiconductor manufacturing. Tulip states that guided workflows, management terminals and dashboards can be created on a common data model with no coding required. Velotic states that its formation coincides with the closings of TPG’s acquisitions of Proficy, the former manufacturing software business of GE Vernova, and PTC’s former industrial connectivity and Internet of Things (IoT) businesses.
This guide defines the category from the ISA-95 standard and the FDA’s electronic records rule, sets three frequently compared products side by side, sets out seven approaches to buying an MES, names eight vendors that represent them, and lists the prices vendors publish. Plant equipment security is covered in the OT & ICS Security Buyer Guide. Quality processes outside production are covered in the Quality Management System Buyer Guide.
What Is a Manufacturing Execution System?
ISA describes ISA-95, also known as ANSI/ISA-95 or IEC 62264, as an international set of standards aimed at integrating logistics systems with manufacturing control systems. Its model sorts plant systems into levels. ISA states that level 2 describes the monitoring and supervising of physical processes in the manufacturing environment and refers to programmable logic controllers (PLCs), distributed control systems (DCSs) and other control devices. ISA places all the activities related to running a business, including enterprise resource planning (ERP) systems, at level 4. An MES sits between those two layers. It turns a production order into dispatched work, collects data from machines and operators as the work runs, and reports results back to the ERP.
Most MES products cover the same core jobs: dispatching work orders, tracking work in progress and materials, enforcing quality checks, recording genealogy, and measuring equipment performance such as overall equipment effectiveness (OEE). Vendors also use the wider term manufacturing operations management (MOM). Dassault Systèmes describes DELMIA Apriso as a Manufacturing Operations Management (MOM) solution, and states that MOM includes all capabilities traditionally considered part of MES but extends them to include integrated quality, materials management, maintenance and other functions.
In regulated plants the MES record is often the record an inspector reads. The FDA rule on electronic records sets the criteria under which the agency considers electronic records and electronic signatures to be trustworthy, reliable, and generally equivalent to paper records and handwritten signatures executed on paper. For closed systems, the rule requires procedures and controls that include the use of secure, computer-generated, time-stamped audit trails that independently record the date and time of operator entries and actions that create, modify, or delete electronic records. Pharmaceutical batch records, medical device history records and aerospace traceability all depend on that kind of record.
An MES is hard to replace once it runs. Operators learn its screens, engineers encode routings and recipes in it, and auditors accept its records. Plan for a system you will run for many years, and test its upgrade path as carefully as its features.
How Do a Portfolio MES, an Industry MES and a No-Code Platform Compare?
Three kinds of product are often compared for the same plant: an MES sold in an industrial software portfolio, an MES sold as separate products by industry, and a no-code platform. The statements below are the vendors’ own, from their own pages, as of November 2026.
Ownership. Velotic states that its formation coincides with the closings of TPG’s acquisitions of Proficy, the former manufacturing software business of GE Vernova, and PTC’s former industrial connectivity and Internet of Things (IoT) businesses. Siemens describes Opcenter as a unified manufacturing operations management (MOM) solutions portfolio.
Deployment. Velotic states that Proficy Smart Factory MES can be deployed as SaaS or on premises with cloud-native Kubernetes support. Siemens describes Opcenter X as a digital manufacturing software-as-a-service (SaaS) solution with a modular approach to manufacturing operations management (MOM) for the SMB market. Tulip calculates plans on Monthly Active Interfaces (MAI), the devices running applications through the Tulip Player, such as computers, tablets, mobile phones or wearable devices. Ask each vendor which products run on premises, which run in its cloud, and which can run on both.
Plant type. Siemens offers separate Opcenter Execution products for discrete, process, electronics, medical device and diagnostics, pharma and semiconductor manufacturing. Tulip lists 21 CFR Part 11 alignment, with electronic records and signatures aligned to FDA requirements from the moment of creation.
Quality and traceability. Velotic states that Proficy embeds quality into manufacturing execution with real-time process monitoring, SPC, data collection, specifications, digital workflows, and approvals. Velotic states that Proficy tracks materials, equipment, processes, production events, and operator activity throughout manufacturing. Siemens states that Opcenter Execution tracks and traces the status of production and disposition of work, including documentation of regulatory and quality requirements. Siemens states that Opcenter Execution Pharma offers paperless manufacturing and electronic batch recording (eBR) of pharmaceuticals.
Scheduling and analytics. Velotic states that combining Proficy Smart Factory MES with Proficy Scheduler extends MES upstream into finite-capacity production scheduling. Siemens states that Opcenter APS production planning and scheduling products help synchronize manufacturing processes to increase resource utilization and reduce inventory levels. Velotic states that MCP support, expanded GraphQL APIs and Chat with Proficy MES help bring conversational AI and contextual insights directly into MES workflows.
Connections. Tulip states that it connects CNC machines, devices and legacy equipment to ERPs, WMSs and enterprise systems through hundreds of pre-built connectors and drivers. Ask each vendor to connect to the same list of machines, historians and ERP systems from your plant floor.
The first pair is compared aspect by aspect, with a source for every fact, on a separate comparison page.
| If you need | Look at | Why |
|---|---|---|
| An MES built for one industry’s rules, such as pharma batch records | Vendors that sell separate products by industry | Industry records and workflows come configured, not built |
| One MES product across plants of different types | Vendors that sell a single configurable MES | One product to train, validate and upgrade |
| Apps your own engineers build and change | A no-code frontline operations platform | Changes ship without a vendor project; governance becomes your job |
| Scheduling tied to execution | Vendors that sell finite-capacity scheduling beside the MES | The schedule reacts to what the floor actually did |
What Should You Test in an MES?
Start with fit to your production model. A discrete plant needs routings, serial numbers and as-built genealogy. A process plant needs recipes, batches, weigh and dispense, and electronic batch records. A mixed plant needs both without custom code. Ask each vendor to configure one of your products, not theirs.
Then test the two seams. Below the MES sit the PLCs, SCADA and historians that feed it. Above it sits the ERP that sends orders and receives confirmations. Ask which protocols and ERP versions each vendor connects to without custom work, and what happens on the floor when the ERP or the network is down.
Test traceability on a recall drill. Pick a component lot and ask the system for every finished unit that used it, and every lot that went into one finished unit. Time the answer and check it against paper records.
For regulated plants, test the record itself: electronic signatures, audit trails, review by exception, and the validation documents the vendor supplies. Ask how a software update is validated and who pays for the revalidation.
Last, test who can change the system. Ask how a new work instruction, a new check or a new screen gets from an engineer’s idea to the floor, how long that takes, and whether it needs the vendor.
| Capability | What it does | Buyer translation |
|---|---|---|
| Work order execution | Dispatches orders to lines and work centers and tracks work in progress | Can a supervisor see where every order stands right now? |
| Genealogy and traceability | Records which materials, equipment and people made each unit or lot | How fast can you scope a recall? |
| Quality in execution | Enforces checks, SPC and holds during production | Can a bad lot move to the next step? |
| Electronic batch and device history records | Records production as the regulated record, with signatures and audit trails | Can QA review by exception instead of page by page? |
| Equipment performance | Measures availability, performance and quality losses (OEE) | Which losses cost the most capacity this week? |
| Machine and ERP integration | Collects data from controls and historians; exchanges orders with the ERP | What is custom code, and who maintains it? |
| Multi-site templates | Deploys a standard model to many plants with local variations | Does the fifth plant cost less than the first? |
Vendors in Manufacturing Execution Systems (MES)
Representative vendors include AVEVA Wonderware MES (AVEVA Manufacturing Execution System), Critical Manufacturing, Dassault DELMIA Apriso, GE Vernova Proficy (Velotic), Rockwell Plex & FactoryTalk, SAP Digital Manufacturing / DM, Siemens Opcenter and Tulip. The list is alphabetical, is not a ranking, and is not for sale. How we choose vendors
The approaches below follow where each product started, where it runs and what kind of plant it was built for. Two vendors in the table share the first approach.
Manufacturing operations management suites from PLM vendors cover execution, quality and planning, and link production to product design. Siemens describes Opcenter as a unified manufacturing operations management (MOM) solutions portfolio. Siemens describes Opcenter X as a digital manufacturing software-as-a-service (SaaS) solution with a modular approach to manufacturing operations management (MOM) for the SMB market. Dassault Systèmes states that DELMIA Apriso provides a cohesive digital infrastructure that standardizes core processes while accommodating regional variations in execution. Dassault Systèmes lists, among the benefits of DELMIA Apriso, fully configurable on premise and private cloud solutions. Dassault Systèmes states that DELMIA Apriso connects ERP systems with shop floor automation to unify production across multiple sites.
A multi-tenant SaaS MES runs every customer on one instance of the vendor’s software. Rockwell Automation describes Plex as a single-instance, multi-tenant edge-to-cloud SaaS production platform that connects people and systems, automates processes and tracks data from end to end. Rockwell Automation states that Plex MES is tailored for discrete, hybrid, and regulated industries. Rockwell Automation offers Plex MES deployment options from cloud-only to hybrid configurations to fit each site’s operational needs. Rockwell Automation lists production finite scheduling among Plex MES capabilities, to determine which jobs to schedule to which work centers with resource availability in mind.
An MES from the ERP vendor connects execution to that vendor’s planning, logistics and HR systems. SAP describes SAP Digital Manufacturing as a manufacturing operations management (MOM) platform. SAP states that SAP Digital Manufacturing supports agility, efficiency, and innovation with a cloud-based manufacturing execution system (MES) and embedded AI. SAP lists skills and certification tracking integrated with SAP SuccessFactors. SAP states that SAP Manufacturing Execution and SAP Manufacturing Integration and Intelligence are being retired, that version 15.5 is the final release, and that it runs a program to help customers transition to SAP Digital Manufacturing.
A hybrid-cloud MES keeps execution on the plant premises and moves multi-site reporting to the cloud. AVEVA states that AVEVA Manufacturing Execution System was formerly known as Wonderware MES. AVEVA states that Schneider Electric completed its acquisition of AVEVA and that AVEVA is now a member of the Schneider Electric group. AVEVA describes AVEVA Manufacturing Execution System as a hybrid cloud MES that combines workflow management and quality control on plant premises with cloud-based multi-site operations management. AVEVA states that AVEVA Manufacturing Execution System fits batch-oriented and flexible, make-to-order production processes in segments such as consumer goods and specialty chemical.
An MES in an industrial software portfolio is sold beside a historian, HMI/SCADA and scheduling software. Velotic states that its formation coincides with the closings of TPG’s acquisitions of Proficy, the former manufacturing software business of GE Vernova, and PTC’s former industrial connectivity and Internet of Things (IoT) businesses. Velotic states that Proficy Smart Factory MES can be deployed as SaaS or on premises with cloud-native Kubernetes support. Velotic states that combining Proficy Smart Factory MES with Proficy Scheduler extends MES upstream into finite-capacity production scheduling.
A no-code frontline operations platform lets plant engineers build their own apps on a shared data model. Tulip states that guided workflows, management terminals and dashboards can be created on a common data model with no coding required. Tulip states that it connects CNC machines, devices and legacy equipment to ERPs, WMSs and enterprise systems through hundreds of pre-built connectors and drivers. Tulip lists 21 CFR Part 11 alignment, with electronic records and signatures aligned to FDA requirements from the moment of creation.
An MES for high-tech discrete manufacturing is built around the routings, equipment integration and genealogy of semiconductor and electronics plants. Critical Manufacturing describes its offer as an MES-powered industrial operations platform for manufacturers of discrete products, with special focus on semiconductor, electronics, medical devices and industrial equipment. Critical Manufacturing states that customers can create and deploy a single baseline MES across multiple sites, with each site keeping the flexibility to model the standard MES to its own business processes. Critical Manufacturing states that ASMPT, an integrated solutions provider in the semiconductor and electronics industries, made a strategic investment in Critical Manufacturing.
| Vendor | Approach | Where it fits |
|---|---|---|
| Critical Manufacturing | High-tech discrete MES | Semiconductor, electronics, medical devices and industrial equipment; one baseline MES across sites |
| AVEVA Wonderware MES (AVEVA Manufacturing Execution System) | Hybrid-cloud MES with an industrial data platform | On premises or hybrid cloud; batch and make-to-order production; part of Schneider Electric |
| SAP Digital Manufacturing / DM | MES from the ERP vendor | Cloud MES; successor to SAP ME and MII, whose final release is 15.5 |
| GE Vernova Proficy (Velotic) | MES in an industrial software portfolio | Proficy Smart Factory MES as SaaS or on premises; now sold by Velotic |
| Dassault DELMIA Apriso | MOM suite from a PLM vendor | Global process standards with regional variation; on premise or private cloud |
| Siemens Opcenter | MOM suite from a PLM vendor | Separate Execution products by industry; Opcenter X as SaaS for smaller manufacturers; APS, Quality and Intelligence |
| Rockwell Plex & FactoryTalk | Multi-tenant SaaS MES | Single-instance, multi-tenant SaaS; cloud-only or hybrid; discrete, hybrid and regulated industries |
| Tulip | No-code frontline operations platform | No-code apps on a common data model; priced per interface |
Eight vendors across seven approaches; Siemens Opcenter and DELMIA Apriso share one. We wrote the approaches first and then selected a vendor for each from the eight the previous edition covered, so every badge holder keeps its row. No vendor bought a row, and rows are not for sale. Other MES vendors can present their own case in the Spotlight below.
How Are MES Platforms Priced?
Most MES vendors price by quote. The license is often a smaller cost than integration, validation and rollout across plants, so ask for a quote that covers your second and fifth plant, not only the first.
Per interface. Tulip lists its Essentials plan at $100/mo per interface billed annually, with a 10 interface minimum. Tulip lists its Professional plan at $250/mo per interface billed annually, with a 10 interface minimum. Tulip calculates plans on Monthly Active Interfaces (MAI), the devices running applications through the Tulip Player, such as computers, tablets, mobile phones or wearable devices.
Credits across a portfolio. AVEVA describes its Flex subscription program as a credits-based system that spans cloud, hybrid, and on-premises solutions across the AVEVA portfolio.
Subscription for SaaS products, and license plus maintenance for software you run on premises, are the other common models. Ask how the price grows: by plant, by line, by user, by device or by module.
All prices are US list prices as published when this guide was checked in November 2026.
| Meter | You are charged for | Grows with | Where it goes wrong |
|---|---|---|---|
| Per site or plant | Each plant that runs the MES | Plant count | Small plants priced like large ones |
| Per user | Named or concurrent users | Operators and supervisors | Every operator on every shift counted |
| Per device or interface | Each station, tablet or screen that runs the software | Stations on the floor | Shared kiosks and dashboards counted one by one |
| Per module | Execution, quality, scheduling, maintenance and analytics | Scope of the rollout | Quality or traceability sold as an add-on |
| Credits | A pool spent across products and deployments | Everything at once | Credits that run out before the year ends |
How long does implementation take for Manufacturing Execution Systems (MES)?
Most MES programs fail at the seams, not in the software. Prove the machine connections, the ERP round trip and operator adoption on one line before you template.
Replacing an older MES is a migration of records as well as screens. SAP states that SAP Manufacturing Execution and SAP Manufacturing Integration and Intelligence are being retired, that version 15.5 is the final release, and that it runs a program to help customers transition to SAP Digital Manufacturing. Ask every vendor the support end date of the version you would install, and how history from your current system is kept for auditors.
Map equipment, protocols, historians and ERP touchpoints for each line. Classify lines as discrete, process or mixed. Decide who owns master data across the MES and the ERP, and, for regulated plants, the validation approach.
Run one representative line live, including its oldest machine. Prove the ERP order and confirmation flow, a quality hold, a network outage and a recall query. Treat operator feedback as a gate.
Extend to the whole plant, then turn what worked into a template: models, integrations and work instructions, with local variations set as parameters rather than copies.
Deploy the template plant by plant, with changes distributed centrally. Retire the old system once its records are archived where auditors can read them.
What should you ask vendors about Manufacturing Execution Systems (MES)?
Ask each vendor to answer in writing and to demonstrate on one of your products and lines.
-
Is the plant regulated (pharma, medical devices, food, aerospace)?Yes Shortlist products with electronic batch or device history records, and ask for validation documents.No Weight speed of change and cost per plant higher.
-
May the execution layer run in the vendor’s cloud?Yes Include SaaS products, and test what an edge component does when the network drops.No Require on-premises or hybrid deployment.
-
Will your own engineers build the screens and workflows?Yes Include a no-code platform, and plan its governance.No Weight packaged industry products and integrator capacity higher.