Handling of events from SCADA

Received events are written down in a queue in the database. We wait at least 10 seconds before an event is being processed to await any events with earlier timestamps that reach us later so that we can sort the events in the correct order.  

 

The event proceeds through a policy based handling. The first regulation that matches, handles the event (the subsequent regulations will not be executed).

 

Below, the regulations are described as they are today and in the order that they are executed as standard. (It is possible to configure the order but what is described is the standard version).

 

1.Execute existing switch order rows in outage.

Criteria:

Tries to find a matching, not executed switch order row, on the same switch as:

•In an outage with the state Verified.

•Is the first row that is not executed in its switch order.

•Has a planned time that is within 2 hours (before or after) the time when the SCADA event occurred. Alternatively, if the planned time is not set, the case matches even though the previous row has an actual time less than 2 hours before the SCADA event occurred.

•Note! There can only be one row that matches the criteria above for the regulation to match.

 

Result:

If a matching switch order row is found, it is marked as executed and the actual time is set to the time of the SCADA event.

 

2.Reconnect customers that are out of power in the same outage

Criteria:

•The event returns the power to one or several customers.

•All the customers became out of power in the same outage.

•The outage is verified.

•All the operation rows in the outage are executed.

 

Result:

A new switch row is added and executed in the last outage and the actual time is set to the time of the SCADA event.

 

3.Reconnect an opened switch in the same outage

Criteria:

•The event is open/close.

•The latest switch row that opens/closes the switch is in a verified outage.

•All the switch rows in the outage are executed.

 

Result:

A new switch row is added and executed last in the outage, the actual time is set to the time of the SCADA event.  

 

4.Add an event in an outage that has made a switch out of power

Criteria:

•The location of the switch is in a network that is out of power.

•There is a verified outage with a switch row on a switch that would bring the power back to the network if it was opened/closed.

•All the switch rows in the outage are executed.

 

Result:

A new switch row is added and executed last in the outage, the actual time is set to the time of the SCADA event.  

 

5.Add events to the same switch in the same outage

Criteria:

• There is one outage with a switch row for the same device as in the SCADA event.

• The outage is verified.

 

Result:

A new switch row is added and executed after any existing executed rows. The actual time is set to the time of the SCADA event. The row is added before any rows not executed yet.

 

6.Create a new outage if customers becomes out of power

Criteria:

•The event causes the customers to become out of power.

 

Result:

•A new operation outage is created. The operation outage has one switch row on the switch in question. This switch row is executed and actual time is set to the time of the SCADA event.  

 

7.Add the event to the tab events

Criteria:

•None, this regulation is always a match. This is of course, like any other regulations, given that none of the previous regulations are a match.

 

Result:

One new switch row is added and executed. Actual time is set to the time of the SCADA event.