Available in ArcMap.

An operator can manually create a fault on a device or on a line (cut). A cut indicates a break in the line that disrupts power. Device incidents indicate a faulty device and may be placed on any devices that have the RXINCIDENTDEVICE model name assigned (see Configuring Responder online help).

A fault may be created using this tool only on devices that are normally closed on any phase (e.g., NormalPosition = Closed). If you select a device that is normally open on all phases, you will be prompted to use the Create Switching Operation tool instead.

For example, if a customer calls and reports a transformer to be on fire, the operator can create an incident on that specific transformer.

Multi-Customer Load Points: When a fault is created on a mult-customer load point (e.g., apartment building) using the Create Fault tool, all customers at the load point are considered out.

Quick Steps

Create Fault

Locate device or cut location.
Click Create Fault.
Click device or cut location.
Enter outage time.
Enter time of restoration.
Update General Information.
Click OK.

Responder Explorer must be open to manually create a fault in ArcMap.

In ArcMap, locate the device or cut location on the map.
Click Create Fault on the Responder toolbar. The cursor becomes a circle with a blue dot in the middle. The blue dot snaps to all selectable devices and lines. A layer must be set as selectable before this tool snaps to its features.

Placing a Cut: When placing a cut, you can hold down CTRL to disable the snapping to devices. The cursor continues to snap to the line. This allows you to place a cut very near a device without snapping to the device. Cuts are always automatically confirmed when placed.

Origination: The Origination field allows you to manually create SCADA incidents. Any incident that has an Origination value of SCADA must also be confirmed. If you do not set the incident to confirmed, Responder issues a warning that the incident will be automatically confirmed.

Click the faulty device or the cut location. In the example below, an incident is created on the transformer over which the cursor is placed. The blue dot snaps to the transformer.
The Create Incident dialog allows the operator to enter an outage time (unless the Cause is Non-Outage) and an estimated restoration time. The outage time must be the current time or earlier. Responder does not allow the user to enter a future outage time.

Non-Outage: If you select "Non-Outage" as the incident Cause, the Actual Status field will equal the value in the Expected Status field. Once you click OK on the Create Incident window with the Cause set to Non-Outage, the Time of Outage field is set to null (since there was no actual outage).

Open Devices: If you place an incident on a device whose Expected Status is Open, the incident is automatically confirmed.
Enter values in the editable fields on the Create Incident window. In addition to the outage time you can modify the region, owner, confirmation status, hazard, remarks, etc. All fields in white may be edited. The Dispatcher field is filtered to display only the dispatchers that have access to the region in which the incident resides.
Click OK.

Responder places an incident on the device or at the cut location. Responder's Prediction Engine identifies the affected upstream load points and places outage symbology.

The outage area is highlighted on the map according to the symbology of the RxLineDisplay class. You must have this feature layer added to your map and the de-energized features functionality configured properly (see Responder Configuration Guide).

For incidents on normally open devices, the Actual Status defaults to the Phase Designation of the device. For all other devices, the Actual Status defaults to Open.

Creating Incidents Downstream of an Existing Incident

An incident may be created on a device downstream of an existing incident. When this situation occurs, you will be presented with the following window:

If the upstream incident has been confirmed, you may elect to consolidate the new downstream incident with the confirmed incident (in which case the new incident has a status of confirmed).

If the upstream incident is unconfirmed, you may only create a confirmed incident downstream. The option to add the device to the upstream incident is disabled.