For decades, how a plant's operator screens looked was left to whoever happened to build them, and it showed - inconsistent, cluttered displays that varied from unit to unit. ISA-101 is the standard that brought discipline to HMI design, the same way ISA-18.2 did for alarms and ISA-95 did for enterprise integration. This guide explains what ISA-101.01 covers, the HMI lifecycle it defines, and why it is treated as the governing reference for how operator displays should be built and maintained.
ISA-101 Standard in one line: ISA-101, formally ISA-101.01, is the standard for human-machine interfaces in process automation. It defines how HMIs should be designed, built, and managed across their full lifecycle - covering the system standards an organization sets, the HMI style guide that fixes conventions, and the ongoing phases of design, implementation, operation, and maintenance. Rather than dictate one look, it provides a framework and requires an organization to define and consistently apply its own display conventions.
ISA-101 addresses the philosophy, design, implementation, operation, and maintenance of HMIs used to monitor and control industrial processes. Its central premise is that operator displays are a safety-relevant part of the control system and therefore deserve the same structured management as any other engineered element, not ad-hoc creation by individual integrators. It draws heavily on the principles of high-performance HMI - clarity, consistency, and reserving salience for what matters - but frames them as requirements to be documented and enforced rather than optional good practice.
Importantly, ISA-101 is a framework rather than a rigid template. It does not prescribe an exact color for a running pump or a fixed layout for every screen. Instead it requires an organization to establish its own conventions, capture them in a style guide, and then apply them uniformly. This lets the standard fit different industries and control systems while still delivering the consistency that operators depend on. The intent is that any operator moving between screens, or between plants within a company, encounters the same visual language.
ISA-101 organizes HMI work as a lifecycle rather than a one-time project. It begins with system standards and a philosophy that set high-level rules and objectives, followed by an HMI style guide that turns those rules into concrete conventions - the specific fonts, colors, indicator shapes, faceplate templates, and navigation patterns every screen must use. With the style guide in place, the design phase specifies what displays are needed and what each must show, and the implementation phase builds them to the style guide so consistency is guaranteed rather than hoped for.
The lifecycle does not end at go-live. The operation phase covers how displays are actually used and monitored in service, and the maintenance phase governs how they are updated as the process, instrumentation, or operating experience changes. Crucially, changes flow back through management of change so that a screen edited years after commissioning still obeys the same conventions. This closed loop is what keeps an HMI from drifting back into the inconsistent, cluttered state that ISA-101 exists to prevent - the standard treats the display estate as a living system to be governed, not a deliverable to be finished.
ISA-101 was written to be system-agnostic, so its lifecycle applies just as well to a browser-delivered SCADA as to a traditional panel-mounted DCS. A cloud platform actually makes several lifecycle stages easier: a style guide can be enforced through a shared library of display objects, screens are built and versioned centrally, and an update propagates to every operator at once rather than being applied inconsistently across many workstations. That central control is exactly what the maintenance phase asks for.
For an oil and gas operator running a cloud SCADA such as Merobix, following ISA-101 principles means the well-pad, separator, tank-battery, and pipeline screens all share one visual language, so a control-room operator or a field technician on a tablet reads any of them the same way. Merobix renders live tags read over Modbus, DNP3, OPC UA, and MQTT into browser graphics, and building those graphics against a documented style guide is what turns a collection of screens into a coherent, standard-conforming HMI that stays consistent as the field grows and changes.
It standardizes the process of designing and managing HMIs, not a single fixed appearance. ISA-101 requires an organization to establish its own display philosophy and conventions, capture them in a style guide, and then apply them consistently through design, implementation, operation, and maintenance. The goal is a coherent, well-governed set of operator displays.
High-performance HMI is the design philosophy - muted graphics, reserved color, analog indicators - and ISA-101 is the standard that puts a lifecycle and governance framework around applying it. In practice, organizations adopt high-performance principles and use ISA-101 to document those principles in a style guide and enforce them consistently over time.
ISA-101 is a consensus industry standard rather than a law, so it is not universally mandated. However, many operating companies adopt it as internal policy because consistent, well-designed HMIs reduce operator error and support safe operation. It sits alongside related standards such as ISA-18.2 for alarms as part of a broader control-room and safety framework.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.