Support More Than One Event Settlement Method for the Same Program

Currently, the application lets you configure only one Event Settlement Method as a program-level attribute, while the associated Settlement Calculation Group is maintained separately in a different zone. The settlement calculation group can include one or more calculation rules that define the baseline methodology, any variable-level computations (such as Vector and Service Quantity Math), and other settlement-specific logic such as deferred calculations. This feature will allow the application to support a more flexible settlement configuration by allowing you to associate multiple settlement methods to a single program and, when a customer or device participates in an event, to run settlement calculations independently for each method based on its configured calculation group. As part of this change, the current model that restricts a program to a single “Event Settlement Method” program-level attribute will be discontinued and replaced with the new multi-method configuration approach.

To support configuring multiple settlement methods for a program, the Settlement Calculation Group zone has been enhanced to capture the settlement method (such as Post Event or End of Season) along with the associated calculation group. This update allows you to create multiple entries in the zone—one per settlement method—to link several settlement methods to the same program. The application enforces uniqueness by preventing duplicate effective calculation groups for a given settlement method.

For instance, you can now configure a Residential Program to use a 'Post Event' settlement method with a 'kWh Settlement' calculation group that applies a baseline rule, calculates kWh savings via a VSM rule, and then settles those savings at the end of the event. Similarly, a Commercial Program can be configured to support multiple calculation groups (such as kWh settlement and kW settlement) under 'Post Event', each with its own baseline, calculation, and end-of-event settlement rule. While another Commercial Program can further be configured to support 'Post Event' kWh settlement, 'Post Event' kW settlement that is deferred, and an 'End of Season' method that finalizes kW settlement later—each handled through its own calculation group and rule set.

Allowing multiple settlement methods at the program level lets a utility support different settlement constructs (for example, kWh savings, kW drop, post-event payments, deferred or end-of-season true-ups) within a single program instead of creating and managing duplicate programs. This increases flexibility to meet tariff, regulatory, and market timelines, improves accuracy and fairness by applying the right calculation rules per settlement path, and reduces administrative overhead and configuration risk. It also strengthens transparency and auditability by clearly separating rule sets and results per method, making reporting and dispute resolution easier while enabling faster evolution and piloting of new settlement approaches.

Steps to enable and configure

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