Proposed-site record
High-priority Applied Digital proposal with a South Dakota PUC facility-permit record for a separate 145 MW dual-fuel generation plant and 345 kV tie line near Toronto. The dataset's 430 MW remains unclassified project/power context; no reviewed source establishes data-center IT load, energized capacity, water quantity, workload, or customer allocation.
This panel tracks what the facility is for without assuming that every project is AI training, inference, or cloud capacity.
No source-backed workload, customer, hardware, or training/inference allocation is attached to this record yet.
Workload classification remains unknown in the reviewed record.Source leads point to attached records or reporting. They still need field-level review before being treated as verified evidence.
Source dataset project_cost field reports $16 billion; public funding records still need local review.
Source reviewed September 9, 2026: the South Dakota PUC Toronto Power Plant application describes the proposed energy-conversion facility and transmission line but does not disclose a data-center water source, cooling method, withdrawal, consumption, or wastewater quantity. The 145 MW plant record is separate power-infrastructure context and should not be treated as facility water evidence.
Source reviewed September 9, 2026: South Dakota PUC docket EL25-028 identifies a proposed 145 MW dual-fuel Toronto Power Plant and approximately 4.9 miles of 345 kV generation-tie transmission to the Astoria substation, with commercial operation expected in 2029. This is proposed generation and transmission infrastructure, not confirmed requested, approved, energized, or data-center IT-load capacity; the dataset's 430 MW remains unclassified project/power context.
No fuel-cell or Bloom Energy source is attached to this project yet.
No NDA reported
Start a moderated thread for local questions, meeting notes, public-records coordination, or context that should not be treated as verified evidence yet.
These links are the current public trail for this record. Treat broad dataset links as leads; local documents and reporting carry more weight.