Power · Sabey Decatur Technology Park · IN

What electricity-system costs has the Sabey Indianapolis petitioner committed to cover, and does that establish statewide customer protection?

A verdict applies only to the wording shown.

Question reviewed

Answer

Verdict on the wording above: Unknown We looked; the reviewed sources do not establish it. Unknown is not zero, not absent, not noncompliant. How verdicts work →

How it was framed
A question DataCenterData examined; no one is quoted.
What the evidence establishes
The petitioner says it will cover costs tied to this site's substation and energy needs. That does not establish how every Indiana data center affects other customers, so statewide protection remains unknown. Unknown is not zero or no effect.
Biggest limitation
Effects outside the reviewed site-specific commitment, including other tariffs, projects and wholesale-market costs, are not established here.
Checked
21 September 2026 · Next review: no trigger recorded · History (4) →

Evidence

What the evidence supports

The developer-authored petitioner appendix says Sabey will pay costs related to the project's substation, generation, transmission and distribution needs. That records a site-specific commitment; it does not establish every tariff, wholesale-market effect or project in Indiana.

Still unknown

Effects outside the reviewed site-specific commitment, including other tariffs, projects and wholesale-market costs, are not established here.

Sources

  1. Indianapolis petitioner appendix, cases 2025-CAP-856 / 2025-CVR-856 → Company

    Exact location Petitioner presentation, PDF pages 24–25, commitment concerning the proposed substation and energy needs

    What it supports The petitioner describes a commitment to pay costs related to the proposed substation and the site's energy needs; that site-specific statement does not establish statewide cost effects for every data center.

    Publication date unavailable · Accessed

Corrections and history

Correction · 12 September 2026 · Software-assisted second check

sabey-indianapolis → Power / cost allocation

Field Power / cost allocation

From Partially supported

To Not independently verified

Why One site's cost commitment cannot establish the statewide claim shown.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 14 September 2026 · Editorial classification update

sabey-indianapolis → Power / cost allocation

Field Power / cost allocation

From Not independently verified

To Partially supported

Why The cited commitment supports cost allocation for one site, but it cannot establish the statewide generalization shown.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 21 September 2026 · Editorial classification update

sabey-indianapolis → Power / cost allocation

Field Power / cost allocation

From Partially supported

To Unknown

Why A developer-authored, site-specific commitment does not establish statewide customer protection. The question now separates what the petitioner promised from what remains unknown.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 21 September 2026 · Editorial classification update

sabey-indianapolis → Power / cost allocation

Field Power / cost allocation

From One Indianapolis developer cost commitment proves no Indiana data center can affect other customers' electricity costs.

To What electricity-system costs has the Sabey Indianapolis petitioner committed to cover, and does that establish statewide customer protection?

Why The prior wording framed a universal inference without citing anyone who made it. The replacement is an answerable research question.

Evidence No additional evidence link; see the linked record or claim.

Review details

Scope

Unit
Power / cost allocation
Geography
Indiana
Period
None recorded
Confidence
medium — Developer-authored petitioner appendix hosted by the City of Indianapolis; no controlling utility order reviewed
Kind
Question reviewed

Conflicting evidence

We looked; the reviewed sources do not establish it. That is not zero and not absent. No conflicting record has been logged either.

Chronology

  1. Changed verdict recorded
  2. Changed verdict recorded
  3. Source retrieved
  4. Sources re-read (software-assisted second check, not an outside audit)
  5. Changed verdict recorded
  6. Changed wording recorded
  7. Checked by DataCenterData
  8. Date not established Next review: no trigger recorded

Data

This claim as JSON →

Suggest a correction

Suggest a correction → Claim ID sabey-cost-allocation-generalized and this page are prefilled. Accepted material corrections appear publicly on Changes.