A screen layout should mirror the physical plant's spatial relationships, not just its logical grouping
Aliases: spatial compatibility of display and plant · control-room interface
What it is
Spatial compatibility requires that the relative position, connectivity, and orientation of equipment on a display map predictably onto the operator's spatial understanding of the physical plant or legacy panel, rather than being laid out arbitrarily and patched up with a legend. The idea traces back to the mimic diagram: plant piping, valves, and units drawn in their actual site layout so an operator can map a screen location straight back to a physical location. Once displays went digital, layout was no longer constrained by real pipework, so compatibility became an active design decision rather than a byproduct of drafting.
Why it happens
Compatibility works not because a realistic layout looks better, but because operators who have walked the plant, trained on it, or used the same panel for years encode equipment relationships as directly callable procedural memory: seeing a region tells them which pump lives there, with no need to read every label. This is recognition-primed decision making — pattern matching produces a candidate object directly, instead of a deliberate search. Mirror, rotate, or reverse the orientation of that layout across a workstation, and the memory no longer fires a direct match; the operator must first perform a mental rotation back to the familiar orientation before matching succeeds. That transformation costs time that scales with rotation angle, and error rates climb with it — under pressure the rotation step is often skipped, and the operator acts on the remembered position, selecting the mirrored object instead. A stable topology is valuable precisely because it removes that transformation cost entirely.
Where it stops holding
This does not mean every screen must replicate the plant literally. Different viewing directions produce genuinely different "correct" layouts on their own — a ground operator and a crane or elevated-vantage operator hold opposite spatial expectations for the same equipment, so one display cannot satisfy both and still count as compatible. Handheld devices rotate with the hand, so there is no fixed orientation to align against. Purely software functions — reports, trends, permissions — have no physical referent, so "spatial consistency" is not a meaningful question for them. Watch the opposite failure too: chasing photorealism (3-D piping, perspective rendering) can bury the causal flow the operator actually needs; industrial mimic diagrams have long favored abstract symbols over realistic rendering because a task-inferable topology matters more than visual likeness. Compatibility here means task-predictable mapping, not pictorial realism.
Applying it
Start by identifying the operator's primary viewing angle and the most common task paths, rather than assuming a single "correct" viewpoint; preserve equipment identity, adjacency, flow direction, and critical orientation, and explicitly flag viewpoint differences across workstations and screens instead of expecting operators to mentally rotate on their own. When migrating or restyling a system, put the old and new layouts side by side in front of incumbent operators and ask "where is this device" before asking "does this look better." How to check: have operators familiar with the legacy layout perform localization tasks on the new display, recording whether the first selection is correct and how long it takes; build a separate mirrored or displaced control set and measure error rate under time pressure — if the mirrored layout produces markedly more errors than the correct one, the layout is relying on memory-matching rather than label-reading, and the compatibility benefit is real.