Energy & Utilities

Grid Event Intelligence

Designed for Control-room operator

Help control-room operators cut through alarm storms by correlating SCADA events with network topology, weather, and field work into a ranked probable-cause narrative, while every switching action stays an operator decision.

Contract ENE-03 · primary aggregate GridEvent · mode loading

Decision brief

Execute operator-approved switching: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Control-room operator

The named role remains accountable for the consequential decision.

Governed evidence

6 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

1 approval gate

Approval gates prevent the copilot from making consequential decisions.

Business problem

A summer storm produces 214 alarms in six minutes; the copilot correlates them into three grid events, attributes the largest to a lightning strike two kilometres from a failed recloser, rules out a fourth cluster as planned crew switching, and proposes a back-feed restoration that the operator reviews and executes for 4,800 customers..

Decision to make

Help control-room operators cut through alarm storms by correlating SCADA events with network topology, weather, and field work into a ranked probable-cause narrative, while every switching action stays an operator decision.

Outcome to show

Executed switching order and updated event disposition gives Control-room operator the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Ingest alarms and protection operations
  2. 2Correlate alarms into a single grid event
  3. 3Rank probable causes with context
  4. 4Propose restoration switching
  5. 5Execute operator-approved switching

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Control-room operator verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved GridEvent evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Help control-room operators cut through alarm storms by correlating SCADA events with network topology, weather, and field work into a ranked probable-cause narrative, while every switching action stays an operator decision.
Primary aggregate
GridEvent
Primary container
gridEvents
Hierarchical key
/tenantId + /controlAreaId
Schema version
1

Sample scenario

A summer storm produces 214 alarms in six minutes; the copilot correlates them into three grid events, attributes the largest to a lightning strike two kilometres from a failed recloser, rules out a fourth cluster as planned crew switching, and proposes a back-feed restoration that the operator reviews and executes for 4,800 customers.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
gridEvents Primary /tenantId + /controlAreaId GridEvent, ScadaAlarm, NetworkTopologySnapshot, WeatherObservation, FieldWorkLogEntry, OperatorActionProposal

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
GridEvent gridEvents /tenantId + /controlAreaId gridevent::{controlAreaId}::{eventId} None
ScadaAlarm gridEvents /tenantId + /controlAreaId alarm::{controlAreaId}::{alarmId} None
NetworkTopologySnapshot gridEvents /tenantId + /controlAreaId topology::{controlAreaId}::{snapshotUtc} None
WeatherObservation gridEvents /tenantId + /controlAreaId weather::{controlAreaId}::{observationUtc} None
FieldWorkLogEntry gridEvents /tenantId + /controlAreaId worklog::{controlAreaId}::{logId} activityNarrativeVector
OperatorActionProposal gridEvents /tenantId + /controlAreaId proposal::{controlAreaId}::{proposalId} riskNotesVector

Query patterns