The ISA-101 HMI Lifecycle Stages, in Order
ISA-101 is best known for gray-scale high-performance screens, but its deeper contribution is treating HMIs as something with a lifecycle rather than a one-time build. This page walks that lifecycle stage by stage, as a sequence of deliverables, so you can see what each phase produces and hands to the next. It is written for the engineer or HMI owner who needs to run a display program properly, not just make one screen look modern.
ISA-101 HMI lifecycle in one line: The ISA-101 HMI lifecycle runs in three broad phases that break into stages: system standards come first, setting the philosophy and style guide; then design and implementation, where displays are designed to the hierarchy and built; then operation and maintenance, where the HMI is used and kept current through managed change. Like the alarm lifecycle it parallels, it is a loop: operational experience feeds back into revised standards and redesigned displays.
System Standards: Philosophy and Style Guide First
The lifecycle opens by establishing the rules before any screen is drawn. This means an HMI philosophy that states the goals and principles, and a style guide that fixes the concrete conventions: the color use, the display hierarchy, the standard elements, and how abnormal conditions are shown. Getting these down first is what makes every later display consistent, because designers build to the same rulebook rather than to personal taste. The HMI style guide is the deliverable that carries those conventions.
The philosophy also fixes the high-performance approach that ISA-101 is known for: a restrained visual language where normal operation is quiet and abnormal conditions stand out. Deciding this at the standards stage, rather than screen by screen, is what prevents the drift back toward colorful, cluttered graphics. The grayscale high-performance HMI background is one of the concrete conventions this stage locks in for everything downstream.
Design and Implementation: Build to the Hierarchy
With the standards set, design lays out the actual displays according to the display hierarchy, from high-level overviews down to detailed views. Each level in the hierarchy has a job: an overview screen for at-a-glance situation awareness, and progressively more detailed screens for diagnosis and control. Designing to the hierarchy means every screen has a defined role and a defined place, so operators always know where to look. The ISA-101 display levels define that hierarchy.
Implementation then builds the designed displays in the actual HMI or SCADA system, faithfully to the design and the style guide. This is where the abstract layout becomes a working screen, and where fidelity to the standards matters, because a build that quietly departs from the style guide undoes the consistency the earlier stages bought. Reviewing built screens against the design and the guide before they go live is the check that keeps implementation honest.
Operation and Maintenance: Use and Managed Change
Once displays are live, the operation stage is where they earn their keep, and where the design is tested against real upsets. Operational experience reveals which screens work under pressure and which do not, and that feedback is the raw material for improvement. A display that looked clear in review but buries a key value during an upset is exactly the kind of finding operation surfaces, and capturing it is part of running the lifecycle rather than just running the screens.
Maintenance keeps the HMI current as the process and the standards evolve, and it must be governed by managed change so edits are reviewed rather than slipped in. Unmanaged HMI changes are how a disciplined display set drifts back into inconsistency over years. The feedback loop closes here: operational findings and process changes drive revisions to the standards and redesign of displays, which is what makes ISA-101 a lifecycle rather than a project, much as the alarm lifecycle loops through its own audit stage.
Frequently Asked Questions
What comes first in the ISA-101 HMI lifecycle?
The system standards: an HMI philosophy that states the goals and a style guide that fixes the concrete conventions for color, hierarchy, standard elements, and how abnormal conditions are shown. Setting these before any screen is drawn is what makes every later display consistent, because designers build to a shared rulebook rather than to individual preference.
Is the ISA-101 lifecycle a one-time process?
No, it is a loop. After displays are designed, built, and put into operation, operational experience and process changes feed back into revised standards and redesigned displays, all under managed change. Treating it as a lifecycle rather than a one-time build is what keeps a display set from drifting back into inconsistency over the years it is in service.
How does the display hierarchy fit the lifecycle?
It is applied in the design stage. Displays are laid out according to the hierarchy, from high-level overviews for situation awareness down to detailed screens for diagnosis and control, so each screen has a defined role and place. The hierarchy is defined in the system-standards stage and realized when displays are designed and built to it.
Sources and verification
This page references the vendor products and their official documentation published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
- Rockwell Automation Literature Library (Allen-Bradley, Studio 5000) - Rockwell Automation
- Siemens SIMATIC and TIA Portal documentation - Siemens
Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.