Outage & Constraint Coordination
Coordinate generator outages against network constraints — an outage request through impact assessment, constraint handling, approval, notification, execution checkpoints and restoration, with the coordination exceptions that arise when an outage clashes with a constraint.
Its central question:
For each outage, is its impact assessed against network constraints, approved by the right authority, notified to affected parties, executed through its checkpoints and restored — with any clash raised as a coordination exception?
This is one component of the Renewable Generation Orchestration reference suite.
The spine
Outage Request → Impact Assessment → (Constraints, Approvals, Notifications) → Execution Checkpoints → Restoration, with Coordination Exceptions
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 outage workflow (requested → assessed → approved → executing → restored), impact/constraint clash detection (an outage window overlapping an active constraint → a coordination exception), approval gating and notification acknowledgement tracking, and the published outage events — see page 03.
Prototype system; draft. All facilities, people and records in the demo data are fictional.