Plant Operating System vs MES vs ERP: Who Does What in a Plant
DBR77 Team7 min read
On this page
ERP plans the business: customer orders, finance, purchasing and the master schedule, in weeks and days. MES runs production orders on the shop floor, in shifts, hours and minutes. A plant operating system covers the whole operations level: production plus maintenance, quality, warehouse and the tasks that connect them, on one data model. Most plants need ERP and MES functions. The question is whether the other three areas run inside the same system or beside it.
The three terms are often used as if they compete, but they sit at different levels, and confusing them leads to the wrong purchase.
What ERP is built to do
The ISA-95 standard puts ERP at Level 4, which covers all the activities related to running a business. In practice: sales orders, purchasing, inventory value, costing and the master plan.
The OPC Foundation's ISA-95 summary says Level 4 typically operates on time frames of months, weeks, and days. For ERP, "real time" means material and logistics information that is available daily.
That is the right speed for finance and the wrong speed for a shift lead. When a press stops at 09:20, ERP does not know, and it should not have to. Its job starts again when the order is closed and the scrap is booked.
At 11:05 a die makes burrs, and the MES records a stop and reason code.
What MES is built to do
MES sits at Level 3. SAP describes it as a system that monitors, tracks, documents, and controls the process of manufacturing goods, from raw inputs to finished products. Its record is the production order: released, started, stopped, counted, completed.
Level 3 runs on a different clock. Per the OPC summary, it works in days, shifts, hours, minutes and seconds, and "real time" means information available a few seconds after a shop floor event. That is why MES owns order tracking, counts, downtime reasons and live OEE.
SAP's summary of the MESA-11 functions also lists quality deviations, maintenance and traceability. Many MES products cover parts of those. In many mid-size plants, though, the MES was bought for production orders, while maintenance runs in a separate CMMS, quality on forms or a QMS, and the warehouse in an ERP add-on.
Where MES alone stops
Level 3 is wider than production. The OPC summary says coordination must happen in at least four parts of an organization: production, quality tests and labs, warehousing and inventory, and maintenance. An MES that covers only the first one leaves three handoffs open.
Illustrative example: on a stamping line, a die starts to produce burrs at 11:05. The MES records a quality stop and a reason code. That is all it knows.
- Maintenance hears about the die by phone and types the machine and reason again into the CMMS.
- Quality checks the last 400 parts on a paper form. The MES does not show which pallets are on hold.
- The warehouse has already moved two of those pallets to the shipping area, because the ERP add-on shows them as finished.
- The planner learns at 14:00 that the order is late and rebuilds the afternoon.
The cost sits between the systems: four people, three records and no owner for the event. For a plain definition of the term, see What Is a Plant Operating System?
ERP vs MES vs plant operating system, side by side
| Question | ERP | MES | Plant operating system |
|---|---|---|---|
| Main job | Plan and account for the business | Run and track production orders | Run all daily plant work on one record |
| Time frame | Months, weeks, days | Shifts, hours, minutes | Shifts, hours, minutes, plus open tasks across days |
| Main record | Sales order, purchase order, cost | Production order, count, stop | Order, work order, inspection, stock move, task |
| Daily users | Finance, purchasing, planning office | Operators, shift leads, production | Operators, setters, technicians, quality, warehouse, planners |
| Level 3 scope | None | Production, sometimes parts of the rest | Production, maintenance, quality, warehouse |
| After a stop | Learns later, at order close | Records it with a reason | Records it, opens owned tasks in each affected area |
| Typical gap | Too slow for the shift | Handoffs to other departments | Needs clean master data and agreed definitions |
ERP stays the system of record for money and customer commitments in every case. The difference between MES and a plant operating system is the scope of Level 3 and what happens after a signal.
How to decide what your plant needs
Four questions sort most cases:
- Does your MES cover the orders you run, and do people trust it? If yes, keep it. A plant operating system can connect to it first and replace parts later, or never.
- How many systems does one stop touch? If the answer is three or more, and each one is fed by hand, the cost sits in the handoffs between tools.
- Who owns an event that crosses departments? If nobody can answer for a quality stop that needs maintenance and a stock hold, you need a task flow, not another report.
- Is ERP being stretched to the floor? If shift leads keep side spreadsheets next to the ERP shop floor module, the answer is yes.
The order of change matters more than the vendor. How to Unify MES, WMS, QMS and CMMS Without Replacing Everything covers what to keep and what to replace, and How to Evaluate a Plant Operating System lists the questions to ask in a demo.
How this works in DBR77 IRIS
DBR77 IRIS is a plant operating system. IRIS MES runs production orders through Planned, Released, In Progress and Completed, records actual start and end times, and tracks downtime with reason codes and OEE from production data. IRIS CMMS, IRIS QMS, IRIS WMS, IRIS APS and IRIS MRP share the same data model, so an equipment failure in MES opens a corrective work order in CMMS, a failed inspection puts the received lot on hold, and order progress updates the schedule.
ERP stays in place. IRIS exchanges orders and closed records with it through its API and webhooks, and the ERP connection is set up for each project. The options are on the integrations page. Machine states and counts come from DBR77 IIoT. When to Integrate IoT with MES, ERP and CMMS sets out the order in which machine data should feed MES, CMMS and ERP.
IRIS Tasks turns cross-department events into tasks that move through open, in progress, review, done and verified. The IRIS assistant answers questions from live plant data and does not change records. Data & AI recommendations wait for a person to apply, approve or reject them, and IRIS records the outcome of each recommendation that is applied.
FAQ
Do we need both MES and ERP?
Usually yes, or at least both sets of functions. ERP plans the business, MES or a plant operating system runs the shift, and they exchange orders and closed records.
Can the production module in our ERP replace an MES?
For simple, slow processes it can. Where stops and counts matter by the minute, ERP modules tend to lag.
Can we keep our current MES?
Yes. Connect it and add maintenance, quality or tasks around it. Replace it only when the connection costs more than the change.
Conclusion
Take one recent stop and count the systems it was typed into by hand. If the answer is three or more and people trust your MES, keep it and connect maintenance, quality and the warehouse around it before replacing anything. ERP stays the system of record for money and customer commitments either way.