WECC Board of Directors April 21-23, 2004 Seattle, Washington WECC Procedure for Reporting of System Events Disturbance Reports Rod Maslowski OC Vice Chairperson Pacific Gas and Electric Company

2 Overview Reporting trigger levels Disturbance report requirements Follow-up process

3 WECC Reporting Trigger Levels Level 1 (most severe) – System separation – System island – Generation loss greater than 2000 MW if it is a precipitating factor of a larger event

4 WECC Reporting Trigger Levels Level 2 (moderate severity) – Loss of firm load greater than 300 MW for larger systems or major damage – 200 MW or 50% for smaller systems – Voltage ±10% – Damage to equipment caused by acts of nature or sabotage – Frequency excursion

5 WECC Reporting Trigger Levels Level 3 (least severe) – Operating outside of MORC or accordance with operating procedures without taking corrective action – Unusual misoperation of equipment – Attempted physical or cyber sabotage with the intent to disrupt service – Abnormal system conditions that might be encountered

6 Other Reports Abnormal and emergency events – Reliability Coordinator RAS failure/misoperation

7 Member Reporting Requirements Same day reporting required Coordinate with Reliability Coordinator and other systems Preliminary report requirements – Describe events – Generation, lines, customers/load affected – UV, UF, RAS tripping – Restoration Typically 1-2 pages, typically reports per year (2004 YTD = 6) No approvals requested

8 Follow-up Disturbance Reporting Abbreviated or detailed reports OC and CMOPS chairs, WECC staff, WECC CEO collaborate on required report level – System impacts – Unique or unusual problems – Publicity and external interest

9 Abbreviated Report Ad Hoc Task Force investigates and prepares report – Led by system entity in which event occurred – Impacted neighboring systems invited to participate – Relay protection personnel and Reliability Coordinator involved Typically 3-5 pages, reports per year (2004 YTD = 0) Report completed within 6 weeks of event occurrence

10 Abbreviated Report Requirements Describe event Lines, load, customers affected Frequency and voltage excursions – Frequency below 59.6 – Voltage dip greater than 20% Restoration and returning system to normal Conclusions (statement of finding) and corresponding recommendations (required actions) – Assess performance with established operating criteria Performance Evaluation Checklist – 15 event categories (facilities, relaying, personnel, etc.) – Contribution to event and explanatory comments

11 Abbreviated Report Approved by Disturbance Task Force and CMOPS FYI to OC, unless of regional significance Available to WECC members, NERC, DOE, FERC, other utilities Summary provided when requested by others if approved by lead organization

12 Detailed Report Ad Hoc Task Force investigates and prepares report – TF chair from outside system where event occurred – Relay WG and Reliability Coordinator included on TF – Neighboring and impacted systems participate Typically pages, plus attachments, 0-2 reports per year (2004 YTD = 0) Report completed within 8 weeks of event occurrence (depending on severity)

13 Detailed Report Requirement Introduction – Describe event – TF participants – Cause and impact of event Conclusions and recommendations – Assess performance with established operating criteria – Must be a conclusion for each recommendation

14 Detailed Report Requirement Conditions prior to the event – Generation and T-line status – Interchange summary – Key voltages – Abnormal system conditions Description of event – Initiating event – Loss of generation and/or transmission – Voltage and frequency excursions – Customers and load affected – Performance of protection schemes – Restoration

15 Detailed Report Requirement Sequence of events – Chronological listing of relevant key actions Exhibits – Diagrams, maps, charts to support report Performance Evaluation Checklist – 15 event categories (facilities, relaying, personnel, etc.) – Contributions to event and explanatory comments

16 Detailed Report Board approval required, following Disturbance TF, CMOPS, and OC approval Available to WECC members, NERC, DOE, FERC, and other utilities Summary provided when requested by others if approved by lead organization

17 Learning and Improving Following Events Review and discussion with other members Follow-up on recommendations (corrective actions) – Tracked via WECC disturbance log – Updated 3 times a year – Managed by CMOPS – Currently 34 active items on log Disturbance Log – Being reviewed by NERC as an industry best- practice

18 In Summary Reporting – Timely and thorough – Allows for learning by others – Corrective actions identified and addressed Opportunities for Improvement – Completion of recommendations – Increasing trend of abbreviated reports