Operation of NonSCADA Device Via SCADAInterface Causes Outage Start Time/CMI Updated
(Doc ID 2812702.1)
Last updated on OCTOBER 06, 2021
Applies to:Oracle Utilities Network Management System - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 2.4 to 2.5]
Oracle Network Management for Utilities - DMS - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 2.4 to 2.5]
Information in this document applies to any platform.
On : 184.108.40.206.0 version
Operation of nonSCADA device via SCADAInterface causes outage start time/CMI to be updated
With some project's implementation of an ADMS system along side the NMS application (acting as a pure OMS system), they have effectively all devices flagged as "SCADA" such that ADMS can send controls to OMS.
A newly identified by-product of this is that when a predicted outage device is operated at a time after the initial calls (AMI or customer) the outage start time and all calls are then updated to the device operation time which then impacts project's reliability numbers by artificially reducing the Customer Minutes Interrupted.
For a "true" SCADA device, we do not expect this to be an issue as we expect to see customer/AMI calls to come in at relatively the same time or just after we see the SCADA device trip. However for nonSCADA devices which are manually operated in ADMS and state sent to OMS, this becomes an issue that CMI gap is created, which requires additional outage to correct the gap based on AMI times. This could be a substantial impact for a short-staffed reliability department.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document