Projects›Project MidSpan›Issues›Power Demand & Grid Infrastructure

Project MidSpan: Power Demand & Grid Infrastructure

The claimed 300-MW power context, grid dependence, infrastructure upgrades, cost allocation, reliability, and evidence still needed.

Available capacity is not the same as a committed service agreement.

Partly documented · Detailed issue review

Current status

SDCL’s complaint says the MidSpan property had access to at least 300 MW of high-voltage electric capacity, and current reporting distinguishes MidSpan from Project River by stating that MidSpan does not propose River-style onsite power plants. The reviewed record does not yet establish the campus’s initial or full-build load, utility commitments, transmission or substation upgrades, redundancy design, or who would pay for project-driven infrastructure.

Sources:MID-004 MID-006 MID-013

What is documented

Records and statements that can be tied to an identified source.

Legal Filing

The complaint cites access to at least 300 MW of high-voltage capacity

SDCL identifies electrical capacity as one of the site-selection attributes that attracted it to the property. That statement establishes the plaintiff’s representation, not a utility commitment or final load study.

Sources:MID-004

Third-Party Analysis

MidSpan is described as grid-supplied rather than River-style onsite generation

Local reporting says MidSpan does not propose the large onsite gas-and-biomass generation complex associated with Project River.

Sources:MID-006

Government Statement

Grid planning and electric-service impacts are outside TDEC’s primary role

TDEC’s data-center guidance identifies electricity supply and grid planning as utility, TVA/local-power-company, and potentially federal matters rather than TDEC environmental permitting decisions.

Sources:MID-013

What the project has represented

These statements are attributed to the project or its participants and are not automatically independent findings.

Developer Statement

Infrastructure should pay its own way

SDCL’s public messaging says energy and infrastructure should pay their own way and should not shift project costs onto nearby households. The current reviewed record does not yet contain the contracts or tariff treatment needed to test that commitment.

Sources:MID-005 MID-007

What must be separated in the power question

Several different numbers can be described as “capacity,” but they do not mean the same thing.

Placeward Analysis

Site access, reserved capacity, contracted service, and peak load are different facts

A credible power review should distinguish nearby transmission capability, utility study results, reserved or allocated capacity, executed service agreements, phase-by-phase demand, and full-build peak load rather than treating a single MW figure as all of them.

Sources:MID-004 MID-013

Placeward Analysis

Redundancy can require infrastructure beyond the IT load

Large data centers typically require reliability planning that may include multiple feeds, substations, transformers, backup systems, and staged capacity. MidSpan-specific quantities and designs must come from project and utility records rather than generic assumptions.

Sources:MID-013

What remains unresolved

?What are the initial, intermediate, and full-build MW demands for the campus?
?Which utility or utilities would serve the site, and what role would TVA have?
?Has any capacity been formally reserved, allocated, studied, or contracted?
?What new substations, transmission lines, distribution facilities, or rights-of-way would be required?
?What reliability standard and redundancy architecture would be used?
?Who would pay capital, operating, maintenance, and replacement costs for project-driven upgrades?
?Could any costs or risks be socialized to other customers under the applicable rate structure?

Evidence needed

Load forecast

Phase-by-phase MW demand, load factor, ramp schedule, and expected full-build peak.

Utility studies

Feasibility, system-impact, facilities, or equivalent studies showing required upgrades and constraints.

Executed service documents

Any reservation, service agreement, interconnection agreement, tariff election, or capacity commitment.

Infrastructure cost allocation

Who funds substations, transmission, distribution, metering, redundancy, and future reinforcement.

Reliability design

Utility feeds, onsite electrical topology, backup duration, generator or battery role, and restoration assumptions.

Supporting detail

Go deeper without losing your place

Expand chronology, community concerns, research priorities, verification methods, and related guidance as needed.

Assessment triggers & records to obtainResearch priorities

What would change this assessment

The current assessment should move when stronger records, rulings, studies, or enforceable commitments materially change the evidence.

→An executed utility agreement confirming the amount, timing, and conditions of electric service.
→A utility study identifying substantial new upgrades, congestion, or reliability constraints not visible in the current record.
→Binding cost-allocation terms showing whether project-driven infrastructure is fully borne by the project or partly by other customers.
→A materially different final load than the 300-MW site-selection figure might lead readers to assume.

Records to obtain

These are the highest-value documents to seek through public records, project disclosures, regulatory filings, or the court record.

Utility correspondence and studies

All capacity letters, load studies, service requests, upgrade estimates, and agreements for the MidSpan site.

TVA / local power records

Applicable large-load review, transmission planning, rate treatment, and infrastructure responsibility documents.

Electrical one-line / site utility plan

Substations, transformers, feeds, generator or battery systems, and phase sequencing.

Cost-allocation agreements

Developer, utility, county, industrial-park, or economic-development agreements assigning infrastructure costs.

Verification approachMethod

Use utility documents for utility facts.Developer descriptions of available power should be checked against records from the serving utility and TVA where applicable.
Track MW by phase.Avoid presenting site-selection capacity as though it were necessarily the project’s final operating load.
Separate reliability from cost.A technically feasible connection can still raise a separate question about who pays for it.