A multistate symbol is an HMI graphic that changes its appearance depending on the discrete value of a tag, so a single object can show whether a valve is open or closed, a pump is running or stopped, or a device is in a fault. Instead of the operator reading a number and interpreting it, the symbol itself signals the equipment's state through color, shape, or fill. It is one of the most direct ways a process graphic communicates status at a glance.
Multistate Symbol in one line: A multistate symbol is an HMI object whose appearance is driven by a discrete tag value, switching between defined looks for states such as open/closed, run/stop, or fault. It turns a raw status bit into an immediately readable indication of equipment state on the graphic, using deliberate color and shape coding so operators grasp conditions without reading numbers.
A multistate symbol is bound to a discrete tag - a value that takes one of a small set of defined states rather than a continuous range. For each possible state, the symbol has a defined appearance, and as the tag changes value the symbol switches to the matching look. A valve symbol might have one appearance for closed, another for open, and another for a fault or discrepancy condition, and it displays whichever one corresponds to the current tag value.
This is what distinguishes a multistate symbol from a symbol driven by a continuous value. A continuously animated object moves smoothly with an analog input, such as a tank fill rising with level, whereas a multistate symbol snaps between a fixed set of discrete looks tied to distinct states. The states are enumerated in advance - open, closed, traveling, fault - and each maps to exactly one appearance, so there is no ambiguity about what the symbol is showing.
The states can be more than two. A valve might have open, closed, and an intermediate or discrepancy state; a motor might have running, stopped, tripped, and unavailable. The symbol is configured so that every meaningful state of the equipment has its own clearly distinct representation, and importantly, so that unexpected or fault states are visually obvious rather than blending in with a normal condition. Getting the state-to-appearance mapping right is the core of designing a good multistate symbol.
Because a multistate symbol communicates through appearance, the choice of colors and shapes carries real operational weight. High-performance HMI practice reserves strong, saturated colors - especially red and yellow - for abnormal and alarm conditions, so a multistate symbol should not use those colors for a normal running or open state. If normal states are painted in bright alarm colors, the graphic becomes noisy and the operator loses the ability to spot a genuine abnormal state quickly.
For that reason, well-designed multistate symbols lean on muted tones and shape or fill differences to distinguish normal states from one another, and save the attention-grabbing colors for the states that actually demand attention, such as a fault or a discrepancy. Relying on shape and pattern in addition to color also matters for operators with color vision deficiency, so that the difference between states is not carried by color alone. A fault should look different in form, not just in hue.
Consistency across the display set is the other half of safe coding. If a closed valve looks one way on one screen and another way elsewhere, the operator cannot build reliable intuition. A multistate symbol should use the same appearance for the same state everywhere, and every symbol of a given equipment type should follow the same convention, so that a state an operator recognizes on one graphic reads identically on any other. This consistency is what turns state coding into instant recognition.
On a live process graphic in a SCADA, multistate symbols are what make the mimic readable at a glance. An operator scanning a screen full of valves, pumps, and equipment does not read each status separately; they take in the pattern of symbols and notice the one that looks abnormal. The multistate symbol is the mechanism that lets equipment state jump out from the graphic, which is exactly what an operator needs when scanning for developing problems.
In a cloud SCADA, the discrete tag values that drive these symbols arrive from the field over the control protocol and update the symbols in the browser, so a remote operator sees the same at-a-glance equipment status as someone in a traditional control room. A valve that goes to a discrepancy state, or a pump that trips, changes its symbol immediately, drawing the remote operator's eye to the affected item on a graphic that may represent a site hundreds of miles away.
Because the symbol's state comes straight from a discrete tag, it also ties naturally into the platform's alarms and history. A state that represents a fault can both change the symbol and raise an alarm, and the state changes are recorded in the event history, so the graphic, the alarm, and the record all agree. For remote and unmanned operation, this alignment - a clear state symbol on the graphic backed by an alarm and a logged event - is what lets an operator trust what the mimic is telling them about equipment they cannot see.
A multistate symbol snaps between a fixed set of appearances tied to discrete states, such as open, closed, or fault. A continuously animated graphic moves smoothly with an analog value, like a tank fill rising with level. The distinction is discrete versus continuous: the multistate symbol enumerates distinct states and shows exactly one look per state, rather than varying smoothly across a range.
It should reserve strong colors like red and yellow for abnormal and alarm states, and use muted tones plus shape or fill differences for normal states. Painting a normal running or open state in bright alarm colors makes the graphic noisy and hides genuine problems. Using shape as well as color also helps operators with color vision deficiency distinguish states reliably.
Consistency lets operators build reliable intuition. If a closed valve looks one way on one screen and different elsewhere, the operator cannot recognize states at a glance. When the same state always has the same appearance, and every symbol of an equipment type follows the same convention, a state recognized on one graphic reads identically on any other, turning state coding into instant recognition.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.