A usage subscription is a record that defines how usage data are collected, processed, and exported for a service point or a device. A usage subscription can have various components that specify the logic and parameters for performing various operations on usage data, such as validation, estimation, editing, calculation, or export. According to the Oracle Utilities Meter Data Management Business User Guide, one example of a component that can be configured in a usage subscription is:

Eligibility criteria: These are rules that determine whether a usage subscription generates a usage transaction or not. A usage transaction is a record that contains usage data that are ready for export to other systems, such as customer information system (CIS) or settlement system. Eligibility criteria can be used to filter out usage subscriptions that do not meet certain conditions or requirements for generating usage transactions.

Measurement condition codes are codes that indicate the quality or status of measurement data, such as raw, estimated, edited, validated, or final. Measurement condition codes are assigned at different stages of processing measurement data and can affect how measurement data are used for billing or analysis purposes. According to the Oracle Utilities Meter Data Management Business User Guide, the final measurement condition code is created from:

Post-VEE condition code: This is the condition code that is assigned after validation, estimation, and editing (VEE) processing has been performed on measurement data. VEE processing is a set of rules and algorithms that check and correct measurement data for any gaps, errors, or anomalies. The post-VEE condition code reflects the outcome of VEE processing and determines whether measurement data are ready for export or further processing.

A service point is a record that represents a physical location where a utility provides service to a customer. A service point can have one or more devices associated with it to measure the usage of the service. A device is a record that represents a physical meter or other equipment that records usage data. A device can have one or more measuring components associated with it to represent different types of usage data, such as interval, time of use, or scalar. According to the Oracle Utilities Meter Data Management Business User Guide, to set up a configuration that allows service points to be used with various meters and support interval, time of use, and scalar devices, one way to meet this requirement is:

Configure one service point, one device, and three measuring components to be related to the service point as required by the data scenarios. This can be done by creating a service point record and associating it with a device record that represents the meter. Then, creating three measuring component records that represent different types of usage data (interval, time of use, and scalar) and associating them with the device record. Depending on the data scenarios, different measuring components can be used to collect and process usage data for the service point.

A virtual meter is a meter that does not physically exist but is used to represent the usage of a group of meters or a portion of a meter. A virtual meter can be used to perform various calculations or adjustments on usage data, such as aggregation, derivation, allocation, or net metering. According to the Oracle Utilities Meter Data Management Business User Guide, to bill the university correctly for a new fast food restaurant that is being installed at the center of the university and whose usage will also be included in the university's master meter, the correct step is:

Use derivation algorithms to exclude the restaurant's usage from the master meter. This can be done by creating a virtual meter that represents the master meter minus the restaurant's meter and applying a derivation algorithm that subtracts the restaurant's usage from the master meter's usage. The virtual meter's usage can then be used for billing the university.

To allow an implementation to send bill determinants to CIS based on the requirements, you should set up the following usage subscription or usage calculation group configuration options:

Scalar usage calculation rule with a valid usage group: This defines how scalar consumption values are calculated from measurements and sent to CIS. You can define scalar usage calculation rules for different measurement types and associate them with usage groups.A usage group is a collection of usage calculation rules that are applied to measurements based on certain criteria3.

TOU usage rule with a valid usage group: This defines how TOU consumption values are calculated from measurements and sent to CIS based on specific TOU periods. You can define TOU usage rules for different measurement types and associate them with usage groups.A usage group is a collection of usage calculation rules that are applied to measurements based on certain criteria3.

You do not need to set up scalar specific group as a fallback VEE group or TOU usage group as a fallback VEE group. A fallback VEE group is used when there is no matching VEE group for a measurement based on its characteristics. A VEE group is a collection of VEE rules that are applied to measurements to validate, estimate, and edit them