Inverter-Based Resource Ride-Through Commissioning Record

This template covers the preconditions, settings verification, disturbance monitoring setup, functional ride-through test results, and final sign-off for an inverter-based resource. It is built to document whether voltage and frequency ride-through behavior matches the approved design and applicable interconnection requirements. It also captures deficiencies and corrective actions so the commissioning package is complete. Use it as the record of what was checked, what was observed, and what remains open.

Use it during commissioning or re-commissioning before the inverter-based resource is accepted for normal operation. It is especially useful after control changes, firmware updates, protection setting revisions, or utility-required retesting. If the site has not yet completed its design review or test plan approval, this record should not be used as a substitute for those upstream documents. It documents execution, not engineering approval.

The inspection is typically completed by a commissioning inspector, test technician, or qualified field engineer, with review by the responsible engineer or owner representative. The person running the test should be able to verify settings, observe the response, and confirm the data capture setup. Final sign-off should come from someone accountable for the asset acceptance decision. If the utility or interconnection agreement requires witness testing, that role should also be identified in the record.

Yes, it is designed to support documentation of ride-through performance expectations associated with PRC-029 and related interconnection requirements. It also fits common utility commissioning practices for inverter-based resources, including verification of disturbance monitoring and event recording. Depending on the site, it may also support broader grid-code, interconnection, or owner specifications. It does not replace the actual standard, utility study, or approved test procedure.

Common mistakes include recording settings without confirming they match the approved design file, skipping time synchronization checks, and failing to archive the parameter export. Another frequent issue is documenting a successful test without noting the exact disturbance conditions or the observed inverter response. Teams also sometimes omit who owns each corrective action or leave the due date blank. Those gaps make the record hard to defend during review.

This record is usually completed at initial commissioning and again whenever ride-through settings, protection coordination, firmware, or control logic change. It may also be repeated after major maintenance, inverter replacement, or utility-directed retesting. The cadence should follow the project commissioning plan, interconnection agreement, and owner change-control process. For ongoing operations, this template can be adapted into a periodic verification record if the site requires it.

Yes, it can be adapted for solar PV, battery energy storage systems, hybrid plants, or other inverter-based resources. You can add manufacturer-specific parameter names, channel lists, test thresholds, and utility witness fields without changing the core structure. If the site uses multiple inverter models, it is helpful to note which units were sampled and which settings were applied fleet-wide. Keep the record focused on observable commissioning evidence rather than generic project notes.

Attach the approved settings sheet, parameter export, disturbance test report, event logs, calibration certificates, and any utility witness notes. If the site uses a separate commissioning checklist or test procedure, reference it in the inspection details section. Photos of the HMI, relay settings, or data acquisition screens can also help support the record. The goal is to make the final package traceable without forcing reviewers to hunt for evidence.