ISA-88ANSI/ISA-88 — Batch Control

ANSI/ISA-88, published internationally as IEC 61512, is the reference standard for the design, operation and recording of batch manufacturing. It emerged from the SP88 committee in the early 1990s as a response to a then-chronic industry problem: every batch-control system used different words for the same things, every recipe was bespoke, and every transfer of a process from R&D to production-engineering to operations went through an error-prone translation step. Part 1 was first published in 1995; the current Part 1 edition is 2010 (functionally identical to IEC 61512-1).

ISA-88 does three things. First, it defines the physical model — process cell, unit, equipment module, control module — that describes how a batch plant is laid out. Second, it defines the procedural model — procedure, unit procedure, operation, phase — that describes what the plant does. Third, it defines the recipe taxonomy — general, site, master, control — that tracks how a product specification flows from R&D to a specific execution on a specific cell. Parts 2, 3 and 4 then add data structures, recipe-language guidance, general/site recipe representation, and the batch production record.

Like its sibling ISA-95, ISA-88 is implementation-neutral. It does not tell you which DCS to buy, which recipe editor to use, or whose MES to run. It tells you what a unit procedure is and is not, what "recipe" properly means, and what a batch production record must contain. The pay-off is portability: a recipe expressed in ISA-88 vocabulary can be moved between plants, between vendors and between system generations without rewriting the meaning.

ISA-88 is the standard for batch processes. A batch process is one in which a finite quantity of material is produced by subjecting raw materials to an ordered set of processing activities over a finite period of time, using one or more pieces of equipment. The defining characteristics are: a finite quantity (a batch), an ordered sequence of activities (the procedure) and a defined start and end (a batch run). Continuous processes (no defined end) and discrete processes (countable units, not bulk quantities) are out of scope — though many real plants run hybrids and need to compose ISA-88 with discrete-execution patterns.

ISA-88 explicitly covers three batch modes:

• Single-product batch — the cell is dedicated to one recipe at a time; campaign mode common in API and bulk-chemical plants.
• Multi-product batch — the cell can run several recipes; changeover discipline (line clearance, cleaning verification) becomes a first-class concern.
• Multi-grade batch — the cell runs the same fundamental recipe with grade-specific parameters; common in food, dietary supplements and cosmetics.

ISA-88's physical model is a strict containment hierarchy. Each level contains zero or more of the next. The model is the same whether the plant makes vaccines, gummies or paint.

Two rules govern the model. First, a unit is the largest piece of equipment that can hold a complete batch (or a complete portion that is treated as a unit-of-work). Granulators, fermenters, blenders, kettles and reactors are units. Second, process cells, units and equipment modules can each carry their own "equipment phases" — atomic operations exposed to the recipe layer. The physical model is the lattice on which the procedural model executes.

The procedural model is the verb side of ISA-88. It is also a four-level hierarchy and is the source of more architectural arguments in batch engineering than anything else in the standard.

Phases are the atomic unit. They are the actions actually performed by equipment phases (in the control layer) or by operators (in the procedural layer). Above phase, all the other levels are coordination: an operation sequences phases inside a unit; a unit procedure sequences operations inside a unit procedure run; a procedure sequences unit procedures across the whole cell.

Perhaps the most useful single contribution of ISA-88 is its recipe taxonomy. A recipe goes through a defined lifecycle as it moves from product definition to actual execution, and at each stage it is a different type of recipe with a different scope and a different owner.

The flow is one-way and convergent. A general recipe yields one or many site recipes; each site recipe yields one or many master recipes; each master recipe yields many control recipes — one per batch. Reverse traceability is the audit trail: any control recipe can be walked back to its master, site and general parents.

ISA-88 Part 1 defines five mandatory categories of content for any recipe. Skipping one is the most common reason a recipe fails an audit.

1. Header — identification (recipe ID, name, version), authorship, approval status, intended use, target product, target batch size, validity window.
2. Formula — the bill of materials (inputs), the bill of intermediates and the bill of products (outputs), each with quantities, units and tolerances.
3. Equipment requirements — equipment classes (not specific instances), required capabilities, required cleaning state, required calibration status.
4. Procedure — the procedural model elements (procedure → unit procedures → operations → phases) with their sequencing, branches, joins and synchronisation.
5. Other information — process safety information, regulatory information, training requirements, sampling plans, in-process checks, expected outcomes.

ANSI/ISA-88.00.04 (2006, reaffirmed 2018) is dedicated to the batch production record (BPR). It defines what content the record must carry, how it must be organised, what its relationship to the control recipe is, and how it should support review and release.

Part 4's content model is hierarchical and mirrors the procedural model: the BPR contains procedure-level records, which contain unit-procedure-level records, which contain operation-level records, which contain phase-level records. Each phase record captures the parameters that drove the phase, the measured outcomes (actual mass, actual temperature, actual time), the operator(s) involved, the equipment instance(s) used, any deviations raised and any in-process checks completed.

The standard distinguishes three classes of BPR information:

• Required information — data the regulation or the master recipe explicitly demands (e.g. each material lot consumed, each operator signature, each in-process check result).
• Conditional information — data captured only if a condition occurs (e.g. deviation details, OOS investigation references, hold reasons).
• Optional information — additional context useful for review (e.g. additional sensor traces, photo evidence, environmental data).

ISA-88 and ISA-95 are sibling standards designed by overlapping committees to compose without conflict. A modern batch-MES architecture uses both: ISA-95 to talk to the ERP and to organise the enterprise; ISA-88 to express recipes and execute batches inside a process cell.

The pay-off of composing the two is clean separation of concerns: the ERP integration team writes against ISA-95 transactions without ever needing to understand the specifics of binder-addition phase parameters; the process engineering team writes recipes against ISA-88 without ever needing to negotiate fields with the ERP integrator. The MES, in the middle, owns the translation.

Different regulated industries have different names for the batch-record artefact, and each name carries its own mandatory content. ISA-88 is the common underlying standard; the regulated overlays add industry-specific signatures, content, retention and review requirements.

Mistake 1 — Skipping master recipes

Going directly from general (R&D) to control (execution) without an approved master in between is the most common source of batch-record findings. The master recipe is the regulated artefact (the MMR / DMR equivalent); without it there is no controlled object to validate against.

Mistake 2 — Misusing "phase"

Phases are atomic. A phase that internally branches, retries, or waits for an unrelated event is not a phase — it is an operation. Splitting it into proper phases makes the recipe easier to review, the audit trail easier to read, and the execution easier to validate.

Mistake 3 — Hard-coding equipment instances in master recipes

A master recipe should bind to equipment classes ("any qualified high-shear granulator"), not equipment instances ("V-105 specifically"). Hard-coding instances means a maintenance outage on one vessel makes the recipe unrunnable — and forces a controlled-document change for every move.

Mistake 4 — Treating the control recipe as ephemeral

The control recipe is the regulated record of what was made. It must be preserved with the batch record, not regenerated from the master on demand. V5 does this via the work_orders.mmr_snapshot deep copy; whatever your system, do something equivalent.

Mistake 5 — Building the BPR by stitching together logs after the fact

The Part-4 batch production record must be contemporaneous (ALCOA+'s "C"). Constructing it by post-hoc concatenation of DCS event logs and operator notes fails data-integrity expectations. The MES must capture each phase record as the phase executes, signed, with attribution, in the record's own structure.

V5 Ultimate is an ISA-88-aligned batch execution platform that composes with the ISA-95 enterprise integration described in the companion long-form page. Its design choices read directly off the standard:

• Physical model — V5's Resources / Equipment model supports the full process-cell → unit → equipment-module → control-module hierarchy, with equipment classes, capability flags and cleaning-state tracking.
• Procedural model — Formulas are structured as procedures / unit procedures / operations / phases; phase-level data capture (mass, temperature, duration, operator, equipment instance, deviation, in-process check) is the atomic event of the batch run.
• Recipe lifecycle — Approved formulas are immutable masters; edits create v+1 with full version history; work-order release deep-copies the approved master into work_orders.mmr_snapshot as the control recipe.
• Part-4 batch production record — generated from the snapshot, structured around required / conditional / optional content, rendered to a signed PDF that satisfies 21 CFR 211.188 / 111.205 / 820.184 / FSMA / MoCRA depending on tenant industry.
• Two-person e-signature — preparer + independent reviewer required for both master approval (211.186 / 111.205) and batch release (211.192 / 820.40), captured against the recipe and the BPR.
• Composition with ISA-95 — V5's ERP bridge translates an Operations Schedule into a work order against the master recipe, and emits an Operations Performance back when the batch is released — the standard L3↔L4 round trip.