The Gold Standard of Utilities | Separating Service Continuity from Supply Adequacy

Ask whether the claim concerns sufficient resources, secure operation, customer interruptions, restoration or resilience. Each requires a distinct record.

Write an evidence ledger before calculating: target quantity, object, unit, boundary, observation rule, transformation and decision limit. Mark every input as observed, stipulated, fitted or assumed.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “define the reader question”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Next chapter

Adequacy compares qualified supply-side and demand-side resources with aggregate demand under a defined boundary. Continuity records whether service remained available to defined customers.

Draw the mechanism in order. Separate the underlying state, the measurement, the mathematical summary and the claim. Then name one rival explanation and the additional observation that could distinguish it.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “separate the two target quantities”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

Record interval, demand, resource contribution, imports, constraints, contingency state, interrupted customers, start time and restoration time.

Keep the comparison fair by holding the specimen, interval, protocol and denominator constant. If one changes, state that the new number answers a different question even when the label looks familiar.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “name the observation rule”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

Name whether the boundary is generation, balancing area, distribution feeder or customer service point. The answer can change when the boundary changes.

Use two checks that can fail differently: reconstruct a total, test a limiting case, repeat the result from definitions or inspect a shared control. Two calculations that reuse one assumption are only one check.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “protect the denominator and boundary”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

Create two fictional hours: A has +5 MW aggregate margin and a local feeder outage; B has a 5 MW internal gap covered by an 8 MW deliverable import.

Separate measurement from decision. A correct number can still be too local, uncertain or method-dependent for the intended action. Report it with its conditions and say what stronger evidence would be needed.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “build the fictional evidence ledger”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

Hour A is adequate on the stated aggregate balance but has a continuity event. Hour B is adequate on the wider deliverable-resource balance and has no recorded interruption.

Preserve identity and order. Equal totals can hide different mechanisms when records come from different specimens, resources, homes or viewing geometries. Aggregate only after the question no longer depends on that identity.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “work the central calculation”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

Megawatts describe power; customer interruptions and customer-minutes describe service experience. Do not combine them into one arithmetic score without an explicit decision model.

Run a changed-context transfer check. Change one consequential condition while holding the remaining basis fixed, calculate again and explain why the result moves or stays stable.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “check units before interpretation”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

A resource contribution needs interval, accreditation, availability and deliverability. A continuity event needs customer and restoration definitions.

Put the boundary of inference beside the answer. Name the system, representation and interval to which the result applies, then name the nearest tempting conclusion the evidence does not establish.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “keep method settings visible”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

Check whether the apparent margin survives the binding network constraint and whether outage logs reconcile with meter or operations records.

Use uncertainty as structure. Vary the input most capable of changing the conclusion over a defensible range and show whether the ranking or interpretation changes.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “locate the usable range”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

Aggregate adequacy can hide local bottlenecks. Conversely, a local outage does not prove that the total system lacked energy or capacity.

Finish with a reproducible evidence package: source records, definitions, exclusions, calculations, validation result and revision rule.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “recognise saturation and censoring”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

Reconstruct the supply-demand balance and independently reconstruct customer-minutes from the event ledger. Agreement within one ledger cannot validate the other dimension.

Write an evidence ledger before calculating: target quantity, object, unit, boundary, observation rule, transformation and decision limit. Mark every input as observed, stipulated, fitted or assumed.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “use controls that can fail differently”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

Carry demand error, deratings, import limits, unreported interruptions and restoration-time uncertainty separately.

Draw the mechanism in order. Separate the underlying state, the measurement, the mathematical summary and the claim. Then name one rival explanation and the additional observation that could distinguish it.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “carry uncertainty into the claim”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

Continuity can fail through protection, equipment, vegetation, control or network faults even when generation is ample.

Keep the comparison fair by holding the specimen, interval, protocol and denominator constant. If one changes, state that the new number answers a different question even when the label looks familiar.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “separate mechanism from appearance”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

Compare like intervals and populations. An annual adequacy study and one realised feeder event should be connected cautiously.

Use two checks that can fail differently: reconstruct a total, test a limiting case, repeat the result from definitions or inspect a shared control. Two calculations that reuse one assumption are only one check.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “compare like with like”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

An interruption during high demand may coincide with tight adequacy without being caused by it. Use event evidence and network topology before assigning cause.

Separate measurement from decision. A correct number can still be too local, uncertain or method-dependent for the intended action. Report it with its conditions and say what stronger evidence would be needed.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “test a rival explanation”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

Remove the import in Hour B while keeping internal resources and demand fixed. The wider adequacy margin becomes -5 MW, but the customer outcome still depends on response actions.

Preserve identity and order. Equal totals can hide different mechanisms when records come from different specimens, resources, homes or viewing geometries. Aggregate only after the question no longer depends on that identity.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “change one consequential condition”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

A stipulated 5 MW demand response restores balance exactly. If it is unavailable, controlled interruption may occur, but the arithmetic alone does not identify which customers.

Run a changed-context transfer check. Change one consequential condition while holding the remaining basis fixed, calculate again and explain why the result moves or stays stable.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “recalculate the changed case”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

The two-axis record establishes the stated resource balance and the separately observed customer outcome for each interval.

Put the boundary of inference beside the answer. Name the system, representation and interval to which the result applies, then name the nearest tempting conclusion the evidence does not establish.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “state what the result establishes”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

It does not establish long-term reliability, causal responsibility, regulatory compliance or the welfare cost of an interruption.

Use uncertainty as structure. Vary the input most capable of changing the conclusion over a defensible range and show whether the ranking or interpretation changes.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “state what it cannot establish”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

Replace ‘no blackout means the system had adequate capacity’ with the documented resource boundary, margin and continuity record.

Finish with a reproducible evidence package: source records, definitions, exclusions, calculations, validation result and revision rule.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “repair an overconfident sentence”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

Can an adequate system have outages? Yes. Local or operational failures can interrupt service.

Does a capacity shortfall guarantee an outage? No. Imports, demand response and operating actions may change the outcome.

Are SAIDI and adequacy margins interchangeable? No. They use different objects and units.

Write an evidence ledger before calculating: target quantity, object, unit, boundary, observation rule, transformation and decision limit. Mark every input as observed, stipulated, fitted or assumed.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “answer focused reader questions”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Next chapter

Use NERC and FERC definitions, then follow the firm-capacity branch for resource accounting and the SAIFI–SAIDI–CAIDI branch for interruption arithmetic.

Draw the mechanism in order. Separate the underlying state, the measurement, the mathematical summary and the claim. Then name one rival explanation and the additional observation that could distinguish it.

Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.

For Utilities, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “continue through verified routes”, a plausible number can otherwise hide a changed definition or undocumented condition.

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

Close with two lines. The first 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.

Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.

Contents · Previous chapter · Return to Utilities