The Gold Standard of Utilities | Separating Connected Load from Coincident Peak Demand

Name the panel, building, campus or utility system and the included voltage level. Loads outside the boundary cannot appear in one numerator and disappear from its denominator.

Write the claim as a small ledger: object, quantity, unit, boundary, time window, method and evidence. Mark every input as observed, stipulated, estimated or assumed. This makes a change in basis visible before it reaches the arithmetic.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “set the electrical boundary”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Next chapter

Record each device, quantity, rated input, standby state and source of the rating. Avoid mixing thermal output, motor shaft power and electrical input.

Draw the mechanism before interpreting the number. Show the stages in order, name the point where each observation is made and identify at least one competing explanation. A diagram helps only when its arrows carry stated conditions.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “build the connected-load inventory”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

A one-second maximum and a fifteen-minute average answer different questions. State meter integration, clock alignment and missing intervals.

Use two checks that fail differently. Reconstruct an input from outputs, calculate a limiting case, inspect a control, or repeat the result from the definitions. Agreement is strongest when the checks do not recycle the same hidden assumption.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “define the demand interval”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

The connected total is 12.6 kW and the measured fifteen-minute maximum is 7.4 kW. Their difference is not a guaranteed spare 5.2 kW.

Keep the comparison fair. Hold the specimen, destination, interval, protocol and unit constant before assigning a difference to the mechanism of interest. If a condition changes, report a changed context rather than quietly treating the rows as equivalent.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “work the fictional 12.6 and 7.4 kw example”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

Energy accumulates power over time and is billed in kWh; demand is a rate or interval average in kW. Equal monthly energy can accompany different peaks.

Separate measurement from decision. A value may be correctly calculated yet too local, uncertain or method-dependent for the intended action. Report the result, its conditions and the observation that would be needed before a stronger decision.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “keep energy separate from demand”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

A device can draw below or above a nominal value depending on load, controls and starting conditions. Treat nameplate data according to its documented purpose.

Treat missing and excluded observations as evidence. Record why they are absent, which denominator they leave and whether absence could follow the process being studied. An explicit incomplete record is safer than a clean table made by silent deletion.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “distinguish nameplate from measured input”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

Single-phase and three-phase systems require current, voltage, phase balance and power-factor evidence. Adding kW alone cannot check every conductor or transformer condition.

Preserve order and identity. Equal totals can hide different mechanisms when events occur in another sequence or belong to different objects. Keep timestamps, sample identities and processing stages until the reader question no longer depends on them.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “preserve phases and power factor”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

Refrigeration, pumps and heaters cycle. Coincidence depends on control logic, occupancy, weather and process schedules rather than a timeless percentage.

Test a deliberately changed case. Change one assumption while holding the others fixed, calculate again and explain why the conclusion moves or remains stable. Transfer is shown when the reasoning survives the new context.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “handle cycling and duty schedules”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

Each device can have its own maximum at a different time. The sum of individual maxima usually differs from the maximum of their summed interval series.

State the boundary of inference in the answer. Name the system, representation and interval to which the result applies, then name one tempting stronger claim it cannot establish. The limit belongs beside the result rather than in a distant disclaimer.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “recognise coincident and non-coincident peaks”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

State whether the factor is sum of individual peaks divided by group peak, connected load divided by peak, or another convention. Never carry a bare factor between projects.

Use uncertainty as structure. Identify the input most capable of changing the conclusion, vary it over a defensible range and show whether the practical choice changes. One linked sensitivity check is more useful than a long generic caveat list.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “use diversity factors only with their definitions”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

A building peak may not coincide with the feeder or grid peak. Re-aggregate timestamped series before making system claims.

Finish with an evidence package: source records, definitions, exclusions, software or instrument version, calculations, validation result and decision rule. A later reviewer should be able to reproduce the result and see what would cause revision.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “change the aggregation boundary”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

Cooling peaks, heating peaks, school terms and production campaigns can shift coincidence. A short study window may miss the governing mode.

Write the claim as a small ledger: object, quantity, unit, boundary, time window, method and evidence. Mark every input as observed, stipulated, estimated or assumed. This makes a change in basis visible before it reaches the arithmetic.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “compare seasons and operating modes”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

Emergency operation, cleaning, restart after outage or failure of controls can create credible combinations absent from ordinary data. Analyse them explicitly.

Draw the mechanism before interpreting the number. Show the stages in order, name the point where each observation is made and identify at least one competing explanation. A diagram helps only when its arrows carry stated conditions.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “protect rare but credible operating states”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

Utilities can use monthly peaks, time-of-use windows or ratchets. Read the applicable tariff rather than inferring cost from technical peak alone.

Use two checks that fail differently. Reconstruct an input from outputs, calculate a limiting case, inspect a control, or repeat the result from the definitions. Agreement is strongest when the checks do not recycle the same hidden assumption.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “treat demand charges as tariff rules”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

Interval averaging can smooth motor starts and fast spikes. Use fit-for-purpose high-resolution data when equipment performance depends on them.

Keep the comparison fair. Hold the specimen, destination, interval, protocol and unit constant before assigning a difference to the mechanism of interest. If a condition changes, report a changed context rather than quietly treating the rows as equivalent.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “use interval data without hiding shorter transients”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

A past maximum is evidence, not a forecast. Growth, efficiency, schedules, weather and uncertainty must be modelled for future planning.

Separate measurement from decision. A value may be correctly calculated yet too local, uncertain or method-dependent for the intended action. Report the result, its conditions and the observation that would be needed before a stronger decision.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “separate historical peak from forecast demand”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

Vehicle charging, heat pumps or process equipment can change both connected inventory and coincidence. Add scenarios with stated adoption and controls.

Treat missing and excluded observations as evidence. Record why they are absent, which denominator they leave and whether absence could follow the process being studied. An explicit incomplete record is safer than a clean table made by silent deletion.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “account for new loads and electrification”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

Protection, conductor sizing and code compliance use prescribed methods and conditions. A low measured peak cannot waive those requirements.

Preserve order and identity. Equal totals can hide different mechanisms when events occur in another sequence or belong to different objects. Keep timestamps, sample identities and processing stages until the reader question no longer depends on them.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “do not substitute peak demand for safety design”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

Capacity margin can support resilience, future loads and uncertain peaks. Its value must be judged against the system purpose and cost.

Test a deliberately changed case. Change one assumption while holding the others fixed, calculate again and explain why the conclusion moves or remains stable. Transfer is shown when the reasoning survives the new context.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “repair the claim that unused capacity is waste”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

Save inventory, diagrams, meter IDs, interval definition, time zone, gaps, operating calendar, transformations, peak timestamps and scenario assumptions.

State the boundary of inference in the answer. Name the system, representation and interval to which the result applies, then name one tempting stronger claim it cannot establish. The limit belongs beside the result rather than in a distant disclaimer.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “build a reproducible demand study”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

If the peak is schedule-driven, controls may help; if boundary capacity is insufficient under credible states, physical upgrades may be required. Verify after change.

Use uncertainty as structure. Identify the input most capable of changing the conclusion, vary it over a defensible range and show whether the practical choice changes. One linked sensitivity check is more useful than a long generic caveat list.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “choose a capacity action from evidence”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Next chapter

Use official tariff and metering definitions, then follow the linked Utilities branches for firm capacity, reliability and measurement resolution.

Finish with an evidence package: source records, definitions, exclusions, software or instrument version, calculations, validation result and decision rule. A later reviewer should be able to reproduce the result and see what would cause revision.

For the chapter record, apply the rule to the central fictional case, preserve the unrounded inputs and label the result with its method. Then write one plausible alternative explanation and the single observation that would separate it from the preferred account.

For Utilities, make the chapter test concrete with six fields: source record, transformation or operating state, observation point, result, competing explanation and decision limit. Fill every field before writing the conclusion. If a field cannot be completed, preserve it as an open item. This is especially useful for “continue through verified utility routes”, because a plausible final value can otherwise hide a changed boundary or undocumented intermediate step.

Change one condition that matters to this mechanism while keeping the object and reporting basis fixed. Recalculate or re-inspect the evidence, state what remains comparable, and name the stronger conclusion that still does not follow.

Contents · Previous chapter · Return to Utilities