Know the triggers: A guide to grid code compliance for gas turbine power plant owners and operators

The compliance implications of modernization

Taking full advantage of modernization investments requires being clear-eyed about the grid code compliance implications. Indeed, McCloud says a growing number of plants are realizing too late that they had not anticipated grid code compliance complications.  

“The number of well-intentioned modernization programs that run into unexpected friction is increasing,” McCloud explains. “Not because the technology didn’t work, not because they’re bad products, but because the regulatory environment those upgrades landed in was different from what the team assumed going in.”

The consequences of not proactively addressing grid code compliance are substantial. Plants can face significant fines, delayed commercial operation, and curtailment penalties if compliance requirements are not submitted and accepted on time. 

Avoiding expensive and disruptive delays requires a robust knowledge of what can trigger compliance violations and reviews. The North American Electric Reliability Corporation (NERC) establishes and enforces grid code compliance requirements for power plants through a set of standards that apply to any synchronous machine over 25MVA that connects to the bulk power system. 

When a plant undergoes modernization, specific changes can trigger the requirement to revalidate compliance with NERC standards and submit updated documentation to the relevant regional reliability entity, like PJM or WECC. Missing or misunderstanding those triggers can result in meaningfully negative consequences that can last for years. Plants that discover they are out of compliance are obligated to self-report. 

There are three specific changes that trigger a revalidation requirement. Understanding each one is the first step in avoiding operational disruptions and fines. 
 

Trigger one: A greater than 10% change in output

NERC’s MOD-025-02 standard requires generators that connect to the bulk power system to verify and document their actual real and reactive power output capabilities. This is different from nameplate capacity and is important to grid operators so they can model how a generator can support reliability.  

If a generator’s output changes by 10% or more, the plant must provide its regional reliability entity with updated verification documentation. There is an important detail to this standard that, if overlooked, can lead plant operators to think they’re compliant when they are not. The 10% change in output is measured against the last submitted verification, not the last interconnection agreement.  

It’s also important for plant owners and operators to be clear that the 10% threshold can be passed just as easily with a series of small upgrades and improvements over time as it can with a single, large project. A modest output uprate one year followed by a combustion retrofit a few years later may be enough to surpass the 10% output change without planners recognizing it. “Plants generally know if they’re uprating by a huge amount that they need to address compliance,” McCloud states. “It’s when they’ve done a series of small changes over five to ten years that it gets missed.” 
 

Trigger two: Any change that affects dynamic behavior

Dynamic behavior is how a unit responds to real-time grid conditions, including frequency fluctuations, voltage changes, and system disturbances. NERC requires units behave in predictable and documented ways under various grid conditions. When a modification changes dynamic behavior, a plant’s compliance documentation must be updated to reflect how the generator will perform. 

What makes this trigger hard to recognize is that some modifications may seem unrelated to grid performance. Often, plant operators will perform what seems like routine maintenance or standard upgrades without realizing that it necessitates a revalidation. For example, replacing copper field windings is often viewed as maintenance, as are controls upgrades and software migrations.  

“Generator rewinds are a big one,” says McCloud. “It’s treated as a maintenance process, but when you replace the copper, it changes the resistances and reactances of the generator field. That has to be accounted for.”  
 

Trigger three: Replacement in kind (that isn’t)

Replacement in kind is when a component or control system is swapped out for a new one that is the functional equivalent of the original. Because the new component doesn’t change the performance or behavior of the generator, it doesn’t trigger a revalidation.  

Here’s the challenge: NERC and original equipment manufacturers (OEMs) don’t always define “identical” in the same way. Differing definitions introduce compliance risk. For example, a replacement part for a turbine manufactured decades ago may perform the same basic function as the part it replaced. However, it may differ significantly enough in its specifications that NERC does not consider it identical and requires a revalidation.  
 

Not an afterthought

These compliance triggers share common features: none of them are immediately obvious, and knowing and responding to them requires someone who is specifically looking for them. But most power plants do not have dedicated compliance staff. Instead, compliance awareness becomes the responsibility of project managers and engineers who are more focused on their physical assets, timelines, and budgets. Grid code compliance will inevitably remain unprioritized unless it is explicitly built into the planning process from the start.