An MES, or manufacturing execution system, is software that manages, monitors, and documents production on the plant floor in real time. It takes the orders your business system releases and executes them: dispatching work to lines, tracking material and labor, recording quality data, and building the genealogy of what was made, when, from what, by whom.
That is the honest one-paragraph version. The longer version is that "MES" covers an enormous range, from a module that tracks work orders to a plant-wide platform that took three years to deploy. This post explains what the category actually does, where it sits, and when you need it.
What does an MES actually do?
The core functions of an MES are consistent across vendors, and roughly track the manufacturing operations management activities described in the ISA-95 standard:
- Order execution and dispatching: turning released orders into scheduled, sequenced work at specific lines and stations.
- Production tracking: counts, statuses, and progress against schedule, in real time rather than end-of-shift.
- Traceability and genealogy: which lots, materials, machines, and operators produced each unit, essential in regulated industries.
- Quality management on the line: in-process checks, holds, and nonconformance capture (often alongside a dedicated QMS).
- Resource management: labor, machines, and tooling, including who is qualified to run what.
- Performance analysis: OEE, downtime reasons, scrap, and cycle times computed from execution data.
Where does MES sit? The ISA-95 view
ISA-95 (adopted internationally as IEC 62264) is the standard for integrating enterprise and control systems, built on a five-level hierarchy often drawn as the Purdue model. The standards body ISA describes the family at isa.org: Level 0 is the physical process, Levels 1-2 are sensing and control (PLCs, SCADA/HMI), Level 3 is manufacturing operations management, where MES lives, and Level 4 is business planning, where ERP lives. Most of what ISA-95 standardizes is the conversation between Levels 3 and 4: what the ERP tells the MES to make, and what the MES reports back.
MES vs ERP vs SCADA vs AI operational layer
| ERP | MES | SCADA | AI operational layer | |
|---|---|---|---|---|
| Core question | What should we make, buy, and bill? | What is being made right now, and how? | What is this machine doing this second? | What does all of it mean, and what should happen next? |
| Time horizon | Weeks to months | Shifts to days | Seconds | Seconds to months |
| Primary users | Finance, planning, purchasing | Production supervisors, quality | Operators, controls engineers | Every role, in role-specific views |
| Data it owns | Orders, inventory, costs | Work orders, genealogy, OEE | Process values, alarms | None exclusively; it connects ERP, MES, machines, paperwork, and tribal knowledge |
| Typical failure mode | Describes the plant as planned, not as run | Long, rigid implementations | Data trapped at the machine | Only as good as the sources it connects |
The comparison with a CMMS is similar: the CMMS owns maintenance work, the MES owns production execution, and they should talk.
How do you evaluate an MES? Seven questions
- What problem, in dollars, are we solving? Traceability mandates, scrap, schedule chaos, and audit prep point to different scopes. "Visibility" alone is not a scope.
- What must it integrate with, and how? Get specific about your ERP version, your PLC brands, and who owns the interfaces when something changes.
- Who maintains it after go-live? An MES that needs a vendor engineer for every routing change will freeze your process in place.
- What is the operator experience? If data entry at the station is slower than the paper it replaces, operators will defeat it, and your data will be fiction.
- Can we deploy one line first? Insist on a scoped pilot with defined success metrics before a plant-wide commitment.
- What is the true total cost? License, hardware, integration, internal labor, and the multi-year tail of change requests. Get references from plants your size.
- What happens to the data? You should be able to get your own production history out, in bulk, in an open format. Anything less is a hostage situation.
When do you need an MES, and when is it overkill?
You likely need MES-grade capability when regulatory traceability is mandatory (pharma, medical devices, aerospace, some food), when you run high-volume discrete production where minutes of misrouting are expensive, or when a corporate customer contractually requires electronic lot genealogy.
For many mid-market plants, a full MES is overkill, at least as a first step. The classic failure pattern: an 18-month implementation scoped around last year's process, a rigid data model, and a floor that quietly returns to whiteboards. If your actual pain is that production data lives on paper and in heads, that OEE is estimated rather than measured, or that nobody can answer "what happened on line 2 last night" without three phone calls, the fix is a data foundation, not a monolith. That is the wedge Harmony takes as a manufacturing operating system: digitize the paper first, connect the ERP, MES, or QMS you already have, pull machine signals, and compute true OEE from the source, with no rip-and-replace. Plants like Chattanooga Labeling Systems replaced paper production logging with real-time visibility without a classic MES project.
An honest rule of thumb: buy an MES when a specific, named requirement demands Level 3 execution control. Build the data layer first when your problem is knowing what is happening at all.