The ISA-88 physical model is the standard's map of equipment, arranged as a strict hierarchy from the whole enterprise down to a single valve or sensor. It answers the question of what the plant is made of, in contrast to the procedural model, which describes what the plant does. Understanding the seven levels, and which of them a recipe actually cares about, is essential for anyone laying out a batch application. It also lines up neatly with the ISA-95 equipment hierarchy, so the two standards can be used together.
ISA-88 physical model in one line: The ISA-88 physical model is a seven-level equipment hierarchy: enterprise, site, area, process cell, unit, equipment module, and control module. The top three levels are organizational, the process cell is the batch boundary, and the bottom three - unit, equipment module, and control module - are where batch equipment logic actually lives.
The top three levels are organizational rather than physical in any batch-specific sense. The enterprise is the company as a whole, the site is a geographic location such as a single plant, and the area is a major subdivision of a site, often corresponding to a business or process grouping. These levels matter for scheduling, accounting, and ISA-95 style planning, but a batch recipe rarely reaches up into them.
The process cell is the pivot point. It is defined as the collection of all units and equipment needed to make one or more batches, and it is the boundary within which a batch is scheduled and coordinated. Below it, a unit is a functional collection of equipment that carries out one or more major processing activities on a batch, such as a reactor, a mixing tank, or a dryer. A unit generally operates on one batch at a time, which is why it is such an important level for batch sequencing.
The two lowest levels handle the fine detail. An equipment module is a functional group of control modules and possibly other equipment modules that performs a finite, minor processing activity, such as a metered dosing header or a temperature control assembly. The control module is the lowest level, the basic grouping of sensors and actuators that is manipulated as a single entity, such as a control valve, a motor, or a single loop. Together, units, equipment modules, and control modules form the equipment that phases actually drive.
Only some levels are meaningful to a recipe. The enterprise, site, and area are essentially context: a recipe is defined for a site and targets equipment in an area, but it does not command those levels. The process cell defines the pool of equipment a batch can draw on, so it scopes what a recipe can use, but the recipe still does not issue commands to a cell as such.
The unit is the highest level a control recipe truly binds to. When a batch is instantiated, its unit procedures are allocated to specific units, so the unit is where procedural logic and physical equipment meet. Equipment modules and control modules sit below the recipe's direct control; the recipe commands a phase, and the equipment phase logic inside the unit orchestrates the equipment modules and control modules to carry it out.
This is why SCADA and DCS engineers spend most of their time in the lower three levels. Configuring a batch cell means defining the units, building the equipment modules that give each unit its capabilities, and wiring the control modules to real I/O. The upper levels are largely a matter of naming and organization, while the units, equipment modules, and control modules are where the actual automation is built and maintained.
ISA-95, the standard for enterprise-to-control integration, shares the top of ISA-88's hierarchy almost exactly. Both begin with enterprise, site, and area, which is deliberate: the two standards were written to interlock so that planning systems and batch systems describe the plant in the same words. Where ISA-88 continues into process cell and below, ISA-95's role-based equipment hierarchy offers work centers and work units that map onto the process cell and unit levels.
For a practitioner, the alignment means a process cell in ISA-88 corresponds to a work center in ISA-95, and a unit corresponds to a work unit. This lets a manufacturing execution system speak to a batch system without a translation layer: an order handed down through ISA-95 arrives at a process cell that the batch engine already understands as an ISA-88 entity. The shared top three levels are the seam that stitches the business layer to the control layer.
In a cloud SCADA context, the same shared hierarchy helps organize field assets. A monitoring platform that models its equipment as sites, areas, and units can present operational data to planners in ISA-95 terms and to control engineers in ISA-88 terms without maintaining two separate trees. Aligning the physical model with ISA-95 up front keeps the equipment model consistent from the corporate dashboard all the way down to a single control valve.
The control module is the lowest level. It is the basic grouping of sensors and actuators that is operated as a single entity, such as a control valve, a motor starter, or an individual control loop. Control modules are assembled into equipment modules, which are in turn part of units.
A control recipe binds to units. When a batch is instantiated, its unit procedures are allocated to specific units within the process cell. The recipe does not directly command equipment modules or control modules; the equipment phase logic inside the unit orchestrates those lower levels to carry out each phase.
The two standards share their top three levels, enterprise, site, and area, by design. Below that, an ISA-88 process cell aligns with an ISA-95 work center and an ISA-88 unit aligns with an ISA-95 work unit. This shared structure lets planning systems and batch systems describe the plant with a common equipment model.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.