ISA-88 vs ISA-95: Batch Control vs Integration
ISA-88 and ISA-95 sound like siblings, and they are related, but confusing their scopes leads to putting logic in the wrong system. This page compares them: what each one governs, why they are complementary rather than overlapping, and where the two models actually hand off to each other. It is written for the engineer or architect deciding which standard frames a given requirement in a batch-manufacturing project.
ISA-88 vs ISA-95 in one line: ISA-88 vs ISA-95 is a scope distinction, not a rivalry. ISA-88 governs batch control: how a single batch is structured with physical, procedural, and recipe models so it runs the same way every time. ISA-95 governs enterprise integration: how operations systems and business systems exchange information such as schedules and production results. ISA-88 works inside the process cell; ISA-95 works between the plant and the business. They connect where a production schedule triggers a batch.
The Decision in One Paragraph
Frame a requirement with ISA-88 when it is about how a batch is made: the equipment hierarchy, the procedural steps, the recipe, and the phase logic that executes on the control system. Frame it with ISA-95 when it is about how the plant talks to the business: production scheduling, production performance reporting, and the interfaces between MES and ERP. The clean test is whether the requirement lives inside the process cell making product, which is ISA-88, or across the boundary to the business systems, which is ISA-95.
The two are designed to complement each other rather than compete, and a batch manufacturing operation typically uses both at once. Trouble comes from putting business-level scheduling logic into the batch engine, or trying to run batch phase logic from the MES, because that ignores the scope each standard was built for. Keeping batch execution in ISA-88 terms and enterprise exchange in ISA-95 terms is what keeps the architecture clean.
Scope, Models, and the Handoff
The two standards use different vocabularies because they describe different things. The table lines up their concerns.
| Aspect | ISA-88 | ISA-95 |
|---|---|---|
| Governs | Batch control | Enterprise integration |
| Scope | Inside the process cell | Between plant and business |
| Key models | Physical, procedural, recipe | Levels, equipment hierarchy |
| Signature object | The recipe | The production schedule |
| Typical system | Batch engine on the control system | MES to ERP interface |
The ISA-88 batch control standard defines the recipe and phases, while the ISA-95 model defines the schedule and performance report, and the two meet at the point where a schedule launches a batch.
That handoff is the interesting part. A production schedule created at the ISA-95 level says make so many batches of this product on this equipment by this time; when a batch actually starts, ISA-88 takes over, selecting the control recipe and running its phases. When the batch finishes, its results roll back up as ISA-95 production performance. So the recipe and the schedule are the two objects that meet at the boundary, one describing how to make it and the other describing how much and when. The physical hierarchies of the two standards are designed to align at that seam.
When Each Wins
ISA-88 wins whenever the concern is the correctness and repeatability of the batch itself: structuring the recipe, designing the phase state behavior, mapping procedures onto units, and making the same product come out the same way each run. If the deliverable is batch application logic, ISA-88 is the frame, and its physical model is where you start describing the equipment.
ISA-95 wins whenever the concern crosses the boundary to the business: scheduling production, reporting what was made, and integrating with ERP. If the deliverable is an interface between operations and enterprise systems, ISA-95 is the frame. The practical rule for a batch plant is to use ISA-88 to run the batches and ISA-95 to schedule them and report them, letting each standard own the scope it was designed for and meeting only at the schedule-to-batch handoff.
Frequently Asked Questions
Are ISA-88 and ISA-95 competing standards?
No, they are complementary. ISA-88 governs batch control inside the process cell, structuring how a batch is made with physical, procedural, and recipe models. ISA-95 governs enterprise integration between the plant and business systems, such as scheduling and production reporting. A batch plant uses both, and they connect where a production schedule triggers a batch.
Where do ISA-88 and ISA-95 connect?
At the schedule-to-batch handoff. A production schedule created at the ISA-95 level says what to make, how much, and by when; when a batch starts, ISA-88 takes over with the control recipe and phase logic; and when it finishes, the results roll back up as ISA-95 production performance. The recipe and the schedule are the two objects that meet at that boundary.
Which standard covers the recipe?
ISA-88. The recipe is ISA-88's signature object, binding the procedural model to the physical model for a specific product. ISA-95's signature object is the production schedule, which lives at the enterprise-integration level. A schedule from ISA-95 can launch a batch that then runs an ISA-88 recipe, but the recipe itself is an ISA-88 concept.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.