NERC Obligations for Federally Funded Generation Assets

Foreword

Foreword

The energy industry has not yet absorbed the implications of one of the most consequential developments in the Infrastructure Investment and Jobs Act and the Inflation Reduction Act era. New generation assets are being financed at scale by entities that have never carried NERC compliance obligations. Federal grants are flowing to municipal utilities, electric cooperatives, tribal utilities, and developers that historically operated below NERC's bulk electric system thresholds or sat behind utility off-takers that absorbed the registration burden. Some of these new assets will be bulk electric system connected. Some will trigger registration as Generator Owners and Generator Operators. Some will carry CIP obligations that the recipient was not prepared to administer. The federal grant compliance discipline and the NERC compliance discipline operate in parallel, on the same assets, with different agencies and different consequences. Neither regime accommodates the other. Both apply.

This is the eighth reference in the Energy Compliance, Inc. Grant Funding Series and the fourth of the long form authority whitepapers. It is also the differentiator paper in the series. The audience is the people responsible for both halves of this intersection: the grants administrator at a public power utility planning a federally funded generation addition, the development VP at a community choice aggregator preparing to take title to bulk electric system connected solar, the chief compliance officer at an electric cooperative who has registered for the first time because the federally funded battery project pushed the entity over the threshold, the energy office director at a state agency whose grant flows to sub-recipients that may unknowingly trigger NERC obligations. Nobody else writes this content because the federal grant world and the NERC world have lived in separate professional communities. The Energy Compliance, Inc. work crosses both, which is why this reference exists.

Thirty years inside the energy regulatory and operational world taught me that the most expensive compliance failures occur at the seams between regimes. Each regime is internally coherent. Each has its own standards, its own examination processes, its own enforcement track record. At the seams, where two regimes both apply to the same facility, the failure pattern is consistent. The entity treats the more familiar regime carefully and treats the unfamiliar regime as someone else's problem. Federal grant recipients new to NERC treat the NERC obligations as something the consulting engineer will handle. NERC-registered entities new to federal grants treat the grant administration as something the grants team will figure out. Both views produce the same outcome at the seam. The federal auditor finds the NERC compliance gap. The NERC auditor finds the federal grant compliance gap. The entity pays at both seams.

This reference walks through the intersection. It assumes the reader is moderately familiar with one regime and less familiar with the other. The chapters address NERC registration triggers for federally funded assets,

the functional model and the obligations that attach to each function, the CIP applicability question, the PRC family that governs new generation interconnection, the FAC standards and the interconnection compliance lifecycle, EOP-011 cold weather preparedness, the dual compliance overlay structure, the documentation architecture that serves both regimes simultaneously, audit coordination between federal single audits and NERC audits, and practical implementation patterns drawn from the field.

This reference is not marketing material disguised as content. It is the bridge document between two regulatory communities that are now operating on the same assets and that need to learn to coordinate. Energy Compliance, Inc. exists at this intersection. The substance below is the substance of the engagements the firm conducts at the intersection.

Rob Smith, Founder, Energy Compliance, Inc.

Closing Note

About Energy Compliance, Inc.

About Energy Compliance, Inc.

When a Federally Funded Project Triggers NERC Registration

When a Federally Funded Project Triggers NERC Registration

The first conceptual move that this reference asks the reader to make is the recognition that federal grant funding does not exempt a project from NERC registration and that NERC registration does not pause for federal grant administration. The two regimes apply concurrently when a federally funded asset meets the registration triggers. The grants team that has built the post-award compliance backbone described in EC WP-905 has done excellent work on the federal side. That work does not satisfy NERC. The reliability compliance team that runs the entity's existing NERC program may not have visibility into the new asset because the new asset came in through the grants channel. The trigger event has to be identified at the moment it occurs, not after the asset is energized and the Regional Entity sends a compliance contact letter.

The Registration Concept NERC registration applies to entities that own or operate equipment that meets the Bulk Electric System definition under the NERC Glossary of Terms and the registration thresholds in the NERC Compliance Registry Criteria. The Bulk Electric System generally includes transmission elements operated at 100 kilovolts or above and certain real and reactive power resources connected at those voltages or above. Generators above specified thresholds connected to the BES are registered as Generator Owners and Generator Operators. The thresholds and inclusions have been refined through the BES definition revision and the BES Exception Process administered by NERC and FERC.

The registration is functional. An entity may register for multiple functions if it performs multiple roles. The functions include Generator Owner, Generator Operator, Transmission Owner, Transmission Operator, Reliability Coordinator, Balancing Authority, Distribution Provider, Planning Coordinator, Transmission Planner, Resource Planner, Transmission Service Provider, and Interchange Authority. Each function carries specific compliance obligations under the NERC Reliability Standards.

A new federally funded generation asset typically triggers Generator Owner registration if the entity holds title to the asset and Generator Operator registration if the entity operates the asset. The registration triggers when the asset is placed in commercial operation and meets the BES thresholds. Registration may be required earlier in some Regional Entity processes if the asset is anticipated to meet the thresholds.

The BES Threshold for Generation For generation, the BES generally includes individual generating units larger than 20 MVA directly connected to BES facilities, or generating plants or facilities consisting of multiple units with aggregate

nameplate capacity above 75 MVA. The BES definition includes exclusions and inclusions specific to certain configurations. Inverter-based resources, distributed energy resources aggregated through specific structures, and certain configurations behind the meter may or may not be BES depending on the specific facts.

Federal energy grants are funding generation assets across a range of sizes. Some are clearly below the BES thresholds. Others are clearly above. A meaningful population sits near the thresholds where the BES Exception Process or the specific facts of the interconnection determine whether the asset is BES. Recipients that have not evaluated the threshold question during application development discover the answer when the interconnection studies complete and the asset configuration is finalized.

When the Trigger Occurs in the Project Lifecycle The registration trigger occurs at commercial operation, but the obligations build during the construction and interconnection phases. The interconnection agreement with the host transmission provider or operator references the NERC obligations the new asset will carry. The generator interconnection studies establish the technical parameters that will govern the asset's operation. The protection settings, the voltage and frequency ride-through capabilities, and the data telemetry to the host operator are specified during the interconnection process.

The entity that intends to register must build its compliance program before the asset goes into service. Programs built after the asset is energized produce gaps that the Regional Entity treats as evidence of inadequate compliance posture. The grant timeline and the NERC compliance timeline must be coordinated from the project's beginning of construction.

Identifying the Trigger Early The recommended practice is for the grants team to flag any application that involves potential BES connected generation as requiring a NERC compliance evaluation during application development. The evaluation determines whether the project will trigger registration, what functional registrations will apply, what compliance obligations will attach, and what budget impact the obligations will carry. The evaluation feeds into the application's management plan and budget.

Projects that have not evaluated the NERC implications during application development frequently encounter the implications during interconnection studies. By that point, the engineering and procurement choices have been made. Some choices that affected the registration trigger or the compliance scope have been locked in. The compliance program now has to fit around the asset configuration rather than informing the configuration. Cost and complexity rise.

Recipients New to NERC Some federally funded projects are owned by entities that have no prior NERC registration. Municipal utilities that previously took service from a larger utility off-taker. Electric cooperatives whose generation portfolio sat below BES thresholds. Tribal utilities developing first-of-kind generation. Community choice aggregators acquiring generation assets directly. Each of these entity types may be encountering NERC registration for the first time.

The entity new to NERC carries a steeper learning curve than the entity that already maintains a NERC compliance program. The entity must establish a compliance organization, identify and qualify compliance personnel, build the documentation architecture, develop the operating procedures, train operators, and produce the evidence base that the Regional Entity will examine at the first compliance audit. The work is substantial. Done well, it produces a sustainable compliance program. Done poorly, it produces the first audit findings.

Recipients Already Registered Entities that already maintain NERC compliance programs may have an easier path on the registration question but a more complex path on the integration question. The new federally funded asset enters an existing portfolio of registered assets. The compliance program must absorb the new asset, update the entity's registration, integrate the asset into the existing procedures, and continue to satisfy the cross-asset obligations the entity already carries.

Integration friction surfaces in specific ways. The new asset may have different technology characteristics that strain procedures designed for the existing portfolio. The new asset's interconnection studies may produce protection settings that interact with adjacent assets. The new asset's data telemetry may need to be integrated into the entity's SCADA and energy management systems. The integration work is documented and the documentation supports the asset's inclusion in the entity's compliance posture.

Bridge to Chapter 2 The registration trigger depends on whether the asset is BES connected. The next chapter walks through the BES classification analysis and the specific facts that determine whether a federally funded asset is BES.

BPS Connectivity and BES Classification for Funded Assets

BPS Connectivity and BES Classification for Funded Assets

The Bulk Electric System definition determines whether a generation asset is subject to NERC Reliability Standards. The definition has been refined through the NERC standards process and through FERC orders and currently appears in the NERC Glossary of Terms. The classification is not always obvious. Federal grant recipients building new generation must analyze the BES question with the care the definition requires. The analysis informs the registration decision, the standards applicability, and the compliance program scope. Recipients that have not analyzed BES classification carefully may miss the trigger or may treat as BES an asset that does not actually meet the definition.

The BES Definition Core Elements The BES definition at its core includes transmission elements operated at 100 kilovolts or higher, including transformers with at least one terminal operated at 100 kilovolts or higher, and real and reactive power resources connected at 100 kilovolts or higher. Real power resources include generating units, generating plants, and dispatchable demand resources subject to specified thresholds. The definition includes named inclusions for certain configurations and named exclusions for others.

For generation, the definition specifies that individual generating units larger than 20 MVA directly connected to BES facilities are included. Generating plants or facilities consisting of multiple units that are physically connected at a common bus and that have aggregate nameplate capacity above 75 MVA are also included if they have aggregate impact on the BES. The thresholds and configurations involve technical considerations that require careful analysis for specific projects.

Inverter-Based Resources Solar generation, storage, and wind generation typically interconnect through inverters. The NERC standards have evolved to address inverter-based resources specifically, including ride-through requirements, model accuracy expectations, and coordination with system protection. The standards have been updated through PRC-024-3 and through NERC alerts and recommendations related to disturbances involving inverter-based resources.

Inverter-based resources connected at BES voltages are BES facilities even though the underlying technology differs from traditional synchronous generation. The compliance obligations may differ in specifics but the registration trigger applies. The entity that has built or acquired inverter-based generation at BES voltages registers if the asset meets the thresholds.

Aggregation and Common Bus Some federally funded projects involve multiple generating units aggregated at a common collection point. The aggregation question affects BES classification. Individual units below the 20 MVA threshold may aggregate above the 75 MVA plant threshold if they share a common bus with aggregate BES impact. The analysis requires evaluation of the collection system topology, the point of interconnection, and the operational coordination.

Aggregation also affects how the asset interfaces with the host transmission system. A 100 MVA aggregated solar project with multiple inverter clusters and a common collection substation operates differently than a single 100 MVA synchronous unit. The interconnection studies, the protection settings, and the operational procedures all reflect the aggregated configuration. The NERC compliance program tracks the aggregated facility as a single BES facility for most purposes.

Behind-the-Meter Configurations Some federally funded projects include behind-the-meter generation that does not directly inject into the BES at BES voltages. Such projects may still affect BES operations through net power flows, but the asset itself may not be classified as a BES facility. The classification depends on the specific configuration and the operational dispatchability.

Behind-the-meter projects that are aggregated through formal Aggregated Distributed Energy Resource constructs may have different classifications under emerging NERC frameworks. The ADER concept is being developed through ongoing NERC and FERC processes and the classification of ADER configurations under the BES definition is one of the developing areas.

Storage Facilities Storage facilities pose specific BES classification questions. Stand-alone storage facilities connected at BES voltages above the relevant thresholds are BES facilities. The thresholds may apply differently to storage given its dual role as both load and generation. The NERC standards have evolved to address storage specifically through revisions to applicable standards.

Storage paired with generation at a common point of interconnection may be analyzed jointly with the paired generation. The aggregated nameplate capacity calculation reflects both the generation and the storage in some configurations. The compliance program addresses storage specifically because storage operations introduce considerations that traditional generation does not.

The BES Exception Process NERC operates a BES Exception Process under which an entity may request that a facility otherwise meeting the BES definition be excluded, or that a facility otherwise excluded be included. The process is administered

by NERC and the relevant Regional Entity. The process requires factual support, technical analysis, and stakeholder review.

The BES Exception Process is not a routine path. Most BES classifications resolve through application of the definition without an exception request. The process exists for facts at the edges of the definition where the standard application produces an outcome inconsistent with the underlying reliability considerations. Entities considering an exception request should engage with the Regional Entity early to understand the process and the documentation requirements.

Documenting the Classification Decision The BES classification analysis is documented in writing. The documentation identifies the asset, the operating voltage, the nameplate capacity, the aggregation configuration if applicable, the technology type, and the specific BES definition elements applied. The documentation references the supporting interconnection studies, the engineering design documents, and any communications with NERC, the Regional Entity, or the host transmission provider regarding the classification.

The documentation supports the registration decision and is preserved as part of the compliance program. The first compliance audit may examine the classification analysis. Audits that find the classification was reached without supporting analysis may identify the classification decision itself as a finding.

Bridge to Chapter 3 Once the asset is classified as BES, the registration pathway and the functional model determine the specific obligations. The next chapter walks through the functional model and the registration pathways for federally funded generation.

Registration Pathways and the Functional Model (GO, GOP, TO, TOP, RC, BA, DP)

Registration Pathways and the Functional Model (GO, GOP, TO, TOP, RC, BA, DP)

) The NERC functional model categorizes registered entities by the functions they perform. The model includes Generator Owner, Generator Operator, Transmission Owner, Transmission Operator, Reliability Coordinator, Balancing Authority, Distribution Provider, Planning Coordinator, Transmission Planner, Resource Planner, Transmission Service Provider, and Interchange Authority. Each function carries specific obligations under the NERC Reliability Standards. A federally funded generation asset typically triggers Generator Owner and Generator Operator functions for the entity that owns and operates the asset. Larger projects may trigger additional functions.

Generator Owner The Generator Owner function attaches to the entity that holds title to the generating asset. Generator Owner obligations include design, maintenance, and configuration responsibilities for the asset. Standards applicable to Generator Owners typically include the PRC family for protection systems and ride-through, the FAC family for facility ratings and interconnection requirements, certain TPL and MOD standards for transmission planning support, and parts of the CIP family for cyber security.

Federal grant recipients that hold title to federally funded BES-connected generation register as Generator Owners. The registration captures the asset's identification, the responsible entity, and the applicable standards. The Regional Entity uses the registration to drive compliance examinations across the standards.

Generator Operator The Generator Operator function attaches to the entity that operates the generating asset. Generator Operator obligations include operational responsibilities such as outage coordination, response to system events, communication with the host Reliability Coordinator and Balancing Authority, and compliance with operational standards including the EOP, COM, IRO, and TOP families.

In many federally funded projects, the recipient is both the Generator Owner and the Generator Operator. In some configurations, particularly where a third-party operator runs the asset under a service agreement, the functions may separate. The Generator Owner remains responsible for the asset's design and configuration even when the Generator Operator function is delegated. The contractual structure between the Owner and the Operator allocates responsibilities but does not change the regulatory obligation each function carries.

Transmission Owner and Transmission Operator Most federally funded generation does not trigger Transmission Owner or Transmission Operator registration because the entity does not own or operate transmission facilities. However, certain configurations include collection facilities that may or may not be classified as transmission. Substations and collector lines built as part of the generation project may be transmission elements that trigger Transmission Owner registration if they are part of the BES.

The classification of project-internal facilities as transmission or as generator-step-up facilities affects the registration question. Facilities classified as part of the generating facility rather than as transmission are typically covered under the Generator Owner registration. Facilities classified as transmission may require additional Transmission Owner registration.

Recipients building generation that includes substantial new substation or interconnection facilities should analyze the classification of those facilities specifically. The analysis informs the registration scope and the standards applicability.

Reliability Coordinator and Balancing Authority Federally funded generation projects do not typically trigger Reliability Coordinator or Balancing Authority registration. These functions are performed by the entities that coordinate operations across larger geographic footprints and the federally funded asset operates within those existing footprints. The asset's Generator Operator coordinates with the host Reliability Coordinator and Balancing Authority through the standard mechanisms.

Some entities developing federally funded generation may already perform Reliability Coordinator or Balancing Authority functions in their broader operations. For such entities, the new asset is incorporated into the existing footprint and the existing compliance program absorbs the new asset.

Distribution Provider The Distribution Provider function attaches to entities that own or operate distribution facilities included in NERC's defined scope. Most distribution facilities are below the BES threshold and do not trigger Distribution Provider registration. Certain larger distribution configurations or distribution facilities that interact with the BES may trigger registration. The federally funded project that includes distribution interconnection investments should analyze the registration implications carefully.

Planning and Resource Coordination Functions The Planning Coordinator, Transmission Planner, and Resource Planner functions attach to entities that perform planning functions in their broader operations. New generation triggers planning support obligations that the entity coordinates with the host Planning Coordinator. The federally funded asset typically does not

itself trigger Planning Coordinator registration but the asset's data and configuration must be provided to the relevant Planning Coordinator under MOD standards.

Registration Mechanics Registration is initiated through the NERC Compliance Registry. The entity submits registration information including the functions to be registered, the assets to be included, the operating contact information, and the compliance program contact information. The Regional Entity reviews the registration and confirms the scope. The entity is added to the registry and is subject to the applicable compliance obligations.

Registration is not retroactive but the obligations attach from the date of operation as a registered function. An entity that operates BES-connected generation without registering may face enforcement for unregistered operation in addition to the underlying compliance obligations. The registration is initiated before commercial operation when possible.

Coordination With the Host Transmission Provider The federally funded generation asset interconnects with a host transmission provider that itself is a registered Transmission Owner and Transmission Operator. The host's interconnection process produces the technical parameters that govern the asset's operation. The host's NERC compliance program addresses the host's facilities. The new asset's compliance program addresses the asset's facilities. The two programs interface at the point of interconnection.

The interface includes data exchanges, protection coordination, voltage and frequency support, outage coordination, and incident response. Each interface element is documented in the interconnection agreement and in the operational procedures both entities maintain. Misalignment at the interface produces compliance gaps for one or both entities.

Bridge to Chapter 4 The registration establishes which standards apply. The CIP family is one of the most consequential standard categories for new BES-connected assets, particularly for assets with cyber components that meet the CIP applicability thresholds. The next chapter walks through CIP applicability for federally funded assets.

CIP Applicability for Funded BPS Assets

CIP Applicability for Funded BPS Assets

The Critical Infrastructure Protection family of NERC standards governs cyber security for BES Cyber Systems associated with registered functions. The CIP family includes CIP-002 through CIP-014 in the current version sequence, with each standard addressing specific aspects of cyber security including categorization, security management controls, personnel and training, electronic security perimeters, physical security of BES cyber systems, system security management, incident reporting and response planning, recovery plans, configuration change management, information protection, supply chain risk management, communications between control centers, and physical security of certain transmission stations and substations. Federally funded generation assets that meet the CIP applicability thresholds carry significant cyber security obligations that must be built into the compliance program from the asset's design phase.

The CIP-002 Categorization CIP-002 governs the categorization of BES Cyber Systems as High, Medium, or Low Impact. The categorization drives the applicability of subsequent CIP standards. Different impact categorizations carry different obligations. The categorization analysis evaluates the BES Cyber System's role in operation of the BES, the geographic footprint of the systems affected, and specific characteristics enumerated in CIP-002.

Most generation assets are categorized as Low Impact under CIP-002, with limited exceptions for assets that meet the Medium or High Impact criteria. The applicability of CIP standards to Low Impact assets is more limited than the applicability to Medium or High Impact assets but is not trivial. CIP-003 requires Low Impact entities to implement specific security policies and controls. Other CIP standards may apply depending on specific characteristics.

Federally funded projects perform the CIP-002 categorization during the design phase and document the categorization. The documentation supports the compliance program scope and identifies the applicable standards.

Cyber System Identification The CIP-002 analysis requires identification of BES Cyber Systems associated with the registered function. BES Cyber Systems include programmable electronic devices that perform reliability-related functions. The identification covers SCADA components, energy management system components, protective relays with programmable interfaces, communication systems supporting reliability functions, and similar systems.

For new generation, the identification occurs during the engineering design phase. The procurement of generation control systems, plant communication systems, and protective relaying produces the underlying inventory. The compliance program captures the inventory and applies the CIP-002 categorization.

Low Impact Obligations Low Impact entities must comply with the requirements of CIP-003. The requirements include implementing cyber security policies covering specific topics, identifying Low Impact BES Cyber Systems, implementing electronic access controls, implementing physical security controls, implementing cyber security awareness, implementing cyber security incident response, and implementing certain TCAs (Transient Cyber Assets) and Removable Media management controls.

The Low Impact obligations are substantive but the implementation depth is lower than for higher impact categorizations. Federally funded generation typically operates at the Low Impact level. The compliance program documents the policies, the controls, the training, and the incident response procedures. The Regional Entity examines compliance through audits and spot checks.

Medium and High Impact Considerations Some federally funded projects may meet Medium or High Impact criteria. Battery storage facilities with significant capacity, large generation aggregations, and projects with control system architectures that aggregate across multiple sites may approach Medium Impact thresholds. The analysis is specific to the project's configuration.

Medium Impact obligations are substantially more extensive than Low Impact obligations. The compliance program for Medium Impact assets implements electronic security perimeters, formal access management, baseline configurations, change management, vulnerability assessments, and specific security event monitoring. The implementation requires meaningful technical and process investments.

Federally funded projects that may meet Medium Impact criteria should engage with the categorization question early in the project design. Design choices may affect whether the categorization remains Low or moves to Medium. The cost and complexity differential between the categorizations is large enough to warrant the analysis.

Supply Chain Risk Management CIP-013 establishes supply chain risk management obligations for entities with applicable BES Cyber Systems. The standard requires the entity to develop and implement a supply chain cyber security risk management plan, to apply specified procurement and supplier security requirements, and to verify supplier conformance with the requirements.

Federal grant recipients building new generation engage with suppliers that are themselves subject to the supply chain rule. The entity's compliance program coordinates with the suppliers to obtain the required information and to verify the procurement controls. The supply chain documentation is captured as part of the procurement files.

Cyber Security Incident Response CIP-008 requires entities with applicable BES Cyber Systems to develop and implement cyber security incident response plans. The plans cover detection, response, and recovery. Incidents are reported to NERC's Electricity Information Sharing and Analysis Center within specified timeframes.

The incident response plan integrates with the entity's broader cyber security posture. Federally funded generation operates within the entity's overall incident response framework, with the new asset's specific systems included in the scope. The plan is exercised through tabletop drills and periodic reviews.

Information Protection CIP-011 governs the protection of BES Cyber System Information. The standard requires entities to identify BCSI, to implement controls for protecting BCSI in storage and transit, and to handle BCSI through specified disposal procedures.

For federally funded projects, BCSI includes the project's engineering drawings, the protection settings, the SCADA configurations, the plant control system documentation, and similar materials. The information protection program captures the BCSI inventory and applies the required controls. Federal grant administrative records that include BCSI components may require coordinated handling to satisfy both the federal records management requirements and the CIP information protection requirements.

Personnel and Training CIP-004 governs personnel security, training, access management, and access revocation. Personnel with cyber or physical access to applicable BES Cyber Systems are subject to personnel risk assessments, training requirements, and access management controls.

Federally funded projects identify the personnel with applicable access during the project's transition to operations. The training program covers the cyber security responsibilities the personnel will carry. The access management program controls the cyber and physical access from initial provisioning through eventual termination or transfer.

Bridge to Chapter 5 CIP governs cyber security. The PRC family of standards governs protection systems and ride-through, which are the primary reliability protection mechanisms that new generation interacts with at the BES interface. The next chapter walks through the PRC family as it applies to federally funded generation.

The PRC Family for Funded Generation (PRC-024, PRC-019, PRC-005)

The PRC Family for Funded Generation (PRC-024, PRC-019, PRC-005)

) The Protection and Control family of standards governs the protection systems that detect and clear faults on the BES and the ride-through capabilities of generating resources during system disturbances. The family includes more than two dozen standards. For new generation, the most operationally consequential standards are PRC-024 for generator voltage and frequency ride-through, PRC-019 for coordination of generating unit voltage controls and protection, and PRC-005 for protection system maintenance and testing. Federally funded generation assets must satisfy these standards from commercial operation forward. The technical work that establishes compliance occurs during the design and commissioning phases.

PRC-024 Voltage and Frequency Ride-Through PRC-024 establishes voltage and frequency ride-through requirements for generating units. The requirements specify minimum durations the unit must remain connected during specified voltage and frequency excursions. The requirements have been revised over time and the current version of the standard reflects the latest understanding of system needs and inverter-based resource considerations.

For inverter-based generation, PRC-024 compliance depends on the inverter capabilities and the protection settings configured. The inverter must be capable of riding through the specified excursions, and the protection settings must not trip the inverter prematurely. The commissioning process verifies the inverter capabilities and confirms the protection settings against the standard.

For synchronous generation, PRC-024 compliance depends on the generator's mechanical and electrical capabilities and the protection settings. The protection coordination study confirms that the protection will not trip the unit during ride-through events that the unit can mechanically and electrically survive.

Documentation of PRC-024 compliance includes the engineering analysis demonstrating the unit's ride through capability, the protection settings applied, the commissioning test results, and the periodic reviews that confirm continued compliance. Federal grant recipients building new generation receive this documentation from the engineering and commissioning contractors and preserve it in the NERC compliance program file.

PRC-019 Coordination of Voltage Controls and Protection PRC-019 requires entities to coordinate generating unit voltage regulating controls, limit functions, equipment capabilities, and protection systems. The coordination ensures that voltage regulation does not

push the unit into protective relay operation under normal operating conditions, and that protection settings do not interfere with the voltage regulation needed for system support.

The coordination analysis is performed during commissioning and verified periodically. The analysis evaluates the interaction among the voltage regulator settings, the field forcing limits, the over-excitation and under-excitation limiters, the volts-per-hertz protection, the loss of excitation protection, and the other applicable protection elements. The result is a coordinated set of settings that supports voltage regulation while maintaining protective coverage.

For inverter-based resources, the coordination involves the inverter's voltage and reactive power controls, the inverter protection settings, and any plant-level coordination through reactive power management systems. The analysis differs in detail from synchronous coordination but the principle is the same. Federally funded inverter-based projects perform the coordination analysis during commissioning and document the result.

PRC-005 Protection System Maintenance and Testing PRC-005 establishes protection system maintenance and testing requirements. The standard applies to applicable protection systems and requires entities to implement a maintenance and testing program that covers the protection components, the maintenance intervals, the testing criteria, and the documentation of testing.

The standard categorizes protection components by maintenance interval. Some components require testing on relatively long intervals. Others require more frequent testing. The standard reflects the reliability importance of the components and the testing necessary to maintain confidence in their availability.

For new federally funded generation, the protection system maintenance program is established before commercial operation. The maintenance program identifies the applicable components, the maintenance intervals, the testing procedures, the responsible personnel, and the documentation requirements. The first round of testing occurs at the appropriate intervals after commercial operation, with results documented and preserved.

The maintenance program operates continuously across the asset's life. Federal grant funding may support the initial protection system installation but the ongoing maintenance is the recipient's obligation under PRC-005. The compliance program tracks maintenance schedules and ensures testing is conducted on time.

Coordinating PRC With Federal Grant Considerations The PRC family obligations operate independently of the federal grant terms. The federal grant did not relax the PRC standards. The PRC standards do not adjust for the federal grant. The recipient operates under both regimes concurrently.

Coordination points exist. Federal grant funds supporting the protection system installation may have specific cost reasonableness requirements under the cost principles. The procurement of protection equipment is subject to the federal procurement framework if the procurement crosses the relevant thresholds. The documentation of the protection system installation supports both the federal grant compliance and the NERC compliance.

The documentation architecture described in EC-WP-905 incorporates the NERC PRC documentation. The protection settings files, the coordination analysis, the commissioning records, and the maintenance procedures all become part of the integrated compliance file that serves both regimes.

Inverter-Based Resource Specific Considerations Inverter-based generation has been the subject of significant NERC focus following several system disturbances that involved unexpected inverter behavior. NERC has issued alerts, recommendations, and standard revisions addressing inverter-based resource issues. The standards continue to evolve in this area.

Federally funded inverter-based projects build the compliance program with attention to the current standards and the published NERC guidance on inverter-based resource performance. The procurement of inverters specifies the required ride-through capabilities, model accuracy, and other relevant characteristics. The commissioning process verifies the capabilities. The compliance program documents the verification and the ongoing performance.

Bridge to Chapter 6 PRC governs protection and ride-through. FAC standards govern facility ratings and interconnection requirements. The next chapter walks through the FAC family as it applies to federally funded generation interconnections.

FAC Standards and Interconnection Compliance

FAC Standards and Interconnection Compliance

The Facilities family of NERC standards governs facility ratings, interconnection requirements, and certain reliability assessments. The standards include FAC-001 for facility connection requirements, FAC-002 for facility interconnection studies, FAC-003 for transmission vegetation management, FAC-008 for facility ratings, FAC-010 and FAC-011 for system operating limit methodology, and FAC-014 for the establishment of system operating limits. For new generation, the FAC standards establish the technical interface with the host transmission system and the data and analysis that supports operations across the interface.

FAC-001 Facility Connection Requirements FAC-001 requires transmission owners to maintain and apply documented facility connection requirements for the connection of new generating facilities, new transmission facilities, and modifications to existing facilities. The transmission owner publishes the requirements and applies them to interconnection requests. The requirements address technical compatibility, planned operations, reliability impacts, and the interconnection process.

For federally funded generation, the host transmission owner's connection requirements drive the interconnection design and operation. The recipient reviews the requirements, designs the asset to satisfy them, and documents the satisfaction. The interconnection agreement memorializes the requirements as they apply to the specific interconnection.

FAC-002 Facility Interconnection Studies FAC-002 requires interconnection studies before new facilities are connected to the BES. The studies evaluate steady-state, short-circuit, dynamics, and transient stability impacts of the new facility on the host system. The studies identify any network upgrades needed and the operational considerations that will apply post-interconnection.

The interconnection studies are typically performed by the host transmission provider or its engineering consultants, with input from the generation developer. The studies have several stages including feasibility, system impact, and facilities studies under FERC pro forma processes for new generation. The studies inform the interconnection agreement, the facility ratings, the protection settings, and the operating procedures.

Federal grant recipients participate in the interconnection studies through providing the data the studies require, reviewing the study results, and addressing any issues identified. The study results inform the

project's technical configuration and the budget. Network upgrades identified in the studies may carry significant cost implications that affect the project's overall economics.

FAC-008 Facility Ratings FAC-008 establishes the methodology for facility ratings and the documentation of the ratings. Facility ratings define the maximum continuous and emergency loading capabilities for transmission facilities and generating units. Accurate ratings are essential because system operations are conducted within the ratings, and operations outside the ratings risk equipment damage and cascading events.

For new generation, the entity establishes facility ratings consistent with FAC-008. Generator ratings reflect the unit's actual capability, the manufacturer's nameplate, the ambient conditions, and any operational limitations. The ratings are documented and provided to the host transmission operator for use in system operations.

The ratings are updated as conditions change. Significant ambient temperature changes, equipment modifications, or operational limitations may produce changes in the applicable ratings. The compliance program tracks the conditions that affect ratings and updates the ratings when warranted.

FAC-003 Vegetation Management FAC-003 governs transmission vegetation management for applicable transmission lines. Generation projects typically do not own transmission lines directly subject to FAC-003. However, projects that include collector lines or generator interconnection tie lines may have vegetation management responsibilities depending on the classification of the lines.

Federal grant recipients with new tie lines or collector facilities evaluate FAC-003 applicability during project design. Where applicable, the vegetation management program is established before energization. The program covers inspection cycles, vegetation maintenance criteria, documentation requirements, and the coordination with landowners or right-of-way holders.

FAC-010 and FAC-011 SOL Methodology FAC-010 and FAC-011 establish methodology requirements for system operating limits in the planning and operations time frames. SOLs are limits on the operating parameters of the BES that, if exceeded, could result in inability to maintain reliable operation. The methodology requirements ensure that SOLs are established through rigorous, consistent analysis.

Federally funded generation contributes to the SOL framework through the unit's impact on the surrounding system. The unit's capability data, dispatch characteristics, and operational limitations feed into the host's

SOL determinations. The unit's operation respects the SOLs established by the host Reliability Coordinator and Transmission Operator.

Recipients typically do not perform SOL analyses themselves unless they have transmission or planning functions. However, the data they provide and the operational coordination they conduct support the SOL framework managed by the host.

Interconnection Agreement Provisions The interconnection agreement between the recipient and the host transmission provider memorializes the NERC compliance interface. The agreement typically addresses facility ratings, protection settings, voltage and frequency support obligations, data telemetry, outage coordination, system event response, and dispute resolution.

The recipient reviews the interconnection agreement with attention to the NERC compliance obligations it creates. The obligations flow into the compliance program. The agreement is a primary reference for the compliance program throughout the asset's life.

Network Upgrades and Cost Allocation Interconnection studies may identify network upgrades needed to accommodate the new generation. The upgrades may be on the host's facilities and funded through interconnection customer payments under the FERC pro forma framework. The cost of network upgrades can be substantial and may affect the project's federal grant budget.

Federal grant applications anticipating major interconnection upgrades should reflect the upgrade costs in the budget. The interconnection cost allocation under the FERC pro forma framework determines how much of the upgrade cost the recipient pays directly versus how much may be reimbursed over time through transmission service credits or other mechanisms. The budget and project schedule reflect the anticipated cost allocation.

Bridge to Chapter 7 FAC governs the interconnection technical interface. EOP standards govern emergency operations and preparedness, including cold weather preparedness for new generation under EOP-011. The next chapter walks through the EOP-011 obligations that have become increasingly significant for new generation.

EOP-011 Cold Weather Preparedness for New Generation

EOP-011 Cold Weather Preparedness for New Generation

The Emergency Operations Plan family of NERC standards includes EOP-011, which addresses emergency operations and, in its recent revisions, cold weather preparedness requirements for generating units. The cold weather requirements developed in response to system events including the February 2021 cold weather event in Texas and similar events in other regions. The standard now requires generating units to take specific preparedness actions and to meet specified performance criteria during cold weather events. Federally funded generation entering service in the post-revision era must build cold weather preparedness into the design, operations, and compliance program from the project's beginning.

The Standard's Scope EOP-011 in its current version applies to applicable generating units and addresses cold weather preparedness, declaration of operating emergencies, and other emergency operations. The cold weather preparedness requirements specify that applicable units must implement winterization measures, develop cold weather preparedness plans, conduct training, perform inspections, and meet performance criteria during cold weather events.

The applicability of EOP-011 to specific units depends on the unit's characteristics, the geographic location, and the specific provisions of the standard. The standard has been revised through multiple iterations and the current version reflects lessons learned from recent system events. Federally funded generation evaluates EOP-011 applicability during project design and incorporates compliance into the project execution.

Cold Weather Preparedness Plans The cold weather preparedness plan documents the unit's preparations for cold weather operation. The plan addresses the freeze protection of critical components, the operations protocols during cold weather, the staffing considerations, the fuel security considerations, the maintenance considerations, and the coordination with the host operators.

For federally funded projects, the plan is developed during the design and commissioning phase. The engineering design specifies the freeze protection components and the winterization approach. The commissioning process verifies the implementation. The operations team trains on the plan before commercial operation.

Performance Criteria EOP-011 includes performance criteria for cold weather operation. The criteria specify the minimum temperatures at which the unit must be capable of operating, the warm-up and start-up considerations, the operating limitations, and the reporting obligations during cold weather events.

The performance criteria are technical and require careful coordination with the equipment vendors. The procurement of generation equipment specifies the cold weather capabilities that the unit must demonstrate. The commissioning process verifies the capabilities through testing under controlled conditions. The compliance program documents the verification.

Cold Weather Operations Training Operations personnel receive training on cold weather preparedness and response. The training covers the preparedness plan, the operating procedures during cold weather, the indicators of approaching problems, the response actions, and the coordination protocols. The training is documented and refreshed on appropriate intervals.

For federally funded projects, the training program is built before commercial operation. The training engages the operations contractor or the entity's own operations team. The training documentation supports the compliance program and demonstrates operational readiness.

Inspections and Maintenance The cold weather preparedness plan typically includes inspections and maintenance actions specific to cold weather. Pre-season inspections verify the freeze protection systems are operational. Periodic inspections during cold weather operation confirm continued readiness. Maintenance addresses any issues identified.

The inspection and maintenance program operates as part of the broader plant maintenance program but with specific cold weather components. The compliance program tracks the inspections and maintenance and documents the results.

Fuel Security For fuel-burning generation, fuel security is a cold weather preparedness consideration. The plan addresses fuel supply during cold weather events, fuel storage requirements, fuel quality considerations, and the coordination with fuel suppliers during constrained conditions.

For inverter-based generation including solar and storage, fuel security is not directly applicable but related considerations such as energy availability and storage state of charge may apply. The plan reflects the specific energy availability profile of the asset.

Coordination With Host Operators Cold weather operations require coordination with the host Reliability Coordinator and Balancing Authority. The coordination includes reporting on unit availability and any cold weather operating restrictions, receiving notifications about anticipated system stress, participating in conservation directives if applicable, and responding to system events.

The coordination protocols are documented in the operations procedures. The communication paths, the reporting cadence, and the response expectations are clear before cold weather events. Federal grant recipients new to NERC operations may need specific attention to the host operator coordination because the relationship is foundational to operating compliantly during stress events.

Documentation of Cold Weather Events When cold weather events occur, the unit documents its response. Documentation includes the timing of the event, the operating conditions, the unit's performance, any operating restrictions, any incidents, and the response actions taken. The documentation supports post-event review and any compliance examination.

NERC and the relevant Regional Entity may conduct post-event reviews following significant cold weather events. The reviews examine the performance of generation across the affected region and identify any compliance concerns or system improvements. Entities with documented preparedness and well-documented event response generally fare better in post-event reviews than entities without the documentation discipline.

Bridge to Chapter 8 The NERC reliability standards establish one regulatory regime. The federal grant award terms and conditions establish another. The next chapter walks through how the two regimes overlay on the same asset and how the entity manages the dual compliance overlay.

The Dual Compliance Overlay: Federal Award Terms and NERC Reliability Standards

The Dual Compliance Overlay: Federal Award Terms and NERC Reliability Standards

A federally funded BES-connected generation asset operates under two parallel regulatory regimes that do not coordinate with each other and that hold the recipient simultaneously responsible to both. The federal award terms govern the documentation, reporting, and substantive compliance with the program's requirements and the Uniform Guidance. The NERC standards govern the reliability-related compliance with the BES function. The two regimes operate on different timelines, with different examiners, with different consequences for noncompliance, and with different documentation expectations. The recipient that has built a strong compliance program for one regime may face gaps in the other. The dual compliance overlay is the framework for managing both simultaneously.

The Two Regimes Do Not Coordinate The federal awarding agency does not consult NERC on grant award decisions. NERC does not consult the federal awarding agency on enforcement matters. The two regimes have separate enabling statutes, separate regulatory architectures, and separate enforcement traditions. The recipient is the integrating party. The recipient's compliance program is what makes the two regimes coherent in practice.

Federal grant findings on a NERC-relevant matter do not automatically transmit to NERC. NERC findings on a federal grant-relevant matter do not automatically transmit to the awarding agency. The recipient that has documentation gaps in one regime cannot rely on the other regime to backstop the gap. The recipient that has overlapping documentation across both regimes benefits from the redundancy but must still satisfy each regime on its own terms.

Identifying the Overlap Areas Some compliance areas have substantial overlap between the two regimes. Procurement of major equipment is subject to federal procurement principles under 2 CFR 200.317-326 and is also subject to NERC supply chain considerations under CIP-013 if applicable. The procurement file must satisfy both regimes. The recipient can build a single procurement record that serves both, but the record must explicitly address each regime's specific requirements.

Personnel records are subject to federal cost principles for time and effort reporting under 2 CFR 200.430 and may be subject to NERC personnel requirements under CIP-004. The personnel files must satisfy both. Records for cyber security personnel under CIP must demonstrate the personnel risk assessment, training,

and access management required by CIP. The same personnel may also need to be documented for federal grant cost principles if their labor is charged to the award.

Documentation of construction activity supports federal grant requirements for cost reasonableness and supports NERC requirements for facility ratings, commissioning, and configuration management. The construction records must satisfy both. Photographs, daily logs, commissioning test results, and engineering certifications support each regime's documentation needs.

Identifying the Non-Overlap Areas Some compliance areas are unique to one regime. Federal grant reporting under SF-425 is unique to the federal regime. NERC self-certification reporting is unique to the NERC regime. Davis-Bacon prevailing wage compliance is unique to the federal regime, although it may have indirect impacts on personnel coordination. CIP cyber security incident reporting is unique to the NERC regime.

The non-overlap areas require specific compliance attention in each regime. The recipient that has built a strong federal grant program but no NERC program has unique exposure in the NERC-only areas. The reverse is also true. The dual compliance overlay identifies the non-overlap areas and ensures each is addressed.

The Sequencing Question Federal grant timelines and NERC compliance timelines do not align perfectly. The federal grant timeline is anchored to the award date, the period of performance, the reporting cadence, and the closeout. The NERC compliance timeline is anchored to the asset's commercial operation date, the standards' specific compliance dates, the audit cycle, and the ongoing operations.

The sequencing requires coordination. The federal grant's beginning of construction milestone may occur before the NERC compliance program is fully built. The federal grant's placed-in-service requirement may align with or differ from the NERC commercial operation registration date. The federal grant closeout may occur years before the NERC audit cycle for the asset.

The compliance program calendar captures both timelines and identifies the dependencies. Activities that satisfy both regimes are scheduled once with documentation that serves both. Activities specific to one regime are scheduled separately.

Roles and Responsibilities The dual compliance overlay requires clear roles and responsibilities. The grants administrator typically owns the federal grant compliance. The reliability compliance officer typically owns the NERC compliance.

The two roles must coordinate. Some entities create a single integrated role for federally funded BES connected assets. Other entities maintain the separate roles with explicit coordination protocols.

The coordination protocols include shared documentation systems where appropriate, joint reviews of compliance status at key milestones, escalation paths for issues that affect both regimes, and unified reporting to senior leadership and the board. The protocols prevent the gaps that arise when each role operates in isolation.

Budget Implications Both regimes carry budget implications. Federal grant compliance carries the administrative burden of the period of performance reporting, sub-recipient monitoring, single audit, and closeout. NERC compliance carries the burden of the compliance program operation, the audit cycle, the standards-specific testing and reporting, and the personnel and training infrastructure.

Federal grant applications for BES-connected generation should reflect the NERC compliance costs in the project budget as appropriate. The costs include the compliance program build, the staffing or contractor support, the documentation systems, and the training. Projects that have not budgeted for NERC compliance discover the cost after the award lands and either absorb the cost through other budget categories or face inadequate compliance.

Reporting to Stakeholders Both regimes generate reporting obligations that may extend to stakeholders beyond the immediate regulator. Boards, lenders, insurers, and rating agencies may require visibility into both regimes. The integrated reporting to these stakeholders draws on the dual compliance overlay and presents the entity's posture across both regimes.

Integrated reporting also supports the entity's risk management posture. Risks that surface in one regime may have implications in the other. A NERC compliance concern that affects the asset's availability may have implications for the federal grant's performance reporting. A federal grant disallowance that affects the project's financial structure may have implications for the NERC compliance program's funding. The integrated view surfaces these connections.

Bridge to Chapter 9 The dual compliance overlay requires an underlying documentation architecture that serves both regimes. The next chapter walks through the architecture and its operational mechanics.

Documentation Architecture That Serves Both Regimes

Documentation Architecture That Serves Both Regimes

The documentation architecture for a federally funded BES-connected generation asset combines the federal grant compliance backbone described in EC-WP-905 with the NERC compliance documentation framework. The combined architecture is not twice the work of either regime alone. It is closer to one and a half times the work because many documentation activities serve both regimes when designed deliberately. The architecture that serves both well is built around shared records where overlap exists and parallel records where overlap does not exist. The architecture is documented in a working register, operated by named personnel, and reviewed at coordinated milestones across the asset's life.

The Integrated Compliance Register The integrated compliance register extends the Compliance Obligation Matrix from EC-WP-905 to include NERC obligations alongside federal grant obligations. The register captures every obligation from both regimes with consistent fields: obligation description, source citation, responsible owner, evidence type, evidence location, review frequency, most recent review date, most recent review outcome, next review date, and risk rating.

The register treats federal grant obligations and NERC obligations as one unified set of obligations rather than as two separate lists. The unified treatment supports cross-regime coordination, surfaces dependencies and conflicts, and produces a single working document for management and board reporting.

Obligations that satisfy both regimes are flagged as cross-regime. The flagging supports efficient evidence collection. A single quarterly review activity that satisfies a NERC operational requirement and a federal grant reporting input can be conducted once with documentation that serves both. Without the flagging, the same activity might be conducted twice with duplicate documentation.

Shared Evidence Categories Construction and commissioning records support both regimes. The construction logs, photographs, commissioning test results, and engineering certifications provide evidence of cost reasonableness for federal grant purposes and evidence of equipment performance for NERC PRC and FAC purposes. The records are organized in a central location with cross-references to both regime requirements.

Procurement records support both regimes. The procurement files demonstrate compliance with federal procurement principles under 2 CFR 200.317-326 and support NERC supply chain requirements under

CIP-013 if applicable. The files include the procurement method documentation, the supplier evaluation, the contract documents, and any cost or price analysis. The same files satisfy the documentation requirements of both regimes when properly organized.

Operations records support both regimes. The plant operating logs, the dispatch records, the outage and event records, and the performance data support federal grant performance reporting and NERC operational compliance. The records are maintained in the plant operations systems with appropriate retention and access controls.

Parallel Evidence Categories Some evidence categories serve only one regime. Federal financial reports (SF-425), Federal Audit Clearinghouse single audit submissions, and federal grant closeout packages serve only the federal regime. NERC self-certification submissions, mitigation plan filings, and Regional Entity compliance audit responses serve only the NERC regime.

The parallel evidence categories are maintained separately because the regulator's review pathway is different and the documentation conventions differ. Federal grant documents follow the federal regime's templates and submission systems. NERC documents follow NERC's standards and submission systems. The compliance program preserves both sets without cross-contamination.

Document Retention Document retention requirements differ across the two regimes. Federal grant records under 2 CFR 200.334 generally must be retained for three years from the date of submission of the final expenditure report, with extensions for litigation, audits, or program-specific rules. NERC compliance records typically must be retained for a defined period that varies by standard, often three to five years, with specific requirements for certain standards.

The longer of the applicable retention periods governs each document. For documents that serve both regimes, the longer retention period applies. The records management system tracks retention by document category and supports compliant disposition when the retention period expires.

Access Controls Documents in the integrated architecture include sensitive content that requires access controls. CIP-011 information protection requirements apply to BES Cyber System Information. Federal grant records may include sensitive financial information, personnel information, and proprietary technical information. The access control framework satisfies both regimes' requirements.

The framework typically includes role-based access, with personnel granted access based on their roles in the compliance programs. Documents with CIP applicability may have additional handling restrictions including encryption in storage and transit, audit logging of access, and specific disposal procedures. Documents with federal grant sensitivity may have similar but distinct handling restrictions.

Coordination With Information Systems The documentation architecture interfaces with various information systems. Financial records live in the entity's general ledger system. Procurement records live in the procurement system. Operations records live in the plant historian and the SCADA system. CIP-relevant configuration data lives in configuration management systems. The architecture identifies the system of record for each document type and the reference paths that connect the architecture to the systems.

The interface design supports compliance examination across both regimes. A federal grant single auditor needing to verify a payroll record can trace from the architecture to the payroll system to the supporting documentation. A NERC compliance auditor needing to verify a protection setting change can trace from the architecture to the configuration management system to the supporting documentation.

Documentation Quality Standards The architecture establishes documentation quality standards that satisfy the higher of the two regimes' expectations. Where one regime is more demanding than the other, the architecture follows the more demanding standard. Contemporaneous documentation, clear attribution, complete source references, and appropriate signatures are the consistent expectations.

The quality standards are reflected in templates, work paper formats, and review checklists that the personnel operating the architecture follow. The standards make the documentation predictable and reviewable across the various personnel who contribute to it over the asset's life.

Bridge to Chapter 10 The documentation architecture supports audits in both regimes. The audit coordination question is itself a discipline. The next chapter walks through how federal single audits and NERC audits relate and how the entity coordinates across them.

Audit Coordination: Federal Single Audit and NERC Audit

Audit Coordination: Federal Single Audit and NERC Audit

The federal single audit under 2 CFR 200 Subpart F and the NERC compliance audit operate on different cycles, with different examiners, against different criteria, and with different consequences. A federally funded BES-connected generation asset is subject to both audit regimes. The entity that has prepared for both audits coordinates the preparation, the responses, and the corrective actions in ways that minimize duplication and maximize the credibility of the underlying compliance posture. The audit coordination discipline is the practical expression of the dual compliance overlay.

The Federal Single Audit Cycle The federal single audit applies to recipients of federal awards expending $1,000,000 or more in federal awards in a fiscal year, as updated in 2024. The audit is conducted annually by an audit firm the recipient procures. The audit examines the recipient's internal controls and compliance with the applicable compliance requirements for each major program identified. The results are submitted to the Federal Audit Clearinghouse and any findings are reported in the Schedule of Findings and Questioned Costs.

For federally funded generation, the single audit typically examines the federal grant compliance posture rather than the underlying NERC compliance. The audit may touch NERC-relevant matters incidentally if they affect federal grant compliance (such as the cost of NERC compliance personnel charged to the award). However, the audit's primary focus is on the federal compliance requirements.

The audit cycle runs on the recipient's fiscal year. Recipients with multiple federal awards consolidate the audit at the entity level. The Schedule of Expenditures of Federal Awards drives major program selection. The audit fieldwork typically occurs in the months following fiscal year end with findings reported in the audit report.

The NERC Compliance Audit Cycle NERC compliance audits are conducted by the relevant Regional Entity on cycles defined by the entity's risk assessment, the standards applicable to the registered functions, and the Regional Entity's planning. Audit frequency for typical Generator Owner / Generator Operator entities ranges from every three to six years depending on the size, complexity, and risk profile of the entity.

The audit examines compliance with the applicable Reliability Standards. The audit team requests evidence of compliance against each requirement. The entity provides the evidence through the documentation

architecture. The audit produces findings on any noncompliance identified. Findings are reported through NERC's compliance and enforcement processes with potential penalties depending on the severity of the noncompliance.

Some Regional Entities also conduct spot checks, self-certifications, and other interim compliance verification activities. The compliance program responds to each verification activity with appropriate evidence.

Coordinating Documentation Across Audits The integrated documentation architecture described in the previous chapter supports both audit regimes. Documents that satisfy both regimes are organized to be retrievable for either auditor on demand. The recipient does not maintain two separate documentation systems that need to be reconciled at each audit.

Coordination also extends to scheduling. Where possible, audit preparation activities for both regimes are scheduled to avoid simultaneous demand on the same personnel. Many recipients schedule federal single audit fieldwork in the months after fiscal year close and NERC compliance audits in the open windows around that schedule. The schedule reduces the operational disruption from audit activity.

Findings Resolution Coordination Findings from one audit may affect the other regime. A federal single audit finding about inadequate internal controls in procurement may surface a CIP-013 supply chain concern. A NERC finding about inadequate documentation of personnel access may surface a federal cost principle concern about personnel time and effort. The findings resolution process considers cross-regime implications.

Corrective actions implemented for one finding may also address the other regime's concerns. A corrective action that strengthens procurement documentation supports both the federal grant program and the CIP supply chain program. The corrective action plan reflects the dual benefit and the documentation captures both regimes' requirements being addressed.

Audit Defense Posture Both audit regimes are conducted under principles of cooperation and good faith engagement. The auditor is not an adversary. The auditor is conducting a regulated review with defined procedures. The recipient that engages cooperatively, provides requested evidence promptly, and addresses substantive concerns directly produces better audit outcomes than the recipient that takes adversarial postures.

Cooperation does not require capitulation on substantive matters. The recipient may disagree with an auditor's interpretation of a requirement and may defend the position in the appropriate forum. The defense is

conducted through substantive engagement rather than through delay or obfuscation. The documentation architecture supports the defense by providing the substantive evidence underlying the recipient's position.

Engagement With Counsel Both audit regimes may involve engagement with counsel at various stages. Federal grant audits with significant findings often involve coordination with general counsel and outside counsel familiar with the Uniform Guidance. NERC audits with significant findings often involve coordination with reliability counsel familiar with NERC enforcement.

Counsel engagement does not change the substantive compliance posture but it does protect the recipient's procedural rights and ensure that responses are calibrated appropriately. The recipient with strong compliance programs and good documentation needs less counsel intervention because the underlying compliance defends itself. The recipient with weaker programs needs more counsel intervention to manage the response process.

Reporting to Senior Leadership Audit results from both regimes are reported to senior leadership and the board through the entity's governance reporting. The reporting presents both regimes in an integrated view that supports the entity's risk management posture. Findings in either regime are tracked through resolution and reported until closed.

The integrated reporting supports executive understanding of the entity's overall compliance posture across the federally funded BES-connected asset. The reporting also supports communication with lenders, insurers, and other stakeholders that may need visibility into both regimes.

Lessons Captured for the Compliance Program Audit findings produce lessons that improve the underlying compliance program. The discipline of capturing lessons, integrating them into program improvements, and tracking the improvements over time supports continuous improvement. Findings that surface repeatedly across audit cycles signal program weaknesses that have not been addressed effectively.

Recipients that operate this discipline well find that audit findings decline in frequency and severity over time. Recipients that treat each audit as an isolated event without organizational learning continue to surface similar findings cycle after cycle.

Bridge to Chapter 11 The audit coordination discipline operates at the back end of the compliance lifecycle. The implementation patterns at the front end and through operations are the practical work the recipient conducts daily. The final chapter walks through practical implementation patterns drawn from the field.

Practical Implementation Patterns From the Field

Practical Implementation Patterns From the Field

Three decades of practice across the regulatory and operational sides of the energy industry have produced a set of practical implementation patterns that work for federally funded BES-connected generation. The patterns are not exotic and they do not require extraordinary resources. They require institutional decisions about staffing, structure, calendar, and coordination that the entity makes deliberately at the project's outset. Entities that have implemented the patterns operate the dual compliance overlay with manageable friction. Entities that have not implemented the patterns operate with friction that compounds and that surfaces eventually as findings, missed deadlines, or operational issues.

Pattern 1: Named Integrated Compliance Lead The first pattern is the appointment of a named integrated compliance lead with responsibility for both federal grant compliance and NERC compliance on the federally funded asset. The lead may carry other responsibilities but the federally funded BES-connected asset has a single integrated lead rather than separated grants administration and reliability compliance leads who happen to work near each other.

The integrated lead understands both regimes at a working level, coordinates across the substantive specialists in each regime, and produces the integrated reporting to senior leadership. The lead is the institutional memory of the asset's compliance posture across both regimes. Personnel transitions in either substantive function do not break the integrated lead's continuous tracking.

The integrated lead model works particularly well for new entrants to NERC who are also new to federal grants. The single lead develops fluency in both regimes simultaneously rather than two leads developing fluency in one regime each. Cross-regime issues surface earlier and are addressed by someone who understands both contexts.

Pattern 2: Coordinated Calendar The second pattern is a coordinated calendar that captures both regimes' obligations in one register. The calendar runs from beginning of construction through the asset's life and includes federal grant reporting dates, federal single audit cycle dates, federal closeout dates, NERC compliance dates including specific standard requirements and self-certifications, Regional Entity audit cycle dates, and the coordination milestones between the two regimes.

The calendar is visible to both the integrated compliance lead and the substantive specialists. Dependencies between events are flagged. Resource constraints during peak activity periods are managed through scheduling adjustments. The calendar prevents the surprise of a federal closeout deadline arriving in the same week as a NERC self-certification deadline.

The calendar is reviewed monthly with the integrated compliance lead and quarterly at a senior leadership level. The review confirms upcoming events are on track, identifies risks, and adjusts resource allocation as needed.

Pattern 3: Cross-Trained Staff The third pattern is cross-training of the staff who operate either compliance function. Federal grant administrators are exposed to NERC concepts at a working level that allows them to recognize when an action they are taking has NERC implications. NERC compliance personnel are exposed to federal grant concepts at a working level that allows them to recognize when a NERC activity has federal grant implications. The cross-training does not produce substantive expertise in the other regime but it produces awareness of the seams.

The cross-training takes a few hours of formal training plus the everyday experience of working alongside personnel in the other regime. Entities that cross-train well develop institutional knowledge that supports the integrated compliance posture. Entities that maintain rigid separation between the two functions produce friction at the seams.

Pattern 4: Documentation Shared Drives With Cross-Regime Tagging The fourth pattern is documentation organization that supports retrieval from either regime's perspective. Documents are stored in folders that reflect the asset's lifecycle (design, construction, commissioning, operations, decommissioning) rather than in folders that reflect the regime (federal grant, NERC). Documents are tagged with the regime requirements they satisfy. A construction commissioning test document might be tagged as supporting NERC PRC-024, NERC FAC-002, and federal grant cost reasonableness simultaneously.

The shared organization supports efficient retrieval. The tagging supports compliance examination from either regime. The structure scales as the documentation volume grows over the asset's life.

Pattern 5: Joint Reviews at Project Milestones The fifth pattern is joint reviews of compliance status at key project milestones. Beginning of construction, completion of major construction phases, commissioning completion, commercial operation, first quarter of operation, first annual review, and other milestones are points at which the integrated compliance lead conducts a review with both substantive teams.

The joint reviews confirm that the documentation is current, that the obligations of both regimes are being satisfied, that issues are being addressed, and that the calendar reflects the actual project status. Issues that surface in joint review at a milestone are addressed before they compound through the next phase.

Pattern 6: Procurement Templates That Address Both Regimes The sixth pattern is procurement templates that satisfy both regimes' requirements simultaneously. The templates include federal procurement principles language, federal cross-cutting compliance flow-downs, NERC supply chain risk management provisions where applicable, and any other regime-specific provisions. A single template, customized as needed for specific procurements, produces procurement files that satisfy both regimes without duplicate work.

The templates are maintained by the procurement function with input from the integrated compliance lead. Updates to either regime's requirements trigger template updates. The current versions are used on every procurement above the relevant threshold.

Pattern 7: Incident Response Protocols That Cover Both Regimes The seventh pattern is incident response protocols that cover both regimes. A cyber security incident triggers both CIP-008 reporting and potentially federal grant program officer notification. A construction safety incident may trigger federal grant performance reporting and NERC operational considerations. A protection misoperation triggers NERC reporting and may have federal grant performance implications.

The protocols include the events that may trigger reporting in either regime, the reporting paths, the timelines, and the documentation requirements. The integrated compliance lead is in the loop on any incident that may have cross-regime implications.

Pattern 8: Lessons Learned Documentation The eighth pattern is a lessons learned document that captures cross-regime insights as the asset progresses through its lifecycle. The document is maintained by the integrated compliance lead and updated continuously. Issues that surface, decisions that are made, and improvements that are implemented are captured with appropriate context.

The lessons learned document supports continuity across personnel transitions, supports development of subsequent projects, and produces institutional learning that the entity can apply across its portfolio. Entities operating their first federally funded BES-connected asset benefit substantially from the discipline because the asset becomes the foundation of the institution's expertise in this space.

Pattern 9: Engagement With Energy Compliance, Inc. Where the Capability Gap Is Substantial The ninth pattern, included for transparency given the source of this reference, is engagement with Energy Compliance, Inc. where the institutional capability gap is substantial. The firm exists in part to support entities operating at the intersection of federal grants and NERC compliance. The engagement provides the integrated compliance lead function on an interim or ongoing basis, supports the documentation architecture build, conducts the cross-regime reviews, and produces the institutional learning that builds in-house capacity over time.

The pattern is not appropriate for every entity. Entities with mature federal grant programs and mature NERC compliance programs can integrate the two with their own resources. Entities new to one or both regimes often benefit from external support during the build phase, with the support tapering as the institution develops internal capability.

Closing the Field Patterns The patterns above are not exhaustive. Every project develops its own variations based on the specific facts. The patterns are the foundation. Entities that adopt the patterns intentionally produce compliance programs that scale, that survive personnel transitions, that respond to audits in both regimes with credibility, and that support the underlying reliability and federal program objectives. Entities that do not adopt the patterns produce programs that depend on individual heroics and that fail when the heroes leave.

Federally funded BES-connected generation is going to be a significant part of the new asset additions in the energy industry over the next decade. The institutional capability to operate the dual compliance overlay well is itself becoming a competitive asset. Entities that build the capability early position themselves to take on additional federal funding with confidence. Entities that postpone the build face the same work later under more pressure.

Closing Note Federal money does not exempt an asset from NERC. NERC does not pause for federal reporting. Funded BPS-connected projects carry both regimes concurrently. The institutional capability to manage both is buildable. The patterns above support the build. The discipline is teachable and the references above transfer it.

If this reference surfaced gaps in your institution's capability to operate at this intersection that you cannot close in the timeframe of your active or pending federally funded BES-connected projects, the next step is a working conversation. Not a sales pitch. Energy Compliance, Inc. operates at the intersection of federal grants and NERC compliance and supports entities through the build phase, the operational phase, and the audit cycles in both regimes. The substance in the engagement is the substance in this reference.

Rob Smith, Founder, Energy Compliance, Inc.