Skip to content
GridVision AI

MISO · Indiana · Public-record retrospective

Reynolds 345 kV Substation: interconnection queue history

Four of nine requests reached commercial operation.

GridVision AI ResearchUpdated

Nine interconnection requests since 2017: 4 reached commercial operation, 2 withdrew, and 3 remain active.

Built
4
Withdrawn
2
Still in queue
3

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
2017-06-16(unnamed)Solar200 MWBuilt2022-08-15 · 5.2 yrs
2017-06-16(unnamed)Wind200.1 MWBuilt2021-08-15 · 4.2 yrs
2017-06-16(unnamed)Wind200.1 MWBuilt2021-08-15 · 4.2 yrs
2018-03-12(unnamed)Wind200 MWStill in queue
2018-03-12(unnamed)Wind200 MWBuilt2023-04-20 · 5.1 yrs
2020-06-22(unnamed)Solar200 MWStill in queue
2020-06-23(unnamed)Wind200 MWWithdrawn2020-12-18
2020-11-06Surplus; J913Storage200 MWWithdrawn2021-02-10
2022-09-13(unnamed)Battery400 MWStill in queue

What the record shows

  • 400 MW of the 2,000 MW filed here withdrew, and 800 MW reached commercial operation.
  • Completions here took between 4.2 and 5.2 years from request to commercial operation (median 4.6).
  • The largest request filed here, 400 MW (battery), was filed in 2022 and is still active.
  • Three requests were filed on 2017-06-16; all of them reached operation.
  • Two of the 2 withdrawals came within a year of filing.
  • By technology, the requests here were wind 5, solar 2, battery 1, storage 1.
  • The longest-standing active request here was filed on 2018-03-12.
  • The dataset records this point of interconnection under four 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.
  • Three 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.

Related points of interconnection

How the MISO process works today: MISO interconnection queue. Comparing candidate nodes for a project? Read how to choose a point of interconnection.

Bring One Live DecisionOther retrospectives