ISA-88 batch control for food manufacturers. The standard your MES vendor keeps mentioning.

Why ISA-88 keeps coming up in proposals.

Have you ever read a batch-control proposal that mentioned ISA-88 four times and never explained what it meant?

ISA-88 is the international standard for batch control. Part 1 — the Models and Terminology section that does most of the work in conversation — was approved by the ISA in October 1995 and ratified by the IEC as IEC 61512-1 shortly after (ISA Standards Committee 88). It defines a common vocabulary and a structuring model for batch processes, so that PLC code, SCADA tags, MES recipes, and vendor product documentation can refer to the same concepts using the same names.

The reason it keeps appearing in proposals is partly genuine usefulness and partly signalling. A vendor who writes "ISA-88-compliant" on the cover page is communicating "we have done this kind of work before and we understand batch." Some live up to it. Others use the term as decoration. The plant manager who can read the procedural model knows which is which by the end of the second meeting.

The procedural model in plain English.

The procedural model is a four-level hierarchy. Each level composes the level below it. Only the bottom level actually executes.

Recipe procedure.

The top-level batch logic for a single product. A recipe procedure says "to make Product X, run unit procedure A then unit procedure B then unit procedure C, with these parameters." It is the closest level to what a food technologist actually writes.

Unit procedure.

The logic for a single piece of equipment (a unit) within the batch. A mixer is one unit; a kettle is another; a filler is another. The unit procedure for the kettle, in a typical recipe, runs operations like "Charge," "Heat," "Hold," "Discharge." Each unit procedure runs on one physical unit. Multiple unit procedures across multiple units can run in parallel within the same recipe.

Operation.

A major processing step inside a unit procedure. Heat. Mix. Hold. Discharge. Operations are composed of phases. An operation is a meaningful unit of work that a plant technologist would describe in a single bullet point.

Phase.

A small, parametrised executable step. Charge-by-mass with the parameter "ingredient = milk powder, target = 47.5 kg." Heat-to-setpoint with the parameter "target = 72°C, hold = 15 seconds." Agitate-hold with the parameter "duration = 600 seconds." The phase is the only level the PLC actually runs. Everything above is composition.

The standard's strength is the strict separation. Phases are reusable across operations and unit procedures. Operations are reusable across unit procedures. Unit procedures are reusable across recipes. A plant that writes ten well-bounded phases can compose hundreds of recipes from them. A plant that writes a fresh chunk of PLC code for every recipe writes ten times as much code and changes it ten times as often.

The physical model.

The procedural model describes what the batch does. The physical model describes the equipment it runs on. ISA-88 defines the physical hierarchy in six layers, top to bottom:

• Enterprise. The company.
• Site. The plant or factory.
• Area. A region of the site (Powder Room, Filling Hall, CIP Bay).
• Process cell. A group of equipment that runs batches together.
• Unit. A single major piece of equipment (a kettle, a mixer, a filler).
• Equipment module. A reusable sub-system within a unit (a CIP loop, a temperature control loop, a charge valve).
• Control module. The lowest-level controllable object (a single valve, a single pump, a single sensor).

The two models meet at the phase. A phase, executing on a unit, calls equipment modules on that unit, which actuate control modules. A "Charge-by-mass" phase running on the Kettle unit calls the kettle's "Charge valve" equipment module, which opens a specific valve control module and reads from a specific load-cell control module until the target mass is reached.

The clean separation pays back in three ways. First, recipes are written against the procedural model, so they survive equipment changes downstream. Second, the equipment library is written against the physical model, so it is reusable across plants with the same equipment shape. Third, the audit trail naturally aligns to both models, which makes batch records readable to auditors who do not know the plant.

What changes in PLC code when you adopt ISA-88.

The differences between a "we just write batch code" approach and a serious ISA-88 implementation are concrete enough to spot in the first hour of a code review.

A phase library, not phase-per-recipe code.

The plant has between five and twenty named phases. Each phase is implemented once, parameterised at runtime. New recipes compose existing phases with new parameter sets rather than triggering bespoke code. A plant where every recipe has its own copy of "Charge-by-mass" code is not running ISA-88 even if the document says so.

State management at the phase level.

Each phase implements the ISA-88 phase state model: idle, running, complete, holding, restarting, stopping, aborting, paused. Operators can hold, restart, stop, and abort phases through a consistent interface across the line. The HMI reflects phase states rather than valve states for the operator audience, and valve states for the engineering audience.

Equipment modules as the unit of reuse.

A CIP loop, a temperature control loop, an interlocked charge valve — each is written once as an equipment module with a defined external interface. Phases call equipment modules. Recipes compose phases. The plant gets the same code-reuse leverage in PLC logic that a software team gets from libraries.

Recipe management decoupled from code.

Recipes live in the SCADA, MES, or a dedicated recipe-management system. Engineering changes to the PLC layer (new equipment, new phase, new instrument) do not require recipe rewrites if the procedural interface stays stable. Conversely, food technologists can change a recipe parameter without engineering involvement.

The visible signal that a plant has the discipline right: when a new SKU is added, the engineering team is not the bottleneck.

When ISA-88 is overkill.

The standard's framework is heavy. Plants that adopt it without the underlying complexity to justify it end up writing more code than they would have written informally, with no compensating benefit.

Three categories of plant should think twice:

• Single-product, single-line operations. One product, one recipe, no plans to expand. The composition machinery has nothing to compose.
• Continuous-process plants masquerading as batch. A plant that runs a continuous process with periodic CIP is not a batch plant. ISA-88's procedural model fits awkwardly. ISA-106 (procedural control for continuous processes) is the relevant standard.
• Craft producers with operator-driven recipe variation. A craft brewer who tweaks the mash temperature by feel three times per batch is not a candidate. Their value is in the operator's judgement. Imposing ISA-88 structure reduces flexibility without producing a meaningful audit benefit.

The dividing line is roughly: three or more product variants, two or more major units, a real audit or recall obligation. Plants above the line benefit from ISA-88. Plants below it benefit from not pretending to.

Platform implementations.

Most major control platforms have an ISA-88 story. Some implement it as an explicit product. Others rely on the developer applying the standard. Both can work.

Explicit ISA-88 products.

Rockwell PlantPAx and FactoryTalk Batch are explicitly ISA-88-aligned. The platform enforces the model at the configuration level; the engineer who writes against PlantPAx is writing ISA-88 whether they intended to or not. AVEVA InBatch (formerly Wonderware InBatch) is one of the longest-running ISA-88 batch products in the market and is the natural batch layer on an AVEVA System Platform stack. Siemens SIMATIC BATCH on PCS 7 and PCS neo is the Siemens equivalent for process-industry batch.

Developer-applied ISA-88.

Inductive Automation Ignition does not ship a dedicated ISA-88 batch module, but the platform supports the model cleanly through application architecture. A team that writes their phase library, their state model, and their recipe-management against ISA-88 produces a fully compliant implementation. The discipline lives with the integrator. The flexibility advantage is significant for plants with non-standard batch shapes.

Custom batch products.

Pac Technologies' Silio is a batch-management product designed around the same procedural-and-physical-model thinking, currently deployed in production at a feed mill in Beaudesert QLD (Omron PLC backbone, EtherCat IO, Tencia ERP via SQL). The implementation is closer to the developer-applied pattern than the platform-enforced one, and it suits plants where the corporate weight of PlantPAx or InBatch is more than the operation needs.

The platform decision is rarely about which one can do ISA-88. All of them can. The decision is about the rest of the stack, the in-house engineering team's existing competence, and the licensing economics over a five-to-ten year horizon.

Common questions.

Sources and further reading.

Standards and vendor references for the model and platform claims above. Retrieved 18 May 2026.

• International Society of Automation. ISA-88 Standards Committee. isa.org
• ISA-88 Part 1. Batch Control — Models and Terminology, approved 23 October 1995.
• PLC Academy. ISA-88 (S88) Batch Control Explained. plcacademy.com
• Rockwell Automation. FactoryTalk Batch. rockwellautomation.com
• AVEVA. AVEVA InBatch. aveva.com

This article sits under the Food & Beverage Automation guide. For the traceability layer that ISA-88 batch records feed into, see the dairy MES article. For the OEE layer above it, see the OEE & SCADA article.