1. Utility Outage Management
  2. Features
  3. Operations control
Feature · Operations control

Operations control

Operation receipts, exceptions and reconciliation.

OverviewOutstanding operation receipts
Utility Outage Management · Operations control

Outstanding operation receipts

Operation receipts

New
IdOperation keyActionParentResult stateOccurred at
IDD-126OK-654ACT-944SC-35642Pending23 Oct
IDD-450OK-747ACT-627SC-33995Failed23 Oct
IDD-790OK-153ACT-356SC-68863Needs review12 Oct
IDD-493OK-546ACT-755SC-20035Pending14 Oct
IDD-287OK-775ACT-593SC-90342Failed23 Oct
6 of 6 records
IDD-126Operation receipts · OR-69103
Pending
Operation keyOK-654
ActionACT-944
ParentSC-35642
Occurred at23 Oct
Failure reasonCut to length
Example screen with sample data

What you can do

Know that every triage and confirmation took effect

Every guarded action, whether triage, evidence review, restoration confirmation, incident approval or a correction, writes an operation receipt. The receipt holds a stable operation key, the action, the case revision expected, the time and a result: pending, completed, failed or needs review. It lists the effects the action should have produced and, when something went wrong, the reason.

During a storm, connections drop and buttons get pressed twice. Receipts make that safe. A repeated action returns the first result, and anything that did not finish waits in the exception queue. Reconciliation re-reads the case records before marking a receipt completed, so the outage figures are built on what actually happened.

How the work is organized

The operations analyst works the exception queue; the supervisor follows it during major events.

  • One key, one effect. Each operation key takes effect once.
  • Checked against the case. Completion is confirmed from the saved case, evidence and decisions.
  • Exceptions together. Pending, failed and needs-review receipts appear in one list.

What to agree during setup

Agree who works the exception queue during normal days and major events, how often reconciliation runs, and when an exception is escalated. Prepare examples of a completed confirmation, a timed-out confirmation that did complete, one that did not, and a correction refused because the case had already moved on.

Check the handoff on an actual case

At the height of the storm three restoration confirmations time out. Their receipts are left pending. Reconciliation finds two of the cases restored with the right times and completes those receipts. The third case is still assigned, so its receipt stays in the queue. The analyst runs the confirmation again under the same key, the case is restored once, and the night’s figures are complete.

The morning after a major event the supervisor checks that the exception list is empty before the restoration figures go to management. An empty list means every triage, confirmation and approval recorded overnight is reflected in the cases themselves.

What your team sees

  • Outstanding operation receipts — Pending, failed and needs-review receipts with their reason.

Follow the work through

See reports.

What it keeps track of

Data model
Operation receipts
Durable receipts for guarded operations with stable operation keys.
Service cases
Outage service cases from report through verified restoration.

Who uses it

Permissions
Operations Analyst
, Utility Supervisor.
The analyst reconciles; the supervisor follows exceptions.

Set up Utility Outage Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started