The ISA-88 phase state model is the state machine that every phase in a batch obeys. It defines a fixed set of states a phase can be in, the commands an operator or the sequencer can issue, and the exact transitions between them. This rigor is what makes hold, restart, stop, and abort behave the same way across an entire plant, so operators can trust that a command means the same thing on every unit. Before you configure phases or design exception handling, this is the reference model you need to have in your head.
ISA-88 phase state model in one line: The ISA-88 phase state model is a standard state machine that governs every phase's behavior. It defines states - such as idle, running, complete, held, restarting, stopped, and aborted - and the commands and transitions that move between them, so that hold, restart, stop, and abort work predictably across all equipment.
The states divide into resting states and transient states. Resting states are stable places a phase can sit indefinitely: idle, where the phase is waiting and has not started; complete, where the phase has finished its normal work; held, where the phase is paused in a defined safe condition; stopped, where the phase has been terminated in an orderly way; and aborted, where the phase has been terminated quickly to a safe state. Running is the active resting state a phase occupies while it is doing its normal work.
Between the resting states are transient states that represent the phase working its way from one resting state to another. Holding is the act of moving a running phase into the held state, and restarting is the act of resuming from held back toward running. Stopping is the controlled shutdown that leads to stopped, and aborting is the fast shutdown that leads to aborted. Some implementations also model pausing and paused for a lighter, hold-point-based pause distinct from a full safe hold.
The distinction between resting and transient states is fundamental. A transient state is where logic actively runs to reach a resting state; a resting state is where the phase waits for the next command or, in the case of running, carries out its normal work. A well-behaved phase always settles into a resting state, so it is never left in limbo. This is why the model can guarantee predictability: from any resting state, the set of legal next commands is fixed and known.
Commands are what drive a phase between states. A start command takes a phase from idle into running. A hold command takes a running phase into holding and then to held; a restart command takes it from held into restarting and back to running. A stop command drives the phase through stopping to stopped, and an abort command drives it through aborting to aborted. A reset command returns a phase from complete, stopped, or aborted back to idle so it can run again.
The transitions are strictly defined so that only legal moves are allowed. You cannot restart a phase that is not held, and you cannot start a phase that is not idle. This tight definition is what prevents ambiguous or dangerous behavior: because the state machine rejects illegal commands, an operator cannot accidentally push a phase into an undefined condition. Every command has a defined effect from every state, or it is refused.
Abort and stop deserve special note because they can be issued from almost any active state and always lead to a defined safe resting state. That universality is deliberate: no matter what a phase is doing, an operator or an interlock must always be able to bring it to a safe, known condition. The state model guarantees there is always a path to safety, which is the foundation everything else in batch exception handling is built on.
For operators, the value of a rigorous state model is consistency. A hold on a reactor phase and a hold on a filtration phase both mean the same thing: the phase moves to a defined safe condition and waits. Operators learn one mental model and apply it everywhere, which reduces mistakes during upsets when clear thinking is hardest. The same four or five commands work on every phase in the plant.
The state model also gives monitoring systems a clean, universal vocabulary. Because every phase reports the same states, a SCADA or cloud monitoring platform can display the status of hundreds of phases across many units using one consistent scheme, coloring held phases one way and aborted phases another regardless of what the phase does. Aggregating status is straightforward when every element speaks the same state language.
That consistency extends to alarming and reporting. An automatic hold triggered by a deviation lands the phase in the held state just as an operator-commanded hold would, so downstream logic and dashboards treat them uniformly. When every phase transition is a defined event in a known state machine, a cloud SCADA system can log, time-stamp, and roll up batch progress reliably, turning a sprawling plant into a single readable picture of who is running, holding, or aborting right now.
A resting state is a stable condition a phase can occupy while it either does its normal work or waits for the next command, such as idle, running, held, complete, stopped, or aborted. A transient state is a temporary condition where logic is actively working to reach a resting state, such as holding, restarting, stopping, or aborting. Phases always settle into a resting state.
Effectively yes. The state model is designed so that an abort command can be issued from almost any active state and always leads to the defined aborted resting state via the aborting transition. This guarantees there is always a path to bring a phase to a safe, known condition, which is why abort and stop are treated as near-universal commands.
Because only certain transitions are defined from each state, the state machine refuses commands that have no legal transition, such as restarting a phase that is not held. Rejecting illegal commands prevents a phase from ending up in an undefined or unsafe condition and is what makes hold, restart, stop, and abort behave predictably across the whole plant.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.