Solmar Insights
For US grid-scale solar projects, the compliance clock starts well before commissioning: projects rated at 20 MVA or higher and interconnecting at 60 kV or above should begin adherence to North American Electric Reliability Corporation (NERC) rules during the earliest design phases. Delaying compliance planning until project commissioning leaves owner-operators at risk of nonconformance and expensive change orders during the transition to commercial operation.
Key figures
20 MVA or greater project capacity triggers NERC requirements
Interconnection voltage threshold of 60 kV or above
Most solar projects are NERC low impact, with critical obligations starting at COD
Why NERC applies from the start
NERC registration and subsequent compliance obligations hinge on early design characteristics, such as plant nameplate capacity and point-of-interconnection voltage. If a facility is at or above the 20 MVA threshold and connects at 60 kV or more, developers should expect to be registered at least as a Generator Owner (GO) or Generator Operator (GOP) under NERC standards. This classification drives NERC’s Operations and Planning (O&P) and Critical Infrastructure Protection (CIP) frameworks, requiring a formal compliance program to be fully operational by the project’s commercial operation date (COD).
Most utility-scale solar projects in the US will be rated “low impact” under NERC standards, a designation that reduces, but does not eliminate, regulatory duties. Misinterpretation that low impact means “no compliance” has resulted in project delays and unexpected costs for developers caught unprepared at COD.
How design drives compliance and cost
Design teams set parameters that will define a project’s ongoing compliance with NERC, including equipment selection, network architecture, and the documentation of cyber system settings. Early-stage decisions also establish the physical and cyber security protocols required for BES (Bulk Electric System) assets. Failure to accurately classify and document these systems at the outset can lead to expensive late-stage redesigns, as compliance obligations become apparent only after construction or during last-minute audits before COD.
Key design elements, such as the location and classification of BES cyber assets and the configuration of protective relays, must align with NERC’s impact categorization. For example, an incorrectly located piece of equipment that qualifies as a medium-impact asset rather than low-impact might prompt physical security upgrades or new network segmentation requirements, drastically increasing both project scope and schedule risk. Developers must document design decisions thoroughly to ensure each setting and asset placement meets NERC standards, thereby avoiding major rework.
Installer challenges and process discipline
Installers and field crews rely on the design package delivered by the developer and are typically not responsible for NERC compliance decisions. However, when a field team observes deviations, such as receiving a relay with specifications inconsistent with approved settings, they must have a straightforward workflow for flagging issues before installation proceeds. The most common error in first-time NERC projects is failing to verify equipment conformity with design drawings, risking noncompliance if mismatches are ignored or addressed after the fact.
Industry best practice is to provide all field crews with targeted, NERC-focused training, especially around process discipline for equipment checks and deviation reporting. Whether development and installation teams are within the same firm or separate contractors, the project’s success depends on a transparent, operationally tight “handoff” in which all documentation, settings, and approvals are reviewed and re-confirmed before physical installation. Reducing friction in the communication loop is a central theme in driving compliance for both developers and contractors.
The compliance risk of inverter settings
Among all design parameters, the configuration of inverter-based resource (IBR) ride-through settings stands out for its outsized regulatory and operational risk. Ride-through requirements stipulate that solar inverters must remain online during brief grid voltage or frequency disturbances, rather than disconnecting in response to relatively benign irruptions. If ride-through thresholds are set too sensitively, a minor event on the transmission network can sweep a region’s solar production offline, triggering system-wide impacts and potentially subjecting asset owners to compliance enforcement actions.
The operational significance of these issues was highlighted during incidents such as the Canyon 2 Fire in California, when a transmission line disturbance tripped thousands of solar inverters and removed over 1,000 MW of generation at once. Overly conservative inverter protection can turn minor faults into major grid events, while exposing owners to both reliability and NERC compliance scrutiny. Developers must ensure detailed review of inverter model selection, protection settings, and integration with system-level controls in the project design documentation, checking each modification for compliance impact.
Market implications and best practices
The front-loading of NERC compliance into the design phase is now standard practice for utility-scale solar developers pursuing grid interconnection. While initial costs may rise as a result of early compliance planning and specialized engineering, downstream savings and schedule reliability outweigh the risk of costly change orders or non-compliance penalties triggered by last-minute discoveries. For institutional investors and asset managers, diligent attention to compliance design not only ensures on-time COD but also bolsters asset value by de-risking long-term operations.
Buyers, developers, and EPC contractors operating in the IDSO, PJM, and broader US markets are now expected to request, document, and verify NERC compliance packages from the outset of every qualifying project. As grid operators and FERC increasingly emphasize reliability standards for inverter-based resources, failure to align compliance and engineering early could result in asset underperformance and exclusion from interconnection queues. Formalizing internal, low-friction processes for deviation handling and cross-discipline signoff is recommended as a best practice by advisory firms specializing in regulatory compliance for solar and storage buildouts.
What this means for buyers
Power and interconnection in US RTO markets, especially projects 20 MVA or higher, are directly affected. COD triggers full NERC compliance and obliges readiness of operational and documentation controls. Buyers should now require project design packages to fully address NERC obligations before moving assets toward interconnection.
Reporting via the original publisher
