The Gold Standard of Utilities | Calculating Load Factor Without Mixing Energy and Peak-Demand Windows

State the start and end timestamps, meter boundary, energy total and demand series. The numerator and denominator must describe the same system and interval.

Write the comparison as a ledger: object, quantity, unit, boundary, time window, protocol and evidence. Mark every input as observed, stipulated, fitted or assumed. This catches a basis change before it reaches the conclusion.

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘define the same reporting interval’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Next chapter

Energy accumulates power over time and is measured here in kilowatt-hours. Load is a rate of energy use measured in kilowatts. The units signal which arithmetic is permitted.

Draw the mechanism before interpreting the number. Put the stages in order, name where each observation is made and identify a competing explanation. The arrows matter only when their conditions remain visible.

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘separate energy from power’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

Divide 36,000 kWh by 720 hours to obtain an average load of 50 kW. Using 30 days without converting to hours would leave the unit and value wrong.

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 stronger when both checks do not recycle the same hidden assumption.

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘derive average load from energy and time’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

Peak demand depends on how the meter averages or records power, such as over 15 or 30 minutes. A momentary transient, interval maximum and equipment nameplate are different quantities.

Keep the comparison fair. Hold the population, material, interval, protocol and unit constant before assigning a difference to the mechanism of interest. A changed condition is a changed context, even when the column heading looks familiar.

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘define the peak demand interval’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

The aligned calculation is 50 kW divided by 125 kW, giving 0.40. Report 40% for this facility, 30-day month and 30-minute demand definition.

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

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘work the 36,000 kwh and 125 kw example’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

Average load cannot exceed the true maximum over the same complete interval, so an aligned load factor normally lies from zero to one. A result above one is a reconciliation warning.

Preserve order and identity. Equal totals can hide different mechanisms when observations occur in another sequence or come from different people, specimens, devices or sessions. Keep identities until the reader question no longer depends on them.

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘check the dimensionless ratio and its bounds’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

Connected load sums assigned equipment capacities. It can greatly exceed the measured coincident peak and cannot replace that peak in this statistic.

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

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘do not substitute connected load for peak demand’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

A five-minute demand series can show a higher maximum than a 30-minute averaged series. Compare peaks only after matching the integration or averaging rule.

State the boundary of inference beside the answer. Name the system, representation and interval to which the result applies, then name one tempting stronger claim it cannot establish.

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘keep demand-interval length visible’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

A 28-day February and a 31-day month have different hours. Use actual timestamps, daylight-saving treatment where relevant and the meter’s interval convention.

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 generic caveat list.

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘match calendar duration to the billing record’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

Estimated reads, outages and gaps affect both accumulated energy and the observed maximum. Mark imputation and test whether a missing interval could contain the peak.

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

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘handle missing intervals and estimated energy’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

Cooling, heating, production schedules and occupancy can change the curve. A month-to-month load-factor change is descriptive until those mechanisms are checked.

Write the comparison as a ledger: object, quantity, unit, boundary, time window, protocol and evidence. Mark every input as observed, stipulated, fitted or assumed. This catches a basis change before it reaches the conclusion.

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘compare months without hiding season or operations’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

A building meter, campus incomer and distribution feeder aggregate different loads. One boundary’s average and another boundary’s peak cannot form a coherent ratio.

Draw the mechanism before interpreting the number. Put the stages in order, name where each observation is made and identify a competing explanation. The arrows matter only when their conditions remain visible.

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘distinguish facility and feeder boundaries’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

Move a fictional 125 kW half-hour event into an unobserved gap. The known-data load factor is no longer definitive because the denominator may be understated.

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 stronger when both checks do not recycle the same hidden assumption.

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘test a shifted short peak’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

Spread the same 36,000 kWh more evenly so the maximum becomes 100 kW. Average remains 50 kW and load factor rises to 50%, illustrating a shape change without an energy change.

Keep the comparison fair. Hold the population, material, interval, protocol and unit constant before assigning a difference to the mechanism of interest. A changed condition is a changed context, even when the column heading looks familiar.

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘test flatter operation with unchanged energy’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

A high load factor can reflect steady useful service, inflexible operation or persistent waste. Efficiency needs an output or service basis as well as energy evidence.

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

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘avoid treating high load factor as automatic efficiency’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

Demand charges use jurisdiction- and tariff-specific rules that can involve ratchets, seasons or contracted capacity. Calculate the engineering statistic before applying billing rules.

Preserve order and identity. Equal totals can hide different mechanisms when observations occur in another sequence or come from different people, specimens, devices or sessions. Keep identities until the reader question no longer depends on them.

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘keep tariffs separate from engineering meaning’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

A single peak and total energy hide when loads overlap. Inspect the time series, operating log and controllable versus essential loads before proposing demand changes.

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

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘use demand profiles before recommending action’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

Meter rounding, clock alignment and interval boundaries can change the reported maximum. Recalculate nearby cases and identify whether the conclusion is stable.

State the boundary of inference beside the answer. Name the system, representation and interval to which the result applies, then name one tempting stronger claim it cannot establish.

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘carry meter resolution and timing uncertainty’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

Peak can fall while energy stays equal or rises, and energy can fall while a short peak remains. Report both quantities and the time profile.

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 generic caveat list.

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘repair the claim that lower peak always means lower use’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

Save meter IDs, boundary diagram, timestamps, interval length, raw energy register, demand series, missing-data flags, time-zone rule, calculation and tariff version if used.

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

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘build a reproducible load-factor ledger’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

Is load factor the same as capacity factor? No. Load factor compares a load profile's average with its peak; capacity factor compares actual generation with possible generation at rated capacity.

Can connected load be used as the peak? Only if the purpose explicitly calls for that conservative inventory, in which case it should not be mislabeled as measured peak demand.

Does a higher load factor prove lower cost? No. Cost depends on the tariff and total energy as well as demand.

Write the comparison as a ledger: object, quantity, unit, boundary, time window, protocol and evidence. Mark every input as observed, stipulated, fitted or assumed. This catches a basis change before it reaches the conclusion.

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘answer focused reader questions’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Next chapter

Use the EIA definitions for the aligned ratio, then follow the linked Utilities branches for connected load, firm capacity and reliability indices.

Draw the mechanism before interpreting the number. Put the stages in order, name where each observation is made and identify a competing explanation. The arrows matter only when their conditions remain visible.

Apply the rule to the central fictional case, preserve unrounded inputs and label the result with its protocol. Then write one plausible alternative explanation and the observation that would distinguish it.

For Utilities, use seven fields: target question, object or population, unit, boundary, protocol, result and decision limit. Complete every field before writing a conclusion. For ‘continue through verified utility routes’, a plausible value can otherwise hide a changed condition or undocumented processing step.

Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, say what stays comparable and name the stronger conclusion that still does not follow.

Before closing the chapter, write a two-line result. The first line states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false. This turns a caveat into a usable check.

Contents · Previous chapter · Return to Utilities