What Is MES: Manufacturing Execution System Explained
Basics4 minInnovialabs editorial team
In short
An MES runs production execution in real time: it issues work orders to shop floor areas, collects actual output from people and machines, controls quality and keeps the full history of every batch.
What MES is in plain terms
An MES (Manufacturing Execution System) manages production processes at the shop floor level. It sits between the plan created by management or the ERP and the real work of machines and operators.
ERP answers "what and how much to produce this month". MES answers "what should this shift do in this area", "what has actually been done right now" and "what materials and process made this batch". Its time horizon is shifts, hours and minutes.
Core MES functions
Work orders
MES turns the plan into specific work orders: which product, on which equipment, in what quantity, following which routing. An order contains the sequence of operations, standards, required materials and operator instructions.
Dispatching
Dispatching assigns work orders to work centers and shifts, taking into account load, changeovers and priorities. When a machine breaks down or material does not arrive, the dispatcher sees it in the system and reorders the queue instead of finding out at the end of the shift.
Data collection
MES collects actual production data:
- from equipment — via PLCs, sensors and industrial protocols (for example, OPC UA);
- from operators — via terminals, tablets and barcode scanners;
- about downtime — with a reason code;
- about material consumption and output.
The more data is collected automatically, the more accurate the picture and the less manual entry.
Quality control
MES embeds inspection points: which parameters to check, at which operation, with which tolerances. Measurements are recorded in the system. If a parameter goes out of range, the batch is put on hold and the responsible person is notified. Defects are caught at the operation, not at the finished goods warehouse.
Traceability
Traceability is the ability to reconstruct the history of any unit or batch: which raw materials from which delivery were used, on which equipment, in which shift, by whom, with which process parameters and inspection results. This is critical in food, pharma, automotive components and other industries with recall requirements.
Shop floor problems MES solves
| Problem | How MES helps |
|---|---|
| Management does not know what is happening on the floor right now | Real-time status of orders and equipment |
| Downtime is not recorded or its causes are unknown | Automatic downtime capture and reason classification |
| Paper shift reports full of errors | Electronic entry and automatic machine data |
| Defects are found too late | In-process inspection and batch holds |
| No way to find the root cause of a customer complaint | Full batch history |
| Costs are based on standards, not actuals | Actual material and time consumption |
MES also provides the data for OEE (overall equipment effectiveness), a metric that combines availability, performance and quality.
Who needs MES and when
Signs that a plant has outgrown spreadsheets:
- several areas or lines, and coordinating them eats up supervisors' time;
- the plan is regularly missed and causes are found after the fact;
- customers or regulators require traceability;
- capacity decisions are based on gut feeling rather than data.
A small plant with one line often does well with an ERP module or simple downtime tracking. A full MES pays off its complexity where there are many operations, machines and quality requirements.
How to approach implementation
- Set a goal: downtime, quality, traceability or scheduling. Do not try to cover everything at once.
- Survey the processes: routings, equipment, which data is available from controllers.
- Pick a pilot area — one line or one workshop.
- Set up data collection and the operator interface.
- Integrate with ERP so orders come from the plan and actuals flow back into accounting.
- Scale to the remaining areas.
Common mistakes
- Implementing without a goal — the system exists, but nobody analyzes the data.
- Manual entry for everything — operators cannot keep up and data is inaccurate.
- A complex interface for the floor — a terminal needs a few large buttons, not office-style forms.
- Ignoring network and hardware — without a stable network on the floor, data collection fails.