Disturbance Reporting & Event Analysis

Foreword

Foreword

This professional reference is one of a series Energy Compliance, Inc. publishes for registered entities and the people who run their compliance programs.

I’ve spent more than thirty years on every side of the bulk electric system. I’ve operated control centers as a Reliability Coordinator, Transmission Operator, and Power System Operator. I’ve audited grid facilities and signed off on findings as a senior compliance auditor. I’ve worked enforcement matters from inside the regulator’s process. For the last several years I’ve advised registered entities directly through the firm I founded.

The entities that do reliability well share a common habit. They take the standards seriously without confusing them with reliability itself. They know that a NERC Reliability Standard is a floor, not a ceiling. They know that compliance is something an auditor evaluates, but reliability is something a system either delivers or doesn’t. They prepare for audits by building programs that survive real questions, not binders that look thick.

That’s the perspective these references try to share. Each one focuses on a single topic. A standard family, an operational function, a regulatory framework, or an emerging industry challenge. Each one walks through how the topic actually works.

These references are written for the compliance manager who wants to understand the system, not just memorize requirements. For the legal counsel who has to brief a board honestly. For the senior operator who’s been told that compliance and reliability are the same thing and suspects they aren’t. And for the new compliance hire who got handed a binder and told good luck.

These references aren’t marketing material disguised as content. They’re the result of three decades of doing this work and watching it succeed and fail. I’ve written them in the same voice I use in a control room or in front of a Regional Entity audit team. Direct, evidence-grounded, honest about what the standards do and do not require.

Energy Compliance exists because most of the consulting offered to registered entities today is structured for billable hours rather than for outcomes. Every engagement is led by one senior practitioner. We don’t bring five people to a meeting that needs one. We automate the work that should be automated. We apply senior judgment to the work that requires it. If that approach matches what you’re looking for in a compliance partner, the back of this reference has our contact information.

If not, the reference still belongs to you. Take what’s useful. Apply it well. And remember the only test that ultimately matters: when the system needs to perform, does it?

Rob Smith, Founder, Energy Compliance, Inc.

EC-WP-600 Disturbance Analysis and Event Reporting

Chapter 1

Statutory Authority and the Evolution of Mandatory Disturbance Reporting

In fact, major system disturbances such as wide-area power outages and cascading blackouts are commonly the result of many factors other than the immediate cause of a single failure or operator mistake. Examples of the complex layers of conditions that can lead to a major system disturbance

include protection system performance, operational awareness, planning assumptions, operator decisions, communication issues and governance boundaries. EOP-004 is intended to identify and document these complex layers of conditions in relation to the occurrence of major system disturbances.

This book examines the regulation of disturbances through governance functions, moving away from the idea of considering disturbance analysis as a maintenance or operational troubleshooting activity. This includes analysis of the reporting thresholds established, methodological requirements for root cause analysis, the structures of entities in charge of supervision, exposure to penalties for non-compliance, and the interaction between disturbance reporting and reliability growth. The investigation of disturbances can therefore have consequences on the standards that maintenance personnel must apply, on the methods used for supervising utilities, and on the level of exposure to compliance risk.

The function of disturbance reporting is not quite recognized as administrative. A look at the place of this function within the structure of the North American reliability system sheds considerable light on this situation.

Mandatory disturbance reporting did not become an operational requirement because FERC or the ISOs wanted it that way. The requirement came about as a consequence of the FERC mandated structural changes to the US electric power system imposed after the realization that voluntary reliability coordination, while being a good idea, lacked any real enforceable consequences to prevent or mitigate blackouts or widespread disturbances.

Existing prior to the Energy Policy Act of 2005, reliability standards were not enforced in a regulatory fashion and were followed on a voluntary basis. NERC relied on a system of compliance via peer pressure and potential reputational damage in the event of any non-compliance. The occurrence of a major power system disturbance such as the Aug. 14, 2003 blackout, was a symptom of underlying issues such as inadequate situational awareness, inadequate monitoring of vegetation growth and inadequate realtime mutual understanding of the status of the power grid. Each of these issues were highlighted by NERC in the final version of its black out after-action task force report in which it was found that reliability information important to power system operation was often not provided in a uniform and consistent fashion across systems.

Section 215 of the Federal Power Act mandated a reliability standard for the Bulk Electric System. It allowed FERC to certify an Electric Reliability Organization (ERO) and approve reliability standards that the ERO would enforce. Disturbance reporting became a mandated standard in the ERO reliability program.

EOP-004 merely formalized the existing requirement to report disturbances to the Electric Reliability Organization (ERO) and applicable Regional Entity. It provided definitions and procedures for identifying and reporting disturbances, including notification timeframes and after-notification activities.

Formalizing these requirements was more than a trivial matter of records keeping. Rather it reflected the growing understanding that it is not possible to reliably assess the effects of blackout-induced system wide disturbances (EWS) if they remain a local phenomenon that is not reported.

Mandatory disturbance reporting supports several governance objectives simultaneously.

Information will facilitate understanding across reliability boundaries. The Reliability Coordinators (RCs), Balancing Authorities (BAs), Transmission Operators (TOs) and Generator Operators (GOs) each operate within somewhat independent systems. A disturbance in one area may have significant impacts in other systems. Better information will enhance situational awareness.

Second, it creates a regulatory enforceable record of the event. Because any disturbance analyzed under a reliability standard that designates particular disturbances as reportable would be reportable whether the utility decides to do the analysis or not, and failure to report an event when required to do so is itself a potential violation of the reliability standard, disturbance analysis moves from the status of being a relatively optional method of understanding what has happened to a regulated utility’s obligation to collect and provide information about certain types of disturbances to the Commission and FERC.

Third, the methodology aids in standards evolution. Many of the present reliability standards were modified because conclusions from disturbance analysis studies revealed specific aspects requiring corrections. Examples abound: misoperations of protection relays, unsatisfactory relay coordination and lack of sufficient reactive reserves have all made their way into revised technical standards, and the process of change is largely a result of distilling and sharing meaningful experiences. If these feedbacks were not recorded systematically, they might not be established at all.

The authority for the Electric Reliability Bulletin disturbance reporting is statutory and institutional in nature. The FERC approved the standard. The ERO implements it. The REs ensure that compliance is maintained and provide technical review of the final event reports. The Registered Entity carries out the instructions of the standard.

Disturbance reporting is a function defined in a boundary. A disturbance event must meet certain criteria in order to be considered reportable for loss of firm load, system islanding, voltage collapse, uncontrolled separation or other criteria defined in the reliability standard. These criteria are not arbitrary but rather are a balance of the burden of reporting and the severity of the event impact on reliability.

When originally released, EOP-004 contained thresholds and definitions which would need to be revised over time in order to better reflect specific operational conditions. Timeframes for disturbance reporting were also adjusted to better meet operational requirements. The changes to EOP-004 show that the process of disturbance reporting is a dynamic one and that governance processes and associated controls must be dynamic to in order to keep pace with increasing system complexity.

Grid disturbance patterns are evolving due to high penetration of inverter-based resources, distributed energy resources and smart grid controls. Event analysis is involving power electronic systems and their associated issues like ride through performance and protection system operations. The new Disturbance Reporting Process enhances the understanding of new reliability patterns occurring in modern grids.

In an enforcement context, Disturbance Reporting can reveal compliance risk beyond the scope of the Reporting Standard. An event analysis may highlight non-compliance with vegetation management requirements, protection system maintenance requirements, or operational planning requirements, and the disturbance report can be used as evidence during a regulatory inspection.

Ce double rôle de caractère pédagogique et d’exposition des acteurs aux contraintes de légalisme constitue le cœur de l’importance institutionnelle des méthodes de simulation d’incidents.

The purpose of disturbance reporting is not to apportion fault in the legal sense. Rather than to assign legal fault, disturbance reports record causality in the reliability sense. The legal and reliability definitions of causality are different. The reliability view records conditions in each of the many layers of the power system that interacted to cause real system consequences. The enforcement view records whether violations of established reliability standards have occurred.

It is crucial to grasp the difference to understand how disturbance analysis works as a governance tool, not as a punishment.

The shift from a regime of voluntary provision of disturbance data to one of mandatory analysis of disturbances constituted a major change in the regime of reliability surveillance. It introduced a certain institutionalisation of the experience and provided a means whereby major incidents in the system can be translated into a quantifiable dynamic for the development of reliability practices.

End-of-Chapter Summary

This authority to require Mandatory Disturbance Reporting is found in the FPA, Section 215. EOP-004 introduces the requirement to be in a position to document and analyze disturbances of significant importance to the Grid. The purpose of Mandatory Disturbance Reporting is to provide visibility, enforce accountability and serve as a learning feedback mechanism to support RRT standard development activities. Mandatory Disturbance Reporting is a process for capturing knowledge and lessons learned in a manner that encourages operational learning and accountability, while providing multiple levels of regulatory oversight and exposure rather than an investigation.

Chapter 2

EOP-004 Structure, Thresholds, and Reporting Architecture

EOP-004 describes in detail the requirement for the registered entities to report disturbances on the Bulk Electric System. This standard does not identify each and every anomalous condition that may occur. The quantities and levels contained herein are intended to represent a range of disturbances with potential reliability impact that are significant to require reporting of other less significant and more normal system operating variations. The EOP-004 standard describes the architecture of events that must be reported in accordance with this standard through three components: initial notification, written follow-up reporting and event analysis documentation. The time limits for each component and the entities concerned are specified in the standard. The allocation of responsibilities is carried out in such a way that the reporting of events corresponds to the operational visibility and control authority that an entity has in relation to the occurring event at the time in question. The initial notification requirements are to ensure that the impact of significant disturbances are reported quickly to the ERO and the applicable Regional Entity, and that is typically within a few hours of the incident being discovered. This is not a matter of trying to perform detailed technical analysis. The purpose of these requirements is to provide a means for the regulatory bodies to quickly get an understanding of the nature of an occurrence so that they can assess whether the conditions that caused it are systemic or isolated and thus have an impact on the overall reliability of the interconnection. The written follow-up report is used to document the factual progression of events, identify the involved technical components, system conditions and to make a preliminary assessment of possible reasons. Notification has thus been changed to documented reporting. The report is a permanent documentation in the plant and may also be subject to official verification. The event analysis requirement is a bit more complicated with the addition of the event analysis component. In this case, entities must conduct a root cause analysis for disturbances that occur in accordance with the defined parameters, in addition to determining the corrective measures necessary. Rather

than simply documenting what failed, an entity must also consider why something failed and what barriers or compensatory controls were in place to allow the failure to occur and to enable the disturbance to proceed. EOP-004 defines disturbances and non-disturbance events that are reportable. Many risk conditions related to reliability are not necessarily disturbances, but are material to reliability nonetheless and should be reportable. For example, a protection system misoperation, an uncontrolled

system islanding, an unexpected voltage collapse, etc. do not necessarily result in large firm load loss, but are still a material reliability issue and are defined within the reporting triggers of this standard. Note that many of the thresholds referenced in EOP-004 are based on measurable system effects such as amounts of firm load lost, durations of an uncontrolled separation, or other activation levels for system protection equipment. Some of these criteria are based on reliability significance, not commercial importance. EOP-004 remains focused on Bulk Electric System stability. Threshold calibration and reporting criteria are generally based upon industry wide experience. Reporting criteria have evolved over time primarily as a result of past disturbance studies and FERC requirements. Thresholds cannot be set too low, or there will be reporting fatigue, and relatively unimportant events will be buried in large volumes of report data. Conversely, thresholds cannot be set too high, or otherwise valuable transmission system knowledge will be lost. Note that functional reporting responsibility is not uniform, and that BAs, Trans Operators, GEs, and RCs may have reporting responsibility based on the nature of an event, in the same manner that they were established in the functional model of the NERC Rules of Procedure and NERC Glossary of Terms. Primary reporting responsibility is based on functional responsibility at the time of the occurrence. This allocation reiterates the notion that disturbance reporting cannot be separated from functional registration. An organisation cannot be said to be able to perform the EOP-004 task of reporting disturbances, if its registered functions and corresponding reliability commitments are unclear. Non alignment of operational authority and reporting can introduce compliance risk. The timeframes in EOP-004 are not simply arbitrary intervals established to achieve some administrative purpose. They are designed to reflect Governance imperatives related to timely institutional actions to achieve goals such as coordination of system planning to address general interconnection issues that may require attention from the Governance structure. Expedited reporting to address the timeframes in EOP-004 is necessary to afford governance or regulatory oversight entities sufficient opportunity to review the reported conditions in order to ascertain whether the events

are unique to the particular interchange or represent a general condition in the WAPA Region that also requires consideration. Without such timely reporting the Governance structure will lose visibility into the transmission system operations, which will diminish visibility and confidence in reliability self reporting. These guidance notes are intended for information only. They do not form part of the contract between FDR and an entity and must not be taken to suggest any particular course of action. The written report must be a true and accurate statement of events and sufficient detail must be provided so that the contents can be verified and reviewed independently. Information that is open to more than one interpretation, or which leads to less than unequivocal conclusions, or where data has not been provided may result in a request for clarification from the Region. The request is likely to be confined to the FDR Reporting Standard(s) but may extend beyond in the event that the circumstances of the disturbance are such that they raise a question of compliance with another Reliability Standard(s). The reporting structure creates a multi-layered record. The first layer is the initial report of the incident; the second

layer is the factual record of events as captured in the written report, the third layer is the event analysis that captures root cause and any corrective actions. These three layers are intended to provide an adequate evidence base for corporate learning within Reliability and audit purposes within Oversight. EOP-004 does not specify root cause failure analysis procedures. Rather, it requires analysis sufficient to determine cause and to identify necessary corrective actions. The Commission recognizes that the complexity of different types of systems and disturbances, as well as the size and resources of different entities, can vary significantly. Failure to adequately analyze disturbances and their consequences may itself attract NRC attention if the entity’s analysis appears to be perfunctory or inadequate. The disturbance reporting process described in EOP-004 is a part of a larger post-event review process. The ERO may investigate a major disturbance independently, or it may send teams of personnel to investigate in conjunction with task forces organized by industry. The FERC may also release reports of its investigations into significant disturbances. The ERO typically uses reports submitted by entities as a basis for the work it undertakes. The reporting architecture serves several institutional audiences at the same time. Reports are meant to contribute to the oversight that bodies, such as industry regulators, have over individual entities. They facilitate awareness building at the level of the internet interconnection ecosystem as a whole, and can be used in discussions concerning the adoption of formal standards, while also serving as proof of compliance with applicable requirements. An entity’s submission of a report means that it acts as both provider and object of the information contained therein. Disturbances on the Bulk Electric System are becoming more complex and variable in nature due to the changing nature of the BES including increased inverter-based resources, greater amounts of distributed energy resources, and use of new control systems. Reporting narratives are addressing a wider variety of dynamic performance behaviors including protection system coordination issues arising from non-synchronous generation and control system interactions. EOP-004 is intended to formally document the new operational issues arising from these changing aspects of BES operations. District and sub-district level disturbance reporting in Bangladesh is largely seen as a matter of compliance. Looking at the broader context of the national disturbance reporting system, it is clear that reporting disturbances is a coping mechanism for bridging the space between on-the-ground operations and policy level adaptation of the governance arrangement at the district level. By setting up specific threshold levels for disturbances to be reported to higher authorities, they act as a filter mechanism to determine when the fluctuations in the daily operations of any project should be considered as unusual and therefore reportable to higher levels of management. The reporting mechanism once triggered, turns ordinary occurrences of disturbances into criminal and operational violations which the implementing agency and the concerned implementing staff have to defend against and explain.

FROM THE FIELD

EOP-004 doesn't list every anomaly that has to be reported. It lists the categories. Knowing which category a real event falls into is the operational judgment the standard demands.

End-of-Chapter Summary

EOP-004 outlines procedures for reporting as a discipline of communication comprising of at least three levels of detail, ranging from an initial alert through to a written account and detailed analysis. The calibrated number of occurrences establishes a reliability disruption of material consequence (MCC) with appropriate bounds of discretion. The responsibility for preparing the report is based on the FSRC for the affected component. Analysis and conclusions included in the report will constitute an official documentation of ERA’s Management’s knowledge base. Disturbance reporting serves two fundamental purposes within a nuclear power plant; the dissemination of knowledge (reliability learning) and as a basis for management decision-making, thereby linking disruptions that occur during normal power operations with the governance processes that shape the station’s overall performance.

Chapter 3

Root Cause Analysis Expectations and Methodological Discipline

The EOP-004 Disturbance Reporting section does not deal simply with sequencing events in a time order. Rather, the standard calls for identification of cause and for corrective actions which calls for more than simple narrative. The standards call for analytical skills in addition to descriptive writing. Root cause analysis in the context of reliability is not defined by a specific method or procedure mandated in the standard. Neither fault tree analysis, cause mapping, barrier analysis nor any other method for investigating disturbances is referred to. The reason is that different types of disturbances have different characteristics, such as magnitude, complexity and character. And this does not imply that no analysis whatsoever should be made. An EOP-004 Disturbance Report which does not contain sufficient detail or analysis to determine the role of system conditions in determining the final outcome (i.e. it is an unreasongable assertion of individual failure and nothing more) does not fulfill the intent of the procedure. As we all know, it’s virtually impossible for individual components to fail in isolation. Most failures will involve multiple variables and combinations of original system design, maintenance practices, relay settings, operational procedures, protocols and environmental and ambient conditions. A root cause analysis identifies both direct and indirect causes. The direct or immediate cause may be a relay operation error or a transmission line (or component) failure. The indirect or underlying cause may be related to items such as relay settings not properly coordinated, inadequate routine testing, incorrect modeling assumptions, or operation constraints. The reliability methodology is not limited to identifying only direct or immediate causes. This analysis helps in bringing the issue of institutional accountability in the limelight. When a major disturbance occur in a system, which could cause harm to people or the environment, the root cause must be corrected for good, as merely attending to the symptom of a problem caused by design or institutional deficiencies does not prevent future such problems occurring in the same system. A repair that merely replaces failed equipment and does not consider the appropriateness of the system’s

procedures and institutional arrangements may be inadequate. Regional Offices that conduct review of disturbance reports covering Fernald Landfill Ash will review the sufficiency of the root cause analysis in the report. The review is not a simple determination that the regulation related to reporting has been met, but rather, an evaluation of whether the sufficient analysis has been conducted relative to the number and type of possible causal paths identified, and appropriate measures taken to preclude

repetition. If the causal analysis is found to be insufficient, additional information requests or a compliance audit may follow. Reliability causation vs enforcement evaluation is still a major issue. Root cause analysis is about understanding the interaction of conditions that resulted in a system impact. Enforcement review is about determining if these conditions constitute a violation of the reliability standard. It is not the same thing. An event can bring to light a weakness in the system independently of causing harm. Conversely, an event can bring to light non-compliance to the reliability standard in isolation. Methods shall ensure that evidence such as event logs, sequence-of-events records, relay data, operator logs and communication transcripts are preserved. Data integrity is critical to any analysis. Loss of data may impact the validity of any conclusions drawn from the analysis and shall be considered when evaluating the adequacy of procedures for compliance with other standards. Digital data is becoming a larger component of the tools used for disturbance analysis. Information ranging from Phasor measurement unit (PMU) data and digital fault recorder (DFR) recordings to supervisory control and data acquisition (SCADA) logs provide great detail about possible sources of power disturbances. However, it can be difficult to pinpoint relevant data, given the amount of information that can be collected from various sources. Without a structured method to analyze that data, it can be overwhelming and confusing. When conducting a Root Cause Analysis (RCA), it is natural to initially focus on the technical and engineering aspects of a potential anomaly. However, the investigation into what happened must also consider the Human Performance (HP) factors. e.g. decisions made by operators in high pressure situations, alarm presentation, operator work load, and adequacy of communication to the various groups of people involved. A technical analysis alone will not account for HumanSystem interactions and their impacts to the system as a whole. Reliability and integrity of institutional learning depend on honest assessment. The value of disturbance reporting to reliability operations is based on accurate description of conditions that may have contributed to the disturbance. While compliance with regulations regarding reporting of disturbances may provide some degree of protection

from exposure to enforcement actions in the short term, distortion of the data to minimize the likelihood of exposure can prejudice the reliability program in the longer term and also undermine the credibility of the regulatory body. The corrective action documentation is an important part of the disturbance reporting process. Corrective actions could be anything from modifications to equipment, procedural changes, additional training, review of current protection settings, modeling updates, and a review of the adequacy of the corrective actions. The NRC will review whether the corrective actions were adequate to address any disturbances. The corrective actions must be logical to the type of disturbance that occurred. High Voltage lines are not always the sole contributing factor to the occurrence of a complex system event. Correlating the root cause to the appropriate function group can be very challenging, and variations in interpretation can cause inconsistency in reporting. It is RCO function to facilitate a concensus of knowledge concerning the nature of events in order to represent the overall understanding by the Interconnection. Entity reports submitted by utilities following a major disturbance

investigation by the ERO or a joint industry task force are often part of a more inclusive investigation that includes other entities. While useful tools for internal reviews, entity-submitted root cause analysis reports can become incorporated into a more institutional review to enhance credibility of the overall effort. The pressure on analytical discipline has increased in recent years. This is primarily due to increasing system complexity and higher-level monitoring. Disturbance reports, which are reviewed by control room personnel and experts, are investigated more thoroughly. The reliability discipline is increasingly moving away from documentation as a reactive measure towards a more regular and institutional basis. This analysis is more than simply a means of performing “technical fault fixing” under EOP-004. We are dealing with a governance procedure that requires careful evaluation of a stack of conditions, maintaining the integrity of the evidence gathered during the root cause analysis, ensuring that the root causes found are consistent with the repairs that are implemented and that this procedure has a significant impact on the compliance level and therefore on the adaptability of the entire reliability framework.

End-of-Chapter Summary

Root cause analysis (in EOP-004) should not be a simplistic check list against possible technical failures. Effective disturbance analysis should take into account not only first order causes and effects but also second and later order and help keep evidence trail alive. Each remedy recommended should be related back to its root cause. Oversight and review then becomes a test of how detailed the analysis was and the degree to which procedures for disturbance analysis were adhered to with the resultant documentation then being a matter of governance rather than documentation for documentation’s sake.

Chapter 4

Institutional Accountability and Oversight Review

In EOP-004, the process of documenting disturbances in order to gather relevant information in support of determining whether a significant event has occurred ultimately results in the submission of an event record that can be processed through the formal regulatory procedures of the Electric Reliability Organization and its member Regional Entities. In this scenario, what begins as an operational disturbance in the power system can come to be seen as nothing more than a paper event; an analytic construct to facilitate regulatory requirements. When reviewed and investigated, and the resulting analysis and event record subject to enforcement, the occurrence of an operational power system event is fully subsumed by the regulatory process. Accountability under this system is multi-layered. Accountability of entities is provided within the context of their registration, with the registered entity being accountable for the accuracy, sufficiency and appropriateness of the content of reports and analyses submitted by others. Accountability of the Regional Entity is ensured by reviewing and verifying the adequacy, relevance and quality of submissions, to determine if they are sufficiently complete, clear and relevant to assure compliance with ERCOT Reliability Standards. The ERO maintains accountably for determining whether events are bulk power system events under ERCOT Reliability Standards or are otherwise appropriately referred to the ERO for management. The FERC retains statutory accountability for ensuring the ERO fulfills its duties under Section 215 of the Federal Power Act. While we do not assume a violation has occurred, our initial focus is on establishing whether applicable reporting requirements have been met and whether criteria are satisfied for more detailed investigation of individual incidents of treecontact or other disturbance to the right-of-way. The review rarely remains constrained to a determination of whether rules applicable to reporting disturbance have been met. Accounts of disturbances to the rights-of-way frequently shed light into various aspects of vegetation management, protection and structure maintenance activities, operating practices, analytical models and training that can be the subject of separate regulatory rules. Der Disturbance report kann als evidentiary startpunkt für die compliance inquiry behandelt werden. Somit wird die Funktionsweise des EOP-004 auf der einen Seite den Prozess der institutional learning, auf der anderen Seite der administrative regulatory compliance zu repräsentieren. Regional Entities will use a risk-informed review process to address disturbance reports. Events involving large loss of firm load, uncontrolled separations, potential voltage instability issues, or protection system maloperations, for example, may warrant closer review. The degree of further review will depend on the size and uniqueness of the event. In a few

instances, regulatory bodies have requested additional information on a variety of subjects, such as relay settings, sequence-of-events information, maintenance records, and operator logs. These requests serve to underscore the importance of having hard evidence to support any disturbance analysis conclusion. Purely subjective findings can undermine the credibility of the regulatory body. Major disturbances may be the subject of independent ERC (ERO) investigations, or may be investigated in conjunction with the federal energy regulatory commission (FERC). These investigations often yield comprehensive reports on the condition of the power system at the time of the occurrence; the events leading up to the occurrence and their relationship to the final disturbance; and suggested enhancements to bulk power system reliability to help prevent similar occurrences in the future. These findings are used as input to various standards and policy changes throughout the industry. There are several instances where institutional accountability cannot be restricted to individual entities. This work explores instances of disturbances that arise because of coordination gaps between various functional entities. Voltage collapse, due to its cascading nature, very often leads to involvement of the Generator Operator, Transmission Operator, Balancing Authority and others. Oversight review would focus on the adequacy of communication agreements, visibility standards, etc. in the grid operations, the degree of alignment between grid models and other aspects that might require accountabilities at a higher level of granularity. Layered accountability does not diminish the need for entity-level discipline. As a registered entity you have governance processes in place to manage reliability risks, document and mitigate potential vulnerabilities. Disturbance reports test the adequacy of these processes. The approach to disturbance oversight has matured. Prior to 2005 the focus was on building a compliance culture and ensuring the relevant processes were in place. As the reliability landscape was solidified, the focus of oversight has progressed towards issues of risk consequence and knowledge development. Nowadays, disturbances are increasingly viewed as an indicator of network and system health, as much as an enforcement event. There are significant enforcement implications arising from the conduct of disturbance reporting activities. While none of the reported incidents resulted in findings of violation, most required recommendations for improvement in reliability to prevent future occurrences. A few instances evidenced more than a reasonable doubt as to compliance with applicable enforcement standards and notices of penalty were issued or settlement agreements entered into. Findings were made on the basis of the particular factual circumstances of each incident and whether the applicable standard was clearly met, and whether required controls were in place. Transparency in relation to disturbance reporting is a very important aspect of ensuring that regulatory credibility is maintained. Quality of analysis and candour when it comes to the identification of potential risks, as well as prompt rectification of issues highlighted in reports, can all be a factor in the assessment of an organization’s reliability governance and, conversely, non-disclosure and late rectification of issues may lead to greater exposure to regulatory actions. IR/WRC – institutional reporting on EOP-004 is related to corporate governance. Boards and senior management now pay greater interest to major disturbances on account of their nature as indicators of enterprise risk. Reliability performance has many corporate consequences

– including economic, reputational and regulatory. So reporting disturbances has become a corporate activity as well as an operational and institutional one. The characterization of disturbances impacting the Bulk Electric System is undergoing change due to increasing levels of automation, higher penetration of inverter-based resources, and evolving digital systems. Regulatory bodies are evolving their analytical frameworks in response. Expectations will likely expand to address new facets of disturbance characterization, such as performance of dynamic models, control system settings, and cyber-physical coupling as appropriate. Disturbance reporting is a mechanism within an adaptive governance system. It transforms ordinary operational disruptions into vehicles for holding managers accountable, for regulatory review, and for organizational learning. Its success will depend on careful management of the reporting process, the quality of the analyses that are prepared to accompany reported events, and the manner in which regulatory bodies choose to exercise their review and disciplinary authority.

End-of-Chapter Summary

Under EOP-004, all disturbance reports are subject to review in one of three possible layers, including one or more of the following: Regional Entities, the Electric Reliability Organization (ERO), or the U.S. Federal Energy Regulatory Commission (FERC). Review may not necessarily be confined to the scope of the report, and could potentially extend to the entire standard to confirm the report is in compliance and has not resulted in a violation of any other standard. Governance, Interconnections, and Corporate will all play a role in the understanding of institutional accountability as it pertains to entity-level oversight of all aspects of disturbance reporting. Disturbance reporting serves not only a learning function to help personnel learn from past disruptions, but also as one of the many tools of regulatory visibility.

Chapter 5

Disturbance Analysis as a Driver of Standards Evolution

In some sense, this disturbance reporting procedure which is part of the implementation of EOP-004, does not represent a very independent activity in the context of the reliability standards development process. In fact, major system events have triggered many of the detailed specifications, definitions of specific functions and reviews of performance criteria which presently exist in this process. Disturbance analysis is the foundation upon which these developments are based. Reliability standards in the FERC SP Section 215 are not static. Changes can occur due to petitions from stakeholders, FERC actions, ERO actions, or through changes proposed by interested parties in the industry. Often the impetus for these changes is based upon lessons learned during disturbance analyses. Major power disruptions have uncovered numerous issues that were not covered by existing IEEE standards. As events occurred, stakeholders realized they lacked situational awareness, operational procedures, protection system performance or adequate practices for vegetation management, among other things. The issues were recorded in the disturbance reports and root cause analysis, which serve to educate the standardization process. The process to transition from the initial disturbance event to the revisions to applicable standards goes in this order. The initial reports contain data and analysis relevant to the affected entity. Further investigations are often done to correlate data across similar areas or functional systems, which are recorded in either the FERC Final Reports or in technical reports for NERC use. Standards Development Working Groups would determine whether current standards or regulatory requirements are adequate to mitigate the risk associated with each of the identified Conditions. This is an example of adaptive governance. The reliability framework is not fixed, it evolves as new information is collected. Disturbance analysis can therefore be viewed as a feedback loop embedded in the regulatory framework. The performance of protection system performance is given as an example. Relay misoperations and coordination problems following past disturbances required more detailed maintenance, testing and recording in the protection and

control standards. However, the analysis of disturbance data revealed that the performance of the protection system may even increase the severity of a disturbance if the coordination assumptions prove to be incorrect. This standard was updated accordingly. Voltage instability events have also influenced some of the criteria for reactive power control performance specifications and model validation. Disturbance analyses to record inadequate reactive support during stressed voltage conditions have led

to increased focus on generator performance characteristics and model validation. Power outages due to Vegetation-related transmission disruptions as recorded in Disturbance Reports prompted the instatement and augmentation of Vegetation Management standards, the legacy of which continues to inform the OSH regime of Compliance Monitoring. The incorporation of inverter-based resources has introduced new reliability challenges and phenomena. Events related to ride-through, dynamic responses to frequency excursions, and protection interactions are becoming focus points for grid reliability regulatory activities. The GRC uses event analysis to document unusual behavior exhibited by systems, resources and technologies and uses these observations in discussions of modeling requirements and performance validation. The evolution of standards is not an automatic reaction to a disruption. The tempo is set by man. Not all incidents of failure warrant a change to regulatory standards. Regulatory agencies typically want to determine if the vulnerability found is an isolated incident or a general trend. The determination greatly influences whether the remedy is left to the individual operator or becomes a part of the general body of national or industry standards. The disturbance reporting framework therefore allows for differentiated governance responses, taking into account both the nature and extent of potential disturbances. In the event of local disturbances caused by faults on individual stretches of transmission lines and power cables, an affected company may undertake measures to rectify faults occurring on its own networks, while the regulatory framework remains unchanged. Should the interconnection-wide disruptions that have been registered on several occasions following specific incident scenarios be confirmed, it may be necessary to adjust the relevant technical standards. Disturbance analysis contributes to risk-based compliance monitoring by providing information on specific events that can impact the focus of the Regional Entity, the priorities for audits, and the scope for targeted compliance activities. The reporting record also assists in the assessment of emerging reliability risk domains. Transparency in the process of disturbance reporting contributes to the transparency and integrity of the process of standard development. The standard development process is made

more transparent when the public disturbance reports contain enough factual information to allow stakeholders to determine whether the proposed changes are based on real operational experience or on policy consideration. Disclosures and Findings provide an institutional record of reliabilty learning experience. Although personnel changes within utility staffs and regulatory bodies can obscure insights gained from past difficulties, these insights are preserved when they are developed into extensive analyses and revised standards and guidelines, and can be brought to bear on future disturbances. This is the third element of the non-punitive nature of the reporting framework. The fact that the work on the disturbance analysis and standards evolution reflects the absence of punitive intent is further proof of this. There may be enforcement exposure in the event of non-compliance being discovered, but the overarching goal of the reliability regime is to achieve improvement. Originally developed as a part of the Grid 4 work item on Cyber Threat Intelligence the work described in this Standard has now been

incorporated into the Canadian Regulatory Framework as part of the Grid disturbance analysis procedure. Disturbance analysis as part of a structured governance cycle of standards development is described below. Current grid operations disrupt some regulatory elements of the standards and analytical documents describing these disruptions are used by regulatory personnel to carry out their evaluation. The evaluation may call for some refinement to the standards and with the evolution of grid resources the design of future grid operations may then differ from that of the past, and so the cycle is reestablished due to the evolving nature of grid complexity. EOP-004 is more than a reporting activity. It is a procedure by which the reliability programme can be dynamically updated and adapted based on real data. A high level of analysis, presentation and management of the data is requested in order to ensure that the activities carried out provide a useful contribution to enhance the reliability programme. Hence, the reliability of CIV-NPP equipment must be assured through appropriate analysis, design, construction, testing, operation, maintenance and quality control of the materials, components, and structures involved.

End-of-Chapter Summary

Disturbance analysis under EOP-004 is an input to the development of reliability standards. Documented events are used by regulators for standard development, technical research and risk-based monitoring. Including documented events in the reporting framework allows for the incorporation of real life experiences into the governance

structure of the grid, thereby allowing for changes to be made to standards as weaknesses in the system are identified. Thus, the disturbance reporting serves as a valuable feedback mechanism to ensure that reliability improvements are maintained over time.

Chapter 6

Disturbance Reporting, Enforcement Exposure, and Risk Posture

The new element to consider in this mix is the aspect of Disturbance reporting under EOP-004, which injects a new layer of transparency to an entity’s overall compliance risk posture. What started as an account of a simple disturbance is now an official entry that the regulator may scrutinize, infer and perhaps take enforcement action on. That this mandatory reliability provision impacts everyday governance processes is neither new nor surprising. It is merely a new fact to take into account. It is not always clear how all of the compliance elements will fall out of a disturbance report. Depending on the findings, a disturbance occurring in a manner that conforms to all reliability standards and, even though the necessary controls and procedures were properly in place, results in considerable system impact may result in little more than exposure to process or other notices. Conversely, the resulting analysis may document a variety of shortcomings related to work practices, operating procedures and modeling, which indicate the existence of enforceable violations of more than just EOP-004. The reporting standard itself is about process. The violation is about non disclosure, lack of detail, late submission etc. While the risk of non-compliance with the reporting requirement is likely to be more substantive in relation to what is actually reported, in particular in relation to system performance and governance controls. This creates a tension in the reliability system. Suppliers have to make a thorough and accurate assessment of their production and procurement capabilities in order to demonstrate reliability of supply. At the same time, they may not wish to draw attention to potential compliance issues which could be revealed by this process. The integrity of the reliability regime, and therefore its ability to promote real and lasting change, will be undermined if suppliers do not provide honest and accurate assessments. As per the riskbased enforcement, a number of findings arising from disturbance investigations are not being taken as seriously as before. While all valid breaches arising from such investigations are being documented, not all carry the same degree of consequence. Regulatory activity is focusing on key elements that are more relevant to

breach rankings. In essence these are focusing on greater damage to the forest environment, absence or adequacy of compliance controls to the extent that non-compliances are more management oversights than other issues, history of compliance at a facility or site and in the timing of their repair. Enforcement activities are evolving. Disturbances can be reported as an indicator of the governance of nuclear safety. An adequate report can serve to reduce the regulatory concern in case of only minor technical

deficiencies are noted, as long as the report is written in a timely manner, with a proper analysis of the event, adequate determination of the causes and appropriate corrective measures. The quality of the reports can also be considered as an indicator of the level of maturity of the organisation being reviewed. Multiple occurrences of the same type of disturbance may affect the regulatory body’s posture toward the utility. If a pattern of overall weakness in maintenance practices, forestry, or operating procedures is observed, it may result in reclassification and increased focus on compliance monitoring. Disturbance data is also used to evaluate reliability performance over time. The exposure to potential enforcement action is not limited to technical standards, and events that lead to communication errors, incorrect modeling assumptions or insufficient data retention may result in enforcement for reliability as identified through the event analysis exercise. The Disturbance Report becomes a “cross-reference document” relative to possibly impacted reliability standards from one or more standard families. The relationship between disturbance reporting and risk posture extends to the corporate governance level. A publicly disclosed disturbance investigation may have an adverse impact on stakeholder confidence, regulatory relationship and market risk assessments. Senior executives now have a greater interest in understanding the nature of the disturbances arising at the operational level, and would be more likely to view them as part of the risk management responsibilities of operational personnel. The requirements of grid transparency in the reliability context derive from the statutes and regulatory authority that apply to the reliability regime. As many know, Section 215 of the Federal Power Act mandates requirements for grid transparency that were established because experience showed that voluntary compliance with electricity grid transparency standards by Grid Operators was not sufficient to prevent massive power grid blackouts. In this context, mandates for collection and use of information for disturbance analysis come from Regulation. Reporting disturbances in a manner that is treated as an obligatory or risk averse exercise rather than a genuine disclosure can potentially heighten exposure risks. Unwillingness to document in sufficient detail, drawing unsupportive conclusions

and failing to take prompt corrective measures can all serve to undermine the credibility of the reports with the regulators. Disciplined corporate governance practices together with the consistent application of a root cause analysis methodology and the appropriate recording of measures to correct deviations are important elements in enhancing corporate credibility. This factor highlights the link between disturbance reporting and enforcement exposure. Operations, compliance, engineering and executive oversight all have to work smoothly together to deal with major system events. Poor communication between these groups can lead to reliability and enforcement risk. As systems become more complex disturbances will increasingly involve interactions between generation, transmission, substations/ distribution and controls as well as market operation/enforcement. Enforcement of reporting will also be an increasingly multi-faceted issue. Disturbance reporting must be viewed as one component of a full risk management strategy rather than as a regulatory requirement. The compliance posture to a given disturbance is a function of the severity of the event and the response from the management of the

system. Reliability is not a goal of perfection. Rather it is a reflection of good governance, sound engineering analysis and appropriate corrective actions. Disturbance reporting is an essential element in achieving these attributes.

End-of-Chapter Summary

Disturbance reporting is a means to achieve regulatory visibility for an entity in a structured manner, which could impact the compliance risk posture. As a procedural rule EOP-004 does not directly impact compliance with reliability standards; however, the analysis of events in such reports could help an entity identify potential exposure to other reliability standards. The Oversight evaluation is a risk based assessment of the technical and governance aspects of the entity’s performance. The reliability of disturbance reports, its transparency and responsiveness significantly impacts the enforcement perception and the long term regulatory credibility.

Chapter 7

Interconnection-Wide Learning and Public Disturbance Analysis

The purpose of reporting disturbances under EOP-004 is to hold an entity accountable for any disturbances that occur at its facilities. However, the real value of the process is that it provides a means by which ERO and REs can learn about disturbances system-wide. A disturbance that occurs at one facility in the BES is unlikely to be limited to that facility. Rather, it will likely reveal underlying conditions in one form or another that could exist at other similar facilities elsewhere in the BES. Reporting the details of the disturbance provides a means by which the ERO and REs can aggregate knowledge about the phenomenon across multiple facilities. Relays are used for publicly disclosed Disturbance Reports that describe the consequences of major events such as blackouts, voltage fluctuations or equipment failures. This typically involves synthesis of data from a variety of sources (Relays, protection relay recordings, SCADA etc) that are used to reconstruct a detailed sequence of events occurring across all boundaries of the power system including performance of protection relays, description of voltage and frequency behavior and checks on coordinated operation of switchgear and other control devices. The Relays function for this application is not merely to aid in determining the cause of the event (i.e. to facilitate adherence to standards for immunity and performance) but is used also to investigate the structural adequacy of the grid. Disturbance Findings Publication The publication of disturbance findings serves multiple governance functions. In addition to serving as an archival function that records events of potential significance, it also feeds into the discussion of standard and provides the industry, interested parties, stakeholders and the public with a transparent record of events that are not minor, that are not infrequent, and that are not suppressed. The disclosure of major disturbances to the public contributes to building legitimacy for the reliability standards framework by assuring that such occurrences are not hidden or diminished. Grid-wide learning will require that disturbance reports can be compared across the Grid. The ability to compare disturbance reports across the grid will depend on common criteria for documentation,

criteria for determining when to submit reports, a common methodology for conducting root cause analysis and other related factors. If the reporting structure is not standardized, the ability to synthesize lessons learned from disturbances will be hindered and underlying vulnerabilities will remain dispersed and hard to determine. Reliability Coordinators play a key role in the overall learning process. Due to their broad situational awareness of the grid, their review of events often provide a more holistic

perspective after the fact. Close coordination between Reliability Coordinators, Transmission Operators, Balancing Authorities, and Generator Operators is needed to understand the sequence of events and accurately reconstruct an interconnection-wide occurrence. Disturbance analysis is moving rapidly into the dynamic system modeling age. Information derived from Phasor measurement units (PMUs) and high-resolution digital field recordings are allowing the detailed examination of power system oscillations, frequency excursions and voltage instability phenomena which can confirm assumptions inherent in planning and operational studies at the grid level. Synchrophasor data analytics for inverter based resources has significantly expanded the scope of power system analysis. Such as ride-through event analysis, blackout event analysis and relay interaction analysis which require physical and control algorithm information. Interconnection-level knowledge requires knowledge of the associated high-level performance characteristics. This effort may also identify common-mode vulnerabilities. An identical relay configuration was used in the three facilities in question. The documentation of this common configuration provides information to stations in the area of potential mutual impact should the relays fail in a similar manner. Results of the analysis were used in preparing a release for publication to Generation and Corporate Relations, along with recommended reliability improvements. These recommendations are not formal orders, but could be considered as suggestions for possible change in operating procedures, assumptions in reliability modeling or priorities in the maintenance program. Potential beneficiaries of the analyses could be other power companies, which may chose to improve their reliability position in line with the NBP findings. Interconnection-wide learning is also used to inform risk-based compliance monitoring activities. Persistent patterns of disturbances discovered during regional reviews may indicate potential reliability risks that warrant additional focus using oversight attention. The regional review learning is used to inform and guide the regulatory priorities going forward. Public disturbance analyses aim to differentiate accountability and blame. Investigations there focus on the behavior of the system and the underlying conditions that may have enabled those actions,

rather than on an individual’s culpability. This approach to analyzing these types of breaches supports open discussion of the events by all concerned parties, and is in line with the reliability culture premise of using these analyses to improve the system as a whole. Data quality is essential to institutional learning. This data should be as complete as possible, well analyzed and made available in an open transparent fashion. The EOP-004 was designed to act as a starting point for initial data. Additional efforts would be required to take the entity level data contained within an entity report and to derive an understanding at the interconnection level. The sum of this knowledge is used to adapt operational procedures and to update standards and regulatory bodies. The importance of structured disturbance documentation will grow as the BPS increasingly operates with more complex systems of distributed energy resources, advanced control systems, and changing marketbased dispatch conditions. Grid reliability at the regional level will continue to depend as much on the learning that can be extracted from historical system disturbances from one utility to another as on adherence to regional reliability

standards. The purpose of disturbance reporting was to link operational experience with systemic learning at the level of the institution. The value of the system is the fact that reporting on disturbances not only served the regulatory purpose of ensuring that all was well on the system but also served to spread knowledge of specific events occurring in one area of the system to other areas and indeed to other systems.

End-of-Chapter Summary

The Disturbance Reporting function helps to achieve learning across the Interconnection by enabling the synthesis of event data across Entities and Regions. Public disturbance analyses help to preserve the knowledge base of the industry, aid in the development of industry standards, and increase regulatory transparency. A disturbance reporting architecture defined in EOP-004 allows for the aggregation of lessons learned, identification of general systemic issues, and the prioritization of potential future risks to ensure the reliability framework remains adaptable.

Glossary

Glossary

Balancing Authority (BA) The Balancing Authority is the entity that coordinates the scheduled activities of generating resources in advance of time to provide system operating reserve and ensures that load interchange and generation are kept in balance within the Balancing Authority Area on an ongoing basis. In real time, the BA works to restore Interconnection frequency.

Bulk Electric System (BES), Definition from the Electric Reliability Organization (ERO): The generation resources, transmission lines, interconnections with other power systems, and associated equipment, primarily utilizing high voltage transmission such as transmission lines above 100 kV and utilizing systems generally operated at 100 kV or higher necessary for reliable operation of the interconnected electric energy transmission network.

Cascading – The uncontrolled successive loss of system elements caused by an initial disruption at any location.

Compliance Monitoring and Enforcement Program (CMEP), The program established by the Electric Reliability Organization and Regional Entities to monitor, assess, and enforce compliance with approved Reliability Standards.

Electric Reliability Organization (ERO) – The ERO is the organization certified by the Federal Energy Regulatory Commission (FERC) under Section 215 of the Federal Power Act to develop and enforce Reliability Standards for the Bulk Electric System.

Event Analysis The step-by-step examination of a reportable event to establish the sequence of events, determine possible causes and provide recommended corrections.

Federal Energy Regulatory Commission (FERC) - The federal agency that has jurisdiction over the interstate transmission of electricity and statutory authority to approve and enforce the Reliability Standards under Section 215 of the Federal Power Act.

Firm Load – The electric load that can be served under normal conditions and that is not interruptable except during emergency conditions.

Generator Operator (GOP) – The operator of the generating units and supplier of energy and Interconnected Operations Services.

Interconnection – A geographic area in which parts of the Bulk Electric System are electrically interconnected. This can include the Eastern Interconnection, the Western Interconnection, or the ERCOT Interconnection.

Loss of Firm Load – The interruption of electric service to customers that are not under contract to accept interruptions (for example, hospitals, water treatment plants, emergency pumps, etc.) due to a disruption on the generation or transmission system or an operational emergency.

Protection System: Protective relays, communication system, voltage and current transducers, station batteries, and control circuits that detect faults and isolate faulty equipment from the Bulk Electric System.

Regional Entity – A Regional Entity is a FERC-approved organization that delegates compliance monitoring and enforcement responsibilities within a defined geographic region.

Reliability Coordinator (RC) – The entity with the most far reaching authority that is responsible for the reliable operation of the Bulk Electric System within its Reliability Coordinator Area.

Reliability Standard – A FRCC-accepted or FERC-approved standard, rule or order that is enforceable and applicable to RELIABILITY FIRST CORP OF TEXAS (FRCT). Reliability Standard(s) are requirements developed and approved by the FERC under Section 215 of the Federal Power Act.

Reportable Disturbance: An event that occurs and is defined as a disturbance by criteria established in the Reliability Standard EOP-004, and requires notification and written reporting by the ERO and Regional Entity.

Root Cause The most basic condition or set of conditions which, if corrected, would eliminate the recurrence of a similar disturbing occurrence.

Section 215 A statutory provision of the Federal Power Act requiring mandatory and enforceable Reliability Standards for the Bulk Electric System.

Transmission Operator (TOP)– The entity responsible for the reliability of its Transmission System and for operating or directing the operation of transmission facilities.

Uncontrolled Separation – The unintended islanding of a portion of the Bulk Electric System resulting from system disturbance.

Voltage Collapse: Voltage instability that leads to a continuous and non-controllable drop in voltage magnitudes resulting in loss of load or system separation.

About the Author

About the Author

Rob Smith is a senior electric industry professional with over thirty years of experience across every major function of the North American Bulk Electric System. His work spans reliability coordination, transmission operations, regulatory compliance, and cybersecurity reliability.

Rob has worked directly in real-time grid operations as a Reliability Coordinator, Transmission Operator, and Power System Operator within RTO/ISO and utility control center environments. He has also held senior regulatory and oversight roles, including senior compliance auditor and subject matter expert for NERC Reliability Standards. In those roles he audited grid facilities for compliance with applicable standards, evaluated the adequacy of mitigation actions, supported the development of violation notifications and settlements as part of FERC-directed enforcement actions, and participated in risk based oversight of utility mitigation activities.

Rob founded Energy Compliance, Inc. to bring senior, regulator-side compliance authority to registered entities directly, without the layered staffing, billable-hour overhead, and generalist advice typical of larger consulting firms. Every Energy Compliance engagement is led by Rob personally.

About Energy Compliance, Inc.

About Energy Compliance, Inc.

Energy Compliance, Inc. is an independent consulting and advisory firm focused exclusively on electric reliability, cybersecurity reliability, and regulatory compliance for organizations connected to the North American Bulk Electric System.

Our work supports registered entities, including Generator Owners and Operators, Transmission Owners and Operators, Reliability Coordinators, Balancing Authorities, and Distribution Providers. We work across NERC Reliability Standards, FERC orders, RTO/ISO market participation rules, Regional Entity oversight, and state regulatory frameworks.

We do this work differently than larger consulting firms. Engagements are led by a single senior practitioner with regulator-side experience. We don’t staff for billable hours. We staff for outcomes. Our deliverables are written to be operationally executable and audit-defensible, not to manufacture activity. Where automation can replace manual work, we build the automation. Where senior judgment is required, the senior is in the room.

Energy Compliance is not affiliated with, sponsored by, or endorsed by the North American Electric Reliability Corporation, the Federal Energy Regulatory Commission, or any Regional Entity.

Services Provided

Our services are written to be clearly defensible. Operationally executable in real time. Audit-defensible at compliance review. Every deliverable is structured for the auditor’s question, not the consultant’s binder.

Energy Compliance services include, but are not limited to:

• NERC reliability and compliance advisory support
• Reliability governance and program assessments
• Registration and applicability analysis
• Operational and engineering reliability alignment
• Compliance program design and improvement
• Audit and enforcement support (non-advocacy)
• Mitigation planning and Self-Report development
• Training and executive briefings on reliability frameworks
• Regulator-perspective program reviews

Each engagement is scoped to the entity’s role, function, and bulk system impact.

ENERGY COMPLIANCE PROFESSIONAL REFERENCE

Rigorous Compliance. Defensible Programs. Energy Compliance, Inc. partners with registered entities on the institutional and technical questions that define strong reliability and cybersecurity programs, from classification through audit through enforcement response.

N ERC CO MP LIANC E S ENIO R ADV ISO RY Program support, interpretation, and audit Direct engagement on complex reliability preparation. questions.

I ND USTRY ENGAGEMENT AUD IT D EFENSE Standards development and working-group Notice of Penalty response and settlement participation. posture.

CONNECT WITH US Scan to visit

E N E RGY COMPL IAN CE , IN C. · EC-WP-600 · © 2026 · AL L RIGHTS RES E RV E D