An operator should be able to narrow from the whole plant down to one device in a traceable path

What it is

A hierarchical display organizes plant, area, loop, and equipment detail into a traceable drill-down path: the operator narrows from the general region where an anomaly appeared down to the specific object that can be acted on. Each level answers a question at a different scale — the overview answers "which area has deviated," the area level answers "which system," the equipment level answers "which valve or sensor exactly." A hierarchical display is not the asset database's classification tree pasted onto the screen; it is organized around the order in which a diagnosis actually narrows scope.

Why it happens

The overview level lets an operator watch many objects at once and notice which one has left its normal pattern — a low-resolution scan across many objects. The equipment level supports parameter-by-parameter diagnostic reasoning and precise control; the two need incompatible information density and cannot share one screen. Chaining them requires preserving object identity across levels: selecting an area on the overview should surface exactly the equipment inside that area on the detail screen, not force the operator to re-identify what they are looking at. The recurring failure is where the level order comes from. If the navigation tree mirrors the asset database's folder structure — site, unit, tag — that structure reflects physical ownership, not fault propagation. An operator diagnosing a fault usually does not yet know which physical module it lives in; a tree that requires picking the right module before descending effectively demands "locate first, diagnose second," the reverse of how real diagnosis proceeds — notice the anomaly first, then narrow down.

Where it stops holding

Urgent alarms should not traverse the hierarchy level by level; an alarm should deep-link straight to the relevant equipment view, because every extra level of drill-down adds directly to emergency response time — an unacceptable cost in high-consequence scenarios. Complex plants with multiple parallel trains or heavily shared equipment can have a single device belonging to different diagnostic paths depending on the task; such plants need multiple entry points rather than one strict tree. Drill-down navigation matters most to operators unfamiliar with the classification scheme; experienced operators often jump straight to a tag by typing it from memory, treating the drill-down path as a fallback rather than the only route.

Applying it

Do not export the asset database's folder structure as the navigation tree. Use real fault-handling records to reconstruct the order in which operators actually narrow scope, and define the decision information shown at each level from that order. Preserve object identity, time window, and state color continuity across levels so operators are not left re-confirming what they are looking at after a level change. Give known high-consequence alarms a deep link that skips intermediate levels. To validate, run simulated faults unfamiliar to the operators and compare a tree exported from asset classification against one reordered by diagnostic path, measuring clicks, wrong branches taken, and total time from overview to the correct equipment screen.

Related

• Same group: Y3.11.2 Direct return from deep views · Y3.11.3 Costs of excessive navigation depth · Y3.11.4 Cross-hierarchy links for coupled equipment
• Nearby: Y1.02 Overview and detail · Y4.07 Reachability and error-proofing for emergency actions
• Search terms: drill-down navigation · overview-to-detail · wayfinding cost · process control HMI