July 26, 2026 | Source: NERC Level 3 Essential Action Alert — "Computational Load Modeling, Studies, Instrumentation, Commissioning, Operations, Protection, and Control" (initial distribution May 4, 2026)
NERC's Level 3 Computational Load Alert: Responses Due August 3
Eight days left. Responses to NERC's Level 3 Essential Action Alert on computational load are due in the NERC Alert System by midnight Eastern on August 3, 2026. Acknowledgement was due back on May 11.
The alert went to six functional registrations: TP, PC, TO, BA, RC, and TOP. It carries seven Essential Actions covering modeling, planning studies, the definition of "qualified change," commissioning, protection coordination, dynamic fault recording, and operator-to-data-center communications.
NERC issued it after responses to the earlier Level 2 Alert showed most entities did not have adequate processes for computational load — AI training, inference, cryptocurrency mining, and traditional data center use. Under Rule 810 of the Rules of Procedure, NERC aggregates the responses and files an anonymized report with FERC.
The regulatory pressure behind it is not theoretical. On July 16, 2026, FERC issued an order in Docket No. RD26-7-000 directing NERC to develop and submit new or modified Reliability Standards addressing computational load integration, along with Rules of Procedure revisions that include registry criteria for computational load entities. Both are due December 31, 2026.
What This Means in the Planning Group and the Control Room
A few specifics worth flagging. NERC's draft threshold for a "Computational Load Entity" is 20 MW or greater, connected at 60 kV, with more than 1 MW of IT load. And the alert is explicit that entities should implement these actions before an interconnection request arrives — not after.
Planners: Essential Action 1 sets the PERC1 model as the minimum modeling baseline, with IT load modeled separately from cooling and other non-IT load. Essential Action 2 asks you to treat the aggregate loss or reduction of computational load as a credible Contingency and update your Contingency files accordingly.
Operators: Essential Action 7 lands squarely on TOPs, RCs, and BAs — establish Interpersonal Communication capability with computational load entities and build joint operating procedures so you can issue instructions ahead of a BES Emergency instead of during one. On most desks today, that is a procedure and training gap, not an equipment gap.
The alert is not a Reliability Standard, and there is no penalty for choosing not to implement the Essential Actions. But the response you file in August becomes part of the record FERC reads while NERC drafts the standards that will carry penalties. Answer it accordingly.
EPG Solutions Can Help
Essential Action 7 is a people problem before it is a technology problem — RCs, TOPs, and BAs need to know how to coordinate with a load that can shed hundreds of megawatts in seconds. GridCert RC training builds that coordination into operator competency now, so when the standards land in December, compliance is a documentation exercise instead of a scramble. Visit EPG Solutions → epgsolutions.services