[Understanding Measurements and Performing Validation/Editing/Estimation (VEE) Processing] When a request for usage is initiated for billing…

In the Oracle Utilities framework, a Measurement entity represents a meter reading. The Validation, Editing, and Estimation (VEE) process operates on these measurements to ensure their accuracy before billing. When a previously billed read is corrected, a new or updated Measurement record is created. This new Measurement is the primary data entity that represents the corrected value. It serves as the fundamental trigger, or "notification," for the system to re-calculate usage for the affected period. Downstream processes, such as the usage calculation engine, detect this superseding measurement and then instantiate a new Usage Transaction, which in turn drives the billing correction. The Measurement is the authoritative source of the correction event.

A. Correction Note: This is not a standard, defined entity in the Oracle Utilities data model for this purpose; it is a plausible but incorrect distractor.
B. Off Cycle Bill Generator: This is a batch process that creates a bill, not a data entity representing a notification of a corrected read.
D. Usage Transaction: This entity is a result of the corrected read. It is created after the system is notified by the new measurement, but it is not the initial notification itself.
E. Usage Request: This entity is used to initiate the original usage calculation process, not to signal a subsequent correction to a reading.

1. Oracle Utilities Customer to Meter Cloud Service (23C) - Business User Guide

Chapter: "About Validation

Editing

and Estimation (VEE)". This chapter details how the VEE process is centered on validating

editing

and creating final

billable measurements. It establishes that the Measurement is the core entity managed in this process. A correction is fundamentally an edit to a measurement

making the Measurement entity the representation of that change.

2. Oracle Utilities Customer to Meter Cloud Service (23C) - Business User Guide

Chapter: "About Usage and Usage Transactions"

Section: "Correcting Billed Consumption". The documentation states

"When you correct a read that has been used to create a bill segment

the system automatically creates a usage transaction for the corrected read." This shows the process is triggered by the corrected read (represented by the Measurement entity)

which then leads to the creation of a Usage Transaction. The Measurement is the cause

and thus the notification.

3. Oracle Utilities Meter Data Management Business User Guide (2.7.0.1)

Chapter 4: "Validation

Editing

and Estimation"

Page 4-1. The guide describes VEE as a process that "validates initial measurements... and creates final

billable measurements". This reinforces that the entire correction and validation lifecycle is centered on the Measurement entity

which serves as the definitive record and notification of data quality and changes for downstream systems like billing.