Datasets

What a released table is for, the period it covers, what is missing and why, and the edition it was built from.

• Annual net generation by plantHow much electricity each published plant delivered in each calendar year, from the annual Form EIA-923 survey. Use it to compare plants and years; a plant EIA did not list for a year has no row, not a zero.
  2015–2024
• Hourly balancing authority operationsDemand, net generation and total interchange for each frame balancing authority and hour, from Form EIA-930. Values are as the authority reported them; EIA's adjusted and imputed values sit beside them and never replace them. Where EIA published an imputed value beside a reported one, EIA marked that report as replaced. The atlas leaves every marked demand hour out of every sum, mean and count and counts it as flagged; a marked net-generation or interchange hour only when it is at least 1.5 times the largest unmarked magnitude of the authority's year.
  2015-07-01 07:00 UTC – 2026-09-06 07:00 UTC
• Monthly net generation by plantHow much electricity each published plant delivered in each calendar month, from Form EIA-923, for the years in which its operator reported monthly. A plant that reported once a year has no rows for that year, because EIA estimates its monthly values; the annual table covers it.
  2015-01–2024-12
• Monthly balancing authority operationsDemand, net generation and total interchange summed by month for each frame balancing authority, from Form EIA-930, with the number of hours each sum covers. A sum adds reported hours only, leaving out the flagged hours (reports EIA marked with its own imputed value, under each measure's rule), so read it beside its hours before treating it as a full month: a month is complete when its hours plus flagged hours cover it.
  2015-07–2026-09
• Plant inventoryEvery plant Form EIA-860 lists for the inventory year: where it is, who operates it, which balancing authority it reports to, and whether the atlas publishes it. Published plants report to a frame balancing authority or sit in Washington, Oregon, Idaho or Montana; the rest stay in the table, marked unpublished.
  2024
• Generator inventoryEvery generator at a published plant as Form EIA-860 lists it for the inventory year: its nameplate capacity, technology, energy source, status and dates. Capacity is a rating in MW, not output; a storage unit's energy capacity in MWh is a separate number.
  2024
• Retail electricity sales by utilityElectricity sold to end customers in Washington, Oregon, Idaho and Montana in the comparison year, from Form EIA-861: energy sold, revenue and number of customers for each utility, state, balancing authority and customer class. It is what customers bought, not what plants generated.
  2024
• Reported production CO2 by plantCarbon dioxide that each published plant's EPA-monitored units reported under 40 CFR Part 75 for each reporting year, summed over those units, as filed in short tons and in tonnes. It is a stack total of one program's population: a plant EPA does not monitor has no row and is not zero, and a plant with an unmonitored combustion generator shows its monitored units' mass, not its total. Each year is set against that year's EIA-860 inventory and crosswalk, and years sit side by side without a difference. Open Grid Emissions fills unmonitored units from EIA-923 fuel (Fredonia, Glendive GT) and allocates a CHP plant's CO2 between electricity and steam; the atlas does neither.
  2023–2024
• Distribution reliability by utilitySAIDI and SAIFI as each utility in Washington, Oregon, Idaho or Montana reported them on Form EIA-861 Schedule 3, with and without major event days, for every report year through the comparison year: one row per utility, state, year and part of the schedule (IEEE 1366 or another method), kept as published. Nothing is computed from another index and nothing is filled; the two parts are never compared, and a system average says nothing about one address.
  2013–2024
• Interconnection queue requestsEvery interconnection request two sources publish for the region, in one schema: LBNL and GridTracker's Queued Up compilation of transmission providers' queues, and BPA's own request workbook. A row is a request for interconnection service, not a plant, and belongs to one source's account: a request both sources carry is two rows related as a candidate and never merged, so a count across sources counts accounts, not requests. Each source's status text stays beside a closed outcome vocabulary, dates appear where the source publishes them, and elapsed days exist only between two present dates.
  2000–2026
• Transmission providers' own interconnection queuesA transmission provider's own posted queue, read as its account of its requests beside LBNL's compilation of the same provider: first NorthWestern Energy's Pre-Cluster Serial Interconnection Queue as updated 2026-09-24, nine months past LBNL's cutoff. A row is a request for interconnection service as the provider lists it, not a plant; the provider's status word stays beside the common outcome, and the workbook dates the request only. The two accounts are related request by request through the provider's own project number, never by name and never merged, and where their outcomes differ both are kept, each as of its own date. Every pinned edition stays loaded; the newest is the one set against LBNL.
  2001–2024
• Generator ownership sharesWho owns what fraction of each generator at a published plant in the inventory year: from Form EIA-860 Schedule 4 where the schedule lists owners, and by the single-owner default (the operator owns all of a generator coded single-owner) where it does not. A share is a fraction of one generator and owned MW is that fraction of its nameplate; the table does not add MW across owners, and a generator with no share row has an unknown owner, not none.
  2024
• Monthly storage operation by plantEnergy each published storage plant took in to charge and sent out in each calendar month, from Form EIA-923 Schedule 3 Part B, with the signed net. Charged and discharged are both MWh over the month and are never netted against generation; a month a plant did not report has no row, not a zero. Months of plants that report annually are EIA's estimates and are kept here, split out by the reporting frequency.
  2015-01–2024-12
• Monthly generator inventory historyWhat EIA's monthly generator inventory (Form EIA-860M) asserted about each generator and when: one row per generator for each month in which a tracked attribute changed, valid until the next change, beside the baseline inventory-year row from Form EIA-860. Every row is dated and expired rows stay; none of them states a generator's current status. The companion change table sets each generator's row valid at the pinned current workbook against its baseline row and names the change.
  2015-07–2026-07
• Customer programme results by utilityEnergy-efficiency and demand-response results as each utility filed them on Form EIA-861 Schedule 6, Parts A and B, for Washington, Oregon, Idaho and Montana, report years through the comparison year: one row per utility, state, year, balancing authority, programme, customer class and metric, each metric in its own unit. The filer's total is its own row (class total) and never a sum of classes; reporting-year and life-cycle savings, and potential and actual peak savings, are separate metrics and never merged. A blank stays null. Short-form (EIA-861S) respondents file no figures and are not applicable, not zero. Savings are self-reported under each utility's own evaluation and are not comparable across utilities.
  2013–2024
• Distributed generation by utilityDistributed generation each utility reported on Form EIA-861 for Washington, Oregon, Idaho and Montana in the comparison year, under net metering and outside it (the non-net-metering schedule): installed capacity in MW and, for storage, energy capacity in MWh, by customer class and technology, with net-metered customers and the energy they sold back to the utility. Rollup rows (technology total, all storage, and the customer-class total) are flagged is_rollup and never added to the rows beneath them. The systems carry no location and are excluded from the EIA-860 plant inventory; a non-net-metered system can also be an EIA-860 unit, which is disclosed, not resolved.
  2024
• PGE distributed-generation screening, one substation's feedersWhat Portland General Electric's public distributed-generation screening said about each feeder it files under one substation, Brookwood in Hillsboro, at the edition's date: peak load in MVA, net daytime minimum load and connected and queued distributed generation in MW, nominal voltage in kV, and PGE's own readiness and generation-limited classifications. PGE publishes no available hosting capacity, so the table has none and none is derived. Feeders are measured at their own times and are never added together. The rows are shown on PGE's organization page and each feeder's 500-foot buffer on the map; the atlas publishes no copy of PGE's layer.
  2026
• Purchased power by seller (FERC Form 1)What each FERC Form 1 respondent the atlas links to an EIA utility paid for purchased power and exchanges in each report year, by seller row as filed on Schedule 326 (Account 555): settlement dollars and MWh. Seller names are free text: a row naming a party is a counterparty, a mechanism row (deferrals, allowances, the residential exchange) is an adjustment, a market operator's row is a market settlement, and the filing's own total row is kept as its own row, never added to the others. Utilities that file no Form 1 (public power, cooperatives, federal agencies) have no rows here, which is not zero purchases. Nominal dollars; the latest report year can still change, since revisions and late filings arrive for months after the April deadline and the source carries no final flag.
  2015–2025
• Electric operating revenues by class (FERC Form 1)Electric operating revenues each linked FERC Form 1 respondent reported on Schedule 300 (Account 400) for each report year, by revenue type: dollars, and on sales lines the MWh sold and average customers per month. The schedule's computed lines (class lines and totals, is_subtotal) are kept as filed and never re-summed with the lines beneath them. Not EIA-861 retail revenue, which is a different survey, scope and year basis. Nominal dollars; the latest report year can still change.
  2015–2025
• Electric operation and maintenance expenses (FERC Form 1)Electric operation and maintenance expenses each linked FERC Form 1 respondent reported on Schedule 320 (Accounts 500 to 935) for each report year, by expense type, in nominal dollars. Function totals the form computes are flagged is_subtotal and kept as filed; the accounts beneath them, such as purchased power (555) and fuel, are components and are never added to a total again. Electric rows only. The latest report year can still change.
  2015–2025
• Plant and service-territory candidatesWhich service-territory polygons contain each published plant's reported coordinate, from four state-hosted layers: Washington Ecology's electric utility service areas, Oregon ODOE's (electric areas only), Idaho's electricity providers and Montana's rural electric cooperatives. A row is a candidate from point-in-polygon containment, never a service relationship or a supplier: the layers are unofficial and approximate, overlaps and gaps are kept, a plant can sit inside several polygons or none, Montana's layer covers cooperatives only, and service questions go to the utility.
  2024
• Council demand forecast (draft Ninth Power Plan)The Northwest Power and Conservation Council's frozen-efficiency demand forecast for the draft Ninth Power Plan, from its 28 public area workbooks as published: annual energy in average megawatts (the Council writes aMW; the dictionary unit here is MWa, the year's megawatt-hours divided by the hours in the year) and the annual single-hour peak in MW, for 2027 through 2046, under each of five future pathways and each of three climate-model weather patterns, with the total load broken into its residential, commercial and industrial, incremental data-centre, electric-vehicle and hydrogen components. Frozen efficiency means equipment efficiency is held fixed so the Council's resource model can choose cost-effective efficiency afterwards: it is a planning input, not a sales forecast, not an observation of load and not a utility integrated resource plan expectation, and it is never merged with one. Futures and climate models are separate dimensions and are never averaged, summed or collapsed together; energy in MWa is never added to a peak in MW. Areas are the Council's own labels, not the atlas frame and not service territories, and NPCC is the Council's own whole-region aggregate, never a sum of the thirteen area rows made here. The hydrogen component is null with not_published on the peak series, which has no hydrogen column. The plan is a draft open for public comment. The data-centre and hydrogen workbooks in the same folder are the forecast's inputs, with their own trajectories and zones, and are described in their own dataset, council-demand-inputs; the folder's README is the citation for the units.
  2027–2046
• Clean-energy obligations (Washington)What Washington's Clean Energy Transformation Act (RCW 19.405) and Energy Independence Act (RCW 19.285) ask of each utility and what has happened since, one curated assertion per row: which statute applies and why, the target owed, what the utility filed, what the issuing body decided about the filing, and the open proceeding a reader can still join. The five kinds are kept apart. A filing that restates a target does not enact it: only rows standing enacted or ordered are the obligation. A fuel-mix value is not a compliance verdict: only a determination row says that. A row with a missing reason is an absence checked on a date. A utility or a kind absent from the file has not been curated, which says nothing about what applies to it.
  2006–2026
• Named large loadsDossiers of named large electricity loads from commission dockets, filed contracts, tariff sheets, utility resource plans and announcements, one dated assertion per row in six kinds kept apart: what was announced, what the customer asked the utility to serve, the minimum the tariff or contract bills, what an executed agreement makes available, a forecast attributable to the facility alone, and what the meter recorded. Each figure stays in its source's unit, never converted, and is never added to another, across facilities or to a utility forecast that already includes the facility. The utility on a dossier is the one a filing or contract names; proximity never establishes a supplier. A row with a missing reason is an explicit absence: withheld or not published names who holds the figure. Dossiers are chosen where public filings exist; they are not a census of large loads.
  2016–2026
• BPA supply accountsWhat a utility's power supply from the Bonneville Power Administration consists of, one curated assertion per row from BPA's workbooks, lists and letters, the utility's own annual report or financial statements and Washington's Fuel Mix Disclosure, for a utility bpa_customer.csv links to its BPA customer id: the product it buys under which contract; its Rate Period and Contract High Water Marks, entitlements in average megawatts; its net requirement and load above the RHWM, which are BPA's forecasts; its monthly Contract Demand Quantities in kilowatts; what it reports paying BPA and buying from it; and the disclosure's attribution of its sales to BPA. An entitlement is not a delivery and neither is a payment: none of these is added to, subtracted from or divided by another, and figures of different periods are never compared as if they covered the same time. Workbook values are read at build time from the cell each row names in BPA's pinned file. A utility without rows has not been curated, which is not a statement about any contract with BPA. Coverage counts a row under the calendar year its period starts: BPA's fiscal year starts on October 1 of the year before the one it is named for.
  2011–2028
• Interconnection requests against EIA's generatorsFor generation requests that reached operation (every one in BPA's own workbook, and the 2015-2020 cohort's requests to other providers in LBNL's compilation), a reviewed disposition against EIA's generator inventory: linked to the EIA units the request concerns (a new plant, phases of one, an uprate, a repower, or an agreement for a plant already running with no capacity change, never counted as a new plant), not in EIA's inventory (a cited source identifies a facility EIA lists no unit for), or unresolved with a reason. A link needs a cited public source that identifies the facility and the same state, county and resource in both accounts; a name is never enough. The queue's and EIA's MW and status stay each source's own and are never reconciled or added; disagreements are counted. Months from request to operation exist only for new plants and phases.
  2000–2023
• Council data-centre and hydrogen load inputs (draft Ninth Power Plan)The two input workbooks the Northwest Power and Conservation Council publishes beside its draft Ninth Power Plan demand forecast, read cell by cell as published: the incremental load of new data centres and chip fabrication plants under low, mid and high trajectories, and the electric load of producing hydrogen in the Northwest under low and high trajectories. Every value is annual energy in average megawatts (the Council writes aMW; the dictionary unit here is MWa); there is no peak, because the Council leaves hydrogen out of its peak forecast and states the data-centre values as annual energy. Data centres run 2024 to 2046 for the region and 2024 to 2030 by utility, split into data centres only, chip fabs only and both; hydrogen runs 2027 to 2050 for the Northwest and 2027 to 2046 by the Council's own hydrogen zones. Trajectories are the Council's alternatives and are never averaged or summed; a zone is the Council's own label, not the atlas frame or a service territory; a regional series or Total column is the Council's own figure, never a sum made here; a blank cell is not published, never zero. These are inputs to the forecast model, not the DC_Load and H2_Load components of the area workbooks (council-demand-forecast), and the plan is a draft open for public comment.
  2024–2050
• Council model resource buildouts (draft Ninth Power Plan)The resources the Northwest Power and Conservation Council's capital expansion model (OptGen) adds to the existing system under each of the 13 sensitivities of its draft Ninth Power Plan scenario analysis, read row by row from the Council's model buildouts workbook: by snapshot year (2028, 2030, 2032, 2034, 2038, 2042 and 2046), the year each resource was built, the Council's model zone, the resource and its resource type. In 2028 the only generating resources open to the model were those regional entities had already planned; demand-side resources were all available. This is a planning scenario: not the plan's recommended resource strategy, not a utility's plan and not a forecast of what will be built. Each sensitivity's portfolio is optimized over the same sampled futures of demand, gas prices, hydro, wind and solar, so there is no future pathway or climate model here; sensitivities are the Council's alternatives and are never averaged or summed. Conservation (resource type EE) is annual energy in average megawatts, as the plan draws it (the Council writes aMW; the dictionary unit here is MWa); every other type is nameplate capacity in MW; the two are never added. A snapshot lists what the model holds in that year, including resources built earlier, and some earlier decisions were not locked, so snapshots are never added together. Zones are the Council's model zones, and a supply-side resource may be built in one zone for another zone's demand; they are not the atlas frame or service territories. The Council's own pivot of one sensitivity is reconciled against the rows. The plan is a draft open for public comment.
  2028–2046
• Council needs assessment reserve margins, 2031 (draft Ninth Power Plan)The Northwest Power and Conservation Council's needs assessment for 2031, the region as a whole, read cell by cell from its needs assessment workbook: for each of five need studies, the planning reserve margin per season that its capital expansion model (OptGen) must build to, with the GENESYS and OptGen seasonal peak loads, the existing system's resource contributions, the need and the load-resource balance it is made from; and the annual firm-energy adequacy reserve margin with its monthly duration value-at-risk, threshold, firm-energy adjustment and average monthly load. Res & Tx is the one study every New Resource & Transmission Risk sensitivity shares (Appendix M, PDF page 25); the other four test hydro operations (Appendix M Table M-10: 2020 BiOp Flex Spill Operation, 2023 RCBA Operations, Recommended Spill and MOP Targets, Limited Flex Operation). The studies share the existing system and the High Growth pathway's load, and the existing system falls short of the Council's adequacy criteria in every one; the margins are the Council's signal to its model, not an observation, not a utility's requirement and not a forecast. Loads, resources and need are MW; the firm-energy adjustment is average megawatts (the Council writes aMW; the dictionary unit here is MWa), as is the average monthly load it is divided by; margins are fractions of the load each row names (0.286 is 28.6% above that load); duration value-at-risk is hours. They are never combined, studies are never averaged and seasons or months never summed. The Council's own totals (Total Resources, the load-resource balance, each study's seasonal need and annual margin) are reconciled against the figures they are made from. The study is final; the plan it supports is a draft open for public comment.
  2031–2031

29 datasets are described so far; the other released tables follow in the same form.

Release 20260929T050546Z-51ae0f7d3c78