Perform Baseline Calculations to Derive Post-Event Energy Reductions

A customer baseline represents an estimate of the electricity a customer would have consumed if a specific event, associated to a demand response program, had not occurred or if the customer had not participated in the event. This baseline is essential for accurately calculating the actual reduction in electricity consumption a customer achieves during the event. By having this precise measurement of curtailment, you can provide appropriate and fair incentives to the customer for their participation, ensuring a transparent and equitable exchange.

This feature introduces a new usage calculation rule for X of Y baseline methodology, providing users with a high degree of flexibility and control. You can now precisely define several key parameters, including:

• Data Selection: Specify the criteria for selecting the raw data.
• X and Y Values: Set the core X and Y values that define the baseline period.
• X of Y Type: Choose the method for calculating the average, with options for high, medium, or low consumption days to best reflect the customer's typical usage.
• Adjustment Parameters: Apply optional additive or multiplicative adjustments to the final baseline.

Based on this comprehensive configuration, the rule automatically handles the entire process for each customer's event participation. This involves identifying a set of qualifying days from the customer's interval meter reads. These are the days that meet the user-defined criteria and are suitable for baseline evaluation. From those qualifying days, the rule then selects the specific X days out of Y days that will be used to compute the baseline consumption. Finally, it applies any configured adjustments to the computed baseline, resulting in a highly accurate estimate of what the customer's consumption would have been in the absence of the event.

Following the successful calculation of the baseline, the Vector and Service Quantity Math calculation rule can be used to compute the avoided energy or demand. This rule leverages the application's native vector and service quantity math capabilities. It works by directly comparing the actual interval measurements recorded during the event with the calculated baseline consumption for the same period. Based on the specific configuration—whether the program aims to measure avoided energy or avoided demand—this rule will then accurately compute the final value. 

The feature also introduces a new usage transaction business object for program event settlement transactions. These transactions are generated by a plug-in monitor process on the Program Subscription after an event is completed. The business object will have a new "Event Settlement" class which will drive the menu, query, and maintenance portals, as well as handle foreign key references and maintenance BPA's. It follows the same pattern as the existing Event Settlement Transaction business object.

This provides you with the flexibility to define and manage program parameters with greater ease. Specifically, you can now associate baseline methods and calculation rules with a program, which then automatically apply to all enrolled participants. This is a significant improvement because these rules can be revised over time to reflect any program modifications. The ability to visualize and modify these parameters ensures complete transparency and verifiability. Ultimately, this guarantees the accuracy of performance-based incentives paid out for event participation, building trust and confidence in the program.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

To configure this feature, refer to the About Program Event Settlement Transactions section of the Oracle Utilities Digital Asset Cloud Service/Digital Asset Management Business User Guide for more information.