Modules · Event analysis · Module 053
PRC-029-2 Event Performance Analysis
Ride-through performance during real grid events analyzed against the standard from plant recordings.
About this module
What this module covers.
Automated ride-through analysis of relay and digital fault recorder (DFR) records under NERC PRC-029-2. Every COMTRADE record and SEL event report your plant's relays capture is read the moment it lands, laid over the PRC-029-2 voltage and frequency ride-through envelopes for your plant's technology (wind, solar or energy storage), and screened for a trip inside the region where the plant must stay connected. A flagged event opens a PRC-029-2 Event Review with the record attached, and the review ends in an issued PRC-029-2 Event Review Report.
At a glance
Module: 053
Kind: Event analysis
Governing body: NERC
Applies to: Operating plants
Typical time: Ten business days per flagged event
Dashboard capabilities
- Every relay and DFR record your plant captures is read on arrival: COMTRADE C37.111-1991, 1999 and 2013, binary and ASCII, single files or archives; SEL compressed event reports (.cev); and synchrophasor COMTRADE streams, by upload or by an SFTP drop we arrange with you.
- Each record is screened against the PRC-029-2 voltage ride-through envelope for your plant's technology (Requirement R1): each phase voltage as one-cycle root-mean-square (RMS) in per unit, with every excursion outside the continuous band judged by the ride-through its zone requires and by whether the record shows a trip (the relay's TRIP output, a breaker status, or the currents falling to zero).
- The record's frequency is screened against the PRC-029-2 frequency ride-through envelope (R3).
- Every record is checked for PRC-028-1 record quality (channels, sampling rate, pre-trigger and record length, time synchronization and COMTRADE version), so a recording that cannot prove an event is found before an auditor asks.
- You see each event on one page: voltage, current and frequency on one clock with the envelope zones drawn and each excursion shaded, two sentences per excursion, and what the screener could not know on its own (recorder position, per-unit base, clock zone).
- A flagged record opens a PRC-029-2 Event Review with its numbers filled in (R1 and its four exceptions, R2 performance during and after the excursion, R3 frequency and rate of change) and ends in a versioned PRC-029-2 Event Review Report (DOCX); every event across your plants shows on one fleet page with its verdict and review status.
Support services
What GridStrong does inside this module.
- Engineer review of every flagged event. For each record the screener marks Fail or Needs review, a GridStrong engineer completes the PRC-029-2 Event Review: confirms where the recorder sits and the per-unit base, names the exception that applies if one does, reads R2 performance from your power plant controller (PPC) and meter logs, and writes the conclusion. Delivered within ten business days of the record landing.
- Report issue. Each review's report issued as a numbered version with its revision history, ready to transmit to the Reliability Coordinator or to hold as evidence.
- Envelope and profile setup. Your plant's technology, nameplate, point of interconnection (POI) nominal voltage and recorder locations entered before the first record, so per unit and the envelope are right from the start.
- Intake setup. An SFTP drop for the plant's relays and DFRs into the Event Data folder, or the upload path for staff who place records by hand.
- Quarterly summary. The quarter's events, findings and open corrective actions in one note to the compliance lead.
Final deliverables
- A PRC-029-2 Event Review Report (DOCX) for every reviewed event, issued as a numbered version with its revision history.
- The event record, its screening, its charts and its review retained in GridStrong as the compliance record for the event.
- Corrective actions as tracked tasks on the plant's task list, each linked to the event and to the plant's PRC-029-2 compliance row.
- A quarterly event summary.
What we need from you
- Relay and DFR event records as COMTRADE (.cfg with its .dat and .hdr, .cff, or a relay's .evzip archive) or SEL compressed event reports (.cev), placed in the plant's Event Data / Events folder.
- The plant profile: technology (wind, solar or energy storage), nameplate, the POI nominal voltage that sets per unit, and where each recorder sits (point of interconnection, collector bus, feeder).
- For R2: the PPC or SCADA log of real and reactive power, voltage and setpoints across the event at one-second or better resolution, and inverter status or fault logs when available.
- The recorder's clock source and time zone when the record carries none (relay settings or a note).
- Any hardware limitation or exemption already documented under R4.
Assumptions and considerations
How the scope is bounded.
- The screener reads the recorder as the point of measurement; PRC-029-2 measures at the high side of the main power transformer. A feeder relay clearing its own fault looks like a ride-through failure until the review places the recorder, so recorder position is confirmed in every review.
- Per unit uses the profile's POI nominal voltage; without one, the pre-disturbance level, and the record says so.
- A record's clock zone comes from the relay's settings (a C37.118-synchronized relay stamps UTC) or from the plant's zone; the record says which.
- A record below 64 samples per cycle, shorter than the standard's minimum length, or ending inside an excursion is marked Needs review, not Pass or Fail.
- Frequency measured by a relay during a voltage collapse is an estimate; R3 conclusions rest on system frequency from a meter or phasor measurement unit (PMU) when the relay trace is in doubt.
- Exemptions for hardware limitations are filed through the plant's PRC-029-2 Workflow (its R4 Exemption page), which is a separate module.
- Intake is per plant, and runs for every record placed once the plant is set up.
Other modules
Every module runs on the same record.
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.