PJM’s State of the Market report for 2025 is out. MISO’s didn’t come out until JUNE last year! The approach in MISO‘s MTEP2024 regarding data centers is markedly, MARKETedly, different!

MISO did put out a “2026 RELIABILITY IMPERATIVE REPORT” with at least one point worth noting:

Approximately 130 GW of projects — nearly half of the queue — have been withdrawn, in part due to changes to tax credits under One Big Beautiful Bill Act.

2026 RELIABILITY IMPERATIVE REPORT, p. 11.

Anyway, back to PJM’s State of the Market report for 2025, starting with Volume 1:

PJM has some interesting statements on data centers. I hear a lot of folks saying the skyrocketing electric rates are due to data centers, but in the Midwest that’s not happening yet. We’re paying for the BILLIONS in transmission, but data centers are lurking. Here’s what PJM has to say:

Data center load growth is the primary reason for recent and expected capacity market conditions, including total forecast load growth, the tight supply and demand balance, and high prices. But for data center growth, both actual and forecast, the capacity market would not have seen the same tight supply demand conditions, the same high prices observed in the 2025/2026 BRA, the 2026/2027 BRA, and the 2027/2028 BRA, and the currently expected tight supply conditions and high prices for subsequent capacity auctions. (Intro, p. 1)

The decisions about the interconnection of large new data center loads when there is not enough capacity to maintain system reliability are public, regulatory decisions because they are about competitive outcomes that are in the interests of all market participants. PJM markets are not laissez faire markets.

It is clear that continuing to simply accept the interconnection of large data center loads that cannot be served reliably because there is not adequate dispatchable capacity, is not a reasonable path forward
and is not an efficient or competitive market solution and is not a solution of any kind. That path leads
to continued shortfalls, increased reliability issues, continued maximum prices, and continued calls to
abandon markets.

The current supply of capacity in PJM is not adequate to meet the demand from large data center loads and will not be adequate in the foreseeable future. This is a simple factual issue. There is not enough capacity currently to meet the data center load. The solution is not to create reliability issues and wealth transfer issues by clearing the capacity market at the maximum price and at a quantity less than the reliability requirement by allowing the ongoing interconnection of large data center loads without adequate generation to serve them and without a clear path to adding the required capacity or to defining full curtailability.

The market solution is to require data centers to bring their own new generation. This would include an
expedited fast track load and generation interconnection process for large new data center loads that bring their own new generation with locational and temporal characteristics reasonably matched to their load profile. The preferred solution would include creating a queue for the addition of large new data center loads, which would not be interconnected until there is adequate capacity to serve them. Another solution would require data centers that do not bring their own new generation to be curtailable prior to current demand side customers but without the pretense that the data centers are providing “demand response” for which they should be paid. Given the level of data center load growth, this curtailability solution would provide a strong incentive to bring new generation, if enforced on a specific data center basis. This broad bring your own new generation solution to the issues created by the addition of unprecedented amounts of large data center load does not require a continued massive wealth transfer. (Intro p. 2).

Here’s the PJM proposal: Monitoring Analytics, LLC, Reliability Backstop Auction Design Proposal – V2 . In short, “the data centers must bear their own costs and risks and not shift them to other customers, and that the data centers must bring their own new generation in any one of a number of forms or be fully curtailable.” Intro, p. 3.

Oh, and about those “benefit/cost” or “cost-benefit” analysis in MISO that I’ve been going on about because likely costs have risen sufficiently to throw the “benefit/cost” analysis completely out of whack and how many MISO transmission projects would no longer be economically sound… MISO isn’t the only one concerned about cost increases! All transmission projects should require a MISO Tariff FF Variance Analysis, which looking at Northland Reliability Project’s public releases thus far, the MISO Variance Analysis Information Letter – 2026 03 06 process isn’t stringent enough, well, anyway, here’s the PJM 2025 State of the Market released

March 12th, 2026 take, from page 94 of the State of the Market report for 2025:

Yet in response to Comments I’d submitted as an individual in the Tranche 2.1 Power on Midwest docket, CN-25-117, the applicants state:

Once more with feeling, “When actual costs exceed estimated costs, the benefit/cost analysis is effectively meaningless…” eh, PJM??? All the MISO Tranche 2.1 projects rely on the MISO benefit/cost analysis for MISO approval and Commission approval. They don’t do an independent analysis to determine whether the project makes any sense. This is not rocket science, but it is so very clear why they don’t want to look at those cost increases!

Here’s the rest of the PJM State of the Market report, and it’s a LOT:

Volume II
Volume II (22MB PDF) contains detailed analysis and results.
Preface (45KB PDF)
Table of Contents (84KB PDF)
Section 1 – Introduction (2MB PDF)
Section 2 – Recommendations (332KB PDF)
Section 3 – Energy Market (5MB PDF)
Section 4 – Energy Uplift (268KB PDF)
Section 5 – Capacity Market (3MB PDF)
Section 6 – Demand Response (1MB PDF)
Section 7 – Net Revenue (1MB PDF)
Section 8 – Environmental and Renewable Energy Regulations (1MB PDF)
Section 9 – Interchange Transactions (1MB PDF)
Section 10 – Ancillary Service Markets (3MB PDF)
Section 11 – Congestion and Marginal Losses (4MB PDF)
Section 12 – Generation and Transmission Planning (2MB PDF)
Section 13 – Financial Transmission and Auction Revenue Rights (1MB PDF)

The Iron Range – St. Louis County – Arrowhead 345kV transmission project is back into gear after a month long pause. This one is PUC Dockets CN-25-111 and TL-25-112, both running together in a joint proceeding (more on that later). Iron Range – St. Louis County – Arrowhead is the fourth BIG project I’m dealing with, and I’m really grateful for this delay!! I guess I’ll have to revert to my “Overload” moniker!

There’s also a webex meeting on Thursday, April 9, for more details on how to participate, see the full notice below:

Comments are due Tuesday, April 23, so there’s some time, but don’t forget!

Here’s the full notice:

You can find the application on Legalectric here:

Iron Range to Arrowhead Xmsn App Filed

Here’s a utility presentation from county meetings:

ISA TRANSMISSION PROJECT APPLICATION

Minnesota Public Utilities Commission process for Certificate of Need and Routing? Good luck with that.

Ja, it’s a little fuzzy, and that’s how PUC process is! I’m drawing up a flowchart for my peeps all over Minnesota in these transmission dockets, and gotta love the internet — this turned up:

What do they have to say about “informal process” for Certificate of Need? Well, from our friends at Taft, the Modern Law Firm, nothing new, but here’s what they’re telling their clients (says “Attorney-Client Privilege” but here it is in the interwebs):

MEMORANDUM 2025-Permitting-Book, p. 20-21. And here’s what Xcel Energy has to say:

And we know all about that pesky Minn. R. 7829.1200 — that is THE rule about “informal process,” with its three points to determine whether it’s appropriate — there is no other:

And Minn. R. 7829.2500 — The Commission must make a decision to utilize the informal process, the informal process governed by Minn. R. 7829.2500, mindful that it must meet the criteria in that rule.

On to the Public Utilities Commission — what does the PUC have to say about “informal process?” MOST?!?! STREAMLINES?!?!? For the first long string of 765kV transmission from South Dakota into the middle of Wisconsin… INFORMAL PROCESS? In what world is this reasonable? Over my dead polar bear…

And Contested Case?

So either way it takes a year. Sounds to me like they don’t want to do the work of a contested case, and/or don’t want the “more rigorous and detailed examination.”

Here’s the “Gopher to Badger” notion of process:

Here’s the utility version of process from the Maple River-Cuyuna transmission project, PUC Docket CN-25-109 (filed yesterday: Supplemental Comments – Maple River to Cuyuna 345kV)

Notice how it goes from “Commission reviews application for completeness” to “Commission issues Certificate of Need decision” in that flowchart and nothing in between? Hmmmm… what’s missing?

THE PUBLIC!!!

For example, missing are these opportunities for the public to weigh in – insert these points in their perception of process:

• Public Comments on Notice Plan
• Public Comments on Completeness
• Public Hearing and Comments on Project
• Intervention
• Evidentiary Hearing
• Briefing
• ALJ Recommendation
• Exceptions to ALJ Recommendaiton
• Staff Briefing Papers
• Commission Agenda Mtg
• Oral Argument if requested and granted
• Commission Decision and written Order after Agenda Mtg
• Motion for Reconsideration
• Agenda Mtg on Reconsideration (usually denied)
• Appeal direct to Minnesota Court of Appeals
• Briefing, maybe Oral Argument
• Decision – usually dismissed/denied/tossed out

The Power on Midwest is a little better — they even mention “INTERVENTION!”

But I’m still looking for that PUC flowchart.

“Informal process” for these big transmission projects? I don’t think so. Particularly when you’ve got toadies lining up pushing for “informal process.” Again, if it’s the same length of time, no “delay,” why? It’s got to be that they don’t want that “more rigorous and detailed examination.” Ja, so?!?!?!

Right… once more with feeling… REMEMBER THE PUC’S PUBLIC PARTICIPATION MANDATE:

MINN. STAT. 216I.16

THE PUBLIC!!!

… AAAAARGH… they’ll have to pry my computer out of my cold dead hands!

Whew, third Comment filed this week, this was Supplement Completeness Comment on the Maple River to Cuyuna transmission line, a 345kV headed from Fargo area to a substation near Baxter. The application is linked here:

Maple River – Cuyuna 345kV line

As for Supplemental Comments, here we go:

And the Applicants, the Supplemental Comments draw on the new info, different info, in the Reply Comments. They’ve changed their tune and now are wanting this “informal process” that does not exist in statute or rule, a simple round of written comments:

And this one from LIUNA is a hoot — seems to be a problem with a real review process, and seems to be toadying for the utilities. Why? How would a serious review of a Certificate of Need application harm LIUNA? Makes no sense.

Busy day today. We’ve had the final round of Completeness Comments on both the Gopher to Badger and Power on Midwest web of 765kV transmission across southern Minnesota. Really,all the way across southern Minnesota. On the western border, it runs through South Dakota from Big Stone coal plant down to Brookings, near Sioux Falls, and then across through Lakefield Junction over to Pleasant Valley… then for some reason up to North Rochester sub just north of Pine Island (with a 345 kV line also running that way, and up to Hampton, WTAF?) and then from North Rochester substation down to the southeast to Marion, then to the southwest (?) back to Pleasant Valley, and from their straight across following Dairyland’s 161kV line to the Mississippi and beyond to the Columbia substation near Portage, Wisconsin. That’s a LOT of 765kV transmission line:

Filed by North Route Group and NO765MN in both dockets – Gopher to Badger CN-25-121 and Power on Midwest CN-25-117. WHY? Because it’s all connected:

Filed by Applicants in both dockets:

Filed by Commerce-DER in both dockets:

Last and least, filed by Liuna – least because how off can ya get??: