Coincident Peak and Individual SP Demand

Interval Data Retrieval Parameters

This rule can be configured to use specific data either directly from a specific device and measuring component on the service point or calculated from more than one devices and/or measuring components on the service point. Each type of data is referred to as a "channel" of data. For example, a service point with solar panels might have separate channels for "Consumed" and "Generated" usage, and the rule could be configured to use data from either or based on calculations involving both.

Parameters used to retrieve interval data for this rule include:

• Check Missing Intervals: A flag that indicates if the rule should check for missing intervals during the calculation period.

• No Meter Condition: The measurement condition assigned to intervals inserted to fill gaps during periods in which when no meter is installed. If not set, the measurement condition defaults to "No Read - System" (100000).

• SP Device Filter: An algorithm used to filter the service point device configuration that will be processed by the rule.  

• Common UOM: The unit of measure that is common among the multiple channels of data used by the rule, if applicable

• Common Interval Size: The interval size used to align service point data of different interval sizes. For instance, if a service point has channels measuring data in both 1-hour and 15-minute intervals, setting this to 01:00:00 (1 hour) would scale the 15-minute data to hourly intervals.

• Channels: A list of the data channels measured at the service point. Each should be assigned a variable name and the appropriate UOM, TOU, and SQI.

• Aggregation Method: The method by which data from multiple channels will be aggregated. Channels can be combined using a simple formula or using a conditional formula. 

To define a single channel for the rule to use, configure the "Vector 1 (IV1)" variable in the Channels section and reference that variable in a simple formula.

To configure the rule to use multiple channels, define each as a variable in the Channels section and configure either a simple or conditional formula to perform any needed evaluations or calculations on the channels.

Defining Formula Operands

Operands used in both simple and conditional formulas are defined in the Operand Lookup (D1-CoincidentPeakOperandLookup) extendable lookup. Operands used to represent channels should use the values in parentheses in the Variables drop-down list in the Channels section. For instance, the operand for "Vector 1 (IV1)" should be "IV1", the operand for "Vector 2 (IV2)" should be "IV2", and so on. 

Operands can also be simple formulas based on the variables defined in the Variables drop-down list in the Channels section. For instance, a simple formula in which the values from Vector 1 are subtracted from the values in Vector2 could be defined as "IV2 - IV1".  

Calculation Modes

This rule has two main modes: calculating demand for individual service points on a usage subscription (Individual SP Demand), or calculating the coincident peak among all of the service points on a usage subscription (Coincident Peak). The coincident peak calculation can be performed on either all readings, or those designated as "on-peak" or "off-peak" via time of use mapping using the Coincident On-Peak  or Coincident Off-Peak function. See Defining Time of Use Mapping Options for more information about time of use mapping.

Individual SP Demand

The "Individual SP Demand" Calculate Function identifies the peak demand for each service point on a usage subscription.

For example, the table below lists sample interval data for three service points belonging to single usage subscription for a 12 hour calculation period. This rule would identify the highest value (peak) for each service point within the calculation period (indicated in bold).

This rule would return the following values in the usage transaction service quantities list, which represent the peak values for each service point during the calculation period:

Coincident Peak / Coincident On-Peak / Coincident Off-Peak 

The "Coincident Peak” (or “Coincident On-Peak” or “Coincident Off-Peak") Calculate Function identifies the coincident peak demand for all of the service points on the usage subscription and the demand values for each service point at the coincident peak. The "coincident peak" is the time at which the combined values of multiple service points is the highest (which is not necessarily the peak for each individual service point). 

The data used in the calculation is based on the specific Calculate Function selected:

• Coincident Peak: Evaluates all measurements matching the configured unit of measure

• Coincident On-Peak: Evaluates measurements matching the configured unit of measure that falls with the "on-peak" TOU period defined in the Results section based on a specified TOU Map Template.

• Coincident Off-Peak: Evaluates measurements matching the configured unit of measure that falls with the "off-peak" TOU period defined in the Results section based on a specified TOU Map Template.

For example, the table below lists sample interval data for three service points belonging to single usage subscription for a 12 hour calculation period. This rule would identify the highest total for all of the service points, as well as the individual values for each service point at the time of the coincident peak within the calculation period (indicated in bold).

This rule would return the following values in the usage transaction service quantities list, which represent the total at the coincident peak and the peak values for each service point at the coincident peak during the calculation period:

Notes and Examples

Notes and Recommendations

• When using the "Coincident On Peak" or "Coincident Off Peak" Calculate Function, you must specify a TOU map template in the On Peak Off Peak Schedule drop-down list in the Calculation Details section, and specify the appropriate time of use period (On-Peak or Off-Peak, respectively) in the TOU field in the Results section.

• A recommended practice is to configure a Service Quantity Identifier (SQI) to uniquely identify coincident peak data and specify it in the SQI field in the Results section.

• Additional detail on the logic of this rule can be found in the Detailed Description of the D1-CALDEMAND Algorithm Type.

For help with the meaning of specific configuration fields, refer to the embedded help on the screen when adding or editing the rule.

Business Object

D1-CoincidentPeakSPDemandRule

Example Scenarios

Below are some example scenarios that can be achieved based on configuration of this rule.

Scenario 1: Calculate demand for individual service points (similar to the example above, based on a single channel)

• Interval Data Retrieval Parameters:

  • Check Missing Intervals: Yes

  • No Meter Condition: No Read - System

  • Common UOM: Kilowatt-Hour

  • Common Interval Size: 01:00:00

  • Channels:

    • Variable 1:

      • Variable Name: Variable 1 (IV1)

      • UOM: Kilowatt-Hour

  • Aggregation Method:

    • Formula Source: Simple Vector Formula

    • Simple Vector Formula: IV1

• Calculation Details:

  • Calculate Function: Individual SP Demand

• Results:

  • UOM: Kilowatt

  • TOU:

  • SQI:

  • Common Interval Size: 01:00:00

Scenario 2: Calculate demand for individual service points (based on two channels)

In this scenario, the service point has two channels, one for consumed energy, and one for generated energy (from a solar panel). If the consumed value is greater than the generated value, subtract the generated value from the consumed value. If the generated value is greater than the consumed value, use zero (0). 

• Interval Data Retrieval Parameters:

  • Check Missing Intervals: Yes

  • No Meter Condition: No Read - System

  • Common UOM: Kilowatt-Hour

  • Common Interval Size: 01:00:00

  • Channels:

    • Variable 1:

      • Variable Name: Variable 1 (IV1)

      • UOM: Kilowatt-Hour

      • TOU: 

      • SQI: Consumed

    • Variable 2:

      • Variable Name: Variable 2 (IV2)

      • UOM: Kilowatt-Hour

      • TOU: 

      • SQI: Generated

  • Aggregation Method:

    • Formula Source: Conditional Vector Formula

    • Conditional Vector Formula:

      • Sequence: 10

      • Left Operand: IV1

      • Criteria Operator: >

      • Right Operand: IV2

      • True Action: Apply True Formula

      • True Formula: IV1-IV2

      • False Action: Apply False Formula

      • False Formula: 0

• Calculation Details:

  • Calculate Function: Individual SP Demand

• Results:

  • UOM: Kilowatt

  • TOU:

  • SQI:

Scenario 3: Coincident Peak (similar to the example above, based a single channel)

• Interval Data Retrieval Parameters:

  • Check Missing Intervals: Yes

  • No Meter Condition: No Read - System

  • Common UOM: Kilowatt-Hour

  • Common Interval Size: 01:00:00

  • Channels:

    • Variable 1:

      • Variable Name: Variable 1 (IV1)

      • UOM: Kilowatt-Hour

  • Aggregation Method:

    • Formula Source: Simple Vector Formula

    • Simple Vector Formula: IV1

• Calculation Details:

  • Calculate Function: Coincident Peak

• Results:

  • UOM: Kilowatt

  • TOU:

  • SQI: Coincident Peak

Scenario 4: Coincident On-Peak (based on a single channel)

• Interval Data Retrieval Parameters:

  • Check Missing Intervals: Yes

  • No Meter Condition: No Read - System

  • Common UOM: Kilowatt-Hour

  • Common Interval Size: 01:00:00

  • Channels:

    • Variable 1:

      • Variable Name: Variable 1 (IV1)

      • UOM: Kilowatt-Hour

  • Aggregation Method:

    • Formula Source: Simple Vector Formula

    • Simple Vector Formula: IV1

• Calculation Details:

  • Calculate Function: Coincident On Peak

  •  On Peak Off Peak Schedule: <TOU map template>

• Results:

  • UOM: Kilowatt

  • TOU: On Peak

  • SQI: Coincident On Peak