A PRC-029-1 assessment in two days

A wind owner had a ride-through assessment in hand for the first plant in a fleet of fifteen. It had been built by hand in the usual way: model the plant, run the cases, transcribe the settings, write the report. The draft arrived about seven weeks after the model was done, the owner sent back a page of comments, and the final came four weeks after that.

The plant has more than 60 turbines, a substation full of relays and a hard October 2026 deadline. It was the template for the plants that followed, so anything wrong in it would be copied.

PRC-029-1 requires an inverter-based plant to stay connected and keep operating through defined voltage and frequency disturbances (R1 and R3), to deliver the right real and reactive current while voltage is disturbed (R2), and to document any equipment that physically cannot meet the requirement as a hardware limitation (R4).

The work was done under PRC-029-1. PRC-029-2 replaced it on October 1, 2026, and keeps the same compliance dates.

We rebuilt the assessment in the Dashboard in about two days, a Friday morning to a Sunday evening. We loaded the plant's own converter, turbine-controller and relay exports, the manufacturer's capability documents and the PSCAD model, and ran all 16 ride-through cases.

The Dashboard checked every protection stage on every unit against the must-ride-through envelope, answered every requirement of the standard, and generated the report in the owner's own template with the evidence attached. Then we audited our report line by line against the original one.

The comparison found six kinds of error in the original report.

• One turbine was running a different protection profile from the other sixty-plus. A report built on a single fleet table could not show it.
• On that turbine an under-frequency stage was armed inside the zone where the standard says the plant must stay connected. The original report marked that requirement as met.
• Several settings had been copied from the manufacturer's published curves rather than the plant's actual export.
• Two groups of settings had been blended into one table.
• The unit count did not match the settings file.
• One requirement had been mapped to an exemption it did not need.

The missed trip setting is a one-unit settings change, not an exemption. The owner's engineers were given access to the Dashboard with the report, and the same workflow runs the rest of the fleet.

Speed is the least of it. The errors in the original report are what hand transcription and a one-size fleet table produce. A platform that reads the settings file directly, keeps every unit's profile separate and checks every stage against the envelope cannot make them. When the data changes, the report regenerates in minutes instead of another round trip.