About Program Event Settlement Transactions

Program event settlement transactions represent credits that will be applied to a customer's bill based on participation in an individual event. Note that program event settlement transactions aren't applied directly to a customer's bill. A customer's program event settlement transactions are totalized into Customer Settlement Transactions (seeAbout Customer Settlements Transactions) which are applied to the customer's bill.

Program event settlement transactions are calculated in different ways depending on the type of event and the program on which they're based. Typically programs are based on either consumption saved or demand reduction events.

• Program event settlement transactions for consumption-based program events can be calculated as they created. The consumption saved per hour (represented as hourly interval values, typically in kWh) are multiplied by hourly prices for the same date and time and the results are totaled to create an settlement amount that will be applied to the customer's bill. Program settlement transactions for consumption-based programs are referred to "kWh Avoided" program settlement transactions.
• Program event settlement transactions for demand-based program events can be calculated as they created or are calculated based on a calculated demand value for a specified period of time, such as a year, a season, and so on (these are referred to as "end of season"). For these demand-based events, program event settlement transactions capture individual demand reduction interval value as well as a the "Maximum Drop" for an event (the largest demand reduction value for the event) and are saved in a "Calculation Deferred" state until a Customer Settlement Transaction is created for the period. Program event settlement transactions for demand-based programs are referred to "kW Drop" program settlement transactions.
• When a Customer Settlement transaction is created for "end of season" demand-based programs, a new program event settlement transaction is created for the entire time period which calculates the average of a set of the "Maximum Drop" values from the "Calculation Deferred" transactions created previously. These program settlement transactions are referred to as "Combined kW Drop" program settlement transactions.

The Program Settlement Method attribute on the Program indicates when settlement is calculated for participating in an event. Options include:

• After Event Participation: Calculations are performed as each program event settlement is created. This option is most often used with settlement calculations based on non-peak or consumption measurements ("kWh Avoided"), but can be used with settlement calculations based on peak or demand measurements ("kW Drop").

• End of Season: Calculations are performed at the end of a specified time period (a year, a season, and so on). This option is used with settlement calculations based on peak or demand measurements ("kW Drop").

Program event settlement transactions can be created either from data received from Oracle Utilities Analytics Insights or via a monitor batch process run for program subscriptions (see Creating Program Event Settlement Transactions in About Program Subscriptions).

• When created from data received from Oracle Utilities Analytics Insights, Oracle Utilities Analytics Insights sends files containing details regarding consumption or demand reduction achieved for the duration of an event for each customer. A batch process imports these files and creates business flags that capture the data for each metered service point. These business flags in turn create program event settlement transactions containing data regarding reductions in consumption or demand for the event.
• When created via batch processing, data regarding reductions in consumption or demand for the event is calculated via Program Settlement Calculation Rules which perform a comparison of actual consumption or demand to a "baseline" that represents an estimate of the customer's consumption or demand for the event period had they not participated in the event. See Baseline Calculations for more information about this calculation.

There are three types of program settlement transactions:

• "kWh avoided" program event settlement transactions are created based on reductions in consumptions achieved for the duration of an event for each customer. See Processing KWH Avoided Files for more information about how "kWh Avoided" program event settlement transactions are created from business flags received from Oracle Utilities Analytics Insights.
• "kW Drop" program event settlement transactions are created based on reductions in demand achieved for the duration of an event for each customer. See Processing KW Drop Filesfor more information about how "kW Drop" program event settlement transactions are created from business flags received from Oracle Utilities Analytics Insights.
• "Combined kW Drop" program event settlement transactions are created by customer settlement transactions and contain demand reduction values derived from individual "kW Drop" program event settlement transactions in the "Calculation Deferred" state that fall within the date range of the customer settlement transaction.

Program event settlement transactions are created in the "Pending" state, and are processed by the Process Program Settlement (X1-PREVS) batch process which transitions the transaction to a specific state depending on the type of program settlement transaction:

• Pending "kWh Avoided" program event settlement transactions (for programs with a Program Settlement Method of "After Event Participation") are transitioned to the "Calculate" state where Consumption-based Program Settlement Calculation Rules defined for the program related to the program settlement transactions (See Understanding Program Settlement Calculation Rules for more information) are executed. The amount of a "kWh Avoided" program settlement transaction is calculated by applying the Program Settlement Calculation Rules defined on the metered service's program to the "kWh avoided" values from the program settlement transaction. These rules apply interval prices to the "kWh avoided" interval values and total the results for the event. Once the program settlement transaction calculations are complete, it is transitioned to the "Calculated" state.
• Pending "kW Drop" program event settlement transactions (for programs with a Program Settlement Method of "End of Season") are transitioned to the "Calculation Deferred" state. These are later used by customer settlement transactions and "Combined kW Drop" program settlement transactions.
• Pending "Combined kW Drop" program event settlement transactions are transitioned to the "Calculate" state where demand-based Program Settlement Calculation Rules defined for the program related to the program event settlement transactions (See Understanding Program Settlement Calculation Rules for more information) are executed. The amount of a "Combined kW Drop" program event settlement transaction is calculated by applying the Program Settlement Calculation Rules defined on the metered service's program to the "kW Drop" values derived from the program event settlement transactions in the "Calculation Deferred" state to calculate the overall reduction in demand and apply a price to calculate the settlement amount for the event. Once the program event settlement transaction calculations are complete, it is transitioned to the "Calculated" state.

Program event settlement transactions contain the following data:

• Program Subscription: The program subscription associated with the event for which the program settlement transaction was created

• Start Date/Time: The start date and time of the event

• End Date/Time: The end date and time of the event

• Parent Customer Settlement Transaction: The customer settlement transaction that is considered the "parent" of the program event settlement transaction. (Note: Only populated after after customer settlement transaction request is received). 

• Used on Bill: A flag that indicates (Yes or No) if the program event settlement transaction has been included in a customer settlement transaction.

• Status: The current status of the program event settlement transaction.

• Calculation Details:

  • Program Event: The program event for which the program event settlement transaction was created.

  • Price: The price used with "kW Drop" program event settlement transactions

  • Program Settlement Calculation Group: The program settlement calculation group containing the program settlement calculation rules executed as part of the program event settlement transaction.

  • Line Description: A single line description of the program event settlement transaction, which can be used when displaying the transaction on bills or reports.

  • UOM/TOU/SQI: The unit of measure, time of use period, and service quantity identifier combination used to define the interval usage values used in the program event settlement calculation. These are derived from the UOM/TOU/SQI defined on the business flag type of the business flag that created the program event settlement transaction.

  • Interval Size: The size of the interval usage values, represented as hours:minutes:seconds (HH:MI:SS). This is derived from the Interval Size defined on the business flag type of the business flag that created the program event settlement transaction. This should match the interval size used for interval price sets.

  • Maximum Drop: The largest demand reduction interval value for the event

  • Minimum Drop: The smallest demand reduction interval value for the event

  • Average Drop: The average demand reduction interval value for the event

  • Settlement Quantity: The total quantity used for the program event settlement.

    • For "kWh Avoided" program settlements, this is the "kwh avoided" consumption saved for the event period, calculated by adding together the individual "kWh avoided" values for the event period

    • For "Combined kW Drop" program settlements, this is the average of the "Maximum Drop" values selected by the Program Settlement Rule - Demand Based program settlement calculation rule.

  • Actual Consumption: The actual consumption for the customer for the event period (applicable only for "kWh Avoided" program event settlement transactions)

  • Program Settlement Amount: The program event settlement transaction's monetary amount, calculated by multiplying interval values by prices that apply to the event.

    • In the case of "kWh Avoided" program settlements, the interval values are individual "kWh avoided" interval values (from the "kWh avoided" business flags received from Oracle Utilities Analytics Insights)
    • In the case of "kW Drop" program settlements, the interval values are those derived from individual "kW Drop" program settlements (based on the Program Settlement Calculation Rule configuration).

  • Intervals: Details of the interval values and prices used in the program settlement transaction calculation, including:

    • Service Quantity Data Date/Time: The date and time of the interval value (per the UOM/TOU/SQI and price (if applicable)

    • Quantity: The interval value (per the UOM/TOU/SQI) for the interval date and time

    • Service Quantity Interval Condition: The condition code of the interval value (per the UOM/TOU/SQI) for the interval date and time

    • Price: The interval price for the interval date and time (applicable only for "kWh Avoided" program settlement transactions)

    • Program Settlement Amount: The monetary amount for the date and time, calculated by multiplying the "kWh avoided" interval value times the interval price at the interval date and time (applicable only for "kWh Avoided" program event settlement transactions)

  • Issues: One or more messages related to the program event settlement transaction.

Example - KW Avoided

An event scheduled for 12:00 PM to 6:00 PM on February 11, 2023 results in the following "kWh avoided" values for a particular customer:

This represents a total "Consumption Saved" of 29.00. 

Later, the system receives the following price data for this event period:

When a program event settlement transaction is calculated for this event, the details of the program event settlement transaction would be as follows:

• UOM/TOU/SQI:  kWh

• Interval Size: 01:00:00

• Consumption Saved: 29.00

• Actual Consumption: 430

• Program Settlement Amount: 12.15

• Intervals:  

System Data

Program event settlement transactions are based on the following system data:

Batch Processing

Program event settlement transaction processing is supported by the following monitor batch processes:

• Process Program Settlement (X1-PREVS): Used to transition program event settlement transactions in the "Pending" state to the "Calculate" state.

• Retry Program Settlement (X1-RTEVS): Used to retry program event settlement transactions in the "Issue Detected" state.

• Recalculate Program Settlement (X1-RCEVS): Used to recalculate program event settlement transactions in the "Calculated" state. This is used in the case of a rebill, when updated measurement data is received from the customer information system, or when updated "kWh avoided" data is received from Oracle Utilities Analytics Insights.

Use the Batch Control portal to learn more about the parameters used by these batch processes.

Correcting Calculated Program Event Settlement Transactions When Measurement Data Changes

In the event that updated measurement data is received after a program event settlement transaction has been calculated, but before it has been included in a customer settlement transaction, the program event settlement transactions must be recalculated and corrected. For example:

• A customer participates in a program event in May, and a program event settlement transaction is created for the event in "Pending" status.
• Measurement data for the customer for the month of May is received in June, and the program event settlement transaction is calculated and updated to the "Calculated" state.
• Before the program event settlement transaction been included in a Customer Settlement. updated measurement data for the customer is received.
• The program event settlement transaction must be recalculated to account for the change in measurement data (which could impact the baseline calculation results used in the transaction).

When updated measurement data is received and processed (via Direct Measurement Processing) the Create UT Correction for Baseline Derived SQs (X1-CRUTCORRB) Post-VEE algorithm on the IMD Type creates a Usage Transaction Correction activity (details regarding parameters for this algorithm can be found in the Detailed Description of the X1-CRUTCORRB Algorithm Type). When this activity is processed, the Recalculate Program Event Transaction Due to Measurement Change (X1-RECLPETMC) algorithm recalculates the program event settlement transaction and marks the transaction with a reason code of "Measurement Change".

Additionally, program event settlement transactions can be recalculated and corrected using the following options:

• Using Recalculate Program Settlement (X1-RCEVS) batch process (see Batch Processing). When using this option, the Recalculation Reason parameter must be set to "X1MC" (Measurement Change).
• Using the "Re-Calculate" button in the Record Actions section of the program event settlement transaction. When using this option, you must select the "Measurement Change" reason for the recalculation.