ERCOT Parameter Verification Reports (PVR): The Ultimate Guide for IBR Compliance

By Keentel Engineering

The rapid growth of inverter-based resources (IBRs) solar, wind, and battery energy storage systems has fundamentally changed how power systems behave during disturbances. While dynamic models have long been used to simulate system performance, recent events have made one thing clear:

• If your model doesn’t match your plant, your compliance doesn’t matter.

This is exactly why ERCOT introduced Parameter Verification Reports (PVRs) as part of its Model Quality initiative to ensure that simulation models accurately represent real-world plant behavior.

In this article, we break down everything you need to know about PVRs, including requirements, technical expectations, industry challenges, and how Keentel Engineering supports clients in achieving compliance.

What is a Parameter Verification Report (PVR)?

A Parameter Verification Report (PVR) is a formal engineering document that confirms:

• The dynamic model parameters (PSS®E / PSCAD) 
• Match the actual field-installed settings 
• Including controls and protection systems 
  
  

ERCOT’s objective is simple but critical:

• Ensure that grid simulations reflect real plant behavior during disturbances 
  

Why PVRs Matter: Lessons from Real Grid Events

One of the most important drivers behind PVR implementation was the Odessa disturbance event.

What happened?

• Multiple plants failed to ride through disturbances 
• But their models indicated they should have stayed online 

Root Cause:

• Mismatch between model parameters and field settings 

As highlighted in the presentation (Page 6):

• Many discrepancies were due to incorrect or outdated model settings 
• Verification processes were missing or incomplete 

This created a major reliability risk for ERCOT.

ERCOT PVR Requirements and Compliance Timeline

PVR requirements were implemented under:

• PGRR-085 (Effective March 1, 2021) 
• ERCOT Planning Guide Sections 5.5 and 6.2 

PVR Submission Requirements:

According to the presentation (Page 2):

• Within 30 days after Part 3 approval 
• Again 1–2 years after approval 
• Within 30 days after any setting change 
• Every 10 years thereafter 
• Mandatory for existing plants (as of March 2023
  

What Does a PVR Actually Verify?

A proper PVR goes far beyond a simple model review.

1. Control System Verification

• AVR (Automatic Voltage Regulator) gains 
• Plant controller parameters 
• Active/reactive power control settings 
• Governor droop

2. Protection System Verification

ERCOT explicitly requires validation of:

• Voltage protection 
• Frequency protection 
• V/Hz protection 

These are critical trip mechanisms that directly impact ride-through performance 

3. Dynamic Model Alignment

• PSS®E model parameters 
• PSCAD model (for IBRs) 
• Model consistency across platforms 
  

Why MOD-026/027 is NOT Enough (Especially for IBRs)

Many developers assume that NERC MOD studies are sufficient. That’s not true—especially for renewable plants.

According to the presentation (Page 4):

For Conventional Plants:

• MOD-026/027 can verify: 

• Exciter models 
• Governor models 

• But still require additional checks (PSS, protection, inertia) 

For IBR Plants:

MOD studies are limited and insufficient because they:

• Cannot verify protection settings 
• Cannot capture fast dynamic response 
• Cannot validate voltage ride-through behavior 

Best practice:

• OEM must confirm settings against PSCAD models (preferred) 
  

The Role of PSCAD in PVR for IBRs

For inverter-based resources, PSCAD plays a critical role in validation:

• Captures fast electromagnetic transients 
• Validates fault ride-through performance 
• Reflects actual inverter control behavior 

ERCOT may require:

• PSCAD Model Quality Testing (MQT) 
• Completion of Guideline Checksheet (OEM-driven) 
  

Common PVR Mistakes (and How to Avoid Them)

From Page 5 of the presentation, the most common issues include:

Missing Model Submission

• Reports submitted without PSS®E/PSCAD models 

Poor Parameter Traceability

• No mapping between report and model parameters 

No Field Verification Explanation

• Missing documentation on: 

• How settings were verified 
• How many units were checked
  
  

Ignoring Protection Relays

• Failure to model the most limiting relay conditions 
  
  

Model Mismatch Between Tools

• Updating PSS®E but not PSCAD 



These mistakes are one of the top reasons for ERCOT review delays.

Best Practices for a High-Quality PVR

At Keentel Engineering, we follow a structured approach:

Verify at the Source

• Confirm settings directly from: 

• SCADA 
• Relay settings 
• OEM documentation 

Align All Models

• Ensure: 

• PSS®E = PSCAD = Field 

Document Everything

• Include:

• Parameter tables with index references 
• Verification methodology 
• OEM confirmations 

Focus on Protection



• Always validate: 

• Trip thresholds 
• Ride-through limits 
• Relay coordination 
  

Challenges in Real Projects

1. OEM Unavailability

• Some OEMs refuse or delay support 
• ERCOT allows “best effort” documentation in such cases 

2. Multi-OEM Plants

• Solar + BESS + Wind = multiple control philosophies 
• May require multiple verification reports 

3. Legacy Plants

• Incomplete documentation 
  
• Outdated models 

How Keentel Engineering Supports PVR Compliance

We provide end-to-end PVR support including:

• Model-to-field parameter verification 
• Protection system validation 
• PSCAD & PSS®E alignment 
• OEM coordination 
• ERCOT-compliant reporting 

Our experience across ERCOT ensures:

• Faster approvals
  
• Reduced review comments
  
• Accurate compliance
  

Conclusion

Parameter Verification Reports are not just a regulatory checkbox—they are a critical reliability tool.

As ERCOT continues integrating more inverter-based resources, the importance of accurate modeling and validation will only increase.

A compliant model is not enough.

A verified model is what ensures grid reliability  .

Detailed FAQ – ERCOT Parameter Verification Reports (PVR)