Key takeaways
- An MES records what actually happened in production; your ERP records what was planned.
- It links work orders, material consumption, machine data and quality checks into one traceable record.
- Most plants adopt one when spreadsheets stop answering “where is this order right now?”
- You do not need the whole thing on day one — start with the question costing you most.
A manufacturing execution system (MES) is software that manages and records what actually happens on the factory floor — from the moment a work order is released to the shop until the finished goods, the scrap and the quality results are all accounted for. If your ERP tells you what you promised to make, your MES tells you what you really made, from which materials, on which machine, and how well it went.
That distinction sounds small. In practice it is the difference between a plant that can answer questions and one that guesses.
What an MES actually does
The term covers a lot of ground, and vendors define it generously. Strip away the marketing and most systems are doing five jobs.
1. Work order execution
The MES takes a production order and turns it into something an operator can act on: which product, which route, which operations in which sequence, on which resource. It then tracks progress operation by operation, so “in progress” means something more precise than a status field somebody updates at the end of a shift.
2. Material and BOM consumption
As production runs, materials are consumed against a bill of materials. A good MES records what was actually issued rather than what the BOM assumed — including overdoses, substitutions and the partial pallet somebody opened at 3am. This is where most of the variance between theoretical and real material cost hides.
3. Machine and process data
Modern equipment already produces data: cycle counts, temperatures, pressures, alarms, downtime reasons. An MES reads it directly rather than asking an operator to transcribe it onto a clipboard. That is what makes it possible to see output, uptime and anomalies as they happen instead of the following week.
4. Quality
Inspections, tolerances, sampling plans and non-conformance handling live alongside production rather than in a separate binder. When a check fails, the system knows which order, which batch and which machine it failed on.
5. Traceability
All of the above combine into a record you can walk backwards. Given a finished unit, which raw material lots went into it? Given a suspect raw material lot, which finished units are affected — and where did they ship? For regulated industries this is mandatory. For everyone else it is the difference between a targeted recall and a catastrophic one.
Your ERP tells you what you promised to make. Your MES tells you what you actually made.
Where an MES sits: between the ERP and the machines
The clearest way to understand an MES is by what it is not.
Your ERP integrates the business: purchasing, inventory, finance, sales orders, planning. It is excellent at the commercial and supply-chain layer, and it generally operates in units of days and orders.
Your machines, SCADA and HMI systems operate in units of seconds and signals. They know a great deal about the physical process and almost nothing about the business context around it.
The MES is the translation layer in between. It takes a planned order from the business layer, drives it through the physical layer, and reports back what really happened in terms the business can use. Without it, that gap is filled by paper, spreadsheets, a few local databases and institutional memory — which is exactly why plant data so often turns out to be scattered, late and mutually contradictory.
Signs you have outgrown spreadsheets
Very few plants adopt an MES because they read an article about one. They adopt it because something specific stopped working. The common triggers:
- Nobody can answer “where is this order?” without walking the floor. Status exists, but only in people’s heads.
- Material variance is unexplained. You know the theoretical consumption and the actual stock movement, and the gap between them is a mystery you rediscover every month.
- A quality question takes days to answer. A customer asks which batch their shipment came from and the reply involves three people and a filing cabinet.
- Reporting is archaeology. Month-end means someone rebuilding the same spreadsheet from the same exports, and the numbers are already stale when they land.
- Downtime is invisible. Everyone agrees the line stops too often. Nobody can rank the reasons by lost hours.
In practice
If more than two of those are familiar, the constraint is not effort. It is that the data is being captured after the fact, by hand, by people whose actual job is making things. No amount of discipline fixes a collection method that competes with production.
What to look for when evaluating
A few criteria matter more than feature-count comparisons.
Does it fit how you already work? Manufacturing processes vary enormously, and a system that forces a discrete-assembly model onto a process plant will be fought and eventually abandoned. Configurability is not a luxury here.
Will operators actually use it? An MES that adds keystrokes to a busy shift will be worked around. The interface on the floor matters more than the dashboard in the office.
How long until it is live? Traditional MES implementations are measured in quarters. That is sometimes justified — and sometimes just the cost of rigid software.
What happens when your process changes? If every new product, route or quality check requires a vendor change request, you have bought a constraint rather than a tool.
Watch out for
Machine connectivity is where MES projects most often stall. Ask specifically about the equipment you own — including the older units without a modern interface. “We integrate with anything” is not an answer; ask which protocol, on which machine, and who has done it before.
Do you need the whole thing on day one?
No — and trying usually backfires. The plants that succeed tend to start with the single question that is costing them most: material variance, downtime, or traceability. They instrument that one thing properly, prove the data is trustworthy, then extend.
The advantage of a configurable platform is that “extend” does not mean a new project every time. Capitán MES manages production flow through work orders, BOMs and processes, reads data directly from your machines, and carries full in-process traceability including in-process inventory, waste and quality control — on a no-code platform you can reshape as the process changes rather than filing a request and waiting.
If you want to see how that maps onto your plant specifically, talk to our team — it is a more useful conversation than a feature list.
The short version
An MES records what really happened in production, in enough detail to act on. It sits between the ERP that plans the work and the machines that do it, and it earns its place the moment “we think” stops being an acceptable answer.