Scada Outage Bit Does Not Propagate Across Model Break
Last updated on JULY 06, 2017
Applies to:Oracle Utilities Network Management System - Version 18.104.22.168 to 22.214.171.124.0 [Release 1.12 to 2.3]
Oracle Network Management for Utilities - DMS - Version 126.96.36.199 to 188.8.131.52.0 [Release 1.12 to 2.3]
Information in this document applies to any platform.
There have been some instances of SCADA-initiated outages in subtransmission (above the model breal) which have grouped earlier predicted outages. Importantly, this means that the begin time on the outage (which would typically be affecting thousands of customers) is set to the earlier begin time of the predicted outage. For the recent outage of concern, it transpires that the scadaOpenGroupThreshold rule is not set for that (scada) device class (scada_sectionalizer_pm). However, even having corrected the rule misconfiguration, earlier predicted outages are still grouping. Looking at the outages generated across the model break, it appears that the "SCADA MASK" bit is not set, where the upstream device is operated via scada. Adding this class to the openGroupThreshold rule corrects the behavio (i.e. prevents earlier predicted outages grouping to the SCADA outage). This might be acceptable for a while, but may become restrictive where another model break at the distribution transformers is planned for the introduction of LV model, and the lack of distinction between scadaOpenGroupThreshold and openGroupThreshold may become limiting. In short, the SCADA MASK bit should propagate across a model break.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms