1. 1 MSRATF Update to TSS (Modeling SPS and RAS Ad Hoc Task Force) Scope of Work Approval January 25, 2013 Joe Seabrook Puget Sound Energy

2. 2 Background In May of 2012, FERC and NERC issued a joint report on the September 8, 2011 Southwest Blackout Event calling for improved planning. It recommended that entities throughout WECC identify and plan for external contingencies that could impact their systems and internal contingencies that could impact their neighbors systems, and expand entities external visibility in their models through, for example, more complete data sharing.

3. 3 Purpose To achieve WECC wide visibility of contingencies in planning and operating an ad-hoc task force was created by TSS to facilitate developing and/or implementing models for RAS, relays and contingency definitions in WECC base cases, in BCCS, and in cases that are consistent with the WSM. This task force will also coordinate with the RAS and Protective Systems Modeling Oversight Task Force (RPSOTF).

4. 4 Purpose - Discussion September 8, 2011 outage report: –Contingencies are not shared between utilities –Relay models / data are not shared between utilities –RAS models are not shared between utilities Past methods for sharing are peer to peer –Must know what to ask, who to ask, provider have time, interest and approval, and to then do this with each case. Has not worked well

5. 5 Ultimate Goal Statement To simulate faults in power flow and transient stability by specifying the fault location and fault type on facilities like buses or branches. –Includes TPL standard faults; balanced and unbalanced, normally cleared, stuck breaker, double circuit, adjacent, extreme and reclosing –RAS and Relays models would trip appropriate breakers at appropriate times –Data would be provided in cases for both near and long term planning and operating –Fault descriptions are resident in (or with) WECC posted cases

6. 6 (Major Changes coming to Town) Base Case Coordination System (BCCS) –Starts out with Bus Node Topology –Add Contingency Definitions (based on Bus Node) –Our programs will exchange data with BCCS Breaker Node Topology –Used in Westwide System Model (WSM) –Primary and Backup Breakers Defined –New Contingency Definitions (w/ Breaker Node) Specify the fault type and location

7. 7 Steps to Get There – 3 Phases Phase 1 – Existing and New Models for RAS, Relays and Contingency Definitions Phase 2 – Base Case Coordination System –Includes sequence data and automatic relay parameter population Phase 3 – Breaker-Node Topology –Build into BCCS, - Compare with WSM –Update Contingency Definitions

8. 8 RAS, Relays and Contingency Definitions Obtain RAS Models (or SPS) –Event Driven –Condition Based Obtain Relay Models –Line, Transformer, Bus, Generator –Primary, Backup, and Reclosing Define Contingencies – B, C & D –Bus topology –Breaker/node topology

9. 9 Activities Phase 1 - Existing and New Models 1.Catalog existing RAS and SPS. Request owners to provide functional descriptions and any available files sufficient to model existing RAS and SPS. Ensure each simulation program (GE PSLF, Siemens PSS/E, PowerWorld) is represented. Due: January 31, 2013 2.Identify existing relay models that are provided by PSLF, PSS/E, and PowerWorld. Due: January 31, 2013 3.Develop standard contingency definition requirements and templates for power flow (PF) and transient stability (TS). Coordinate with each simulation program vendor to ensure common expectations and requirements to manage definitions by bus, owner, zone and area. Due: January 31, 2013

10. 10 Activities Phase 1 - Existing and New Models 4.Identify and recommend to System Review Work Group (SRWG) and Modeling & Validation Work Group (MVWG) any PF and TS RAS model development still needed for each program. Identify and write protective system requirements of these relays. Due: March 31, 2013 5.Begin work to develop RAS and relay models that currently do not exist in PSSE, PSLF, and PowerWorld. Due: March 2013 6.Develop request for facility owners to provide sequence data. Due: April 2013

11. 11 Activities Phase 1 - Existing and New Models 7.Work with program vendors to map and validate available protective system models. Develop and validate new models where needed. Due: May 2013 8.Model existing relays in WECC base cases that are in member systems and that have available power flow models. Due: June 2013 9.Facilitate collecting data of model parameters, contingency definitions by entities and distribution with WECC base cases. Due: June 2013 10.Develop and test conversion routines to transfer data between the three programs for power flow and transient stability models. Due: September 2013

12. 12 Activities Phase 1 - Existing and New Models 11.Begin identifying RAS, relays and contingency definitions to be included in the Base Case Coordination System (BCCS). Due: October 2013 12.Coordinate RAS, relay and contingency definition needs with WSM development. Due: November 2013 13.Throughout the process, update data input and user guides, such as the Data Preparation Manual (DPM), and provide training and educational tools. Due: Revise, as necessary, at each SRWG meeting.

13. 13 Activities Phase 2 - Base Case Coordination System 14.Implement contingency definitions in BCCS for PF & TS. Due: January 2014 15.Bring sequence data from CAPE, ASPEN, etc. into BCCS. Due: March 2014 16.Complete development of RAS and relay models. Due: August 2014 17.Include models in simulation programs. Due: September 2014 18.Bring relay data from CAPE, ASPEN, etc. into BCCS. Ensure this data can be used in each simulation program. Due: December 2014

14. 14 Activities Phase 3 – Breaker-Node Topology 19.Build breaker-node topology into BCCS and for all three simulation programs that is consistent with the WSM. Ensure read and write capabilities. Due: August 2015 20.Convert and update contingency definitions to utilize breaker-node topology. As needed, update each simulation program for breaker node topology and updated contingency definitions. Due: June 2015

15. 15 Membership Technical Studies Subcommittee (TSS) and its work groups RAS and Protection Systems Modeling Oversight Task Force (RPSOTF) Remedial Action Scheme Reliability Subcommittee (RASRS) Software Vendors Other Subject Matter Experts (SMEs). Decision Making in MSRATF Decisions will be made by consensus agreement. Proposals, idea and value sharing, and polls may be used for everyone to understand this agreement (and lack of).