An Introduction to ISA-88

and the Standardized Language of Batch Control

Article By Global Instruments

Before the mid-1990s, batch process automation was something of a Tower of Babel. Every plant, every vendor, and often every engineer had their own way of describing a "batch," a "recipe," or a "step." A

term that meant one thing on a pharmaceutical line might mean something entirely different at a chemical plant down the road. Reusing control logic when a formula changed was difficult, communicating requirements between process engineers and control engineers was error-prone, and every new project risked reinventing terminology from scratch.

ISA-88 changed that. Known informally as S88, and internationally harmonized as IEC 61512-1, this standard from the International Society of Automation gave batch manufacturing a common language — a shared set of models and terms that any engineer, at any plant, working with any vendor's equipment, could use to describe the same concepts in the same way. First approved in 1995 and updated in 2010, ISA-88 remains the foundational architecture underpinning virtually every modern batch control system and batch manufacturing execution system (MES) in use today.

This article introduces the core ideas behind ISA-88: the problem it solves, its three interlocking models, and why this decades-old standard remains as relevant as ever in an age of Industry 4.0 and digital manufacturing.

The Core Insight: Separating "What" From "How" From "With What"

The single most important idea in ISA-88 is a separation of concerns. Batch manufacturing involves three fundamentally different kinds of information, and the standard's genius lies in treating each one as a distinct, independently manageable model:

• What you want to do — the recipe: the formulation, the ingredients, the target parameters.
• How you do it — the procedure: the generic sequence of steps required to execute that recipe.
• With what you do it — the equipment: the physical vessels, valves, sensors, and controllers that actually carry out each step.

Before ISA-88, these three layers were frequently tangled together directly in PLC ladder logic. A recipe change often meant an engineer had to go back into the control code itself and rewrite it — a slow, error-prone, and expensive process, and one that made it nearly impossible to reuse control logic across products or equipment. By formally separating recipe, procedure, and equipment into distinct models, ISA-88 allows each to evolve independently: a marketing team can request a new flavor variant, and a supervisor can adjust the recipe's parameters, without anyone needing to touch the underlying PLC program that drives the mixer or the valve.

The Physical Model: The Equipment Hierarchy

The Physical Model describes the plant itself — its equipment, organized into a strict hierarchy where lower levels combine to form higher ones. ISA-88 defines seven levels in total, though the top three are considered business-level concepts and are not elaborated further within the standard itself:

• Enterprise — the company as a whole, potentially spanning multiple sites and product lines.
• Site — a specific physical location or facility.
• Area — a functional area within a site.
• Process cell — the logical boundary within which a single batch is executed; typically the collection of equipment needed to run a particular batch process from start to finish.
• Unit — a major piece of process equipment, such as a reactor, blender, or granulator, along with the equipment modules and control modules associated with it, collectively capable of carrying out one or more major processing activities.
• Equipment module — a functional grouping of equipment that can carry out a finite number of specific minor processing activities, such as a dosing subsystem or a heating jacket.
• Control module — the lowest level: individual devices like valves, pumps, and sensors, and the control logic that directly operates them.

It is the bottom four levels — process cell, unit, equipment module, and control module — that are of primary interest to batch process automation, since these are the levels where actual production activity takes place. This hierarchy gives every piece of equipment in a plant a precise, standardized address within the overall structure, which becomes essential when the Procedural Model needs to specify exactly where a given action should occur.

The Procedural Model: The Generic Control Instructions

If the Physical Model answers "with what," the Procedural Model answers "how." It describes the generic sequence of actions required to execute a batch, independent of any specific product formulation, using a four-level hierarchy:

• Procedure — the highest-level description of the entire strategy for making a batch of a particular product, from start to finish.
• Unit procedure — a strategy for carrying out contiguous processing on a single unit, made up of one or more operations.
• Operation — a defined series of process activities that accomplish a significant processing task, such as "charge," "react," or "cool," made up of one or more phases.
• Phase — the smallest independent element of the procedural model, representing a single, discrete process action, such as opening a valve, starting an agitator, or dosing a fixed quantity of material.

The standard is deliberately flexible here: it does not require that every level be used in every application, nor does it preclude the definition of additional hierarchical levels where useful. What it provides instead is a broad, standardized vocabulary for describing batch procedures — a vocabulary that means an engineer at one plant can describe a process to a colleague at a completely different facility, using a different vendor's control system, and be understood immediately.

Phases are particularly important in practice because they are the executable building blocks that connect procedural intent to physical action. A phase is typically linked to a specific unit or equipment module, and its execution results in a real output — an electrical or optical signal — that drives an actual valve, pump, or heater. This linkage between the Procedural Model and the Physical Model is what allows the same generic operation, say "heat to target temperature," to be executed on different physical equipment simply by binding the phase to a different unit.

The Recipe Model: Turning Procedures Into Products

The third pillar of ISA-88 is the Recipe Model, which layers actual product formulations on top of the generic procedural structure. This is organized into four recipe types, arranged from most general to most specific:

• General recipe — an enterprise-level formulation, independent of any specific site, equipment, or language, describing a product in the broadest, most portable terms.
• Site recipe — the general recipe adapted to reflect the specific raw materials, terminology, units of measure, or regulatory requirements of a particular manufacturing site.
• Master recipe — the site recipe further refined for execution on a specific process cell or equipment train, specifying exact equipment assignments, formula parameters, and process instructions.
• Control recipe — a working, executable copy of the master recipe, generated for one specific batch run, carrying that batch's unique identifiers, lot numbers, actual material quantities, and any operator-approved adjustments made during execution.

This four-tier structure is what allows a multinational manufacturer to maintain one general recipe for a product globally, while letting each site adapt it to local conditions, and letting each individual batch run carry its own precise, auditable record. When a batch MES generates a control recipe and sends it to the plant floor for execution, it is essentially instantiating the master recipe — binding its generic procedural steps to real equipment, real material lots, and a specific point in time.

State Models and Batch Control Concepts

Beyond the three core models, ISA-88 also defines standardized state models that govern how procedural elements and equipment behave during execution — concepts like running, held, paused, stopped, aborted, and completed. These states, and the standardized transitions between them, ensure that operators, supervisors, and control systems across different vendors interpret concepts like "the batch is on hold" or "the phase has aborted" in exactly the same way. This shared state vocabulary is what makes it possible for a batch MES, an operator's HMI screen, and the underlying PLC to stay synchronized and to present a consistent picture of what is actually happening on the plant floor at any given moment.

Why ISA-88 Still Matters

Three decades after its initial approval, ISA-88 remains the de facto architecture for batch control for a simple reason: the underlying problem it solves — coordinating recipe, procedure, and equipment across a diverse, evolving plant — has not gone away, and neither has the value of a shared vocabulary for describing it.

In regulated industries such as pharmaceuticals and food manufacturing, ISA-88's structure has become deeply intertwined with compliance requirements. Because the standard cleanly separates recipe content from equipment logic, recipe changes can be routed through formal change-control and approval workflows, while modifications to equipment or control-module logic can trigger separate impact analysis and requalification processes, such as installation, operational, and performance qualification (IQ/OQ/PQ). This separation gives quality and regulatory affairs teams a defensible, auditable structure for demonstrating exactly what changed, when, and under whose authority — evidence that becomes part of the electronic batch record required under frameworks like 21 CFR Part 11.

ISA-88 also underpins the relationship between batch control and the enterprise systems above it. Its companion standard, ISA-95, governs how information flows between the enterprise and control layers, and the two standards are explicitly designed to interoperate: what ISA-88 calls "recipe execution" is treated in ISA-95 as an example of "production execution management." A modern batch MES typically implements both standards together — using ISA-88 to structure how a batch executes on the floor, and ISA-95 to expose that execution to the ERP, quality, and scheduling systems that run the wider business.

Conclusion

ISA-88 endures because it solved a problem that has only grown more important with time: how to describe, in a precise and universally understood way, the relationship between what a manufacturer wants to make, the generic steps required to make it, and the specific equipment used to do so. Its three interlocking models — physical, procedural, and recipe — give engineers, operators, and quality professionals a common vocabulary that transcends any single vendor's control system or any single plant's idiosyncratic terminology. For anyone working in batch manufacturing today, from process engineers writing new recipes to MES architects designing the systems that execute them, fluency in the standardized language of ISA-88 remains as essential as it was when the standard was first written.

How Checkweighers Work:

Batch Manufacturing Execution Systems (MES):