ISA-88 (also referred to as S88) is an international standard for batch control developed by the International Society of Automation. When people say the “ISA-88 format,” they usually mean one of two things:
- The ISA-88 conceptual models for how batch processes, equipment, and recipes are structured.
- An ISA-88-inspired data structure used by a specific vendor (for example, how a batch server or MES stores recipes and procedures).
ISA-88 itself is not a single file format or data interchange standard like XML or JSON. It is primarily a set of models and terminology that define how to represent and break down batch manufacturing.
What ISA-88 actually defines
ISA-88 provides a consistent way to model batch operations, covering:
- Physical model: Enterprise, site, area, process cell, unit, equipment module, control module.
- Procedural model: Procedures, unit procedures, operations, phases.
- Recipe models: General, site, master, and control recipes, with defined sections (header, equipment requirements, formula, procedure, etc.).
Vendors implement these concepts in their own databases, configuration tools, and sometimes proprietary or semi-standardized file structures. Those implementations are often described informally as being in “ISA-88 format,” but the exact schema is vendor-specific.
How “ISA-88 format” shows up in real systems
In brownfield environments, you are likely to see ISA-88 concepts used in several ways:
- Batch control systems / DCS: Recipe editors and batch engines that organize logic into procedures, unit procedures, operations, and phases mapped to units and equipment modules.
- MES or eBR systems: Data models that distinguish master recipes from control recipes and link them to equipment and material genealogy.
- Export/import structures: XML, JSON, or proprietary files that contain recipes, phase logic references, and equipment requirements in an ISA-88-like hierarchy.
The structure may follow ISA-88 closely, but the serialization format (file type, schema, APIs) is implementation-dependent. There is no universal, regulator-recognized “ISA-88 file format.”
Implications for regulated, long-lifecycle plants
For operations, engineering, and quality teams, the practical questions are less about a specific ISA-88 file format and more about how ISA-88 modeling affects:
- Traceability: Mapping batch records back to units, equipment modules, and phases in a consistent way.
- Change control: Managing revisions of master and control recipes, including procedures and formulas, under formal change management and validation.
- System coexistence: Keeping an ISA-88-based batch system aligned with legacy MES, ERP, and QMS structures that were not designed around S88.
- Validation burden: Any change to recipe models or control logic can trigger revalidation, especially in GMP or aerospace-grade contexts.
Attempting to replace all non-ISA-88 systems with a single “pure S88” platform is rarely practical in regulated environments. The qualification burden, downtime required for cutovers, and integration with legacy historians, MES, and ERP typically make big-bang replacement high risk. Incremental adoption of ISA-88 concepts around existing assets is more common.
Key tradeoffs when using ISA-88-based structures
When you standardize on ISA-88 models in a brownfield environment, expect tradeoffs:
- Pros:
- Clear, shared vocabulary for engineering, operations, and IT.
- More reusable and modular batch logic (phases, operations, unit procedures).
- Better alignment between equipment capabilities and recipe requirements.
- Cons / constraints:
- Legacy systems may not map cleanly to ISA-88 models, leading to compromise mappings.
- Integration and data exchange rely on vendor-specific schemas or custom interfaces.
- Retrofitting S88 structure onto older control code can be invasive and slow, especially under strict change control.
Practical guidance
If someone in your organization asks for data “in ISA-88 format,” clarify the intent:
- Do they need ISA-88-compliant recipe structures (e.g., procedure, operations, phases) from a batch system?
- Do they expect a specific vendor’s export format that follows ISA-88 concepts?
- Are they referring to modeling and naming conventions for equipment and recipes rather than a file format?
From there, you can determine what is feasible given your control systems, MES, and validation constraints, and whether you need a one-time migration, a connector, or just harmonized modeling across systems.
