A plant overview design that operators read answers three questions in a few seconds: does anything need me, where is it, and is it getting worse. Show states and exceptions first, give every number its normal range, keep each area in the same place every day, and move detail one click away.
The overview is the top of the screen hierarchy that Serhat describes in his post on HMI display hierarchy. An overview goes wrong when it tries to be the detail screen as well.
What should a plant overview screen show?
It should show the state of each area and the few values that change what an operator does next. Everything else belongs on a detail page.
- Area states. One tile per line, building or unit: running, stopped or in alarm. I put states first because they read faster than numbers.
- Decision values. The handful of numbers someone acts on, such as a tank level that triggers a call or a temperature that stops a batch. Each one carries its unit and its normal range.
- Short trends. Only for values whose direction matters, so “is it getting worse” has an answer on the board itself.
I leave out monthly totals, device lists and anything that only an engineer needs. They are useful, one click away.
How many cards fit on an overview board?
As many as it takes to answer the three questions, and no more. My rule is that if the overview needs scrolling on the screen it is shown on, it is two boards.
I would rather have fewer, larger cards than many small ones, with the detail on pages behind them. Keep each area in the same place on the board, too. Operators learn where things are, so I never move a tile without telling the shift.
How do you show numbers with their normal range?
Put the range next to the number, or give the number a colour that says normal or not. A bare 4.7 means nothing to someone who did not set the limits.
Agree the ranges with the shift before you draw them, because the board makes those limits public. Which colours to use, and why most of the screen should stay grey, is in my post on the HMI colour scheme. A number also needs its age: a value that stopped updating an hour ago looks normal unless the board says so, as I wrote in dashboard last updated time.
Hermetry connects field devices to dashboards, rules and alerts: IoT telemetry and SCADA in one platform. Its dashboards have had charts, tables, maps and gauges since release 2.0, since 2.0.1 a card can open a page or run an action when it is clicked, and release 2.1.0 on 24 September reworked how you create, edit and arrange your own dashboards. That covers the overview and the click to the detail behind it; see create and organise dashboards and card actions and drill-down.
How do you test a dashboard with operators?
Sit an operator in front of the board and ask the three questions. If they cannot answer from the board alone, without clicking, the board is not finished.
Then watch what they click first and ask which card they would miss if it were gone. Cards nobody would miss come off. I repeat this after the first weeks of use, because what people look at changes once the board is part of the shift.
Frequently asked questions
Should the overview show alarms or values?
Both, but alarms and states first. An operator who sees that one area is in alarm needs to know where to go before they need the number. Put values next to the area they belong to, with their normal range, rather than in a separate block of numbers.
Should every operator see the same overview?
For the plant overview, yes. A shared starting point means two people on a shift are looking at the same picture when they talk on the phone or hand over. Personal boards are fine for the detail someone follows every day, but the overview stays one board that the whole shift agrees on.
Who should decide what goes on the overview?
The shift that uses it, with one person who owns the board. I let operators propose changes, but one owner makes them, so the board does not drift card by card. Every change gets announced at handover, because a tile that moved costs someone a few seconds at the worst moment.

