Tariff Analysis - Ratchet Tab

Ratchet tab on Tariff Analysis dialog

 

Ratchets are commonly used by US utility tariffs for large commercial and industrial electricity customers as a mechanism to calculate the demand charges on monthly electricity bills. They may be used to ensure that a high demand spike in one month, or season, results in a minimum billing charge for several subsequent months, even if the customer's actual usage is lower.

 

Utilities charge customers based on two main components:

 

 

A ratchet is a clause in the tariff that links the demand charge for the current month to a high demand peak from a previous month or season. A typical demand ratchet determines the Billed Demand (kW amount the customer is charged for) as the greater of:

 

  1. The actual maximum demand in the current billing month.

  2. A percentage (often 50% to 90%) of the highest maximum demand in a specified "look-back" period (e.g., the previous 11 months, or the peak summer season).

Why Utilities Use Ratchets

A utility must design its infrastructure (generators, transformers, transmission lines) to handle the maximum demand of all its customers. Even if a customer only hits a high peak once a year, the utility still has to build and maintain the capacity to serve that spike year-round. Utilities use ratchets to ensure they can recover the costs of building and maintaining a reliable electricity grid, especially the capacity required to serve peak loads. Ratchets create a strong financial incentive for large customers to avoid or manage short, excessive spikes in power usage, thereby smoothing out the load on the grid and deferring the need for costly infrastructure upgrades.

Multiple Ratchets

Multiple ratchets may be used to manage different peak concerns - like summer heat vs. year-round capacity - and they are applied sequentially to ensure the billed demand reflects the highest possible charge across all rules.

 

When a utility tariff contains multiple demand ratchets, they are applied in a chain or sequence. The goal is to compare the maximum demand from different look-back periods and different rules, and ultimately select the highest result as the customer's final Billed Demand. The mechanics are as follows:

 

  1. Ratchet 1 (e.g., Annual Ratchet): The calculation for the first ratchet is performed, comparing the current month's peak to the highest peak in the previous 11 months (or the year).1 The higher of these two values becomes the interim Billed Demand, let's call it D1.

  2. Ratchet 2 (e.g., Seasonal Ratchet): The calculation for the second ratchet is performed. This ratchet often compares a seasonal peak (like the highest summer peak) to the current month's demand. The Billed Demand from Ratchet 1 (D1) is used as the starting value or baseline for this comparison.

     

    Final Billed Demand = Greater of (D1 OR a percentage of the highest kW peak during the last peak season).

 

Essentially, the output of the first ratchet is fed into the second, and the output of the second is fed into the third (if one exists). This layering guarantees the customer pays a demand charge based on the worst-case scenario (highest demand spike) as defined by any of the tariff's ratchet rules.

 

In DesignBuilder, if multiple ratchets occur in the same tariff, they can be “chained” together using the Baseline source variable replaced with the Ratchet variable name of the previous Ratchet.

Ratchet

Ratchet variable name

This entry defines the name of the ratchet and the variable that stores the result of this ratchet. The ratchet variable name should be used wherever the ratchet should be applied and is often the source variable for Simple or Block charge objects.

Baseline source variable

The name of the variable used as the baseline value. When the ratcheted value exceeds the baseline value for a month the ratcheted value is used but when the baseline value is greater than the ratcheted value the baseline value is used. Usually the electric demand charge is used. The baseline source variable can be the results of another ratchet object. This allows utility tariffs that have multiple ratchets to be modelled.

Adjustment source variable

This field defines the variable that the ratchet is calculated from. It is often but not always the same as the baseline source variable. The ratcheting calculations using offset and multiplier are using the values from the adjustment source variable. See the bottom of this section for how ratchet works.

Season from

This is the name of the season that is being examined. The maximum value for all of the months in the named season is what is used with the multiplier and offset. This is most commonly Summer or Annual. When Monthly is used, the adjustment source variable is used directly for all months.

 

The choices are:

 

Season to

This is the name of the season when the ratchet would apply. This is most commonly Winter. The ratchet only is applied to the months in the named season. The resulting variable for months not in the Season To selection will contain the values as appear in the baseline source variable. The choices are:

 

Multiplier value or variable name

Often the ratchet has a clause such as “the current month demand or 90% of the summer month demand”. For this case a value of 0.9 would be entered here as the multiplier. This value may be given as one if no multiplier is needed. This can also be a variable name, which should be defined on User variables tab.

Offset value or variable name

A less common strategy is to say that the ratchet must be all demand greater than a value, in this case an offset that is added to the demand may be entered here. If entered, it is common for the offset value to be negative representing that the demand be reduced. The value can be zero if not offset is needed in the ratchet. This can also be a variable name, which should be defined on User variables tab.

Detailed step taken for ratchet calculation

 

 

For a simple typical case using totalDemand for both “Baseline source variable” and “Adjustment source variable”, please see the example at the top of this page.