About Event Settlement Transactions

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

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.

• 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. Event settlement transactions for consumption-based programs are referred to "kWh Avoided" event settlement transactions.
• Event settlement transactions for demand-based program events, however, are calculated based on a calculated demand value for a specified period of time, such as a year, a season, and so on. For these demand-based events, 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. Event settlement transactions for demand-based programs are referred to "kW Drop" event settlement transactions.
• When a Customer Settlement transaction is created for demand-based programs, a new 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 event settlement transactions are referred to as "Combined kW Drop" event settlement transactions.

The Event Settlement Calculation 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 event settlement is created. This option is used with settlement calculations based on non-peak or consumption measurements ("kWh Avoided")

• 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").

Event settlement transactions are 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 event settlement transactions. There are three types of event settlement transactions:

• "kWh avoided" event settlement transactions are created from files containing details about 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" event settlement transactions are created from business flags.
• "kW Drop" event settlement transactions are created from files containing details about reductions in demand achieved for the duration of an event for each customer. See Processing KW Drop Filesfor more information about how "kW Drop" event settlement transactions are created from business flags.
• "Combined kW Drop" event settlement transactions are created by customer settlement transactions and contain demand reduction values derived from individual "kW Drop" event settlement transactions in the "Calculation Deferred" state that fall within the date range of the customer settlement transaction.

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

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

Event settlement transactions contain the following data:

• Program Subscription: The program subscription associated with the event for which the event 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 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 event settlement transaction has been included in a customer settlement transaction.

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

• Calculation Details:

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

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

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

  • Line Description: A single line description of the 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 event settlement calculation. These are derived from the UOM/TOU/SQI defined on the business flag type of the business flag that created the 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 event settlement transaction. This should match the interval size used for interval price sets.

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

    • For "kWh Avoided" event 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" event settlements, this is the average of the "Maximum Drop" values selected by the Event Settlement Rule - Demand Based event settlement calculation rule.

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

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

    • In the case of "kWh Avoided" event 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" event settlements, the interval values are those derived from individual "kW Drop" event settlements (based on the Event Settlement Calculation Rule configuration).
  • Maximum Drop: The largest demand reduction interval value for the event

  • Intervals: Details of the interval values and prices used in the event 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" event settlement transactions)

    • Event 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" event settlement transactions)

  • Issues: One or more messages related to the 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 an event settlement transaction is calculated for this event, the details of the event settlement transaction would be as follows:

• UOM/TOU/SQI:  kWh

• Interval Size: 01:00:00

• Consumption Saved: 29.00

• Actual Consumption: 430

• Event Settlement Amount: 12.15

• Intervals:  

System Data

Event settlement transactions are based on the following system data:

Batch Processing

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

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

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

• Recalculate Event Settlement (X1-RCEVS): Used to recalculate event settlement transactions in the "Calculated" state. This is used in the case of a rebill 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.