MES, ERP, OEE: who does what, and when to use each

Three acronyms, three needs that get confused far too often

ERP, MES and OEE measurement are three software building blocks that live side by side in industry, yet they are routinely mixed up, and that confusion carries a cost. It leads people to tie a simple need, measuring your real OEE, to a heavy project that was never meant to deliver it. Plenty of plants put off measuring their performance on the grounds that they don’t have an MES, when in fact the two answer entirely different questions.

Clarifying who does what is therefore more than a vocabulary exercise: it is a precondition for moving forward. Once you understand that each of these tools covers a distinct need, you stop subordinating everything to one grand project and you can treat performance measurement for what it is, a standalone need, quick to satisfy, that creates value immediately.

ERP: running the business

The ERP, or enterprise resource planning system, is the administrative nervous system of the company. It runs orders, purchasing, stock, overall planning and finance. Its purpose is to coordinate management information flows across the whole organisation, from order intake to invoicing.

What the ERP does not do is measure, in real time, what is happening on a production line. It knows a work order exists and has to be produced, but it has no idea whether the machine is suffering micro-stops, running below pace or stringing together slow restarts. Real OEE, to the second, lies outside its scope. Expecting an ERP to reveal shop-floor losses is asking it to do something it was never designed for.

MES: orchestrating execution on the floor

The MES, or manufacturing execution system, sits between the ERP and the machine. It manages production execution: fine scheduling, work-order tracking, traceability, quality management and shop-floor flows. It is a powerful tool, often indispensable in heavily regulated or high-traceability environments.

But the MES is also a major project. Its deployment is counted in months, mobilises IT, assumes deep integration with equipment and demands substantial change management. That scale is justified when the need is full orchestration of execution. It becomes an obstacle when the real, more modest need is simply to know your OEE. Tying measurement to an MES turns a need of a few weeks into a project of several months. Worse, it makes the easy win hostage to the hard one: the OEE figure that could have been live this week ends up waiting for a system that may not go live for a year, and during that wait the losses it would have exposed stay invisible.

The OEE measurement layer: answering one precise question

The OEE measurement layer answers a simple, standalone question: what is my real OEE, line by line, right now. It does not pretend to run the business or orchestrate execution. It measures machine performance, continuously, and renders it in a form teams can act on out on the floor. Its scope is deliberately narrow, and that is exactly what makes it strong.

Because it targets nothing but measurement, this layer is fitted in under an hour, with no MES, no production stop, on old and new machines alike. It satisfies, straight away, a need that neither the ERP nor the MES covers directly, and it does so without imposing the delay and cost of a big project. It is the right answer to a precise question, rather than a universal system.

Why OEE measurement is a standalone need

The key point is that measuring OEE doesn’t have to wait for anything. It isn’t a feature of some larger system you must deploy first: it is a need that stands on its own. A plant can perfectly well measure and improve its performance without an MES, and many sites do exactly that, with concrete results.

Recognising this autonomy frees you from all-or-nothing thinking. You are not forced to choose between doing nothing and launching a monolithic project. You can start by measuring, prove the value on one line, and then decide, with full knowledge, whether an MES is justified for other needs. Measurement becomes an accessible first step rather than a blocking dependency. And because OEE breaks down simply into Availability times Performance times Quality, the measurement layer gives you a figure that any team can read and act on without waiting for a wider system to be in place.

Making them coexist, and even complement each other

Choosing the OEE measurement layer does not mean giving up on the MES or the ERP. All three coexist perfectly well, because they cover distinct needs. OEE measurement lives alongside the MES and the ERP, and can even feed them reliable performance data, precisely where those systems often lack a precise field measurement.

That complementarity is an asset. A plant can deploy measurement quickly for immediate gains, while keeping or planning an MES for orchestration. The objective OEE figure then enriches the whole. Hutchinson improved its OEE from 42% to 75% with the same headcount and machines, sensor installed in under an hour. The gain did not wait for a complete system: it came from visibility, put in place as a standalone step.

The classic mistake: subordinating everything to the big project

The most widespread mistake is to say “we’ll measure OEE once we have the MES.” That sentence, reasonable on the surface, amounts to postponing an accessible gain indefinitely. Since the MES is a long project, measurement waits months, sometimes years, during which hidden losses keep running, neither seen nor recovered.

Reverse that logic and everything changes. Measure first, structure later: you start by making performance visible, you recover OEE points quickly, and you approach any future MES project with real knowledge of your lines rather than approximate readings. Measurement does not compete with the MES; it prepares it and makes it more relevant.

Choosing well, based on your real need

The right decision always starts from the real need. If the question is “how do I run my orders, my stock and my finances?”, that’s the ERP. If it is “how do I orchestrate and trace all of my shop-floor execution?”, that’s the MES. If it is “what is my real OEE and how do I recover it?”, that’s the OEE measurement layer, and it requires nothing but itself.

Telling these three questions apart keeps you from oversizing the answer. You don’t launch a multi-month project to answer a measurement question, any more than you expect a sensor to run your finances. That clarity about the need is what lets you move fast and well, handling each issue with the right tool. The measurement layer, installed in under an hour with first data within 48 hours, is sized exactly for the OEE question and nothing more. More than 450 plants across 30+ countries already monitor their OEE to the second with TeepTrak.

Key takeaways

The ERP runs the business, the MES runs shop-floor execution, and the OEE measurement layer answers the real OEE of your lines. Confusing the three ties a simple measurement to a heavy project, and pushes accessible gains out of reach. OEE measurement is a standalone need: it is fitted in under an hour, with no MES, and can coexist with these systems or even feed them. Measure first, structure later.

FAQ

What’s the difference between MES and ERP?
The ERP runs the business (orders, stock, finance, overall planning); the MES runs production execution on the floor (fine scheduling, traceability, work orders). Two distinct scopes, two different tools.

Do I need an MES to measure OEE?
No. Measuring OEE is a standalone need that a plug-and-play measurement layer satisfies in under an hour, with no MES and no integration project. Waiting for an MES to measure means postponing an accessible gain.

Does OEE measurement replace an MES?
No. It answers a different need (knowing your real OEE) and can coexist with an MES, or even feed it reliable performance data. The two are complementary, not competing.

What should I choose between ERP, MES and OEE measurement?
It depends on the real need: the ERP for running the business, the MES for orchestrating execution, the OEE measurement layer to know and recover your OEE. You pick the tool that fits the question, without oversizing the answer.

Can I start with measurement before an MES project?
Yes, and it is often the smartest path: measuring first makes performance visible and recovers OEE points quickly, then you approach any MES with real knowledge of your lines rather than approximate readings.