Every batch process in GMP biomanufacturing runs on a recipe. The recipe defines what temperature to hold, when to add the inoculum, how fast to ramp the feed, and when to harvest. ISA-88 (also called S88, published internationally as IEC 61512) is the standard that structures those recipes, defines how equipment is modeled, and governs how batch control systems execute procedural logic. It is the foundation on which every major DCS and SCADA platform in biopharma is built.
This guide explains the ISA-88 standard from a bioprocess engineer's perspective. It covers the physical model mapped to bioreactor hardware, the procedural model that organizes phase logic, the recipe hierarchy from general to control recipe, and how electronic batch records built on S88 automation meet 21 CFR Part 11 requirements for GMP manufacturing.
What Is ISA-88? The Batch Control Standard Explained
ISA-88 is a family of standards published by the International Society of Automation (ISA) that defines the terminology, models, and data structures for batch process control. First released in 1995 as ANSI/ISA-88.00.01, it has been updated and expanded through several parts, with the most recent revision of Part 1 published in 2010.
The standard solves a specific problem: in batch manufacturing, the same equipment (a bioreactor, a chromatography skid, a CIP system) must run different products with different recipes. Without a common framework, every recipe change requires reprogramming the control system. ISA-88 separates the process knowledge (the recipe) from the equipment capability (the physical model), so recipes can be created, modified, and transferred between sites without touching PLC or DCS code.
The ISA-88 standard consists of several parts:
- Part 1 (S88.01) defines the physical model, procedural model, and recipe model. This is the foundational document that most engineers reference.
- Part 2 (S88.02) defines data structures and guidelines for languages used to describe batch control.
- Part 3 (S88.03) covers general and site recipe models and representation.
- Part 4 (S88.04) addresses batch production records.
- Part 5 (S88.05) covers implementation models and terminology for modular equipment control.
For bioprocess engineers, Parts 1 and 4 are the most directly relevant. Part 1 provides the framework for structuring bioreactor control, and Part 4 connects to electronic batch record requirements under GMP regulations.
The Three Core Models of ISA-88
ISA-88 is built on three interlocking models that together describe every aspect of a batch process. Understanding these three models is essential before mapping them to bioreactor operations.
1. Physical Model
The physical model describes the equipment hierarchy. It defines seven levels from the enterprise down to individual control elements:
| Level | S88 Term | Bioreactor Example |
|---|---|---|
| 1 | Enterprise | PharmaCo Global |
| 2 | Site | Dublin Manufacturing Facility |
| 3 | Area | Upstream Processing Area |
| 4 | Process Cell | Bioreactor Suite 1 (BR-100 + media prep + CIP) |
| 5 | Unit | 200 L Stirred-Tank Bioreactor (BR-101) |
| 6 | Equipment Module | Agitation drive, aeration system, temperature jacket, pH dosing skid, feed pump |
| 7 | Control Module | Agitation motor, air mass flow controller, jacket valve, pH PID loop, DO probe |
2. Procedural Model
The procedural model defines the hierarchy of actions that transform raw materials into product. It has four levels:
- Procedure — the complete batch process (e.g., "Fed-Batch CHO mAb Production")
- Unit Procedure — a sequence of operations on a single unit (e.g., "Inoculation", "Growth Phase")
- Operation — a group of related phases (e.g., "Seed Addition" within Inoculation)
- Phase — the smallest unit of procedural control (e.g., "Set Temperature to 37 °C", "Open Seed Valve")
3. Recipe Model
The recipe model defines four levels of recipe abstraction, from equipment-independent process knowledge down to the executable batch instance. This hierarchy is what enables recipe portability across sites and equipment.
Mapping the Physical Model to Bioreactor Equipment
The physical model maps directly to the hardware in a bioreactor suite. A process cell encompasses all equipment required to complete a batch, including the bioreactor unit, media preparation vessels, CIP/SIP systems, and supporting utilities. The unit is the bioreactor itself, where the batch transformation occurs.
Diagram showing the ISA-88 physical model hierarchy from process cell through unit, equipment modules, and control modules on the left, and the procedural model hierarchy from procedure through unit procedures, operations, and phases on the right. Arrows show that recipes bind to equipment at runtime, enabling the same recipe to run on different bioreactor units.
Each equipment module is a functional group of devices that performs a specific task. The agitation equipment module, for example, includes the motor, variable-frequency drive, shaft, and impeller. The control module is the lowest level: individual sensors, actuators, and PID loops that the equipment module uses to carry out its function.
This separation matters for multi-product facilities. When a CDMO switches from a CHO mAb campaign to an E. coli fed-batch, the physical model stays the same but the recipe changes. The same agitation equipment module that held 150 RPM for CHO now ramps to 800 RPM for E. coli, driven by a different recipe but executing through the same phase logic.
Phase Logic and the Procedural Model
The phase is the atomic unit of batch control in ISA-88. Every action a bioreactor performs is decomposed into phases, and every phase executes through a defined state machine. This state machine is what makes S88-based batch control deterministic and auditable.
The S88 Phase State Machine
ISA-88 defines the following states and transitions for every phase:
| State | Description | Bioreactor Example | Valid Transitions |
|---|---|---|---|
| Idle | Phase is ready but not executing | Feed pump configured, awaiting start | Start → Running |
| Running | Phase is actively executing | Feed pump delivering at 2.5 mL/min | Complete, Pause, Hold, Stop, Abort |
| Complete | Phase finished normally | Feed volume target reached | Reset → Idle |
| Paused | Temporarily suspended, resumes from same point | Operator paused to check feed line | Resume → Running |
| Held | Process-safe hold, may require restart logic | DO alarm triggered hold; agitation and aeration maintained | Restart → Running |
| Stopped | Orderly shutdown, can restart | Controlled shutdown of feed sequence | Reset → Idle |
| Aborted | Emergency halt, immediate stop | Contamination detected, all actions cease | Reset → Idle |
The distinction between Held and Paused is critical for bioreactors. A Pause freezes the procedural timer but continues all active control outputs (agitation, temperature, DO). A Hold goes further: it executes a defined "hold logic" sub-sequence that may adjust setpoints to a safe state, such as reducing temperature to 33 °C or switching to air-only sparging. The Restart from Held may include a ramp-back sequence rather than immediately resuming where it left off.
Typical Bioreactor Phases
A fed-batch CHO mAb production recipe typically uses phases such as:
- Temperature Control — Set jacket PID to target (37.0 °C), wait for within ±0.5 °C for 5 min
- Agitation Ramp — Ramp RPM from 0 to target over a defined period, monitoring torque
- Gas Flow Set — Set mass flow controllers for air, O₂, CO₂, N₂ overlay
- DO Cascade Enable — Enable the multi-level DO cascade (agitation → air flow → O₂ enrichment)
- pH Control Enable — Enable two-sided pH control (CO₂ sparging + base pump)
- Bolus Addition — Pump a defined volume (e.g., 500 mL seed culture at 50 mL/min)
- Continuous Feed — Execute an exponential, linear, or constant feed profile
- Timed Wait — Hold current state for a defined duration (used in incubation periods)
- Sample Prompt — Pause procedure and prompt operator to take an aseptic sample
- Harvest — Open drain valve, monitor weight/level, confirm vessel empty
Each phase is parameterized. The "Bolus Addition" phase accepts volume, flow rate, and source vessel as parameters, making it reusable for inoculum addition, nutrient boluses, and antifoam dosing without writing separate code for each.
Recipe Management: From General to Control Recipe
ISA-88 defines a four-level recipe hierarchy that progressively binds process knowledge to specific equipment. This hierarchy is what makes ISA-88 recipes portable across facilities and scalable across bioreactor volumes.
| Recipe Level | Contains | Created By | Bioreactor Example |
|---|---|---|---|
| General Recipe | Process chemistry, target parameters, equipment-independent procedure | Process Development | "CHO DG44 mAb X: seed at 0.3 × 10⁶/mL, 37 °C, pH 7.0, feed at 3% v/v/day from day 3" |
| Site Recipe | General recipe adapted to site-level constraints (utilities, raw material grades) | Site Process Engineering | Dublin site: WFI grade water, NaOH 1 M for pH base, specific media vendor lot ranges |
| Master Recipe | Mapped to specific equipment set, validated parameter ranges (NORs/PARs) | Automation / Validation | BR-101 (200 L Sartorius Biostat STR): agitation 80-250 RPM, DO cascade levels 1-4, feed pump P-101 at 0.5-10 mL/min |
| Control Recipe | Executable instance with batch-specific values: lot numbers, actual weights, operator IDs | MES / Batch Engine (runtime) | Batch CHO-2026-0914: Lot M-4821 media, 520 mL inoculum, operator JS-042 authorized |
In practice, most GMP biomanufacturing sites maintain the master recipe as the primary validated document. It contains the procedure mapped to specific equipment, with all setpoints within validated normal operating ranges (NORs) and proven acceptable ranges (PARs). The control recipe is generated automatically by the batch engine when an operator initiates a new batch, pulling batch-specific parameters from the MES.
Worked Example: Recipe Parameter Binding
A general recipe for a CHO mAb specifies: "Maintain temperature at 37.0 °C during growth phase, shift to 33.0 °C at transition."
The master recipe for BR-101 (200 L Sartorius Biostat STR) translates this to:
- Phase:
TEMP_CTRL→ Equipment Module:EM_JACKET_101 - Parameter:
SP_TEMP = 37.0,DEADBAND = 0.5,PID_KP = 5.0,PID_TI = 300 - Transition condition:
WHEN ELAPSED_TIME >= 72h AND VCD_OFFLINE > 8e6 THEN SP_TEMP = 33.0
The control recipe for batch CHO-2026-0914 inherits these values unchanged but adds: BATCH_ID = CHO-2026-0914, OPERATOR = JS-042, MEDIA_LOT = M-4821.
How Does ISA-88 Recipe Management Work in Bioprocessing?
In bioprocess manufacturing, ISA-88 recipe management works by decomposing complex bioreactor operations into parameterized, reusable phases that bind to equipment at runtime. The batch engine reads the control recipe, identifies which equipment modules are needed, verifies they are available and in the correct state, and then executes each phase sequentially or in parallel according to the procedural logic.
The recipe contains five components as defined by ISA-88:
- Header — Recipe ID, version, product, author, approval status, effective dates
- Formula — Process inputs (media volume, feed concentration, seed density), outputs (target titer, viable cell density), and process parameters (temperature, pH, DO setpoints)
- Equipment Requirements — What type and capacity of equipment is needed (a 200 L STR with DO cascade, not specifically BR-101)
- Procedure — The ordered set of unit procedures, operations, and phases
- Other Information — Safety data, regulatory references, deviations history
When an operator initiates a batch, the system performs equipment arbitration: it checks which units matching the equipment requirements are available, allocates them, and locks them for the batch duration. This is essential in multi-product CDMO facilities where multiple products share equipment.
Recipe versioning under GMP follows change control. Every modification to a master recipe triggers a change request, impact assessment, re-validation (if the change affects a validated parameter), and approval workflow. The batch engine maintains a complete version history, and every control recipe records which master recipe version it was instantiated from.
Electronic Batch Records and 21 CFR Part 11 Compliance
Electronic batch records (EBRs) are the GMP documentation output of an ISA-88-based batch control system. Every phase execution, parameter change, operator intervention, alarm, and material addition is captured automatically with timestamps, user attribution, and reason codes. EBRs replace paper-based batch records and are subject to FDA 21 CFR Part 11 requirements.
21 CFR Part 11 Requirements for Batch Records
21 CFR Part 11 establishes the criteria under which electronic records and electronic signatures are considered trustworthy, reliable, and equivalent to paper records. For batch automation systems, the key requirements are:
- Audit trails — Computer-generated, time-stamped trails that independently record the date and time of operator entries and actions that create, modify, or delete electronic records. Trails must be retained for the record retention period and must be available for FDA review.
- Electronic signatures — Linked to their respective electronic records and include the printed name, date/time, and meaning (approval, review, responsibility) of the signing.
- Access control — System access limited to authorized individuals. Unique user IDs and passwords. Authority checks ensuring only authorized individuals can use the system, sign records, or alter records.
- Data integrity — Records must be accurate, complete, and unalterable once signed. The ALCOA+ framework (Attributable, Legible, Contemporaneous, Original, Accurate, Complete, Consistent, Enduring, Available) provides the quality system foundation.
- System validation — Systems must be validated to ensure accuracy, reliability, consistent intended performance, and the ability to discern invalid or altered records.
EBR Benefits Over Paper
Facilities that transition from paper batch records to S88-based EBRs typically report:
- Batch release time reduced from 10-15 days to 2-5 days (60-70% reduction)
- Documentation errors reduced by 50-80% (elimination of transcription errors)
- Review-by-exception: only deviations and out-of-range events require human review, rather than page-by-page verification of 200+ page paper records
- Real-time deviation detection during batch execution, enabling immediate corrective action rather than post-batch discovery
What Are the Benefits of ISA-88 for Multi-Product Biomanufacturing?
The primary benefit of ISA-88 for multi-product facilities is recipe portability. A CDMO manufacturing 5-10 different biologics products on shared equipment can maintain separate master recipes that all execute through the same physical model, using the same phase library and equipment modules. Changing products requires loading a different recipe, not reprogramming the control system.
Measurable benefits from applying ISA-88 to bioprocess manufacturing include:
- 30% savings on first S88 implementation project and up to 80% on follow-up projects due to phase library reuse (ISA published benchmark)
- Recipe changeover time reduced from days to hours because equipment-independent recipes require only parameter rebinding, not code changes
- 40-60% reduction in batch deviations through structured exception handling (Hold/Restart vs. ad-hoc manual intervention)
- Simplified technology transfer between development and manufacturing sites, since the general recipe travels with the product and is adapted to each site's equipment
- Regulatory submission clarity, because the recipe hierarchy maps directly to CTD Module 3.2.S.2 (Manufacturing Process) descriptions
For CDMOs adopting flexible manufacturing (single-use bioreactors, ballroom layouts), ISA-88 is particularly valuable because the physical model handles equipment allocation dynamically. The batch engine can assign any available bioreactor that meets the recipe's equipment requirements, rather than hard-coding a specific vessel.
Implementing S88: DCS and SCADA Platforms for Bioreactors
All major DCS and SCADA platforms used in biopharmaceutical manufacturing implement ISA-88 natively. The choice of platform depends on facility size, existing infrastructure, and single-use vs. stainless-steel equipment strategy.
| Platform | Vendor | S88 Implementation | Typical Bioprocess Application |
|---|---|---|---|
| DeltaV Batch | Emerson | Native S88 batch engine, recipe editor, equipment arbitration | Large-scale stainless-steel facilities, multi-unit process cells |
| SIMATIC BATCH | Siemens | S88-compliant batch control within SIMATIC PCS 7 / PCS neo | Hybrid single-use + stainless, European biopharma |
| FactoryTalk Batch | Rockwell Automation | S88 recipe management, phase manager, equipment arbitration | North American CDMOs, integration with PlantPAx DCS |
| BioPAT MFCS | Sartorius | ANSI/ISA-88 compliant batch control for Biostat STR and AMBR | Single-use bioreactors, process development labs, clinical manufacturing |
| 800xA Batch Management | ABB | S88 batch control within Ability 800xA | Large integrated facilities, continuous + batch hybrid |
| zenon Batch Control | COPA-DATA | ISA-88 recipe management, S88 procedural model | OEM equipment builders, smaller-scale pharma |
Implementation of ISA-88 in a new biomanufacturing facility typically follows a phased approach:
- Phase library development (4-8 weeks) — Define and code all reusable phases: temperature control, agitation, gas management, additions, sampling prompts, CIP/SIP sequences
- Physical model configuration (2-4 weeks) — Map actual equipment to the S88 hierarchy (units, equipment modules, control modules)
- Master recipe creation (2-4 weeks per product) — Build the validated recipe from the phase library, define parameter ranges
- FAT/SAT and commissioning (4-8 weeks) — Factory and site acceptance testing, including IQ/OQ/PQ of the batch control system
- 21 CFR Part 11 validation (4-6 weeks) — Audit trail, e-signature, access control, and data integrity validation
Total implementation for a single process cell with 2-3 bioreactor units and CIP/SIP typically takes 4-8 months from phase library development through validation.
Frequently Asked Questions
What is the difference between ISA-88 and ISA-95?
ISA-88 (S88) defines batch process control within a single process cell, covering recipe management, procedural logic, and equipment abstraction. ISA-95 (S95) defines the interface between enterprise systems (ERP/MES) and control systems across the entire plant. ISA-88 sits inside ISA-95 Level 2, handling batch execution, while ISA-95 manages production scheduling, material tracking, and quality management at Levels 3-4. In a biomanufacturing facility, the MES (ISA-95 Level 3) tells the batch engine which recipe to run and when; the batch engine (ISA-88) executes the recipe on the equipment.
How many phases does a typical fed-batch CHO bioreactor recipe have?
A typical fed-batch CHO mAb production recipe contains 35-50 phases across 6-8 unit procedures. This includes media preparation (5-8 phases), SIP sterilization (6-10 phases), inoculation (4-6 phases), growth phase (4-6 phases), production phase with feeding (6-10 phases), and harvest (5-8 phases). Perfusion processes can exceed 80 phases due to continuous cell retention, bleed, and harvest sub-procedures running in parallel.
Is ISA-88 mandatory for GMP biopharmaceutical manufacturing?
ISA-88 is not legally mandated by the FDA or EMA. However, it is the de facto industry standard for batch control in GMP biomanufacturing. FDA 21 CFR Parts 211 and 212 require documented batch records, and ISA-88-structured automation systems are the most straightforward path to meeting 21 CFR Part 11 requirements for electronic records and signatures. Most DCS and SCADA platforms used in biopharma (DeltaV, SIMATIC BATCH, FactoryTalk) implement S88 natively.
What are the four recipe types in ISA-88?
ISA-88 defines four recipe levels. The general recipe is equipment-independent and contains the core process knowledge. The site recipe adapts the general recipe to site-specific constraints. The master recipe maps procedures to specific equipment sets with validated parameter ranges. The control recipe is the executable instance created for each batch run, with batch-specific parameters like lot numbers, actual weights, and setpoints.
What is a phase in ISA-88 batch control?
A phase is the smallest unit of procedural control in ISA-88. It represents a single process-oriented action that causes a specific change in the process material, such as "Heat to 37 °C", "Add 500 mL seed culture", or "Ramp agitation to 200 RPM". Phases execute on equipment modules through a state machine with defined states (Idle, Running, Complete, Paused, Held, Stopped, Aborted) and transitions. Each phase is reusable across multiple recipes.
Fed-Batch Calculator
Calculate exponential, linear, and constant feeding profiles for your bioreactor recipe. Generate the feed schedule that your S88 "Continuous Feed" phase will execute.
Scale-Up Calculator
Compare scale-up criteria (constant P/V, tip speed, kLa) for transferring recipes between bioreactor units. Essential when adapting a master recipe to a different vessel size.
Fermentation Economics Calculator
Estimate COGS per gram across batch, fed-batch, and continuous manufacturing modes. Compare the economic impact of recipe optimization and campaign scheduling.
Related Tools
- Gas Mixing Calculator — Configure the gas flow setpoints that your S88 "Gas Flow Set" phase will execute
- OTR & kLa Estimator — Estimate oxygen transfer capacity to set DO cascade parameters in your recipe
- Heat Transfer Calculator — Size jacket cooling/heating for the temperature control phases
References
- ANSI/ISA-88.00.01-2010. Batch Control Part 1: Models and Terminology. International Society of Automation, Research Triangle Park, NC.
- De Minicis M, Giordano F, Poli F, Schiraldi MM. Recipe Development Process Re-Design with ANSI/ISA-88 Batch Control Standard in the Pharmaceutical Industry. Int J Eng Bus Manag. 2014;6:16. doi:10.5772/59025
- Parshall J, Lamb L. Applying S88: Batch Control from a User's Perspective. ISA, 2000. ISBN 978-1-55617-703-5.
- Steinwandter V, Borchert D, Herwig C. Data Science Tools and Applications on the Way to Pharma 4.0. Drug Discov Today. 2019;24(9):1795-1805. doi:10.1016/j.drudis.2019.06.005
- FDA. 21 CFR Part 11 — Electronic Records; Electronic Signatures. Code of Federal Regulations. Title 21, Chapter I, Subchapter A, Part 11. U.S. Food and Drug Administration.