NERC finalizes first phase of large-load reliability standards after stakeholder approval

The North American Electric Reliability Corporation (NERC) has finalized the first phase of its large-load reliability standards. The proposed rules for data centers, artificial intelligence facilities, and cryptocurrency operations passed their final stakeholder ballot on October 15. The standards and implementation plans will next go before NERC's Board of Trustees for adoption, followed by submission to the Federal Energy Regulatory Commission (FERC) for U.S. regulatory approval.

This Project 2026-02 package comprises three new reliability standards. They govern interconnection studies and modeling, operational data and communications, and protection coordination and disturbance monitoring. The standards address FERC's July 16 directive requiring NERC to file initial computational-load reliability standards and proposed registration criteria by December 31, 2026. The proposed standards apply to computational-load sites with at least 50 MW of total connected load supplied through electrical equipment connected to the bulk-power system at 100 kV or above.

NERC's board approved proposed revisions to its Rules of Procedure on October 8, establishing two new functional entity categories: Computational Load Owner (CLO) and Computational Load Operator (CLOP). The proposed standards form the first phase of NERC's broader Large Loads Action Plan, which seeks to address gaps in how computational loads are studied, monitored, and coordinated.

New Standards and Requirements

The first standard, CLO-001-1, requires coordinated interconnection studies, commissioning procedures, and planning-model data for qualifying sites. Computational-load owners must provide modeling data covering equipment tripping, ride-through capabilities, and recovery following disturbances. They must also provide information about computing infrastructure use. Owners must verify that configurable, site-specific model parameters reflect installed equipment. Updated verification documentation is required within 180 days of changes to hardware, software, firmware, or settings that alter dynamic response.

The second standard, CLO-002-1, establishes operational data and communications requirements between computational-load facilities and grid entities. Requirement R8 mandates that computational-load operators comply with operating instructions from transmission operators, balancing authorities, or reliability coordinators. An exception exists if the action cannot be physically implemented or would violate safety, equipment, regulatory, or statutory requirements. Requirement R9 requires operators unable to comply to notify the entity issuing the instruction.

The third standard, CLO-003-1, establishes requirements for coordinating protection-system settings and recording electrical disturbances. Computational-load owners must establish a process for developing protection settings so protective systems operate in the intended sequence during faults. This includes coordinating settings across equipment owned by different entities. The standard requires sequence-of-events recording of specified circuit-breaker positions, fault recordings, and continuous dynamic disturbance data.

Scope and Thresholds

The standards apply to computational-load sites with at least 50 MW of connected load supplied through equipment at 100 kV or above. This 100-kV threshold represents a change from NERC's initial registration proposal of 20 MW and 60 kV, raised following stakeholder comments. The package targets computational loads, not AI alone, including sites for AI training, cryptocurrency mining, and other data-center computing.

Large data centers can connect quickly and draw power at a scale that makes their response to faults operationally significant. FERC's July order cites multiple disturbances in which computational loads caused or contributed to bulk-system instability. A July 2024 incident in the Eastern Interconnection caused the near-simultaneous loss of roughly 1,500 MW of data center load. This triggered a frequency rise to 60.053 Hz before returning to 60.0 Hz within four minutes. NERC said: "This incident demonstrates how large-scale load tripping can meaningfully affect BPS frequency."

A January 2026 NERC review examined 26 events involving cryptocurrency mining loads in ERCOT between January 2023 and September 2025. Each event involved load reductions exceeding 100 MW, with facilities losing between 17% and 95% of pre-disturbance consumption. NERC also issued a Level 3 Essential Action Alert on May 4, calling on existing registered entities to address computational-load modeling, interconnection studies, commissioning, protection and control, disturbance monitoring, and operational coordination.

Implementation Timeline

Compliance periods vary by requirement, with initial actions due within 3-6 months and full disturbance monitoring compliance required within 15-36 months depending on site status. NERC has proposed three implementation plans establishing effective dates and phased compliance periods.

Under the CLO-001-1 implementation plan, planning coordinators would have three months after the standard's effective date to establish qualified-change definitions. Transmission owners, distribution providers, and generator owners would have six months to establish interconnection requirements. Under the CLO-002-1 plan, grid operators would have six months to establish operational-data specifications, while computational-load entities would generally have 12 months to meet data and communications rules.

Disturbance monitoring would have the longest proposed transition period. Sites already operating when the standard takes effect would have 36 months to meet recording requirements. Sites entering service afterward would have until 15 months after the standard's effective date or their in-service date, whichever is later. Entities with sites in service within 12 months of the standard's effective date could request extensions if circumstances beyond their control prevent installation of monitoring equipment.

The proposed standards would not become enforceable until applicable regulatory approval and relevant implementation deadlines. Section 215 of the Federal Power Act requires FERC approval for NERC standards to become mandatory and enforceable in the United States. The December 31 filing deadline does not make the proposed standards enforceable. Final adoption by NERC's Board of Trustees and subsequent FERC approval is required before standards become enforceable.