We are hiringCome build the future of the grid with us.Find your role

Modules · Compliance studies · Module 087

CLO-003-1 Computational Load Protection Coordination & Disturbance Monitoring

Protection System settings coordination and event, fault and disturbance recording for data-center sites under NERC's proposed CLO-003-1.

About this module

What this module covers.

The new CLO-003-1 standard (Computational Load Protection Coordination & Disturbance Monitoring) applies to Computational Load Sites with a total connected Load of 50 MW or more supplied through electrical equipment connected at 100 kV or above, and requires disturbance monitoring data at each site and coordinated Protection System settings. The Computational Load Owner (CLO) must have sequence of event recording (SER) of circuit breaker position for breakers associated with equipment it owns, including buses and, as applicable, the main power transformers, on-site generation, and shunt static and dynamic reactive devices (R1). The owner of the main power transformer(s) supplying the site, whether the CLO, a Transmission Owner, a Distribution Provider, or a Generator Owner, must have triggered fault recording (FR) on the high side of the main power transformer(s) or common point of connection, capturing phase-to-neutral voltages, phase and residual or neutral currents, and three-phase real and reactive power, with at least a two-cycle pre-trigger, a 2.0-second total record, 64 samples per cycle, and triggers for neutral (residual) overcurrent, phase overvoltage and undervoltage, and overfrequency and underfrequency (R2, R3); and must have continuous dynamic disturbance recording (DDR) and storage of voltage, current, real and reactive power flows, and frequency at the same location, with an input sampling rate of at least 960 samples per second and an output recording rate of at least 60 times per second (R4, R5). The entity responsible for the data must synchronize it to UTC with device clock accuracy within +/-1 millisecond (R6), keep it retrievable for 20 calendar days, inclusive of the day recorded, and provide requested data to its Transmission Planner, Planning Coordinator, Transmission Operator, Balancing Authority, Reliability Coordinator, Regional Entity, or NERC within 15 calendar days of a request unless the requestor grants an extension, with SER data in ASCII CSV following Attachment 1, FR and DDR data in CSV or COMTRADE, and COMNAME file naming (R7), and, on discovering a recording failure, restore it within 90 calendar days or submit a Corrective Action Plan (CAP) to the Regional Entity within 90 calendar days and implement it (R8). The CLO must also establish and use a process for developing new and revised Protection System settings so that Protection Systems operate in the intended sequence during Faults, including provisions to coordinate with Transmission Owners, Generator Owners, and Distribution Providers whose equipment is electrically joined at the site (R9, R10).

CLO-003-1 is pending FERC approval; FERC has directed NERC to file computational load Reliability Standards by December 31, 2026. If FERC approves it, the standard becomes effective in the United States on the first day of the first calendar quarter after the effective date of FERC's approval order, or as FERC otherwise provides. The implementation plan sets compliance with R1-R8 at 36 months after the effective date for sites in service on or before the effective date, and at 15 months after the effective date or the in-service date, whichever is later, for sites in service after it; R9 and R10 apply 9 months after the effective date. An entity with a site in service no later than 12 months after the effective date may request an extension of the R1-R8 compliance dates from its Compliance Enforcement Authority if circumstances beyond its control, such as supply chain delays, inability to secure scheduled outages, or other exceptional circumstances, prevent installation of Disturbance Monitoring Equipment; the request is due no later than 3 months before the compliance date.

This module covers digitizing the assessment and compilation of compliance documentation to support compliance preparedness for NERC CLO-003-1.

At a glance

Module: 087
Kind: Compliance studies
Governing body: NERC
Applies to: New and in-service sites
Typical time: Follows the standard's clocks

Dashboard capabilities

  • Automated Compliance Workflow for CLO-003-1
  • Plant File Manager (intake of disturbance monitoring equipment specifications, station drawings, and Protection System settings)
  • Dashboard (per-site tracking of R1-R8 compliance dates, 15-day data request deadlines, and 90-day restoration or CAP deadlines)

Support services

What GridStrong does inside this module.

Task 1: Develop Compliance Procedure

  • Create an audit-ready compliance procedure for meeting the CLO-003-1 requirements, working collaboratively across engineering, field services, operations, and compliance departments. This includes:
  • Identifying applicable Computational Load Sites and the owner of the main power transformer(s) at each site, which determines who holds R2-R5 and R6-R8 for FR and DDR data (the CLO holds R1 and R6-R8 for its SER data at every site), along with SMEs, roles, responsibilities, and ownership
  • Determining specific actions and evidence to demonstrate compliance with specific requirements and measures
  • Conducting a gap analysis comparing current practices versus the new requirements, identifying missing processes, incomplete documentation, any staff training needed, etc.
  • Developing clear step-by-step procedures for CLO-003-1 that align with internal controls and documentation policies, including SER/FR/DDR device configuration, time synchronization, data retention and retrieval, and recording failure response
  • Establishing compliance timelines that align with the implementation plan (R1-R8 at 36 months after the effective date for sites in service on or before the effective date, or at 15 months after the effective date or the in-service date, whichever is later, for sites in service after it; R9-R10 at 9 months)
  • Defining and determining specific compliance evidence per site, including retention of R1-R8 evidence for three calendar years and R9-R10 evidence since the last audit

Task 2: Assess Disturbance Monitoring at each Site (R1-R5)

  • Create an inventory of all disturbance monitoring equipment (DME) and circuit breakers at the site.
  • Verify SER of breaker position (open/close) for breakers associated with equipment you own, including buses and, as applicable, main power transformers, on-site generation, and shunt static and dynamic reactive devices (R1).
  • Where you own the main power transformer(s), verify FR on the high side of the main power transformer(s) or common point of connection: phase-to-neutral voltage for each phase, each phase current and the residual or neutral current, and three-phase real and reactive power (R2); a pre-trigger of at least two cycles and a total record of at least 2.0 seconds, a recording rate of at least 64 samples per cycle, and triggers for neutral (residual) overcurrent, AC phase overvoltage and undervoltage, and overfrequency and underfrequency (R3).
  • Where you own the main power transformer(s), verify continuous DDR and storage at the same location of phase-to-neutral voltages, phase and residual or neutral currents, three-phase real and reactive power flows for all circuits where current is measured, and frequency (R4), with an input sampling rate of at least 960 samples per second and an output recording rate of at least 60 times per second (R5).
  • Identify deficiencies and propose new equipment, or modifications to existing equipment where feasible, to meet the requirements.
  • For sites not yet in service, review the DME design so recording is in place by the compliance date.

Task 3: Verify Time Synchronization (R6)

  • Verify that each SER, FR, and DDR device synchronizes to Coordinated Universal Time (UTC), with or without a local time offset, with device clock accuracy within +/-1 millisecond of UTC.
  • Document the time source, device configuration, and synchronization status indication as evidence (M6).

Task 4: Set Up Data Retention and Production (R7)

  • Confirm that SER, FR, and DDR data is retrievable for 20 calendar days, inclusive of the day it was recorded.
  • Develop the request-response procedure for providing data to the Transmission Planner, Planning Coordinator, Transmission Operator, Balancing Authority, Reliability Coordinator, Regional Entity, or NERC within 15 calendar days of a request, unless the requestor grants an extension.
  • Format data on request: SER in ASCII CSV following Attachment 1 (Date, Time, Local Time Code, Site Name, Device, State); FR and DDR in CSV with appropriate headers or in IEEE C37.111 COMTRADE (1999 or later); file names in IEEE C37.232 COMNAME (2011 or later).

Task 5: Respond to Recording Failures (R8)

  • On discovery of a failure of SER, FR, or DDR recording capability, track the 90-calendar-day deadline and plan restoration.
  • Where restoration cannot be completed within 90 calendar days, prepare a CAP for submission to the Regional Entity within 90 calendar days, then track its implementation against the CAP timeline.
  • Keep dated failure reports, restoration records, SCADA records, and CAP transmittals as evidence (M8).

Task 6: Develop the Protection System Settings Coordination Process (R9, R10)

  • Develop the CLO's process for developing new and revised Protection System settings so that Protection Systems operate in the intended sequence during Faults (R9).
  • For settings at sites that electrically join equipment owned by Transmission Owners, Generator Owners, or Distribution Providers, include provisions to respond to each owner's proposed settings by identifying coordination issues or affirming that none were identified; to verify that identified issues are addressed before implementation; and to communicate with the other owner(s) of the electrically joined equipment regarding revised settings resulting from unforeseen circumstances that arise during implementation or commissioning, Misoperation investigations, maintenance activities, or emergency replacements required as a result of Protection System component failure (Part 9.1).
  • Apply the process to each new or revised settings package and keep dated documentation of its use (R10, M10).

Task 7: Prepare Extension Requests (where applicable)

  • For sites in service no later than 12 months after the effective date where circumstances beyond your control prevent DME installation, prepare the extension request to the Compliance Enforcement Authority, including site identification, a plan and timetable for installing the DME, a description of the circumstances and why they are beyond your control, and any other relevant information.
  • Track the filing deadline of 3 months before the compliance date, and prepare an updated request if more time is required.

Final deliverables

  • Task 1: Compliance procedure for NERC CLO-003-1.
  • Task 2: Disturbance monitoring compliance report per site documenting the DME and breaker inventory, the assessment against R1-R5, deficiencies, proposed equipment or modifications, and a compliance timeline that meets the implementation plan.
  • Task 3: Time synchronization verification record per site.
  • Task 4: Data retention and request-response procedure, an SER CSV template following Attachment 1, and a formatted data package per request.
  • Task 5: Restoration record or CAP per recording failure, ready for your submission to the Regional Entity.
  • Task 6: Protection System settings coordination process, and a dated coordination record per new or revised settings package.
  • Task 7: Extension request per affected site, ready for your submission to the Compliance Enforcement Authority.

What we need from you

  • Site one-line diagram, station drawings, total connected Load, and the voltage level at which the electrical equipment supplying the site is connected to the Bulk-Power System, for each point of connection.
  • Ownership of the main power transformer(s) supplying each site (CLO, Transmission Owner, Distribution Provider, or Generator Owner).
  • Circuit breaker list identifying the equipment each breaker is associated with (buses, main power transformers, on-site generation, shunt static and dynamic reactive devices).
  • DME specifications, configuration, and settings, including recording locations, measured quantities, sampling and recording rates, record lengths, triggers, data storage, and time synchronization source.
  • Current Protection System settings, and proposed settings received from Transmission Owner, Generator Owner, or Distribution Provider owners of electrically joined equipment.
  • In-service date of each site.
  • Data requests received and records of any recording failures.
  • For extension requests: DME procurement, engineering, installation, commissioning, and outage schedules.

Assumptions and considerations

How the scope is bounded.

  • CLO-003-1 is pending FERC approval; it has no effective date until FERC approves it, and compliance then phases in under the implementation plan. We align the compliance procedure with the version FERC approves.
  • Applicability depends on registration as a Computational Load Owner under the Rules of Procedure registry criteria the NERC Board approved on October 8, 2026 (a Computational Load Site with a total connected Load of 50 MW or more supplied through electrical equipment connected at 100 kV or above); those criteria have not yet been filed with FERC, and NERC expects Computational Load Owners to be registered beginning in 2027.
  • If you are a Generator Owner that owns the main power transformer(s), R2-R8 apply through your existing Generator Owner registration, not Computational Load Owner registration.
  • Requirements on Transmission Owners and Distribution Providers, including R2-R8 at sites where they own the main power transformer(s), are outside the scope of this Module; requests from Transmission Planners, Planning Coordinators, Transmission Operators, Balancing Authorities, Reliability Coordinators, Regional Entities, and NERC are in scope only as you respond to them under R7.
  • We do not install DME, change device configuration, or apply Protection System settings; you or your contractors perform field work.
  • You inform us promptly when you receive a data request or discovers a recording failure, since the 15-day (R7) and 90-day (R8) clocks start on those dates.
  • You, as the registered entity, transmit each data package, CAP, and request; we prepare them ready to send.
  • You supply all required documentation and access to engineering, field services, and operations SMEs.
  • We will use engineering judgment and best practices to support compliance preparedness.
  • We do not assume liability for inaccurate or incorrect data or information you supply.

Run this module on one site.

Tell us the plant and the deadline. An engineer confirms the inputs, the schedule and what the Dashboard needs from you.