Description
Calculate demand-time support inside flagged peak periods, preserving an undefined zero-total 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.
Calculate demand-time support inside flagged peak periods, preserving an undefined zero-total share.
When to use this tool
Use Demand Period Coincidence Share when checking an explicit peak, ratchet or demand-allocation convention.
How to use the tool and how it works
- Enter demands, durations, inPeakPeriod. Keep parallel arrays aligned. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read totalDemandTime, coincidentDemandTime, share, defined. Inspect defined before interpreting the associated values.
Require equally long demands, durations and inPeakPeriod arrays with nonnegative demands and durations. Sum demand*duration into totalDemandTime and the flagged contributions into coincidentDemandTime. share is their ratio when the total is positive, otherwise zero with defined = false.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| demands | Demands | Required. Array of finite number; maximum items 256. |
| durations | Durations | Required. Array of finite number; maximum items 256. |
| inPeakPeriod | In Peak Period | Required. Array of boolean; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| totalDemandTime | Total Demand Time | Required. Finite number. |
| coincidentDemandTime | Coincident Demand Time | Required. Finite number. |
| share | Dimensionless selected contribution divided by the stated total; not percent. | Required. Finite number. |
| defined | Whether the stated denominator has positive support; read this before interpreting a zero placeholder. | Required. Boolean. |
{
"input": {
"demands": [
2,
3
],
"durations": [
5,
10
],
"inPeakPeriod": [
true,
false
]
},
"output": {
"totalDemandTime": 40,
"coincidentDemandTime": 10,
"share": 0.25,
"defined": true
}
}Limitations and assumptions
- This is a demand-time share, not a maximum-demand coincidence factor. Intervals, peak flags, overlap and tariff treatment are supplied rather than inferred.
- 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.