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

Oracle Utilities Meter Data Management (MDM) DataConnect is a feature that facilitates extraction of data for use in external applications such as energy management systems. According to the Oracle Utilities Meter Data Management Business User Guide, some examples of data that can be exported in the MDM version of DataConnect are:

Billing determinants: These are usage data that have been divided into time-of-use periods and applied with factors for billing purposes. Billing determinants can be exported to a billing system or a customer information system for generating bills or invoices.

Usage measurement data: These are raw or processed interval data that have been recorded by smart meters or other devices. Usage measurement data can be exported to an analytics system or a demand response system for analysis or optimization.

To configure the derived values that are relevant for a device, you should configure them on the measuring component type for the measuring components to be defined on the device. A measuring component type defines the type of measurement that a device can record, such as scalar, interval, or event. A measuring component type can also define the derived values that are calculated from raw measurements based on certain rules or factors. A measuring component is an instance of a measuring component type that is associated with a device.

You do not need to configure the derived values on the final measurement type, which defines how measurements are stored and processed in Oracle Utilities Meter Data Management. Final measurement types do not define derived values.

You do not need to configure the derived values on the device type, which defines the physical characteristics and attributes of a device, such as manufacturer, model, or serial number. Device types do not define derived values.

You do not need to configure the derived values on the measuring component, which is an instance of a measuring component type that is associated with a device. Measuring components inherit derived values from their measuring component types.

To configure the application to generate service investigative orders for revenue protection, you should perform the following tasks:

Set up VEE rules to look for low usage: VEE rules are used to validate, estimate, and edit measurements based on certain criteria. You can set up VEE rules to look for low usage patterns that may indicate theft or meter malfunction.

Configure service task type to look for Validation, Estimation, and Editing (VEE) exceptions, device events, and failed commands: Service task types are used to define the types of work that need to be performed on devices or service points. You can configure service task types to look for VEE exceptions, device events, and failed commands that may indicate theft or meter malfunction. You can also configure service task types to trigger service orders when these conditions are met.

Import device events related to theft: Device events are occurrences that happen on devices, such as tampering, reverse energy flow, or magnetic interference. You can import device events related to theft from smart meter systems using the Smart Grid Gateway or other integration methods.

You do not need to tune the AI engine to look for theft by using theft algorithms or configure case management. These are features of Oracle Utilities Revenue Protection Cloud Service, which is a separate product from Oracle Utilities Meter Data Management.

Asset and component specifications are used to describe design details and asset attributes that are common to a group of assets or components. According to the Oracle Utilities Meter Solution Cloud Service Business User Guide, some examples of smart meter specifications are:

Firmware: The software version installed on the smart meter

Asset type: The category of the smart meter, such as electric, gas, water, or heat

Manufacturer: The company that produced the smart meter