Description
coincidentKw = customerKw when systemPeak is true, otherwise zero; ownPeakFraction = customerKw/customerOwnPeakKw regardless of systemPeak.
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.
coincidentKw = customerKw when systemPeak is true, otherwise zero; ownPeakFraction = customerKw/customerOwnPeakKw regardless of systemPeak.
When to use this tool
Use Peak Demand Coincidence One Interval when checking an explicit peak, ratchet or demand-allocation convention.
How to use the tool and how it works
- Enter customerKw, customerOwnPeakKw, systemPeak. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read coincidentKw, ownPeakFraction. Use the output convention below.
Require positive customerOwnPeakKw and customerKw between zero and that peak. coincidentKw = customerKw when systemPeak is true, otherwise zero; ownPeakFraction = customerKw/customerOwnPeakKw regardless of systemPeak.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| customerKw | Customer Kw | Required. Finite number; minimum 0. |
| customerOwnPeakKw | Customer Own Peak Kw | Required. Finite number; strictly above 0. |
| systemPeak | System Peak | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| coincidentKw | Coincident Kw | Required. Finite number. |
| ownPeakFraction | Own Peak Fraction | Required. Finite number. |
{
"input": {
"customerKw": 30,
"customerOwnPeakKw": 50,
"systemPeak": true
},
"output": {
"coincidentKw": 30,
"ownPeakFraction": 0.6
}
}Limitations and assumptions
- The system-peak flag is supplied and does not suppress the own-peak fraction. No interval search, billing-demand rule or contribution to actual system costs is established.
- 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 Period Coincidence Share
Calculate demand-time support inside flagged peak periods, preserving an undefined zero-total share.
- Demand Charge Peak Share
share = contribution/billingPeak; allocatedCharge = charge*share.