Grid Impact, Energy-Systems Integration & Grid Services

The data center industry's relationship with the grid used to be a single transaction: buy firm power, pay the bill, never think about it again. The facility was a price-taking, always-on, inflexible block of demand, and the grid was sized to serve it. That arrangement broke down around 2024, when a single AI campus grew large enough that its interconnection request could move a balancing authority's entire load forecast. A 1 GW campus is no longer a customer the grid serves. It is a system-scale event the grid has to plan around, and a load that large is also one the system operator can ask to curtail or shift in return.

This chapter is the canonical home for flexibility: the property that turns an AI load from a passive liability in the interconnection queue into an active, dispatchable, sometimes revenue-generating grid resource. Four decisions organize it: the interconnection posture (firm or flexible), the co-location / behind-the-meter question (bypass or integration), the grid-services stack (what you can sell, and to whom), and the social-license / carbon dimension that increasingly gates whether a project is permitted at all. Behind all four runs the flexibility-unlocks-headroom thesis: the cheapest gigawatt is the one already on the grid, and you reach it by agreeing to get out of the way for a handful of hours a year instead of building new generation. How a facility rides through and supports the point of interconnection is in Chapter 4.10, the queue and speed-to-power story is in Chapter 3.2, and the macro load-growth narrative is in Chapter 16.1. Here they meet as a strategy.

Every other decision in this chapter descends from one choice, made the day you file an interconnection request: do you ask the grid to serve you unconditionally, or do you offer to limit your draw under defined conditions? Firm service asks the utility to build for your full peak under its tariff's service class, planning criteria and interruption rights. If serving that peak takes new transmission or generation, you wait on the reinforcement schedule, which in constrained markets often runs to years (Chapter 3.2 covers the large-load studies and network upgrades that set that schedule). The service label carries no standard timeline, so price the signed in-service date and its remedies.

The flexible path inverts the logic. If you agree to curtail, shedding or shifting load for a bounded number of hours when the system is tight, the utility may study a lower service obligation under its tariff. It can use headroom between average and peak system conditions only if the local network, delivery conditions and enforceable curtailment rights support your connection. A Duke University Nicholas Institute planning study sized that headroom nationally. Under its assumptions, the existing US grid could absorb ~98 GW of new load at an average curtailment of just 0.5% of annual load, roughly 44 full-curtailment-equivalent hours per year, rising to ~126 GW at 1.0% (Duke Nicholas Institute, 2025). That is a modeled national technical potential. It does not show that the announced AI build-out can connect without new plants, because the requested site, dispatch duration and local network may miss the modeled case. The headroom is also uneven: PJM alone holds ~18 GW of it at 0.5%, MISO ~15 GW, ERCOT and SPP ~10 GW each, Southern Company ~8 GW.

Choosing flexible is a trade you must be able to price: you exchange a contractually bounded reduction or shift in useful work for a potentially multi-year gain in speed-to-power. Six months of earlier billable service on a 200 MW phase brings forward roughly $1.2–1.3B of gross revenue at SemiAnalysis's June 2026 rental estimate (Chapter 2.2 works the example). Set the curtailment and recovery cost against your own contracted margin on that service, not the gross figure, and only where the workload mix can absorb a few dozen interruption-hours a year without breaching its SLAs. That proviso is a workload question, so this chapter sends it back to scoping. → archetype-level interruption tolerance in Chapter 1.1.

"Flexible load" is not one thing. When the grid calls, a data center has four main levers, and they differ enormously in cost, speed and blast radius. Choosing which lever answers a given call is the operational core of grid-interactive operation. Get the assignment wrong and you either break an SLA or leave money and headroom on the table.

Shed (curtail compute). Pause or kill interruptible work (batch inference, evaluation sweeps, fine-tuning, internal jobs) and let the power draw fall. This is the purest form of demand response, and the cheapest per hour if the displaced work is genuinely deferrable. The cost is lost goodput: every shed hour is compute you did not sell. Google's fleet is the canonical proof point. It has signed ~1 GW of demand-response capacity across utilities (Indiana Michigan Power, TVA, Entergy Arkansas, Minnesota Power, DTE) by committing to shift or pause machine-learning workloads when grids are stressed (Google, March 2026). Single-campus contracts now write the lever in too. Georgia Power's deal for OpenAI's 3.2 GW Project Camellia campus (announced 2026-07-22, phased 2028–2032) provides up to 1 GW of flexible demand response, and the Georgia PSC approved it in August 2026. When statewide demand peaks, the utility can cut deliveries to the site. Georgia Power says that lowers how much new generation it must build, and it ranks the commitment among the largest single-facility demand-response deals in the US.

Shift (move compute in time or space). Rather than destroying the work, relocate it: defer batch jobs to off-peak hours, or migrate flexible workloads to a sister site in a region that is not constrained. This preserves eventual completed work for deadline-flexible jobs, but checkpointing, migration, idle capacity, bandwidth and deadline misses reduce time-bounded goodput. It is a valuable lever and the hardest to engineer, because it needs a scheduler that is power-aware and carbon-aware across a fleet. → power-aware orchestration in Chapter 16.3.

Ride through (UPS / BESS discharge). Hold compute draw constant and supply the curtailed grid energy from on-site storage, either the UPS battery or a dedicated grid-scale BESS, for the duration of the event. The workload stays within its SLO only if transfer, duration and recovery have been tested. The cost is the storage capex and round-trip losses. The constraint is duration: a ride-through UPS sized for seconds to minutes cannot cover a multi-hour demand-response window unless it is grossly oversized or paired with a true BESS. This is where the UPS stops being a reliability device and becomes a grid asset. → Chapter 4.5.

Fail over (on-site generation). Hold compute constant and replace grid energy with already-hot or qualified fast-start gas turbines, reciprocating engines or fuel cells. This turns a grid-curtailment event into a generation-dispatch event, at the cost of fuel, emissions and standby-plant capex, and it is the lever that blurs into the co-location question below. Dedicated nuclear belongs under continuously operating firm primary or co-located supply, not standby: after a trip it requires stable off-site supply and can take a day or more to restart.

A fifth, smaller lever: cooling. In EPRI's DCFlex results (September 2026), thermal mass, precooling, relaxed setpoints and thermal storage can let the cooling plant draw less for tens of minutes or longer, depending on the architecture. That can cover a short call with no change to compute. The limit is how far the IT inlet or coolant supply temperature can rise, and the rebound when cooling catches up counts against your withdrawal cap. → setpoint and thermal-transient limits in Chapter 5.12.

The four main levers form a stack: a well-engineered facility uses the cheapest lever that satisfies the call and reserves the expensive ones for deep, rare events. Shedding batch can suit a shallow, frequent curtailment when the lost contribution is low. A deep, multi-hour event needs enough BESS energy or permitted on-site generation after the protected reserve. Neither depth nor duration alone promises that the revenue-bearing inference fleet never blinks. Operators go wrong by committing a single lever to the utility ("we will shed 100 MW") when the value comes from committing curtailment terms (depth, duration, notice) the facility can meet with whichever lever is cheapest at the moment of the call.

When the grid cannot energize you fast enough, you bring your own power, and how you connect it to the grid is itself a strategic choice with very different consequences. Behind-the-meter (BTM) bypass islands the generation: a gas plant or fuel-cell farm feeds the data center directly, the campus draws little or nothing from the grid, and there is no export and minimal grid interaction. This is the speed-to-power play. Cleanview's 'Bypassing the Grid' tracker listed ~90 GW of announced behind-the-meter generation across 59 US data centers by mid-2026, largely gas turbines and engines. Of that, ~82 GW was announced since January 2025, ~2 GW is operating and ~1 GW is under construction. Developers differ, with some planning to stay off-grid and others to connect later. The appeal is speed: the plant can start before grid service arrives. A bridge plant that plans to connect later still needs its place in the queue. The cost is that you have built and must operate a merchant power plant, with the emissions, fuel exposure and O&M that implies, and you forgo the reliability backstop of a grid connection.

Co-located integration is the opposite posture. The generation and the load both connect to the grid, synchronized and metered, so the campus can draw, export and provide services in either direction, but only to the extent its metering, permits and executed service rights authorize each action. This is harder to permit and slower to stand up. It turns the on-site plant into a grid asset instead of a grid bypass, and it preserves the option to sell capacity and energy back. Until recently the choice between bypass and integration was left to bilateral negotiation and a patchwork of utility tariffs. In December 2025 that changed for the largest US market.

Price the right you can actually deliver. The annual call energy is 5 MW × 10 × 2 h = 100 MWh. Receipt is $225,000; displaced-work cost $80,000; recovery energy $2,000; controls $50,000; expected penalties $20,000. Net value is about $73,000/year, so accept the bounded offer if the dispatch and recovery tests pass. The break-even availability price is $152,000 ÷ 5 MW = about $30,000/MW-year. At the offered price, the lost-contribution crossover is ($225,000 − $72,000) ÷ 100 MWh = about $1,500/MWh. At $2,000/MWh of lost contribution, net value becomes −$47,000/year, so reject the offer or narrow the commitment. Loss of tenant dispatch consent, a recovery deadline the queue cannot meet, or any use of the protected 4 MWh is an independent reason to reject, even above the price crossover. Measure import reduction and rebound at the settlement boundary. The carbon inventory follows Chapter 15.3 and makes no automatic avoided-emissions claim. → test the electrical reserve in Chapter 4.5 and service obligations in Chapter 3.2.

Once a facility is flexible and grid-synchronized, it can monetize that flexibility through a layered stack of grid products. The stack matters because the products differ in value, in the response speed they demand, and in whether they can be combined ("stacked") on the same megawatt or selling one forecloses another. For most operators, grid services are a siting accelerant first and a revenue stream a distant second: the headroom they open is worth more than the payments they earn.

Demand response and interruptible-load credits sit at the base: you are paid, or given a tariff discount, for committing to curtail when called. This is the most accessible product and the one most directly tied to the speed-to-power benefit. Capacity payments reward you for being available to curtail during the system's tightest hours. PJM's capacity market accredits a demand resource that reliably sheds on call, much as it accredits a power plant. Starting with the 2027/28 delivery year, it has to be available every hour of the year instead of only in daytime peak windows (PJM, 2025). In PJM, then, the curtailment right you sell is round-the-clock. Ancillary services split by product and jurisdiction: regulation responds within seconds, spinning and non-spinning reserves commonly use ten-minute windows, and voltage support is a distinct reactive-power service. Match telemetry, duration and performance to the tariff before assigning BESS, grid-interactive UPS or controllable load. The mechanics of providing frequency response and reactive/voltage support toward the point of interconnection are engineered in Chapter 4.10. This chapter is where you decide whether to.

Most pro-formas get the stacking question wrong. The same 100 MW of UPS/BESS cannot be held in reserve for facility ride-through, committed to a capacity-market curtailment, and bid into frequency regulation at full depth all at once. The commitments overlap, and the market operator will not let you sell the same megawatt-hour twice. Real flexibility revenue comes from partitioning the resource: a slice for reliability, a slice for capacity, a slice for fast ancillary services, sized so that a worst-case simultaneous call is still survivable. Over-promise the stack and a single coincident event forces you to default on a grid commitment, which costs far more than the revenue was ever worth.

The flexibility posture and the powering strategy are entangled with carbon, and the entanglement cuts both ways. A BTM-gas bypass that energizes a gigawatt two years early also adds a gigawatt of fossil generation that may run far more than the operator's clean-energy commitments imply. The speed-to-power that looks brilliant on the schedule can be a liability on the carbon account and in the permit hearing. Conversely, a grid-integrated flexible load can help decarbonize: a campus that shifts batch compute to hours of high renewable output, or curtails during fossil-heavy peaks, may lower emissions if recovery energy, destination power and backup fuel do not erase the saving. Inventory treatment still follows ownership, attributes and the method in Chapter 15.3, and a lower reported intensity alone does not prove avoided grid emissions. Flexibility is both a grid-access strategy and a carbon strategy, and the best designs exploit both. The 24/7 carbon-free-energy framing and the procurement instruments that make this real are in Chapter 15.3.

The carbon and grid footprints also feed directly into the disclosure obligations an operator now faces. Emissions reporting, grid-impact assessments and load-flexibility commitments are increasingly things you must report, not just things you do. → reporting frameworks in Chapter 15.7.

The final dimension is the one engineers most often underestimate and that most often kills a project: social license. A gigawatt campus is a community event as much as a grid event. It raises questions about who pays for the transmission upgrades (ratepayers or the data center), whether residential electricity bills rise to subsidize a hyperscaler's load, how much water the cooling plant draws from a stressed aquifer, and whether the jobs and tax base justify the strain. In 2025–2026 these questions hardened into organized opposition and into law: zoning reforms ending by-right data-center development, state large-load statutes mandating curtailability and cost-causation, and ballot-box fights over new substations.

Flexibility is, perhaps surprisingly, one of the strongest social-license arguments an operator has. A flexible load that explicitly agrees to curtail during system peaks reduces the capacity the utility has to plan for that load's peak, and that is the defensible version of the grid-asset argument. Say what you actually signed: curtailment depth, the annual energy or equivalent-hour cap, notice, event limits, and the cost-allocation terms you accepted for interconnection and network upgrades. Do not turn Duke's 0.5% of annual energy into a promise about event hours, a particular feeder's capacity, or a household's bill. It equals about 44 full-curtailment-equivalent hours, which curtailing 20% would spend across 219 hours. A commitment stated in those contract terms makes a far better public-hearing story than "we need a gigawatt of new firm power and someone has to build it," and unlike a bill guarantee it survives cross-examination. Flexibility chosen for speed-to-power also pays a second dividend in the permit hearing, which is why the most sophisticated operators lead with flexibility commitments in community engagement instead of hiding them in the tariff. The cost-causation and ratepayer-equity mechanics behind these fights are in Chapter 3.2.

Compliance is arriving too, and in ERCOT part of flexibility is already mandatory. Under Texas SB 6 (2025), a transmission-voltage load connected after 31 December 2025 must let its serving utility curtail it during firm load shed. ERCOT can also direct a load of 75 MW or more with on-site backup generation to run that plant or curtail in an energy emergency. SB 6 further directs ERCOT to build a competitively procured demand-reduction service for 75 MW-plus loads, called with at least 24 hours' notice, which a load that already curtails on wholesale price cannot join. None of this is a faster queue (Chapter 3.2).

Federally, FERC's July 2026 order RD26-7-000 tells NERC to file computational-load reliability standards and registration criteria by 31 December 2026. NERC's Phase I standards (CLO-001/002/003) passed final ballot in October 2026 and cover sites of 50 MW or more supplied at 100 kV or above, but they bind no one until NERC's Board adopts them and FERC approves them. Neither the order nor the standards set ride-through thresholds. New large loads in ERCOT (since 1 August 2026) and SPP already face ride-through rules, and PJM has proposed its own. Selling a curtailment and riding through a voltage sag are separate duties, and your controls must satisfy each. → Chapter 4.10 covers ride-through engineering and Chapter 4.3 registration.