Quick Reference

Group Models
Estate & Dependencies Site, Location, Asset, AssetDependency
Critical Controls CriticalEvent, CriticalControl, ControlAsset
Verification VerificationRequirement, VerificationActivity
Assurance & Exceptions AssuranceException, CorrectiveAction, Evidence, Approval
Change & Conflicts ChangeRequest, ChangeAsset, OperationalConflict

The dashboard, read in ten seconds

  • Operations cards — 26 critical controls, 22 effective, 7 open exceptions, 8 operational changes, 2 changes with conflicts, 33 infrastructure assets.
  • Data Health lights — the alerts: 1 blocking operational conflict (red), 1 critical exception (red), 2 degraded controls, 1 failed control, 1 unverified control.
  • The Blocking operational conflicts light links straight to the OperationalConflict list, whose top row is the flagship scenario.

The flagship scenario (DC-SCENARIO-001)

The demo is built around one intersection that a critical-infrastructure person recognises instantly:

  1. On the B power path at Northgate, UPS-B02 and its battery BAT-B02 are DEGRADED — battery runtime is below the performance requirement.
  2. That is exception EX-014 (control NGDC-BATTERY_CAPACITY, severity HIGH, status ASSESSED) with an interim control: keep GEN-02 available; prohibit work that removes B-path standby generation until capacity is restored.
  3. Change CHG-021 proposes to take standby generator GEN-02 UNAVAILABLE for a quarterly service.
  4. Because B-path battery capacity is already degraded, removing GEN-02 would leave Data Hall 02 without required electrical redundancy → operational conflict OC-001: OPEN_CONTROL_EXCEPTION, CRITICAL, blocking, linking CHG-021 → GEN-02 → UPS-B02 → EX-014.
  5. CHG-021 sits in ENGINEERING_REVIEW with redundancy_impact = COMPROMISED; approval is blocked.

To walk it live: Change & Conflicts → Operational Conflicts (top row), then follow the affected asset (GEN-02), the affected control (POWER_REDUNDANCY) and the referenced exception code (EX-014). Or start from the dashboard's red Blocking operational conflicts light.

Phase 1 note: this end-state is seeded. Creating CHG-021 in the app does not yet auto-raise OC-001 — that inference is Phase 2. Demo read-only mode keeps the seeded picture intact.

Demo data codes

Code Meaning
NGDC / SWDC Sites: Northgate Data Campus (primary) / Southwater Edge (DR)
POWER-A / POWER-B The two electrical redundancy paths at NGDC
COOL-A / COOL-B The two cooling redundancy paths at NGDC
UPS-B02, BAT-B02, GEN-02, BUS-B The B-path scenario assets
EX-014 UPS-B02 battery runtime below requirement (the interim-control exception)
EX-021 GEN-W1 failed autostart — the one CRITICAL exception
CHG-021 Quarterly service GEN-02 — the flagship change
OC-001 The blocking redundancy conflict

Status vocabularies

  • Asset.operational_status — AVAILABLE, RUNNING, STANDBY, DEGRADED, MAINTENANCE, BYPASSED, ISOLATED, FAILED, UNAVAILABLE, DECOMMISSIONED
  • Asset.assurance_status — ASSURED, DEGRADED, FAILED, UNVERIFIED, NOT_APPLICABLE
  • CriticalControl.current_status — EFFECTIVE, DEGRADED, FAILED, UNVERIFIED, SUSPENDED
  • AssuranceException.status — OPEN, ASSESSED, ACCEPTED, ACTIONED, PENDING_VERIFICATION, CLOSED (open = anything but CLOSED)
  • AssuranceException.severity — LOW, MEDIUM, HIGH, CRITICAL
  • ChangeRequest.status — DRAFT, IMPACT_REVIEW, ENGINEERING_REVIEW, AWAITING_APPROVAL, APPROVED, SCHEDULED, EXECUTING, VERIFICATION, COMPLETED, REJECTED, CANCELLED
  • ChangeRequest.redundancy_impact — NONE, REDUCED, COMPROMISED, UNKNOWN
  • OperationalConflict.severity — INFO, WARNING, HIGH, CRITICAL; plus a blocking flag and status OPEN / ACKNOWLEDGED / OVERRIDDEN / RESOLVED

Rules of thumb

  • A control with no current verification activity reads as UNVERIFIED — that is a gap, not a pass.
  • An exception with interim_control_required means something must be true in the field right now (e.g. GEN-02 kept available) — that is what a change can violate.
  • A blocking conflict is the one that should stop an approval. In Phase 2 it will; in Phase 1 it is recorded and surfaced.