ISA-88 Batch Control in SCADA: A Complete Guide

Introduction

If your facility runs batch processes — mixing chemicals, brewing beer, manufacturing pharmaceuticals, producing paints, or processing food — then ISA-88 (also known as S88) is the standard you need to understand. Published by the International Society of Automation, ISA-88 defines a consistent framework for designing, implementing, and operating batch control systems.

Despite being established decades ago, many facilities still run batch operations with ad-hoc PLC programs, manual recipe tracking in spreadsheets, and no standardized reporting. This guide explains what ISA-88 requires, why it matters, and how modern SCADA systems implement it.

What Is ISA-88?

ISA-88 is a standard for batch process control that separates what you want to make (the recipe) from what you make it with (the equipment). This separation is the core insight of the standard, and it enables:

• Running different products on the same equipment without reprogramming
• Scaling recipes from pilot to production
• Consistent batch reporting across products and equipment
• Easier validation for regulated industries

The standard is organized into several parts:

• ISA-88.01: Models and terminology
• ISA-88.02: Data structures and language guidelines
• ISA-88.03: General and site recipe models
• ISA-88.04: Batch production records
• ISA-88.05: Implementation models and terminology for modular equipment control

The Physical Model

ISA-88 defines a hierarchy for physical equipment:

\\\`

Enterprise

└── Site

└── Area

└── Process Cell

└── Unit

└── Equipment Module

└── Control Module

\\\`

Process Cell: A logical grouping of equipment that can execute a batch. For example, a dairy processing cell might include a pasteurizer, a homogenizer, and a filling line.

Unit: A major piece of equipment that can carry out a significant processing activity. A reactor vessel, a mixing tank, or a dryer would each be a unit. A batch is typically processed through one or more units.

Equipment Module: A functional group of control modules and equipment that can carry out a finite number of specific minor processing activities. An agitator assembly (motor + VFD + level switch) is an equipment module.

Control Module: The lowest-level directly controlled device — a valve, a pump, a sensor.

The Procedural Model

The procedural model defines how a batch is executed:

\\\`

Procedure

└── Unit Procedure

└── Operation

└── Phase

\\\`

Procedure: The complete strategy for making a batch. "Make 1,000 kg of Product X" is a procedure.

Unit Procedure: The part of the procedure that executes within a single unit. "Charge and mix in Reactor 1" is a unit procedure.

Operation: A major processing action within a unit procedure. "Heat to 80°C" or "Add Ingredient A" are operations. Operations typically run sequentially within a unit procedure.

Phase: The lowest level of procedural control. A phase is the smallest element that accomplishes a process-oriented task. "Open valve V-101," "Start agitator M-201," or "Wait for temperature > 75°C" are phases. Phases are where the control system actually sends commands to equipment.

Why This Hierarchy Matters

The hierarchy enables recipe portability. A master recipe says "Add Ingredient A" at the operation level. The control recipe, generated at runtime, translates this into specific phases for the specific equipment assigned: "Open valve V-101 for 30 seconds" or "Open valve V-205 for 45 seconds," depending on which unit was allocated.

Recipe Management

ISA-88 defines four levels of recipes:

1. General Recipe

The highest-level description of how to make a product. It is equipment-independent and expressed in terms of process actions and parameters. Think of it as the R&D specification.

2. Site Recipe

A general recipe adapted for a specific site. It may reflect site-specific raw material names, local regulatory requirements, or available equipment classes.

3. Master Recipe

A site recipe adapted for a specific process cell. It includes equipment-specific details such as vessel sizes, agitator speeds, and valve identifiers. This is what operators typically select when starting a batch.

4. Control Recipe

A master recipe instantiated for a specific batch run. It is created at runtime, assigned to specific equipment units, and populated with actual parameters (lot numbers, batch sizes, operator inputs). The control recipe is the one the automation system executes.

Recipe Parameters

Recipes contain several types of parameters:

• Process parameters: Temperatures, pressures, flow rates, times
• Equipment parameters: Agitator speed limits, valve timeout values
• Formula parameters: Ingredient quantities, ratios
• Header information: Product name, version, author, approval status

In regulated industries, recipes must be version-controlled with change history, approval workflows, and electronic signatures. Changes to a master recipe must follow your change management procedure.

Equipment Modules and Phases

The real power of ISA-88 emerges when you design reusable equipment modules with standardized phases.

For example, an agitator equipment module might support these phases:

• Start: Ramp agitator to target speed
• Stop: Decelerate and stop
• Change Speed: Adjust to a new target speed

A dosing equipment module might support:

• Dose by Weight: Add material until target weight is reached
• Dose by Volume: Add material until target volume is reached
• Dose by Time: Open valve for a specified duration

Because these phases are reusable, you can build new recipes by assembling existing phases in new sequences — without writing new PLC code.

Batch Reporting (ISA-88.04)

Every batch should produce a batch record that documents exactly what happened:

• Start and end times for every phase, operation, and unit procedure
• Actual parameter values vs. recipe setpoints
• Alarm and event logs during the batch
• Operator actions and interventions
• Material consumption and lot traceability
• Equipment used and condition at each step

In FDA-regulated industries (21 CFR Part 11), batch records must include electronic signatures, tamper-evident storage, and complete traceability from raw materials to finished product.

A well-implemented SCADA system automatically generates batch records by logging phase transitions, parameter values, and operator actions as the batch executes. Manual compilation of batch records after the fact is error-prone and should be avoided.

Implementing ISA-88 in Your SCADA System

Step 1: Model Your Physical Equipment

Map your plant to the ISA-88 physical hierarchy. Identify your process cells, units, equipment modules, and control modules. This mapping becomes the foundation of your automation design.

Step 2: Define Your Phases

For each equipment module, define the phases it can execute. Keep phases simple and reusable. A phase should do one thing well.

Step 3: Build Your Master Recipes

Assemble phases into operations, operations into unit procedures, and unit procedures into complete procedures. Define the parameters for each recipe, including default values and allowable ranges.

Step 4: Implement Recipe Management

Your SCADA system needs a recipe editor that allows authorized users to create, modify, version, and approve recipes. OptiZeus includes a built-in recipe and procedure management module that follows the ISA-88 recipe hierarchy, with version control and electronic signatures for change tracking.

Step 5: Build Batch Execution Logic

The batch engine in your SCADA or PLC must be able to:

• Select a master recipe and create a control recipe
• Allocate equipment (handling contention when multiple batches compete for the same unit)
• Execute phases in the correct sequence, with proper transitions
• Handle exceptions: what happens when a phase fails, a sensor goes out of range, or an operator intervenes?

Step 6: Configure Batch Reporting

Every transition, parameter, alarm, and operator action during batch execution should be automatically logged. OptiZeus generates ISA-88.04-compliant batch reports that include phase timing, parameter deviations, alarms, and operator actions — all exportable to PDF or Excel.

Common Pitfalls

1. Over-engineering phases: Keep phases granular. A phase that "charges, heats, mixes, and cools" is really four phases crammed together.
2. Hard-coding recipes in PLC logic: This defeats the purpose of ISA-88. Recipes belong in the SCADA/MES layer, not in ladder logic.
3. Ignoring exception handling: Happy-path batch logic is easy. The complexity is in handling sensor failures, operator aborts, and equipment faults gracefully.
4. No unit allocation strategy: If you have two identical reactors, the system must decide which one to assign. Manual allocation is fine for small operations; automated allocation matters at scale.

How OptiZeus Implements ISA-88

OptiZeus provides a built-in ISA-88 batch control framework that includes:

• Physical model configuration: Define your process cells, units, equipment modules, and control modules through a structured tag hierarchy
• Recipe editor: Create and manage master recipes with version control, approval workflows, and electronic signatures
• Batch execution engine: Execute recipes with automatic phase sequencing, parameter tracking, and exception handling
• Batch reporting: Automatic generation of ISA-88.04-compliant batch records with full traceability
• Integration with historian: All batch data is stored in the built-in historian for long-term trending and analysis

Conclusion

ISA-88 is not just a standard — it is a design philosophy that separates what you make from how you make it. By adopting ISA-88 principles, you gain recipe flexibility, consistent batch quality, regulatory compliance, and a clear audit trail. Whether you are building a new batch facility or modernizing an existing one, structuring your SCADA system around ISA-88 is an investment that pays dividends in reduced downtime, faster product changeovers, and easier compliance.