ISA-88 gives batch processes two parallel structures: a physical model that describes equipment and a procedural model that describes the ordered logic of making a product. The procedural control model is the part that answers the question of what happens, and in what sequence, to turn raw materials into a finished batch. It breaks that logic into four nested levels so that a recipe can be written once and run on many different pieces of equipment. This separation of procedure from equipment is one of the most powerful ideas in modern batch automation.
ISA-88 procedural control model in one line: The ISA-88 procedural control model is a four-level hierarchy - procedure, unit procedure, operation, and phase - that describes the ordered sequence of actions a batch performs. It captures the logic of making a product independently of the equipment, so the same procedure can be executed on different units.
At the top sits the procedure, which represents the entire strategy for making a batch of a product from start to finish. A procedure is composed of unit procedures, each of which is a self-contained sequence carried out within a single unit, such as a reactor or a blend tank. A batch often moves through several units in turn, so a procedure typically strings together several unit procedures.
Inside a unit procedure are operations. An operation is a major processing activity that usually takes the material through a significant state change, such as a reaction, a crystallization, or a dilution. Operations give the procedure its coarse structure and are often the level at which operators think about progress: charging, reacting, cooling, discharging.
The smallest procedural element is the phase. A phase is a single, well-defined action such as add ingredient, agitate, heat to setpoint, or hold for a time. Phases are where the procedure actually issues commands that move real material and energy. Every higher level is built from phases: operations from phases, unit procedures from operations, and the whole procedure from unit procedures.
Imagine an operation that prepares an intermediate by mixing two liquids, heating the mixture, and cooling it back down. In ISA-88 terms this operation decomposes into a short chain of phases. First a charge phase adds ingredient A to a target quantity, then a second charge phase adds ingredient B. An agitate phase starts the mixer, a heat phase ramps the jacket to the reaction temperature and holds it, and finally a cool phase brings the batch back to a safe transfer temperature.
Each phase in that chain has a clear beginning and end and a small set of parameters: a target quantity, a temperature setpoint, a hold time. The operation orders those phases, sometimes strictly in sequence and sometimes with parallel or conditional branches, for instance running agitation continuously while heating proceeds. Roll several such operations together within one reactor and you have a unit procedure; chain the reactor's unit procedure to a downstream filtration unit procedure and you have the full procedure.
The value of writing the recipe this way is that the mix-heat-cool logic is expressed in generic terms. The heat phase says heat to setpoint and hold; it does not say which valve or which PID loop to actuate. That binding is left to the equipment, which is exactly what lets the next level of the standard, equipment phase logic, take over the physical control while the procedure stays portable.
Because the procedural model describes only the ordered logic, the same procedure can run on different equipment as long as that equipment can perform the required phases. A plant with three interchangeable reactors can run one validated procedure on whichever reactor is free, because the procedure references a heat phase and a charge phase generically and the equipment supplies the concrete implementation. This portability is what keeps recipe libraries small and approvals reusable across a whole cell.
For teams running SCADA over distributed assets, the same discipline pays off even outside a classic reactor hall. A cloud SCADA platform monitoring wellsites, terminals, or blending skids benefits from expressing repeatable field procedures as ordered, parameterized steps rather than hard-wiring them to one location's tags. When the logic of a task is kept separate from the specific I/O of a site, an operator can apply the same tested sequence to many sites and read progress in the same procedural terms everywhere.
The separation also sharpens exception handling and reporting. Because every action lives in a named phase within a named operation, a hold, an alarm, or a deviation can be pinned to an exact point in the sequence, and the resulting batch record reads as a clean tree of procedure, operation, and phase. That structured trail is far easier to audit and to feed into cloud dashboards than a flat log of setpoint changes with no procedural context.
The procedural model describes the ordered sequence of actions that makes a product, using procedure, unit procedure, operation, and phase. The physical model describes the equipment that can perform actions, using process cell, unit, equipment module, and control module. Keeping them separate lets one procedure run on many equipment sets and one equipment set run many procedures.
A phase is the smallest procedural element, a single defined action such as charge, heat, or hold. An operation is a larger processing activity built from several phases, typically taking the material through a meaningful state change like a reaction or a crystallization. Operations give structure to the sequence, while phases do the actual commanding.
Not always. Simple batches carried out entirely in one unit may collapse the hierarchy, with a unit procedure containing just a few operations and phases. The four levels are a framework, and implementations use as many as the process needs; a single-unit batch may barely distinguish procedure from unit procedure while a multi-unit train uses every level.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.