A modern process plant has hundreds or thousands of measurements, and an operator cannot look at them all on one screen. The graphics hierarchy is how a DCS organises its displays into layers so operators can move from a broad view of the whole plant down to the detail of a single device in a controlled, predictable way. The ISA-101 standard describes this as a four-level structure. This guide explains what each level shows, how operators navigate between them, and how the hierarchy differs from the individual process graphics and faceplates it is built from.
DCS graphics hierarchy in one line: A DCS graphics hierarchy is the layered structure of operator displays, usually described in four levels by the ISA-101 standard: a plant or process overview, unit or area displays, detailed control displays, and diagnostic or support displays. The hierarchy defines how an operator drills from a wide situational view down to the detail of a specific piece of equipment, giving navigation a consistent shape rather than a flat pile of unrelated screens.
The ISA-101 standard on human-machine interfaces frames operator displays as a hierarchy of levels, each with a distinct purpose and a different altitude over the process. Level 1 is the plant or process overview, a wide situational display that shows the health of the whole operation on a single screen using a small number of key indicators, so the operator can tell at a glance whether the plant is normal or whether something needs attention somewhere. It is not for making adjustments; it is for keeping the big picture and deciding where to look next.
Level 2 is the unit or area display, which shows one process unit in enough detail to run it, with the main equipment, streams, and controls for that part of the plant. This is where an operator spends much of a normal shift, watching and adjusting a manageable section. Level 3 is the detail display, which focuses tightly on a single subsystem or piece of equipment, exposing the values, loops, and interlocks needed to work on it closely, such as during a start-up or a problem. Each level down narrows the scope and increases the detail.
Level 4 covers diagnostic and support displays: the screens an operator or technician calls up to troubleshoot, such as detailed device diagnostics, help, procedures, or trends supporting an investigation. These are not part of routine watch-keeping but are reached when the levels above have shown that something is wrong and a closer, more technical look is required. Together the four levels give a consistent ladder from the widest view to the deepest, so an operator always knows roughly where a given kind of information lives.
The point of arranging displays into levels is that navigation becomes a drill-down rather than a hunt. An operator starts at the overview, notices something on a particular unit, moves to that unit's Level 2 display, and if needed drills into a Level 3 detail display for the specific equipment involved. Because the hierarchy is consistent, the operator learns the path once and applies it everywhere, which matters most during an abnormal situation when time is short and stress is high and there is no room to search for the right screen.
Well-designed navigation supports this by making the relationships between levels explicit. From the overview, an operator can jump directly to the area that looks abnormal; from an area display, links lead to the detail displays for the equipment on it; and there is always a clear way back up. The hierarchy is not just a filing scheme for screens but a designed set of routes, so that moving toward a problem is fast and moving away from it to regain the big picture is equally fast. This is a core reason ISA-101 treats navigation as part of the display design, not an afterthought.
The layering also reflects how attention should flow. High-performance HMI practice, of which the ISA-101 hierarchy is a part, keeps the overview calm and information-dense so the operator can hold situational awareness, and reserves detail and colour for the levels where action happens. An operator who lives mostly at the overview and unit levels, dropping into detail only when needed, keeps a clearer picture than one who works from a flat set of busy screens. The hierarchy is what makes that disciplined way of working possible.
It helps to separate the hierarchy from the pieces it is made of. A process graphic is an individual screen depicting part of the plant with its equipment, pipes, and values. A faceplate is the small pop-up panel that lets an operator interact with a single control loop or device, showing its mode, setpoint, and output. The graphics hierarchy is neither of those; it is the organising structure that decides which graphics belong at which level and how they connect, and faceplates are called up from within graphics at any level. The hierarchy is the map; graphics and faceplates are the places on it.
Understanding that distinction avoids a common confusion. Building good individual graphics and good faceplates is necessary but not sufficient, because a set of excellent screens with no coherent hierarchy still leaves operators lost. Conversely, a clear four-level hierarchy is what gives each graphic a role: this one is an overview, that one runs a unit, this other one is for troubleshooting a pump. The hierarchy assigns purpose, and the graphics fulfil it. Both layers of design have to be right for operators to navigate well.
The same structuring principle carries into cloud SCADA for distributed operations. A platform such as Merobix that monitors many remote sites benefits from an equivalent layering: a fleet overview showing the health of every site at a glance, site-level displays for working a particular location, and detail views for a specific wellhead, tank, or compressor. An operator watching a hundred remote sites needs the same disciplined drill-down that an ISA-101 hierarchy gives a plant operator, moving from the wide picture to the abnormal site to the equipment causing it. The four-level thinking translates directly, whether the process is one plant or a spread of unmanned sites viewed from a screen far away.
Level 1 is a plant or process overview giving whole-operation situational awareness; Level 2 is a unit or area display detailed enough to run one section; Level 3 is a detail display focused on a single subsystem or piece of equipment; and Level 4 covers diagnostic and support displays used for troubleshooting. Each level narrows scope and adds detail as the operator drills down.
A process graphic is a single screen showing part of the plant, while the graphics hierarchy is the organising structure that decides which graphics belong at which level and how operators move between them. The hierarchy is the map and the individual graphics are the places on it. You need both: good graphics with no hierarchy leave operators lost, and a hierarchy needs graphics to fill each level.
A hierarchy turns navigation into a predictable drill-down instead of a search, which matters most during abnormal situations when operators are under pressure. Starting from an overview, an operator moves to the area that looks wrong, then into the detail for the specific equipment, with a clear route back up to regain the big picture. Consistency means the operator learns the path once and applies it everywhere.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.