Overview

What this is

Outage & Constraint Coordination (outage) — 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. It is built from one component of the Renewable Generation Orchestration reference pack.

The domain, in one paragraph

An OutageRequest (facility, equipment, window, expected capacity reduction) gets an OutageImpactAssessment (generation/network/market/compliance/commissioning/safety impact). Network Constraints (thermal, voltage…) may bound it; an Approval authorises it, Notifications advise affected parties (AEMO, NSP). Execution runs through ExecutionCheckpoints (isolation confirmed, etc.) and ends in a Restoration (equipment returned, capacity restored). A CoordinationException captures a clash between an outage and a constraint.

The 8 models

Requests & Impact

OutageRequest · OutageImpactAssessment · ExecutionCheckpoint · Restoration

Constraints & Approvals

Constraint · Approval · Notification

Exceptions

CoordinationException

The demo scenario

A planned inverter-block maintenance outage OUT-2026-0031 on the Northgate Solar Farm (INV-3, 60 MW reduction, 06:00–16:00, approved). Impact assessment OIA-0031 (60 MW, within N-1). A network thermal constraint CON-THERMAL-14 caps export during peak ambient; the outage window overlaps it, raising coordination exception CEX-0031 (medium, cleared by a combined export cap). Approval APP-0031 (NSP), an AEMO notification (acknowledged), an isolation checkpoint (passed), and restoration RES-0031 (60 MW restored, firmware updated).

8 rows across all 8 models.