Overzicht

📊 RTT Facilities — Dashboard Mockups

Visualizing Risk, Readiness, and Governance

This document describes conceptual dashboard mockups for RTT Facilities.

These mockups illustrate how the Global Index Schema is rendered into visual interfaces for different audiences, without prescribing specific tools or visual styles.


1. Dashboard Philosophy#

RTT Facilities dashboards are:

  • Governance instruments, not monitoring toys
  • Trend‑oriented, not snapshot‑obsessed
  • Corridor‑aware, not asset‑siloed
  • Audience‑specific, not one‑size‑fits‑all

Every dashboard answers a decision question.


2. Dashboard Layers#

Facilities dashboards are organized into four layers:

  1. Global / Continental Overview
  2. City Portfolio View
  3. Corridor Drill‑Down
  4. Asset & Intervention Detail

Each layer inherits from the Global Index Schema.


3. Global / Continental Overview#

Purpose#

Provide GHQ and national leadership with macro‑level situational awareness.

Key Visual Elements#

  • World or continental map with city markers
  • Aggregate risk index per city
  • Corridor class distribution (C‑0 → C‑4)
  • Trend arrows (improving / stable / degrading)

Primary Questions Answered#

  • Where is risk concentrating globally?
  • Which regions require attention?
  • Are trends improving or worsening?

4. City Portfolio Dashboard#

Purpose#

Support City Managers and executive leadership.

Key Visual Elements#

  • City map with corridor overlays
  • Corridor class heatmap
  • System‑level risk summary (Electrical, Water, etc.)
  • Capital cycle alignment indicators
  • Audit status flags

Primary Questions Answered#

  • Which corridors matter most right now?
  • How does risk align with capital plans?
  • Are governance reviews current?

5. Corridor Drill‑Down Dashboard#

Purpose#

Support infrastructure directors and planners.

Key Visual Elements#

  • Corridor boundary visualization
  • Drift, harmonics, and propagation trend charts
  • Cross‑system dependency graph
  • Intervention history timeline
  • Upcoming review and capital milestones

Primary Questions Answered#

  • Why is this corridor classified as it is?
  • What is driving risk?
  • What actions are planned or overdue?

6. Asset & Intervention Detail View#

Purpose#

Support operators and technical staff.

Key Visual Elements#

  • Asset list within corridor
  • Condition and performance indicators
  • Maintenance vs modernization markers
  • Active or planned interventions
  • Audit notes and findings

Primary Questions Answered#

  • What work is happening here?
  • Is maintenance masking modernization need?
  • What data supports the current classification?

7. Capital & Audit Overlay#

Purpose#

Make governance state visible.

Key Visual Elements#

  • Capital cycle badges (10 / 20 / 50‑year)
  • Deferred modernization warnings
  • Audit trigger indicators
  • Follow‑up status markers

Primary Questions Answered#

  • Are decisions aligned with risk?
  • Where is deferral accumulating?
  • Are audits closing the loop?

8. Public‑Facing Dashboard Subset#

Purpose#

Support transparency without technical overload.

Key Visual Elements#

  • Simplified corridor map
  • High‑level system status
  • Planned modernization timelines
  • Plain‑language explanations

Primary Questions Answered#

  • How is the city planning ahead?
  • What improvements are coming?
  • How is reliability being protected?

9. Visual Consistency Guidelines#

Across all dashboards:

  • Corridor classes use consistent color coding
  • Trends are emphasized over raw values
  • Alerts indicate governance thresholds, not noise
  • Explanatory text accompanies metrics

Dashboards should explain themselves.


10. Relationship to the Global Index Schema#

All dashboards:

  • Read directly from the Global Index Schema
  • Do not introduce new metrics ad‑hoc
  • Reflect governance state explicitly
  • Support drill‑down without context loss

Visualization never replaces governance logic.


11. Canonical Status#

These mockups are canonical conceptual references.

All RTT Facilities dashboards should align with these patterns, regardless of implementation platform.

Updated