August 6, 2026 | Source: NERC Level 3 Essential Action Alert — "Computational Load Modeling, Studies, Instrumentation, Commissioning, Operations, Protection, and Control" (initial distribution May 4, 2026)
The Level 3 Alert Window Closed. Your Answers Now Write the Standard.
Reporting on NERC's Level 3 Essential Action Alert closed at midnight Eastern on August 3, 2026. Three days ago.
The Alert went out May 4 to six functions: Transmission Planner, Planning Coordinator, Transmission Owner, Balancing Authority, Reliability Coordinator, and Transmission Operator. Acknowledgement was due May 11. Full responses were due August 3.
It carries seven Essential Actions covering computational load — AI training, cryptocurrency mining, and conventional data center use.
Modeling data collected against the PERC1 model, with IT load separated from cooling load. Study of operating limits and credible contingencies for aggregate computational load loss. A revised definition of "qualified change." A formal commissioning process. Protection coordination so normally cleared faults don't drop firm load. Dynamic fault recording. And Interpersonal Communication capability between TOPs, RCs, BAs and the load itself.
NERC issued it after finding, in responses to the earlier Level 2 Alert, that entities generally did not have sufficient processes, procedures, or methods to address the risks associated with computational loads.
Why the Closed Window Matters More Than the Open One
A Level 3 Alert is not a Reliability Standard. There is no penalty for failing to implement the Essential Actions. The Alert says so plainly.
But under Rule 810 of NERC's Rules of Procedure, NERC aggregates the responses and delivers an anonymized report to FERC.
Those responses were not open-ended. They asked, action by action, whether your modeling requirements, study process, qualified-change definition, commissioning practice, protection coordination, fault recording, and operator communication already meet the bar — and if not, whether you close the gap in 2026, 2027, 2028, or beyond.
That data set feeds Project 2026-02 Computational Loads, whose draft registry criteria and Standard Authorization Request posted April 1, 2026. NERC's accelerated Large Loads Action Plan targets filing revised registry criteria and Reliability Standards with FERC by the end of 2026.
Translation for the control room and the compliance desk: the gap you self-reported on August 3 is the gap a drafting team is now writing requirements around.
The draft registry threshold is worth knowing — loads 20 MW and greater, connected at 60 kV, containing more than 1 MW of IT load. If that describes something in your footprint, a new registered function is coming toward you.
Three things worth checking while the drafting is still live.
Confirm your RC, TOP, and BA have a working voice or SCADA path to every computational load in the footprint — that is Essential Action 7, and it is an operations problem, not a planning problem.
Verify your contingency files reflect aggregate computational load loss, and that the BA and Resource Planner have those numbers in hand (Essential Action 2).
Check whether "qualified change" in your PC's process actually captures load growth, settings and configuration changes, and repurposing of a facility from crypto to AI training (Essential Action 3).
Those three cost the least and close the most exposure before a standard locks the expectation in.
EPG Solutions Can Help
NERC's aggregated findings will be published anonymized. That tells you what the industry said — not where you sit inside it. Closing that gap is exactly what benchmark intelligence is for: seeing how your modeling, commissioning, and large-load operating practices compare against peer utilities of similar size and footprint, while there is still time to move before the standard lands. Visit EPG Solutions → epgsolutions.services