1 / 38

EOP-011-1 Project 2009-03 Emergency Operations

EOP-011-1 Project 2009-03 Emergency Operations. Regional Outreach WECC ISAS Meeting August 20, 21 , 2014. Agenda. Background and overview FERC Directives Five Year Review Attachment 1 of EOP-011-1 and BAL-002 coordination Project moving forward Discussion and recommendations.

Télécharger la présentation

EOP-011-1 Project 2009-03 Emergency Operations

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. EOP-011-1Project 2009-03 Emergency Operations Regional Outreach WECCISASMeeting August 20, 21, 2014

  2. Agenda • Background and overview • FERC Directives • Five Year Review • Attachment 1 of EOP-011-1 and BAL-002 coordination • Project moving forward • Discussion and recommendations

  3. Project 2009-03 Background • Nov. 11, 2010 – NERC SC authorized moving the Project 2009-03 Emergency Operations SAR forward to standard drafting and appointed a SAR Drafting Team. • Project 2009-03 involved reviewing and revising • EOP-001-0 • EOP-002-2 • EOP-003-1 • IRO-001-1 • Project 2009-03 was placed on hold in late 2010/early 2011 due to NERC Standards prioritization effort.

  4. Project 2009-03 Background • April 22, 2013 – EOP Up for 5 year Review • NERC SC appointed eight SMEs to serve on the Emergency Operations Five-Year Review Team (EOP FYRT) to review and make recommendations regarding: • EOP-001-2.1b • EOP-002-3.1 • EOP-003-2 • August 6–September 19, 2013 – The EOP FYRT developed a set of recommendations which were posted for a 45-day comment period.

  5. Project 2009-03 Background • October 17, 2013: • NERC SC accepted the recommendations of the EOP FYRT • Appointed a drafting team • Authorized posting the SAR developed by the EOP FYRT • November 6–December 5, 2013: SAR posted for comment period.

  6. Project 2009-03 Background • EOP-011-1 was drafted by the Emergency Operations Standard Drafting Team (EOP SDT) through the examination and consideration of: • Applicable FERC directives • EOP FYRT recommendations • Independent Expert Report • Paragraph 81 criteria • SAR • EOP-011-1 was posted for informal comment period so industry could review and help guide the current body of work.

  7. Key Milestones • The informal comment period for EOP-011-1 was open until Friday, April 28. • The EOP SDT held a drafting team meeting May 13–15 to review comments and further develop the EOP-011-1 standard. • EOP-011-1 is now posted for the first formal comment period. • Submittal to the Board and subsequent regulatory filing is targeted for the end of 2014 or early 2015.

  8. EOP Standard Drafting Team

  9. Five-Year Review Projects

  10. Five-Year Review Projects • Five-Year Review Overview • Part of NERC’s broader objective to transition to a clear, concise, and stable body of world-class, high-quality reliability standards • Five-year reviews must be conducted on current standards that are due for assessment and have not been revised in recent standards development projects • Required by ANSI-accredited Reliability Standards development process Industry Webinar: Five-Year Review Projects Overview 05/2013

  11. Five-Year Review Projects • Five-Year Review Objective • Determine whether the Reliability Standard should be: • (1) affirmed; • (2) revised; or • (3) withdrawn. • Elements of the Five-Year Review • Outstanding FERC directives • Stakeholder requests for clarity or revision • Results-Based Standards (RBS) principles • Paragraph 81 principles EOPFYRT recommendations were submitted to Standards Committee on September 19, 2013 and accepted by SC in October.

  12. UVLS and EOP Project Coordination

  13. EOP and UVLS Project Coordination • Project 2009-03 EOP consolidates and replaces EOP-001-2.1b, EOP-002-3.1, and EOP-003-2 with EOP-011-1. • Project 2008-02 UVLS consolidates and replaces PRC-010-0, PRC-020-1, PRC-021-1, and PRC-022-1 with PRC-010-1. • The respective performance formerly required by EOP-003-2, Requirements R2, R4, and R7 is reflected in PRC-010-1. • The EOP and UVLS projects are progressing simultaneously to properly align legacy standard retirements and revised standard implementations. April 10, 2014 EOP and UVLS Joint Webinar

  14. Additional Information • Please contact the respective NERC Standards Developers for more information, to schedule an outreach session, or to be added to a project’s email distribution list: • Project 2009-03 EOP: Laura Anderson at Laura.Anderson@nerc.net • Project 2008-02 UVLS: Erika Chanzes at Erika.Chanzes@nerc.net

  15. Project 2009-03 – EOP-011-1 Conflict with BAL 002 – use of reserves

  16. Attachment 1 – EOP and BAL-002 Conflict with BAL 002 on use of Reserves in EEA’s Attachment 1 has been changed. • Use of OR was removed from EEA 2 and added to EEA3 • At EEA 2 BA is still able to meet load and maintain reserves • At EEA 3 unable to meet load without dipping into reserves. Utilizing reserve margins is preferable to dropping load to maintain reserves. BAL 002 team will be changing their new standard to align with EOP 011

  17. Project 2009-03 – EOP-011-1 Drafting the new Standard

  18. EOP-011-1 Definition Revision Proposed revised definitions: Energy Emergency - A condition when a Load-Serving Entity or Balancing Authority has exhausted all other resource options and can no longer meet its expected Load obligations. This defined term was revised to provide clarity that an Energy Emergency is not necessarily limited to a Load-Serving Entity.

  19. EOP-011-1 Definition Revision This defined term, or variations of it, is also used in the instances below. The EOP SDT does not believe that the proposed revisions change the reliability intent of these standard or definitions. • BAL-002-WECC – Contingency Reserve • IRO-005-3.1a — Reliability Coordination — Current Day Operations • MOD-004-1 — Capacity Benefit Margin • INT-004-3 – Dynamic Transfers • Defined term Emergency Request for Interchange

  20. EOP-011-1 Purpose Statement Purpose of the Standard: To mitigate the effects of operating Emergencies by ensuring each Transmission Operator and Balancing Authority has developed Emergency Operating Plans, and that those plans are coordinated within a Reliability Coordinator Area.

  21. EOP-011-1 Functional Entities Applicable to these Functional Entities: • Balancing Authority • Transmission Operator • Reliability Coordinator • Load Serving Entity has been dropped in EOP 011

  22. EOP-011-1 Requirement R1 R1. Each Transmission Operator shall develop, maintain and implement a Reliability Coordinator-approved Emergency Operating Plan to mitigate operating Emergencies on its Transmission System. At a minimum, the Emergency Operating Plan shall include the following elements: [Violation Risk Factor: High] [Time Horizon: Real-Time Operations, Operations Planning] (The list following was taken from the original attachment 1 of EOP 1 for those elements deemed important for TOP’s)

  23. EOP-011-1 Requirement R1 1.1. Roles and responsibilities to activate the Emergency Operating Plan; 1.2. Strategies to prepare for and mitigate Emergencies including, at a minimum: 1.2.1. Notification to the Reliability Coordinator, to include current and projected System conditions, when experiencing an operating Emergency; 1.2.2. Controlling voltage; 1.2.3. Cancelling or recalling Transmission and generation outages; 1.2.4. System reconfiguration; 1.2.5. Requesting the redispatch of generation; 1.2.6. Operator-controlled manual Load shedding plan coordinated to minimize the use of automatic Load shedding; 1.2.7. Mitigation of reliability impacts of extreme weather conditions; and 1.3. Strategies for coordinating Emergency Operating Plans with impacted Transmission Operators and impacted Balancing Authorities.

  24. EOP-011-1 Requirement R2 R2. Each Balancing Authority shall develop, maintain and implement a Reliability Coordinator-approved Emergency Operating Plan to mitigate Capacity and Energy Emergencies. At a minimum, the Emergency Operating Plan shall include the following elements: [Violation Risk Factor: High] [Time Horizon: Real-Time Operations, Operations Planning] (again, taken from the original attachment 1 of EOP 1 for those elements deemed important for BA’s) 2.1. Roles and responsibilities to activate the Emergency Operating Plan; 2.2. Notification to the Reliability Coordinator, to include current and forecasted conditions, when experiencing a Capacity Emergency or Energy Emergency; 2.3. Criteria to declare an Energy Emergency Alert, per Attachment 1;

  25. EOP-011-1 Requirement R2 2.4. Strategies to prepare for and mitigate Emergencies including, at a minimum: 2.4.1. Generating resources in its Balancing Authority Area: 2.4.1.1. capability and availability; 2.4.1.2. fuel supply and inventory concerns; 2.4.1.3. fuel switching capabilities; 2.4.1.4. environmental constraints. 2.4.2. Voluntary Load reductions; 2.4.3. Public appeals; 2.4.4. Requests to government agencies to implement their programs to achieve necessary energy reductions; 2.4.5. Reduction of internal utility energy use;

  26. EOP-011-1 Requirement R2 2.4.6. Customer fuel switching; 2.4.7. Use of Interruptible Load, curtailable Load and demand response; 2.4.8. Operator-controlled manual Load shedding plan coordinated to minimize the use of automatic Load shedding; and 2.4.9. Mitigation of reliability impacts of extreme weather conditions. 2.5. Strategies for coordinating Emergency Operating Plans with impacted Balancing Authorities and impacted Transmission Operators.

  27. EOP-011-1 Requirement R3 R3. Each Reliability Coordinator shall approve or disapprove, with stated reasons for disapproval, Emergency Operating Plans submitted by Transmission Operators and Balancing Authorities within 30 calendar days of submittal. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning ]

  28. EOP-011-1 Requirement R4 R4. Each Reliability Coordinator that receives an Emergency notification from a Transmission Operator or Balancing Authority shall notify, as soon as practical,  other impacted  Reliability Coordinators, Balancing Authorities and Transmission Operators. [Violation Risk Factor: High] [Time Horizon: Real-Time Operations]

  29. EOP-011-1 Requirement R5 R5. Each Reliability Coordinator that has a Balancing Authority experiencing a potential or actual Energy Emergency within its Reliability Coordinator Area shall initiate  an Energy Emergency Alert, as detailed in Attachment 1. [Violation Risk Factor: High] [Time Horizon: Real-Time Operations]

  30. Project 2009-03 – EOP-011-1 FERC Directives

  31. FERC Directives FERC Directives In the development of the proposed EOP-011-1 reliability standard, the EOP SDT addressed the outstanding FERC directives in Order No. 693 related to Emergency Operations and planning.

  32. FERC Directives EOP-001-1 Emergency Operations Planning: • Include reliability coordinators as an applicable entity. • Consider Southern California Edison’s and Xcel’s suggestions in the standard development process. • Clarify that the 30-minute requirement in requirement R2 to state that Load shedding should be capable of being implemented as soon as possible but no more than 30 minutes. • Includes definitions of system states (e.g., normal, alert, emergency), criteria for entering into these states. And the authority that will declare them. • Consider a pilot program (field test) for the system states proposal. • Clarifies that the actual emergency plan elements, and not the “for consideration” elements of Attachment 1, should be the basis for compliance.

  33. FERC Directives EOP-002-2 Capacity and Energy Emergencies: • Address emergencies resulting not only from insufficient generation but also insufficient Transmission capability, particularly as it affects the implement of the capacity and energy Emergency plan. • Include all technically feasible resource options, including demand response and generation resources.

  34. FERC Directives EOP-003-1 Load Shedding Plans: • Develop specific minimum Load shedding capability that should be provided and the maximum amount of delay before Load shedding can be implemented based on overarching nationwide criteria that take into account system characteristics. • Require periodic drills of simulated Load shedding. • Consider comments from APPA and ISO-NE in the standards development process.

  35. FERC Directives • Order No. 693 at P 573 “Demand response covers considerably more resources than interruptible load. Accordingly, the Commission directs the ERO to modify the Reliability Standard to include all technically feasible resource options in the management of emergencies. • Order No. 693 at P 595: “The Commission directs the ERO to address the minimum load and maximum time concerns of the Commission through the Reliability Standards development process.” • Nick Henery (FERC Staff participating in SDT meetings) feels the SDT has adequately covered the Directives in our process.

  36. Attachment 1 – EOP and BAL-002 Current Status Industry Outreach - ongoing Posted in early July for first “formal” comment and balloting. Comments accepted through August 15 Ballot Pool Registration open through July 31 Balloting August 5 through August 15 (40% approval) Comment Review and further refinement of the Standard EOPDT meeting August 27 – 29.

  37. Viewing Webinars

  38. Discussion and Questions

More Related