ECC Task Force Webinar September 3, 2015

2 Peak Anti-Trust Statement Phase 1A Update webSAS Integration PSE Access Peak and the Task Force Next Steps Agenda

3 Anti-Trust Statement I would like to remind ECC Task Force members and observers that this meeting is being conducted subject to the condition and requirements of NERC’s Antitrust Guidelines, which supports compliance with antitrust laws and the avoidance of all conduct that unreasonably restrains competition. A copy of NERC’s Antitrust Compliance Guidelines will be provided upon request. If you have any questions or concerns regarding your antitrust responsibilities, please see a member of Peak’s Legal Department. The NERC Antitrust Guidelines are available at: liance%20Guidelines.pdf

4 Confirm New Notification Process

5 Peak to put together a FAQ on the project and post to peakrc.com Develop strawman for Element definition process Peak to set up meeting with training sub- group Action Items

6 Phase 1A Testing occurred last week at OATI o Peak staff Monday - Wednesday o External testers Thursday - Friday  8 participants representing 6 entities (BPA, CAISO, PSCO, TSGT, WALC, WAUW) Phase 1A Testing

7 Peak Testing o System did not demonstrate input data processing to appropriate factors and flows o Situational awareness and element definition GUIs still require tweaks for user experience o Variances and enhancements documented Phase 1A Testing

8 Stakeholder Testing o Good representation of operations perspective o Overall positive feedback about getting a first look into the system o Documented improvements more than variances o Several conversations around operational usage of the tool Phase 1A Testing

9 OATI is correcting variances and enhancing system based on Peak and stakeholder feedback OATI will have updated system on Sept. 21 st Peak will confirm system readiness with demonstrations and remote testing prior to next FAT o Tentatively early October Peak remains committed to facilitating additional stakeholder testing to verify GUIs and calculations Phase 1A – Moving Forward

10 Peak is still targeting usage of tool before end of 2015 Phase 1A will be deployed to Peak in 2015 but stakeholder usage will be delayed to early 2016 Phase 1A – Moving Forward

11 Original training was planned both internally and externally for October & November Peak training will remain between now and end of 2015 Peak is committed to effective stakeholder training including in-person sessions o To maintain this commitment, training will slide to early 2016 prior to deployment Phase 1A – Training Changes

12 Mappings o Peak needs more assistance with mapping sinks to model data o Discussed in Minneapolis the possibility of confirmation display in webIntegrity Naming convention o Need to have common name between Peak and entities when looking at congested elements Element definition o Peak will provide updated business process Phase 1A – Open Stakeholder Items

13 Peak will increase project management effort around webIntegrity o More frequent meetings, decision break points Peak is working to obtain more view into the development to avoid similar scenarios o Remote access, more face to face with OATI Phase 1A – Lessons Learned

14 Next FAT - October 2015 Internal training – Complete 4 th quarter 2015 Phase 1A use by RSCO – end of 4 th quarter 2015 External training – Hold 1 st quarter 2016 Phase 1A use by external entities – no later than end of 1 st quarter 2016 Updated Phase 1A Schedule

15 Peak and the ECCTF had agreed at the June meeting to move up webSAS integration in the project schedule Recommendation was to meet with UFAS and get their endorsement webSAS Integration

16 Peak developed a short position paper that was circulated to UFAS Discussion with UFAS on August 25 th call o Participants generally felt positives outweighed the negatives on making this project change o Some discussion around PSE access (next topic today) Peak received UFAS support to move forward with this change webSAS Integration

17 Peak agrees with this change in project schedule and will move webSAS integration ahead of current Phase II “curtailment methodology” development in the project schedule Will develop change order with OATI Will update ECCTF on project impacts webSAS Integration

18 Question of PSE access in webIntegrity and webSAS unresolved o Lots of conversation with the Task Force o Main concern UFAS raised in moving ahead with webSAS integration Question is not tied to webIntegrity tool but is open issue across all Peak tools related to Standards of Conduct and data sharing PSE Access

19 Peak will: o Document the issues o Organize talks between Peak Legal and interested stakeholders as needed Interested stakeholders are encouraged to document position and provide to Peak Internal conversations at Peak are ongoing PSE Access

20 Improved communication o Continue to hear that more info is needed on webIntegrity o Need to engage operations o FAQ document is next priority to provide to stakeholders Prioritize ECCTF work o Must refocus on issues related to Phase 1A delivery o Need to prioritize topics based on updated Phases Utilize Task Force expertise o Need to revisit open items and utilize participants o Peak is looking for collaboration in addition to guidance Peak and the Task Force

21 Peak expectations o Short – two pages o Targeted to Operations stakeholders o Topics  Phases  Functionality  Training Other needs from Task Force ? Peak will vet through ECCTF FAQ Document

22 Action Items Peak is focused on Phase 1A efforts o Need to focus on related open Task Force items o Will plan meetings to address these open issues by end of 2015 Next Steps