Determine Historical Usage Patterns using Spike Check Validation
(Doc ID 2167590.1)
Last updated on SEPTEMBER 26, 2022
Applies to:
Oracle Utilities Meter Data Management - Version 2.1.0.3 to 2.1.0.3 [Release 2.1]Information in this document applies to any platform.
Symptoms
In Oracle Utilities Meter Data Management version 2.1.0.3 there are two tolerances associated with the spike check validation to aid in identifying abnormal spikes: The minimum number of intervals must be greater than or equal to the configurable minimum number of intervals for this validation to be executed (20 intervals).
The factored peak ((highest interval – 3rd highest interval)/third highest interval) must exceed the configurable threshold (2000%).
There is one requirement for the spike check validation which looks back over a configurable period of time (i.e 648 hours) to determine historical usage patterns.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |