What Is an MES?

Back to Blog

What an MES Does

An MES coordinates the execution of production. Typical functions include detailed scheduling and dispatching of work orders, tracking materials and product genealogy (what went into each unit and where it came from), collecting production and quality data, managing work instructions, and reporting performance metrics like yield and downtime. It answers the operational questions ERP cannot: what is being made right now, on which line, with which materials, and to what quality.

The MES draws real-time data from the control layer - PLC, DCS, and SCADA - and hands finished production and inventory results up to ERP. This makes it the translation layer between the fast, physical world of the plant floor and the slower, financial world of the enterprise. In heavily regulated industries, the MES is also where electronic batch records and compliance documentation are captured.

MES and Its Neighbors

MES is easy to confuse with SCADA and ERP, but each has a distinct job. SCADA monitors and controls equipment in real time. ERP plans the business - orders, procurement, finance - over days and weeks. MES fills the gap between them, managing the execution of production shift by shift. SCADA data feeds the MES; MES results feed the ERP.

MES is fundamentally a discrete- and batch-manufacturing concept - think automotive, pharmaceuticals, food and beverage. In oil and gas, classic MES is less common; upstream and midstream operations lean on SCADA, production accounting, and hydrocarbon allocation systems that play a similar Level 3 role without always carrying the MES label. Where a Level 3 system needs live field data, a cloud SCADA platform like Merobix can supply it through APIs after reading devices over Modbus, OPC UA, and other protocols.

The ISA-95 Stack at a Glance

The cleanest way to place an MES is the level model from ISA-95, which assigns each class of system a layer and a time horizon:

Level	What lives there	Time horizon
Level 4	ERP: orders, procurement, finance	Days to months
Level 3	MES and operations management	Shifts and days
Level 2	SCADA and HMI supervision	Seconds to minutes
Level 1	PLCs, RTUs, and basic control	Milliseconds to seconds
Level 0	Sensors and actuators on the process	Continuous

The value of the model is not academic tidiness; it is that each boundary is an interface someone has to build and maintain. The Level 3 to Level 4 boundary carries orders down and production results up. The Level 2 to Level 3 boundary carries live process data up and, sometimes, setpoints or recipe parameters down. Most MES project pain lives at those two boundaries, not inside the MES itself. When someone proposes that the MES should talk directly to the PLCs, the model is also the polite way to explain why that couples the enterprise to the process and usually ends badly.

Integrating an MES with the Control Layer

An MES consumes control-layer data with context attached: not just a flow value, but which order, material, and batch that flow belonged to. Building that context is the real integration work. The plumbing is comparatively standard - OPC UA or database exchange upward from SCADA, and structured message models derived from ISA-95 for the traffic between MES and ERP - but mapping raw tags to orders and materials is site-specific engineering that no product does for you.

Three integration details decide whether the system stays trustworthy. Buffering: when the network between layers drops, production events must queue and forward, not vanish, or genealogy develops holes. Time: every layer must share a synchronized clock and a declared time zone, or batch records will show effects preceding causes. And transactions: an MES speaks in discrete events - order started, batch complete - while the control layer streams values continuously, so something must reliably detect the moment a streamed process crossed an event boundary.

Traffic downward deserves its own caution. An MES that writes setpoints or recipe parameters into the control layer is now part of the control narrative: writes must be permissioned, logged, range-checked at the receiving controller, and designed to fail safe when the MES is offline. Many sites deliberately keep Level 3 read-only against the process and route every change through the operator and the HMI instead - a slower loop, but one with a human accountable inside it.

Do You Actually Need an MES?

The honest test is regulatory and traceability pressure. If your industry requires electronic batch records, enforced work instructions, or unit-level genealogy - pharmaceuticals, food, medical devices - an MES or equivalent is essentially non-optional. If what you need is production visibility, downtime tracking, and performance reporting, a well-built historian with dashboards and reports may cover it at a fraction of the complexity, and you can grow into Level 3 functions later.

In oil and gas the answer is usually a Level 3 system, but not a classic MES. Production accounting, hydrocarbon allocation, and field data capture fill the same layer for a continuous-flow business that has no discrete units to serialize. The ISA-95 questions still apply - what comes down, what goes up, who owns the interfaces - even when nothing on the purchase order says MES. The label matters less than the interfaces; buy or build the functions you can name, and let the architecture diagram call the box whatever it likes.

Frequently Asked Questions