ISA-88.
ISA-88, also IEC 61512 is the international standard for batch control. It defines a hierarchy of physical equipment, recipes, and procedural elements that lets a batch BPCS execute the same recipe consistently across different equipment trains. ISA-88 underpins essentially every modern batch automation system in pharma, food, beverage, and specialty chemicals.
Three drawings included on a new account.
What ISA-88 means.
ISA-88, published internationally as IEC 61512, is the standard that made modern batch automation maintainable by separating two things that used to be welded together in controller code. The recipe, which is what to make, and the equipment, which is how a given train runs. Before it, a batch sequence was hard-coded ladder, and changing a product meant editing, re-validating, and re-deploying control logic. ISA-88 defines a physical model, enterprise, site, area, process cell, unit, equipment module, control module and a procedural model, procedure, unit procedure, operation, phase, and it puts the equipment-specific phase logic in the controller while the recipe lives in a database or a batch manager that calls those phases. The payoff is that a new product becomes a new recipe rather than new code, and the validation effort shifts from re-qualifying the whole machine to qualifying one recipe against already-qualified equipment phases, which is why regulated pharma and food manufacturers adopted it most aggressively. On the P&ID the physical-model boundaries are often drawn as labelled unit or equipment-module zones, and those boundaries decide which instruments and actuators belong to which ISA-88 entity, and therefore which phase logic commands each device. That mapping from drawing boundary to equipment module is one of the inputs a commissioning team uses to organize loop folders and the batch function-block allocation, and it starts from a clean, tag-by-tag reading of the set.
The ISA-88 model in five phrases
Physical model. Enterprise -> site -> area -> process cell -> unit -> equipment module -> control module. Procedural model. Procedure -> unit procedure -> operation -> phase. Recipe model. General recipe -> site recipe -> master recipe -> control recipe. Activity model. Information flows between recipe management, production scheduling, and execution. The standard is verbose but the core insight is simple. Separate the recipe, what to make from the equipment, how to run it so the same recipe runs on different equipment trains and the same equipment runs different recipes.
Why ISA-88 changed batch automation
Before ISA-88, batch logic was hard-coded ladder. Changing a recipe meant editing PLC code, re-validating, re-deploying. ISA-88 separates recipe data from equipment phases. The phase logic lives in the PLC, DCS, the recipe lives in a database or a batch manager. New products require new recipes, not new code. The validation effort shifts from re-validating the whole machine to validating the recipe change against pre-validated equipment phases. Pharma got the biggest benefit because the regulatory cost of re-validation is so high.
The ISA-88 physical model beside the procedural model
The two hierarchies are read together: a procedural element is executed by the physical element at the matching level. That pairing is what lets the same recipe run on a different train.
| Physical model level | What it is | Matching procedural element | What that element does |
|---|---|---|---|
| Enterprise | The company | Not modelled in ISA-88 | Covered by ISA-95 instead |
| Site | A geographic production location | Not modelled in ISA-88 | Covered by ISA-95 instead |
| Area | A production area within a site | Not modelled in ISA-88 | Covered by ISA-95 instead |
| Process cell | The group of units that together make one batch | Procedure | Makes one batch of one product |
| Unit | A vessel or train that holds the batch through one major activity | Unit procedure | The part of the batch carried out in a single unit |
| Equipment module | A functional group of equipment, for example a dosing skid or a transfer header | Operation | An independent processing activity, for example charge, react or transfer |
| Control module | A single actuator or sensor group, for example one valve or one control loop | Phase | The smallest procedural step, for example open a valve or dose to a weight |
The four ISA-88 recipe levels
Each level binds one more thing. A recipe only becomes equipment specific at the master recipe, which is why a general recipe survives a plant change.
| Recipe level | Who owns it | What it fixes | What it deliberately leaves open |
|---|---|---|---|
| General recipe | Corporate process development | The chemistry, the raw materials and the quantities, in equipment independent terms | Site, units, equipment and local materials |
| Site recipe | The site | The general recipe adapted to local raw materials, units of measure and language | The specific process cell and train |
| Master recipe | Automation engineering at the site | The site recipe bound to one process cell's equipment and its available phases | The quantities and equipment selection for an individual batch |
| Control recipe | The batch execution system | The master recipe plus this batch's identifier, quantities and selected equipment | Nothing; it is the copy that is executed and recorded |
ISA-88 phase state model
The phase state machine is what makes a batch recoverable. Hold preserves the batch, stop ends it in a controlled way, abort ends it as quickly as it is safe to do so.
| State | What it means | Command that enters it | Where it can go next |
|---|---|---|---|
| Idle | Loaded and waiting to be started | Reset, from a terminal state | Running |
| Running | Executing its normal logic | Start | Complete, Holding, Pausing, Stopping, Aborting |
| Complete | Finished its work normally | Reached automatically on completion | Idle, after Reset |
| Pausing | Finishing the current step so it can pause at a defined boundary | Pause | Paused |
| Paused | Halted at a step boundary, ready to carry on | Reached automatically from Pausing | Running, after Resume |
| Holding | Driving the equipment to a defined hold state | Hold | Held |
| Held | At the hold state, with the batch preserved | Reached automatically from Holding | Restarting, after Restart |
| Restarting | Returning from the hold state to normal execution | Restart | Running |
| Stopping | Executing the controlled stop logic | Stop | Stopped |
| Stopped | Stopped; the batch cannot simply resume | Reached automatically from Stopping | Idle, after Reset |
| Aborting | Terminating as quickly as it is safe to do | Abort | Aborted |
| Aborted | Terminated | Reached automatically from Aborting | Idle, after Reset |
Common questions
Is ISA-88 only for batch.
Does ISA-88 dictate which BPCS platform to use.
How does ISA-88 affect P&ID content for batch units.
Run it on your drawings.
Upload a drawing set, get every document populated and classified, export to the format your team uses.
Three drawings included on a new account.