[Configuring Rates] An implementation is starting an Advanced Meter Infrastructure (AMI) roll-out initiative and they plan to replace their legacy scalar TOU meters with smart meters. They wantto continue to bill for the same TOU periods and they do not want to change the rate being used. Which three actions should an implementation take to support this requirement?

To support billing with smart meter interval data on an existing Time-of-Use (TOU) rate, the system must be configured to map intervals to the correct TOU periods. This requires a "TOU Mapping" usage calculation rule. There are two valid architectural approaches for implementing this logic:
1. Create a new, dedicated Usage Calculation Group for smart meters (A).
2. Modify the existing Usage Calculation Group by adding the new rule (E). Regardless of the chosen approach, the system needs to dynamically apply the correct logic based on the meter type. This is achieved by configuring plug-in logic on the usage subscription (or its type) to identify the appropriate "new or existing" usage calculation group at runtime (C).

B. Usage calculation rules are components of a Usage Calculation Group, not configured directly in a Customer Rate Schedule extendable lookup.
D. This option is too specific as it only refers to identifying a "new" usage calculation group, while option C correctly encompasses both scenarios (new or existing group).
F. The primary link between a usage subscription and its usage calculation group is determined dynamically by a plug-in, not via a Customer Rate Schedule extendable lookup.

1. Oracle Utilities Customer Cloud Service Administrative User Guide (23C)

Chapter: Usage Calculation

Section: Defining Usage Calculation Rules

Subsection: TOU Mapping.

This section details the purpose of the "TOU Mapping" rule type: "This type of usage calculation rule is used to process interval usage by mapping interval reads to the appropriate time of use periods defined on a TOU Map." This supports the core requirement of using a TOU mapping rule as stated in options A and E.

2. Oracle Utilities Customer Cloud Service Administrative User Guide (23C)

Chapter: Usage Calculation

Section: How is a Usage Calculation Group Determined?

This section outlines the hierarchy for determining the usage calculation group

with the first step being the "Determine Usage Calculation Group algorithm on the usage subscription type." This confirms that dynamic identification via plug-in logic is the standard mechanism

supporting the action described in option C. It also invalidates options B and F

which propose using extendable lookups.

3. Oracle Utilities Customer Cloud Service Administrative User Guide (23C)

Chapter: Usage Calculation

Section: Defining Usage Calculation Groups.

This section describes the process of creating and maintaining Usage Calculation Groups and their associated rules. It implicitly supports both creating a new group (Option A) and modifying an existing one by adding new rules (Option E) as standard configuration actions.