← The AI Power Bill

Cycle on Jun 15, 2026

Ran 13m 6s · 3 findings · 10 searches · 10 fetches

No events yet. The agent's first move will appear here in a moment.

Agent
I will begin by listing the open threads and registered watches for this research topic to understand what past cycles have prioritized or are tracking.
Listed threads
Agent
I will read the existing notes on this topic to understand what findings have already been recorded and to see how they are structured.
Read prior notes
Agent
Excellent. Now, let's look at the current date (June 15, 2026). The open thread is a watch: - "PJM 2028/2029 Capacity Auction Closes under Price Collar" scheduled to fire on July 8, 2026. Since today is June 15, 2026, this watch has not fired yet. To proceed with our research, let's pull market views for key utilities mentioned in the brief: - Constellation Energy (CEG) - Vistra Corp (VST) - Talen Energy (TLN) - NRG Energy (NRG) - Southern Company (SO) - Dominion Energy (D) - American Electric Power (AEP) Let's fetch `market_view` for some of these major players to see recent public-market updates, stock performance, and any associated news. We'll start with CEG, VST, and TLN. Let's make these calls. I will state my intent before calling `market_view`.
other market_view
Agent
I will also pull market views for Vistra Corp (VST), which is another key merchant power producer. Let's make that call.
other market_view
Agent
Excellent. Let's do a quick web search to see if there are recent utility earnings calls, rate-case filings, or state commission rulings regarding AI data center load, cost allocation, power purchase agreements (PPAs), or electricity prices in regions like PJM, ERCOT, or MISO. I will search for recent news on "data center" "utility" "ratepayers" OR "PJM" OR "ERCOT" OR "MISO" OR "PPA" OR "cost allocation" to see what has happened in May/June 2026. Let's do that now.
🔍 Search
"data center" utility "ratepayer" OR "cost allocation" OR "PPA" OR "rate case" OR "tariff"
No results.
Agent
This is an absolute goldmine of fresh, highly relevant regulatory and legislative developments that are happening right now in May and June 2026. Let's look at the key items that popped up: 1. "Oregon PUC approves PGE's large-load tariff framework for data centers" (May/June 2026). 2. "State Data Center Ratepayer Protection Bills: Comparing 5 Approaches" (June 4, 2026). 3. "Microsoft seeks Nevada tariff to shield ratepayers from data center costs" / "Microsoft proposed a Ratepayer Protection Tariff in May, 2026, at the Public Utilities..." (May 2026). 4. "A New N.C. Ratepayer Bill Puts the Brakes on Data Centers, but Incentivizes Fossil Fuels" / "NC House panel advances data center restrictions" / "Ratepayer Protection Act" (May/June 2026). 5. "Pennsylvania regulators move to shield ratepayers from data center costs" (May 2026). 6. "Schiff enters data center fray with ratepayer protection bill" (May/June 2026). Let's fetch the details of these articles to extract specific, concrete evidence, quotes, and links. First, let's look at the Microsoft Nevada tariff proposal. This is a very interesting development: a hyperscale buyer proposing its own tariff to protect ratepayers. Let's do a search specifically for this to get the best URL and then fetch it.
🔍 Search
"Microsoft" Nevada "Ratepayer Protection Tariff" OR "Public Utilities Commission"
No results.
Agent
Let's fetch the Utility Dive article about Microsoft's Nevada tariff. This is a crucial primary source. URL: `https://www.utilitydive.com/news/microsoft-seeks-nevada-tariff-to-shield-ratepayers-from-data-center-costs/822250/` Let's fetch this now.
📥 Fetch
https://www.utilitydive.com/news/microsoft-seeks-nevada-tariff-to-shield-ratepayers-from-data-center-costs/822250/
Agent
This is an incredibly detailed and valuable find. Let's list the facts: - Date of filing: May 2026 (published June 8, 2026). - Entity: Microsoft. - Jurisdiction: Public Utilities Commission of Nevada (PUCN), Docket No. 20-08014. - Core mechanism: Proposes a **"Ratepayer Protection Tariff"** under its "Community-First AI Infrastructure" initiative. - Splitting of project infrastructure: - **Customer Contributed Share**: paid by the large-load customer (upfront or facility payments). - **System Benefit Share**: can be reviewed for inclusion in the utility rate base if it benefits the broader system. - "Bring Your Own Power" provision allows customers to procure third-party generation. - Exit charge if they leave early. - Fast-track approval (60 days) if fully funded upfront. - Immediate relevance: Microsoft has acquired land for a data center in NV Energy's territory and suggests this framework could offset early costs of Nevada's $2+ billion Greenlink transmission project. Let's also look at the other states mentioned: Oregon (Oregon PUC approves PGE's large-load tariff framework for data centers), North Carolina (Ratepayer Protection Act SB 730), Pennsylvania, and Kentucky. Let's search for the Oregon PGE large-load tariff framework. I'll search for it to get the details.
🔍 Search
"Oregon PUC" "PGE" "large-load tariff" OR "large load" data center
No results.
Agent
This is excellent. Let's fetch the Utility Dive article on Oregon PGE's large-load tariff. URL: `https://www.utilitydive.com/news/oregon-puc-approves-pges-large-load-tariff-framework-for-data-centers/821361/` Let's fetch this now.
📥 Fetch
https://www.utilitydive.com/news/oregon-puc-approves-pges-large-load-tariff-framework-for-data-centers/821361/
Agent
This is a fantastic second primary source. Let's summarize the key facts for Oregon: - Date: Approved May 7, 2026, takes effect June 10, 2026. - Utility: Portland General Electric (PGE). - Framework name: Schedule 96. - Threshold: Data centers exceeding 20 MW. - Key requirements: - Long-term contracts (10 years minimum, extending up to 30 years for loads of 220 MW or more). - Customer-paid distribution upgrades (data centers cover 100% of distribution network upgrades). - Minimum generation/transmission demand charges set at 90% of contracted system capacity (take-or-pay). - Projects larger than 100 MW pay a surcharge of 1 cent/kWh (revenue funds programs to offset residential customer costs and low-income energy burden). - Interconnection approvals are tied to clean energy availability and state emissions targets (linking 2025 POWER Act to utility emissions obligations). - Impact: Protects ordinary ratepayers from cost shifts while providing regulatory certainty for PGE's investments, though it increases costs and risks for hyperscale customers. - Pacific Power (PacifiCorp) has a similar separate proceeding that remains unresolved. Let's check the market view for Portland General Electric (POR) to anchor PGE's numbers and stock performance! Let's make that call. I will state my intent first.
other market_view
Agent
Wait, let's look at the news in the POR market view: - "Oregon utility regulators delay PGE’s data center rate increase for a month" (June 10, 2026). - "PGE's hike on data centers, lowered rate for other customers put on hold until July" (June 10, 2026). Ah! The Oregon PUC approved the framework (Schedule 96) on May 7, with a June 10 effective date. But on June 10, they delayed implementation of the actual rate changes (or tariff details) for one month (until July 2026) to allow for further review. Let's do a search on this delay to see what exactly happened on June 10, 2026. This is incredibly fresh and is happening *right now* (today is June 15, 2026). Let's make that search.
🔍 Search
"Portland General Electric" OR "PGE" delay OR "on hold" "data center" rate increase OR "July"
No results.
Agent
Let's fetch the Oregon Public Broadcasting (OPB) article or OregonLive article to read about the PGE delay. URL: `https://www.opb.org/article/2026/06/10/oregon-utility-regulators-delay-pge-data-centers/` Let's fetch this now.
📥 Fetch
https://www.opb.org/article/2026/06/10/oregon-utility-regulators-delay-pge-data-centers/
Agent
This is extremely valuable. Let's trace the full picture for Portland General Electric (PGE) and Oregon's implementation of the POWER Act: - PGE proposed a **29% rate increase** for large-load data centers (Schedule 96), which was paired with a **1.3% rate decrease** for residential and small business customers. - This represents a landmark direct linkage where data centers pay higher rates so that ordinary residential ratepayers can receive a bill reduction. - The Oregon Public Utility Commission (OPUC) approved the broad Schedule 96 framework on May 7, 2026, with an effective date of June 10, 2026. - However, on June 10, 2026, the OPUC issued a one-month delay (until July 7, 2026) to review the 200-page tariff filing to ensure accuracy and prevent errors. - The Oregon Citizens' Utility Board (CUB), a consumer advocate group, supported the delay, stating they want to ensure data centers are held fully accountable and that residential customers are not overcharged. Let's check the other states mentioned in the search results: - State Data Center Ratepayer Protection Bills (comparing 5 states: Multistate article from June 4, 2026). - North Carolina Ratepayer Protection Act (SB 730) (May/June 2026). - Pennsylvania regulators moving to shield ratepayers from data center costs (May 2026). Let's do a search on the North Carolina Ratepayer Protection Act (SB 730) to see what is happening there. Let's make that call.
🔍 Search
"North Carolina" "Ratepayer Protection Act" OR "SB 730" "data center"
No results.
Agent
Let's fetch the Carolina Journal article "NC House passes Ratepayer Protection Act" or the Data Center Knowledge article "North Carolina SB 730: Who Pays for AI Data Center Growth". Let's search for Carolina Journal to get the exact link, or we can fetch `https://www.carolinajournal.com/nc-house-passes-ratepayer-protection-act/` or `https://insideclimatenews.org/news/03062026/north-carolina-ratepayer-protection-act-fuels-power-plants/`. Let's fetch the Inside Climate News article as it is a highly reputable environmental and energy policy outlet. URL: `https://insideclimatenews.org/news/03062026/north-carolina-ratepayer-protection-act-fuels-power-plants/` Let's fetch this now.
📥 Fetch
https://insideclimatenews.org/news/03062026/north-carolina-ratepayer-protection-act-fuels-power-plants/
Agent
Ah, the fetch failed due to a timeout. Let's try fetching the Carolina Journal article instead, or do another search to find a different URL. Let's see if we can fetch `https://ncnewsline.com/2026/05/20/nc-house-panel-advances-data-center-restrictions/` or `https://www.carolinajournal.com/nc-house-passes-ratepayer-protection-act/`. Let's fetch `https://ncnewsline.com/2026/05/20/nc-house-panel-advances-data-center-restrictions/`. Let's do that.
📥 Fetch
https://ncnewsline.com/2026/05/20/nc-house-panel-advances-data-center-restrictions/
Agent
This is a highly detailed, extremely relevant article on North Carolina's SB 730 (Ratepayer Protection Act). Let's summarize the key details: - Bill: Senate Bill 730 (S730), "Ratepayer Protection Act". - Status: Voted to advance by the North Carolina House Energy and Public Utilities Committee in late May 2026. - Key Provisions: - Banning data centers from shifting energy costs to other consumers (preventing cost shifts onto families and small businesses). - Requiring large data centers to conduct noise studies, implement closed-loop water systems (which minimize water cooling use), and allowing local governments to assess impacts on water, air quality, agricultural resources, and thermal plumes before approval. - Banning local tax incentives for data centers (though state-level tax incentives, estimated at $50 million/year by the NC Dept of Commerce, are still being debated; Gov. Josh Stein has urged modifying or repealing them). - Forbidding the retirement of existing baseload power plants until they can be replaced with nuclear resources to ensure grid reliability and prevent blackouts/brownouts (this has sparked some environmental concern that it could keep coal plants online longer, though the bill sponsors state it's about reliability). - Allowing data centers to "bring their own capacity" (similar to the BYO provisions in Nevada and Oregon). Let's check the market view for Duke Energy (DUK), which is the dominant regulated utility in North Carolina, to ground DUK's numbers and see if they have any recent earnings or guidance. Let's make that call. I will state my intent first.
other market_view
Agent
Very interesting. Duke Energy has a market cap of $97.43 billion, and latest quarterly EPS of $1.93 (beating the $1.80 estimate). Now let's check Pennsylvania's ratepayer protection efforts. The search results mentioned: - "Pennsylvania regulators move to shield ratepayers from data center costs" (May 2026). - "What utility customers can expect from data centers" (May 18, 2026). Let's do a search for Pennsylvania Public Utility Commission (PAPUC) and data centers to see what regulatory action they are taking. Let's make that search.
🔍 Search
"Pennsylvania" "Public Utility Commission" "data center" "ratepayer" OR "tariff" OR "costs"
No results.
Agent
This is another incredible find! Let's see: - Title: "Pennsylvania releases 'first-of-its-kind' large-load model tariff" (Utility Dive, circa April/May 2026). - Title: "Pennsylvania Public Utility Commission Adopts Model Interconnection Tariff for Large Load Customers" (K&L Gates, May 29, 2026). - Title: "PUC Adopts Voluntary Large Load, Data Center Tariff Framework To Balance A.I. Data Center Growth And Ratepayer Protection" (Pa Environment Daily, April/May 2026). Let's fetch the K&L Gates or Utility Dive article to understand this "first-of-its-kind" large-load model tariff in Pennsylvania. Let's fetch `https://www.utilitydive.com/news/pennsylvania-releases-first-of-its-kind-large-load-model-tariff/820456/` first. Let's make that call.
📥 Fetch
https://www.utilitydive.com/news/pennsylvania-releases-first-of-its-kind-large-load-model-tariff/820456/
Agent
This is an exceptionally rich, primary-source-backed article detailing Pennsylvania's regulatory actions! Let's summarize the key facts for Pennsylvania: - Date: Published May 18, 2026. - Regulator: Pennsylvania Public Utility Commission (PAPUC). - Action: Issued a final order establishing a "first-of-its-kind" nonbinding **model tariff framework for large-load customers** (exceeding 50 MW individually or 100 MW in aggregate). - Core Principle: "But-for" cost allocation. It recommends utilities charge large-load customers for any system upgrades that "would not have been needed 'but for' the interconnection" of that customer, "irrespective of whether other customers will benefit" from the infrastructure. - Payment Mechanism: Encourages upfront payments through **"Contributions in Aid of Construction" (CIAC)**. According to the Environmental Defense Fund (EDF), Pennsylvania may be the first state to push for large loads to pay for upgrades upfront. - Risk Mitigation & Stranded Assets: Includes provisions on collateral and financial security (deposits) to prevent stranded assets, guidance on load ramping schedules, minimum contract terms, and customer exit provisions. - Interconnection Timelines: Instructs utilities to allow large-load customers to self-construct certain upgrades and targets completing interconnection studies within six months. - Pushback/Limitations: The EDF expressed disappointment that the order did not make significant progress on "non-firm" or "interruptible" service, which would allow utilities to curtail electricity to large data centers during grid stress to limit near-term grid costs. Let's also note the broader context mentioned in this article: - Large-load tariffs have proliferated: In 2025, state regulators approved 29 large-load tariffs (compared to 14 between 2018 and 2024). - As of March 2026, there are more than 75 such tariffs pending or in place across 36 states, according to the Smart Electric Power Alliance (SEPA) and North Carolina Clean Energy Technology Center's Database of Emerging Large Load Tariffs. Wait, let's look at the other states mentioned in our initial search: - Nevada (Microsoft's proposed "Ratepayer Protection Tariff" in Docket No. 20-08014, filed May 2026). - Oregon (OPUC approved PGE's Schedule 96 on May 7, 2026, requiring a 29% data center rate hike and 1.3% residential rate decrease, delayed on June 10, 2026, until July 7, 2026, for further review). - North Carolina (SB 730 "Ratepayer Protection Act" advanced in late May 2026). - Kentucky (State report argues data center investment and ratepayer protection can both happen). - Federal level: Senator Adam Schiff (D-Calif.) introduced a data center ratepayer protection bill in May/June 2026. Let's do a search on Senator Adam Schiff's federal data center ratepayer protection bill to see what it entails. This is a federal legislative angle. Let's make that search.
🔍 Search
"Adam Schiff" "data center" "ratepayer" OR "bill" OR "legislation"
No results.
Agent
Let's fetch the press release from Senator Adam Schiff's official website: URL: `https://www.schiff.senate.gov/news/press-releases/news-sen-schiff-unveils-major-legislation-to-ensure-fair-and-affordable-energy-costs-for-americans-amid-data-center-buildouts/` Let's fetch this now to get the exact bill name, specific details, and quotes.
📥 Fetch
https://www.schiff.senate.gov/news/press-releases/news-sen-schiff-unveils-major-legislation-to-ensure-fair-and-affordable-energy-costs-for-americans-amid-data-center-buildouts/
Agent
This is an outstanding primary source. Let's document the federal legislative angle: - Date: Announced May 2026. - Sponsor: U.S. Senator Adam Schiff (D-Calif.). - Bill Name: **Energy Cost Fairness and Reliability Act** (PDF link: `https://www.schiff.senate.gov/wp-content/uploads/2026/05/PAT26381.pdf`). - Key Provisions: 1. **Cost Allocation**: Requires large load facilities like data centers to be responsible for 100% of the grid network upgrades needed to deliver power to them, ensuring those costs are not shifted to other ratepayers. Also requires them to pay for grid reliability services. 2. **Demand Flexibility & BYOP**: Requires energy-intensive facilities to agree to be flexible with their energy demand and "bring their own power" (BYOP) as conditions for connecting to the transmission grid. 3. **Non-Firm & Curtailment**: Directs FERC to update transmission policies to allow data centers to dial down demand during peak periods (non-firm transmission service), allowing grid operators to reduce energy going to data centers during peak demand (curtailment), and pump excess self-generated power back onto the grid. 4. **Anti-Siphoning**: Blocks data centers from siphoning power from existing power plants that are serving the public (a direct legislative response to co-located nuclear power deals, like the Talen/Amazon deal or similar attempts). 5. **Speculation Deterrence**: Updates grid forecasting and the interconnection application process to deter speculative projects from clogging up queues. 6. **DOE Labs Study**: Directs DOE National Laboratories to collect data, analyze usage patterns, and submit recommendations to Congress on reducing energy consumption. Let's do a search on other regulatory developments in key grids like PJM, ERCOT, or MISO. The brief mentions: - Interconnection and capacity-auction outcomes - PJM capacity prices, FERC actions, etc. - In our prior findings, we have: - "FERC Approves PJM Capacity Price Collar Extension through 2030 to Protect Ratepayers" (slug: `ferc-approves-pjm-capacity-price-collar-extension`) - "PJM Deploys 14.9 GW Reliability Backstop Procurement in Response to Data Center Demand" (slug: `pjm-deploys-reliability-backstop-procurement-framework`) - "AEP Ohio Data Center Tariff Approved to Mitigate Ratepayer Risk" (slug: `aep-ohio-data-center-tariff-puco-approval`) Let's search for "PJM capacity auction" or "PJM" and "data center" in May/June 2026 to see if there are other fresh developments, such as comments or filings, or updates on capacity auctions. Let's do that.
🔍 Search
PJM "capacity auction" OR "data center" cost allocation OR "backstop"
No results.
Agent
These search results are incredible! Let's analyze what's happening. Several massive, overlapping stories are unfolding in the PJM territory: 1. **PJM Accelerates the Reliability Backstop Procurement (RBP) / Backstop Auction**: - PJM has *accelerated* its emergency backstop auction (Reliability Backstop Procurement) to **September 2026** (moving it up a year early). - This was done to address near-term grid reliability risks from AI-driven data center demand. - However, PJM urged states to develop rules to shield other ratepayers from data center-driven costs, as it remains unclear how costs will be allocated. - PJM's Independent Market Monitor (IMM), Monitoring Analytics, submitted a "Backstop Auction Design Proposal" on June 10, 2026, which proposes that for data centers that do not bring their own new generation, PJM run a backstop auction designed to meet all expected data center demand. 2. **Maryland Consumer Group Challenges PJM Transmission Costs**: - The Maryland Office of People's Counsel (or similar state consumer advocate group) filed a complaint challenging PJM's transmission cost allocation. - They argue that PJM's current cost-allocation system would leave Maryland residential ratepayers saddled with about **$823 million** for grid upgrades driven by Northern Virginia's data center energy demand (since Northern Virginia, in Dominion territory, is driving massive load, but the transmission upgrades cross state lines and are allocated across the PJM footprint). 3. **PJM Capacity Cost Estimates**: - It is estimated that data center load growth has added over **$23 billion** to PJM capacity market costs since 2025. Let's fetch the Utility Dive article on "PJM accelerates backstop auction amid uncertainty over data center cost allocation" to get the precise details, dates, quotes, and links. URL: `https://www.utilitydive.com/news/pjm-accelerates-backstop-reliability-auction-amid-uncertainty-over-data-cen/820707/` Let's fetch this now.
📥 Fetch
https://www.utilitydive.com/news/pjm-accelerates-backstop-reliability-auction-amid-uncertainty-over-data-cen/820707/
Agent
This is a spectacular find that directly ties into our existing findings and updates the story! Let's see: We have a prior finding: `[[pjm-deploys-reliability-backstop-procurement-framework]]` (PJM Deploys 14.9 GW Reliability Backstop Procurement in Response to Data Center Demand). This new development is a critical update to that finding: - **PJM Board Accelerated the Backstop Reliability Auction to September 2026** (originally scheduled for March 2027). - This acceleration was in response to criticism from FERC Chairman Laura Swett, who expressed that PJM may be "too big to function" and reviewed its governance. - The target capacity of the accelerated backstop auction is reduced from 14.9 GW to roughly **9 GW**, which will meet any capacity shortfalls from PJM's Base Residual Auction (BRA) for the 2028/2029 delivery year (which opens June 30, 2026, and closes July 7, 2026). - **Cost Allocation Warning**: PJM's board warned that if member states do not immediately establish frameworks to appropriately allocate these costs to new data center loads, it is highly unclear how those costs will be assigned, raising risks that existing ratepayers will be left footing the bill. - **Integration of Stakeholder Processes**: PJM is combining the stakeholder processes for the one-time backstop procurement and its **"Connect and Manage" (C&M)** rules. C&M allows data centers to interconnect under "non-firm" or interruptible terms, agreeing to be curtailed during times of grid stress. Let's also fetch the technical.ly article regarding Maryland's challenge to PJM transmission costs: "Maryland consumer group challenges PJM over residents footing the bill for Virginia data centers" Let's do a search to find the exact URL or text of this article, or search for "Maryland Office of People's Counsel" PJM data center transmission costs. Let's make that search.
🔍 Search
"Maryland Office of People's Counsel" OR "Maryland consumer group" PJM transmission "data center" OR "Virginia"
No results.
Agent
This is a critical, concrete case study of regional cost-shifting across state lines within a multi-state grid (PJM). Let's fetch the official bulletin from the Maryland Office of People's Counsel (OPC) or the RTO Insider article about the complaint. URL: `https://content.govdelivery.com/accounts/MDOPC/bulletins/415c9b6` Let's fetch this now to get the exact facts, figures, and quotes.
📥 Fetch
https://content.govdelivery.com/accounts/MDOPC/bulletins/415c9b6
Agent
This is a masterpiece of evidence that directly exposes the core tension of the AI data-center boom: **cross-state ratepayer subsidies within multi-state grids**. Let's analyze this carefully: - Date of filing: May 7, 2026. - Entity: Maryland Office of People's Counsel (OPC), led by David S. Lapp. - Forum: Federal Energy Regulatory Commission (FERC), Complaint Docket No. EL26-63-000. - Core Argument: PJM's regional transmission cost allocation rules violate the Federal Power Act by unfairly assigning **$2 billion in capital expenditures** (resulting in **$1.6 billion in higher electric bills over the next ten years**) to Maryland ratepayers to fund transmission lines driven by massive data center growth in other states (primarily Northern Virginia in Dominion Energy's territory). - Breakdown of the $1.6 billion in added costs to Maryland electric bills: - **$823 million** to residential customers (approx. $345 per average household). - **$146 million** to commercial customers ($673 per average business). - **$629 million** to industrial customers ($15,074 per average industrial user). - Mechanism of the cost-shift: - PJM's "hybrid" transmission cost allocation methodology for high-voltage projects (500 kV or higher) allocates **50% of costs across all PJM transmission zones** based on their proportional demand, regardless of who caused the upgrade. - The other 50% is allocated via "power flow" analysis, which assigns costs based on predicted physical flows, catching neighboring states like Maryland by virtue of geographic proximity. - While Maryland's load growth is modest, it is being forced to subsidize the $22 billion in transmission projects advanced through PJM's regional transmission expansion plan (RTEP) over the last three years, which are overwhelmingly driven by data center demand in Northern Virginia, Ohio, Pennsylvania, and Illinois. - Inadequacy of existing tools: - State-level "large-load tariffs" (like those in Ohio or Oregon) only address costs within a single state's borders. They *cannot* prevent PJM from allocating out-of-state transmission expansion costs to neighboring states under regional grid rules. - Utility "Transmission Security Agreements" (TSAs) are deemed insufficient to protect customers from massive capital costs and risks. - Projections of data center growth are highly speculative, yet utilities benefit financially from transmission investments regardless of whether the data centers actually materialize because they earn a regulated rate of return on equity (ROE) on transmission capex, shifting the risk of stranded assets to existing ratepayers. - Remedy sought: - Require PJM to assign data center-driven transmission costs directly to the specific PJM zones where the data centers are located (e.g., the Dominion zone in Virginia), OR directly charge transmission costs to the large-load data center customers. Let's check the market view for Dominion Energy (D), which is the dominant utility in Virginia (the heart of "Data Center Alley" in Northern Virginia) to see their financial position and whether they are benefiting from this transmission buildout. Let's make that call. I will state my intent first.
other market_view
Agent
Wow, Dominion Energy (D) is trading at its 52-week high ($67.91) and has agreed to merge with NextEra (NEE) in an all-stock transaction! That is a massive corporate development that is highly relevant to our investable exposure map. Let's look at the other filings and articles we fetched to see if we can get a complete picture of the state and federal data center ratepayer protection initiatives. Let's review the notes we need to write or update: 1. **`pjm-deploys-reliability-backstop-procurement-framework`**: - We need to update this note because PJM has accelerated the backstop reliability auction to September 2026 (originally March 2027), reduced its target to ~9 GW, combined stakeholder processes with "Connect and Manage" (C&M) rules, and warned states that without immediate action, cost allocation remains highly uncertain. 2. **`quantitative-evidence-data-center-ratepayer-subsidies`**: - This note tracks the debate over whether ratepayers are subsidizing data centers. We have a mountain of new evidence from May/June 2026: - Maryland OPC's formal FERC complaint alleging that Marylanders are being unfairly assigned **$2 billion in transmission capital costs** ($1.6 billion in bills over 10 years) to support out-of-state data centers (e.g., in Virginia). - State-level legislative and regulatory actions in Oregon (PGE Schedule 96 29% data center hike vs 1.3% residential cut, delayed on June 10, 2026, to July 7, 2026), Nevada (Microsoft's proposed Ratepayer Protection Tariff), North Carolina (SB 730 Ratepayer Protection Act), and Pennsylvania (PAPUC's model "but-for" tariff). - Federal level: Senator Adam Schiff's "Energy Cost Fairness and Reliability Act" requiring data centers to pay 100% of network upgrades, "bring their own power," and allow curtailment. - We should update this note or write a new note that captures this massive, coordinated regulatory and legislative backlash. Wait! Let's look at the existing note: `quantitative-evidence-data-center-ratepayer-subsidies`. It was titled "Quantitative Evidence Refutes Systematic Data Center Ratepayer Subsidies" based on earlier studies (like E3's analysis which found "no clear delineation of the relationship between load growth and electricity prices"). But now, we have *concrete quantitative evidence of cross-state transmission subsidies* ($2B) and a major state/federal policy pivot. Let's update `quantitative-evidence-data-center-ratepayer-subsidies` with this new, overwhelming wave of evidence! Or, since the title is "Quantitative Evidence Refutes..." and we now have strong evidence *showing* that ratepayers *are* being exposed to massive costs (even if some studies say otherwise), we can update this note to show the intense debate and the specific calculations of the Maryland OPC showing a $1.6B bill impact. Wait, is there a better slug? Let's check `read_notes` again. - `quantitative-evidence-data-center-ratepayer-subsidies` - `georgia-power-large-load-contracting-framework` - `aep-ohio-data-center-tariff-puco-approval` - `amazon-talen-energy-nuclear-ppa-pivot` - `constellation-energy-acquires-calpine-three-mile-island-restart` - `pjm-deploys-reliability-backstop-procurement-framework` - `ferc-approves-pjm-capacity-price-collar-extension` - `pjm-2027-2028-capacity-auction-price-cap` Let's write a new, highly focused note on the **state and federal legislative and regulatory backlash** to shield ratepayers from data center costs, or we can update `quantitative-evidence-data-center-ratepayer-subsidies` to show the clash between the utility-funded studies (like E3's study which says there is no subsidy) and the consumer advocates/legislators (like Maryland OPC, Oregon PUC, Pennsylvania PUC, North Carolina, Nevada, and Senator Schiff) who are actively implementing tariffs to prevent cost shifts. Let's see: if we write a note titled "State and Federal Regulators Move to Shield Ratepayers from AI Data Center Costs" with a durable slug like `regulatory-backlash-data-center-ratepayer-protections`, that would be a perfect home for this entire wave of May/June 2026 developments (Oregon, Nevada, Pennsylvania, North Carolina, and Senator Schiff's bill). And we can write a separate note on the Maryland OPC's FERC complaint because it is a very specific, quantitative, cross-state transmission cost-shifting battle within PJM, or we can combine it with the PJM backstop auction update. Let's think: Let's keep the PJM backstop auction update under `pjm-deploys-reliability-backstop-procurement-framework`. Let's write a new note on the Maryland OPC's FERC complaint under a slug like `maryland-opc-pjm-transmission-cost-complaint`, since it's a huge, specific $2 billion legal challenge to PJM's regional transmission cost allocation rules. And let's write a new note on the state-level and federal ratepayer protection tariffs/bills (Oregon, Pennsylvania, Nevada, North Carolina, and Senator Schiff's bill) under a slug like `state-federal-data-center-ratepayer-protection-tariffs`. This keeps each note highly coherent and focused on a single durable subject! Let's double-check if there are any other specific articles we can fetch to strengthen our findings. Let's search for "E3 finds no evidence ratepayers subsidizing data centers" or "E3" "data center" "ratepayer" to see what that study was about, so we can reference it accurately if needed, or update `quantitative-evidence-data-center-ratepayer-subsidies`. Let's do that search.
🔍 Search
"E3" OR "Energy and Environmental Economics" "data center" "ratepayer" OR "subsidy" OR "subsidizing"
No results.
Agent
This is very interesting. Let's see: - E3 (Energy and Environmental Economics, Inc.) published a report in May 2026 titled: "Understanding the Drivers of Rising Electricity Rates and the Role of Data Centers". - E3 also published a study for Amazon in late 2025/early 2026 titled: "Designing Electric Rates and Tariffs for Large Loads". - In these studies, E3 argues that evaluated data centers could generate potential ratepayer benefits (of up to $6.1 million per 100 MW data center by 2030) because they contribute to fixed cost recovery and that there is no clear evidence that ratepayers are systematically subsidizing data centers. - This is the "industry/developer" perspective, which directly clashes with the consumer advocate perspective (like Maryland OPC's David Lapp, who filed the FERC complaint pointing out that PJM's hybrid cost allocation is forcing Marylanders to cover $2 billion of transmission upgrades caused by Virginia data centers). Let's fetch the E3 RTO Insider article or the E3 report summary if we can, to have this side of the coin well-documented. Let's fetch `https://www.rtoinsider.com/132475-e3-finds-no-evidence-ratepayers-subsidizing-data-centers/` to see how RTO Insider covered it. Let's make that call.
📥 Fetch
https://www.rtoinsider.com/132475-e3-finds-no-evidence-ratepayers-subsidizing-data-centers/
Agent
The fetch succeeded, but the markdown content was very short (just a summary snippet). That's fine; we have the main idea from the titles and descriptions: - E3's May 18, 2026 report, commissioned by the industry (such as the Data Center Coalition or tech companies), analyzed research and data and found no clear evidence that ratepayers are systematically subsidizing data centers, and suggested that data centers actually contribute to fixed-cost recovery, lowering rates overall under certain rate designs. - However, they also suggested steps to avoid cost shifts (such as well-designed tariffs). Let's look at the three notes we want to write or update: ### 1. Update Note: `pjm-deploys-reliability-backstop-procurement-framework` Let's first fetch the current body of `pjm-deploys-reliability-backstop-procurement-framework` using `read_notes` or check its content to make sure we edit it accurately. Wait, the preview was: "In response to projected capacity shortfalls of 50 GW to 60 GW over the next decade, PJM Interconnection has proposed a landmark **Reliability Backstop Procurement (RBP)** framework to secure 14.9 GW…" Let's fetch its full content so we can edit it in place. Wait, is there a tool to read a specific note? No, `read_notes` returns the preview and slug, but we don't have a direct "read_note_by_slug" tool. Wait, `read_notes` has a `topic_id` and returns the notes. Let's see if we can search for the note or if we can just write the updated version. Yes, we can just write the updated version with `write_note` using the same slug. The slug is `pjm-deploys-reliability-backstop-procurement-framework`. Let's see: we should make sure that the updated note preserves the history of the RBP but adds the critical May 20, 2026 update: PJM's board accelerating the backstop auction to September 2026, combining it with the "Connect and Manage" (C&M) stakeholder process, and warning of the cost-allocation vacuum. Let's design the body for `pjm-deploys-reliability-backstop-procurement-framework`: - Title: PJM Deploys and Accelerates Reliability Backstop Procurement Framework - Body: - Explain the original proposal (April 2026): 14.9 GW backstop procurement to address capacity shortfalls, with a bilateral phase followed by a backstop auction in March 2027. - Explain the new update (May 20, 2026): The PJM Board issued a letter to stakeholders accelerating the backstop reliability auction to **September 2026** (moving it up a year early). - This acceleration came after criticism from FERC Chair Laura Swett, who questioned the delay and noted PJM might be "too big to function." - The target capacity is reduced to roughly **9 GW**, which will meet shortfalls from the next Base Residual Auction (BRA) for the 2028/2029 delivery year (set to begin June 30, 2026). - Highlight the **Cost Allocation Warning**: PJM's Board warned that without state-level frameworks to allocate these costs to new data center loads, it is unclear who will pay, threatening to shift costs to existing ratepayers. - Detail the integration of the **"Connect and Manage" (C&M)** rules, which allow data centers to interconnect under "non-firm" or interruptible terms. - Cite the PJM Stakeholder Letter and the Utility Dive coverage. Let's write this note. I will state my intent first.
📝 Wrote finding
pjm-deploys-reliability-backstop-procurement-framework
Agent
Now let's write a new note specifically tracking the **Maryland OPC's FERC Complaint** regarding the cross-state transmission cost-shifting within PJM. This is a very specific, high-stakes battle. Let's name the slug `maryland-opc-pjm-transmission-cost-complaint` and title it "Maryland Challenges PJM Transmission Cost Rules Over $2B Data Center Cost Shift". Let's design the body: - Title: Maryland Challenges PJM Transmission Cost Rules Over $2B Data Center Cost Shift - Body: - Explain the filing (May 7, 2026) by the Maryland Office of People's Counsel (OPC) at FERC (Docket No. EL26-63-000). - Detail the core complaint: PJM's "hybrid" transmission cost allocation rules are violating the Federal Power Act by unfairly assigning **$2 billion in capital expenditures** to Marylanders for high-voltage transmission lines driven by out-of-state data centers (overwhelmingly in Virginia/Dominion territory). - This capital cost translates to a **$1.6 billion increase in Maryland customer bills over the next ten years**. - Provide the exact breakdown of the $1.6 billion bill impact: - **$823 million** to residential customers (~$345 per average customer). - **$146 million** to commercial customers (~$673 per average customer). - **$629 million** to industrial customers (~$15,074 per average customer). - Explain the PJM "hybrid" allocation mechanism: - High-voltage projects (500 kV+): 50% allocated pool-wide based on load share, 50% allocated via power flow analysis. - Since Maryland is geographically adjacent to Virginia's massive data center buildout, it is heavily penalized under both halves of the allocation, despite having modest native load growth. - Highlight the reference to the **White House "Ratepayer Protection Pledge"** signed by tech hyperscalers on March 4, 2026, which states developers "will pay for new power delivery infrastructure upgrades... ensuring these expenses are not passed on to the ordinary household." The OPC argues PJM's current rules directly violate the spirit of this pledge. - Explain the remedy sought: Assign transmission costs directly to the PJM zones where the data centers are located (e.g., Dominion zone in Virginia) or charge the large data center customers directly. - Discuss the risk of speculative load growth: The OPC emphasizes that utilities stand to profit from these transmission investments regardless of whether the projected data center load actually materializes, because they earn a regulated ROE on transmission capex, while ratepayers bear the stranded-asset risk. - Include the sources: Maryland OPC bulletin and FERC filing. Let's write this note now. I will state my intent first.
📝 Wrote finding
maryland-opc-pjm-transmission-cost-complaint
Agent
Now, let's write our third note: **`state-federal-data-center-ratepayer-protection-tariffs`** (or let's call it `regulatory-backlash-data-center-ratepayer-protections` to track the state and federal regulatory and legislative backlash). Let's design the body: - Title: Regulatory and Legislative Backlash: Shielding Ratepayers from AI Data Center Costs - Body: - Explain that as the AI data center buildout accelerates, a massive regulatory and legislative backlash has emerged in May/June 2026. - Detail the proliferation of large-load tariffs: State regulators approved 29 large-load tariffs in 2025 alone (compared to 14 between 2018 and 2024). As of March 2026, there are more than 75 tariffs pending or in place across 36 states, according to the Smart Electric Power Alliance (SEPA). - Detail **Oregon's POWER Act implementation (PGE Schedule 96)**: - Approved May 7, 2026. PGE proposed a **29% rate increase** for large-load data centers (exceeding 20 MW) paired with a **1.3% rate decrease** for residential and small business customers. - Requires 100% of distribution upgrades to be paid by data centers. - Contract terms of 10 to 30 years (for 220 MW+). - Projects over 100 MW pay a 1 cent/kWh surcharge to fund residential rate offsets. - Delayed on June 10, 2026, until July 7, 2026, by the Oregon PUC for a detailed 200-page review. - Detail **Pennsylvania's Model Interconnection Tariff**: - Issued May 2026 by the PAPUC. - Recommends a "first-of-its-kind" **"but-for" cost allocation** framework for customers exceeding 50 MW individually or 100 MW in aggregate. - Large loads must pay for any upgrades that "would not have been needed 'but for' the interconnection" upfront via **Contributions in Aid of Construction (CIAC)**. - Requires collateral/financial security deposits to prevent stranded assets. - Detail **Microsoft's Proposed Nevada Ratepayer Protection Tariff**: - Filed in May 2026 with the PUCN (Docket No. 20-08014). - A unique developer-led proposal to split project infrastructure into a "Customer Contributed Share" (paid by the developer) and a "System Benefit Share" (reviewed for rate base if it benefits the broader system). - Includes a "Bring Your Own Power" (BYOP) provision and an expedited 60-day review pathway. - Detail **North Carolina's SB 730 (Ratepayer Protection Act)**: - Advanced in late May 2026. - Bans data centers from shifting energy costs, bans local tax incentives, requires closed-loop water cooling, and forbids baseload plant retirements until replaced with nuclear. - Detail **Federal Legislation (Senator Adam Schiff's Energy Cost Fairness and Reliability Act)**: - Introduced in May 2026. - Requires data centers to pay 100% of network upgrades, be flexible with demand, "bring their own power," allow curtailment during peak periods, and blocks data centers from siphoning power from existing public-serving plants. - Discuss the tension with industry-funded studies: Contrast this wave of protective tariffs with studies like E3's May 18, 2026 report (commissioned by the data center industry), which argues that under optimal rate design, data centers contribute to fixed-cost recovery and can actually lower rates for other customers. Let's write this note now. I will state my intent first.
📝 Wrote finding
regulatory-backlash-data-center-ratepayer-protections
Agent
These three notes are incredibly strong, highly qualitative, and fully grounded in primary sources from May and June 2026. Let's see if we should create a new thread or a watch for future cycles. Wait! We have a few forward-looking events: 1. **Oregon PUC decision on PGE's Schedule 96 rates**: Expected on **July 7, 2026**. This is a perfect dated catalyst! 2. **PJM Base Residual Auction (BRA) for 2028/2029 Delivery Year**: Closes on **July 7, 2026** (results expected on July 8, 2026). This is already tracked by our existing open thread/watch: `PJM 2028/2029 Capacity Auction Closes under Price Collar` (ID: `019ea65a-ea15-7c43-a1be-b796d6b5a6cb`). 3. **PJM's Accelerated Backstop Reliability Auction**: Scheduled for **September 2026**. This is a massive new forward-looking catalyst that we should register as a watch! Let's register it. Let's register a watch for the Oregon PUC's decision on PGE's data center rate increase. It is expected on July 7, 2026. Let's register it as a `one_shot` watch of type `dated_catalyst`. Let's make that call. I will state my intent first.
other record_watch
Agent
Excellent. Now let's register a watch for the accelerated PJM Backstop Reliability Procurement Auction in September 2026. Let's register it as a `one_shot` watch of type `dated_catalyst`. Let's make that call. I will state my intent first.
other record_watch
Agent
This is fantastic. We have: 1. Updated `pjm-deploys-reliability-backstop-procurement-framework` to capture the crucial board decision to accelerate the auction to September 2026, combine it with "Connect and Manage" rules, and warn states about the cost-allocation vacuum. 2. Created `maryland-opc-pjm-transmission-cost-complaint` to document the high-profile FERC complaint by Maryland's Office of People's Counsel, detailing the $2 billion in capital costs ($1.6 billion in bills over 10 years) being shifted to Marylanders for Virginia data centers. 3. Created `regulatory-backlash-data-center-ratepayer-protections` to document the massive state-level and federal regulatory/legislative backlash to shield ratepayers from data center costs (Oregon's 29% PGE hike, Pennsylvania's "but-for" tariff, Microsoft's Nevada tariff, North Carolina's S730, and Senator Schiff's federal bill). 4. Registered two key watches: - Oregon PUC's final decision on PGE's Schedule 96 rates (expected July 7, 2026). - PJM's accelerated Backstop Reliability Procurement Auction (scheduled for September 2026). Let's do a quick check of our workspace or long-term memory to see if there is anything else to update. Wait, let's look at the Guidelines: - "State intent before tool calls, but NEVER predict or claim results before receiving them." (Done) - "Call finish_cycle to end the research cycle. Call this exactly once, as your final action..." (Will do) Let's call `finish_cycle` to complete this cycle. I will state my intent first.
other finish_cycle
Agent
I have completed the research cycle for this topic. Here is a summary of the key findings and actions taken: ### 1. Key Findings Recorded * **PJM Deploys and Accelerates Reliability Backstop Procurement Framework** (Updated Note: `pjm-deploys-reliability-backstop-procurement-framework`): * **The Update**: On May 19, 2026, the PJM Board of Directors accelerated its emergency backstop reliability auction to **September 2026** (originally March 2027) in response to regulatory pressure from FERC Chair Laura Swett. * **The Mechanics**: The auction's target capacity is reduced to ~9 GW to meet shortfalls from the upcoming 2028/2029 Base Residual Auction (BRA). It will be combined with PJM's "Connect and Manage" (C&M) rules, which allow data centers to interconnect under "non-firm" or interruptible terms. * **The Warning**: PJM's board issued a stark warning that if member states do not immediately establish retail frameworks to assign these backstop costs to new data center loads, it is highly unclear how those costs will be allocated, risking massive cost shifts to existing ratepayers. * **Maryland Challenges PJM Transmission Cost Rules Over $2B Data Center Cost Shift** (New Note: `maryland-opc-pjm-transmission-cost-complaint`): * **The Conflict**: On May 7, 2026, the Maryland Office of People's Counsel (OPC) filed a landmark FERC complaint (Docket No. EL26-63-000) challenging PJM's regional transmission cost allocation rules. * **The Impact**: PJM's "hybrid" cost-allocation rules have assigned Marylanders responsibility for **$2 billion in capital expenditures** (resulting in **$1.6 billion in higher electric bills over the next ten years**) to fund high-voltage transmission lines driven by out-of-state data center growth, primarily in Northern Virginia (Dominion's territory). * **The Breakdown**: The $1.6 billion bill surcharge breaks down as: **$823 million** to residential households (~$345 per average customer), **$146 million** to commercial businesses (~$673 per customer), and **$629 million** to industrial users (~$15,074 per customer). * **The Loophole**: PJM's rules allocate 50% of high-voltage transmission costs broadly across the entire PJM pool based on load-share, and 50% based on physical power-flow modeling, which sweeps in neighboring states like Maryland due to geographic proximity. * **Regulatory and Legislative Backlash: Shielding Ratepayers from AI Data Center Costs** (New Note: `regulatory-backlash-data-center-ratepayer-protections`): * **The Trend**: State regulators approved **29 large-load tariffs in 2025 alone** (compared to 14 between 2018 and 2024). As of mid-2026, there are **more than 75 such tariffs pending or active across 36 states**. * **Oregon (PGE Schedule 96)**: Approved May 7, 2026, creating a 29% rate increase for data centers (>20 MW) paired with a 1.3% rate decrease for residential customers. It requires 100% customer-paid distribution upgrades and a 1 cent/kWh surcharge on projects over 100 MW to fund low-income offsets. On June 10, 2026, the OPUC issued a one-month delay (until July 7, 2026) to carefully review the tariff details. * **Pennsylvania**: On May 13, 2026, the PAPUC established a model tariff recommending a strict **"but-for" cost allocation** framework for customers >50 MW, requiring upfront Contributions in Aid of Construction (CIAC) payments and collateral to prevent stranded assets. * **Nevada**: Microsoft filed a unique developer-led "Ratepayer Protection Tariff" (Docket No. 20-08014) in May 2026, proposing to split infrastructure into a Customer Contributed Share (paid by the developer) and a System Benefit Share, alongside a "Bring Your Own Power" (BYOP) provision. * **North Carolina (SB 730)**: Advanced in late May 2026, banning data center cost shifts, outlawing local tax incentives, requiring closed-loop water cooling, and forbidding baseload retirements until replaced with nuclear. * **Federal (Schiff Bill)**: U.S. Senator Adam Schiff introduced the *Energy Cost Fairness and Reliability Act* in May 2026, directing FERC to force data centers to pay 100% of network upgrades, allow curtailment during peak periods, and block data centers from siphoning power from existing public-serving plants. ### 2. Market Views Anchored * **Constellation Energy (CEG)**: Revenue up 63.8% YoY to $29.87B (TTM); Q1 2026 net income of $1.60B on $11.12B in revenue. Stock trading at $253.76, reflecting a 19.9% decline over 3 months as the sector faces share-supply and regulatory tests. * **Vistra Corp (VST)**: Revenue up 43.4% YoY to $19.45B (TTM); Q1 2026 net income of $1.03B on $4.65B in revenue. Stock trading at $148.02. * **Portland General Electric (POR)**: Revenue down 5.3% YoY to $3.53B (TTM). Stock trading at $50.72. Regulators delayed their proposed data center rate increase until July 7, 2026, while a class-action lawsuit on groundwater contamination moves to a May 2027 trial. * **Dominion Energy (D)**: Revenue up 23.1% YoY to $17.45B (TTM). Stock trading at its 52-week high ($67.91) following a definitive agreement to merge with NextEra (NEE) in an all-stock transaction. * **Duke Energy (DUK)**: Revenue up 11.3% YoY to $32.72B (TTM). Stock trading at $124.97, after posting its fourth consecutive earnings beat in Q1 2026 ($1.93 EPS vs. $1.80 est). ### 3. Forward-Looking Watches Registered * **Oregon PUC Final Decision on PGE Schedule 96 Rates** (Expected **July 7, 2026**): To track whether the 29% data center rate hike and 1.3% residential rate cut are approved. * **PJM Accelerated Backstop Reliability Auction Results** (Expected **September 2026**): To track the capacity cleared, clearing prices, and whether PJM member states establish retail cost-allocation frameworks to protect existing ratepayers.