AES-Led Grid 2.0 Protocol Would Give New Loads Firm Service Plus Three Tiers of Flexible Service
- Flexible service tiers: 3 plus firm
- Peak hours cited: 30 hours per year
- Authors: 5 (4 AES, 1 Fluence)
- Operators with connect-and-manage plans: PJM, SPP, ERCOT
- Document: G2TF RFC #1
A team led by AES Corporation senior vice president Chris Shelton published a proposed Grid 2.0 protocol on August 17, 2026. The protocol is a standardized way to connect new loads and new generators without waiting for the grid to be built out first. It gives each interconnection customer a block of firm service plus three progressively less assured tiers of flexible service. The authors argue that planners overbuild for peak periods that last as little as 30 hours per year. Any utility or transmission operator could adopt the protocol voluntarily.
What the Protocol Proposes
The core idea is to separate system access from traditional reliability planning. Today a new large load or generator waits until studies show the network can serve it firm at every hour. Grid 2.0 would instead sell a graded product. A customer takes some firm service and accepts curtailment on the rest, and the grid protects itself automatically rather than through a queue. The protocol also treats new storage projects as network-directed buffers, which reduces how often the operator has to call on that flexibility at all.
This is not a new concept so much as an attempt to standardize one. PJM, SPP and ERCOT have each announced their own connect-and-manage arrangements for flexible large loads. The protocol’s authors want a common specification instead of three incompatible ones. ERCOT is the reference case. Its flexible approach for new generators is widely credited for the speed of solar, wind and storage deployment in Texas.
Why Thirty Hours a Year Drives the Design
The 30-hour figure is the argument. If the network is sized for a handful of critical peak hours, then the equipment sits underused for the rest of the year while its cost is spread across relatively few kilowatt-hours. Admitting more load under flexible terms raises utilization of what is already in the ground. The authors expect that to lower the per-unit cost of delivered electricity, because fixed costs get spread across more sales.
AJ Hall, an AES portfolio management director and a co-author, told pv magazine that version 1 will likely be deployed first with a large load rather than with generation. He said existing interconnection and transmission policy makes that the easier path. The task force plans two companion documents, one on expedited renewables interconnection and one on network-directed storage.
Who Is Behind It
Five authors wrote the document. Four work at AES and one at the storage firm Fluence. They have formed a Grid 2.0 Task Force and modeled it on the Internet Engineering Task Force, down to the request-for-comments format. The proposal is labeled G2TF RFC #1 and is open for comment. Listed supporting organizations are AES Next, Fluence, and Tapestry, a firm incubated by Google that has worked with PJM on interconnection processing.
The sponsorship is worth noting plainly. AES owns utilities and develops generation, and Fluence was originally an AES and Siemens joint venture. A protocol that speeds interconnection for large loads and renewables serves the businesses of the people proposing it. That does not make the engineering wrong, but it does mean the document is a position as well as a specification.
Why It Matters
Interconnection delay is now the binding constraint on data center siting and on new generation alike. Voluntary adoption is the protocol’s weakness and its strength. Nothing compels a utility to offer graded service, so uptake depends on whether operators see faster revenue in it. But a voluntary standard also needs no rulemaking, which means it can move faster than a FERC proceeding. Watch whether any of the three operators already running connect-and-manage programs adopts the common specification instead of keeping its own.
Critical Perspective
Thirty hours of peak is about 0.34% of the year, and the entire case for graded service rests on that sliver. The authors model their task force on the Internet Engineering Task Force, which standardized a network no single company owned. Transmission is not that, and ERCOT already showed the speed case while PJM and SPP wrote their own versions. If a customer disputes a curtailment under the least assured tier, who arbitrates a specification that no regulator approved?
Sources
- pv magazine USA, Proposed Grid 2.0 protocol would enable connect and manage for both load and generation, August 17, 2026
- Grid 2.0 Task Force, An open standard for grid service access and allocation