Dashboards for Operators, Engineers, and the Public
The same data serves different audiences only through different views; matching depth, framing, and controls to the reader is the design task.
One dataset, three readers
Operators, engineers, and the public look at a plant with different goals, prior knowledge, and time budgets. A single dashboard cannot serve all three well. The discipline is to derive distinct views from a shared, trustworthy data layer, each tuned to its reader.
The operator view
Operators need real-time state, margin to limits, and unambiguous alarms. Depth is shallow but latency and reliability are paramount. See Operator Dashboards. Layout is fixed to support trained response.
The engineer view
Engineers need depth: raw and derived signals, comparison across runs, access to underlying models, and freedom to explore (Interactive Exploration). Here flexibility and completeness matter more than instant glanceability.
The public view
Public views explain rather than operate. They favor clear framing, plain language, honest context, and no controls that could confuse. They must never expose sensitive detail or present modeled quantities as measurements.
- Shared data layer with a single source of truth.
- Access control so each view exposes only what is appropriate.
- Consistent definitions so numbers agree across views.
Kronos use
Kronos maintains a public build with vetted, economics-free content and a private engineering build with full detail; both draw from the same simulation and design data, with a firewall between them.