Description
share = contribution/billingPeak; allocatedCharge = charge*share.
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.
share = contribution/billingPeak; allocatedCharge = charge*share.
When to use this tool
Use Demand Charge Peak Share when checking an explicit peak, ratchet or demand-allocation convention.
How to use the tool and how it works
- Enter contribution, billingPeak, charge. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read share, allocatedCharge. Use the output convention below.
Require positive billingPeak, contribution in [0,billingPeak] and nonnegative charge. share = contribution/billingPeak; allocatedCharge = charge*share.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| contribution | This operation’s local contribution, to be combined only under the same larger-model convention. | Required. Finite number; minimum 0. |
| billingPeak | Billing Peak | Required. Finite number; strictly above 0. |
| charge | Charge | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| share | Dimensionless selected contribution divided by the stated total; not percent. | Required. Finite number. |
| allocatedCharge | Allocated Charge | Required. Finite number. |
{
"input": {
"contribution": 20,
"billingPeak": 100,
"charge": 500
},
"output": {
"share": 0.2,
"allocatedCharge": 100
}
}Limitations and assumptions
- This is a supplied proportional allocation, not a determination of cost causation or an actual customer's billing obligation. Contributions must use the same demand unit.
- 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
- Demand Charge Ratchet One Month Term
billedKw = max(currentPeak,historicalPeak*ratchetFraction); charge = billedKw*pricePerKw.
- Peak Demand Coincidence One Interval
coincidentKw = customerKw when systemPeak is true, otherwise zero; ownPeakFraction = customerKw/customerOwnPeakKw regardless of systemPeak.