What is ISA-88? A Practical Overview of the Batch Control Standard

What is ISA-88?

ISA-88, formally known as ANSI/ISA-88.01-1995 and also referenced as S88 or IEC 61512, is an international standard that defines models and terminology for batch control in manufacturing processes. The standard originated from the work of the International Society of Automation (ISA) SP88 committee in the early 1990s, driven by the need for a consistent set of concepts that could be applied across plants, vendors, and automation platforms. Rather than prescribing specific control algorithms or batch control software configurations, ISA-88 provides a structured framework for describing how batch processes work, how equipment is organized, and how recipes translate product requirements into executable procedures.

The standard was developed primarily for batch process industries such as pharmaceuticals, specialty chemicals, food and beverage, and biotechnology. However, the underlying concepts have proven useful in any manufacturing environment where finite quantities of material are produced through defined sequences of processing activities on shared or reusable equipment. ISA-88’s main contribution is the conceptual separation of recipe, equipment, and process, which provides a common language for control engineers, IT teams, operations personnel, and management. This separation allows organizations to describe what they make, where they make it, and how they make it as distinct but connected concerns.

Connect981 works with manufacturers that often rely on ISA-88 concepts to structure their batch documentation, traceability, and shopfloor workflows, even when control systems differ across sites or supplier facilities. The models and terminology defined by the standard offer a foundation for consistent communication regardless of the specific batch automation platforms in use.

Batch Manufacturing and Batch Control Context

Batch production involves creating finite quantities of material by subjecting inputs to an ordered sequence of operations over a defined period, typically using equipment that can be reconfigured or reused for different products. This stands in contrast to continuous processing, where material flows through a plant without discrete start and stop points, as in large petroleum refineries or paper mills. It also differs from one-off discrete manufacturing, such as custom fabrication of a unique part, where each item may follow a distinct path.

Many regulated and high-mix environments rely on batch logic. Pharmaceutical manufacturing, for example, produces defined lots of tablets or injectable solutions where every batch must meet strict quality specifications. Chemical processors run different formulations through shared reactors and separators. Food manufacturers produce finite runs of different product recipes on the same filling and packaging lines. In each case, batch operations coordinate what happens, when it happens, and on which equipment, covering activities such as charging materials, heating, holding, reacting, cooling, and discharging.

In life sciences and aerospace-related special processes, the batch concept extends to operations like composite curing, surface treatment baths, and heat treatment cycles. These batches must be tightly controlled and fully traceable to support regulatory compliance and product quality. ISA-88 provides a consistent way to model this complexity so that procedures, equipment capabilities, and recorded batch data remain aligned and auditable across different sites, systems, and even supplier networks.

Purpose and Scope of the ISA-88 Standard

The primary goal of ISA-88 is to define a common set of models and terminology for batch control that can be applied consistently across plants, control systems, and suppliers. Before the standard existed, batch automation was often implemented using custom, plant-specific software that made it difficult to transfer processes between sites, communicate requirements to automation vendors, or integrate systems from different manufacturers.

ISA-88 addresses these challenges by improving efficient communication between process engineering, automation, IT, and operations teams. The standard enables modular, reusable design of batch procedures, meaning that a well-defined phase or operation can be deployed across multiple products without being rewritten for each application. It also supports regulatory compliance by providing structured data structures for batch production records, making it easier to demonstrate traceability and process consistency during audits.

The ISA-88 standard is organized into multiple parts. Part 1 establishes the core models and terminology. Part 2 covers data structures and guidelines for languages used to represent batch logic. Part 3 extends the recipe framework to general and site recipe models that support multi-site standardization. Part 4 defines a data model for batch production records, capturing materials, activities, and process conditions. Part 5 addresses modular concepts for automated control systems, applying ISA-88 principles to reusable automation components. These parts are discussed in more detail later in this article.

The boundaries of the standard’s scope are deliberate. ISA-88 focuses on batch control models and data structures, not on mechanical design, detailed safety interlock systems, or business planning logic. It is also technology-agnostic: the concepts apply whether batch control is implemented on PLCs, DCS platforms, SCADA systems, MES layers, or custom batch engines. Higher-level coordination may use modern platforms like Connect981 or legacy tools, and the ISA-88 framework remains applicable in either case.

Core ISA-88 Models and Terminology

ISA-88 defines a set of abstract models that describe batch processes from multiple perspectives. These include the process model, the physical model, and the procedural control model, along with standardized terminology such as process cell, unit, phase, and recipe. Each model provides a different view of the same manufacturing reality. The process model focuses on the scientific and chemical requirements of what must happen to the material. The physical model describes the equipment hierarchy that exists in the plant. The procedural control model captures how operations are executed over time, connecting process requirements to physical resources.

These models give multidisciplinary teams a shared framework for discussing batch operations without getting lost in vendor-specific control code or hardware details. The following subsections introduce each model and its key components.

ISA-88 Process Model

The process model describes the manufacturing process in terms of what needs to happen to the material, independent of specific physical equipment. It uses a hierarchy of process, process stages, process operations, and process actions. At the top level, a process represents the complete set of steps required to transform raw materials into a final product. For example, in pharmaceutical manufacturing, this might encompass everything from raw active ingredients and excipients through to compressed tablets ready for packaging.

Process stages break the overall process into major segments that are meaningful to process engineers and quality teams. These might include stages such as solution preparation, reaction, purification, and finishing. Each stage represents a significant portion of the overall transformation without yet specifying which tanks, reactors, or dryers will be used.

Process operations and process actions allow further refinement. Operations capture logical steps within a stage, while actions represent elementary tasks such as charging solvent, heating to a setpoint, agitating, or holding for a defined reaction time. Throughout this hierarchy, the process model remains equipment-agnostic. This allows organizations to define a common process description that can later be mapped onto different physical installations, whether at a headquarters plant, a contract manufacturer, or a supplier facility. In aerospace-related special processes, the process model might capture stages like surface preparation, coating application, cure, and post-cure inspection, without assigning specific ovens or spray booths.

ISA-88 Physical Model

The physical model represents the real equipment hierarchy that exists in a manufacturing facility. ISA-88 defines levels including enterprise, site, area, process cell, unit, equipment module, and control module, though batch control typically focuses on the levels from process cell downward.

A process cell is a collection of control equipment arranged to produce one or more products. For example, a pharmaceutical process cell might include a set of reactors, filters, and dryers that can be combined in various configurations to run several different recipes. The process cell is the scope within which batch control coordinates activities.

Units are major pieces of physical equipment capable of carrying out unit procedures. A reactor vessel, blending tank, granulator, or autoclave would each be considered a unit. In the standard model, each unit operates on one batch at a time, making it a natural boundary for procedural execution and traceability.

Equipment modules represent functional groupings within or across units. A dosing skid, heating loop, or clean-in-place module would be examples. Control modules sit at the lowest level and include individual devices like valves, motors, sensors, and measurement instruments. These are the components that receive basic control commands and provide feedback to higher-level logic.

The physical model allows batch designers to reason about what each part of the plant can do, independent of any specific recipe. This makes it easier to reuse units or modules across many products and to understand capacity constraints when scheduling batch production. While ISA-88 was created for control systems, the same physical structure proves useful in higher-level digital tools for mapping work instructions, traceability, and maintenance records onto specific units and modules.

ISA-88 Procedural Control Model

The procedural control model describes how a batch is executed over time, using a hierarchy of procedure, unit procedure, operation, and phase. A procedure represents the complete set of steps needed to run a batch, mapped to a process cell. A unit procedure is a logical segment tied to a specific unit, such as a charging and reacting sequence that takes place entirely within a single reactor.

Operations divide unit procedures into smaller logical steps. Phases are the smallest procedural elements, directly interacting with equipment modules and control modules. A phase might represent actions such as starting an agitator, heating and holding at a setpoint, or transferring material to a buffer tank. Phases are where sequential control and regulatory control commands are typically applied to the physical equipment.

The procedural control model is where the separation between recipe logic and equipment capability becomes operational. The same unit might support phases used by multiple different recipes. A reactor that can heat, cool, agitate, and transfer can execute phases for dozens of products without requiring new control logic for each one.

ISA-88 also defines standard execution states and transitions for phases and units. These include quiescent states like idle and held, transient states representing transitions, and final states indicating completion. The standard provides guidelines for unit states without prescribing PLC programming patterns or specific vendor implementations. This allows multidisciplinary teams to discuss sequence behavior and exception handling using common terminology.

Consider a simple unit procedure: charge materials, heat to reaction temperature, hold for reaction time, cool to discharge temperature, transfer to the next unit. This sequence illustrates how the procedural control model organizes activities without specifying the exact valve sequences or controller settings that would vary by installation.

Separation of Recipe, Equipment, and Process in ISA-88

One of ISA-88’s defining principles is the clear separation of three concerns: what must happen to the material (process), what physical resources exist (equipment), and how a specific product is made at a given site (recipe). This separation allows each concern to be managed, documented, and changed somewhat independently.

ISA-88 defines several recipe types that sit on top of the process and physical models. A general recipe describes a product at a high level, independent of any specific site. A site recipe adapts that general recipe to the capabilities and constraints of a particular manufacturing location. A master recipe adds equipment-specific details for a particular process cell or set of units. A control recipe is the actual executable instance created for a single batch, containing specific parameter values, material quantities, and equipment assignments.

The process model expresses product and chemistry requirements. The physical model describes available units and modules. Recipes bind these two worlds together for a specific product on specific equipment. Recipe management becomes a structured activity rather than ad-hoc customization of control code.

This separation creates practical benefits for organizations. Moving a recipe between sites with different equipment layouts becomes a matter of adapting the recipe at the appropriate level rather than rewriting control logic from scratch. Introducing new equipment modules does not require rethinking the entire product definition if the module can support the required phases. Change control and validation in regulated industries become more tractable when process intent, equipment capability, and recipe parameters are documented in aligned but distinct structures.

Consider scaling a biotech fermentation process from a pilot plant to commercial production. The process model describes the fermentation requirements: media preparation, inoculation, growth phase, harvest. The pilot plant has one set of units with specific volume and control capabilities. The commercial plant has larger fermenters with different instrumentation. By maintaining the separation, the organization can adapt recipes to the new physical model without changing the underlying process definition.

In aerospace and MRO operations, many special processes and repair routes follow similar patterns. Process requirements remain stable, specifying what must happen to achieve required material properties or surface conditions. Equipment assignments and control recipes may vary between in-house facilities, approved suppliers, or partner locations. The ISA-88 framework provides a conceptual structure for managing this variation while maintaining traceability and compliance.

What ISA-88 Standardizes (and What It Does Not)

ISA-88 standardizes how to describe batch processes, equipment, procedures, and data. It does not standardize how to program or configure specific batch control systems. This distinction is fundamental to understanding the standard’s role and limitations.

What ISA-88 Standardizes	What ISA-88 Does Not Standardize
Common terminology for batch control objects	Specific PLC, DCS, or MES configurations
Conceptual models (process, physical, procedural)	Control algorithms or tuning parameters
Types and structure of recipes	User interface layouts or alarm designs
High-level data structures and relationships	Enterprise planning logic (scheduling, capacity)
Concepts for batch production records	Vendor-specific file formats
Modular automation concepts	Manual processes implementation details
Functional model guidelines	Data acquisition system specifics

The standard provides guidelines rather than rigid specifications. It establishes that a control recipe should contain a header, formula, equipment requirements, and procedure, but it does not dictate the database schema or file format used to store that information. It defines what regulatory control and basic control mean in a batch context, but it does not provide guidelines on specific tuning approaches or controller selection.

This deliberate boundary allows ISA-88 to remain stable and vendor-neutral while giving suppliers and manufacturers freedom to innovate implementations. Organizations often map ISA-88 structures onto their own databases, MES systems, or digital operations platforms to maintain consistency from control logic through documentation and traceability without enforcing a single control technology. Connect981, for example, helps organizations structure shopfloor workflows and documentation in ways that align with ISA-88 concepts even when underlying batch control software varies across sites.

The standard is just a standard: a conceptual framework rather than a turnkey solution. Its value lies in widespread adoption of common terminology and models that enable smooth integration across disciplines, vendors, and organizational boundaries.

Relationship Between ISA-88 and ISA-95

ISA-95 is a companion standard focused on integrating enterprise systems and control systems. While ISA-88 addresses the structure of batch control at the equipment and process cell level, ISA-95 defines models for how information flows between higher-level business systems (ERP, planning, MES) and lower-level control environments.

In terms of the Purdue reference model, ISA-88 primarily addresses Levels 1 and 2, where batch operations and control logic reside, with some extension into Level 3 for batch supervision. ISA-95 covers Levels 3 and 4, defining production operations management, scheduling, performance analysis, and inventory management. Together, the standards provide guidelines for a cohesive architecture from enterprise planning through shopfloor execution.

ISA-88 objects such as units, control recipes, and batch production records can be mapped into ISA-95’s production order, production schedule, and production performance models. Joint guidance from ISA working groups, including discussions at the World Batch Forum and related industry events, has clarified how these mappings work in practice.

Consider a practical example: an ERP system creates a production order for a batch of specialty chemicals. This order, structured according to ISA-95 concepts, is translated into one or more control recipes and batch runs modeled according to ISA-88. As each batch executes, batch data is collected according to ISA-88’s production record concepts. Batch results then feed back as production responses and records into higher-level systems, completing the information loop.

Connect981 typically operates in the space between ERP/PLM and on-the-floor control, where ISA-95 production models and ISA-88 batch structures both matter. The platform helps organizations orchestrate work, share data with suppliers, and maintain audit-ready histories in ways that respect both standards’ concepts. Seamless integration between these levels is increasingly important as manufacturers pursue digital transformation and require better visibility across operations, quality, and supply chain functions.

Structure of the ISA-88 Standard Parts

ISA-88 is a multi-part standard developed over several decades, with parts published and maintained both by ISA and as IEC 61512 standards for international adoption. Understanding the structure helps organizations determine which parts are most relevant to their operations.

Part 1: Models and Terminology was published in the mid-1990s and remains the foundation of the standard. It defines the core process model, physical model, and procedural control model along with the vocabulary that has become widely adopted across batch industries. Any organization working with ISA 88 batch control should be familiar with Part 1 concepts.

Part 2: Data Structures and Guidelines for Languages extends Part 1 by describing data models for batch procedures and records. It provides guidance on how to represent batch logic and procedural elements in a structured way that supports implementation across different platforms. While more technical than Part 1, Part 2 is valuable for teams designing batch control software architectures or MES integrations.

Part 3: General and Site Recipe Models and Representation expands the recipe framework above the master and control recipe levels. It addresses how organizations can define recipes at corporate or general levels and then adapt them for specific sites, supporting multi-site standardization and technology transfer. This part is particularly relevant for large organizations with multiple manufacturing locations or extensive contract manufacturing networks.

Part 4: Batch Production Records defines a data model for capturing and storing batch histories, including activities, materials, and process conditions. This part directly supports regulatory compliance requirements in industries like pharmaceuticals, where complete batch records are mandatory for product release. The technical report guidance in Part 4 helps organizations design systems that capture the right information in auditable formats.

Part 5: Modular Concepts for Automated Control Systems applies ISA-88 concepts to modular, reusable automation components. This part extends the standard builds beyond traditional batch process industries to address modular equipment and plug-and-play automation scenarios that are increasingly common in flexible manufacturing.

The IEC 61512 series represents the international adoption of ISA-88, with only minor technical differences between the ISA and IEC versions. Global manufacturers often reference the IEC designation in their documentation, particularly when working with European suppliers or regulatory bodies.

Organizations rarely implement all of ISA-88 at once. Most selectively apply models and recipe concepts that align with their products, regulatory requirements, and legacy batch systems. The modular nature of the standard supports this approach, allowing organizations to adopt terminology and models progressively as their batch operations mature.

For organizations managing complex batch operations across aerospace, pharmaceutical, or chemical industries, understanding ISA-88 provides a common language that bridges engineering, operations, and compliance. Connect981 helps teams put these concepts into practice through digital work instructions, traceability, and workflow management that align with how batch operations are structured and documented. To explore how your batch documentation and shopfloor workflows can benefit from this structured approach, request a demo to see the platform in action.