ISA‑88 and ISA‑95 are related but solve different problems in manufacturing. They are often used together, but they are not interchangeable.
Core intent
ISA‑88 (S88) focuses on batch control and how to structure and execute recipes on equipment:
- Defines models for procedural control (procedures, operations, phases).
- Defines equipment models (enterprise, site, area, process cell, unit, equipment module, control module).
- Defines recipe models (general, site, master, control recipes).
- Targets DCS/PLC/SCADA and batch MES implementations.
- Most applicable to batch and semi‑continuous processes (e.g., pharma, specialty chemicals, food, biotech).
ISA‑95 (S95) focuses on integrating business and manufacturing systems:
- Defines functional levels (Level 4 business planning & logistics, Level 3 manufacturing operations management, Levels 2–0 control).
- Defines information models for products, equipment, materials, personnel, and production.
- Standardizes interfaces between ERP, MES, LIMS, WMS, and control systems.
- Targets system integration, data exchange, and MES/ERP architecture.
- Applies to batch, discrete, and continuous manufacturing.
Scope and typical use
ISA‑88 typical scope:
- Designing batch control strategies and unit procedures.
- Structuring equipment hierarchies in DCS/PLC and batch servers.
- Defining recipe versions and parameter sets for validated processes.
- Separating product logic (recipes) from equipment logic (control modules) to simplify change control.
ISA‑95 typical scope:
- Defining what lives in ERP vs MES vs control and who owns which data.
- Standardizing order download, results upload, material and status messages.
- Structuring production schedules, production orders, and performance data.
- Supporting multi‑system traceability and genealogy across ERP, MES, LIMS, WMS.
Key differences
- Problem domain
- ISA‑88: How to execute a batch on equipment.
- ISA‑95: How business and manufacturing systems exchange information.
- Primary audience
- ISA‑88: controls engineers, process engineers, batch MES engineers.
- ISA‑95: MES architects, ERP/integration teams, OT/IT architects.
- Level of the Purdue model
- ISA‑88: mainly Levels 0–3 (control and batch execution).
- ISA‑95: mainly Levels 3–4 (operations and business planning) and their interfaces.
- Applicability to manufacturing types
- ISA‑88: strongest in batch; parts of the modeling approach can be adapted to discrete, but that is not its core.
- ISA‑95: explicitly defined for batch, discrete, and continuous environments.
- Interaction with validation and change control
- ISA‑88: directly impacts validated recipes, unit procedures, and automation logic. Changes often trigger re‑validation and documented impact assessments.
- ISA‑95: impacts master data models, integration mappings, and MES workflows, which also require controlled changes but at the information/model level rather than control logic.
How ISA‑88 and ISA‑95 fit together
In mature environments, ISA‑88 and ISA‑95 are used in a complementary way:
- ISA‑88 defines how a unit actually runs a batch and how recipes are structured.
- ISA‑95 defines how production orders, material definitions, personnel, and results flow between ERP, MES, and the batch system that implements S88 concepts.
Examples:
- A Level 4 ERP system creates a production order (ISA‑95 object) and sends it to the MES.
- The MES maps that order to a master recipe and control recipe defined using ISA‑88 models.
- The batch engine (ISA‑88) executes the recipe on units and equipment modules.
- Execution results (ISA‑95 production response, material consumption, and quality data) are sent back to MES/ERP.
Brownfield and regulated environment considerations
In existing, highly regulated plants, you rarely get a “pure” ISA‑88 or ISA‑95 implementation:
- Legacy DCS/PLC platforms may predate S88; equipment models and phase structures are only partially aligned.
- MES and ERP often implement ISA‑95‑inspired models, but with vendor‑specific extensions and naming.
- Long equipment lifecycles and validated systems mean aggressive refactoring to align fully to the standards is often not practical due to re‑qualification effort and downtime risk.
- Plants may adopt a subset of S88/S95 concepts (e.g., using the S95 activity model and equipment model, but not full message models; or using S88 recipe structures without fully restructuring existing control modules).
Benefits from ISA‑88 and ISA‑95 in these settings depend heavily on:
- The discipline of the data and recipe modeling.
- The quality of integration design, version control, and traceability.
- How changes are handled through formal change control and validation.
- Realistic scoping that respects downtime constraints and integration debt.
When to focus on which standard
- Prioritize ISA‑88 work when:
- You are redesigning or expanding batch automation or adding a batch execution system.
- Recipe variants and product introductions are slow and expensive due to tightly coupled product and equipment logic.
- You need clearer recipe versioning and procedural traceability for audits.
- Prioritize ISA‑95 work when:
- You are implementing or re‑architecting MES or major ERP/MES integration.
- You have fragmented order, material, and production data across multiple systems and spreadsheets.
- Cross‑system traceability and reporting are weak or highly manual.
In many plants, a pragmatic approach is to stabilize S88 usage at the control/batch level first, then use ISA‑95 to bring consistent structure to MES and ERP integration, rather than attempting a full top‑to‑bottom re‑platform, which often fails in regulated, long‑lifecycle environments.
