Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
ISA-88 and ISA-95 solve different problems: ISA-88 describes how batch equipment and procedures execute a recipe; ISA-95 describes how manufacturing operations exchange information with business systems. An IIoT platform can connect and process that information, but it does not replace either model. Used together, the standards help keep batch meaning intact as information moves from control systems to operations management and enterprise applications.
What ISA-88 describes
ISA-88, also adopted as IEC 61512, is a model and terminology for batch control. It helps teams describe the equipment used to make a batch, the procedures that run it, the recipe parameters that guide it, its operating states, and the records produced during execution. The goal is consistent, understandable batch control—not a particular software product or control-system brand.
Its main models address two complementary views:
- Physical model: the equipment hierarchy, from a process cell and units down to equipment modules and control modules. It helps define what equipment exists and how responsibilities are divided.
- Procedural model: the hierarchy of procedures, unit procedures, operations, and phases that describes how equipment carries out a process.
A recipe brings process requirements together with procedural instructions and parameter values. A batch record captures information about what happened during execution. ISA’s official description also includes standardized data structures and terminology; the ISA88 committee scope describes the aim as simplifying programming, configuration, and communication among system components.
ISA-88 was first published in 1995 and adopted by the IEC in 1997 as IEC 61512-1, according to the International Society of Automation’s 2020 history. Its concepts can be implemented in PLC, DCS, MES, or other engineering and software environments.
#1 Best Overall
What ISA-95 describes
ISA-95, also known as IEC 62264, is a model for integrating enterprise and manufacturing-control functions. It provides shared terminology, equipment and activity models, and a way to describe information exchanges. It is commonly explained with Purdue-oriented levels, which indicate functional scope rather than a mandatory physical network design.
| Level | Typical scope |
|---|---|
| Level 0 | The physical process itself |
| Level 1 | Sensing and actuation |
| Level 2 | Supervisory control, such as control-system and SCADA functions |
| Level 3 | Manufacturing operations management, including MOM and MES activities |
| Level 4 | Business planning and logistics |
The interface between Levels 3 and 4 is a familiar focus: for example, business systems may send production requirements, while manufacturing operations report production results. ISA-95 also helps describe boundaries and information needs across the wider stack; it is not limited to one software interface or a single point-to-point connection.
How ISA-88 and ISA-95 work together
Use ISA-88 to describe the batch’s equipment and execution logic. Use ISA-95 to describe the operational and business context in which that batch is requested, scheduled, supplied, and reported. ISA identifies technical report ISA-TR88.95.01, “Using ISA-88 and ISA-95 Together,” as guidance for aligning the models, terminology, and data structures.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Question or concern | ISA-88 | ISA-95 / IEC 62264 | IIoT platform |
|---|---|---|---|
| Primary scope | Batch equipment, procedures, recipes, and states | Operations information and integration between manufacturing and enterprise functions | Connectivity, transport, processing, analytics, and applications |
| Typical artifacts | Physical and procedural models, recipes, batch records | Equipment, personnel, material, process-segment, and operations-exchange models | Device models, events, telemetry, APIs, and analytics or digital-twin models |
| Key question | How should this batch execute? | What information must manufacturing and business functions exchange? | How can data be transported, contextualized, analyzed, and acted on? |
For example, an enterprise planning system can communicate a production request and relevant material or schedule information to manufacturing operations. An MES can then use the request in the context of an ISA-88 recipe and available equipment. The control system executes the batch, and operations can return production responses or events to enterprise systems using ISA-95 concepts. This is a conceptual division of work; exact system ownership and interfaces vary by implementation.
Where IIoT platforms fit
An IIoT platform typically supplies implementation capabilities around the models: connecting devices and control systems, moving data through edge or cloud services, storing events and telemetry, and supporting analytics or applications. It should preserve ISA-88 meaning when exposing batch information and ISA-95 context when exchanging manufacturing and enterprise information. A stream of values without identifiers for the batch, equipment, procedure, or event can be difficult to interpret or use consistently.
ISA-95 is technology-agnostic and activity-focused; it does not prescribe a particular cloud, broker, API, or product. ISA-88 likewise defines models rather than one runtime. As a result, an IIoT implementation may use several standards in combination rather than expecting one to cover every layer. NIST’s smart-manufacturing standards landscape places IEC 61512 (ISA-88), IEC 62264 (ISA-95), OPC UA, BatchML, and PackML among standards relevant to connected manufacturing. ISO/IEC TR 30166 frames IIoT as a broader system landscape with technical, functional, and non-functional elements involving multiple standards organizations.
Rank #3
OPC UA and PackML
OPC UA can provide interoperable communication for structured information, but choosing OPC UA alone does not guarantee that two systems agree on the meaning or context of every data item. That still depends on the information model, mappings, identifiers, and implementation choices.
PackML is relevant in machine and packaging settings. The OPC Foundation says it was created by OMAC to extend ISA-88 terminology and concepts to packaging, assembly, filling, and other production machines. It is a companion for those environments, not a substitute for ISA-95’s enterprise integration role.
A practical way to apply the models
- Define the batch process. Identify the process cell, units, modules, procedures, recipe parameters, states, and batch records that matter to execution. Keep equipment structure and procedural logic clear enough to reuse and maintain.
- Identify the information crossing system boundaries. List what enterprise planning, MOM/MES, and control functions need to send or receive: production requests, schedules, material and equipment context, production responses, and operational events.
- Map terms and identifiers deliberately. Agree how a batch, product, material, unit, operation, and event will be identified in each system. Preserve the relationships needed to connect batch records to operations and enterprise records.
- Select transport and platform components. Decide where OPC UA or other interfaces provide connectivity, what runs at the edge or in the cloud, and which applications consume the information. Treat transport choice and semantic agreement as separate design decisions.
- Assign ownership and governance. Control engineering typically owns batch execution models; MOM/MES and integration teams own operational exchanges; platform, OT/IT, and analytics teams own connectivity and platform services. Establish how model changes, mappings, and versions are reviewed across those teams.
- Validate end-to-end behavior. Trace a representative production request through scheduling, batch execution, recording, and production response. Check that context survives each handoff and that an event can be understood by its receiving system.
What an implementation example can—and cannot—show
Siemens TIA Portal documentation describes an ISA-88-conformant physical model from a unit down to control modules. This is an example of an engineering environment implementing the model; it does not make ISA-88 a Siemens-specific product or mean that a particular platform automatically resolves enterprise integration.
ISA has also reported implementation experience from Dennis Brandl of 30 percent savings on a first project and up to 80 percent on follow-up projects through modular reuse (International Society of Automation/InTech, 2020). These are reported project outcomes, not independently established industry-wide benchmarks or guaranteed savings for a new implementation.
How to assess a proposed architecture
When comparing designs or products, evaluate them against the information and responsibilities they actually need to support:
Recommended Free Tools
- Scope and abstraction: Does the component address batch execution, enterprise operations exchange, connectivity, or more than one of these?
- Information exchanged: Can it represent the recipes, equipment, materials, production requests, responses, and events relevant to the use case?
- Context and interoperability: Are identifiers and relationships preserved, and are interfaces based on agreed models rather than only vendor-specific fields?
- Timing and resilience: Which information needs prompt delivery, and what happens during a network outage or delayed synchronization?
- Lifecycle ownership: Who maintains batch models, interface mappings, platform components, and change governance?
These checks keep the standards in their proper roles: ISA-88 gives batch execution structure, ISA-95 frames operational and enterprise exchanges, and IIoT technologies connect and use the resulting information.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
