1. Utility Outage Management
  2. Data model and import order
Reference

The tables behind Utility Outage Management

Utility Outage Management ships with 10 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.

Tables
10
Features
6, plus shared settings
Change it
Add fields and tables in Proto

How the model is organised

Service cases:

Service cases. Outages from report to closure.

Field evidence and review:

Service evidence, review decisions, record attachments. Crew evidence, supervisor decisions and files.

Restoration records:

Outage incidents. Approved incident records per case.

Service areas and people:

Service areas, Organizations, team members, Users.

Operations control:

Operation receipts. Results of every guarded action.

Every table, by feature

Service cases

3 tablesAbout this feature
  • Service cases

    Outage service cases from report through verified restoration.

    Linked to Organizations, Team members, Service areas
  • Service areas

    Districts, circuits and service territories where outages are reported.

    Linked to Organizations
  • Organizations

    Utility operating companies and their operating configuration.

Triage and assignment

3 tablesAbout this feature
  • Service cases

    Outage service cases from report through verified restoration.

    Linked to Organizations, Team members, Service areas
  • Team members

    Authorized utility staff with role scope and authenticated platform identity.

    Linked to Organizations, Users
  • Operation receipts

    Durable receipts for guarded operations with stable operation keys.

    Linked to Service cases

Field evidence and review

4 tablesAbout this feature
  • Service evidence

    Source-identified operational evidence received against a service case.

    Linked to Service cases
  • Review decisions

    Independent reviewer decisions recorded against a frozen revision.

    Linked to Service cases, Team members
  • Record attachments

    Files supporting a service case with visibility and evidence type.

    Linked to Service cases, Team members
  • Service cases

    Outage service cases from report through verified restoration.

    Linked to Organizations, Team members, Service areas

Restoration records

4 tablesAbout this feature
  • Outage incidents

    Outage incident records supporting record verified service restoration.

    Linked to Service cases, Organizations
  • Service cases

    Outage service cases from report through verified restoration.

    Linked to Organizations, Team members, Service areas
  • Service evidence

    Source-identified operational evidence received against a service case.

    Linked to Service cases
  • Review decisions

    Independent reviewer decisions recorded against a frozen revision.

    Linked to Service cases, Team members

Service areas

3 tablesAbout this feature
  • Service areas

    Districts, circuits and service territories where outages are reported.

    Linked to Organizations
  • Service cases

    Outage service cases from report through verified restoration.

    Linked to Organizations, Team members, Service areas
  • Organizations

    Utility operating companies and their operating configuration.

Operations control

2 tablesAbout this feature
  • Operation receipts

    Durable receipts for guarded operations with stable operation keys.

    Linked to Service cases
  • Service cases

    Outage service cases from report through verified restoration.

    Linked to Organizations, Team members, Service areas

Shared and settings

1 table
  • Users

    Users

    Linked to Users

Keys and references

Evidence, decisions, attachments, incidents and operation receipts reference their case. Cases reference their service area, owner and organization. Team members link to user accounts. Keep case record numbers, service area codes and external incident IDs stable and import by them.

Migration order

  1. Load Organizations, Users and team members.
  2. Load service areas with codes, contacts and notes.
  3. Load open service cases with their external incident IDs.
  4. Load recent outage incidents for reporting history.
  5. Reconcile open cases with your outage reporting system and test permissions before go-live.

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