Skip to content

ERCOT · Texas · Public-record retrospective

Tesla 345 kV: interconnection queue history

Three of eight requests withdrew; one reached operation.

GridVision AI ResearchUpdated

Eight interconnection requests since 2016: 1 reached commercial operation, 3 withdrew, and 4 remain active.

Built
1
Withdrawn
3
Still in queue
4

The queue record

Every interconnection request the dataset records at this point of interconnection, in filing order.

Interconnection requests recorded at this point of interconnection, with request date, capacity and outcome.
RequestedProjectTechnologyCapacityOutcome
2016-06-23Shorthorn SolarSolar200 MWWithdrawn2018-09-04
2016-10-19Misae SolarSolar240.8 MWBuilt2021-12-20 · 5.2 yrs
2016-10-25Shorthorn 2 SolarSolar200 MWWithdrawn2019-06-05
2018-05-15Fagus Solar Park 1 SLFSolar + battery166.42 MWStill in queue
2019-12-03Independence Trail StorageBattery100 MWStill in queue
2020-02-03Ponil SolarSolar145 MWWithdrawn2024-11-07
2024-06-03Fagus Solar Park 2 SLFSolar + battery166.57 MWStill in queue
2024-06-03Fagus Solar Park 3 SLFSolar + battery169.59 MWStill in queue

What the record shows

  • 545 MW of the 1,388 MW filed here withdrew, and 241 MW reached commercial operation.
  • The one request that reached operation took 5.2 years from request to commercial operation.
  • The largest request filed here, 241 MW (solar), reached operation 5.2 years after filing.
  • Two requests were filed on 2024-06-03; all of them remain active.
  • None of the 3 withdrawals came within a year of filing; the quickest took 2.2 years.
  • By technology, the requests here were solar 4, solar + battery 3, battery 1.
  • The longest-standing active request here was filed on 2018-05-15.
  • The dataset records this point of interconnection under three spellings, which are combined here.

What a decision record would have to make explicit

  • What separated the requests that reached operation from those that withdrew, such as study results, upgrade assignments or site conditions, is not in the public queue record, so a decision record here would have to carry it as an unknown.
  • Four requests are unresolved, so the outcome counts at this node can still change.
  • The dataset records outcomes and dates, not reasons, so no cause is attributed to any outcome here.

What this does and does not show

This is a reading of a public dataset, not a customer case study: no engagement, customer or client is involved. The dataset records outcomes — what was built, what withdrew, and when — but not why any project withdrew, so no cause is attributed here. Nothing on this page claims GridVision predicted, influenced or would have changed any outcome, and a pattern at one point of interconnection does not generalise to another.

Source: Lawrence Berkeley National Laboratory, Queued Up: 2026 Edition — project-level interconnection queue dataset. Interconnection requests through year-end 2025. Used under CC BY 4.0; attribution to Lawrence Berkeley National Laboratory and GridTracker.