1 MSRATF Update to TSS (Modeling SPS and RAS Ad Hoc Task Force) May 15, 2013 Joe Seabrook Puget Sound Energy

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 Purpose To achieve WECC wide visibility of contingencies in planning and operating. –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 –Throughout program platforms used by planners in WECC This task force will also coordinate with the RAS and Protective Systems Modeling Oversight Task Force (RPSOTF).

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 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 –Available on programs used by planners in WECC

6 Steps to Get There – 3 Phases Ph 1 – Existing and New Models for –RAS, –Relays, and –Contingency Definitions Ph 2 – Base Case Coordination System –Includes fault sequence data Ph 3 – Breaker-Node Topology –Build into BCCS –Compare with WSM

7 RAS Writing RAS Specification –Event Driven & Condition Based –Power Flow then Transient Stability Had presentations by 3 vendors on current capabilities and future vision Will engage specific response by vendors at next meeting

8 Relays – Inverse Time Over Current Seeking approval of existing 3-phase relays –Existing for two vendors are curve based –Existing for third vendor is both curve and equation based Preparing generic specification for 3-phase –Is both curve and equation based –Send to MVWG 2 weeks before their meeting Data from relays is generally equation based –Equation based faster & fewer errors than curve

9 Relays – Distance / Impedance Will seek approval of existing 3-phase relays later in summer –Existing for two vendors are different but similar Will write specification for generic relay with features still needed

10 Contingency Definitions Writing specification for criteria and extreme faults (to cover faults required by standards) Could be used to develop (1) A common format, or (2) BCCS contingencies data base Exploring the BCCS data base option –Contingencies managed in BCCS –Written by a contractor –Could be used in the long term –Program vendors provide round trip conversion to the contingency processor of their choice

11 Fault – Sequence Data (MOD B) Network Sequence Data in CAPE, Aspen, planning programs (negative sequence for branches, transformer tertiary and connections, line mutual coupling –Update bus numbers, device IDs –Export to planning program –Create equivalents at boundaries as needed –Automate changes in protection program for future updates (Demonstrated at MSRATF meeting)

12 Breaker Node Continental interest to move planning models from Bus/Branch to Breaker Node NERC paper Proposal for Development and Use of a Single Node-Breaker Topology Representation for Off-line and Real-time Study Models