Standards Help Center
Computational Load Interconnection, Studies, & Modeling Data
CLO-001-1 sets interconnection, study and modeling data requirements for 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. Transmission Owners, Distribution Providers and Generator Owners that interconnect these sites document interconnection requirements. Transmission Planners and Planning Coordinators study the interconnections and set modeling data requirements. Each Computational Load Owner cooperates on the studies, submits modeling data, answers technical concerns and verifies its models. 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.
Source
NERC Project 2026-02 (final ballot draft, October 2026)October 29, 2026
Requirements
What it means. Each Transmission Owner and Distribution Provider documents its Computational Load Site interconnection requirements, updates them as needed and makes them available on request. One with no existing site interconnection must do so within 45 calendar days of full execution of an Agreement to study a new site's interconnection. R4 studies check a data-center interconnection's adherence to these requirements, along with Reliability Standards and planning criteria.
What it means. The R1 requirements include procedures for coordinated studies of new interconnections and qualified changes, for notifying those responsible for affected systems, and for coordinating site-specific interconnection requirements and commissioning with the Transmission Planner, Planning Coordinator, Transmission Operator, Balancing Authority and Reliability Coordinator. They set how studies and commissioning of a data-center interconnection are coordinated with the planning and operating entities.
What it means. Within 45 calendar days of full execution of an Agreement to study interconnecting a Computational Load Site to its existing Facility used to interconnect to the Transmission system, the Generator Owner documents Computational Load Site interconnection requirements and makes them available on request. The requirements address procedures for coordinating them with the applicable Transmission Owner and applicable Distribution Provider.
Evidence an auditor expects. Dated, documented Computational Load Site interconnection requirements.
What it means. Each Transmission Planner and Planning Coordinator studies the reliability impact of new Computational Load Site interconnections and of existing ones seeking a qualified change (R7): impact on affected systems; adherence to Reliability Standards, planning criteria and the site interconnection requirements; and steady-state, short-circuit and dynamics studies as necessary, with documented assumptions, alternatives and coordinated recommendations. A data-center owner supports these studies with data under R5.
What it means. Each Computational Load Owner seeking to interconnect a new Computational Load Site, or whose existing site interconnection is seeking to make a qualified change as defined by the Planning Coordinator under R7, coordinates and cooperates on studies with the Transmission Owner, Generator Owner, Distribution Provider, and Transmission Planner or Planning Coordinator. That includes, but is not limited to, providing data as described in R4 Parts 4.1 to 4.4.
Evidence an auditor expects. Documents containing the data provided in response to the requests of the Transmission Owner, Generator Owner, Distribution Provider, and Transmission Planner or Planning Coordinator.
What it means. Each Transmission Owner, Generator Owner and Distribution Provider coordinates and cooperates with its Transmission Planner or Planning Coordinator on studies of its interconnections of new Computational Load Sites, or of existing sites seeking a qualified change as defined under R7, including but not limited to providing data as described in R4 Parts 4.1 to 4.4.
Evidence an auditor expects. Documents containing the data provided in response to the requests of the Transmission Planner or Planning Coordinator.
What it means. Each Planning Coordinator maintains a publicly available definition of qualified change for the interconnection of Computational Load Sites. That posted definition decides which changes at an existing site bring in the study duties in R4 to R6 and an incremental data submission under R9, as specified under R8 Part 8.3.2.
What it means. Each Planning Coordinator and its Transmission Planners jointly develop steady-state, dynamics and short circuit modeling data requirements and reporting procedures for Computational Load Sites in the planning area. They name the data and the entity responsible for each item, including at a minimum parameters, settings and capabilities related to cessation, tripping, Ride-through and post-Disturbance recovery; the amount or percentage of information technology infrastructure; and its expected uses or behaviors. They also set the data format, the level of modeling detail, a submission schedule of at least once every 13 calendar months, incremental submissions for the as-built site after commissioning and for a qualified change, and how the requirements are distributed or posted. This is the specification a Computational Load Owner's R9 data must follow.
What it means. Each Computational Load Owner provides steady-state, dynamics and short circuit modeling data for its sites to its Transmission Planner(s) and Planning Coordinator(s), following the R8 data requirements and reporting procedures. For data that has not changed since the last submission, a written confirmation that it has not changed is sufficient. If dynamic models are required, the owner provides models accepted by the Transmission Planner, or as otherwise agreed, where such models are available.
Evidence an auditor expects. Records such as emails or postal receipts showing the recipient and date of each data submission, or the written confirmation that the data has not changed.
What it means. When a Computational Load Owner receives written notification from its Planning Coordinator or Transmission Planner of technical concerns with its R9 data, stating the technical basis or reason, it responds with either updated data or an explanation with a technical basis for keeping the current data. The response is due within 90 calendar days of receipt unless the notifying entity agrees to a longer period.
Evidence an auditor expects. Records such as emails or postal receipts showing the recipient and date of the response, or a statement that no written notification of technical concerns was received.
What it means. Each Computational Load Owner gives its Transmission Planner documentation of Model Verification showing that the configurable, site-specific parameters of the models behind its R9 data are representative of the design and settings of the in-service equipment at each site, with a written statement naming any parameter that cannot be verified and why. Documentation is due within 365 calendar days after the in-service date, within 180 calendar days after a hardware, software, firmware or setting change that alters the dynamic response, and then within 10 calendar years of the most recent transmittal. In-service date means the site is fully ready and available for its intended specific use, including completion of its interconnection.
Evidence an auditor expects. Dated evidence for each applicable site, such as an email message, postal receipt or web portal upload, that the documentation was provided to the Transmission Planner.
A Computational Load Owner's own obligations are R5, R9, R10 and R11. Whether a change at an existing site brings in R5 depends on the Planning Coordinator's posted definition of qualified change (R7), and the content, format and schedule of R9 data come from the Planning Coordinator and Transmission Planner's R8 requirements. Evidence for R5 is kept for three years; evidence for R9 to R11 is kept from the last audit onward.
A Generator Owner that fully executes an Agreement to study interconnecting a Computational Load Site to its existing Facility documents interconnection requirements within 45 calendar days of full execution (R3) and coordinates and cooperates on the studies with its Transmission Planner or Planning Coordinator (R6). Under the implementation plan, R3 applies from 6 months and R6 from 9 months after the effective date. Evidence for both is kept for three years.
Related guidance
A question about how this standard applies to a specific plant, model or deadline? Bring it to a GridStrong engineer.