Skip to content

Recurring series · The Intelligent Infrastructure Review

Project Spotlight

How infrastructure projects are actually structured, developed, financed, delivered, and operated.

Take one project at a time and show the whole structure — who owns it, who builds it, who pays for it, what the systems have to do, and what the surrounding community gets — so the same reasoning can be applied to the next site.

How the series works

Every spotlight, the same twelve parts

One project at a time, taken apart in the same order — so two projects can be compared without re-reading either of them.

  1. 01

    Project overview

    What it is, at what scale, and where it sits.

  2. 02

    Business or infrastructure challenge

    The condition the project exists to resolve.

  3. 03

    Stakeholders

    Every party and what they actually control.

  4. 04

    Energy and infrastructure requirements

    The technical obligations, stated as requirements.

  5. 05

    Delivery model

    Contract structure and the sequence of work.

  6. 06

    Technology or systems architecture

    Layer by layer, and how they interact.

  7. 07

    Capital structure

    Where publicly available, with sourcing stated.

  8. 08

    Community considerations

    What the surrounding area experiences.

  9. 09

    Risks and constraints

    What can go wrong and how it is held.

  10. 10

    Lessons for future projects

    What transfers to the next site.

  11. 11

    GRIDSTROM perspective

    Independent commentary, labeled as such.

  12. 12

    Related services

    Where the work connects to GRIDSTROM.

Editorial standard

Public information, clear sourcing, and no implied participation

This series analyses how projects are structured. It does not trade on private information, and it does not use analysis to imply a commercial relationship.

Public information

Drawn only from public filings, tariffs, permits, agency dockets, and published statements.

Illustrative composite

A constructed example. Not a real project, not a named owner — used to show how the variables interact.

Published with owner approval

Project-specific detail published with the written approval of the project owner.

  • Only public information is used unless the project owner has provided written approval for additional detail.
  • GRIDSTROM participation is never implied. Every spotlight states GRIDSTROM's relationship to the project explicitly, and the default is no involvement.
  • Illustrative or hypothetical projects are labeled as illustrative on the page, in the overview facts, and beneath the project map.

The recurring visual

Every project is mapped the same way

Ten roles, four bands. The map shows who sets the requirement, who builds it, who enables it, and what the surrounding community receives.

  1. 01

    Owner

    Holds the asset and the operating requirement.

  2. 02

    Developer

    Assembles site, entitlements, and structure.

  3. 03

    Utility

    Controls service capacity and energization.

  4. 04

    EPC

    Single-point delivery of the built system.

  5. 05

    Engineers

    Design, studies, and performance criteria.

  6. 06

    Contractors

    Civil, electrical, and mechanical execution.

  7. 07

    Technology providers

    Equipment, controls, and software.

  8. 08

    Capital providers

    Funds construction and long-term ownership.

  9. 09

    Public stakeholders

    Permitting, oversight, and public interest.

  10. 10

    Community outcomes

    What the surrounding area actually receives.

Project map

Direction · Delivery · Enablement · Outcome

01Direction

Sets the requirement and controls whether the project can proceed

  • Owner

    Campus ownership entity

    Holds the asset and the tenant obligation.

  • Developer

    Data-center developer

    Site, entitlements, phasing, delivery oversight.

  • Utility

    Distribution utility

    Controls capacity allocation and the upgrade schedule.

02Delivery

Converts the requirement into a built, commissioned system

  • EPC

    Design-build contractor

    Single-point delivery of buildings and electrical works.

  • Engineers

    Owner's engineer + design engineers

    Performance criteria and interface ownership.

  • Contractors

    Civil, electrical, mechanical trades

    Execution under the EPC agreement.

03Enablement

Supplies the equipment, the capital, and the public authority

  • Technology providers

    Generation, storage, switchgear, controls vendors

    Competitively selected inside a fixed architecture.

  • Capital providers

    Infrastructure equity, construction debt, term lender

    Draws gated on energization milestones.

  • Public stakeholders

    County planning, air authority, fire authority

    Land use, generation permits, life safety.

04Outcome

What the surrounding area actually receives

  • Community outcomes

    Host community

    Closed-loop water, limited generation hours, grid services, tax base.

Project map from Project Spotlight No. 01 — An AI Campus Behind a Constrained Substation. Illustrative structure; no organization is identified.

Latest spotlight

An AI Campus Behind a Constrained Substation

A 120 MW compute campus where the controlling milestone was energization, not construction

The challenge

Construction of the first two data halls could complete in roughly 18 months. Full utility service depended on an upstream substation upgrade with a multi-year schedule controlled by neither the owner nor the developer. Without a change in structure, the campus would sit finished and unenergized while the tenant's compute commitments moved elsewhere.

Lessons for future projects

  • Energization date, not substantial completion, should drive the capital and leasing schedule.
  • Contracting the energy scope separately lets it follow the utility timeline instead of the building timeline.
  • Designing the distribution backbone at full-build capacity is usually cheaper than rebuilding it at phase three.

The series

All spotlights

Each one covers a different asset class, delivery model, and capital structure.

Written for

Everyone who has to make a project work

Each spotlight is written so a developer, a lender, an engineer, and a public agency can all read the same document.

  • Developers
  • Data-center and AI infrastructure teams
  • EPC firms
  • Engineers and contractors
  • Utilities
  • Investors and infrastructure funds
  • Commercial property owners
  • Public agencies
  • Economic-development organizations
  • Procurement and operations executives
The Intelligent Infrastructure ReviewAI, Energy, Data Centers and RoboticsPublished by GRIDSTROM Energy Solutions

Follow Project Spotlight

Each spotlight is sent as it publishes — one project, fully structured.

Content preferences

Only what is listed above is collected. No third-party sharing. Every issue carries an unsubscribe and preference-management link.

Have a project you want structured this way?

Bring a site, a load, or a delivery structure you are working through. If you own a project and want it profiled with named detail, that is published only with your written approval.