Manufacturing execution system (MES): what it does, where it fits, and how to choose one

What is a manufacturing execution system?

A manufacturing execution system (MES) is software that manages and documents the execution of production orders on the shop floor in real time — dispatching work, tracking what is produced on which machine by whom, enforcing the process (recipes, routings, quality checks) and feeding actuals back to the ERP. In the ISA-95 model it is the Level 3 system: above the PLCs, SCADA and HMIs (Levels 0–2) and below business planning in the ERP (Level 4).

The practical test: if your ERP knows that order 4711 for 10,000 parts was released on Monday, the MES is what knows that 6,240 have been produced so far, on machine 12, by the night shift, with 38 rejects for a burr defect, using lot 2211 of raw material — and that the order is running 3 hours behind plan.

The 11 MES functions (MESA model)

The MESA International model is still the most useful checklist for what "full MES" means. Few plants need all eleven; knowing which ones you need is most of the selection work.

MESA function	What it does in practice	Typically needed when…
Resource allocation & status	Tracks machines, tools, materials, people and their current state	Shared resources, tooling constraints
Operations / detailed scheduling	Sequences orders on equipment, considering setups and constraints	High mix, changeover-heavy lines
Dispatching production units	Pushes the right job to the right workstation at the right time	Multi-step routings, cells
Document control	Serves work instructions, drawings, SOPs at the point of use	Regulated or high-variant production
Data collection / acquisition	Captures counts, times, parameters from machines and operators	Every plant — this is the foundation
Labour management	Tracks operator time, skills, certifications	Labour-intensive assembly
Quality management	In-process checks, SPC, non-conformance handling	Regulated sectors, high scrap cost
Process management	Monitors and corrects the process against limits	Process and batch industries
Maintenance management	Links equipment events to maintenance work	Asset-intensive plants (often handled by CMMS)
Product tracking & genealogy	Full as-built record: which lot, which machine, which operator	Traceability requirements (food, pharma, automotive, aerospace)
Performance analysis	OEE, cycle time, yield, downtime Pareto vs targets	Every plant — usually the first business case

Most manufacturers under a few hundred employees actually run on three of these: data collection, performance analysis and (sometimes) traceability. That gap between "what MES can do" and "what we will use in year one" is why MES projects overrun — and why the lighter production-monitoring category has grown so fast.

Where MES sits: ISA-95 in one picture

ISA-95 level	System	Time horizon	Example question it answers
Level 4	ERP / business planning	Weeks – months	What should we make this month, and what did it cost?
Level 3	MES / MOM	Shifts – days	Which order is running on which line right now, how far along, with what quality?
Level 2	SCADA / HMI	Seconds – minutes	What is the temperature in zone 3 and is the alarm active?
Level 1	PLC / controllers	Milliseconds	Is the cylinder extended and the sensor made?
Level 0	Physical process, sensors, actuators	Real time	—

Two consequences follow. First, an MES is only as good as its Level 1–2 connections: if machine data arrives by clipboard, the "real-time" MES is a real-time form. Second, the ERP integration (order download, actuals upload) is where most MES budgets and delays actually go, not in the software licence.

MES vs OEE / production-monitoring software

This is the comparison buyers most often get wrong. Production-monitoring platforms (often called OEE software) automate the data collection and performance analysis functions of the MESA model — and increasingly add operator terminals, reason coding, andon and light traceability. They do not do detailed scheduling, recipe enforcement or full genealogy.

Criterion	Full MES	OEE / production monitoring
Core purpose	Execute and document orders	Measure and reduce losses
MESA functions covered	8–11	2–4
Typical deployment	Months, per-site configuration, integrator	Days to weeks, sensor or PLC connection
Machine connectivity	Usually via PLC/SCADA, controller-specific	Sensor-agnostic (current, vibration, optical) or PLC/OPC UA/MTConnect
Who uses it daily	Planners, supervisors, quality, IT	Operators, team leads, CI engineers
Best fit	Regulated, traceability-driven, complex routings	Discrete/packaging plants where downtime and speed losses dominate

A useful rule: if your first-year business case is written in terms of OEE points, downtime hours or changeover minutes, start with production monitoring. If it is written in terms of traceability, compliance or scheduling accuracy, you need MES scope. Many plants run both — monitoring feeds the MES/ERP with clean machine actuals.

How to choose an MES in 2026: a selection checklist

• Write the year-one use cases first. Which MESA functions must work in the first 6 months? Everything else is roadmap, not requirement.
• Audit machine connectivity. List every machine with controller type, age and available protocol (OPC UA, MTConnect, Modbus, proprietary, none). Machines with "none" need retrofit sensors — check the vendor supports them natively.
• Define the OEE and loss model up front (ISO 22400 gives standard definitions). A system that cannot reproduce your OEE calculation to the decimal will be distrusted on the floor.
• ERP integration scope: which objects flow which way (orders, BOMs, confirmations, consumption) and who owns the mapping.
• Operator experience: reason-code entry in under 5 seconds, works with gloves, tolerates network drops. Adoption dies here, not in the boardroom.
• Deployment model: cloud, on-premise or hybrid; who patches it; what happens when the internet link fails (edge buffering).
• Pricing model: per machine, per site, per user — and what hardware, integration and annual maintenance add. See our OEE software pricing guide.
• Exit path: data export in open formats, API access, no lock-in of your own production history.

Implementation sequence that works

Plants that get value in the first quarter tend to follow the same order: (1) connect the machines and get trusted automatic run/stop and count data; (2) add operator reason codes for stops and quality; (3) publish live OEE and downtime Pareto on the floor and in the daily meeting; (4) only then integrate orders and scheduling. Reversing the order — orders and scheduling first — means the system is running on manual data for months.

The scale of what the first three steps alone can deliver is well documented: at Hutchinson, a TeepTrak deployment focused on measuring and attacking losses took OEE from 47% to 72%.

Frequently asked questions

What is the difference between MES and ERP?

ERP plans and accounts for production at the business level (orders, inventory, cost) over weeks and months; MES executes and documents those orders on the shop floor in real time — which machine, which operator, how many good parts, what went wrong. In ISA-95 terms ERP is Level 4 and MES is Level 3.

What is the difference between MES and SCADA?

SCADA supervises and controls equipment and process variables (Level 2) — temperatures, pressures, alarms. MES manages production orders, materials, people and quality across the plant (Level 3). SCADA tells you the oven is at 180 °C; MES tells you which batch is in it and whether it is on schedule.

Can OEE software replace an MES?

For plants whose priority is measuring and reducing losses — downtime, speed loss, scrap — modern production-monitoring platforms cover the data collection and performance analysis functions of MES at a fraction of the deployment effort. They do not replace detailed scheduling, recipe enforcement or full genealogy.

How long does an MES implementation take?

It depends on scope and connectivity: monitoring-focused deployments with retrofit sensors are typically live in days to weeks per site; full MES with ERP integration, scheduling and traceability is typically a multi-month project per site with an integrator. The ERP interface and machine connectivity usually drive the timeline more than the software itself.

What does MES stand for?

MES stands for Manufacturing Execution System. The broader term MOM (Manufacturing Operations Management), used in ISA-95, covers the same Level 3 scope including quality, maintenance and inventory operations.