ISA-95 Levels in Practice: A Real-World Map
The ISA-95 level diagram is familiar, but mapping the boxes to the actual systems on your site is where it gets useful and where confusion starts. This page places real equipment at each level, from field sensors to ERP, and is honest about where modern architectures blur the boundaries. It is written for the engineer or integrator who knows the levels in theory and needs to say which of their systems sits where, and why it matters.
ISA-95 levels in practice in one line: In practice, the ISA-95 levels map like this: Level 0 is the physical process and field instruments, Level 1 is the sensing and actuating done by PLCs and I/O, Level 2 is supervisory control and monitoring done by SCADA and HMI, Level 3 is manufacturing operations management done by MES and historians, and Level 4 is business planning done by ERP. The levels describe function, not boxes, so one physical device can span more than one level.
Levels 0 to 2: The Plant Floor
Level 0 is the process itself and the instruments that touch it: the valves, the motors, and the sensors that turn a physical quantity into a signal. A pressure transmitter on a separator lives at Level 0, converting pressure into a 4-20 mA signal. Level 1 is the sensing and actuating layer that reads those signals and drives outputs, which in practice means the PLC or RTU I/O and the basic control it runs. The line between 0 and 1 is roughly the line between the field device and the controller reading it.
Level 2 is supervisory control and monitoring, the SCADA and HMI layer where an operator watches the process and intervenes. This is where the digitized field values become named tags an operator can trend and alarm on, so a Level 0 pressure transmitter feeding a Level 1 PLC surfaces at Level 2 as a SCADA tag on a screen. In practice, Levels 1 and 2 often run on overlapping hardware, which is one of the first places the neat diagram blurs.
Levels 3 and 4: Operations and Business
Level 3 is manufacturing operations management: the systems that coordinate production across the plant, such as MES, historians, batch management, and production scheduling. This is where the plant-floor data is aggregated, stored, and turned into operational information, for example a historian archiving every tag or a batch system tracking recipes. Level 3 answers how the plant is running over hours and shifts rather than second to second.
Level 4 is business planning and logistics, the ERP layer that handles orders, inventory, and enterprise scheduling. It works in the currency of the business, not the process, and it exchanges information with Level 3 rather than reaching down to the plant floor directly. The whole point of the ISA-95 model is to structure the exchange between Levels 3 and 4 so the business systems and the operations systems speak a common language, which is where the model's equipment hierarchy earns its keep.
Where the Levels Blur in the Real World
The honest truth is that modern architectures do not respect the level boundaries as cleanly as the diagram implies. A single edge device can do Level 1 control, Level 2 monitoring, and even push data toward Level 3 storage, collapsing three levels into one box. Cloud and edge computing have made the physical mapping looser, so the levels are best treated as a description of function rather than a rule about which hardware may do what. Reading them as functions keeps the model useful when the boxes overlap.
The value of the levels in practice is as a shared vocabulary for where a function belongs, not as an architecture you must build literally. When an integrator says a requirement is a Level 3 concern, they mean it is about operations management rather than real-time control, regardless of which server it runs on. This is why the model outlived the rigid stacks it grew up with, and why it maps closely to the security-oriented Purdue model that borrows its levels.
Frequently Asked Questions
What sits at each ISA-95 level?
Level 0 is the physical process and field instruments, Level 1 is sensing and actuating by PLCs and I/O, Level 2 is supervisory control and monitoring by SCADA and HMI, Level 3 is operations management by MES, historians, and batch systems, and Level 4 is business planning by ERP. The levels describe function, so one device can cover more than one.
Can one device span multiple ISA-95 levels?
Yes, and in modern architectures it commonly does. A single edge device can perform Level 1 control, Level 2 monitoring, and push data toward Level 3 storage. The levels describe functions, not mandatory hardware boundaries, so treating them as a vocabulary for where a function belongs keeps the model useful even when one box covers several levels.
How do the ISA-95 levels relate to the Purdue model?
They share the same numbered levels, and the Purdue model borrows ISA-95's hierarchy to frame OT network segmentation and security zones. ISA-95 uses the levels to structure information exchange between control and enterprise systems, while the Purdue model uses them to organize where security boundaries belong. The level numbers line up closely between the two.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.