Utilities trade faster access for data center commitments, from Ohio's 85% minimum to SPP's 90-day studies
An opinion article published by Utility Dive argues that data centers do not need special treatment to get power faster, only clearer rules about what they must give the grid in return. It was written by Seyed Madaeni, chief executive and co-founder of Verse, a company that sells battery dispatch optimisation software to data centers, so its conclusion favours tools his firm provides. The examples it cites, however, are regulatory decisions that can be checked.
In Ohio, regulators approved a settlement after AEP Ohio proposed a tariff for data centers: large customers pay for up to 85 percent of their subscribed capacity even when they use less, accept longer contracts and post more collateral. In return a moratorium on new connections was lifted. In Texas, a facility that meets ERCOT's ride-through requirements clears one step towards energisation, and under the new Batch Zero process developers can choose controllable-load or bring-your-own-generation paths, accepting curtailment under ERCOT's real-time control in exchange for earlier connection.
Southwest Power Pool offers a similar bargain through its High Impact Large Load framework. Developers that accept real-time forecast reporting, limits on how fast their demand ramps and remote disconnection can have their interconnection study completed within 90 days. In PJM, the proposed Interim Resource Adequacy Service would have let some new large loads connect even when capacity fell short of the usual reliability standard, provided they reduced consumption in limited emergencies unless they brought new capacity. The author notes that FERC rejected most of that framework in October on jurisdictional grounds while encouraging states to decide which retail customers are curtailed under stress.
The article also recalls that in June FERC directed the six regional grid operators under its jurisdiction to justify their large load tariffs or propose reforms. Its main complaint is timing: developers often learn what commitments a site requires only after spending money on it, and requirements differ from one utility to the next.

What it means
The common thread across these markets is a trade of certainty for speed: money, flexibility or data in exchange for a faster connection. Publishing those terms before site selection, as the author urges, would let developers compare locations on what they actually have to promise.