Event Analysis
An event is defined as “an unwanted, undesirable change in the state of plants, systems or components that leads to undesirable consequences to the safe and reliable operation of the system.” Events can be avoided proactively or reactively. The combination of proactive and reactive methods is the best strategic approach for the identification and elimination of hidden organizational weaknesses and situations that can cause an event to occur.
Goals of the Event Analysis Program
Promoting Reliability
The principal goal of Texas Reliability Entity, Inc. (Texas RE) is to promote the reliability of the bulk power systems in North America. This goal is directly supported by:
- Evaluating bulk power system events.
- Understanding the underlying cause of events.
- Undertaking appropriate levels of analysis to determine the causes of the events.
- Promptly implementing corrective actions.
- Providing recommendations and lessons learned to the industry.
- Providing valuable feedback to the reliability standards development process, compliance enforcement, training and education, and reliability trend analysis efforts.
- Developing a culture of reliability excellence that promotes and rewards aggressive self-critical review and analysis of operations, planning, and critical infrastructure protection processes.
Successful event analysis relies on a collaborative approach through which registered entities, Regional Entities (RE), and NERC work together to achieve a common goal.
Key Ingredients
- Identify what transpired – sequence of events;
- Understand the root causes of events;
- Identify and ensure timely implementation of corrective actions;
- Develop and disseminate recommendations and valuable lessons learned to the industry;
- Develop the capability for integrating risk analysis into the event analysis process;
- Forward key results to facilitate enhancements in and support of the various NERC programs and initiatives.
Top of Page
Registered Entity Requirements
| 1 |
Draft within 5 business days, sent to applicable Regional Entity for review. Final Report within 10 days. |
Not required |
Within 30 business days (if applicable) |
10 business days following receipt of Brief Report |
| 2 |
Draft within 5 business days, sent to applicable Regional Entity for review. Final Report within 10 days. |
(If requested) Within 30 business days of the event |
Within 30 business days |
30 business days following receipt of EAR |
| 3 |
Draft within 5 business days, sent to applicable Regional Entity for review. Final Report within 10 days. |
Within 60 business days of the event |
Within 60 business days |
30 business days following receipt of EAR |
| 4 |
Draft within 5 business days, sent to applicable Regional Entity for review. Final Report within 10 days. |
Within 180 business days of the event |
Within 180 business days |
60 business days following receipt of EAR |
| 5 |
Draft within 5 business days, sent to applicable Regional Entity for review. Final Report within 10 days. |
Within 180 business days of the event |
Within 180 business days |
60 business days following receipt of EAR |
Data Holds
As Registered Entities begin to analyze events, they must retain all data and information relative to the event in order to perform the detailed analysis. Regional Entities will formally send a Data Hold Retention Notice (Appendix H) for events in Category 2 or higher. Data holds will have an end date corresponding to the closing of the event or a timeframe identified in the request from the Regional Entity for the data hold.
Top of Page
Event Contact Information
Event reports should be sent to rapa@texasre.org 
.
Comments on the ERO Event Analysis Process Field Test should be sent to information@texasre.org .
Top of Page