Skip to content

Project Spotlight · No. 01

An AI Campus Behind a Constrained Substation

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

Illustrative projectIllustrative composite

This project is illustrative. It is not a real project and no owner, operator, or site is identified. It is published to show how the variables interact.

GRIDSTROM did not participate in this project. Analysis is independent commentary.

The Intelligent Infrastructure Review · August 1, 2026 · 9 min read

Project overview

A developer secures a 60-acre parcel in a metropolitan fringe market and takes it to a hyperscale tenant as a phased AI compute campus. Land, zoning, water, and fiber all clear early. The binding condition is the distribution substation two miles away, which has committed capacity to other queued projects and a planned upgrade several years out. The project is restructured around that single fact: phased load, on-site generation and storage for the first phase, and full utility service timed to the upgrade.

Asset type
Phased AI compute campus
Design load
120 MW at full build
First phase
24 MW, energized ahead of utility upgrade
Site
60 acres, metropolitan fringe
Nature
Illustrative composite

Business and infrastructure challenge

The asset could be built years before it could be powered

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.

  • Tenant commitments dated against energization, with penalties for slip
  • Queue position behind other large loads in the same feeder area
  • Long-lead transformer and switchgear procurement
  • Carrying cost on land and construction debt during any energization gap

Project map

Who holds what on this project

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.

Illustrative structure. Parties are described by role; no organization is identified.

Stakeholders

Each party and what it controls

Owner

Campus ownership entity

Holds land and the long-term asset; signs the tenant agreement.

Developer

Data-center developer

Site assembly, entitlements, tenant structure, delivery oversight.

Anchor tenant

Compute operator

Defines load profile, redundancy tier, and phasing dates.

Utility

Investor-owned distribution utility

Service study, capacity allocation, upstream upgrade schedule.

EPC

Design-build contractor

Single-point delivery of buildings, electrical infrastructure, and commissioning.

Owner's engineer

Independent engineering firm

Reviews design against operating criteria on behalf of ownership and lenders.

Capital

Construction lender and infrastructure equity

Funds phases against defined energization and lease milestones.

Public agencies

County planning, air permitting, fire authority

Land use, on-site generation permits, life-safety review.

Energy and infrastructure requirements

Stated as obligations, not preferences

Full-build capacity
120 MW
Reached across four phases rather than a single service request.
Phase-one capacity
24 MW
Sized to what on-site resources and existing service could carry.
Redundancy
Concurrently maintainable
Any distribution element can be serviced without dropping compute load.
Storage
Multi-hour battery system
Bridges transitions, shaves peaks, and supports ride-through.
Interconnection
Transmission-adjacent long term
Distribution service for phase one; higher-voltage service at full build.
Water
Closed-loop cooling
Chosen partly to reduce permitting and community exposure.

Delivery model

Phased design-build with an owner's engineer and a separate energy infrastructure scope

The buildings were delivered under a conventional design-build agreement. The energy scope — on-site generation, storage, medium-voltage distribution, and controls — was contracted separately so it could start earlier and follow the utility schedule rather than the building schedule. An owner's engineer held the interface between the two, and commissioning was written as a joint acceptance test rather than two independent handovers.

  1. Step 01

    Feasibility

    Load study, utility capacity screening, and energization-date scenarios before land closing.

  2. Step 02

    Structuring

    Phasing plan, tenant milestones, and capital draws aligned to energization rather than substantial completion.

  3. Step 03

    Early works

    Long-lead equipment orders and on-site electrical infrastructure ahead of vertical construction.

  4. Step 04

    Phase-one delivery

    First data halls, on-site generation and storage, controls integration, joint commissioning.

  5. Step 05

    Utility transition

    Cutover to full utility service as the substation upgrade completes; on-site assets shift to a supporting role.

  6. Step 06

    Operations

    Ongoing dispatch, demand management, and performance reporting against the original criteria.

Technology and systems architecture

Layer by layer, and how they interact

  1. 01

    Service and distribution

    Medium-voltage campus loop with sectionalizing, designed at full-build capacity so later phases add equipment rather than rebuild the backbone.

  2. 02

    On-site generation

    Dedicated generation sized to phase-one load, permitted for continuous duty in early phases and reduced-hours operation after utility service arrives.

  3. 03

    Battery energy storage

    Multi-hour system supporting transitions, peak management, and ride-through between source changes.

  4. 04

    Controls and dispatch

    A single control layer sequencing utility, generation, and storage, with defined priorities and failure modes rather than device-level automation.

  5. 05

    Compute environment

    High-density halls with liquid-ready provisioning; load profile shared with the energy layer so dispatch reflects real behavior.

  6. 06

    Monitoring and reporting

    Metering at each interface, producing the evidence base for lender reporting, tenant SLAs, and utility coordination.

Capital structure

Where it comes from, and what each source does

Disclosure

Illustrative structure. No figures are attributed to any real project, and no capital terms are represented as market rates.

Infrastructure equity

Land, development cost, and first-loss position.

Construction debt

Drawn against phase milestones tied to energization.

Term financing

Refinances construction debt once the anchor lease is operating.

Equipment financing

Applied to generation and storage assets with their own useful-life profile.

Public participation

Where applicable, local infrastructure or workforce programs — disclosed in public filings.

Community considerations

What the surrounding area experiences

Load added without shifting cost to ratepayers

On-site resources carry early load, so the campus does not rely on capacity that other customers are waiting for. Cost allocation for the upstream upgrade is defined in public utility filings rather than negotiated privately.

Local emissions and noise

On-site generation is sited, enclosed, and permitted with continuous-duty limits, and reduced after utility service arrives. Both are conditions of the air and land-use permits, not voluntary commitments.

Water

Closed-loop cooling reduces consumptive use, which is often the single most visible community concern for a campus of this scale.

Employment and tax base

Construction employment is substantial and temporary; operating employment is smaller and long-term. Both should be stated plainly rather than combined into one headline number.

Grid services

Storage and flexible load can be made available to the utility during system peaks, converting a large load into a partially dispatchable resource.

Risks and constraints

What can go wrong, and who holds it

Utility upgrade slips beyond its published schedule
ResponsePhase-one design does not depend on the upgrade; later phases are contractually gated on confirmed capacity.
Long-lead equipment delays
ResponseTransformers and switchgear ordered during structuring, before design is fully complete, with specification tolerances.
Air permit conditions restrict generation hours
ResponsePermit limits set the phase-one load ceiling; storage absorbs the variance rather than additional generation.
Tenant load profile differs from the design assumption
ResponseControls tuned during a monitored ramp period; storage duty cycle re-specified before later phases commit.
Interface gaps between building and energy scopes
ResponseOwner's engineer holds interface ownership; joint commissioning is a condition of acceptance for both contracts.
Community opposition at permitting
ResponseWater, noise, and emissions positions established before the first hearing, with the evidence public.

Lessons for future projects

What transfers to the next site

  1. 01

    Energization date, not substantial completion, should drive the capital and leasing schedule.

  2. 02

    Contracting the energy scope separately lets it follow the utility timeline instead of the building timeline.

  3. 03

    Designing the distribution backbone at full-build capacity is usually cheaper than rebuilding it at phase three.

  4. 04

    Permit conditions on generation are a load constraint and belong in the load model, not in a compliance appendix.

  5. 05

    Interface ownership between scopes is worth more than any single equipment decision.

GRIDSTROM perspective

Sequence is the design decision

In projects of this shape, the technology choices are rarely what separates a working outcome from a stranded one. The separating factor is whether the schedule was built around the one milestone the owner does not control. GRIDSTROM works these projects backwards from confirmed energization, then determines what on-site architecture is justified by the gap.

GRIDSTROM did not participate in this project. Analysis is independent commentary.

  • Model energization as a range with named dependencies, not a single date.
  • Size on-site resources to the gap, not to the full build.
  • Specify system behavior — transitions, priorities, failure modes — before selecting equipment.
  • Keep vendor-neutral selection inside a single accountable architecture.

Structure your project with GRIDSTROM

GRIDSTROM engineers and delivers integrated energy systems for data centers, AI and robotics facilities, fleets, commercial portfolios, and public infrastructure. Bring a site, a load, or a structure you are working through.

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.

We send occasional analysis only. No third-party sharing. Unsubscribe at any time.