What Is an MES?
A Manufacturing Execution System (MES) is the real-time command center of the shop floor. While ERP plans what should happen over weeks and months, MES manages what is happening right now — tracking every work order, every machine cycle, every quality check, every operator action as it occurs.
Think of it this way: ERP is the flight plan. MES is the cockpit instrument panel. You need both, but when you're actually flying (producing), the instrument panel is what keeps you from crashing.
The 11 Core MES Functions
The Manufacturing Enterprise Solutions Association (MESA) defined 11 core functions that an MES should provide. Not every implementation uses all 11, but understanding the full scope helps you evaluate what your operation needs:
| # | Function | What it does |
|---|---|---|
| 1 | Operations Scheduling | Detailed sequencing of work orders on specific machines/lines — minute-by-minute, not weekly buckets |
| 2 | Resource Allocation | Assigns machines, tools, materials, and labor to work orders based on availability and skills |
| 3 | Dispatching | Releases work orders to the floor in the right sequence with the right documentation |
| 4 | Document Control | Delivers the right work instructions, drawings, SOPs to the operator at the right time |
| 5 | Data Collection | Captures production counts, cycle times, downtime events, scrap — manually or via machine integration |
| 6 | Labor Management | Tracks operator time, certifications, and labor allocation by work order |
| 7 | Quality Management | In-process inspections, SPC, non-conformance tracking, enforced hold points |
| 8 | Process Management | Monitors process parameters (temperature, pressure, speed) against specifications |
| 9 | Maintenance Management | Triggers preventive maintenance based on run hours/cycles, tracks equipment status |
| 10 | Product Tracking & Genealogy | Full traceability — which materials, operators, and machines touched each unit |
| 11 | Performance Analysis | OEE, throughput, yield, cycle time analysis — the dashboards that drive improvement |
The Gap MES Fills
There's a persistent gap between what ERP plans and what the shop floor does. MES fills this gap:
Without MES
- ERP says "make 500 units" — nobody knows how many are done until shift end
- Machine goes down — nobody outside the cell knows for 30 minutes
- Quality issue found at inspection — no idea when it started or how many are affected
- ERP lead times are guesses — actual cycle times unknown
- End-of-month fire drill to reconcile actual vs. planned production
With MES
- Real-time production count visible on every screen, every minute
- Machine down event triggers instant alert to maintenance and supervision
- SPC chart flags out-of-spec condition; MES quarantines affected units automatically
- Actual cycle times feed back to ERP, keeping lead times honest
- Cost, yield, and OEE calculated automatically every shift
ISA-95: The Integration Standard
ISA-95 (also known as IEC 62264) is the international standard that defines how manufacturing systems should be organized into layers. Understanding these layers is key to knowing where MES fits:
| Level | Name | Systems | Time scale |
|---|---|---|---|
| 4 | Business Planning | ERP, S&OP, demand planning | Weeks to months |
| 3 | Manufacturing Operations | MES, quality, maintenance, scheduling | Shifts to days |
| 2 | Control Systems | SCADA, DCS, HMI, PLCs | Seconds to minutes |
| 1 | Sensors & Devices | Sensors, actuators, drives, instruments | Milliseconds |
| 0 | Physical Process | The actual manufacturing process | Continuous |
Data Collection: The MES Superpower
The single biggest value of MES is automatic, real-time data collection. Here's how data gets into an MES:
Machine integration
- OPC-UA / OPC-DA — Industry standard protocol for reading machine data (cycle counts, status, parameters)
- MTConnect — Open standard specifically for CNC machines and manufacturing equipment
- Direct PLC communication — Reading signals directly from Siemens, Allen-Bradley, or other PLCs
- IoT sensors — Bolt-on sensors for older equipment (vibration, temperature, current draw)
Operator interaction
- Barcode/QR scanning — Scan work orders, parts, and operators for tracking
- Touchscreen terminals — Operators log downtime reasons, quality checks, counts
- Tablet/mobile — Roaming data collection for manual processes
What gets collected
- Production counts (good parts, scrap, rework)
- Cycle times (actual vs. standard)
- Downtime events with reason codes and duration
- Changeover start/stop times
- Quality measurements (dimensions, weights, visual inspections)
- Material consumption (lot tracking, traceability)
- Process parameters (temperature, pressure, speed, torque)
- Operator ID and timestamps for everything
MES and OEE: Real-Time Visibility
One of the most common MES use cases is automatic OEE calculation. Instead of manually calculating OEE at the end of a shift from handwritten logs, MES calculates it continuously:
MES-Driven OEE vs. Manual OEE
Manual approach: Supervisor reviews handwritten downtime log at shift end. "We were down for about 45 minutes." (Reality: 68 minutes across 4 events, but two were too short to log.) OEE calculation: optimistic by 5-8 points.
MES approach: Machine signals captured every second. Four downtime events totaling 68 minutes, each with a reason code. Actual cycle time = 22 seconds (standard = 20). 12 rejects caught at in-line inspection. OEE = 72.3% — accurate, instant, actionable.
The difference: With manual tracking, you think you're at 80% OEE. With MES, you discover you're at 72%. That 8-point gap is where millions of dollars of capacity is hiding.
Traceability and Genealogy
In regulated industries (aerospace, medical devices, food, automotive), MES provides complete product genealogy:
- Which raw material lots went into which finished products
- Which operators performed which operations
- Which machines were used (and their calibration status)
- All quality inspection results
- Environmental conditions during production
- Every deviation, waiver, or non-conformance
Major MES Systems
| System | Typical industry | Notable strengths |
|---|---|---|
| Siemens Opcenter (Camstar) | Semiconductor, electronics, pharma | Deep quality/genealogy, Teamcenter PLM integration |
| Rockwell Plex | Automotive, food & beverage | Cloud-native, combined ERP+MES |
| DELMIA Apriso (Dassault) | Aerospace, automotive | Global multi-plant, 3DEXPERIENCE integration |
| SAP ME / SAP DMC | Large enterprise, discrete & process | Tight SAP ERP integration, Industry 4.0 |
| Aegis FactoryLogix | Electronics assembly | No-code configuration, IIoT connectivity |
| GE Proficy | Process manufacturing, utilities | SCADA/historian integration, Predix IoT |
MES Implementation: Lessons Learned
How SymplProcess Relates to MES
SymplProcess operates in the same space as MES for shift-level operational visibility: structured reports capturing safety, quality, production, equipment, and personnel data every shift. For operations that don't have (or can't justify) a full MES deployment, SymplProcess provides the critical daily rhythm of structured data capture and trend analysis that makes problems visible and actionable.
Key Takeaway
Remember This
MES is the real-time execution layer that turns ERP plans into actual production reality. It collects data as production happens — not after — giving you OEE, traceability, quality control, and performance visibility that manual methods can never match. The #1 rule of MES: the data must drive action. Collection without action is just surveillance.
Interactive Demo
Explore MES real-time production tracking. Toggle features to see how each reduces manual effort and errors.
Stop reading, start doing
Model your process flow, optimize staffing with Theory of Constraints, and track every shift — all in one platform. Set up in under 5 minutes.