A well-designed HMI is not a flat pile of screens the operator hunts through - it is a structured hierarchy that mirrors how an operator's attention should move, from a broad view of the whole facility down to a single control loop. This guide explains the four-level HMI display hierarchy, what each level is for, and how an operator drills down from a plant overview to the detail behind a developing problem.
Display Hierarchy (Levels 1-4) in one line: An HMI display hierarchy is a structured, four-level organization of operator screens that supports drilling down from the broadest view to the finest detail. Level 1 is a facility or area overview for at-a-glance monitoring, Level 2 is the process control screens an operator works from most, Level 3 is detailed process and equipment displays, and Level 4 is diagnostic and support information. The hierarchy lets an operator start wide, spot where attention is needed, and navigate progressively deeper to act on it.
Level 1 is the process overview: a single, high-level screen showing the health of an entire facility or area at a glance, built around KPIs, trends, and status so an operator can monitor overall condition and spot a developing problem before it alarms. It carries few controls; its job is awareness, not action. Level 2 is the main process control level - the working screens, typically one per major unit or area, where the operator spends most of their time and from which they actually run the process, opening faceplates and adjusting setpoints. Most routine operation happens at Level 2.
Level 3 is process detail: focused displays for a single piece of equipment, sub-system, or a group of related loops, giving the fine-grained information an operator needs when working closely with one part of the plant during a specific task or problem. Level 4 is diagnostic and support - the deepest layer, holding equipment diagnostics, help documents, procedures, instrument detail, and troubleshooting information that an operator or technician consults occasionally rather than continuously. The numbering reflects depth and frequency of use: lower numbers are broader and watched more often, higher numbers are narrower and consulted on demand.
The power of the hierarchy is the path it creates. An operator begins at the Level 1 overview and notices that one area indicator has shifted from gray toward amber. Rather than searching a menu, they click straight into that area's Level 2 control screen, where they see the specific unit involved and its live values in the context of the process. Seeing the separator level climbing, they drill to the Level 3 detail for that separator or open the level-control loop, and if the controller itself looks suspect they can reach Level 4 diagnostics for the instrument or valve behind it.
That progressive narrowing matters because it matches how situational awareness is built - perceive broadly, comprehend the situation, then act on the specific cause. A flat display structure forces the operator to already know which screen to open, which fails exactly when they are under pressure and unsure what is wrong. A proper hierarchy lets the overview point them toward the problem area and each level hand them off to the next, so navigation itself guides the diagnosis rather than getting in its way. Consistent navigation controls at every level keep the drill-down predictable.
In oil and gas, the operator's world is rarely one plant - it is a field of scattered wells, pads, batteries, and pipeline segments, which makes a good hierarchy more important, not less. A Level 1 overview that summarizes the whole field lets a single operator watch many remote sites at once, and drilling into a Level 2 area screen and then a Level 3 site or well display is how they reach the detail of the one location that needs attention among dozens that are fine.
A cloud SCADA such as Merobix is well suited to this structure because it reads tags from many geographically separated sites over Modbus, DNP3, OPC UA, and MQTT and presents them in one browser environment. Building screens as a deliberate hierarchy - a field overview at Level 1, area and site screens beneath it, and equipment detail below that - turns a large distributed operation into something one operator can actually navigate. The hierarchy is what keeps remote monitoring at scale from becoming an unmanageable flat list of hundreds of individual site screens.
Level 1 is the process overview for at-a-glance facility or area monitoring; Level 2 is the main process control screens where operators do most of their work; Level 3 is detailed displays for a single piece of equipment or a group of loops; and Level 4 is diagnostic and support information consulted on demand. Lower numbers are broader and watched more often; higher numbers are narrower and used occasionally.
A hierarchy matches how an operator's attention should move - from a broad overview, to the affected area, to the specific cause. It lets the overview point the operator toward a developing problem and each level hand off to the next, which is far more effective under pressure than a flat structure that assumes the operator already knows which screen to open.
The alarm summary is a specialized display that works alongside the hierarchy rather than sitting neatly at one level. Operators use it together with the Level 1 overview to see what is abnormal, and a good alarm summary lets them jump directly from an alarm row to the relevant Level 2 or Level 3 screen for that tag, connecting the alarm to the place where they can act on it.
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.