A Manufacturing Execution System (MES) is software that manages, monitors, and controls manufacturing operations on the shopfloor in real time. MES is the middle layer of the manufacturing IT hierarchy — sitting between the ERP system (business planning) and the plant control layer (PLCs, SCADA, machines). It bridges the gap between planning and physical production execution.
According to ISA-95 (the international standard for manufacturing enterprise system integration), MES is the Level 3 system in the manufacturing automation pyramid — responsible for production execution, tracking, and performance analysis.
A Manufacturing Execution System (MES) is software that tracks, manages, and controls work-in-progress on the shopfloor from order release to finished goods, providing real-time visibility and decision support to operations teams.
MES provides 11 core functional capabilities, as defined by MESA International:
The three systems often cause confusion because they overlap at their boundaries. Here is a clear comparison:
| Dimension | ERP | MES | SCADA |
|---|---|---|---|
| Layer | Level 4 (Enterprise) | Level 3 (Operations) | Level 2 (Control) |
| Time horizon | Days to months | Seconds to shifts | Milliseconds to seconds |
| Primary focus | Business planning, finance, procurement | Production execution, tracking, OEE | Machine control, alarms, sensor data |
| Users | Finance, procurement, management | Operations managers, supervisors, operators | Control engineers, automation teams |
| Data source | ERP transactions, purchase orders | MES + machine data via OPC UA | PLCs, sensors, actuators |
| Examples | SAP S/4HANA, Oracle, Dynamics 365 | Shopfloor Copilot, Siemens Openter, Rockwell FTPC | Siemens WinCC, Ignition, GE iFIX |
ISA-95 defines the standard architecture for integrating manufacturing enterprise systems. The five levels are:
MES at Level 3 is the critical integration point: it receives production orders from ERP (Level 4), translates them into machine-level instructions, and collects real-time execution data from SCADA (Level 2) to report back to ERP.
Manufacturers implementing MES typically report:
Traditional MES solutions (1990s–2010s) were monolithic, vendor-locked, expensive to implement (€500k+), and required months of customisation. Modern MES — including cloud-native and on-premise platforms like Shopfloor Copilot — offer:
| Factor | On-Premise MES | Cloud MES (SaaS) |
|---|---|---|
| Data sovereignty | ✓ Full — data stays in factory | ✗ Data leaves facility |
| OT security compliance | ✓ Air-gap capable | ✗ Requires internet connectivity |
| Latency | ✓ Sub-millisecond local network | ✗ Round-trip internet latency |
| Uptime dependency | ✓ Independent of vendor cloud uptime | ✗ Vendor outage = your downtime |
| Implementation cost | One-off licence + hardware | Ongoing subscription |
| Regulatory fit | ✓ ITAR, GxP, ISO, AS9100D | Varies by vendor |
A Manufacturing Execution System (MES) is software that manages, monitors, and controls manufacturing operations on the shopfloor in real time. It tracks production orders, machine availability, output quality, downtime events, and operator actions — providing operations teams with live visibility into production performance. MES sits between ERP and the plant control layer (PLCs, SCADA) in the ISA-95 manufacturing hierarchy.
SCADA monitors and controls individual machines at the signal level — real-time sensor data, alarms, and machine control. MES operates at a higher level, tracking production orders, OEE, quality, and workforce across multiple machines and lines. SCADA feeds data into MES; MES provides production context and business reporting. Both are needed in a complete Industry 4.0 architecture.
ERP handles business processes above the shopfloor: order management, procurement, financial accounting. MES handles execution on the shopfloor: production scheduling, machine monitoring, quality control, downtime management. ERP works in planned time horizons (days, weeks); MES works in real time (seconds, minutes). A complete manufacturing IT stack uses both.
Traditional legacy MES: 6–18 months. Modern Docker-based MES (like Shopfloor Copilot): initial deployment in 2–4 hours, integration with OPC UA machines in 1–3 days for a typical production line. Full rollout across a facility typically takes 2–6 weeks for configuration, data validation, and operator training.
Shopfloor Copilot is a full-stack AI MES that deploys via Docker in under 2 hours. Built-in OEE monitoring, OPC UA connectivity, predictive maintenance, and local AI diagnostics — with data sovereignty guaranteed.
Explore Platform →