The group display is a screen with a DCS heritage that puts a handful of related control loops side by side, each drawn as a compact faceplate, for one functional part of the plant. Rather than opening one loop's faceplate at a time, the operator sees perhaps eight loops for a unit at once - their values, setpoints, modes, and outputs - and can watch and adjust them together. It is a Level 2 display in the standard hierarchy, sitting between the plant overview and the single-device detail, and it is where an operator manages a cluster of loops as a working set.
Group Display (Level 2) in one line: A group display is an HMI or DCS screen that arranges several related control loops - often around eight - as compact faceplates for one functional unit, letting an operator monitor and adjust them side by side. It is a Level 2 hierarchy element, broader than a single faceplate but narrower than a plant overview, used to manage a set of loops that operate together.
In the classic four-level display hierarchy, the group display occupies Level 2. Level 1 is the plant or area overview that shows the whole process at a glance; Level 3 is the detailed mimic of a single unit with its equipment drawn in context; a single faceplate zooms into one device or loop. The group display sits alongside the unit mimic at the middle of that structure, but it takes a different approach: instead of a schematic of pipes and vessels, it presents a row or grid of loop faceplates for loops that belong together functionally, such as all the control loops on a separator or a compression train.
Each faceplate in the group is a condensed version of the full standalone faceplate. It typically shows the loop's process variable, setpoint, and output as small bar indicators, its mode - auto, manual, or cascade - and its alarm state, along with the minimal controls to change setpoint or mode. The design is deliberately compact so that eight or so loops fit on one screen without clutter, trading the richness of a full faceplate for the ability to see many loops together. When the operator needs the full detail of one loop, they call up its complete faceplate from the group.
The grouping is functional, not arbitrary. Loops land on the same group display because they interact or because an operator works them as a unit: the loops on one heater, the loops on one dehydration train, the loops on one pump station. That grouping is what makes the display useful - the operator can see how a change to one loop ripples to its neighbors, which is exactly the situational awareness a single isolated faceplate cannot give.
The group display shines when loops interact and have to be coordinated. Cascade and ratio schemes, where one loop's output becomes another's setpoint, are far easier to supervise when both loops are visible on the same screen: the operator can watch the master and the slave respond together rather than flipping between two faceplates and holding the relationship in their head. Startups and shutdowns of a unit, when several loops are being moved between manual and auto in sequence, are similarly natural on a group display because every loop in the sequence is in view.
During steady operation the group display serves as a compact scan of a unit's health. A quick look tells the operator whether every loop is in its normal mode, whether any process variable is drifting off setpoint, and whether any loop has been left in manual when it should be automatic - a common and easily missed condition. Because the faceplates show mode and alarm state consistently, an out-of-place loop stands out from its neighbors, which makes the group display a fast way to catch the small abnormalities that never rise to an alarm.
It is worth being clear about what the group display is not. It is not the single faceplate, which gives full detail and full control for one loop; the group trades that depth for breadth. It is not the tag detail display, which exposes a point's configuration, ranges, and quality for diagnosis; the group is an operating screen, not a diagnostic one. And it is not the overview, which shows the whole plant with no loop-level control. The group display's specific value is holding a working set of interacting loops in one view so they can be operated as a set.
The group display concept translates cleanly to a SCADA world where the loops in a functional set are not in one control cabinet but spread across a site or several sites. A cloud platform such as Merobix can present the loops for one pad, skid, or facility together, drawing their live values, setpoints, and modes back from the controllers over Modbus or DNP3 and laying them out as a group so an operator sees the whole unit at once rather than clicking site by site. The grouping is by function - one compressor package, one measurement skid - regardless of which RTU each point physically lives on.
This matters most for equipment that behaves as a coordinated unit even though its instruments are distributed. A compression package with suction, discharge, and recycle control, or a treating skid with several loops, is easier to supervise remotely when its loops are grouped on one screen than when they are scattered across a generic site list. The operator gets the same coordinate-them-together benefit the plant group display gives, without being on site.
Because remote loops can be left in the wrong mode after a callout or a communications interruption, the group view also becomes a quick integrity check for a lean field team. A grouped display that flags any loop sitting in manual, or any loop whose value has gone stale, lets one operator confirm that a whole unit is running as intended in a single glance, then move on to the next unit - which is the kind of leverage distributed operations depend on.
A single faceplate shows the full detail and controls for one loop or device, while a group display lines up several loops as compact faceplates on one screen. The group trades the depth of a full faceplate for the breadth of seeing many related loops together. Operators use the group to coordinate interacting loops and open a single faceplate when they need everything about one of them.
Traditionally around eight, a figure inherited from early DCS group displays, though modern HMIs vary. The practical limit is how many compact faceplates fit legibly on one screen while remaining useful at a glance. The loops chosen for a group are grouped by function - they belong to the same unit or interact with one another.
It sits at the second level of the standard high-performance HMI display hierarchy, between the Level 1 plant overview and the Level 3 detailed unit mimic. Level 1 shows the whole process, Level 2 shows a functional unit's loops as a set, and lower levels show single-device detail. The group display gives a unit-level view without the full schematic of a Level 3 mimic.
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.