Comprehensive and Detailed Explanation From Exact Extract:

In Oracle Utilities Customer to Meter, transitioning from legacy scalar Time-of-Use (TOU) meters to smart meters in an Advanced Meter Infrastructure (AMI) roll-out requires careful configuration to maintain existing TOU billing periods and rates. The Oracle Utilities Customer to Meter Configuration Guide outlines the steps to support this requirement, focusing on usage calculation groups and TOU mapping rules. The correct actions are:

Option A: Add a new usage calculation group with a TOU mapping usage calculation rule.This is correct, as a new usage calculation group may be needed to handle the data from smart meters, which often provide interval data rather than scalar readings. The TOU mapping usage calculation rule ensures that the smart meter data is mapped to the existing TOU periods (e.g., peak, off-peak) for billing consistency.

Option C: Set up the new or existing usage calculation group to be identified dynamically by plug-in logic configured on the usage subscription if not configured already.This is correct, as dynamic identification of the usage calculation group via plug-in logic on the usage subscription allows the system to select the appropriate group based on the meter type (e.g., smart meter vs. legacy). This ensures flexibility and compatibility with the new AMI infrastructure.

Option E: Add a TOU mapping usage calculation rule to the existing usage calculation group.This is also correct, as an alternative to creating a new group, the existing usage calculation group can be updated with a TOU mapping rule to process smart meter data while maintaining the same TOU periods, avoiding the need for extensive reconfiguration.

The Oracle Utilities Customer to Meter Implementation Guide explains that TOU mapping rules are critical for aligning meter data with billing periods, especially during AMI transitions. Smart meters typically provide granular interval data, which must be aggregated and mapped to TOU periods using these rules to match the legacy billing structure.

The other options are incorrect:

Option B: Add the TOU mapping usage rule to the Customer Rate Schedule extendable lookup for the rate.This is incorrect, as TOU mapping rules are part of usage calculation groups, not rate schedules, which focus on billing calculations.

Option D: Set up the new usage calculation group to be identified dynamically by plug-in logic configured on the usage subscription’s type if not configured already.This is incorrect, as plug-in logic for dynamic group identification is typically configured on the usage subscription, not the subscription type.

Option F: Add the new usage calculation group to the Customer Rate Schedule extendable lookup for the rate.This is incorrect, as usage calculation groups are linked to usage subscriptions, not rate schedules.

Practical Example:A utility replacing scalar TOU meters with smart meters wants to maintain peak (7 AM–7 PM) and off-peak (7 PM–7 AM) billing periods. They create a new usage calculation group with a TOU mapping rule to aggregate smart meter interval data into these periods (Option A). Alternatively, they update the existing group with a TOU mapping rule (Option E). Plug-in logic on the usage subscription dynamically selects the appropriate group based on whether the meter is smart or legacy (Option C). This ensures billing continuity without changing the rate.

The Oracle Utilities Customer to Meter User Guide highlights that these configurations enable seamless AMI transitions, allowing utilities to leverage smart meter capabilities while preserving existing billing structures.