Contact information

Get in touch

Contact us today, and let’s work together to find solutions.

Invalid name
Invalid last name
Invalid email address
Incorrect email address
Submit

Thank you!

We will contact you shortly to provide further assistance and answer any questions you may have.

Oops! Something went wrong while submitting the form.
/

IEEE 2800 Compliance: Requirements, Adoption and How To Stay Audit-Ready

Adam Shaw
CMO, Integ
Date
October 26, 2026
Time
2026-10-26T07:38:28Z

Subscribe to our newsletter

The latest on NERC compliance, energy tech, and grid modernization news, weekly.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Ride-through obligations under Protection and Control standard PRC-029-1, which is based on IEEE 2800, begin on October 1, 2026 for BES IBR facilities. IEEE 2800 reaches inverter-based resource owners through two routes: the interconnection rules an ISO/RTO or transmission provider adopts, and the NERC standards built on IEEE 2800. IEEE 2800 compliance therefore runs as a plant-level program for the life of the asset.

What IEEE 2800 compliance means

IEEE 2800 compliance means a transmission- or sub-transmission-connected solar, wind, or storage plant, or isolated IBRs combined with the VSC-HVDC facility that connects them radially, meets IEEE Std 2800-2022 at the plant level. IEEE published the standard in April 2022. Nothing in it binds a plant until an Authority Governing Interconnection Requirements (AGIR), meaning a regulatory body, an ISO/RTO, or a transmission provider, adopts it.

Which plants IEEE 2800 applies to

The scope is large-scale, transmission- and sub-transmission-connected inverter-based resources. Within it, almost all requirements apply at the Point of Measurement, including ride-through. An “IEEE 2800 certified inverter” likely will not exist, because conformity is assessed at the plant level.

Core technical requirements

IEEE 2800 sets requirements in capability categories including:

  • Active power-frequency control
  • Reactive power-voltage control
  • Low short-circuit power
  • Power quality
  • Ride-through capability and performance

Additional requirements cover protection, modeling data, and measurement data for performance monitoring and validation. PRC-029-1 bases its ride-through zones on IEEE 2800-2022; the zones are covered in the IEEE 2800 ride-through requirements article.

IEEE 2800 vs IEEE 1547

IEEE 2800 is a transmission-level standard, while UL 1741 SA/SB is linked to distribution-level requirements. Misapplication of IEEE 1547 to transmission-connected IBRs is a key contributor to reliability risk, as a speaker citing NERC disturbance reports said at ESIG’s February 24, 2026 meeting.

How compliance is verified: IEEE 2800.2 and modeling

IEEE 2800.2 supplies the test and verification procedures that turn IEEE 2800 requirements into something testable. Adoption of IEEE 2800 is not contingent upon publication of IEEE P2800.2. Accurate IBR unit and plant modeling is a foundational aspect of conformity assessment. ISO-NE has required PSCAD models since 2016.

Who enforces it: AGIRs, FERC, and NERC

FERC Order No. 901 directed NERC to close IBR gaps; three standards resulted:

Standard What it requires Compliance start
PRC-028-1 Disturbance monitoring, recording, and reporting Effective April 1, 2025; phased to 2030
PRC-029-1 Frequency and voltage ride-through inside zones based on IEEE 2800-2022, stricter than PRC-024 October 1, 2026 (BES); January 1, 2027 (non-BES)
PRC-030-1 Identify, analyze, and mitigate unexpected changes in IBR power output October 1, 2026 (BES); January 1, 2027 (non-BES)

FERC approved PRC-029-1 in Order No. 909 on July 24, 2025. PRC-029 evaluates actual ride-through behavior from event data, where PRC-024 focused on protection settings.

NERC Project 2025-05 produced PRC-029-2.

Adoption status by grid operator

AGIRs adopt IEEE 2800 in full or in part, by general or clause-by-clause reference, with additional requirements. Current approaches:

Check your AGIR’s planning procedures and manuals. Consult its reliability rules for the clauses that apply.

Existing plants and what developers should do now

Adopting IEEE 2800-2022 for new IBRs with a transition period is relatively easy; for legacy IBRs it is challenging. For each plant, build an ongoing program that maps requirements to data, manages event reviews and mitigation, and keeps audit evidence current as standards change.

How to build an IEEE 2800 compliance program

Run these seven steps per plant:

  1. Identify requirements from the region and interconnection agreement; determine the plant’s BES or non-BES status.
  2. Map each requirement to the data that proves it.
  3. Connect the data sources: historians, SCADA, inverter feeds, and ISO connections.
  4. Set up event detection and review workflows.
  5. Track mitigation actions to completion.
  6. Maintain continuous audit-ready evidence.
  7. Track standard revisions and update processes.

Staying audit-ready with PowerCompliance

PRC-029-1 evaluates actual ride-through behavior from event data. PowerCompliance from Integ Enterprise Consulting supports IEEE 2800 and ride-through compliance with these capabilities:

  • Integrations: PowerCompliance integrates with existing historian systems, SCADA platforms, inverter data feeds, and ISO connections across 200+ operational data sources, and most connections go live in days.
  • Disturbance data: It continuously captures SER, fault recording, DDR, and real power performance data in line with NERC requirements and flags deviations and threshold breaches in real time.
  • Event workflows: On a disturbance or performance deviation, it routes analysis tasks to the right people, tracks mitigation to completion, and keeps a full evidence trail.
  • Living audit package: Its audit package updates automatically.
  • Standard changes: Workflows update when NERC standards change, with advance notification and pre-built templates.
  • Security: PowerCompliance offers SOC 2 Type II and NERC CIP alignment. It also provides automated audit trails.
  • Outcomes: PowerCompliance reduces evidence collection time by up to 85%, and clients save about 70% of manual compliance work. Audit prep drops from 3–4 months to 2–3 weeks.

FAQ

IEEE 2800 obligations depend on AGIR adoption and related NERC standards, including PRC-029-1. Applicability and conformity are assessed at the plant level, with IEEE 2800.2 providing test and verification procedures.

Is IEEE 2800 mandatory?

Not on its own; an AGIR must adopt it. FERC Order No. 901 led to PRC-029-1, which bases its mandatory ride-through zones on IEEE 2800-2022.

Does IEEE 2800 apply to existing plants?

It depends on the adopting authority, which sets any transition period. New-IBR adoption with a transition period is relatively easy; legacy adoption is challenging.

How does IEEE 2800 relate to NERC PRC-029?

PRC-029-1 enforces ride-through zones based on IEEE 2800-2022 from October 1, 2026 for BES IBRs and January 1, 2027 for non-BES. PRC-029-2 now carries the requirements forward.

How does it differ from IEEE 1547?

IEEE 2800 covers transmission-level plants; UL 1741 SA/SB is distribution-level. Applying IEEE 1547 to transmission-connected IBRs was named at ESIG’s February 2026 meeting as a key contributor to reliability risk.

What is IEEE 2800.2?

IEEE 2800.2 defines the test and verification procedures for IEEE 2800; adoption does not depend on its publication.

Can an inverter be IEEE 2800 certified?

Likely not. Almost all requirements, including ride-through, apply to the IBR plant, where conformity is assessed.

Next steps

Keep each plant’s requirements mapped to data, and keep evidence current as PRC-029-2 and regional adoptions change. Schedule a Demo to see PowerCompliance in action.

/
Latest from Integ

Related articles

No items found.
/
See it in Action