Why Peak Demand, Not Average kWh, Will Kill Data Center Projects
Part I argued flexibility is the new front door to a connection. Part II names the number underneath it: a campus can average 40% of its reserved load, look excellent on efficiency, and still be unconnectable, because the gate is peak MW, not average kWh.
Average kWh feeds the PUE narrative, the carbon inventory, the annual report. Peak MW feeds the interconnection application, the transformer order, the capacity charge, the neighbor’s reliability case, and only that audience decides whether the campus exists. A campus averaging 40% still occupies 100% of its reservation in the planner’s model. Peaks kill projects in four places, none tied to annual consumption: MW-driven connection queues (European 7–10 year waits; Texas’s 2026 ERCOT pause and audit on a hundreds-of-GW queue); equipment lead times stretching toward four years; reserved-but-unused capacity sterilizing the queue; and a single 15-minute coincident interval of IT-plus-cooling the feeder actually sees. One cause: a peak declared once and never revisited.
The fix isn’t less compute, it’s declaring which 15 minutes you plan for: orchestration that shifts non-urgent jobs, cooling that doesn’t ramp with IT, a firm tranche plus a movable flexible tranche, batteries covering the ramp, and an application stating both absolute and holdable peak. Your action this week: ask what peak you declared and whether anyone checked it against actual use. Full breakdown at renegrywnow.com.
Reflection questions
What peak did your last connection case declare, and has anyone checked it against what the site actually uses?
Does page one of your data-center case lead with peak MW and 15-minute coincident demand, or with PUE?
Are you reserving far more than you use, and sterilizing capacity the next project needed?
Keywords: Peak Demand, Coincident Peak, Transformer Lead Time, ERCOT Interconnection, Capacity Charge, Reserved vs Used, 15-Minute Interval, PUE, Data Center Gate, Physical AI
Series: Energy Dominance · Week 42 · Part II
Previous: Part I: Flexible AI Data Centers: When Compute Must Follow the Grid.
