IMDTouchKnowledge BaseShop main store

Explainer

Designing HMI Screens for Clear Operator Decisions

HMI and touchscreens Published 6 min read

Short answer

High performance HMI design under ANSI/ISA-101.01-2015 makes abnormal conditions easier to spot than normal operation: normal running renders flat and gray, saturated color appears only on deviations, and every icon, font and color follows one documented project style. Verify the style mechanism on a single screen before scaling to the full library.

On this page
  1. The standard and what it demands
  2. The gray baseline
  3. The emphasis budget, with arithmetic
  4. Icons, labels, and navigation
  5. Typography that survives the panel
  6. Detail matched to the task
  7. One style for the whole project
  8. Questions asked

Make abnormal conditions easier to spot than normal operation. That sentence is the whole method, and it is the intent behind ANSI/ISA-101.01-2015: give healthy running a flat, gray, motionless baseline and reserve saturated color for the states that need a decision. An operator scanning a healthy overview should see nothing but grays; when one pump trips, a single red object should be the only thing on the screen worth looking at. The sections below give the palette, the emphasis budget with the arithmetic, the icon and navigation rules, the typography, and the project-wide style behavior to verify before you build a hundred screens.

The standard and what it demands #

ANSI/ISA-101.01-2015 is the standard for human-machine interfaces in process automation. In plain terms it requires a documented design process, not a mandated look: you write down what operators must detect and do, turn that into a style guide covering color, shape, font and dynamic behavior, design every display against that guide, and keep the whole set under control through the display's life — changes, training, periodic review. The standard does not publish a color table; it obliges you to define one and hold every screen to it.

Two companion references matter in practice. The ASM Consortium's HMI Design Guidelines supply the worked examples of good and bad display design, and their second edition added 28 new figures and revised 43 more. When a customer hands you their own standards document with exact RGB numbers, font type and size, those figures are the project style guide; enter the values as given, never approximated by eye. Decision: even on a small project, write one page of philosophy and two pages of style guide before the first graphic.

The gray baseline #

Normal running earns no color at all: flat light-gray background, equipment line work and fills in grays, no animation on anything healthy. Gradients are out for two concrete reasons: a shaded background reads like a viewing-angle fault on an LCD panel, and a button sitting on a gradient shows different apparent contrast depending on where it sits. Flat fills only, everywhere.

Adopt this palette as the default when no customer standard exists, and replace it wholesale — never mix palettes across screens:

State Example color RGB Meaning
Background Light gray 210, 210, 210 Canvas; carries no meaning
Running Mid gray 160, 160, 160 Equipment operating as expected
Stopped or standby Outline gray 120, 120, 120 Available but not running
Alarm, abnormal Red 255, 0, 0 Needs operator action now
Warning Yellow 255, 200, 0 Deviating; action soon
Maintenance, bypass Blue 0, 112, 192 Out of normal service until restored

Red never means "valve closed" or "motor stopped" — a closed valve is a normal state and gets gray. Color is a statement about the process, not a picture of it. One limit the palette cannot cross: screen indication is not a safety function. Emergency stops and interlocks stay in hardwired, rated circuits; the HMI shows their status, it does not perform it, and a blue bypass must correspond line-for-line with what is actually bypassed in the controller until it is cleared.

The emphasis budget, with arithmetic #

Color is a budget, and you can count it. Take a legacy overview with 140 dynamic objects — motors, valves, setpoints, indicators — where normal running lights 95 of them in saturated green, red and blue:

95 ÷ 140 = 0.68, so 68% of the screen is shouting while the plant is healthy.

Redesign the same screen on the gray baseline and normal running shows zero colored objects. One pump trips with an unacknowledged alarm and its discharge valve goes red — two colored objects:

2 ÷ 140 = 0.014, about 1.4% of the screen.

That contrast is the entire effect. Working limit: on any single screen, at most one object in ten carries saturated color or motion at the same time — 140 × 0.10 = 14 objects — and a healthy plant shows zero. If a normal state needs color to be understood, the graphic is wrong, not the palette.

Icons, labels, and navigation #

Test every icon the way an operator meets it: cold, without tooltips. If a reviewer cannot name the function unaided, the icon gets a short text label — icon plus the fewest words that name the function. Glossy, three-dimensional symbols fail this test routinely; a rendered meter or information glyph reads as decoration with several plausible meanings. Distinguish navigation from commands with consistent placement and shape, so a touch that changes the page never looks like a touch that starts a motor.

Navigation runs three levels deep at most: plant overview, unit, then detail or faceplate. The way back sits in the same corner on every page. Menus that wrap around screen edges hide where you are; a second-level menu that opens from the selected category keeps the hierarchy visible. Decision: three levels, one fixed back button, no edge-wrapped menus.

Typography that survives the panel #

One sans-serif family, three sizes: labels smallest, process values larger, alarm text largest. As a starting point, 14 pt labels and 18 pt values hold up on a 15-inch 1024 × 768 panel read at about one meter — then verify on the installed panel at the real viewing distance before scaling the library, because the engineering tool's rendering is not the runtime's. Fonts that fit on the development PC can overflow on the panel once the runtime substitutes its own: HMI text runs off the screen after downloading the project covers that failure and its fix.

Detail matched to the task #

Minimalism is not the goal; matching detail to the task is. The overview carries a dozen conditions and no loop detail. The unit level adds the process values an operator diagnoses with. The detail or faceplate level carries everything that task needs. Run one sequence per screen: name the operating task, list the information that task needs, delete everything that supports neither recognition, diagnosis nor action. Then print the screen static — if an operator cannot tell normal from abnormal on the paper, fix the hierarchy before adding any dynamics.

When a redesign rides on new hardware, apply the palette and hierarchy to fresh layouts rather than porting the old graphics across: planning an HMI terminal replacement from an older operator panel walks that decision path.

One style for the whole project #

Before building a large library, find out how your platform manages color and font centrally. Many HMI tools keep a project style or theme, and a change to the theme propagates only to objects that reference the style — a locally overridden alarm red stays put. Prove the mechanism on one representative screen: change the theme's red, download, and confirm every alarm object follows; anything that does not is a local override to clean up. If the platform has no theme engine, a program-side color variable works, but it becomes custom code you must test and maintain. Vendor demo projects usually show the intended style mechanism in practice, and learning advanced HMI features from demo projects shows how to mine them.

Questions asked

How do operators react to gray screens after years of colorful graphics?

Expect pushback for the first few weeks. Operators used to bright green run lights read the flat baseline as dead until they learn that color now means action. Run the old and new overviews side by side during the changeover, then induce one test alarm on the new screen: a single red object on gray usually settles the argument faster than any memo.

Does ISA-101 tell me which colors to use?

No. ANSI/ISA-101.01-2015 specifies the design process — philosophy, style guide, display design and lifecycle control — and obliges you to define and enforce a palette. The ASM Consortium guidelines supply practical color and layout examples. If a customer issues exact RGB values and font specifications, those numbers become the project style guide and override any internal baseline.

How many colors belong on a high performance HMI?

A working ceiling is six: three grays for the normal baseline (background, running, stopped) plus red for alarms, yellow for warnings and blue for maintenance or bypass. Every color carries exactly one meaning, and every meaning maps to exactly one color across all displays. Anything beyond six needs a documented reason.

When is flashing or animation acceptable?

Flash only an unacknowledged high-priority alarm, and stop the flashing the moment the operator acknowledges it, leaving steady red. Nothing in normal operation animates: no rotating pumps, no flowing pipes, no blinking confirmations. Motion on a healthy screen trains operators to ignore motion, which is exactly the reflex you cannot afford when something is wrong.

Can I migrate existing screens to this style one at a time?

Yes, and staged migration is the usual path. Convert the overview and the alarm and bypass colors first, because those carry the decisions that matter, then migrate unit screens as you touch them. Never leave both palettes on one screen; a half-converted screen is harder to read than either style alone.

Keep reading

  • Explainer

    Selecting and starting a DX200 robot job from an HMI

    A DX200 selects a job for an HMI only through its documented Job Select command, 0x87, covering tasks 0 through 15 on the high-speed Ethernet server function; if the installed driver does not expose that service, a robot-side job must interpret the request. Gate every start request on reading back the accepted job, because selection and execution are separate controller conditions.

    HMI and touchscreens

  • Troubleshooting

    HMI Text Runs Off the Screen After Downloading the Project

    The panel and the project are both fine: the engineering PC's Windows display scaling is above 100%, so the downloaded layout lands past the panel edge even though the editor and offline simulation look correct. Set the scale to 100%, restart the PC, then redownload.

    HMI and touchscreens

  • Troubleshooting

    Fixing Goto Display Buttons Locked by HMI Global Connections

    While the Global Connections remote display number is active — its DINT tag still holding 21 — FactoryTalk View ME disables every other form of navigation, so Goto Display buttons stay dead whether or not the popup is visible. Write 21 with a one-shot on bit A and let a startup macro on display 21 reset the tag to 0; the popup stays up and the buttons respond.

    HMI and touchscreens