Reliability has several meanings
This lab focuses on bulk-system resource adequacy: whether the system has enough deliverable capacity and energy to serve firm demand over time, allowing for uncertainty.
Resource adequacy
Planning for enough generation, storage, demand response, and imports to meet demand across plausible conditions.
Modeled hereOperating reliability
Keeping frequency, voltage, reserves, and transmission secure in real time after credible disturbances.
Not solved hereDistribution reliability
Customer interruption frequency and duration on local wires, often summarized with SAIDI and SAIFI.
Not solved hereResource adequacy is an hourly balance repeated across many plausible years
A planning reserve margin compares a single peak-demand number with an adjusted capacity total. It is useful for screening, but it cannot see whether solar output fades before the peak, a battery empties during a long event, wind is correlated across regions, or several generators fail together. Probabilistic adequacy replaces that single comparison with thousands of chronological hourly balances.
The model records every negative margin, then aggregates the same events in several ways. That is why LOLE, LOLH, LOLEV, and EUE are complementary rather than competing answers.
A shortfall occurs when available supply cannot cover firm demand
For each hour, the model compares firm demand with the supply that is actually available after renewable profiles, outages, derates, import limits, demand response, and storage dispatch. Any remaining gap is unserved energy.
One event can create several different metrics
Width, height, and area say different things
The horizontal span tells you when and how long the deficit lasts. The vertical separation tells you how deep the deficit is. Their hourly sum is EUE. A thin, deep event and a broad, shallow event can have the same EUE but different operating consequences.
Five hourly deficits become 39 GWh
The plotted deficits are 6, 10, 12, 9, and 2 GW. With one-hour intervals, EUE is (6 + 10 + 12 + 9 + 2) GW × 1 h = 39 GWh. Because all five hours occur on one calendar day and form one uninterrupted episode, that case-year contributes 1 LOLE day, 5 LOLH hours, and 1 LOLEV event.
Adequacy shortfall is not a customer-outage forecast
The red region is system-level energy not served before emergency actions. It does not identify which customers would be interrupted, for how long, or whether transmission and distribution equipment can deliver available generation.
One historical year is not enough
Rare-event planning needs many chronological case-years. This lab pairs each weather chronology with independent year-long equipment failure and repair sequences. Every case preserves all 8,760 hours so storage, event duration, and seasonal patterns remain meaningful.
Weather years
Different synchronized hourly patterns of demand, solar, and wind. They represent the finite range of weather chronologies in the input library.
Outage draws
Different random sequences of equipment failures and repairs applied to each weather year. More draws reduce Monte Carlo sampling noise; they do not create new weather.
Hour 4 depends on what happened in hours 1–3
A chronological model carries state forward. A failed unit remains unavailable until it repairs. Storage state of charge rises when it charges and falls when it discharges. Demand-response energy budgets reset on their stated schedule. Shuffling the same 8,760 hours could therefore change the answer.
Weather variables must stay synchronized
A hot evening may combine high load, weak wind, reduced thermal output, and constrained imports. Sampling each input independently can create impossible combinations or erase genuine compound stress. The California ensemble keeps load, solar, and wind aligned within each weather chronology.
Case-years do not automatically have equal meaning
Within this lab, each weather year receives the same number of outage draws and weather years are equally weighted. A production study may use explicit weather weights, climate-adjusted futures, multiple load forecasts, or scenario probabilities. The reported mean must reflect those weights.
The answer is conditional on the modeled world
“Expected” means expected across the study’s weather records, outage processes, dispatch rules, and input assumptions. It does not mean every uncertainty in the real grid has been sampled. Fuel constraints, transmission topology, hydro chronology, and emergency procedures may require separate modeling.
Demand shape and supply weather are separate choices
A data center may draw nearly constant power even though the surrounding grid has a strongly seasonal and daily load shape. Applying California system demand to that facility would answer the wrong question. In the lab, choose Constant 24/7 or upload the facility’s own 8,760-hour load profile, then independently choose the 25-year supply-weather set.
What stays fixed
The facility load shape is repeated across every selected supply-weather year. A flat 100 MW case remains 100 MW in every hour before the optional annual forecast multiplier and cooling uplift. The model does not reshape it into California system demand.
What still changes
Solar and wind output, weather-linked thermal and import stress, hydro uncertainty, common-mode events, and equipment failures still vary. This tests the same customer demand against many plausible bulk-supply conditions.
Each metric answers a different question
Let Ui,h be unserved demand in hour h of simulated case-year i. An indicator 1(·) equals one when its condition is true and zero otherwise.
On how many calendar days does at least one shortfall hour occur, on average?
For how many hourly intervals is firm demand not fully served, on average?
How many separate contiguous shortfall episodes occur, on average?
How much firm energy is not served, capturing both depth and duration?
What share of annual demand energy is expected to be unserved?
What fraction of simulated cases has a shortfall in a particular hour?
What fraction of simulated years contains at least one shortfall hour?
| Metric | Occurrence? | Duration? | Depth? | Common mistake |
|---|---|---|---|---|
| LOLE | Yes, by day | Not within a day | No | Treating 0.1 day/year as 2.4 hours/year |
| LOLH | Yes, by hour | Yes | No | Calling it LOLE without stating hours |
| LOLEV | Yes, by event | No | No | Assuming every event lasts one hour or one day |
| EUE | Indirectly | Yes | Yes | Ignoring a few very severe tail cases |
| Annual risk | Yes, by year | No | No | Equating it with LOLE days/year |
Suppose 1,000 simulated case-years contain 100 shortfall-days, 180 shortfall-hours, 72 contiguous events, and 12,000 MWh of unserved energy. Sixty of those case-years contain at least one event.
None of these values can be converted into another without the underlying event chronology and depths.
A reliability estimate needs an uncertainty statement
Shortfalls are deliberately rare in a well-planned grid, so estimates can move when more outage draws are added. A point estimate without its sample count, weather basis, and confidence interval can look more precise than it is.
The interval—not the dot—determines the evidence category
Compare the whole interval with the criterion
If the upper bound is below 0.1, the sampled evidence supports “below target.” If the lower bound is above 0.1, it supports “above target.” If the interval crosses 0.1, the honest conclusion is sampling-uncertain, even when the mean is on one side.
They reduce one uncertainty, not every uncertainty
Additional outage draws usually narrow Monte Carlo uncertainty. They do not add new heat waves, change incorrect outage assumptions, represent transmission constraints, or eliminate structural model error. Those require more weather data, sensitivities, and better model detail.
Monte Carlo uncertainty
Comes from using a finite number of outage draws. Increase draws to reduce sampling noise, particularly near a planning criterion.
Model and weather uncertainty
Comes from assumptions, data, future climate, portfolio detail, imports, hydro, and the finite weather library. More outage draws do not remove it.
Firm need translates risk into a capacity question
The firm-need study asks how much perfectly reliable, always-available capacity would need to be added—or could be removed—before the portfolio reaches a chosen LOLE target.
Estimate its current LOLE using fixed weather years, outage draws, and seed.
Add or remove a perfect-firm proxy until results lie on both sides of the target.
Use bisection until the capacity bracket reaches the selected MW tolerance.
Show the bracket, estimate, sampling interval, and whether the conclusion is statistically clear.
If 7.3 GW of perfect firm capacity leaves mean LOLE above 0.1 d/yr and 7.4 GW brings it to or below 0.1 d/yr, the solution is a 100 MW bracket. Reporting 7.36 GW would claim precision the search and finite Monte Carlo sample do not support. A conservative planning value uses the safe endpoint, while the midpoint is a convenient estimate.
A positive answer means perfectly firm capacity to add. A negative answer means perfect-firm-equivalent surplus that could be removed in this simplified single-area model. It is not automatically a procurement recommendation.
EFC and ELCC measure capacity value in different ways
Capacity value asks how much reliability contribution a resource provides—not how many nameplate megawatts it has. This matters most for weather-dependent and energy-limited resources.
Equivalent Firm Capacity
Replace the candidate resource with perfectly reliable firm capacity and find the amount that produces the same risk. This lab divides EFC by candidate nameplate for its firm-equivalent capacity-credit percentage.
Effective Load-Carrying Capability
Add the candidate, then find how much extra load the full portfolio can carry while returning to the base portfolio’s risk.
ELCC is a horizontal shift at equal reliability
Define the base and candidate systems
B is the entire portfolio with the selected candidate removed. B + C restores that candidate. This definition matters: ELCC is marginal to the portfolio and can change when the rest of the system changes.
Hold reliability risk constant
In the teaching curve, B serves 66.0 GW at 0.1 d/yr. B + C serves 68.4 GW at that same risk. The vertical matching rule prevents us from confusing lower risk at unchanged load with load-carrying capability.
Subtract matched loads
ELCC = 68.4 − 66.0 = 2.4 GW. This is a reference-peak load increase, not a claim about instantaneous output. The lab reports EFC divided by nameplate as its firm-equivalent capacity-credit percentage.
- Remove the selected resource from the portfolio to form base system B.
- Run B at the current peak load to obtain the reference risk.
- Restore the candidate C, then increase load and rerun the same weather/outage sample design.
- Bracket the load increase whose selected risk metric—LOLE or EUE—matches the base risk.
- Report the ELCC bracket midpoint as a reference-peak load increase and firm-equivalent capacity credit = EFC / candidate nameplate.
Common seeds reduce comparison noise, but finite Monte Carlo estimates are stepwise. The app therefore reports a bounded estimate at the selected MW tolerance instead of false precision.
A battery’s ELCC depends on when risk occurs
A battery contributes most when it has enough power, duration, stored energy, and availability to discharge during the system’s risk hours. Adding battery nameplate does not guarantee one-for-one ELCC.
Charging and discharging move energy into the risk window
A 10 GW / 40 GWh battery shifts energy, not time
The example charges 39 GWh during lower-load hours and returns 35 GWh in the evening—about 90% round-trip efficiency. It reduces the daily peak from 68 to 58 GW. The lower panel exposes the exact signed power schedule rather than asking an area annotation to do two jobs.
Peak reduction is not automatically ELCC
A 10 GW peak reduction on this one deterministic day does not establish 10 GW of ELCC. ELCC must be risk-matched across all weather years and outage draws. A battery may begin an event partly charged, experience an outage, face a longer event, or encounter multiple tight days without enough recharge.
Read a study as a connected story
Start with the study basis
Portfolio, peak demand, weather years, outage draws per year, stress mode, seed, and storage starting SOC.
Read occurrence and severity together
LOLE and LOLH show frequency/duration; EUE and event tables show depth and tail severity.
Find when risk happens
Use the month-by-hour heatmap, worst-day trace, and per-weather-year results.
Check sampling confidence
Inspect the LOLE interval and convergence. Increase draws when conclusions are close to the target.
Separate diagnostics from causes
Stress signatures show conditions present during shortfalls; they do not prove causal attribution.
State the model boundary
Single-area adequacy does not establish transmission deliverability, operating security, or customer outage performance.
“The portfolio’s mean LOLE is below 0.1 shortfall-day/year, but the 95% interval crosses the criterion. Risk is concentrated in September evenings and in two weather years. The result is therefore sampling-uncertain and weather-sensitive; more outage draws and targeted sensitivity cases are warranted before concluding that the system meets the reference.”
That statement is more decision-useful than “the model passed.”
Questions an industry analyst should ask
Days, hours, contiguous events, MWh, ppm, or affected years are not interchangeable.
Weather, load forecast, outages, hydro, imports, ambient derates, fuel, and common-mode events may be treated differently.
Repeated outage draws improve conditional estimates but do not expand the weather record.
A single-zone model assumes away transmission constraints that may prevent resources from reaching load.
Starting SOC, energy budgets, charging, foresight, and event duration can materially change capacity value.
Check confidence intervals, convergence, weather-year dispersion, sensitivities, and alternative risk metrics.
Study-grade work should reconcile documented test systems or published cases before informing procurement.