Between the wide overview that shows the whole plant and the deep detail screens that dissect one device sits the screen an operator actually spends the shift on. The primary control display, often called the level 2 or working display, is the graphic an operator drives a unit from, combining the process picture with the controls, trends, and alarm context needed to run that unit normally. It is where routine operation happens, so its design shapes how well the operator can keep the unit steady. This guide explains what a primary control display contains, where it sits in the hierarchy, and how it works in remote cloud operation.
Primary Control Display in one line: A primary control display is the main working screen an operator uses to run a process unit day to day, sitting at level 2 of the display hierarchy between the plant overview and the detailed device screens. It shows the unit's process graphic with the controls, key values, trends, and alarm context an operator needs for normal operation, so most routine work is done from this one screen without drilling deeper.
A primary control display is built around one process unit and is meant to be the screen the operator lives on while running it. It shows the unit as a process graphic - the vessels, the flows, the key equipment - overlaid with the live values that matter and the controls the operator reaches for regularly, such as setpoints and mode changes for the main loops. The idea is that everything needed to keep the unit operating normally is present on this one screen, so the operator is not constantly diving into detail displays to make routine adjustments.
Because it is a working screen, its content is chosen for the job of operating, not for completeness. It carries the values an operator watches to know the unit is healthy, the controls they use most, and enough alarm context to know what is wrong within the unit, but it deliberately leaves the exhaustive diagnostics and tuning parameters to the detail screens beneath it. Getting that selection right is the core of designing a good primary display: put what the operator needs for normal running in front of them and push the rest one level down.
Embedded trends and alarm indicators give the display its situational depth. A small trend of a key variable on the graphic lets the operator see not just the current value but where it is heading, which is often what tells them to act before an alarm ever fires. Alarm indication on the display shows which parts of the unit are in trouble, so the operator can respond from the same screen they are already watching. Together these make the primary control display a self-contained cockpit for the unit rather than a static picture.
The primary control display occupies the middle of a layered hierarchy, and its role is defined by what sits above and below it. Above is the overview, a wide screen showing the whole plant or area at a glance so the operator can spot where attention is needed. Below are the detail displays, which open up a single loop or device for troubleshooting, tuning, and deep diagnostics. The primary display is the level the operator navigates to from the overview to actually run a chosen unit, and the level they drill down from when a specific problem needs closer inspection.
This middle position is what makes the primary display the hub of everyday navigation. In normal operation an operator moves between the overview and the primary displays of the units they are responsible for, dropping into detail only when something specific demands it. Because so much time is spent here, the primary displays are the screens most worth designing carefully, since small improvements in how quickly an operator can read and act on them pay off across the whole shift.
Defining the boundaries between the levels keeps each display doing its own job. If a primary display tries to carry every detail, it becomes cluttered and slow to read; if it carries too little, the operator is forced to drill down for routine tasks. The discipline is to keep the primary display focused on normal operation of the unit, letting the overview handle breadth and the detail screens handle depth, so each level stays clean and the operator always knows which screen to be on for what they are trying to do.
The primary control display keeps its central role in cloud SCADA, but the population of units it represents can be far larger and more scattered. On a platform such as Merobix an operator may run many remote sites, each with its own working screen, and the primary display for a given site is where they go to operate that facility normally - reading its key values, adjusting its main setpoints, and watching its embedded trends - just as a plant operator works a unit from its screen. The pattern is the same; the reach is wider.
Remote operation raises the importance of the primary display carrying enough context to act with confidence, because the operator cannot see the site. Where a plant operator can glance out at the equipment, a remote operator relies entirely on what the working screen shows, so the primary display has to present the values, trends, and alarm state that let them judge the unit's health without being there. That makes the selection of what appears on this screen even more consequential than it is in a control room next to the process.
Because remote operators reach these screens through a browser on varied devices, the primary control display has to stay usable from a console, a tablet, or a phone. The layout has to keep the essential values and the most-used controls readable and reachable when the screen shrinks, so an operator responding to a site during a callout can still run it from the working screen rather than being forced into fiddly detail displays. A primary display that degrades gracefully across devices is what keeps a distributed operation controllable from wherever the operator happens to be.
An overview display is a wide, high-level screen that shows a whole plant or area at a glance so the operator can spot where attention is needed. A primary control display focuses on one unit and carries the controls, values, and trends the operator uses to actually run it. The overview is for awareness across the plant; the primary display is where the operator does the day-to-day work of operating a specific unit.
Level numbering comes from the layered display hierarchy used in high-performance HMI design, where level 1 is typically the plant or area overview, level 2 is the primary working display for a unit, and lower levels hold the detailed device and diagnostic screens. Calling it level 2 places it in the middle of that structure, above the overview and below the detail screens, which is exactly where the operator does normal operation.
Yes, that is a defining feature of it. The primary control display is meant to be the screen the operator runs the unit from, so it embeds the controls used in normal operation, such as the main setpoints and mode changes, rather than forcing the operator to drill into a detail screen for every routine adjustment. Deeper or less frequent controls and tuning parameters are what get pushed down to the detail level.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.