MES Software: Vendors, Features & Costs Compared 2026
MES software compared: vendors, functions per VDI 5600, costs (cloud vs. on-premise) and implementation. Honest market overview 2026.
By Martin Brandel · Last updated: April 2026
What is production monitoring and control?
Production monitoring and control is the real-time collection of machine and process data from the shopfloor (monitoring) combined with the ability to act on that data — dispatching orders, adjusting schedules, triggering maintenance, stopping a line when quality drifts (control). It is not a single product or standard. It is the combined capability delivered by three established system layers: Machine Data Collection (MDE), which captures signals directly from the machine — cycle counts, running/stopped states, energy consumption; Production Data Collection (BDE), which adds the business context — which order, which operator, which batch, how many good/reject parts; and a Manufacturing Execution System (MES), which ties MDE and BDE data together, calculates KPIs like OEE, visualises the shopfloor in real time, and provides the control functions — order dispatching, alarm management, quality gating, and process parameter surveillance. The SYMESTIC Cloud MES platform integrates all three layers into a single system with a go-live time measured in days, not months.
What are the 4 maturity levels of production monitoring and control?
Most manufacturing plants do not jump from zero visibility to full MES overnight. Production monitoring and control evolves through 4 maturity levels — each building on the previous one, each delivering measurable value independently:
| Level | Capability | What is captured | What you can do with it | SYMESTIC module |
|---|---|---|---|---|
| 1 | Machine monitoring (MDE) | Machine states (running, stopped, idle), cycle counts, cycle times — captured automatically from PLC signals or digital I/O sensors. No manual operator input required. | OEE calculation (availability and performance), downtime Pareto, real-time shopfloor dashboard. At Klocke, DI-gateway-based machine monitoring went live across all packaging lines in 3 weeks. | Production metrics (MDE segment) |
| 2 | Production data collection (BDE) | Order-to-machine mapping (which order is running on which machine), operator assignment, good/reject counts per order, downtime reason codes (operator-entered or automatic). Typically requires ERP integration to import order data. | OEE with quality rate, order progress tracking, scrap analysis per product/order, shift reports with order-level granularity. At Meleghy, bidirectional SAP integration enabled real-time order feedback across 6 plants. | Production metrics (BDE segment) + Production control |
| 3 | Process data & alarms | Machine alarms from the PLC (alarm number, timestamp, duration), process parameters (temperature, pressure, force, speed, torque) per cycle or per time interval. Captured via OPC UA or native PLC protocols. | Root cause analysis (which alarm preceded which downtime?), process parameter correlation with quality defects, SPC-style trend monitoring. At Neoperl, SPS alarm correlation reduced scrap by 15 %. | Alarms module + Process data module |
| 4 | Active production control | Not a new data source — this is the control layer that acts on the data from levels 1–3. Order dispatching, scheduling, quality gating (hold an order if defect rate exceeds threshold), maintenance triggering based on operating hours or alarm patterns. | The shopfloor is not only visible but steerable: orders are assigned to machines, sequences are optimised, deviations trigger alerts or automatic holds. At Schmiedetechnik Plettenberg, the bidirectional ERP integration closes the loop between planning and execution. | Production control + Production planning |
The key insight: level 1 (machine monitoring) delivers measurable results within days and requires no ERP integration, no PLC programming, and no production interruption. At Klocke, DI gateways were connected to fully automated packaging lines without LAN infrastructure — and OEE data was available the same day. Each subsequent level adds depth, but the first level is sufficient to start. The progression from level 1 to level 4 typically takes 3–12 months depending on plant complexity and ERP landscape.
How does production monitoring and control relate to MES?
Production monitoring and control is not a separate system alongside an MES — it is the core function of an MES. The international standard ISA-95 (IEC 62264) defines the MES as the Level 3 system that sits between the shopfloor (Level 0–2: sensors, PLCs, SCADA) and the enterprise level (Level 4: ERP). Within ISA-95, the MES performs 8 functional areas. Production monitoring and control maps directly to several of them:
| ISA-95 / VDI 5600 function | Monitoring or control? | What it covers | SYMESTIC capability |
|---|---|---|---|
| Data collection / acquisition (VDI 5600: Datenerfassung) | Monitoring | Automated capture of machine signals, part counts, states, cycle times | MDE via OPC UA, native PLC protocols, digital I/O gateways. 2–4 hours per machine for modern PLCs, 1–2 hours for DI gateways. |
| Performance analysis (VDI 5600: Leistungsanalyse) | Monitoring | OEE, downtime Pareto, micro-stop analysis, shift comparison, trend analysis | Production metrics module — real-time OEE dashboards with drill-down to machine, shift, product, order level |
| Production execution management (VDI 5600: Feinplanung & Steuerung) | Control | Order dispatching, sequence optimisation, machine assignment, progress tracking | Production control + Production planning. At Carcoustics, digital changeover (Rüstprozesse) support was a key use case. |
| Quality management (VDI 5600: Qualitätsmanagement) | Both | Quality rate tracking (monitoring), quality gating and inspection triggering (control) | OEE Quality rate per station. At Meleghy, bidirectional CASQ-it integration triggers sample inspections automatically. |
| Maintenance management (VDI 5600: Instandhaltungsmanagement) | Both | Operating-hour tracking and alarm patterns (monitoring), maintenance notifications (control) | Alarms module correlates alarm frequency with downtime. At Neoperl, PLC alarm correlation identified the failure modes causing the most downtime — enabling targeted preventive action. |
The practical conclusion: if a plant implements an MES, it gets production monitoring and control as part of the package — because that is what an MES does. The question is not "Do I need MPC or MES?" — the question is "At which maturity level do I start, and how fast do I progress to the next?"
What does production monitoring and control look like without an MES?
Many plants attempt production monitoring without a dedicated system. The result is a patchwork of manual processes and local tools:
| Common workaround | What it delivers | What it misses | Why it breaks at scale |
|---|---|---|---|
| Paper-based shift logs | Downtime reasons written by operators at end of shift. Good/reject counts from manual tally. | Micro-stops (operators do not log stops under 5 minutes). Accurate timestamps. Cycle time data. Anything that happened when the operator was away from the machine. | Analysis requires manual transcription into Excel. Results are available days later. At 20+ machines, the transcription effort alone consumes 1–2 FTE. |
| Excel-based OEE tracking | OEE calculated from shift log data entered manually. Charts and Pareto generated in Excel. | Real-time visibility (data is always at least 1 shift old). Automatic cycle time measurement. Machine-level granularity for micro-stops. | Multiple Excel files with inconsistent formulas across shifts and plants. No single source of truth. At Meleghy with 6 plants, this approach was unsustainable — SYMESTIC replaced it with consistent, automatic OEE across all sites. |
| SCADA as monitoring tool | SCADA shows machine states in real time on the control room screen. Good for process control. | SCADA is designed for process control (Level 2 in ISA-95), not for production KPI analysis (Level 3). No OEE calculation, no order tracking, no shift comparison, no Pareto analysis, no trend over weeks/months. | SCADA data is typically not historised for KPI analysis. Extracting OEE from SCADA requires custom development — which becomes a maintenance burden when the SCADA system is upgraded. |
| ERP production module | Order status tracking (planned, in progress, completed). Good/reject quantities per order. | Real-time machine visibility (ERP operates in transaction cycles, not real time). Cycle time data. Machine-level downtime analysis. OEE. Everything between "order started" and "order completed." | ERP was designed for business transactions, not for shopfloor monitoring. The gap between the ERP order world and the physical machine world is exactly where the MES sits — as defined by ISA-95. |
None of these workarounds are wrong — they are the natural starting point for most plants. The transition to an MES happens when the cost of not knowing (hidden downtime, undetected micro-stops, delayed reaction to quality drift) exceeds the cost of implementing a system. At Brita, the transition happened without a formal POC — because the gap between estimated and actual OEE was so large that the business case was obvious from the first week of data.
FAQ
Is "production monitoring and control" (MPC) an industry standard term?
No. Unlike MES (defined in ISA-95 / IEC 62264 and VDI 5600), SCADA (widely standardised), or OEE (defined in ISO 22400-2), "production monitoring and control" is a descriptive phrase, not a standardised system category. You will not find an "MPC" entry in ISA-95 or VDI 5600. It describes a function — real-time shopfloor visibility plus the ability to act on it — that is implemented by MDE, BDE and MES systems. When evaluating vendors, look for the specific capabilities (machine data collection, OEE calculation, order tracking, alarm management, process data capture) rather than the label.
How quickly can production monitoring deliver measurable results?
Level 1 (machine monitoring / MDE) delivers OEE data within days. At Klocke, all packaging lines were connected in 3 weeks — 7 additional hours of productive time per week were identified in the first week. At Meleghy, 10 % downtime reduction was achieved within 6 months across 6 plants. The pattern is consistent: the first week of automatic data collection reveals a gap of 10–20 percentage points between what the plant believes its OEE is and what the measured OEE actually is. That gap is the improvement potential that production monitoring makes visible.
Does production monitoring require stopping the machines for installation?
No — if the connectivity approach is chosen correctly. Digital I/O gateways (optical or inductive sensors clamped to existing signal lines) require no PLC modification and no production interruption. OPC UA connections to modern PLCs (Siemens S7-1500, Beckhoff TwinCAT 3, etc.) read data from the PLC's built-in OPC UA server — also without PLC programming changes or production stops. Only older PLCs without Ethernet or OPC UA may require a brief connection window. At Klocke, all lines were connected via DI gateways without any LAN infrastructure — completely non-invasive.
What is the difference between production monitoring and shopfloor management?
Production monitoring is the data layer: collecting machine and production data automatically and presenting it in real time. Shopfloor management is the management method: the structured daily routine of short interval control meetings at the shopfloor board, where teams review the data, discuss deviations, and define countermeasures. Production monitoring feeds shopfloor management with facts. Shopfloor management turns those facts into action. One without the other is incomplete: monitoring without management is data without decisions; management without monitoring is decisions without data.
Related: MES: Definition & Functions · OEE Explained · Machine Data Collection (MDE) · Production Data Collection (BDE) · Shopfloor Management · ISA-95 · SCADA · SYMESTIC Production Metrics · SYMESTIC Production Control · SYMESTIC Alarms Module · SYMESTIC Process Data
About the author
Martin Brandel
MES Consultant at SYMESTIC. Dipl.-Ing. Nachrichtentechnik. Over 30 years in industrial automation. Has connected machines from 1991 Simatic S5 controllers to 2026 OPC UA cloud gateways — and can tell you within 10 minutes of walking a shopfloor which maturity level the plant is at and what the next step should be. · LinkedIn
Start working with SYMESTIC today to boost your productivity, efficiency, and quality!
