Projects

Generation interconnection requests the providers received in 2015 through 2020, sited in WA, OR, ID, MT, with their outcome and elapsed time as of each source's cutoff. Counted in requests, not projects: many requests can describe one facility. An agreement is not operation, and a request still active at the source’s cutoff is unresolved, not failed.

Against EIA’s generator inventory, PacifiCorp’s 17 operational requests in LBNL’s compilation: 14 linked to EIA units, 1 not in EIA’s inventory, 2 unresolved. A request is linked only where a cited public source identifies its facility and the state, county and resource both accounts give agree; unresolved says why not. queue-generator-links

Against EIA’s generator inventory, NWMT’s 24 operational requests in LBNL’s compilation: 14 linked to EIA units, 1 not in EIA’s inventory, 9 unresolved. A request is linked only where a cited public source identifies its facility and the state, county and resource both accounts give agree; unresolved says why not. queue-generator-links

Against EIA’s generator inventory, BPA’s own 26 operational requests: 13 linked to EIA units, 7 not in EIA’s inventory, 6 unresolved. A request is linked only where a cited public source identifies its facility and the state, county and resource both accounts give agree; unresolved says why not. queue-generator-links

Against EIA’s generator inventory, IP’s 54 operational requests in LBNL’s compilation: 24 linked to EIA units, 19 not in EIA’s inventory, 11 unresolved. A request is linked only where a cited public source identifies its facility and the state, county and resource both accounts give agree; unresolved says why not. queue-generator-links

Against EIA’s generator inventory, Avista’s 3 operational requests in LBNL’s compilation: 2 linked to EIA units, 0 not in EIA’s inventory, 1 unresolved. A request is linked only where a cited public source identifies its facility and the state, county and resource both accounts give agree; unresolved says why not. queue-generator-links

Against EIA’s generator inventory, PSE’s 3 operational requests in LBNL’s compilation: 0 linked to EIA units, 0 not in EIA’s inventory, 3 unresolved. A request is linked only where a cited public source identifies its facility and the state, county and resource both accounts give agree; unresolved says why not. queue-generator-links

Against EIA’s generator inventory, PGE’s 3 operational requests in LBNL’s compilation: 3 linked to EIA units, 0 not in EIA’s inventory, 0 unresolved. A request is linked only where a cited public source identifies its facility and the state, county and resource both accounts give agree; unresolved says why not. queue-generator-links

Requests, not projects: many requests can describe one facility and one request can be restudied. An executed interconnection agreement is not operation. A request still active or suspended at the source's observation cutoff is unresolved, not failed; the cutoff is the newest request date in the LBNL file and BPA's workbook generation date. Elapsed days run from the provider's request date to the date the source publishes for the milestone, computed only where both are present; a median or quartile is published only for a group with at least 5 such requests. Overall figures use LBNL's compilation alone, which already carries BPA's queue; BPA's own workbook is a separate group and dates no milestone but the request. Providers run different queue processes, so cross-provider comparison reflects process as much as outcome. MW are the requesters' figures within one source, never operating capacity. LBNL and BPA carry the same request numbers for 992 requests; the two accounts disagree on outcome for 117 of them, mostly by cutoff, and are shown side by side on each request’s page rather than merged. Attribution: Lawrence Berkeley National Laboratory and GridTracker, Queued Up (CC BY 4.0).Frozen facts ↗