Description
Compare current and historical-ratchet demand peaks and flag strict ratchet dominance.
Demand charges depend on a defined peak, interval and possible historical ratchet. A maximum demand, a demand-time share and a customer’s contribution to a system peak are distinct quantities.
Compare current and historical-ratchet demand peaks and flag strict ratchet dominance.
When to use this tool
Use Peak Ratchet Lookback Weight Term when checking an explicit peak, ratchet or demand-allocation convention.
How to use the tool and how it works
- Enter currentPeak, historicalPeak, ratchetFraction. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read ratchetPeak, billingPeak, binding. Inspect binding before interpreting the associated values.
Require nonnegative currentPeak and historicalPeak and ratchetFraction in [0,1]. ratchetPeak = historicalPeak*ratchetFraction; billingPeak is max(currentPeak,ratchetPeak); binding is true only when ratchetPeak > currentPeak.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| currentPeak | Current Peak | Required. Finite number; minimum 0. |
| historicalPeak | Historical Peak | Required. Finite number; minimum 0. |
| ratchetFraction | Ratchet Fraction Unit: 1. | Required. Finite number; minimum 0; maximum 1. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| ratchetPeak | Ratchet Peak | Required. Finite number. |
| billingPeak | Billing Peak | Required. Finite number. |
| binding | Strict historical-ratchet dominance; false when current and ratchet peaks tie. | Required. Boolean. |
{
"input": {
"currentPeak": 50,
"historicalPeak": 100,
"ratchetFraction": 0.8
},
"output": {
"ratchetPeak": 80,
"billingPeak": 80,
"binding": true
}
}Limitations and assumptions
- Peaks share a demand unit. Equality does not set binding; the historical lookback and actual tariff ratchet are not selected or verified.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Use metered interval data and the applicable tariff to determine actual billing peaks, lookbacks and allocation rules.
References
Similar or alternative tools
- Peak Demand Coincidence One Interval
coincidentKw = customerKw when systemPeak is true, otherwise zero; ownPeakFraction = customerKw/customerOwnPeakKw regardless of systemPeak.
- Demand Charge Ratchet One Month Term
billedKw = max(currentPeak,historicalPeak*ratchetFraction); charge = billedKw*pricePerKw.