Welcome Back to Chicago 2.0. Please Bring a Generator.
Welcome Back to Chicago 2.0. Please Bring a Generator.
Hammond Wants the Chicago Bears, Billions in AI Data Centers and an Entire New Economic Corridor. Then Northwest Indiana Spent More Than a Week Trying to Turn the Lights Back On.
By F’nAround Media
A funny thing happened after we were researched whether Hammond, Indiana might quietly be turning itself into Chicago 2.0.
The lights went out.
Not metaphorically.
Not in some clever systems-theory way where we tell you the regulatory lights went out and then spend 4,000 words discussing institutional gravity.
The actual fucking lights went out.
Across Northwest Indiana.
And for portions of the region, they stayed out for more than a week.
Which presents a rather inconvenient question when the same region is simultaneously discussing billions of dollars in artificial-intelligence infrastructure, a massive CoreWeave data center, enormous future electrical demand, utility expansion, institutional redevelopment and potentially becoming the future home of the Chicago Bears:
Exactly how resilient is the electrical system underneath Chicago 2.0?
That question wasn’t part of our original investigation.
It is now.
Because sometimes you spend weeks studying infrastructure and then Mother Nature apparently decides to peer-review your work.
Previously on F’nAround: Why the Hell Is Everyone Suddenly Interested in Hammond?
Our original article, The Hammond Bears and Chicago 2.0?, began with something much less dramatic.
A number didn’t make sense.
While looking into Dave Pavlik, Decennial Group and the enormous data-center development occurring at Hammond’s Digital Crossroad campus, we encountered the kind of discrepancy that makes systems researchers lose an otherwise perfectly productive afternoon.
The proposed CoreWeave expansion is enormous.
Hammond approved a development agreement in June 2025 for what the city described as the largest economic-development project in its history. Decennial Group, which developed and owns the existing Digital Crossroad facility, is slated to construct another approximately 450,000-square-foot building on 25 acres of the former State Line Generating Plant property for CoreWeave.
The proposed CoreWeave facility has been reported at approximately 180 megawatts.
That’s not a warehouse with particularly enthusiastic air conditioning.
That’s industrial-scale electricity consumption.
And once we started following the electricity instead of simply following the real estate, the story expanded dramatically.
Northwest Indiana wasn’t merely getting a data center.
Utilities were preparing for enormous future electrical loads. Generation planning was changing. Data centers were appearing throughout Indiana. Former industrial sites were becoming digital infrastructure. Billions of dollars were moving toward places most Americans historically associated with steel mills rather than GPUs.
Then another seemingly unrelated development entered the map.
The Chicago Bears.
Except that part isn’t really speculative anymore.
On August 13, 2026, Bears President and CEO Kevin Warren said the organization’s “sole focus” is developing a world-class stadium and mixed-use development in Hammond.
The Bears say due diligence at Hammond’s Lost Marsh site has been completed and the property has been deemed viable. They’re also evaluating Wolf Lake Terminal and have discussed potentially utilizing both sites.
So suddenly the theoretical map became substantially less theoretical.
On one side of Hammond:
billions of dollars in AI infrastructure.
On another:
potentially one of the largest sports and entertainment developments in the Midwest.
Surrounding everything:
housing, hotels, retail, transportation, institutional investment, industrial redevelopment and the economic ecosystem that naturally follows developments of this scale.
Our original question therefore became fairly straightforward:
Is Hammond simply attracting several unusually large projects at approximately the same time?
Or are we watching the early formation of an entirely new economic node within the Chicago metropolitan system?
We called it Chicago 2.0.
Then August 11 happened.
Northwest Indiana Meets Its Real-Life Stress Test
A devastating storm system tore through Northwest Indiana with reported wind gusts reaching approximately 99 mph.
This wasn’t a normal summer thunderstorm.
Trees came down.
Utility poles snapped.
Transmission and distribution infrastructure sustained extensive damage.
Hundreds of thousands of customers lost electricity.
Days later, enormous numbers remained without service.
CBS Chicago reported approximately 175,000 homes and businesses were still without power several days after the storm. Gary alone still had tens of thousands of customers without electricity.
And restoration wasn’t measured in hours.
It was being measured in days.
Then a week.
For some customers, potentially longer.
Residents were buying generators.
Businesses were operating without normal electricity.
Traffic signals became four-way stops.
People reorganized their lives around finding electricity, refrigeration and hot food.
All because one of the most technologically ambitious emerging economic corridors in the Midwest had just encountered an extremely old-fashioned infrastructure problem:
A tree can still beat a power line.
And that creates an important distinction that our first Hammond investigation didn’t fully examine.
Having Electricity and Delivering Electricity Are Two Different Systems
Our first article concentrated largely on generation capacity.
Where is Northwest Indiana going to find enough electricity for all of this?
That’s still an important question.
But the storm exposed another one.
What happens after the electricity is generated?
Power generation and power delivery are different infrastructure problems.
You can build another power plant.
You can generate another 2,000 megawatts.
You can build solar.
Natural gas.
Battery storage.
Whatever combination eventually wins the political, regulatory and economic argument.
None of that guarantees electricity reaches your refrigerator after 99 mph winds put a tree through the distribution system.
The grid between generation and the customer matters.
Transmission lines matter.
Substations matter.
Distribution circuits matter.
Poles matter.
Vegetation management matters.
Redundancy matters.
Repair crews matter.
Replacement equipment matters.
Emergency planning matters.
And perhaps most importantly after a regional catastrophe:
restoration capacity matters.
That is where the Chicago 2.0 question gets substantially more interesting.
Because Hammond isn’t merely talking about adding another subdivision.
It is discussing infrastructure that cannot casually tolerate prolonged electrical interruptions.
Imagine Telling an AI Data Center You’ll Have the Power Back Next Week
This is where the economics become absurdly different.
A residential customer losing power for a week is miserable and potentially expensive.
Food spoils.
Hotels cost money.
Generators cost money.
Fuel costs money.
Businesses lose revenue.
Medical equipment becomes a concern.
Work becomes difficult.
Now imagine applying prolonged downtime to hyperscale AI infrastructure.
You can’t simply tell an AI cloud provider:
“Good news. We’re hoping to have everybody restored by Friday.”
That’s not how this industry works.
CoreWeave reported more than $5 billion in revenue during 2025 and more than 850 megawatts of active power capacity by year-end.
Here’s a deliberately crude thought experiment.
Take $5 billion.
Divide it across 850 MW of active power.
That works out to roughly $5.88 million of annual revenue for every active megawatt across CoreWeave’s overall system.
Now apply that simplistic ratio to a hypothetical fully operational 180 MW Hammond facility.
That’s roughly:
$1.06 billion of annual revenue-equivalent activity.
Divide that across 52 weeks:
about $20.3 million per week.
Again and this distinction matters enormously that does not mean a one-week Hammond outage would automatically cost CoreWeave $20 million.
It almost certainly wouldn’t work that simply.
Cloud infrastructure uses redundancy.
Workloads can potentially migrate.
Contracts differ.
Utilization differs between facilities.
Customers have different service arrangements.
The facility could have backup generation, batteries, multiple utility feeds and redundant systems specifically designed to prevent a grid interruption from becoming an actual computing outage.
The calculation is useful for one reason:
scale.
It demonstrates why data centers treat electricity reliability completely differently from ordinary commercial customers.
At this level, downtime isn’t inconvenient.
Downtime is potentially financially catastrophic.
Independent research from Uptime Institute makes that clear. Its 2025 outage analysis found that more than half of respondents experiencing significant, serious or severe outages said the incident cost more than $100,000.
One in five reported costs exceeding $1 million.
And power problems remain the leading cause of serious and severe data-center outages.
So hyperscale infrastructure doesn’t simply need electricity.
It needs electricity with backup plans for the backup plans.
Which Brings Us Back to Hammond
Digital Crossroad already understands this.
The existing Hammond campus advertises a dedicated onsite substation with more than 100 MW of capacity and distributed redundant topology.
That’s exactly what you would expect.
The question isn’t whether engineers building a multibillion-dollar data center remembered that power outages exist.
Of course they did.
The more interesting public-policy question is what happens outside the fence.
Because Northwest Indiana may soon contain two electrical realities.
One could consist of extraordinarily hardened hyperscale infrastructure with dedicated substations, redundant power feeds, backup generation and sophisticated continuity systems.
The other could consist of ordinary residents and businesses connected to a distribution network where an extraordinary storm can produce restoration timelines stretching beyond a week.
Neither reality automatically means somebody did something wrong.
A 99 mph wind event can destroy even well-maintained infrastructure.
But when billions of dollars begin flowing into a region specifically because of its future infrastructure potential, the condition and resilience of the surrounding public system becomes a legitimate question.
Especially when Chicago 2.0 isn’t supposed to contain only servers.
Because the Bears Need Electricity Too
A Bears stadium creates an entirely different infrastructure problem.
The team isn’t discussing building a football field surrounded by parking spaces.
Kevin Warren has explicitly described the Hammond concept as a world-class stadium and mixed-use development.
Mixed-use means the stadium becomes only one component.
Hotels.
Restaurants.
Retail.
Entertainment.
Housing.
Transportation.
Parking infrastructure.
Potential convention activity.
Possibly major national sporting events.
Potentially a Super Bowl.
Potentially NCAA events.
Tens of thousands of people moving simultaneously through a concentrated geographic area.
That means electricity becomes part of public safety.
Imagine a severe weather event occurring during a sold-out Bears game.
Now you’re not merely asking whether the scoreboard works.
You’re talking about emergency lighting.
Communications.
Traffic control.
Elevators.
Security systems.
Payment systems.
Cellular infrastructure.
Public transportation.
Restaurants.
Hotels.
Digital ticketing.
Broadcast systems.
Emergency services.
And potentially 60,000-plus people trying to leave one area simultaneously.
A world-class stadium therefore requires something beyond “available electricity.”
It requires world-class resilience.
And that’s where the Bears, CoreWeave and Northwest Indiana storm suddenly belong in the same article.
Not because they’re causally connected.
Because they’re infrastructurally connected.
Chicago 2.0 Can’t Have Chicago 1890 Electrical Reliability
This is the point where F’nAround’s original systems map gets another layer.
The first article asked whether the extraordinary convergence of capital in Hammond suggested the emergence of a new metropolitan economic corridor.
Now we need to ask what infrastructure must exist underneath that corridor for the theory to work.
If Hammond is going to host hyperscale AI computing, potentially the Chicago Bears, hotels, housing, entertainment, healthcare, transportation and billions in new investment, then the infrastructure conversation cannot stop at:
“How many megawatts can NIPSCO generate?”
It has to include:
How quickly can the system recover?
How much redundancy exists?
Which substations are hardened?
Which transmission corridors have alternate paths?
How much distribution infrastructure is being replaced?
How much is underground?
How much is vulnerable to vegetation?
How much emergency equipment is available locally?
How quickly can transformers and poles be replaced after catastrophic events?
How many repair crews can be mobilized?
Which customers receive priority restoration?
What infrastructure improvements associated with hyperscale customers also strengthen surrounding communities?
And perhaps the biggest question:
Who pays for all of it?
Because that may ultimately determine whether Chicago 2.0 becomes an economic-development success story or an infrastructure paradox.
Follow the Megawatts. Then Follow the Money.
Indiana wants data centers.
Developers want data centers.
AI companies desperately need data centers.
Utilities see enormous new customers.
Hammond sees billions in investment.
The Bears see land, political cooperation and the possibility of building the stadium ecosystem they’ve been trying to create for years.
Everybody has an incentive.
That’s fine.
Economic development is supposed to create incentives.
But infrastructure economics becomes considerably more complicated when a handful of enormous electricity consumers begin requiring capacity previously associated with entire communities.
That makes cost allocation critically important.
If a hyperscale customer requires a new substation, who pays?
If transmission infrastructure needs reinforcement, who pays?
If new generation becomes necessary, who finances it?
If grid-hardening projects benefit both data centers and residential customers, how are those costs allocated?
If they benefit only hyperscale customers, are ordinary ratepayers protected from subsidizing them?
And if billions are being invested into generation specifically to accommodate future industrial demand, what proportion of investment is simultaneously being directed toward making the existing distribution system more resilient for the people already living there?
Those aren’t anti-data-center questions.
They’re basic infrastructure-governance questions.
In fact, the best possible answer would be:
The massive investment required for AI and stadium development is accelerating modernization that makes Northwest Indiana’s electrical system dramatically better for everyone.
If that’s what’s happening, fantastic.
Document it.
Measure it.
Show the investment.
Show the reliability improvements.
Show the restoration targets.
Show the ratepayer protections.
Show how the enormous new industrial loads improve rather than strain the system around them.
That’s the beauty of systems analysis.
The answer doesn’t have to be scandalous to be interesting.
It just has to be measurable.
Mother Nature Just Established the Baseline
And that’s what makes the August 2026 outage so important.
It gives Northwest Indiana a baseline.
Before the Bears stadium.
Before the 180 MW CoreWeave expansion reaches full scale.
Before potentially thousands of additional megawatts of data-center demand.
Before hotels.
Before mixed-use districts.
Before whatever other development follows the infrastructure gravity currently forming around Hammond.
We now know what an extreme regional weather event can do to portions of the existing system.
That’s valuable information.
Painful information.
Expensive information.
But information nonetheless.
Now we get to watch what happens next.
Does NIPSCO substantially accelerate grid hardening?
Do regulators require new reliability investments?
Do data-center infrastructure projects create stronger transmission and distribution systems for surrounding communities?
Does Hammond’s potential Bears development incorporate microgrids, onsite generation, battery storage or extraordinary redundancy?
Do new utility investments improve restoration times?
Does Indiana use billions in new economic development as an opportunity to rebuild the underlying electrical architecture?
Those answers will tell us considerably more about Chicago 2.0 than another stadium rendering ever could.
Because Infrastructure Doesn’t Matter Until It Fails
Nobody talks about substations when the lights work.
Nobody discusses transmission redundancy while watching football.
Nobody thinks about distribution topology while asking ChatGPT to write an email.
Infrastructure succeeds by becoming invisible.
Until it isn’t.
Then suddenly everyone becomes an electrical engineer.
And Northwest Indiana just experienced one of those moments.
The same region currently preparing to host some of the most technologically sophisticated infrastructure ever constructed spent more than a week trying to restore electricity to portions of its existing communities after catastrophic weather.
That does not prove the region cannot support its ambitions.
Quite the opposite.
It identifies what those ambitions will require.
If Hammond genuinely wants to become the home of the Chicago Bears, a major AI-compute corridor and one of the Midwest’s most important redevelopment zones, then electricity cannot merely be plentiful.
It must be resilient.
Repairable.
Redundant.
Recoverable.
And capable of surviving the increasingly extreme conditions that infrastructure engineers are now forced to plan around.
Because a $7 billion AI development cannot wait a week for ComEd’s cousin to come over with a ladder.
A world-class NFL stadium cannot tell 60,000 people:
“Sorry guys. NIPSCO says Tuesday.”
And Chicago 2.0 probably shouldn’t require everyone living next door to own a Honda generator.
Maybe that’s the real infrastructure test Hammond is facing.
The first question was whether Northwest Indiana could generate enough power for the future.
The storm just gave us the second:
Can it keep that future turned on?
F’nAround Media
Following the infrastructure gravity until somebody remembers the extension cord.