MES Systems (Manufacturing Execution Systems)

What an MES does between ERP and the floor: the 11 core functions, ISA-95, data collection, real-time OEE, traceability and implementation lessons.

13 min read 12 sections Guide 2 of 11, Enterprise Systems & Technology Updated

ERPPLMMESFLOORQMS

New to this topic?

Read these first to get the most out of this guide:

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.

Real-time
Data collection
20-30%
Typical OEE improvement
ISA-95
Integration standard
11
Core MES functions (MESA)

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:

ScopeRequests push at the scope line; only the approved change gets through the gateThe Scope guide
#FunctionWhat it does
1Operations SchedulingDetailed sequencing of work orders on specific machines/lines, minute-by-minute, not weekly buckets
2Resource AllocationAssigns machines, tools, materials, and labor to work orders based on availability and skills
3DispatchingReleases work orders to the floor in the right sequence with the right documentation
4Document ControlDelivers the right work instructions, drawings, SOPs to the operator at the right time
5Data CollectionCaptures production counts, cycle times, downtime events, scrap, manually or via machine integration
6Labor ManagementTracks operator time, certifications, and labor allocation by work order
7Quality ManagementIn-process inspections, SPC, non-conformance tracking, enforced hold points
8Process ManagementMonitors process parameters (temperature, pressure, speed) against specifications
9Maintenance ManagementTriggers preventive maintenance based on run hours/cycles, tracks equipment status
10Product Tracking & GenealogyFull traceability, which materials, operators, and machines touched each unit
11Performance AnalysisOEE, 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:

VISIBLEHIDDEN
Cost of qualityThe cost of quality is an iceberg: scrap and rework above, the larger hidden part belowThe Cost of quality guide

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:

4 ERP3 MES2 CONTROL1 SENSE0 PROCESS
ISA-95 levelsFive levels stack from sensors at the bottom to the business system at the top; orders go down and results come up
LevelNameSystemsTime scale
4Business PlanningERP, S&OP, demand planningWeeks to months
3Manufacturing OperationsMES, quality, maintenance, schedulingShifts to days
2Control SystemsSCADA, DCS, HMI, PLCsSeconds to minutes
1Sensors & DevicesSensors, actuators, drives, instrumentsMilliseconds
0Physical ProcessThe actual manufacturing processContinuous
Level 4: ERP
↕
Level 3: MES
↕
Level 2: SCADA/PLC
↕
Level 0-1: Machines & Sensors
ISA-95 automation pyramid: MES is the critical middle layer
Why ISA-95 matters practically: When you're evaluating MES vendors or designing integrations, ISA-95 tells you where each system's responsibility starts and stops. If your MES vendor is trying to do ERP functions (Level 4), that's a red flag. If your ERP vendor says you don't need MES and can do everything from Level 4, they're ignoring the real-time execution gap.

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:

25.40
MeasurementA gauge should resolve a tenth of the toleranceThe Measurement guide

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:

PLANAA×POEE81%
OEEOEE = availability × performance × qualityThe OEE guide

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:

ASSEMBLYSN 0417LOT A12LOT B07LOT C33
TraceabilityA serial number links up to the assembly it went into and down to the lots it was built from
  • 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
Why defense contractors invest heavily in MES traceability: When you're building aircraft, every rivet, every weld, every composite layup must be traceable to specific material lots, operators, and conditions. If a material defect is discovered years later, you need to know exactly which serial numbers are affected. Without MES, this means weeks of manual record searches. With MES, it's a query that returns in seconds.

Major MES Systems

Production systemPlanning, the floor and the people orbit one production systemThe Production system guide
SystemTypical industryNotable strengths
Siemens Opcenter (Camstar)Semiconductor, electronics, pharmaDeep quality/genealogy, Teamcenter PLM integration
Rockwell PlexAutomotive, food & beverageCloud-native, combined ERP+MES
DELMIA Apriso (Dassault)Aerospace, automotiveGlobal multi-plant, 3DEXPERIENCE integration
SAP ME / SAP DMCLarge enterprise, discrete & processTight SAP ERP integration, Industry 4.0
Aegis FactoryLogixElectronics assemblyNo-code configuration, IIoT connectivity
GE ProficyProcess manufacturing, utilitiesSCADA/historian integration, Predix IoT

MES Implementation: Lessons Learned

The constraintOutput is set by the constraint; an hour lost there is lost for the systemThe constraint guide
Start with one line or cellDon't try to deploy MES plant-wide on day one. Pick a bottleneck line where visibility will have the biggest impact.
Define your reason codes firstDowntime reason codes are the foundation of MES analytics. If they're vague ("other," "misc"), your data is useless. Involve operators in defining them.
Integrate machines before asking operatorsAutomatic data collection is always more accurate. Get machine cycle counts and status from PLCs before relying on manual input.
Close the loop with ERPMES data only creates value if it flows back to ERP: actual cycle times update routings, actual yield updates planning factors, actual costs update standards.
Act on the data, or lose credibilityIf you collect downtime data but never fix the top reasons, operators will stop entering accurate data. Show them their input drives action.

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

Key takeawayThe point of the guide pinned to the board with a strip of tape

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.

MES Production Tracking

View work order status in real-time. Toggle MES features on/off to see how each one reduces manual effort and data entry errors. Click a work order status to cycle it.

Work Orders — Line 1
WO-001Assembly A-100
487/500
WO-002Assembly B-200
300/300
WO-003Assembly C-350
120/400
Reason: Material shortage
MES Features
Auto Data Collection
Machine sensors automatically capture cycle times, counts, and quality data — no manual entry
-45 min/shift-3.5% errors
Recipe Management
Automatically downloads correct machine parameters when a new work order starts
-25 min/shift-2.8% errors
Product Genealogy
Tracks every component, material lot, and process step for full traceability
-30 min/shift-1.5% errors
Work Order Dispatch
Optimizes work order sequencing based on priorities, due dates, and equipment availability
-20 min/shift-1.2% errors
Manual Paperwork120 min/shift (100% of baseline)
120 min
= 0 min vs baseline
Manual Time
8.0%
= 0.0% vs baseline
Error Rate
0 / 4
Features Active
0%
Digitization

Ready for the full knowledge check? Guided scenarios and data export. Included with every plan.

PlanTake the advanced knowledge check

Frequently asked questions

What are the functions of a manufacturing execution system?

MESA defines 11 core MES functions: operations scheduling, resource allocation, dispatching, document control, data collection, labor management, quality management, process management, maintenance management, product tracking and genealogy, and performance analysis (OEE, throughput, yield, cycle time). Not every implementation uses all 11.

What does MES stand for in manufacturing?

Manufacturing Execution System: the real-time command center of the shop floor. ERP plans what should happen over weeks and months; MES manages what is happening right now, tracking every work order, machine cycle, quality check and operator action as it occurs.

What is the difference between MES and ERP?

ERP plans what should happen over weeks and months. MES manages what is happening right now on the floor. ERP is the flight plan, MES is the cockpit instrument panel. MES data creates value when it flows back to ERP: actual cycle times update routings and actual yield updates planning factors.

How do you implement an MES?

Start with one line or cell, usually the bottleneck. Define downtime reason codes first, with operators. Integrate machine data from PLCs before relying on manual input. Close the loop so MES data flows back to ERP. Then act on the data, or operators stop entering it accurately.

Share this guide: LinkedIn X Follow SymplProcess on LinkedIn
Take the advanced knowledge check Plan Included with every plan.

Take this to a room

The running order

For operations considering or running an MES. They should leave able to describe the gap it fills in their own plant's terms.

7 beats · 12 min
  1. 1

    The gap, stated as a day on the floor

    Describe the plant without an MES and everyone recognises it immediately.

    • ERP says make 500. Nobody knows how many are done until the end of shift.
    • A machine goes down and nobody outside the cell knows for thirty minutes.
    • A quality issue found at inspection: no idea when it started or how many are affected.

    Ask the room How many of those are true here today?

  2. 2

    The same day with one

    Same events, different information, and the difference is entirely timing.

    • Real-time count visible on every screen, every minute.
    • A down event triggers an instant alert to maintenance and supervision.
    • An out-of-spec condition quarantines the affected units automatically.
  3. 3

    It closes the loop back to ERP

    The benefit people forget, and it is the one that compounds.

    • Actual cycle times feed back, so ERP lead times stop being guesses.
    • Cost, yield and OEE calculate continuously rather than in a month-end fire drill.
    • An ERP fed by real data plans better every subsequent week.
  4. 4

    ISA-95 and the levels

    A shared vocabulary for where each system sits, which prevents most integration arguments.

    • Level 4 ERP. Level 3 MES. Level 2 SCADA and PLC. Levels 0 to 1 machines and sensors.
    • Each level talks to the ones next to it.
    • When someone proposes connecting level 4 directly to level 1, that model is why you say no.
  5. 5

    Real-time OEE is the headline benefit

    Twenty to thirty per cent OEE improvement is typical, and the mechanism is visibility rather than technology.

    • Losses become visible while the shift is still running.
    • Reason codes captured at the moment of the stop, not reconstructed later.
    • You cannot Pareto what nobody wrote down.

    Ask the room How do we capture downtime reasons today?

  6. 6

    Traceability and genealogy

    Which lot, which machine, which operator, which settings: for every unit.

    • Containment becomes a query rather than an investigation.
    • In regulated industries this is not optional.
    • In every industry it is the difference between recalling 40 units and recalling 4,000.
  7. 7

    Implementation lessons

    The same lessons as ERP, with one addition specific to the floor.

    • Start with one line or one cell, not the plant.
    • Involve operators in the interface design: they will use it every cycle.
    • Data collection design comes before dashboard design.
    • An MES nobody on the floor wants to use collects nothing.

    Ask the room Which line would we pilot on?