Skip to content
Okko Oulasvirta
Energy & Utilities

Grid Operations Assistant

Give the control room the live network state, the likely cause of a disturbance and the safe options — in one place, at the speed the grid moves.

The decision it supports

What is happening on the network right now, why, and what is the safe next move?

What changes

Faster, better-evidenced operator decisions during disturbances, and a record of what was seen and done. The operator acts within control procedures; the assistant assembles the picture.

Data domains

  • Grid and network
  • Assets
  • Weather
  • Metering

Interactive preview

Grid Operations Assistant is described here as an opportunity rather than shown as a working demonstration. The interactive build for this industry is Asset Health & Field Operations Twin — it uses the same primitives, the same governed data model and the same decision-to-action pattern this application would.

We build one flagship per industry properly rather than four shallow ones. The pattern transfers.

The workflow

  1. 01A disturbance or constraint is detected on the network
  2. 02The affected topology and current flows are shown live
  3. 03Probable cause is proposed with the signals behind it
  4. 04Weather and asset condition in the area are overlaid
  5. 05Safe response options are presented for the operator to weigh
  6. 06The operator acts within existing control procedures
  7. 07The event and the response are recorded for review

Platform capabilities most relevant here

  • Eventstreams

    Let operational applications react to what is happening now, not what happened yesterday.

  • Eventhouse / KQL

    Ask questions of high-volume machine and event data fast enough to act on the answer.

  • OneLake

    One governed copy of enterprise data that analytics, AI and applications can all build on.

  • Ontology

    Encode the vocabulary, relationships and rules your business already works with.

  • AI functions

    Apply language models to business data as a normal part of a data pipeline.

  • Fabric Apps

    Build the application where the governed data already lives, instead of copying it out.

  • Application state

    Remember decisions, assignments and approvals — the things a report cannot hold.

Not every application needs every capability. This is the subset that this decision actually depends on.

Talk about building this