All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

Utility Outage Management · Available now

Utility outage management from first report to restoration.

Utility Outage Management follows each outage from the first report to a restoration the utility can prove. A service case records the subject, the service area, the asset reference, the number of affected units, when it was reported and, once fixed, when service was restored.

  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewOpen service cases
Utility Outage Management · Service cases

Open service cases

Service cases in one list

New service ca
Service cases in view
6
Total affected units
3,140
Reported
2
Triaged
2
Reported2
Oak Hollow feeder trip after stormMaple Court feeder 4
360
15 Nov
Pine Terrace service line downMaple Court feeder 4
890
18 Nov
Add
Triaged2
North Ridge transformer failureCedar Flats service area
590
17 Nov
Cedar Flats voltage lossMaple Court feeder 4
670
10 Nov
Add
Assigned1
Maple Court underground cable faultMaple Court feeder 4
210
23 Nov
Add
Review1
Riverbend substation breaker tripOak Hollow circuit 12
420
18 Nov
Add
Oak Hollow feeder trip after stormService cases · SC-72017
Reported
CounterpartyMaple Court feeder 4
Affected units360
Reported at15 Nov
Review evidenceSC-72017 · Oak Hollow feeder trip after storm

The utility supervisor reviews field evidence before restoration.

Waiting for Utility Supervisor
ApproveReturn
Example screen with sample data
Tables, ready to use
10
Saved views
11
Roles with set permissions
5
Reports and dashboards
6
Features

Work for coordinators, supervisors and field crews

Every feature works on the same records. Pick one to see the screen your team works in.

Service cases

Outage reports from intake to closure.

  • One case per outage
  • Affected units on the case
  • Closed only after restoration
  • Service cases
  • Service areas
  • Organizations
Explore service cases
OverviewCases awaiting review
Utility Outage Management · Service cases

Cases awaiting review

Service cases

New
Record numberSubjectCounterpartyAffected unitsReported atRevision
SC-28361Oak Hollow feeder trip after stormMaple Court feeder 473012 Nov290
SC-44786North Ridge transformer failureCedar Flats service area21005 Nov920
SC-77283Maple Court underground cable faultMaple Court feeder 45007 Nov860
SC-92522Riverbend substation breaker tripNorth Ridge district50019 Nov500
SC-66186Pine Terrace service line downWestfield circuit 945025 Nov230
6 of 6 records
Oak Hollow feeder trip after stormService cases · SC-28361
CounterpartyMaple Court feeder 4
Affected units730
Reported at12 Nov
Revision290
Example screen with sample data
Process

From first report to verified restoration

Report to verified restoration ships ready to use. 2 steps need a named approval before the work moves on: Review evidence (Utility Supervisor) and Approve incident record (Utility Supervisor).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Report case

    Record the outage with its area, asset and affected units.

    Oak Hollow feeder trip after stormSC-72017 · Outage Coordinator
    Report caseBy Outage Coordinator
  2. Triage case

    Check the case and assign the authorised responder.

    Oak Hollow feeder trip after stormSC-72017 · Outage Coordinator
    Triage caseBy Outage Coordinator
  3. Review evidence

    A supervisor reviews the crew's field evidence.

    Oak Hollow feeder trip after stormSC-72017 · Utility Supervisor
    Review evidenceBy Utility Supervisor
    ApprovalThe utility supervisor reviews field evidence before restoration.
  4. Confirm restoration

    Restore the case from crew evidence with the real time.

    Oak Hollow feeder trip after stormSC-72017
    Confirm restoration
  5. Approve incident record

    A supervisor approves the incident record once.

    Oak Hollow feeder trip after stormSC-72017 · Utility Supervisor
    Approve incident recordBy Utility Supervisor
    ApprovalThe utility supervisor approves each incident record; self-approval is refused.
  6. Close case

    Close the case after the record is approved.

    Oak Hollow feeder trip after stormSC-72017 · Outage Coordinator
    Close caseBy Outage Coordinator
Inside a record

One case, its evidence and its record

Open any service ca to see its operation receipts, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Counterparty, Affected units and Reported at.

  2. 2
    Operation receipts

    Each line is linked to this service ca.

  3. 3
    Who works on it

    Outage Coordinator, Utility Supervisor and Field Crew Lead, each with their own permissions.

  4. 4
    Process stages

    Every status change, in order.

  5. 5
    Approvals

    Review evidence and Approve incident record, with who decides.

Open service casesOak Hollow feeder trip after storm
Utility Outage Management · Service cases

Oak Hollow feeder trip after storm

Maple Court feeder 4 · Reported

Log activity
1
Record details
CounterpartyMaple Court feeder 4
Affected units360
Reported at15 Nov
2
Operation receipts

Oak Hollow feeder trip after storm

IdOperation keyAction
OUT-2026-1042outage-1042-dispatchDispatch field crew
OUT-2026-1043outage-1043-isolateIsolate damaged feeder
OUT-2026-1044outage-1044-restoreRecord restoration time
Operation receipts
6
3

Who works on it

  • Outage CoordinatorManage service cases, outage incidents, record attachments
  • Utility SupervisorManage review decisions
  • Field Crew LeadManage service evidence
5

Approvals

  • Review evidenceUtility Supervisor
    Approved
  • Approve incident recordUtility Supervisor
    Waiting
Example screen with sample data
Approvals

Restoration you can prove

OverviewApprovals
Utility Outage Management · Overview

Approvals

Signed in as Utility Supervisor

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • OI-47696OUT-2026-1042
    Brook Lane pole damageRequested by Outage Coordinator
    Waiting0dActions
  • OI-75187OUT-2026-1043
    Pine Terrace service line downRequested by Outage Coordinator
    Waiting3dActions
  • OI-57401OUT-2026-1044
    Brook Lane pole damageRequested by Outage Coordinator
    Waiting5dActions
  • OI-20177OUT-2026-1045
    Brook Lane pole damageRequested by Outage Coordinator
    Waiting6dActions

Who approves what

DecisionApprover
Review evidenceA supervisor reviews the crew's field evidence.Utility Supervisor
Approve incident recordA supervisor approves the incident record once.Utility Supervisor
Approve service evidence, outage incidentsUtility Supervisor
3 approval rules · set per role in Proto
Example screen with sample data
Roles

A workspace for each role

Everyone opens Utility Outage Management to the work that is theirs. Pick a role to see what it starts with.

Outage Coordinator

Owns service cases, triages them and assigns the responder.

This is the first screen this role sees.

OverviewIncidents awaiting decision

Incidents awaiting decision

Outage incidents · Outage Coordinator

IdParentService areaStarted atRestored atAffected customers
OUT-2026-1042Brook Lane pole damageOak Hollow circuit 1216 Nov25 Nov510
OUT-2026-1043Pine Terrace service line downNorth Ridge district06 Nov14 Nov280
OUT-2026-1044Brook Lane pole damageMaple Court feeder 424 Nov02 Dec480
OUT-2026-1045Brook Lane pole damageRiverbend substation zone07 Nov09 Nov270
OUT-2026-1046Riverbend substation breaker tripPine Terrace neighborhood26 Nov05 Dec150
6 of 6 records
Example screen with sample data
Reports

Cases, restoration time and exceptions by area

Cases by area, affected customers, restoration time, review turnaround and exceptions.

Overview
Utility Outage Management · Overview

Utility Outage Management dashboard

This quarter

Outage incidents in view
6
Total affected customers
1,770

Service cases by status

How far records got this quarter

StageReachedStep
Reported45
Triaged1431%
Assigned429%
Review250%

Affected units by status

Sample totals per stage

2.0k0
2.0kReported
-3000Triaged
-1000Assigned
0Review
1.0kRestored
Example screen with sample data
  1. 01Cases by service area and status

    Where are outages open right now, and where are they closed?

  2. 02Affected units and customers

    How many units were out per case, and how many customers per approved incident?

  3. 03Time to restoration

    How long from report to restoration per case and area?

  4. 04Evidence review turnaround

    How long do supervisors take to review evidence?

  5. 05Weekly reports and restorations

    Cases reported and restored each week.

  6. 06Operation exceptions

    Pending, failed and needs-review operations with their reason.

Controls

No duplicate cases, no unverified restoration

Each stage of report to verified restoration names the role that acts and the status it records, so a change is never anonymous.

OverviewReport to verified restoration
Utility Outage Management · Process

Report to verified restoration

Each stage, the role that acts and the status it records

Process stages
12
Approval steps
2
Roles involved
4
Tables touched
7
Triage case
Outage Coordinator
StatusReported → Triaged → Assigned
RecordsOrganizations
Review evidenceApproval
Utility Supervisor
StatusAssigned → Review
Confirm restoration
Any role with access
StatusReview → Restored
Report to verified restoration
  1. Start
    Triage caseReported → Triaged → Assigned
    Organizations
  2. Approval
    Review evidenceAssigned → Review
    Utility Supervisor
  3. Step
    Confirm restorationReview → Restored
  4. Step
    Submit incident recordDraft → Submitted
    Outage incidents
  5. Approval
    Approve incident recordSubmitted → Approved
    Utility Supervisor
Example screen with sample data
AI agent

Prepare the next shift with Proto

Prepare and review outage work with Proto.

It can

  • Outage Coordinator: List open cases by service area with affected units, largest first.
  • Utility Supervisor: Show cases waiting for evidence review and incident records waiting for approval.
  • Field Crew Lead: Show my assigned cases and the evidence still missing on each.
  • Operations Analyst: Summarize failed or pending operations from the last shift.

Stays with a person

  • Coordinators triage and confirm restoration, supervisors review evidence and approve incident records, and crews record evidence.
  • Proto prepares lists and drafts for them; it does not confirm, approve or record evidence on its own, and it works with the permissions of the person or service account it runs as.
Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • Utility Outage Management
  • Outage reports and contact centre
  • Network operations and SCADA
  • Field crew devices
  • Identity provider
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 10 tables
10tables
  • Service cases3
  • Triage and assignment3
  • Field evidence and review4
  • Restoration records4
  • Service areas3
  • Operations control2
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Agree the operating boundary

    The system holds cases, evidence, reviews, incident records and operation receipts. Outage detection, telemetry and customer notifications stay in connected systems. The utility decides priorities and when service counts as restored.

  2. Map the source data

    Agree service area codes, case numbers and which external incident ID to keep. Load open cases and recent incidents.

  3. Configure a bounded pilot

    Run one district for a month: triage, evidence review, restoration and incident approval.

  4. Rehearse the exceptions

    A repeated confirmation never restores twice, a coordinator cannot approve their own incident record, restoration needs crew evidence, and a duplicate external incident is not entered twice.

  5. Reconcile and release

    Compare cases and restoration times with your current records, get sign-off from the supervisor and agree the rollback window.

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for Utility Outage Management.

All questions
How do I get started?

Click Get started, then use Proto to configure Utility Outage Management for your business. Start with one district's service areas and run a month of outages live before adding more.

Does it detect outages automatically?

Detection stays in your network and telemetry systems. This system takes the reports, runs triage, evidence review and restoration, and keeps the incident record.

What stops the same outage being entered twice?

The external incident ID from the reporting system is kept on the case, so repeat reports of the same incident are matched.

How is restoration confirmed?

From crew evidence such as readings with their source, after the supervisor has reviewed it.

Who approves the incident record?

A utility supervisor other than the coordinator who prepared it.

What if the network drops during a storm?

Each action has an operation receipt. Repeated actions take effect once, and unfinished ones wait in an exception queue until checked.

Does it work for water and gas too?

Yes. Evidence lines carry any measured value and unit, so pressure or quality readings work the same way as voltage.

Can we run several districts?

Yes. Each district is a service area; several organizations can each have their own.

What drives the cost?

Ordinary manual use has no per-user charge under the platform policy. Imports, integrations, agent execution and other machine work use prepaid credits; implementation is scoped separately. The pricing page lists current rates.

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

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appUtility Outage Management

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.