Key Initiatives September 29, 2015 RC Users Group

Transcription

1 Key Initiatives September 29, 2015 RC Users Group

2 Data Sharing Michelle Mizumori

3 Data Sharing Developing revised Universal Data Sharing Agreement (UDSA) Major Changes from previous UDSA: o Addition of WECC o Addition of Natural Gas Pipelines for certain data o Process for sharing data with third parties o Clean-up throughout Several open issues in discussion For more information, click HERE 3

4 Data Sharing Timeline 4 Aug 20 First Draft UDSA posted o Aug 20-Sep 21 Comment Period Sep 9-10 Board meeting discuss first draft Oct 5 Face to Face meeting (Portland) Oct 12 Second draft UDSA posted o Oct 12-Nov 2 Comment period Nov 9 Post recommended response to comments Nov 13 MAC webinar Nov 16 (tent.) Open Board webinar Nov 23 Post near-final draft UDSA posted Dec 8-9 Board meeting discuss any last direction/issues Dec 31 Final version out for signature

5 Reliability Messaging Tool Michelle Mizumori

6 What is the Reliability Messaging Tool (RMT)? A web-based, real-time application that will be used as the core operations messaging and communication tool. Users will be Peak, Balancing Authorities (BA) and Transmission Operators (TOP) As soon as RMT is operational, Peak will no longer use WECCNet. 6

7 Benefits of RMT Leverages Peak existing extranet infrastructure to deliver a more unified toolset. Provides greater accessibility to users without the need for specialized terminals. Provides built in message acknowledgement processing and tracking Provide capabilities to interface with Peak tools such as displays and logs Provides flexibility for future enhancements and customization 7

8 Benefits of RMT (cont.) Acknowledgment feature: o Identifies clearly messages that must be acknowledged by recipient o Allows sender to easily track which recipients have acknowledged messages o Assures that important messages are read 8

9 Summary To view the webinar, click HERE. For more information, contact Key Dates: October 1 RMT Beta version released Early Nov. RMT Advanced Webinar (Beta Participants) Early 2016 RMT released to all Entities/Users 9

10 GridEx III Terry Baker

11 Grid Security Exercise 2015 GridEx III Participant Map 11

12 12

13 Grid Security Exercise Entities in Peak RC Area playing 13

14 Grid Security Exercise 2015 recover from severe events Continuing Long Term View evolution Exercising timely, real-world scenarios Increasing stakeholder participation and training value Increasing integration with BPS operations Greater state/provincial and local government participation GridEx 2011 GridEx II 2013 GridEx III 2015 Greater integration with U.S. and Canadian senior executives and government officials Including other most critically interdependent infrastructure sectors Increasing interactive simulation into joint simulation 14

15 Grid Security Exercise 2015 Organization Benefits Voluntary participation Individual Training NERC Certified Operators may earn up to 16 NERC CEHs Training hours for staff with information technology or cyber security certifications Training hours for staff with physical security certifications Opportunity to cross-train staff to support other business functions 15

16 Grid Security Exercise 2015 GridEx III November 18-19, 2015 Contact for information or contact to enroll 16

17 West-Wide System Model Validation Gareth Lim

18 Peak Internal Quality Assurance Peak Internal Network Model Verification o In addition to EMS vendor provided validation o Improves efficiency of modeling & model validation (via automation of verifications) o Assures Modeling Consistency & Quality Rigorous Model Testing Process o Includes Network Applications testing SE, CA, VSA, PSLF 18

19 Peak Internal Quality Assurance Peak Mapping Verification Process o Resolve broken mapping to other subsystems due to new Model Release o Assures Integrity & Continuity of Data Mapping with various Integrated & External Systems / Applications Internal Feedback Mechanism o Internal Issues Tracking Sharepoint List / Ticketing System 19

20 WBRTF Efforts West-Wide System Model Basecase Reconciliation Task Force (WBRTF) o Peak s attempt to work on External validation efforts focused on Data Validation against WECC Planning Basecase Model o Focused on Generators, Transformers, and Lines Parameter Comparison o Received limited responses from several TOPs, and implemented recommended changes 20

21 WBRTF Efforts Approach Produced Mixed Results Lessons Learned o Inaccurate Mapping = Inaccurate Comparison o Slow-Response / Non-Response from Larger TOPs o Disagreement between TOPs Operations & Planning departments modeling data o One-time manual effort, with limited follow-up 21

22 Planning Comparison Efforts Comparison Process: o Comparison Tool Development To automate WSM vs. Planning Basecase comparisons o Translation Table Mapping To facilitate automation of comparison process 22

23 Planning Comparison Efforts Reporting Process o Develop Process to Periodically Generate Comparison Reports Highlighting larger differences Benefit: Allows for Continuous Comparison Efforts o Comparison Reports will be sent to both TOP Operations & Planning contacts for reconciliation 23

24 WSM Validation & Acceptance Strategy Peak Developing WSM Validation & Acceptance Strategy, focusing on: o Data Validation o Model Enrichment o BA / TOP Outreach WSM Exports & WSM Value Added o Metrics o Continuous Process Improvement 24

25 WSM Model Exports Peak Reliability posts on PeakRC.org the various WSM Exports each Model Release. Includes: 25 o Network Model in Various Formats e.g. CSV, CIM o Scada Model o One-line Diagrams Posted on o Seasonal Ratings Data PeakRC.org in o Mappings to External Systems the Model Library o Model Release Highlights o ICCP Data Points List Encourage BAs & TOPs to Access & Review

26 Hosted Advanced Applications Brett Wangen

27 Peak Hosted Advanced Applications (HAA) Service objectives o Enhance reliability for all o Help meet TOP compliance obligations 14 HAA users 45 day trial available for interested TOPs Peak providing 101 and 201 training Peak Hosted Advanced Applications User Group looking at service enhancements 27

28 How do I learn more about HAA? Peak contacts o Brett Wangen and Mandee Elenes (hosted.apps@peakrc.com) Alstom contact o Erik Felt (erik.felt@alstom.com) Check out 28

29 Peak Reliability Synchrophasor Program Brett Wangen

30 Peak Reliability Synchrophasor Project (PRSP) PRSP is focused on: o Data quality o Expanded use of V&R ROSE voltage stability o Linear State Estimation (LSE) o Improvements to mode meter and oscillation detection tools o PMU management through the registry o Situational awareness improvements through improved visualization capabilities 30

31 Three-Day Study Process Jason Ausmus

32 Iterative 3-day OPA Process New 3-day study process began after Labor Day Process is iterative which means: o Multiple studies for same day being performed (3 iterations) o Updating topology (COS), load and Path SOL data, where applicable o First iteration is 3 days out last iteration is evening ahead Currently ramping up 3 new study engineers o Initial 3-day OPA focus on weekdays 32

33 Overview of Peak s 3-Day Ahead Process changes to snapshot cases Projected peak 17:00 MST 3 Business Days Ahead 1 st iteration of 3-day study 2 Business Day Ahead Cont. w/3-day study (update data as necessary) 1 Business Day Ahead 2 nd iteration (New SE case) Engineer 1 Engineer 2 Projected peak 10:00 MST Peak ROE Study From Evening Ahead 33

34 What changes does Peak make to a snapshot? Topology (return/remove from service) 34 o All changes driven by COS accuracy o Currently gen adjustments only made via data submitted to COS; future goal is to use UC submitted via EIDE Load Forecast o All data retrieved via EIDE submissions o Some data smoothing occurs via internal Excel tool Path SOL

35 Study Outcomes Input data quality is key to performing accurate studies o Need to ensure data in COS is correct Purpose of moving to a 3-day study is to allow more time to investigate/resolve concerns Peak study engineers routinely send out study result s following internal validation o s sent as far as 3 business days in advance o response expectations: If concern is valid and mitigation is known, then please respond as time allows. 35

36