ISA-88, widely called S88, is the standard that brings structure and shared terminology to batch process control. It separates what a plant is built from, its physical equipment, from what a product is made by, its procedure or recipe, so the same equipment can run many products and the same recipe can move between compatible units. That separation is the core idea that makes modern batch automation, recipe management, and flexible manufacturing possible.
ISA-88 (S88 batch) in one line: ISA-88, or S88, is the standard for batch process control that defines a physical model of equipment and a separate procedural model of recipes. By keeping equipment definitions independent of recipes, it lets one set of equipment make many products and lets recipes be reused, scaled, and managed cleanly.
The physical model organizes a facility into a hierarchy of nested equipment. At the broadest levels sit the enterprise, the site, and the area, which describe the business and geographic structure. The interesting part for batch control is below that: the process cell, the unit, the equipment module, and the control module.
A process cell is the collection of equipment needed to make a batch. A unit is a major piece of equipment, such as a reactor or a mixing tank, that carries out one or more major processing steps and typically holds the batch material during those steps. Within a unit, equipment modules are functional groups of devices that carry out a defined minor function, like a dosing or heating package, and control modules are the lowest level, individual valves, pumps, and instruments.
The value of this hierarchy is that it defines equipment capability independently of any particular product. A unit knows how to heat, mix, or transfer; it does not care which product it is making. Because the physical model describes what the equipment can do rather than what it is doing right now, the same unit can host many different recipes over time.
Running parallel to the physical model is the procedural model, which describes the sequence of actions that turns raw materials into product. It, too, is a hierarchy: a procedure is carried out by unit procedures, each unit procedure is made of operations, and each operation is made of phases. A phase is the smallest procedural element, a single defined action such as charge, heat, hold, or transfer, and phases are where the procedure actually touches the equipment.
This procedural structure lives inside a recipe. A recipe binds together the formula, the procedure, and the equipment requirements needed to make a specific product, and S88 distinguishes recipe types, from a general recipe that is equipment-independent down to a control recipe that is tied to the actual equipment for one batch. Keeping the recipe separate from the equipment is what lets the same procedure scale between units and lets a product be defined once and produced many times.
The pairing of the two models is the elegant part. A recipe phase, say heat, is written against a generic capability, and at run time it is mapped to the equipment phase in whichever unit is actually assigned to the batch. That mapping between the procedural and physical models is the mechanism that gives batch systems their flexibility.
Batch processes dominate chemicals, food and beverage, pharmaceuticals, and many oilfield water-treatment operations, where product is made in discrete, repeatable runs rather than a continuous flow. S88 gives these operations a common vocabulary and a clean way to manage recipes, so a new product becomes a new recipe rather than a rewrite of the control code, and quality and traceability follow the batch from charge to transfer.
In produced-water and other batch treatment, an operation might dose a chemical, mix for a set time, let solids settle, and then decant, each a phase in an S88 sense. Structuring the automation this way makes the sequence auditable and repeatable, so every batch follows the same defined steps and the record shows exactly what happened and when.
A cloud SCADA platform like Merobix fits naturally alongside S88-structured operations by capturing the outcome of each batch and each phase for remote visibility. Because the procedure is broken into defined phases and units, the trended data and event log map back to recognizable steps, so an operator watching remotely can see which phase a batch is in, confirm it completed, and review the record of past batches without being on site.
The physical model describes the equipment hierarchy, from process cell down through units, equipment modules, and control modules, and it defines what the equipment can do. The procedural model describes the sequence of actions, from procedure down through unit procedures, operations, and phases, and it defines what a product is made by. Separating the two lets one set of equipment run many recipes and lets recipes be reused.
A phase is the smallest element of the procedural model, a single defined action such as charge, heat, hold, or transfer. Phases are where the procedure actually commands the equipment, and operations are built from phases, unit procedures from operations, and the overall procedure from unit procedures. Breaking a recipe into phases makes each batch repeatable and auditable.
S88 is simply the common shorthand for the ISA-88 standard, referring to the same batch control model. Both names describe the standard that defines the physical and procedural models for batch process control. It is unrelated to pipeline batching, which is a different concept about moving distinct product slugs through a single line.
Safety & engineering notice. This article is general educational information, not site-specific engineering, safety, or legal advice, and it does not reflect any particular facility. Standards and regulations (for example OSHA, API, IEC, ISO, NFPA, NIST, and NERC CIP requirements) change and vary by edition, jurisdiction, and application. SCADA and remote monitoring cannot verify physical isolation, atmosphere, lockout/tagout, permit status, or a safe go/no-go decision. Qualified personnel must perform site-specific engineering, hazard analysis, and safety review, and confirm current requirements with the authority having jurisdiction, before acting.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.