At the bottom of the ISA-88 procedural hierarchy is the element where a recipe finally causes something to happen in the plant: the phase. But there are really two sides to a phase, and confusing them causes endless trouble. The recipe side carries the parameters and targets that describe what should happen, while the equipment side holds the logic that actually drives the valves and setpoints. This guide explains what a recipe phase is, how the recipe-side and equipment-side phases relate, what parameters and report parameters a phase carries, and how a sequencer commands a phase through start, hold, restart, stop, and abort.
recipe phase in one line: A recipe phase is the smallest procedural element in ISA-88 that triggers a process-oriented action, such as charging a set amount of material or holding a temperature for a time. On the recipe side it is defined by its parameters and targets, the values that tell the phase what to do, while a separate equipment phase holds the actual logic that drives the valves, pumps, and setpoints. The recipe phase supplies the intent and the numbers; the equipment phase carries them out.
A phase is where the procedural hierarchy stops describing and starts doing. The levels above it, procedure, unit procedure, and operation, organise and sequence, but they do not themselves touch the equipment. The phase is the smallest procedural element that triggers a process-oriented action: it is the step that says charge this much reagent, agitate for this long, or heat to this temperature. Everything above the phase is arrangement; the phase is the point where arrangement becomes a real change in the process. That is why it sits at the base of the hierarchy and why it is the element that ultimately matters to the plant.
Because it is the action-causing element, a phase corresponds to a discrete, meaningful bit of processing. A charge phase adds a defined quantity of a material. An agitate phase runs a mixer for a defined period or condition. A heat phase brings a batch to a target and holds it. Each of these is small enough to be a single coherent action yet complete enough to be worth naming and sequencing. The recipe is ultimately a structured arrangement of such phases, and the phases are what actually get the batch made, one action at a time.
This makes the phase the natural point of connection between the recipe world and the equipment world. Everything above the phase is about strategy and sequence and is largely independent of the specific hardware; the phase is where that strategy meets a particular piece of equipment that must carry it out. Understanding the phase therefore means understanding that it has two faces: the recipe-side definition of what to do, and the equipment-side logic of how to do it, which are deliberately kept separate so that recipes and equipment can vary independently.
The recipe-side phase is the phase as it appears in the recipe: a named step with parameters that specify what it should achieve. It does not contain the logic that manipulates equipment. Instead, it carries the intent and the numbers, such as the target quantity for a charge or the temperature and time for a hold, and it points to the equipment phase that will actually do the work. The recipe-side phase is portable in the sense that it describes what to do in terms the recipe understands, without embedding the details of how any particular skid or vessel accomplishes it.
The equipment phase, sometimes called the equipment phase logic, is the counterpart that lives with the equipment and actually drives it. It is the code that opens and closes valves, starts and stops pumps, ramps setpoints, and watches conditions to accomplish the phase's purpose on real hardware. When a charge phase runs, it is the equipment phase logic that sequences the valves and reads the flow to deliver the requested amount. This logic is written against a specific equipment module, so it embodies the how, while the recipe-side phase supplies the what. The two are joined when the phase runs, with the recipe-side parameters handed to the equipment logic.
Keeping these two sides separate is a core discipline of ISA-88 and the source of much of its power. Because the recipe-side phase describes intent and the equipment phase holds the mechanism, the same equipment phase logic can serve many recipes, and the same recipe can, in principle, run on any equipment that provides the matching phases. A person configuring batch execution has to map each recipe-side phase to the equipment phase that will carry it out, and getting that mapping right, so that the recipe's parameters are correctly consumed by the equipment logic, is exactly the work of connecting the recipe world to the plant. Blurring the two, by baking equipment specifics into recipes or recipe intent into equipment code, is what makes batch systems brittle.
A phase carries parameters in both directions. Phase parameters, sometimes called formula or input parameters, are the values passed into the phase to tell it what to do: the amount to charge, the temperature to reach, the duration to hold. These come from the recipe and are what make a phase adjustable, so the same charge phase can add different quantities in different recipes simply by giving it a different parameter. Report parameters run the other way: they are values the phase produces and hands back when it completes, such as the actual amount charged or the actual peak temperature, which feed the batch record and let the recipe react to what really happened.
This two-way flow of parameters is central to how batch execution works. The recipe supplies phase parameters as targets, the equipment phase logic uses them to drive the process, and it returns report parameters describing the outcome. That outcome becomes part of the batch history and can influence subsequent steps. A configurer setting up a phase therefore has to define both what the phase needs to be told and what it should report back, and to ensure the recipe supplies the former and captures the latter. The parameter interface is the contract between the recipe-side phase and the equipment phase.
A phase does not simply run to completion untouched; it is commanded by the sequencer that drives the batch, and it responds to a defined set of commands that govern its life. The sequencer can start a phase to begin its action, hold it to pause in a safe state, restart it to resume from a hold, stop it to end it in a controlled way, and abort it to terminate it quickly when something is wrong. The equipment phase logic must implement sensible behaviour for each of these, so that a hold parks the process safely and an abort brings it to a safe stop. This command set is what lets a batch be paused, resumed, or halted cleanly, and it is why the phase, small as it is, must be a well-behaved state machine rather than just a script that runs once.
Because the phase is where action happens and where parameters and results are exchanged, it is also the level at which batch execution is most visible. As a batch runs, the currently active phase, its parameters, its state, and its emerging report values describe exactly what the process is doing at any moment. A supervisory layer that tracks phases sees the batch not as an opaque process but as a sequence of named actions with numbers attached, which is what makes it possible to say precisely where a batch is and how it is behaving. The phase is the finest-grained honest picture of what the plant is doing.
For operations that run batches across multiple sites or many units, surfacing this phase-level detail centrally is what turns remote batch monitoring from guesswork into real visibility. A cloud SCADA platform such as Merobix can present which phase each unit is executing, the parameters it was given, its current state, and the report values it produces, alongside the underlying process data. A team watching from anywhere can then see that a charge phase is running, how much it has delivered against its target, and whether it completed cleanly, without standing at a batch panel. The phase's parameter and report structure is exactly the information a monitoring layer needs to make batch progress legible.
This visibility also supports the command side of phases in a distributed setting. Knowing that phases respond to start, hold, restart, stop, and abort means a supervisory view can show not just where a batch is but whether it is proceeding normally, paused in a hold, or being aborted, which is critical information when nobody is standing beside the equipment. Presenting phase state and history centrally lets a remote team understand and, where appropriate through the batch system, respond to what is happening at the action level of the batch. The clean, parameterised, command-driven nature of the ISA-88 phase is what makes a batch running on distant equipment something a central team can actually follow and trust.
A recipe phase is the recipe-side step that carries the intent and parameters, such as the amount to charge or the temperature to hold, describing what should happen. Equipment phase logic is the counterpart that lives with the equipment and actually drives the valves, pumps, and setpoints to accomplish it. The recipe phase supplies the what and the numbers; the equipment phase supplies the how, and the two are joined when the phase runs.
Phase parameters, sometimes called formula or input parameters, are values passed into a phase to tell it what to do, such as a target quantity or temperature, and they make the phase adjustable between recipes. Report parameters run the other way: they are values the phase produces on completion, such as the actual amount charged, which feed the batch record and can influence later steps. Together they form the two-way contract between recipe and equipment.
A sequencer drives a phase through a defined set of commands: start to begin the action, hold to pause in a safe state, restart to resume from a hold, stop to end it in a controlled way, and abort to terminate it quickly when something is wrong. The equipment phase logic must implement sensible behaviour for each, so a hold parks the process safely and an abort stops it safely, which lets a batch be paused, resumed, or halted cleanly.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.