A Logistics Depot Electrifying Ninety Vehicles
Where the constraint was not chargers but the service entrance and the dwell window
August 1, 2026 · 8 min read
Recurring series · The Intelligent Infrastructure Review
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
One project at a time, taken apart in the same order — so two projects can be compared without re-reading either of them.
What it is, at what scale, and where it sits.
The condition the project exists to resolve.
Every party and what they actually control.
The technical obligations, stated as requirements.
Contract structure and the sequence of work.
Layer by layer, and how they interact.
Where publicly available, with sourcing stated.
What the surrounding area experiences.
What can go wrong and how it is held.
What transfers to the next site.
Independent commentary, labeled as such.
Where the work connects to GRIDSTROM.
Editorial standard
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.
The recurring visual
Ten roles, four bands. The map shows who sets the requirement, who builds it, who enables it, and what the surrounding community receives.
Holds the asset and the operating requirement.
Assembles site, entitlements, and structure.
Controls service capacity and energization.
Single-point delivery of the built system.
Design, studies, and performance criteria.
Civil, electrical, and mechanical execution.
Equipment, controls, and software.
Funds construction and long-term ownership.
Permitting, oversight, and public interest.
What the surrounding area actually receives.
Project map
Direction · Delivery · Enablement · Outcome
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.
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.
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.
What the surrounding area actually receives
Community outcomes
Host community
Closed-loop water, limited generation hours, grid services, tax base.
Latest spotlight
A 120 MW compute campus where the controlling milestone was energization, not construction
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.
The series
Each one covers a different asset class, delivery model, and capital structure.
Where the constraint was not chargers but the service entrance and the dwell window
August 1, 2026 · 8 min read
When the investment case is measured in avoided disruption rather than energy savings
August 1, 2026 · 9 min read
Written for
Each spotlight is written so a developer, a lender, an engineer, and a public agency can all read the same document.
Each spotlight is sent as it publishes — one project, fully structured.
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.