Protection relay testing is the last line of defence before a fault becomes a blackout — yet most power plant electrical teams still manage testing calendars through spreadsheets that cannot enforce compliance intervals, track evidence, or warn when a PRC-005 deadline is approaching. NERC PRC-005-6 mandates documented maintenance intervals for every component in the protection system — from numerical relays and trip coils to station batteries — with audit evidence retained for six years. A missed test window is not just an operations gap; it is a potential penalty event during a NERC audit and a liability exposure during any incident investigation. OxMaint's preventive maintenance scheduling engine pre-loads your PRC-005 maintenance basis and auto-generates work orders at compliant intervals, with every test result sealed as timestamped, audit-ready evidence the moment a technician closes the record in the field.
NERC PRC-005-6 Intervals
What the Standard Actually Requires
PRC-005-6 defines maximum allowable maintenance intervals by component and monitoring tier. Time-based maintenance and condition-based maintenance follow different schedules — your CMMS must know which basis applies to each asset.
Protective Relays
Time-Based
6 Years
Electromechanical and solid-state relays without monitoring. Includes functional testing of pickup, timing, and trip output verification.
Pickup / dropout verification
Timing accuracy test
Trip output functional test
Target / indicator check
Numerical Relays (Monitored)
Condition-Based
12 Years
Microprocessor-based relays with continuous self-monitoring. Extended interval permitted only with documented monitoring scheme in maintenance basis.
Self-test alarm verification
Settings audit vs. protection study
Communication channel test
Firmware version documentation
Station DC Supply
Time-Based
18 Months
Battery banks without per-cell monitoring. Visual inspection, connection resistance, float voltage check, and capacity test at 85% threshold.
Float voltage measurement
Cell voltage survey
Connection resistance test
Charger output verification
Control Circuitry
Time-Based
6 Years
Trip coils, auxiliary relays, lockout relays, and wiring associated with protection functions — the full trip path from relay output to breaker coil.
Trip coil continuity and resistance
Lockout relay functional test
Wiring insulation resistance
End-to-end trip path verification
Current / Voltage Transformers
Time-Based
12 Years
Metering-class and protection-class CTs and VTs providing inputs to protective relays. Ratio, polarity, and burden tests required.
Ratio and polarity verification
Burden and excitation curve test
Wiring continuity check
Insulation resistance test
Communications Systems
Time-Based
3 Months
Transfer trip, POTT/PUTT pilot channels, and direct transfer trip systems. Operational verification required at the shortest mandatory interval in PRC-005.
Channel operational verification
Signal level / noise floor check
Guard / trip frequency test
Keying test from both ends
Testing Checklist
Pre-Test, In-Test, and Post-Test — Every Work Order
Pre-Test
Outage window confirmed with operations
Protection test requires half or full outage — coordinate with system operator at minimum 48 hours prior
Prior test records reviewed
Compare previous pickup settings, timing results, and any as-found anomalies before conducting new test
Current protection settings sheet pulled
Verify test targets against approved relay coordination study — settings must match the signed protection study
Test equipment calibration current
Relay test set calibration certificate must be within 12-month validity — document test set serial number and certificate number in work order
Temporary blocking schemes in place
Trip outputs must be blocked or control room notified before injecting test current — document blocking switches opened
In-Test
As-found pickup and timing recorded
Record as-found values before any adjustments — as-found condition is the primary compliance data point under PRC-005
All protection functions tested per relay type
Distance, overcurrent, differential, ground fault — each element tested and timed. Do not skip elements not previously flagged as defective
Trip path end-to-end tested
Verify relay output energises trip coil correctly — test through the full circuit including lockout relay and auxiliary contacts
Anomalies documented before adjustment
Any as-found deviation from set point must be recorded and investigated — adjusting without documenting as-found is an audit finding
Settings verified as-left
After any adjustment, re-verify all elements to confirm as-left condition matches approved protection study values
Post-Test
All blocking removed, trip path restored
Confirm all test shorting plugs removed, blocking switches returned to normal, and trip path continuity verified before energising
Test data sheet signed and timestamped
Technician name, date, test set identification, and witness signature (if required) must be on record before work order is closed
Next test date calculated and scheduled
Calendar interval starts on completion date — next work order must be auto-generated and assigned to confirm the cycle is maintained
Evidence package filed to asset record
Test sheets, photos, and anomaly reports attached to asset history — NERC requires six-year retention from completion date
Operations notified — protection returned to service
Formal return-to-service notification logged with time — control room must confirm relay is active before outage is released
OxMaint for Protection Systems
Never Miss a PRC-005 Deadline Again
OxMaint calculates your next test date from the completion record, auto-generates the work order, and locks every test result into an audit-ready asset history. Your NERC evidence package is one click away — not buried in shared drives.
Annual Planning
How a Protection Test Calendar Should Be Structured
Effective relay test scheduling coordinates outage windows, crew availability, and test equipment allocation across all units. A compliant calendar is not a list of due dates — it is a sequenced plan.
| Component Type | PRC-005 Interval | Outage Required | Typical Duration | Crew | Evidence Required |
|---|---|---|---|---|---|
| Electromechanical / Static Relays | 6 Calendar Years | Half or Full Protection Outage | 4 – 8 hours per panel | 2 Protection Techs + Ops Coordination | Pickup / timing data, as-found / as-left comparison |
| Numerical Relays (Monitored) | 12 Calendar Years | Partial — Settings Audit | 2 – 4 hours per relay | 1 Protection Tech + Settings Engineer | Settings comparison report, firmware version log |
| Station Batteries (Unmonitored) | 18 Calendar Months | None — In-Service | 2 – 3 hours per bank | 1 Tech (PPE Class 2 minimum) | Cell voltage survey, float voltage, connection resistance |
| Pilot / Transfer Trip Channels | 3 Calendar Months | None — Operational Test | 30 – 60 min per channel | 1 Tech each end + Comm coordination | Keying test record, signal level log |
| CT / VT Inputs | 12 Calendar Years | Full Outage — De-energised | 4 – 6 hours per circuit | 2 Techs + LOTO supervision | Ratio, burden, insulation resistance values |
| Trip Coils and Control Wiring | 6 Calendar Years | Breaker Outage | 2 – 4 hours per breaker | 1 Tech + Ops supervision | Trip coil resistance, continuity, end-to-end trip test |
Common Audit Findings
Four Gaps That Trigger NERC Findings During Relay Audits
01
Interval calculated from wrong start date
PRC-005 specifies the calendar year starts on the first day of the calendar year after maintenance is completed — not the completion date itself. Plants using completion date as the interval start routinely exceed the maximum allowable interval on their next cycle without knowing it.
02
Maintenance basis not documented per component
Claiming the extended 12-year interval for a monitored numerical relay requires a written maintenance basis documenting the monitoring scheme, its alarm routing, and how it has been verified. Without this, the 6-year interval applies — and any relay tested at year 8 is non-compliant regardless of condition.
03
As-found data missing or adjusted before recording
NERC auditors specifically look for as-found test values before adjustments. A test record showing only as-left values with no as-found comparison gives auditors no basis to assess whether the relay was operating correctly at the time of test — triggering an audit finding even on a perfectly functioning relay.
04
Evidence retention not linked to asset record
Paper test sheets in filing cabinets — or PDFs in shared drives with no traceability to a specific relay asset — create a retrieval problem during audits. If you cannot produce the test record for relay XY-101 for the last six years within minutes of a request, the evidence might as well not exist.
Performance Metrics
KPIs That Tell You If Your Relay Testing Program Is Actually Working
100%
On-Time Completion Rate
Tests completed before maximum allowable interval expires. Anything below 100% is a potential NERC compliance event.
<2%
As-Found Anomaly Rate
Percentage of relays found outside settings tolerance on arrival. Above 5% suggests calibration drift or coordination study gaps.
6 Yrs
Evidence Coverage Window
Every relay in the program must have a linked, retrievable test record covering the past six years — the NERC standard retention window.
<4 Hrs
Outage Window Coordination Lead Time
Time from test completion to return-to-service notification logged in CMMS. Long gaps indicate process breakdowns, not technical ones.
FAQs
What Electrical Teams Ask About Relay Testing Compliance
What exactly does NERC PRC-005-6 require from a power plant relay testing program?
PRC-005-6 requires a documented maintenance program that defines each protection system component, the applicable testing interval, and the specific maintenance tasks to be performed. Maximum allowable intervals range from three months for communications channels to twelve calendar years for monitored numerical relays. Every completed test must generate evidence retained for six years. OxMaint pre-loads these intervals by component class and auto-generates compliant work orders so no interval is managed manually.
Can we use the extended 12-year interval for our numerical relays?
Only if you have a documented maintenance basis that describes the continuous monitoring scheme, the alarms it generates, how those alarms are routed and responded to, and how the monitoring system itself is verified. Without this written basis, NERC defaults the applicable interval to six years. Many plants claim the 12-year interval without adequate documentation — a common finding during field audits. Book a demo to see how OxMaint stores and links maintenance basis documents to each asset's interval rule.
How should relay test scheduling be coordinated with planned outage windows?
Protection test outages should be sequenced alongside related equipment outages whenever possible — testing a relay while the line is in service requires temporary blocking of one protection system, which eliminates redundancy and increases risk. Effective PM scheduling tools map protection test windows against generation unit outage calendars, flagging relay tests that fall due outside planned outage windows and triggering coordination at least 45–60 days in advance.
What happens if a relay is found outside tolerance during a PRC-005 test?
An as-found anomaly must be documented before correction, and the root cause must be investigated. If the deviation represents a protection system that was non-functional between the last test and this one, NERC may classify the period as a maintenance gap requiring a violation report. The as-found record is your evidence of when the issue was identified — which is why recording it before any adjustment is mandatory, not optional.
How does OxMaint handle multi-unit plants with hundreds of protection system components?
Each relay, battery bank, CT circuit, and communications channel is a unique asset with its own component type, interval rule, and evidence history. OxMaint's compliance dashboard surfaces every asset approaching its maximum allowable interval, sorted by days remaining, and allows test managers to batch-schedule by outage window, crew availability, and unit. Start a free account to see how multi-unit relay calendars look in practice.
Your Next NERC Audit Is a Calendar Event
Build a Relay Testing Calendar That Survives Scrutiny
OxMaint maps every protection system component to its PRC-005 interval, auto-generates work orders before deadlines, and stores six years of audit evidence per asset — ready the moment an auditor requests it.
