Device Availability for Self-Healing

<< Click to Display Table of Contents >>

 

Device Availability for Self-Healing

The Self-Healing Module of Elipse Power uses availability signaling to identify which devices can be operated due to a contingency, that is, devices that can receive commands from the Self-Healing Module. Unavailable devices are not considered as a possibility of maneuvering to compose a Self-Healing Module solution.

The definition of Measurements that must be considered in the expression to provide a device to the Self-Healing Module is configured on the CSV load files (Remote and Substation Models). The result of that availability expression is a logical AND of all conditions configured in the CSV file, and the device is only available when all conditions are in the informed status, or in a normal operation status. Examples of Measurements that can turn a device unavailable are::

Communication failure

Some field condition in an abnormal status

Some field condition normalized, but it needs acknowledgment from an operator

A device was impacted by a Self-Healing Module maneuver and it is unavailable until an operator acknowledges its unavailability

A device received an opening or closing command and is unavailable until an operator executes an acknowledgment

A device was opened or closed by a field team and it is unavailable until an operator acknowledges its unavailability

A downstream device is unavailable

An operator blocked a device for the Self-Healing Module

 

The graphical representation of unavailability on the operation diagram is shown on the next figure.

Device unavailable

Device unavailable

Unavailability is represented by a dotted yellow rectangle around a device. The letter J, on the upper left corner, indicates that a device also turns all downstream devices unavailable, even open devices tied to other Feeders. If a device is unavailable due to any downstream device, the letter M is displayed on the upper left corner.

Was this page useful?