The ISA-88 Batch Model Elements, Explained
ISA-88 is often taught as a pile of terms, physical model, procedural model, recipe, phase, that are hard to hold together until you see how they interlock. This page is the map: the major model elements of ISA-88 and how they fit as a system rather than a glossary. It is written for the engineer or batch programmer who knows the individual terms and needs the picture that connects them before designing or reviewing a batch application.
ISA-88 batch model elements in one line: The ISA-88 batch model is built from three interlocking models. The physical model describes the equipment as a hierarchy from enterprise down to control module. The procedural model describes the actions as a hierarchy from procedure down to phase. The recipe ties them together, mapping the procedural steps onto the equipment for a specific product. Separating what the equipment can do from what a product needs is the core idea that makes batch control reusable.
The Physical Model: What the Equipment Is
The physical model organizes the plant equipment into a hierarchy so that batch logic can refer to it consistently. From the top it runs enterprise, site, area, process cell, unit, equipment module, and control module, each level a container for the ones below. A reactor is a unit; the agitator on it is an equipment module; the valve that lets steam into the jacket is a control module. This hierarchy is the noun side of ISA-88, the stable description of what physical things exist.
The power of the physical model is that it decouples the equipment description from any particular product. Because a process cell and its units are defined once, independent of what they make, the same equipment can run many products without being redescribed each time. The lower levels, the equipment module and control module, are where the physical model meets the actual valves and motors on the plant floor.
The Procedural Model: What the Equipment Does
The procedural model organizes the actions into a matching hierarchy: procedure, unit procedure, operation, and phase. A procedure is the whole sequence to make a product; a unit procedure is the part of it that runs on one unit; an operation is a major processing activity like charging or heating; and a phase is the smallest independently meaningful action, such as opening a valve until a level is reached. This is the verb side of ISA-88, the description of what gets done.
The phase is where the procedural model meets equipment reality, because a phase is what actually commands the control modules, and its behavior is governed by a state model that says how it starts, holds, and stops. That is why the recipe phase is the element most batch programmers spend their time on. Keeping the procedural model separate from the physical model is what lets the same action logic be reused across equipment that can perform it.
The Recipe: Binding Actions to Equipment
The recipe is the element that ties the procedural model to the physical model for a specific product. A recipe carries the procedure to follow, the formula of parameters and quantities, and the mapping onto the equipment that will run it. It is what turns the general capability of a process cell into the specific act of making one product to one specification, which is why the recipe is where product knowledge and equipment capability meet.
ISA-88 distinguishes kinds of recipe by how equipment-specific they are, from a general recipe that is product knowledge independent of any plant, down to a control recipe bound to the actual equipment for one batch. The separation of the procedural control model from the equipment it runs on is exactly what lets one product's recipe move between compatible units. Understanding the three models as a system, physical, procedural, and recipe, is what makes the individual ISA-88 terms finally click into place.
Frequently Asked Questions
What are the three models in ISA-88?
The physical model, the procedural model, and the recipe. The physical model describes the equipment as a hierarchy from enterprise to control module. The procedural model describes the actions as a hierarchy from procedure to phase. The recipe binds procedural steps to physical equipment for a specific product. Separating equipment capability from product action is the core idea.
Why does ISA-88 separate the physical and procedural models?
So that equipment and actions can be described and reused independently. The physical model defines what equipment exists without reference to any product, and the procedural model defines what actions to take without reference to specific equipment. The recipe joins them per product. This separation is what lets the same equipment run many products and the same action logic run on many units.
What is the smallest element in the procedural model?
The phase. It is the smallest independently meaningful action, such as opening a valve until a level is reached or dosing a set quantity. A phase commands the control modules directly and is governed by a state model that defines how it starts, holds, and stops, which is why it is where most batch programming effort is spent.
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.