Who carries the data-center bill: Indiana's upgrades, diesel backup and a regulator's plea
Three pieces Utility Dive published on 10 November look at the same pressure from different ends: large new loads are arriving faster than the grid can be built, and someone has to absorb the gap.
The first is money in the rate base. Indiana's commission approved AES Indiana's $737 million plan for a 390 MW Google data center, and $73.8 million of network upgrades will be recovered from all customers, not only Google. The commission's reasoning was that upgrades driven by one customer can still benefit the system; consumer advocates say the cost causer should pay. AES says Google's contract recovers the incremental costs anyway, but key prices are redacted (Utility Dive).
The second is the backup fleet. An opinion piece by executives of Inlyte Energy, an iron-sodium battery developer, and former FERC chairman Jon Wellinghoff, an adviser to the company, describes emergency orders letting PJM call on diesel generators at data centers, most recently during an unseasonably warm 13 to 16 October. They count 13 such uses of federal authority this year, seven in PJM, and cite a study finding that running Northern Virginia's data-center generators to permitted limits would raise the region's nitrous oxide emissions by 45%. Their warning is that an emergency exception becomes the normal source of capacity; their proposed alternative is battery storage, which is also what they sell (Utility Dive).
The third is trust. Minnesota PUC vice chair Joseph Sullivan, interviewed at the NARUC meeting, names affordability as the top challenge, says hearings are becoming more contentious, and asks utilities for "a breather" from rate cases. He points to demand-side programmes that, by his account, keep the state's system about 20% smaller than it would otherwise be, and to a state law that makes data centers pay into the weatherization fund (Utility Dive).

What connects them
Each case moves a cost of new load onto someone who did not ask for it: Indiana's households through transmission rates, residents near data centers through generator exhaust and noise, and all ratepayers through a pace of rate cases that a regulator himself calls painful. The tools differ, cost allocation rules, environmental review, efficiency programmes and dedicated levies, but each one only works if the public can see the numbers.
The open question
Indiana's redactions are the sharpest example. A rule that large customers reimburse at least 80% of the costs allocable to them cannot be checked by other customers when the contract terms are hidden. Sullivan's point about transparency and lost trust applies there directly.