Coordinate Operations Standard

1. Coordinate Operations Standard Jason Shaver Standard Drafting Team Chair September 29, 2005

2. Presentation Overview • Proposed Standards • Key Concepts Supporting Standards • Key Requirements • V0 Retirements • Effective Dates • Questions

3. Coordinate Operations Standards: • IRO-014 • Procedures, Process or Plans to Support Coordinate Between Reliability Coordinators • IRO-015 • Notification and Information Exchange Between Reliability Coordinators • IRO-016 • Coordination of Real-Time Activities Between Reliability Coordinators

4. Key Concepts Purpose & Scope • Ensure RC’s operations are coordinated such that there’s no adverse impact on other RCs • Preserve the reliability benefits of interconnected operations • Focus solely on RC to RC coordination

5. Key Concepts: Build on Other Standards • Other Standards Require: • Each RC must be Certified • Each RC must have procedures, processes & plans for its own area • Each RC must monitor & direct others to protect its own area

6. Key Concepts:Require RC to RC Cooperation • Agree to take actions under specified conditions (documented in procedures, processes, plans) • Exchange information • Notify others of impactive conditions or events • Coordinate actions

7. IRO-014Procedures, Processes, Plans • Ensure documents address all required topics • Have agreement from those who will take actions • Have latest version of each document available to system operators (includes those developed by other RCs) • Company-specific version of documents developed by other RCs may be developed to support (not replace) an RC to RC document • Available to system operators • Reference source document • Support source document

8. IRO-014Procedures, Processes, Plans Documents that require notification, information exchange or coordination involving multiple RCs • ‘Impactive’ operating scenarios • Other activities: • Communication and real-time notifications • Energy and capacity shortages • Outage information • Voltage control • Information exchanged to support reliability assessments

9. IRO-015 Notifications & Information Exchange • Follow approved procedures: • Notify other RCs of impactive issues • Participate in agreed-upon conference calls and other communications forums • Provide reliability-related information upon request

10. IRO-016Coordination • RC that identifies a problem notifies impacted RCs • RCs involved agree on problem, solution, actions –document actions & notify others • If RCs disagree – each re-evaluates conflicting information, takes action to preserve RC Area and Interconnection, documents actions & notifies others

11. Blackout Findings: • Need to communicate emergency conditions to neighbor systems • These standards: • Require a procedure (agreed-upon with other RCs) for making notifications • Require following procedure in making notifications of anything ‘impactive’ to another RC’s Area • Require participation in agreed-upon conference calls and other communications forums

12. Implementation Plan – Revise V0 • COM-002 Communications and Coordination • EOP-002 Capacity and Energy Emergencies • IRO-003 RC – Wide Area View • IRO-004 RC – Operations Planning • IRO-005 RC – Current Day Operations • TOP-005 Operational Reliability Information

13. COM-002Communications & Coordination • Revise/retire requirements R2., R2.1, R2.2, R2.3 for RC to relay information to other RCs for a select set of scenarios • New standards require RCs to relay information to one another for a wider scope of scenarios

14. EOP-002 Capacity & Energy Emergencies • Retire/revise requirements R2 and R4 for RC to implement its capacity and energy emergency plan & inform other RCs • New standards require RCs to coordinate the development and implementation

15. IRO-003 RC – Wide Area ViewIRO-005 Current Day Operations • Retire/revise requirements (IRO-003 R2 and IRO-005 R11) to notify neighboring RC of operational concerns in the neighboring RC Area • New standards require notification and cooperation in resolving the operational concern

16. IRO-004 RC – Operations Planning • Retire requirement R6 for RC to initiate a conference call if warranted based on a reliability analysis • New standards require RCs to initiate conference calls for a wider array of scenarios

17. IRO-004 - RC – Operations Planning • Modify the RCs requirements to issue alerts (IRO-004 R7 and IRO-005 R15) • New Standards require notifications for a wider array of scenarios – alerts may not be practical for all situations – new Standards don’t reference a specific tool

18. IRO-005 RC – Current Day Operations • Retire part of R7 that requires the RC to participate in NERC hotline discussions • New Standards require participation in a wider array of communications for a more specific set of scenarios – new Standards don’t reference a specific tool

19. IRO-005 RC – Current Day Operations • Retire part of R9 that requires the RC to coordinate with other RCsto develop action plans for exceeding limits and to coordinate outages • New Standards require coordination be agreed upon in advance and then coordinated per agreement for a wide array of scenarios, including limits and outages

20. IRO-005 RC – Current Day Operations • Retire parts of R12 that require the RC to be aware of the impact of a special protection system on inter-area flows • New Standards require the RCs to have procedures that address issues in one RC Area that may have an adverse reliability impact on other RC Areas

21. TOP-005 Operational Reliability Information • Retire requirement (R5) for the RC to share data needed for reliability assessments and coordination of operations • New Standards require coordination be agreed upon in advance and then coordinated per agreement for a wide array of scenarios, including coordination of info needed for reliability assessments

22. Effective Dates • 1st Ballot Oct 4 – 13, 2005 • 2nd Ballot Oct 21-31, 2005 • BOT Adoption Nov 1, 2005 • Effective Nov 1, 2006 • RCs have 1 full year to become compliant

23. Questions