Earliest Power On from a Single Meter is Used As a Restoration Time During Restoration Verification
(Doc ID 2876054.1)
Last updated on JUNE 09, 2022
Applies to:
Oracle Utilities Network Management System - Version 2.3.0.2.0 to 2.5.0.2.0 [Release 2.3 to 2.5]Oracle Network Management for Utilities - DMS - Version 2.3.0.2.0 to 2.5.0.2.0 [Release 2.3 to 2.5]
Information in this document applies to any platform.
Symptoms
On : 2.3.0.2.0 version, Web Workspace
Earliest power on from a single meter is used as a restoration time during Restoration Verification
The following issue with restoration verification functionality has been reported:
- during restoration efforts, a meter may be powered on briefly multiple times before a final restoration is made
- when the outage is finally restored, the system does not issue a ping because of the meterPingSuppress rule enabled for Restoration Verification
- the time of the earliest power on is being used, even though in some cases it is hours before the actual restoration took place.
The following example was provided:
- At 02:54 AM a ticket was created for a customer with a Side Off
- The customers AMI meter was sporadically sending Power on Signals over the course of the morning, with the first occurring at 3:13 AM
- This is most likely due to a flickering light situation
- Operators made final repairs, with the final power on signal coming in at 9:05 AM
- Operators restored the job at 9:55 AM
- After the restoration, the system automatically changed the restoration time to 3:13 AM, which should be the restoration time to be set to 9:05 AM (last power-up received).
Cause
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
| Symptoms |
| Cause |
| Solution |
| Fix Description |
| Migration |
| References |