Effective
Requirement or document is in effect according to the official source. Confirm effective date and applicability in the primary text.
Grid reliability · Independent watch
NERC & Grid Reliability Change Watch
Independent engineering interpretation of emerging reliability requirements affecting transmission planning, large loads, data centers, protection, operations and cybersecurity.
Page role: NERC Reliability Change Watch tracks selected evolving NERC matters and GR engineering interpretation. For a broader primary-source and research gateway (NERC, FERC, EPRI, large loads), use Power Reliability Developments.
Last verified: 29 August 2026. This is a selected change watch, not a complete inventory of NERC standards, projects, alerts, or Rules of Procedure postings. Confirm current deadlines and draft text on NERC’s official pages before acting.
Purpose and scope
Why this page exists
Utilities, transmission planners, large-load customers, and consultants face a growing set of reliability-related standards, projects, guidelines, and alerts. This page is a structured watch list for engineering interpretation — not a compliance portal and not a substitute for reading the official requirements.
GR tracks emerging topics that may affect study assumptions, modeling, protection practices, operations readiness, and cybersecurity boundaries. Entries are added only when supported by a supplied or official primary source.
Scope includes: transmission planning, large and emerging loads (including data centers), modeling and validation, ride-through and disturbance response, protection and remedial-action considerations, and selected CIP-related control-center topics — as those subjects become verified.
Engineering perspective
Prepared by Dr. Sudhir Agarwal, drawing on more than 35 years of experience in power-system planning and reliability, probabilistic methods, utility studies, reliability software, and engineering-study automation. The objective is to translate changing requirements into practical questions about models, studies, controls, evidence, and implementation.
Prepared independently from publicly available NERC, FERC and industry materials. General Reliability is not affiliated with or endorsed by NERC. This information provides engineering interpretation and does not constitute legal advice, compliance certification or a substitute for review of the official requirements.
How to read the tracker
Status legend
Approved / Future Effective
Approved or filed path exists, with a future effective date or implementation timeline still to be confirmed from the official source.
Proposed / Under Development
Project, draft, or proposal is under development or industry review. Content may change before finalization.
Guideline / Alert
Guidance, white paper, lesson learned, or alert — useful for engineering awareness, not automatically a mandatory standard.
Structured tracker
Change watch table
Selected developments are shown because they may materially affect utilities, transmission planners, data centers, and other large-load stakeholders. Status and dates were checked against NERC primary sources and the NERC One-Stop-Shop workbook; applicability still requires review of the governing documents.
Current attention — August 2026
Status checked August 29, 2026. NERC has moved from broad large-load risk identification into specific proposed registration language and draft Reliability Standards for computational loads. That does not mean every data center is a NERC-registered entity, that Computational Load Owner or Operator functions are already effective, or that draft CLO text is enforceable. Final applicability, approvals, and effective dates remain unresolved. Deadlines and draft text should be reconfirmed on NERC’s official pages before acting. For facility electrical and POI context, see Data-Center Power & Grid Reliability and Load Behavior & Grid Interaction.
A. Project 2026-02 formal posting — draft standards under development
NERC’s Project 2026-02 Computational Loads page reports that initial posting was authorized on August 19, 2026. A formal comment period is open through 8:00 p.m. Eastern, Friday, September 18, 2026. Ballot-pool formation runs through 8:00 p.m. Eastern, Thursday, September 3, 2026. Initial ballots for the standards and implementation plans, and non-binding VRF/VSL polls, are scheduled September 9–18, 2026. Status checked August 29, 2026 — reconfirm deadlines and drafts on NERC’s official pages.
The proposed package posted for comment (all draft Reliability Standards / proposed revisions under development, not final or effective) includes:
- CLO-001-1 — Computational Load Interconnection, Studies, & Modeling Data
- CLO-002-1 — Computational Load Operational Data and Communications
- CLO-003-1 — Computational Load Protection Coordination & Disturbance Monitoring
- Limited proposed updates to FAC-001-5 (Facility Interconnection Requirements) and FAC-002-5 (Facility Interconnection Studies)
- Associated implementation plans, technical rationale, and VRF/VSL materials
Engineering significance of the draft package (paraphrased): clearer expectations around interconnection requirements and studies; modeling-data ownership and exchange; operating data and communications; protection coordination; disturbance monitoring; and the interface between proposed computational-load entities and existing planning/interconnection functions. Treat every CLO/FAC item as proposed draft language until NERC’s standards and regulatory processes conclude.
B. Registration-criteria proposal — Rules of Procedure
NERC is posting proposed Rules of Procedure revisions (Appendices 2, 5A, and 5B) that would establish Computational Load Owner and Computational Load Operator registered-entity types/functions. An additional public-comment period runs August 19–September 18, 2026. These functions and criteria are proposed, not yet effective. Whether any facility or organization would be registered will depend on the final approved registration criteria and governing process—not on draft language alone. Official materials: Proposed Changes to Rules of Procedure and the Large Loads Action Plan summary. Status checked August 29, 2026.
C. Disturbance Performance for Computational Loads — Standard Authorization Request
NERC’s Large Loads Working Group issued a Standard Authorization Request (SAR) on Disturbance Performance for Computational Loads on 26 August 2026, with comments requested through 24 September 2026. A SAR seeks or frames further standards work; it is not itself an effective Reliability Standard and does not invent enforceable requirements. The SAR focus, as described by NERC, relates to disturbance-related computational-load performance—including concerns associated with rapid or simultaneous load reduction, oscillatory behavior, ride-through/disturbance response, and bulk-power-system consequences. Official SAR PDF: Disturbance Performance for Computational Loads SAR; comment matrix: SAR comment matrix (XLSX). Hub: Large Loads Action Plan. Status checked August 29, 2026.
D. Upcoming event — two-day Load Modeling Working Group workshop
Load Modeling Working Group Workshop on Data Center Load Modeling is a two-day workshop:
- Session 1: September 15, 2026, 12:00–5:00 p.m. Eastern
- Session 2: September 16, 2026, 12:00–5:00 p.m. Eastern
Microsoft Teams. Official event: 09-15-26 LMWG Workshop. Official agenda: Data Center Load Modeling Workshop agenda (PDF). This is a workshop, not a standards ballot or effective requirement.
E. Continuing items (positioned accurately)
- Level 3 Essential Action Alert issued May 4, 2026: NERC identified seven actions for applicable registered entities. The registered-entity response deadline was August 3, 2026 and has passed; retain response evidence where applicable and monitor subsequent findings/follow-up. The Alert does not imply that every data center is a NERC-registered entity or was directly subject to the Alert. Official announcement and Alert PDF.
- Reliability Guideline: Risk Mitigation for Emerging Large Loads remains non-binding guidance.
- Project 2026-02 remains under development despite the formal draft posting; final applicability and effective dates are unresolved.
- Past event: the 27 August 2026 Project 2026-02 industry webinar is no longer current attention; treat it as a completed informational session if useful for context.
NERC Large Loads Action Plan (official hub) · Project 2026-02 · Proposed Rules of Procedure changes
| Topic | NERC document or project | Status | Important date | Who may be affected | Why it matters | Practical action | Official source |
|---|---|---|---|---|---|---|---|
| Draft computational-load Reliability Standards | Project 2026-02: proposed CLO-001-1, CLO-002-1, CLO-003-1; limited proposed FAC-001-5 and FAC-002-5 updates; implementation plans | Draft standards · formal posting / comment | Initial posting authorized August 19, 2026. Comments through 8:00 p.m. Eastern, September 18, 2026. Ballot pool through 8:00 p.m. Eastern, September 3, 2026. Initial ballots and non-binding VRF/VSL polls scheduled September 9–18, 2026. Status checked August 29, 2026; dates may change—reconfirm on NERC’s official pages. FERC year-end directive context remains December 31, 2026 for related filings—drafts are not yet effective standards. | Utilities, planners, operators, interconnection hosts, and organizations that may later fall under proposed Computational Load Owner/Operator criteria—if and when approved | Draft package addresses interconnection/studies/modeling data, operational data and communications, and protection coordination & disturbance monitoring, plus limited FAC clarity—still proposed, not enforceable CLO standards. | Compare study assumptions and data ownership with the draft package without treating drafts as binding. Follow comments and ballots; inventory models, telemetry, protection, and disturbance-monitoring evidence. See What organizations should do now. | NERC Project 2026-02 |
| Proposed Computational Load registration criteria | Proposed Rules of Procedure revisions (Appendices 2, 5A, 5B) — Computational Load Owner and Computational Load Operator | Proposed ROP / registration criteria | Additional public comment August 19–September 18, 2026. Proposed Computational Load Owner and Computational Load Operator functions are not yet effective. Status checked August 29, 2026. | Potential future Computational Load Owners/Operators; coordinating utilities, planners, and operators | Proposed entity types would frame who may become subject to related reliability obligations—if approved. Applicability depends on final criteria and process. | Determine transmission- vs distribution-connection and which entity owns interconnection, planning, operating, protection, and model obligations. Do not assume automatic registration. | Proposed Changes to Rules of Procedure · Large Loads Action Plan |
| Disturbance performance standards scoping | Standard Authorization Request: Disturbance Performance for Computational Loads (Large Loads Working Group) | SAR · comments requested | Issued August 26, 2026; comments through September 24, 2026. A SAR is not an effective Reliability Standard. Status checked August 29, 2026. | Planners, operators, large-load stakeholders, and future standards-development participants | Frames further work on disturbance-related computational-load behavior (e.g., rapid/simultaneous reduction, oscillations, ride-through/disturbance response) without creating draft enforceable requirements by itself. | Assess fast load-reduction, oscillation, ride-through, protection, transfer, reconnection, and rebound behavior with study-appropriate models; follow SAR comments without inventing requirements. | SAR PDF · Comment matrix · Action Plan hub |
| Immediate computational-load risk actions | Level 3 Essential Action Alert: Computational Load Modeling, Studies, Instrumentation, Commissioning, Operations, Protection, and Control | Essential Action Alert | Issued May 4, 2026. NERC identified seven actions for applicable registered entities. Registered-entity responses were due August 3, 2026; the deadline has passed. Monitor subsequent findings and follow-up. Status checked August 29, 2026. | Registered entities identified by NERC for the Alert; coordination may involve large-load customers and equipment providers. Does not mean every data center was subject to the Alert. | NERC cited rapid customer-initiated load reductions and oscillations that can leave little time for real-time response. | Preserve Level 3 Alert response evidence where applicable. Monitor NERC follow-up concerning models, studies, instrumentation, commissioning, operations, protection and controls. | NERC announcement · Alert PDF |
| Risk mitigation for emerging large loads | Reliability Guideline: Risk Mitigation for Emerging Large Loads | Non-binding guideline | Published 30 April 2026 | Utilities, grid operators, large-load owners/developers, and equipment manufacturers | The guideline recommends coordinated practices to integrate industrial-scale loads while protecting grid stability. Guidelines do not create mandatory Reliability Standard obligations by themselves. | Benchmark interconnection, modeling, ride-through, communications, and operating practices against the recommendations—without treating the guideline as enforceable. | NERC Reliability Guidelines |
| Planning-model data requirements | MOD-032-2 — Data for Power System Modeling and Analysis | Future enforcement | Effective 1 April 2028; Requirements R2-R4 transition on 1 April 2029 | Planning Coordinators, Transmission Planners, and entities that provide modeling data | Revised data requirements and reporting procedures support planning-horizon case development and more consistent system analysis. | Inventory required data, owners, formats, validation checks, submission workflows, and evidence well before transition dates. | NERC MOD-032-2 |
| Steady-state and dynamic model validation | MOD-033-3 — Steady-State and Dynamic System Model Validation | Effective | Effective 1 April 2026 | Reliability Coordinators and other applicable registered entities identified in the standard | The standard establishes a process for model validation to support model accuracy. | Confirm validation procedures, actual-system comparison methods, discrepancy handling, responsibilities, and retained evidence. | NERC MOD standards |
| Transmission Owner Control Center classification | CIP-002-8 — Cyber Security: BES Cyber System Categorization | Future enforcement | Effective 1 July 2028 | Transmission Owners with applicable real-time control capabilities; CIP and operations teams | The revised Control Center definition can bring certain Transmission Owner facilities with qualifying real-time control capability into TOCC classification and CIP scoping. An ordinary computational-load data center does not automatically become a Transmission Owner Control Center. | Assess whether applicable facilities meet the revised Control Center definition; document real-time monitoring and control functions, operating authority, system architecture and BES Cyber System categorization. | NERC CIP-002-8 |
| Operational data and information specifications | TOP-003-7 — Transmission Operator and Balancing Authority Data and Information Specification and Collection | Future enforcement | Effective 1 October 2026 | Transmission Operators, Balancing Authorities, and entities supplying requested operational data | The standard supports the data and information needed to plan, monitor, and assess reliable operation. | Confirm data specifications, providers, collection processes, quality checks, delivery timing, and evidence before the effective date. | NERC TOP standards |
Status checked August 29, 2026. Source base: official NERC Project 2026-02 posting, Proposed Changes to Rules of Procedure, Large Loads Action Plan hub and linked Q2 2026 update / FAQ / SAR PDFs, LMWG workshop event and agenda, Level 3 Alert announcement and Alert PDF, Reliability Guidelines, and FERC order context. Confirm applicability, later revisions, and deadlines in the controlling NERC documents before acting. This page remains a selected tracker, not a complete NERC inventory.
GR engineering interpretation
What organizations should do now
The following is independent engineering interpretation—not legal advice, not official applicability determination, and not compliance certification. Draft CLO language and proposed registration criteria are not binding. GR does not determine whether an organization must register with NERC or certify compliance.
Clarify connection and ownership
- Determine whether the facility is transmission- or distribution-connected
- Identify which entity owns interconnection, planning, operating, protection, and model obligations
- Document data-sharing, confidentiality, telemetry, and operating-coordination boundaries
Compare drafts to existing evidence
- Compare agreements and study assumptions with the draft CLO/FAC package—without treating drafts as binding
- Inventory static, dynamic, protection, control, communications, and disturbance-monitoring data
- Identify model owners, parameter sources, validation evidence, and update responsibilities
Assess disturbance behavior and process
- Assess fast load-reduction, oscillation, ride-through, protection, transfer, reconnection, and rebound behavior
- Follow comments and ballots; reconfirm deadlines on NERC pages
- Preserve Level 3 Alert response evidence where applicable
How this connects to GR services
Where helpful, GR can support engineering review through Load Behavior & POI Model Assessment, Grid Capacity & Flexibility Assurance, Architecture & Reliability, independent study review, model/data-gap assessment, probabilistic reliability and nonperformance analysis, and study automation / evidence organization. See also Power-System Reliability & Large-Load Engagements.
Boundary: GR provides engineering interpretation and scoped assessments. GR does not provide legal advice, does not determine official NERC applicability or registration, and does not certify compliance.
Outlook
What to Expect Through Year-End 2026
The following separates near-term process milestones from work that remains subject to NERC’s stakeholder, standards-development and regulatory processes. Dates and outcomes may change; controlling NERC and FERC documents govern. Status checked August 29, 2026. Reconfirm deadlines and drafts on NERC’s official pages.
Near-term milestones (reconfirm)
- September 3, 2026 — Project 2026-02 ballot-pool formation closes (8:00 p.m. Eastern)
- September 9–18, 2026 — Project 2026-02 initial ballots and non-binding VRF/VSL polls (scheduled)
- September 15–16, 2026 — two-day LMWG Workshop on Data Center Load Modeling, 12:00–5:00 p.m. Eastern each day (Teams)
- September 18, 2026 — Project 2026-02 formal comments and proposed ROP registration-criteria comments due (8:00 p.m. Eastern for the standards posting)
- September 24, 2026 — Disturbance Performance SAR comments due
- September 16, October 21 and November 18, 2026 — scheduled Standards Committee meetings (per prior bulletin; reconfirm)
- December 31, 2026 — FERC-directed deadline associated with computational-load registration criteria and initial Reliability Standards/Rules of Procedure revisions
Past informational session: August 27, 2026 Project 2026-02 industry webinar (completed). Reconfirm all dates on NERC project, ROP, Action Plan, and event pages.
Work under development
- Draft CLO-001-1 / CLO-002-1 / CLO-003-1 and limited FAC-001-5 / FAC-002-5 revisions under formal comment and ballot
- Proposed Computational Load Owner and Operator registration criteria (ROP Appendices 2, 5A, 5B)
- Disturbance Performance for Computational Loads SAR (further standards scoping)
- Continued work on load models, model validation and disturbance-performance information
- Coordination among NERC, Regional Entities, planners, operators, utilities and large-load stakeholders
Specific drafts, ballots, approvals, filings and effective dates must be confirmed as NERC publishes them. Drafts are not final or enforceable CLO standards.
Items to monitor
- NERC analysis or follow-up resulting from Level 3 Alert responses
- Changes to proposed entity registration and applicability thresholds
- Ballot results, successive drafts, and any future-effective dates if standards are approved
- Protection, control, instrumentation, ride-through and commissioning expectations
- FERC action on NERC submissions and related large-load proceedings
- Regional Entity and RTO/ISO implementation implications
These are monitoring topics, not promises that NERC will issue a final enforceable CLO standard by year-end.
Consulting connection
How GR Can Help
Translate emerging requirements into study questions
Map alerts, guidelines, and projects under development to planning cases, modeling checks, protection assumptions, and documentation needs — with engineers retaining judgment.
Organize evidence and engineering workflows
Connect assumptions, study outputs, checklists, and follow-up tracking so teams can show what was reviewed and when — without claiming compliance certification.
Assess transmission and computational-load implications
Evaluate how emerging topics may affect transmission systems, computational loads, data centers, and the grid–facility interface — distinguishing confirmed requirements from work still under development.
Probabilistic reliability and study review
Support probabilistic assessment and independent transmission-study review and QA where projects need decision-focused interpretation of power-flow, transient-stability, and reliability results.
Technical training
Provide specialist training and mentoring on reliability methods, study automation, and practical use of GR software where useful — connected to, not a substitute for, the official requirements.
Discuss a reliability change topic
Contact GR to discuss how emerging reliability topics may affect your planning, modeling, protection, operations, or documentation workflows.