Goals

The functionality aims to make it easier for the system designer based on Action.NET to implement in the project the storage of occurrences of interruption of supply and the use of this data for the generation of reports with the SAIDI and SAIFI indexes, daily, weekly and monthly, considered each feeder, each substation, city, and state served by the concessionaire.
To obtain the interruption events of the feeders correctly, it was considered appropriate to include, in the same project, the ease of Unifilars Energization Visualization. The advantage of this facility is to allow the definition of the bays topology of the substations and to calculate the energized state or not of each bay periodically. You must have an appropriate template for each type of bay for the bay.

General Project Organization

This item describes the overall organization of the project and the contents of the main tables so that the functionalities developed can be used more appropriately.

Objects Table

In the table Objects, each entry must be one of the bays of a substation.
For each type of bay, you must have an appropriate template for the Bay.
In this template, in turn, we will have sub-templates of point types grouped according to their functionalities. The figures show examples of this organization: the bays of a substation are shown.

In this example, we are showing the bays of a substation, with the name of ANAKAPELLE D2, for which the abbreviation was used ANKD2, to identify all bays.
In this case, we have the following types of bays, with their templates used in the table: Feeder, BusLow, Trafo, and SS_Data (general substation data).
In the column Category, the bays of the kind Feeders are indicated, which will be the targets of the SAIDI and SAIFIcalculation routines (for feeders).
In the column Comment, with a view to the use of Deploy Extension, which assists in creating points tables (for data acquisition), there is information on the NODES to be used.
And here is the definition of bays for feeders.

TOPG is the template for defining the substation topology. Together with the measurements (MEA) and status (STA), circuit breakers will be used by the calculation methods of the Unifilares Energizing Display feature to define power supply interruptions.
The SDFS template is used to save the daily calculated indicators of SAIDI and SAIFI for each feeder to have the history of these calculations over months and years.
The reason for the interruption separates the calculation: Planned, not planned, or occurred not in the feeders but upstream supplying bays—no tension on the bar before the feeder= NO_VOLT.

For each of these reasons, the indicators are calculated:

ASSETS Table (Levels)

Levels should be created in such a way that the geographical hierarchy necessary for the calculation of SAIDI and SAIFI should be defined by consumer areas such as

State

Division

City

Substation

Feeder

Therefore, all feeders will be located in some substations and some subdivisions and regions.

Categories Table

To access the bays through collections, when necessary, it is also recommended to define the types of bays through Categories, for example, for the calculation of SAIDI and SAIFI, only the Feeders.
The bays will then be assigned the Categories, categories.

Alarm Items Table

To better understand how the detection of de-energization occurrences works, refer to the manual
ActionNet - NT - Show Energizing functionality in Unifilares or
ActionNet - EN-NT - Energization Display in OneWire Diagrams .
To detect circuit breaker openings in feeders, alarms should be set in the Alarm Items table, both for circuit breakers and BAYSTATE members of the TOPG template.
For the calculation of the SAIDI and SAIFI, the alarms of circuit breakers will be used, but the alarms of the BAYSTATE member, defined in the TOPG template (topology), which should be one of the members of the feeder template.
This tag is calculated through the topology and indicates whether the bay is energized or not, regardless of the state of the nearby circuit breakers, but rather the connections in the topology. The figure shows this definition of alarms.

An alarm message is created when the BAYSTATE goes to zero (not energized). When you return to the energized state, you return to value 1; the normalization message is created. In this message, the field appears Duration, with the total time it was de-energized. This will be the time used for calculating SAIDI. The amount of these occurrences will be used to calculate the SAIFI.
See the example in the list of events.

See below the de-energization shown in the unifilar diagram.

Two other essential alarms, for the definition of the reason for the interruption, are:
OC_EF - Indication of occurrence of the trip (protective action)
NO VOLT - Indication of the event of NO_VOLT (lack of tension in the bay without having occurred protection).

Template SAIDI_SAIFI

The feature uses a specific template for controlling reports and name tables that SAIDI_SAIFI, which the project will need.
The figure shows this template.

The PARAMS sub-template saves constants used by SAIDI and SAIFI calculation methods, which can be changed from one project to another.