RX_INCIDENTS

Much of the data in this table may be viewed on Responder Explorer Incidents tab by right-clicking an incident and selecting Edit Incident.

Field Name

Description

STATUS

The status of the incident. This field uses the STATUS domain.

REGION

The region in which the incident is located. This field uses the REGION domain.

CRITICAL

Indicates if the incident is at a customer site that is critical. This field uses the CRITICAL domain.

CAUSE

Indicates the cause of the outage. This field uses the CAUSE domain.

WEATHER

Indicates the weather at the incident site. This field uses the WEATHER domain.

TROUBLE

Indicates the problem reported by the customer (e.g., no power, flickering lights, etc.). This field uses the TROUBLE domain.

CUSTOMER_COUNT

Indicates the number of customers affected by the incident.

CRITICAL_CUSTOMER_COUNT

Indicates the number of critical customers affected by the incident.

PRIORITY_CUSTOMER_COUNT

Indicates the number of priority customers affected by the incident.

FEEDER_ID

The Feeder ID of the incident device.

SUBSTATION

The substation that feeds the incident device.

TIME_CREATED

The time the incident was created.

TIME_OUTAGE

The time the outage occurred.

TIME_RESTORED_EST

The time power is estimated to be restored.

TIME_RESTORED

The time power is actually restored.

REMARKS_DISPATCH

Remarks from the dispatcher.

REMARKS_FIELD

Remarks from the field crew.

USER_CREATED

The name of the user who created the record. This field is populated automatically by Responder.

USER_UPDATED

The name of the user who updated the record. This field is populated automatically by Responder.

CONFIRMED

Indicates whether the device has been confirmed out. This field uses the CONFIRMED domain.

ORIGINATION

Indicates whether an incident was created by a user or by Prediction Services.

OWNER

The dispatcher to whom the incident has been assigned.

CANCEL_REASON

Reason the incident was cancelled.

NETWORK_LEVEL

This value indicates the grouping to which the incident device belongs. For example, incidents may be grouped by distribution vs. transmission. In this case all incident devices would have a Network Level value of distribution or transmission.

AMI_EVENT

The type of outage reported by the meter (e.g., No Power, Partial Power).

QR code for this page

Was this helpful?