A control room's wall shows the whole plant; each workstation shows only that operator's own patch

What it is

A control room's public wall display and the operators' personal workstations form a display ecology: the wall carries the plant-wide picture, the workstation carries each operator's own area of responsibility. The split is driven by what a judgment requires, not by simply projecting the same data onto a bigger screen. If the wall is just a magnified copy of a workstation view, the division of labor hasn't actually been designed.

Why it happens

Wall and workstation complement each other along two axes: who can see it, and at what resolution. The wall is visible to everyone in the room, which suits judgments that need to be confirmed jointly or that span multiple units — whether a disturbance in one unit will propagate downstream. A workstation is visible only to its operator, which suits tasks that need fine-grained readings and stepwise control, such as the exact position of one valve.

What decides where an item belongs is not "is this global information" but "can the resolution this judgment needs actually be read at wall-viewing distance." A control-room wall is typically read from several meters away, and that physical constraint filters out anything requiring precise numeric discrimination — even when the underlying quantity is genuinely plant-wide in scope, it still has to live at a workstation to be usable. Ignore this and teams cram unreadable numbers onto the wall, which degrades it into decoration nobody actually reads, while the workstation ends up missing detail it should carry instead.

The split roughly tracks Endsley's three-level model of situation awareness: the wall mainly supports Level 1 perception and Level 2 comprehension, letting everyone converge on a shared picture of what is happening and what it means; the workstation supports Level 3 projection and the concrete control action that follows, because both projection and manipulation have to land on one specific object's detailed state. Push Level 1 perception entirely onto workstations and each person assembles their own partial picture, raising the odds that understanding diverges across the team; push Level 3 projection onto the wall alone and operators can see the trend but cannot resolve it into an executable action.

Studying it

In anomaly-response exercises, record operators' gaze shifts, verbal references, and screen-to-screen transitions, coding which judgments happen at the wall, which at the workstation, and which need a round trip between the two before they resolve. The independent variable can be the allocation scheme itself — the same data placed on the wall versus at the workstation; dependent variables include how closely independent recollections of the situation agree across team members, plus individual task completion time and error rate. The unit of analysis should be the team, not a single operator: the payoff from a good allocation shows up in coordination, and single-operator reaction-time measures both understate that benefit and miss the specific failure mode of repeated round trips caused by misplaced information.

Where it stops holding

In small control rooms with no physical wall display — a small water-treatment plant, a single-operator station — this split has no physical carrier: the global picture and the personal scope have to be separated within one workstation, or one cluster of monitors, through windows, layers, or role-specific views rather than through screen position. In single-operator settings, one person carries both roles at once, and the split collapses into switching attention within the same pair of eyes; what matters there is a disciplined habit of switching views, not a physical division.

Remote or distributed operations centers often substitute a shared software dashboard for a physical wall. The principle still applies, but a software dashboard can be minimized or covered by another window, so the assumption that a wall display is "always visible" no longer holds automatically — it needs an added mechanism, such as forcing it onto a dedicated always-on screen, or the "wall" quietly stops functioning as one.

Applying it

For every category of information, answer three questions: who needs to see it, for what judgment, and whether that judgment requires several people to agree on the same object. If the answers are "an individual," "control action," and "no shared agreement needed," it belongs at the workstation. If they are "the team," "a judgment or coordination act," and "agreement is required," and the resolution it needs is legible at wall-viewing distance, it belongs on the wall.

Keep device names, state codes, and timestamp formats identical across screens; otherwise the same device can appear under different names or time bases on the wall and at the workstation, and referential language stops lining up between the two.

How to check: using recordings from past exercises or incidents, annotate, segment by segment, which screen actually carried each key judgment and whether it required a round trip between wall and workstation. If a category of judgment routinely needs more than one round trip, that category is currently placed on the wrong screen and needs reassignment.

Related

• Same group: Y1.08.2 Cross-display synchronization lag · Y1.08.3 Verifiability across shared and workstation displays · Y1.08.4 Shared visual reference in control rooms
• Nearby: Y1.01 Three levels of situation awareness · Y1.02 Overview and detail
• Search terms: situation awareness · common operating picture · display ecology · out-of-the-loop performance