Operational Exception Manager
Manage operational exceptions raised across the generation estate — a single exception through triage, assignment, decision, action, escalation and closure, with links to the events that caused or relate to it.
Its central question:
For each operational exception, is it triaged to the right severity and owner, decided and actioned within its response window, escalated when it slips, and closed only on a reviewed resolution?
This is one component of the Renewable Generation Orchestration reference suite.
The spine
Operational Exception → Triage → Assignment → Decision → Action → Escalation → Closure Review, with Related Events
The documents
| Page | What's in it |
|---|---|
| 00 — Overview | What the app is, the domain, the 8 models, the demo scenario |
| 01 — Quick Reference | Menu map, every model, key status vocabularies, the demo data set |
| 02 — System Diagram | The data model as a diagram (+ interactive viewer) |
| 03 — Phase 2 Scope | The runtime not yet built: workflow, governance, events |
Status
Phase 1 (built): all 8 models render as an AI-Safe CRUD register with a dashboard, seeded with one coherent scenario (8 rows).
Phase 2 (scoped, not built): the exception lifecycle/state machine (open → triaged → assigned → in_progress → closed), SLA timers on response_due_at, automatic escalation when a response window is breached, closure gating (evidence complete + review) and the published exception events — this is the estate-wide exception hub the other apps route into — see page 03.
Prototype system; draft. All facilities, people and records in the demo data are fictional.