Manufacturing Glossary

What is MES? A Practical Guide for Plant Managers

By Mahasys Multi Zenith · Manufacturing software for Indonesian plants · Last updated June 2026

A Manufacturing Execution System (MES) is software that tracks production execution in real time on the factory floor — recording what was made, when, by which machine, and where time was lost. It sits between ERP (which plans the business) and SCADA or PLC controls (which run the equipment), converting plans into accountable execution data.

Where MES sits in your plant

Industrial systems are typically described as a stack of five levels, formalized in the ISA-95 standard. The bottom layers — Level 0 (the physical equipment) and Level 1 (sensors and actuators) — run the machine. Level 2 (SCADA, HMI, control loops) supervises real-time control. Level 4 (ERP) handles business planning, finance, and order management. Level 3, between them, is where MES lives.

MES is the translator. It takes the plan that came down from ERP — "we need 4,000 of part A by Tuesday" — and turns it into shop-floor execution that can be measured, recorded, and reported on. It also takes shop-floor reality back up the stack: which work order is actually running, how many good parts were produced, where the line went down, and why.

A short history

MES emerged in the 1990s as plants began to recognize a gap. ERP systems were good at planning and accounting but knew nothing about what happened on the floor. SCADA systems knew everything about individual machines but nothing about business orders or downstream consumers. Plant managers were stuck assembling the picture by hand.

The Manufacturing Enterprise Solutions Association (MESA) formalized the category in 1997 with the MESA-11 model, which listed eleven core MES functions including production tracking, dispatching, document management, performance analysis, and maintenance management. The model has been refined since, but the central idea hasn't changed: MES is the system of record for shop-floor execution.

What an MES actually does

Modern MES platforms typically cover six core functions:

Production order tracking. Which work order is running on which machine, started by which operator, with what quantity target. Updated in real time, not at end of shift.
Downtime capture. When a line stops, the operator records the reason from a structured list. The system logs duration automatically. No more lost minutes.
OEE calculation. Availability × Performance × Quality, computed continuously from real data — not estimated from end-of-shift paperwork.
Genealogy and traceability. Every finished unit traces back to the raw material lot, the operator on shift, the machine settings, and the QA check that approved it.
Quality data capture. In-process inspections, abnormality reports, and signal escalation when measurements drift out of spec.
Integration with ERP and downstream consumers. Production confirmations push back to ERP. Live KPIs feed dashboards. Maintenance data flows to CMMS.

MES vs ERP vs SCADA: what's the difference?

Aspect	ERP	MES	SCADA / PLC
ISA-95 level	Level 4	Level 3	Level 2 / 1
Primary user	Finance, sales, supply chain	Plant manager, operators	Process engineers
Time horizon	Days to weeks	Minutes to hours	Milliseconds
Answers the question	What should we make?	What is happening right now?	Is the machine running correctly?
Typical data	Orders, inventory, costs	Work orders, OEE, downtime, traceability	Temperatures, pressures, motor states

In a well-architected plant, all three coexist. MES is the connective tissue: it depends on ERP to know what to make, and on SCADA to know what the machines are doing, but it owns the question that matters most to plant managers — what is actually happening on my floor right now, and what did it cost me?

What changes when you deploy MES

Downtime becomes visible in minutes, not hours. Supervisors see the issue, the duration, and the reason on a dashboard while the line is still down.
OEE becomes a real number. No more "we think we're at 75%" — the system computes it from live data and historical baselines.
Paper logs disappear. The shift handover happens through the system. Audit trail is automatic.
Production confirmations flow back to ERP automatically. Finance closes the period faster. Sales sees real shipping commitments.
Quality issues escalate as they happen. Operators flag abnormalities through the system; QA gets pinged before a bad lot ships.
Decisions move from monthly to daily. Plant reviews stop being storytelling sessions. They become focused work on what the data shows.

Common implementation challenges

Off-the-shelf doesn't fit. Every plant's process is slightly different. Generic MES platforms cover 70% of needs and require costly customization for the rest.
Operator adoption. If the shop-floor interface is hard to use in gloves, under bad lighting, with a stylus, it won't get used — and the data won't be accurate.
Integration scope. Connecting MES to ERP, SCADA, and CMMS is a project in itself. Most timeline overruns come from underestimating integration work.
Change management. Plant managers have been making decisions from paper for years. The transition to data-driven reviews takes coaching, not just software.
Network reliability. MES depends on stable connectivity on the floor. Plants with flaky Wi-Fi need an offline-capable client design.

What to look for in an MES partner

Process literacy. Have they actually stood on factory floors? Can they speak to your supervisor in the language she uses, not slide-deck language?
Customization without lock-in. The system should fit your process, not the other way around — and you shouldn't be priced into corner you can't get out of.
Pilot-first engagement. Any vendor proposing a 12-month rip-and-replace as the only option is selling you risk. The right path is a tightly-scoped pilot on one line, with a clear go/no-go before plant-wide rollout.
Operator-grade UI. Ask for a live demo on a tablet held in actual industrial gloves. If the demo is on a clean office screen, you haven't seen what your operators will see.
Ongoing support, not handoff. The first month after go-live is where most MES projects either land or fail. Make sure the team is still in the building.

Frequently asked questions

What does MES stand for? +

MES stands for Manufacturing Execution System. It is software that tracks and documents how raw materials are transformed into finished goods on the factory floor, in real time.

What is the difference between MES and ERP? +

ERP (Enterprise Resource Planning) handles business-level processes like sales orders, purchasing, inventory accounting, and finance. MES handles shop-floor execution: which work order is running on which machine right now, how much was produced this hour, why the line was down, and what the OEE is this shift. ERP plans what should happen; MES records what actually happens.

Do I need MES if I already have ERP? +

For any plant beyond a small job shop, yes. ERP cannot tell you in real time which machine is producing which part, where downtime is happening, or what your true OEE looks like — that data lives at the shop floor. Without MES, plant managers rely on paper logs and end-of-shift Excel reports, which means decisions are made on stale data.

What is OEE and why does MES calculate it? +

OEE (Overall Equipment Effectiveness) is the standard benchmark for production efficiency: Availability × Performance × Quality. A truly accurate OEE number requires real-time data on planned production time, run time, ideal cycle time, actual cycle time, total parts produced, and rejected parts — exactly the data MES captures. Without MES, OEE is a guess.

How long does MES implementation take? +

A focused pilot on one production line typically runs 8 to 12 weeks from discovery to go-live. A plant-wide rollout follows in phased waves over 3 to 6 months, depending on how many lines, equipment integrations, and downstream consumers (ERP, dashboards) are in scope.