What Is a Plant Operating System? A Plain Definition for Plant Leaders
DBR77 Team7 min read
On this page
A plant operating system is one software system that runs the daily work of a factory: production, maintenance, quality, warehouse and safety, on one shared data model. It takes signals from machines and people, turns them into tasks with an owner and a deadline, and checks that the work was done. ERP still plans the business. The plant operating system runs the shop floor.
The name comes from computing: an operating system lets many programs share one computer, and a plant operating system lets production, maintenance, quality and the warehouse share one record of machines, orders, materials and people.
Where a plant operating system sits
The ISA-95 standard gives the most useful map. Levels 0 to 2 cover the physical process, sensors and PLCs. Level 3 covers manufacturing execution systems (MES) and other systems that run operations. Level 4 covers the activities of running the business, where ERP sits.
Level 3 is broader than production. The OPC Foundation's summary of ISA-95 says coordination and control must happen in at least four parts of an organization: production, quality tests and labs, warehousing and inventory, and maintenance. LNS Research uses the same four areas to define manufacturing operations management (MOM).
In most mid-size plants, those four areas run on separate tools: an MES or a spreadsheet, a CMMS or a whiteboard, quality forms, an ERP add-on for the warehouse. A plant operating system covers the whole of Level 3 as one system, with machine data coming in from below and ERP connected above.
ISA-95 puts machines, sensors and PLCs at Levels 0 to 2, and ERP at Level 4.
What a plant operating system contains
Each layer answers a different question on the shift.
| Layer | What it does | Typical modules | Question it answers |
|---|---|---|---|
| Machine data | Reads states, counts and condition values from machines | IoT | What is each machine doing right now? |
| Execution | Runs orders, stock moves, inspections, work orders, safety records | MES, WMS, QMS, CMMS, HSE, HRM | What is made, checked, moved, repaired? |
| Planning and measurement | Builds the schedule and material plan, tracks KPIs | APS, MRP, KPI | Are we on plan, and where are we losing time? |
| Tasks and communication | Turns signals into owned tasks, carries open work across shifts | Tasking, messaging | Who does what, by when, and is it closed? |
| Intelligence | Ranks issues, suggests next steps, tests changes first | AI, digital twin | What first, and what if we change it? |
Most toolsets lack the fourth layer: plants have data and screens, but no shared route from a signal to an owner to a verified fix. Why Dashboards Don't Fix Factories looks at that gap.
A plant operating system vs a set of separate tools
The difference shows up when one event touches several departments. Illustrative example: on a two-shift bottling line, the bearing temperature on a filler starts to climb at 14:10.
With separate tools, the SCADA screen shows an amber value. The operator phones maintenance. A technician adds grease and writes a note on paper. Quality does not know that two hours of bottles may have fill-level drift. The plan still assumes full speed tomorrow. At the morning meeting, four people tell the story from four systems.
With a plant operating system, the same temperature reading is one event in one data model. It opens a maintenance work order with an owner and a response time. It flags the batches filled since 12:00 for a quality check. It warns the planner that the filler may need a stop, so a changeover can move into that window. The shift lead sees the open work order at handover.
What a plant operating system is not
Common mix-ups:
- It is not a bigger MES. It includes MES functions and adds maintenance, quality, warehouse, planning and tasks on the same data. Plant Operating System vs MES vs ERP compares the two.
- It does not replace ERP. ERP keeps finance, purchasing and the master plan. The plant operating system connects to it and sends back closed records.
- It is not a dashboard on top of old systems. A reporting layer only reads data, while a plant operating system also creates work and closes it.
- It is not a big-bang project. A plant can start with one or two modules on one line. The order matters more than the scope; How to Unify MES, WMS, QMS and CMMS Without Replacing Everything explains how to choose it.
How to tell if your plant needs one
Not every plant does. A single-line plant with a stable product can run well on a good MES and a disciplined morning meeting. The case grows with the number of handoffs between departments. Five signs they are costing you:
- The same event is typed in twice or more. A stop goes into the MES, again into the CMMS, and again into the shift report.
- KPIs differ by department. Production and finance report a different OEE or scrap rate for the same week.
- Issues live in chats and emails. Nobody can say how many problems are open on a line right now.
- Quality learns about machine problems late, often from a customer complaint or an audit.
- The plan is rebuilt by hand every time a machine stops or material arrives late.
If three or more apply, the gap is the connection between your tools. McKinsey's 2018 survey of more than 700 manufacturers found that less than a third had moved critical digital use cases into large-scale rollout.
How this works in DBR77 IRIS
DBR77 IRIS is a plant operating system with modules for production (IRIS MES), warehouse (IRIS WMS), quality (IRIS QMS), maintenance (IRIS CMMS), planning (IRIS APS and IRIS MRP), KPIs, safety (IRIS HSE), workforce (IRIS HRM) and ESG. All modules share one data model, so adding a module is configuration, not a new interface. Machine data comes from DBR77 IIoT, and changes to layout or flow can be tested first in DBR77 DT.
In IRIS Tasks every task moves through the same states: open, in progress, review, done and verified. Open tasks carry over at handover and become overdue alerts when the deadline passes. The IRIS assistant answers questions about plant data on any screen, and Data & AI proposes recommendations that a person applies, approves or rejects. If your policies require it, IRIS can run in a private cloud or in your own data center.
Most plants start with machine data, MES and KPIs on one line, then add maintenance, quality and warehouse. For the full module list, see the IRIS platform and the plant operating system overview.
FAQ
Is a plant operating system the same as MOM?
Close. MOM describes the activities at ISA-95 Level 3. A plant operating system is one system that runs them on a shared data model, with tasks and AI built in.
Does a plant operating system replace ERP?
No. ERP plans the business. The plant operating system runs the floor and exchanges orders and closed records with ERP.
Where should a plant start?
With one line and one painful handoff, for example machine stops that maintenance retypes by hand. Fix that loop first, measure it, then add the next module.
Conclusion
Check the five signs against your own plant. If three or more apply, start with the handoff that costs the most on one line, keep ERP and the existing tools connected, and add modules once that loop runs. If fewer apply, a good MES and a disciplined morning meeting may be enough for now.
Sources
- ISA, ISA-95 Standard: Enterprise-Control System Integration
- OPC Foundation, OPC 10030 ISA-95 Common Object Model: ISA-95 Summary
- LNS Research, What Is Manufacturing Operations Management?, 2012
- McKinsey & Company, How digital manufacturing can escape "pilot purgatory", 2018