Outage Information File
Outage information must be sent in two files: Outages and Outage Customers.
The Outages file contains information about outage steps. An outage step is a set of customers affected by an outage who have identical outage start and restoration times. Utilities often restore power in multiple steps, where some outages are restored to one set of customers in one step, and another set of customers is restored in the next step.
The Outage Customers file contains lists of affected customers for each outage step presented in the first file.
Outages
The outages file is meant to be a list of outage steps.
| Column | Description |
|---|---|
| OUTAGE_ID |
Outage identifier. Type: NUMBER Can be empty?: No. |
| STEP_ID |
Outage step identifier (starts at 1). Type: NUMBER Can be empty?: No. |
| OUTAGE_TIME |
Outage step start time. Type: DATE. See Date and Time Handling for details. Can be empty?: No. |
| RESTORE_TIME |
Outage step restoration time. Type: DATE. See Date and Time Handling for details. Can be empty?: No. |
| NUM_CUST_OUT |
Number of affected customers. Type: NUMBER Can be empty?: No. |
| DEVICE_TYPE |
Outage device type (device class name). This is the device that the customer's meter is attached to, or what point of the electrical network is serving the customer. For most customers, it is a supply transformer. Example Values:
Type: VARCHAR2(32) Can be empty?: Yes. |
| LATITUDE |
Latitude of the outage device location. Type: NUMBER Can be empty?: Yes. However, it is recommended that you complete this field. Otherwise, the outage device location will not be known. |
| LONGITUDE |
Longitude of the outage device location. Type: NUMBER Can be empty?: Yes. However, it is recommended that you complete this field. Otherwise, the outage device location will not be known. |
| CREWS |
Comma-separated list of crews that worked on this outage. Type: VARCHAR2(4000) Can be empty?: Yes. However, it is recommended that you complete this field. Otherwise, the application will not be able to use this data to calculate accurate restoration rates. |
| ENROUTE_TIME |
Time when the first crew was placed en-route to this outage. Type: DATE. See Date and Time Handling for details. Can be empty?: Yes. However, it is recommended that you complete this field if you are not populating ONSITE_TIME. Otherwise, the application will not be able to use this data to calculate accurate restoration rates. |
| ONSITE_TIME |
Time when the first crew arrived onsite for this outage. Type: DATE. See Date and Time Handling for details. Can be empty?: Yes. However, it is recommended that you complete this field if you are not populating ENROUTE_TIME. Otherwise, the application will not be able to use this data to calculate accurate restoration rates. |
| ZONE1 |
Level 1 control zone for the outage. Type: VARCHAR2(64) Can be empty?: No. |
| ZONE2 |
Level 2 control zone for the outage. Type: VARCHAR2(64) Can be empty?: Yes. |
| ZONE3 |
Level 3 control zone for the outage. Type: VARCHAR2(64) Can be empty?: Yes. |
| ZONE4 |
Level 4 control zone for the outage. Type: VARCHAR2(64) Can be empty?: Yes. |
| ZONE5 |
Level 5 control zone for the outage. Type: VARCHAR2(64) Can be empty?: Yes. |
| ZONE6 |
Level 6 control zone for the outage. Type: VARCHAR2(64) Can be empty?: Yes. |
| ZONE7 |
Level 7 control zone for the outage. Type: VARCHAR2(64) Can be empty?: Yes. |
| ZONE8 |
Level 8 control zone for the outage. Type: VARCHAR2(64) Can be empty?: Yes. |
| ZONE9 |
Level 9 control zone for the outage. Type: VARCHAR2(64) Can be empty?: Yes. |
| ZONE10 |
Level 10 control zone for the outage. Type: VARCHAR2(64) Can be empty?: Yes. |
| W_CUST_OUT |
Weighted number of affected customers. Type: NUMBER Can be empty?: Yes. However, it is recommended that you complete this field. Otherwise, the application will not be able to identify the number of weighted customers who are without power. Weighted customers are those who are given a higher priority due to special circumstances (such as customers in a hospital or school). |
| FEEDER_NAME |
Feeder name for the outage device. Type: VARCHAR2(64) Can be empty?: No. |
Example Outages File
"OUTAGE_ID"|"STEP_ID"|"OUTAGE_TIME"|"RESTORE_TIME"|"NUM_CUST_OUT"|"DEVICE_CLS"|"DEVICE_IDX"|"DEVICE_NAME"|"DEVICE_TYPE"|"LATITUDE"|"LONGITUDE"|"CREWS"|"ENROUTE_TIME"|"ONSITE_TIME"|"ZONE1"|"ZONE2"|"ZONE3"|"ZONE4"|"ZONE5"|"ZONE6"|"ZONE7"|"ZONE8"|"ZONE9"|"ZONE10"|"W_CUST_OUT"|"FEEDER_NAME"
0101010|1|"2024-05-28 11:21:00"||7|123|1234567890|"L20:32AI:69395:BSV:1234567890"|"bldg_towr"|||"56443"|"2024-06-28 16:01:46"||"UtilCo"|"Oracle City"|"Oracle Village"|"o-ov"|"l20"||||||5|"321"
0101011|1|"2024-05-28 11:46:00"||3|123|1234567891|"SN:58AB:T182:BSV:1234567891"|"bldg_towr"||||||"UtilCo"|"Oracle City"|"Oracle Town"|"o-ot"|"o_ot_ot21s"||||||1|"or_ac_le23"
0101012|1|"2024-05-28 12:46:00"||4|123|1234567892|"PS:23M:56447:BSV:1234567892"|"bldg_towr"|||"54773"|"2024-06-28 16:15:06"|"2024-06-28 16:57:34"|"UtilCo"|"Oracle City"|"Oracle Village"|"o-ov"|"o_ov_20s"||||||2|"or_ac_le35