Utilities and grid operations

Let the grid agent handle routine switching

Routine feeder reconfiguration runs without waiting for the control room. A switch affecting thousands of customers needs control-room review, and load shedding at a medical district stops without operator authorization.

Connecting the agent? See the developer guide for Energy & Utilities

A storm night on one district

Three proposals from the agent, and who handles each.

  1. Grid operations manager

    Wants routine reconfiguration handled by the agent so operators can watch the storm.

  2. Control-room supervisor

    Gets the 3,400-customer switch in the Inbox with the feeder and load facts, and approves it.

  3. System operator

    Is the only person who can authorize load shedding at the medical district. The agent cannot.

  4. Reliability compliance

    Reviews the night’s actions and approvals from one record the next morning.

Operators stay in charge

Authority you define

Operator-authorization rules keep the agent away from critical load unless a person approves.

Checked before it happens

Each switching proposal is checked against your limits before the agent acts on it.

One record per event

Proposals, approvals, and outcomes for an event sit together for reliability review.

Built-in handoff

Large switching actions wait for the control room

Control-room supervisor

The supervisor gets the proposed action with the facts behind it. If it sits too long, reminders go out and it escalates, and the decision goes back to the agent.

See the six role portals and how work moves between them

Why grid automation moves slowly

Utilities trust automation for routine work. The hard part is showing where the limits sit.

Critical facilities, like hospitals, need a person before anything changes their supply.

Operators need to see what the agent proposed and why while the event is still active.

Reliability reviews ask who authorized each action long after the shift ended.

Grid and field work to start with

Pick actions that are frequent, reversible, and already bound by written operating limits.

Switching and reconfiguration

Check customer impact, critical facilities, and operator authorization before the agent switches a feeder.

Maintenance planning

When the agent defers work on an asset, the condition data and the planner’s decision stay with it.

Outage triage

Route an anomaly to the right crew, with its severity and signal kept for the after-action review.

Start with routine switching in one district

Bring your operating limits and critical-facility list, and see what the agent can handle alone.