ISA-88 vs ISA-95: two standards, two different questions
ISA-88 (IEC 61512) is the batch control standard. It defines the physical model, the procedural model, and the recipe types that separate what to make from the equipment that makes it. ISA-95 (IEC 62264) is the enterprise-control integration standard, defining the five levels and the information exchanged between them.
The confusion is understandable
Both standards come from the same body. Both have similar numbers.
Both describe manufacturing in hierarchies. Both get cited in the same product datasheets.
It is easy to assume one supersedes the other.
They do not overlap that way. They answer different questions.
- ISA-88 (IEC 61512): how is a batch defined and made?
- ISA-95 (IEC 62264): what information do business systems and manufacturing systems exchange?
One is about the structure of production itself.
The other is about the structure of the conversation between systems.
What ISA-88 defines
ISA-88 came from a real and expensive problem in batch processing.
Recipes were written into the control system of a particular equipment train.
Move production to a different train, and the recipe had to be rewritten, with all the validation that implies.
The standard’s central move is a separation.
Separate what to make from the equipment that makes it.
It does this with three models.
The physical model
A hierarchy of equipment.
Enterprise → Site → Area → Process Cell → Unit → Equipment Module → Control ModuleThe procedural model
A parallel hierarchy of activity.
Procedure → Unit Procedure → Operation → PhaseA phase is the smallest meaningful step.
Heat to 80°C. Add ingredient B. Agitate for 20 minutes.
Phases are implemented once against the equipment. Recipes call them.
The recipe types
Recipes become progressively more specific.
| Recipe type | Bound to | Who maintains it |
|---|---|---|
| General | Nothing, equipment independent | Corporate R&D |
| Site | A location, with local materials and constraints | Site technical team |
| Master | A specific equipment train | Plant, in the MES |
| Control | One individual batch | Created automatically per batch |
The master recipe is the template a plant maintains.
The control recipe is the copy made for batch 0417, carrying that batch’s actual values, actual lots, actual measured results.
That distinction is what makes a batch record possible. The control recipe is the record of what was supposed to happen, against which what did happen is recorded.
What ISA-95 defines
ISA-95 addresses a different problem.
ERP and manufacturing systems need to exchange information, and every integration was being invented from scratch.
It defines the five-level model, an equipment hierarchy, object models for the things exchanged, and the activities within Level 3.
The full level model is covered in ISA-95 explained.
Its equipment hierarchy looks similar to ISA-88’s at the top, then diverges.
Enterprise → Site → Area → Work Center → Work UnitThe first three levels are deliberately the same.
Below that, ISA-88 goes into process-cell detail specific to batch. ISA-95 uses the more general Work Center and Work Unit, so the model works for discrete, batch and continuous production alike.
That shared top is not accidental.
The standards were written to be compatible, and ISA-95 explicitly acknowledges ISA-88 for batch.
Side by side
| ISA-88 (IEC 61512) | ISA-95 (IEC 62264) | |
|---|---|---|
| Subject | Batch control | Enterprise-control integration |
| Question | How is a batch defined and executed? | What information crosses between systems? |
| Core concepts | Physical, procedural and recipe models | Five levels, equipment hierarchy, object models |
| Scope | Mostly Level 2 to 3, inside the plant | Level 3 to 4 boundary, across systems |
| Best fit | Batch and process manufacturing | All manufacturing types |
| Common artefact | Master recipe | B2MML message |
Where they meet in practice
In a plant running both, the division usually looks like this.
ISA-88 structures what production is. ISA-95 structures how it is talked about.
The flow is typically:
- A production order arrives from ERP in an ISA-95-shaped message.
- The MES resolves it to a master recipe defined in ISA-88 terms.
- The MES generates a control recipe for that specific batch.
- Production runs.
- Production results go back to ERP in another ISA-95-shaped message.
The two standards touch at the equipment hierarchy.
That is why getting that model right matters more than it first appears.
An equipment model that only supports one site, or that cannot nest areas, will constrain both the recipe structure and the integration later.
It is also one of the hardest things to change once master data and history depend on it.
What alignment claims are worth
Both standards get cited loosely on datasheets, so the claim is worth testing rather than accepting.
For ISA-88, the question is whether recipes are genuinely equipment-independent.
Ask to move a master recipe to a different equipment train and see what has to be rewritten.
If the process definition contains equipment addresses, the separation is nominal.
For ISA-95, the question is whether the plant model actually nests.
Ask to create a second site with its own areas, and to represent an area within an area.
Products that flatten this into a single-level list of work centres are workable for one plant, and become a problem for the second.
Neither standard is a compliance regime. There is no certificate, and conformance is a matter of degree.
Alignment is worth caring about because it predicts what will be painful in two years. Not because it is a box to tick.
Where VECHR MES fits
VECHR MES models the plant along ISA-95 lines.
Unlimited plants, hierarchically nested areas, work centers and resource groups. A second site or a nested area is a configuration change rather than a structural one.
Process definition follows ISA-88 thinking.
Specifications act as master recipes. Routing composes them into sequential, parallel and rework flows through a visual designer.
The process definition stays separate from the equipment that runs it, and version control leaves orders already in flight undisturbed when a definition changes.
Because both models live in the same platform, a production order can resolve to a specification, execute against real resources, and return results without translation between two separately maintained plant models.
Frequently Asked Questions
Do we need both standards, or can we pick one?
They answer different questions, so it depends what you are doing. If you run batch processes and need recipes portable across equipment trains, ISA-88 is the relevant one. If you are integrating ERP with shop-floor systems, ISA-95 is. Batch plants doing both typically use ISA-88 for recipe structure and ISA-95 for the information exchange around it.
Does ISA-88 apply to discrete manufacturing?
Its recipe and procedural models were written for batch processing, and much of the value is specific to that. But the underlying principle transfers well to discrete routing. Separate the definition of what to make from the equipment that makes it. Many MES products apply ISA-88 thinking to discrete processes without claiming full conformance.
What is a control recipe versus a master recipe?
ISA-88 defines four recipe levels. A general recipe is equipment-independent. A site recipe adapts it to a location. A master recipe is bound to a specific equipment train and is what a plant maintains. A control recipe is the copy created for one individual batch, carrying that batch actual values. The master is the template, the control recipe is the instance.
Is B2MML part of ISA-95?
B2MML is an XML implementation of the ISA-95 object models, published by MESA rather than by ISA itself. The standard defines what information should be exchanged. B2MML provides a concrete schema for exchanging it. Using ISA-95 does not require B2MML, but it removes the need to invent your own message format.
Which one matters more when choosing an MES?
For a batch or process plant, ISA-88 alignment usually reveals more about product quality, because it shows whether recipes are genuinely separated from equipment or hardcoded per line. ISA-95 alignment tends to matter more for integration, and for whether the plant model can represent multiple sites properly.