1 / 10

MSRATF Update to TSS (Modeling SPS and RAS Ad Hoc Task Force) Activities August, 2013

MSRATF Update to TSS (Modeling SPS and RAS Ad Hoc Task Force) Activities August, 2013. Joe Seabrook Puget Sound Energy, Inc. MSRATF Engagement. MSRATF formed in August by TSS upon assignment from PCC Chair – Responsive to Sep 8, 2011 event

ziarre
Download Presentation

MSRATF Update to TSS (Modeling SPS and RAS Ad Hoc Task Force) Activities August, 2013

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. MSRATF Update to TSS(Modeling SPS and RAS Ad Hoc Task Force)ActivitiesAugust, 2013 Joe Seabrook Puget Sound Energy, Inc.

  2. MSRATF Engagement • MSRATF formed in August by TSS upon assignment from PCC Chair – Responsive to Sep 8, 2011 event (Perform contingency events in WECC cases across the system with a few mouse clicks) • Details in Needs Statement, Scope Statement approved by PCC • Includes vendor participation by GE, Siemens/PTI, PowerWorld, V&R, and PowerTech • WECC groups helping include TSS, RPSOTF, MVWG, SRWG, RASRS, Relay WG • WECC web site for documents: WECC > Committees > Standing Committees > PCC > TSS > Documents > MSRATF Documents http://www.wecc.biz/committees/StandingCommittees/PCC/TSS/Shared%20Documents/Forms/AllItems.aspx

  3. MSRATF Meetings • Since August 2012, 6 face-to-face meetings and many WebEx sessions • Formed three subgroups with vendor representation in each group • RAS • Relays (Modeling Sequence Component Networks) • Contingency Definitions (Breaker Node Topology) • Additional • Breaker Node Topology • Modeling Sequence Component Networks

  4. RAS Subgroup James O’Brien (BPA) • Developing a Generic RAS specification • MSRATF approved on Tuesday 8/7 • Seeking MVWG comment and approval With WebEx (8/26 at 2:00 Mt time) • Seeking TSS comment and approval With WebEx (9/5 at 2:00 Mt time) • Donald Davies will be emailing to you this week.

  5. RAS Subgroup James O’Brien Colstrip owners are developing an ATR specification PAC is beginning to develop a Bridger RAS specification Jason Wilson presented an overview of the Bridger RAS 5

  6. RAS Subgroup James O’Brien • To demonstrate responsiveness to 9/2011 Outage Report recommendations we are asked to post and share Conditional RAS model files we currently use: • Send RAS files to Enoch by 8/21 to post • Under 2013 Base Cases, folder at bottom of web page: Contingency and Remedial Action Scheme Files (Various Formats) • Template for RAS descriptions also being developed for later, starting with WAPS

  7. Relays Subgroup Amos Ang (SCE) • Amos is new chair, taking over for Tracy • 3Φ Over-Current, non-directional Relays • MVWG approved existing relay models for WECC • MSRATF & MVWG approved spec for 3Φ, non-directional, curves and equations Over-Current relay (use for RAS) • Power Flow (steady-state) & Transient Stability (instantaneous and inverse time) • Seeking TSS approval, then vendors will develop and jointly validate with WECC

  8. Relays Subgroup Amos Ang • TSS Motion: Approve generic specification for 3Φ, non-directional, curves and equations Over-Current relay!! • Next – Generic 3Φ Distance relay • After that – 3Φ, differential relays • Soon - 3Φ, directional component to overcurrent relay • Then – Model unbalanced sequence networks in WECC planning cases • And – 1Φ Directional Over-Current and Distance relays

  9. Contingency Definitions Subgroup Jonathan Young (CG) • Developed a Contingency Definitions generic specification • Contingency file will be common format, read (translated) by all programs • Editing, sorting, selecting would be done within the programs • Seeking TSS approval, then vendors will develop and jointly validate with WECC

  10. Contingency Definitions Subgroup Jonathan Young • TSS Motion: Approve generic specification for Contingency Definitions!! • Developing specification to import / export in Contingency Definitions in BCCS • Beginning to develop Breaker-Node Topology for WECC planning cases • Explore changes to contingency definitions and relay models (bus / branch)

More Related