This section is relevant for those customers that has or is thinking about getting the module for SCADA-prenumeration. Except for the software for the prenumeration, a minor configuration adjustment is required in order for the SCADA-events to find the Operating order.

SCADA-events are sorted to the assumed operating order according to similar regulations as for the switch orders. Operation rows are marked as executed as they occur in SCADA.

If the previous operation row is not executed:

If the SCADA timestamp is within three minutes of the planned time for the operation row, the operation is marked as completed. If the difference is greater than three minutes, the SCADA event is not automatically matched with the operation row. This behavior can be reconfigured on demand.

In order for the SCADA-event to find the right row, it is important that the planned time is set as correctly as possible. Normally there is a time margin applied, that is set for two hours in order for the system to connect a SCADA-event with the planned time for the operation row. For those customers that has the possibility to navigate to/start maneuvering in SCADA from dpPower the handling becomes much easier. The regulatory framework for matching against the presumed row is extensive. Now and then the system can still make a "wrong guess". To move the operations correctly, you can apply the same handling as for outages:

•Move operations that are wrong to the tab Events.

•Move operations from the tab Events to the intended outage (only when an operating order is missing) or to an operating order.