Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 61512-3-2008: Batch Control โ Recipes (Part 3)
💡 Engineering Insight: The recipe model defined in IEC 61512-3 (aligned with ISA-88) separates product knowledge from equipment capability through the procedural control model — enabling true equipment-independent recipe management and accelerating product changeovers in multi-product batch facilities.
1. Scope and Recipe Model Concepts
IEC 61512-3-2008 is Part 3 of the IEC 61512 series on batch control, addressing the representation and management of recipes in batch manufacturing processes. The standard defines a comprehensive recipe model that encompasses four recipe types: general, site, master, and control recipes. Each type serves a distinct purpose at different levels of the manufacturing hierarchy, from corporate product development through site-level planning to plant-floor execution.
The recipe model is built on the procedural control model defined in IEC 61512-1 (equivalent to ISA-88), which decomposes batch manufacturing into a hierarchy of procedural elements: procedure, unit procedure, operation, and phase. The standard specifies how recipe information — including formula, equipment requirements, and procedural logic — is structured and represented within each level of this hierarchy. This separation of recipe (product-specific knowledge) from equipment control (plant-specific capability) is the fundamental innovation that enables recipe portability across different facilities and equipment configurations.
⚠ Key Concept: A general recipe represents product knowledge independent of specific equipment. Through successive transformations — general to site to master to control — recipe information is progressively refined with equipment-specific parameters while preserving the product knowledge core. This allows a product developed in R&D to be manufactured at any suitably equipped plant in the enterprise network.
2. Recipe Types and Structure
The standard defines four recipe types with specific characteristics and applications:
| Recipe Type | Scope | Key Content | Recipes Can Be Transformed To |
|---|---|---|---|
| General Recipe | Enterprise/corporate (product-focused) | Product knowledge, chemical reactions, processing requirements, quality targets | Site recipe |
| Site Recipe | Site/location-specific | Site-specific equipment classes, local raw materials, regulatory constraints | Master recipe |
| Master Recipe | Process cell (equipment-specific) | Equipment-specific parameters, process cell target device control recipes, process parameters | Control recipe |
| Control Recipe | Batch-specific (single batch instance) | Batch ID, actual equipment assignments, dynamic parameter values, batch history | (Executes on equipment) |
2.1 Recipe Procedural Elements
The standard defines a hierarchical procedural model that provides the structure for recipe execution. At the top level, a procedure describes the overall strategy for producing a batch. A procedure is composed of unit procedures, each of which represents a major processing activity typically executed in a single unit. Unit procedures are composed of operations, which represent specific processing actions (e.g., charge, heat, react, cool, transfer). Operations are composed of phases, the lowest level of procedural control that can initiate and manage equipment actions. Each phase represents a finite state machine with defined states (idle, running, complete, paused, holding, held, stopping, stopped, aborting, aborted) that provide precise control over batch execution.
3. Engineering Design Insights and Applications
The recipe transformation process — converting a general recipe through successive refinements into executable control recipes — is one of the most powerful concepts in the standard, but also one of the most challenging to implement in practice. The transformation from general to site recipe typically involves selecting appropriate equipment classes and specifying local raw material substitutions. The site-to-master transformation requires mapping unit procedures to specific process cell equipment and defining equipment-specific parameters such as expected transfer times, heat transfer coefficients, and agitator speed ranges. The master-to-control transformation creates a batch-specific instance with actual equipment assignments, batch identifiers, and dynamic parameters such as process setpoints calculated from the batch size.
A practical challenge in recipe implementation is managing the interaction between recipe phases and equipment phases. IEC 61512-3 defines that a recipe phase initiates and coordinates equipment phases, but the recipe phase should not contain detailed equipment control logic. For example, a “Heat to Temperature” recipe phase would initiate an equipment phase “Temperature Control” on the appropriate unit, passing the target temperature setpoint. The equipment phase manages the PID control loop, heating rate limits, and safety interlocks. This separation ensures that recipe logic remains equipment-independent and that equipment phases can be optimised without modifying recipes.
🔥 Critical Warning: A common implementation error is embedding equipment-specific control logic directly in recipes, which destroys the equipment independence that is the primary benefit of the standard. When a recipe contains hard-coded pump run times or valve positions, any equipment change requires recipe modifications, defeating the purpose of the procedural control model.
💡 Engineering Practice: When designing the procedural element hierarchy for a new batch process, start by identifying the natural processing operations (charge, heat, react, sample, cool, transfer, discharge) before defining phases. Each operation should be self-contained and represent a meaningful process step that could potentially be reordered or omitted depending on the product variant being manufactured.
The standard also addresses the important topic of recipe management for exception handling. Batch processes frequently encounter process deviations, equipment failures, or operator interventions. IEC 61512-3 specifies how recipes should handle exceptions through state transitions in the procedural element state machine. For example, if a reactor reaches a high-temperature alarm during the “React” phase, the procedural element transitions from “running” to “holding” state, initiating the hold procedure defined in the recipe. The hold procedure may specify actions such as reducing the heating rate, activating additional cooling, or waiting for operator confirmation. After the condition is resolved, the procedural element transitions back through “restarting” to “running” to complete the phase.
4. Frequently Asked Questions
Q1: What is the difference between IEC 61512 and ISA-88?
IEC 61512 is the international standard that is technically identical to the ISA-88 series. IEC 61512-1 corresponds to ISA-88.01, IEC 61512-2 to ISA-88.00.02, and IEC 61512-3 to ISA-88.00.03. The two standards are maintained in alignment through formal liaison between IEC and ISA.
Q2: Can recipes be transferred between different manufacturers’ batch control systems?
With proper implementation of the IEC 61512-3 recipe model, recipe transfer between systems from different vendors is possible but requires careful attention to the recipe representation format. The standard recommends an XML-based recipe exchange format (BatchML) for cross-platform recipe portability.
Q3: How does the recipe model handle different batch sizes?
The recipe model separates formula parameters into two categories: scale-dependent and scale-independent. Scale-independent parameters (such as reaction temperature and pressure targets) remain constant regardless of batch size. Scale-dependent parameters (such as raw material quantities) are calculated based on the batch size using scaling algorithms defined in the recipe formula.
Q4: What is the role of an “equipment phase” versus a “recipe phase”?
A recipe phase is defined in the recipe and describes what needs to be done from a process perspective. An equipment phase is defined in the equipment control system and describes how the equipment will accomplish the required action. The recipe phase initiates the equipment phase, passes parameters, and monitors its progress, but does not contain the detailed control logic.
