ISA-88 (also published as IEC 61512) is the international standard for batch process control: it defines how recipes, equipment, and procedures should be modeled so that making a product becomes a structured, repeatable execution instead of a tangle of custom PLC code. If your plant makes anything in batches, food, beverage, pharma, chemicals, coatings, ISA-88 is the grammar your automation and MES layers should share.
Before ISA-88, the knowledge of how to make a product was welded into control code: changing a mixing time meant changing a PLC program. The standard splits the world in two. The recipe describes what to do: procedures, operations, phases, and parameters like temperatures and durations. The equipment model describes what the plant can do: units, equipment modules, and control modules exposing capabilities such as heat, agitate, or transfer. Execution marries the two at runtime: the recipe asks for "heat to 80 for 20 minutes" and the unit’s phase logic delivers it. New product variants become new recipes, not new code.
A process cell has a 2,000 liter mixing unit with phases: charge water, charge concentrate, agitate, heat, hold, transfer. Product A’s recipe calls charge 1,400 liters, agitate 10 minutes, heat to 65, hold 15. Product B reuses the same six phases with different parameters; Product C skips heating entirely. Three products, zero new control code, and every batch execution produces the same structured record: which phases ran, with which parameters, on which unit, with which deviations. When quality asks six months later why batch 4711 gelled, the answer is a query, not an archaeology project.
ISA-88 gives loss analysis a vocabulary. When performance data is recorded against units and phases, you can see that the heat phase on Unit 2 has stretched from 20 to 27 minutes over three months, a fouled heat exchanger announcing itself, or that transfers wait on a shared pump, a scheduling constraint worthy of the theory of constraints. Batch plants that measure OEE without phase context see that a unit was slow; with it, they see which step was slow and why.
The two standards are siblings: ISA-95 governs how operations talk to the business layer across all manufacturing types, while ISA-88 governs procedural control inside batch operations. In practice the ISA-88 physical model plugs into the lower levels of the ISA-95 hierarchy, and batch execution systems report production performance upward in ISA-95 terms.
Fabrico is not a batch execution system and does not run recipes. It is the performance and maintenance layer around them: real-time production monitoring shows run, wait, and stop time per unit (computer vision covers vessels and lines with no usable control data), and the CMMS holds the unit hierarchy, work orders, spare parts, and preventive schedules that keep phase times honest. Slow-drifting phases become maintenance evidence instead of folklore. EU-built, with EU data residency.
No. It originated across process industries and fits any batch or semi-batch operation: food, beverage, specialty chemicals, coatings, cosmetics. Pharma leans on it heavily because structured recipes and batch records align with GMP expectations, including qualification work like IQ/OQ/PQ.
In ISA-88 terms the procedure is the structural part of a recipe: the ordered logic of unit procedures, operations, and phases. The recipe adds everything else needed to make the product: header information, formula parameters, and equipment requirements.
Yes. Modern stacks change how data moves, not what batch logic is. Phases, units, and recipes remain the working abstraction inside batch automation, and newer architectures typically expose ISA-88 structured execution data through modern transports rather than replacing the model.
Want unit-level performance and maintenance data that makes your batch records worth reading? Book a Fabrico demo to see real-time OEE and a field-ready CMMS working across your process cells.
Connexion
Blog
