A control recipe is the fully specified, executable instance of a recipe used to run a particular batch, lot, or production order in an automated or semi-automated manufacturing system. The term is most commonly associated with ISA‑88 (S88) batch control, but the concept also appears in other recipe-driven production environments.
What a control recipe includes
In an S88-style model, a control recipe typically contains:
- Identification information, such as recipe ID, batch ID, product code, and version
- The selected master recipe reference (the standard definition of how to make the product)
- Specific parameter values for this run, such as quantities, target setpoints, and timing
- Selected equipment and units, consistent with the plant’s equipment model
- Scheduling and sequencing information for the batch or order
- Links to required materials, intermediates, and consumables
- Required checks, holds, or approvals, such as quality checks or signoffs
- Reporting requirements, such as which data must be logged as batch records
The control recipe is what the control system (for example a batch engine, DCS, or MES) actually uses to orchestrate and monitor the production run.
Role in operations
Operationally, a control recipe connects the product definition to the plant floor:
- It is created from a master recipe when a specific batch, lot, or order is planned.
- It may be instantiated or managed by a batch management system, MES, or a dedicated recipe management system.
- It provides the control system with all necessary details to execute, monitor, and log the process.
- It often forms part of the electronic batch record or production history for compliance and traceability.
In regulated or highly controlled environments, version control and approval workflows are commonly applied to control recipes and the parameters they contain.
What a control recipe is not
- It is not the generic product definition. That is usually the domain of a master recipe or product specification.
- It is not the low-level equipment logic (for example PLC code or DCS configuration), although it references and drives that logic.
- It is not the long-term production plan or finite schedule, but it may be generated as part of scheduling.
Common confusion
Control recipe vs. master recipe: In S88, a master recipe is the generalized, approved description of how to manufacture a product. A control recipe is a specific, executable instance of that master recipe for a particular run, with concrete parameter values and equipment selections.
Control recipe vs. formula or BOM: A formula or bill of materials usually lists materials and quantities. A control recipe includes those, but also embeds the procedural steps, setpoints, and runtime instructions needed by the control system.
Connection to ISA‑88 (S88)
Within the ISA‑88 framework, control recipes are one of the defined recipe types. They support the separation of:
- What is being made (product and master recipe)
- How the plant equipment is organized (equipment model)
- How a given batch is actually executed in the control system (control recipe)
In practice, this separation allows plants to maintain standard master recipes while generating many different control recipes adapted to specific batch sizes, equipment availability, and order requirements.