Scalar Proration VEE Rule Does Not Produce Equally Distributed Measurements
(Doc ID 2743168.1)
Last updated on JANUARY 11, 2021
Applies to:Oracle Utilities Customer to Meter Base - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
**Disclaimer:** This KM article may include the following abbreviations:
C2M - Oracle Utilities Customer To Meter and Advanced Meter Solutions
VEE-Validation Estimation and Editing Rules
IMD-Initial Measurement Data
On C2M version 126.96.36.199.0
The Scalar Proration rule distributes consumption evenly across the gap when no overlapping IMDs exist during this period. However, when a finalized measurement exists during the period being prorated, the calculated estimate is incorrect. Below is an example with Periodic Estimation running daily:
1) 1/1 : 10 KWH (Regular)
2) 1/1 – 1/2 : VEE Exception
3) 1/1 – 1/3 : VEE Exception
4) 1/1 – 1/4 : VEE Exception
5) 1/1 – 1/5 : VEE Exception
6) 1/1 – 1/6 : 60 KWH (Regular)
When the VEE Exceptions are retried in sequence, 1/1 – 1/2 gets the correct estimated value, but the estimate for 1/1 – 1/3 gets the same estimated value as 1/1 – 1/2 which is incorrect as the former IMD spans two days as opposed to just one.
When Periodic Estimation is configured, Estimation IMDs created have overlapping dates as the IMD Start Date would always equal the previous measurement date time.
When a subsequent read is available and the Estimation IMDs are retried in the right sequence, this would always cause the IMD duration for Scalar Proration to be calculated incorrectly for Estimation IMDs Day 2 and higher.
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