The Electricity Question Nobody's Asked Yet

So here's a thing I've learned about data centers that probably should have been obvious from the start.

They need power.

Like, a lot of power.

I mean, I knew that in the abstract. Servers run on electricity. That's not exactly news.

But what I didn't think about was the logistics of that.

Where does the power come from?

How does it get there?

What happens if the grid can't handle it?

And who figures all that out?

Following the Power Trail

Recently, while digging through Project Shelby information—that's the large data center development being tracked here—I found something interesting in our Project Dossier.

Panattoni, the developer behind Shelby, has stated publicly that they're coordinating with AEP Ohio on electricity availability.

That's their claim.

That's what they said.

I want to be clear about that distinction, because it matters: this is what the developer told a local news outlet. It's not independently verified. Nobody's confirmed it. Nobody's published AEP's side of the story saying, "Yep, we've got enough power," or "We're upgrading the substation," or anything specific about requested load versus approved load versus what infrastructure changes might be needed.

Just: we're coordinating.

Which sounds great.

But what does it actually mean?

I honestly don't know.

And I'm not going to pretend I do.

The Infrastructure Nobody Sees

Here's what I keep running into as I learn more about this: data centers need infrastructure the same way a house needs plumbing and electrical.

Except it's not one house.

It's a facility that can pull as much power as a small town.

That power has to come from somewhere.

It has to travel through wires and transformers and substations.

If you're building something that big in a place that wasn't built expecting something that big, somebody has to figure out: can the system handle it?

And if it can't, what needs to change?

Those are legitimate questions.

The thing is, I have no idea how long that takes to figure out.

I don't know what conversations happen between a developer and a utility company.

I don't know what regulatory hoops have to be jumped through.

I don't know if upgrading substations is routine or if it's a months-long process or if it costs money the developer pays or if there's some other mechanism I'm completely unaware of.

It's all just... blank space.

What I'm Actually Asking

Here's where my own confusion becomes relevant.

If I'm trying to build a site where people can see what's actually happening with these projects, one of the most important pieces of information is: what's the power situation?

Is there a filing somewhere that says what load the developer requested?

Is there a response from AEP saying whether that's feasible?

Are there engineering studies?

Are there minutes from meetings where this got discussed?

Those documents probably exist.

But I haven't found them yet.

And I don't even know where to look.

The Real Work

This is where Stark Civic Monitor is supposed to help, honestly.

Not by me deciding what the power situation means.

Not by me guessing whether there's a problem or whether there isn't.

But by actually tracking down those documents and making them visible so that people who know what they're looking at—contractors, engineers, utility workers, residents, officials—can see them side by side.

Right now, all anybody has is a developer's statement to a news outlet.

Which might be completely true and completely fine.

Or there might be five other documents filed with the county or the state or AEP that tell a more detailed story.

I just don't know yet.

And that gap—between what's been said and what's actually been filed—is exactly the kind of thing a records tracker is supposed to help close.