Standards Help Center
CLO-002-1
Computational Load Operational Data and Communications
CLO-002-1 applies to Computational Load Sites, such as data centers, with a total connected Load of 50 MW or more supplied through electrical equipment connected at 100 kV or above. Computational Load Owners and Operators meet the data specifications that Transmission Operators, Balancing Authorities and Reliability Coordinators write and distribute, and each Computational Load Operator complies with Operating Instructions (with stated exceptions), keeps Interpersonal Communication capability with its Balancing Authority and Transmission Operator, and trains operators who can receive oral two-party, person-to-person Operating Instructions to repeat them back and receive confirmation, or ask for them to be reissued. The standard passed final ballot on October 14, 2026 and was adopted by the NERC Board of Trustees on October 26, 2026; it awaits filing with FERC and FERC approval and is not in force.
Who it applies to
- Computational Load Owners (entities that own and maintain a Computational Load Site) and Computational Load Operators (entities that operate a Computational Load Site). Both meet the data specifications they receive (R7). The Operator carries the Operating Instruction, communication and training requirements (R8, R9, R11, R13, R14, R15).
- Covered sites: Computational Load Sites with a total connected Load greater than or equal to 50 MW that are supplied through electrical equipment connected at a voltage level greater than or equal to 100 kV from one or more points of connection. A Computational Load Site is one or more buildings, structures or installations at a single location that primarily contains information technology infrastructure used for creating, executing and delivering software applications and services, artificial intelligence training, deployment and delivery, cryptocurrency mining, or other computational activities at a data center, and that is supplied through electrical equipment connected to the Bulk-Power System.
- Balancing Authorities, Transmission Operators and Reliability Coordinators, which write and distribute the site data specifications (R1 to R6). Transmission Operators and Balancing Authorities also keep communication capability with Computational Load Operators and give notice of their own communication failures (R10, R12).
Key dates
- October 8, 2026: the NERC Board of Trustees approved proposed Rules of Procedure revisions that would establish Computational Load Owner and Computational Load Operator as functional entity types once FERC approves them, with registry criteria covering sites with a total connected Load of 50 MW or more supplied through electrical equipment connected at 100 kV or above. NERC had not filed them with FERC as of October 20, 2026. The implementation plan expects Computational Load Owners to be registered beginning in 2027.
- October 14, 2026: CLO-002-1 and its implementation plan passed final ballot.
- October 26, 2026: the NERC Board of Trustees adopted CLO-002-1, together with CLO-001-1, CLO-003-1 and the conforming FAC revisions, as reported by the American Public Power Association. NERC files them with FERC by December 31, 2026. CLO-002-1 is not in force; its effective date follows FERC approval and the implementation plan.
- December 31, 2026: deadline for NERC to file the standards with FERC, set by FERC's July 16, 2026 order (196 FERC ¶ 61,031, Docket No. RD26-7-000).
- Effective date (not yet set): where governmental approval is required, as with FERC in the United States, CLO-002-1 and the definitions of Computational Load Operator and the modified Operating Instruction become effective on the first day of the first calendar quarter after the effective date of the order approving it, or as that authority otherwise provides. The Computational Load Site and Computational Load Owner definitions must be approved before CLO-002-1 can take effect. No approval order exists yet, so every date below is counted from an effective date that is still unknown.
- 6 months after the effective date: R1 to R6 (Transmission Operator, Balancing Authority and Reliability Coordinator data specifications).
- 12 months after the effective date: R7 to R15, including every Computational Load Owner and Computational Load Operator requirement.
- Extension request (R8 to R15): an entity with one or more applicable sites in service no later than 12 months after the effective date may ask its Compliance Enforcement Authority for more time if circumstances beyond its control, such as supply chain delays for Interpersonal Communication equipment, prevent establishing Interpersonal Communication capability and protocols at a site. The request identifies the sites, gives a plan and timetable, explains the circumstances, and is due no later than 3 months before the compliance date in question.
Source
NERC Project 2026-02 (final ballot draft, October 2026)October 29, 2026
Requirements
What each requirement asks for, in plain English.
R1 · Transmission Operator data specification (Transmission Operator requirement)
What it means. Each Transmission Operator maintains a documented specification of the Computational Load Site data and information it needs for its Operational Planning Analyses, Real-time monitoring and Real-time Assessments. It lists the data, names the entities responsible for responding, sets a mutually agreeable process for resolving conflicts, and sets how the data is provided: deadlines or periodicity; availability and accuracy criteria; model submissions consistent with the planning model, subject to modifications for operations purposes, as applicable; provisions to update or correct data; and a mutually agreeable format and secure transfer method. A data-center owner or operator that receives it must meet it under R7.
R2 · Balancing Authority data specification (Balancing Authority requirement)
What it means. Each Balancing Authority maintains the same kind of specification, with the same contents as R1, for its analysis functions, Real-time monitoring and Near-Term Energy Reliability Assessments. A data-center owner or operator that receives it must meet it under R7.
R3 · Reliability Coordinator data specification (Reliability Coordinator requirement)
What it means. The Reliability Coordinator maintains the same kind of specification, with the same contents as R1, for its Operational Planning Analyses, Real-time monitoring and Real-time Assessments. A data-center owner or operator that receives it must meet it under R7.
R4 · Distribute the Transmission Operator specification (Transmission Operator requirement)
What it means. Each Transmission Operator distributes its specification to the entities that have the data and information it needs. Receiving it is what brings a Computational Load Owner or Operator under R7.
R5 · Distribute the Balancing Authority specification (Balancing Authority requirement)
What it means. Each Balancing Authority distributes its specification the same way, with the same effect under R7.
R6 · Distribute the Reliability Coordinator specification (Reliability Coordinator requirement)
What it means. The Reliability Coordinator distributes its specification the same way, with the same effect under R7.
R7 · Meet the data specifications you receive
What it means. Each Computational Load Owner and Computational Load Operator that receives a data and information specification from a Transmission Operator, Balancing Authority or Reliability Coordinator under R4, R5 or R6 satisfies the obligations of that documented specification, including its deadlines or periodicity, availability and accuracy criteria, format and transfer method.
Evidence an auditor expects. Electronic or hard copies of data transmittals, or attestations of the receiving entities.
R8 · Comply with Operating Instructions
What it means. Each Computational Load Operator complies with each Operating Instruction issued by its Transmission Operator(s), Balancing Authority or Reliability Coordinator, unless the action cannot be physically implemented or would violate safety, equipment, regulatory or statutory requirements. The proposed modified Glossary definition of Operating Instruction covers a command to change or preserve the state, status, output or input of a Computational Load Site.
Evidence an auditor expects. Dated operator logs, voice recordings or transcripts, electronic communications or equivalent evidence; for an instruction not followed, copies of the safety, equipment, regulatory or statutory requirements relied on. If such a situation has not occurred, an attestation.
R9 · Say when you cannot comply
What it means. Each Computational Load Operator informs the Transmission Operator(s), Balancing Authority or Reliability Coordinator that issued an Operating Instruction of its inability to comply with it.
Evidence an auditor expects. Dated operator logs, voice recordings or transcripts, electronic communications or equivalent evidence that the issuer was informed. If such a situation has not occurred, an attestation.
R10 · Communication capability with Computational Load Operators (Transmission Operator and Balancing Authority requirement)
What it means. Each Transmission Operator and Balancing Authority has Interpersonal Communication capability with the Computational Load Operators in its area, unless it detects a failure of that capability, in which case R12 applies. This is the other end of the Operator's R11 capability.
R11 · Communication capability with your Balancing Authority and Transmission Operator
What it means. Each Computational Load Operator has Interpersonal Communication capability with its Balancing Authority and its Transmission Operator, unless it detects a failure of that capability, in which case R13 applies.
Evidence an auditor expects. Physical assets, or dated evidence such as equipment specifications and installation documentation, test records, operator logs, voice recordings or transcripts, or electronic communication.
R12 · Notice of a communication failure (Transmission Operator and Balancing Authority requirement)
What it means. Each Transmission Operator and Balancing Authority notifies the Computational Load Operators in its area within 60 minutes of detecting a failure of its Interpersonal Communication capability that lasts 30 minutes or longer. This is how an Operator learns of a failure on the Transmission Operator's or Balancing Authority's side.
R13 · Restore failed communication
What it means. A Computational Load Operator that detects a failure of its Interpersonal Communication capability consults each entity affected by the failure (its Balancing Authority, its Transmission Operator or both) to determine a mutually agreeable action to restore the capability.
Evidence an auditor expects. Dated operator logs, voice recordings or transcripts, or electronic communications showing the consultation.
R14 · Initial training on oral Operating Instructions
What it means. Before any of its operating personnel receives an oral two-party, person-to-person Operating Instruction, each Computational Load Operator trains that person to either repeat the instruction, not necessarily verbatim, and receive confirmation from the issuer that the response was correct, or request that the issuer reissue it.
Evidence an auditor expects. Initial training records such as attendance logs, agendas, learning objectives or course materials.
R15 · Repeat back oral instructions during an Emergency
What it means. A Computational Load Operator that receives an oral two-party, person-to-person Operating Instruction during an Emergency either repeats it, not necessarily verbatim, and receives confirmation from the issuer that the response was correct, or requests that the issuer reissue it. Written or oral single-party to multiple-party burst Operating Instructions are excluded.
Evidence an auditor expects. Dated and time-stamped voice recordings if the entity has them, dated operator logs, an attestation from the issuer of the Operating Instruction, memos or transcripts.
For data-center owners
R7 falls on both the Computational Load Owner and the Computational Load Operator, and its content comes from the Transmission Operator, Balancing Authority and Reliability Coordinator specifications under R1 to R6. R8, R9, R11 and R13 to R15 fall on the Operator. R7 evidence is kept for the most recent 90 calendar days. For R8 to R15, voice recordings are kept for the most recent 90 calendar days, and documentation for the most recent 12 calendar months (R8 to R13) or two calendar years (R14 and R15).
Related guidance
Go deeper.
Ask an engineer.
A question about how this standard applies to a specific plant, model or deadline? Bring it to a GridStrong engineer.