1. ECC Task Force Webinar November 13, 2015

2. 2 Peak Anti-Trust Statement Meeting Minutes (June and Sept) Phase 1A Progress Phase 1A External Entity Testing Phase 1A Training/Implementation Plan FAQ Document webSAS Integration Future Meetings Agenda

3. 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: http://www.nerc.com/gov/Annual%20Reports/NERC%20Antitrust%20Comp liance%20Guidelines.pdf

4. 4 June 30 – NWPP Offices September 3 – Webinar Other meeting minutes posted on peakrc.com Meeting Minutes

5. 5 After the August testing session, OATI developed a plan to address issues o Sprints o More collaboration between OATI and Peak Peak detailed conditions that were required before next round of acceptance testing Phase 1A Progress

6. 6 Peak performed acceptance testing week of October 19 th at OATI’s offices Positive direction o Factors verified against Peak EMS Functionality left for OATI to demonstrate o Element definition o Some calculation/layer issues o System performance Phase 1A Progress

7. 7 Peak will review variance corrections and system changes next week (Nov 16 th ) RCSO training will be complete in early December webIntegrity Phase 1A in Peak control rooms: December 16 th Phase 1A Progress

8. 8 Peak remains committed to facilitating additional stakeholder testing to verify GUIs and calculations Prefer that stakeholders test prior to the Peak implementation mid-December Do not believe that travel to OATI’s offices is needed to retest Phase 1A External Entity Testing

9. 9 External Entity Retest Plan: o Dates: December 3 rd and 4 th o Location: Peak’s offices (Loveland and Vancouver) o OATI will provide support during retesting o Restricted to testers from reliability entities  No MFEs o No more than 10 testers per site o Priority to entities who participated in August Phase 1A External Entity Testing

10. 10 If interested in participating, let Jeremy know no later than Friday, November 20 th jwest@peakrc.com (970) 776-5561 Phase 1A External Entity Testing

11. 11 Stakeholder training delayed until Q1 2016 Maintaining commitment to multi-pronged approach to training external stakeholders o Classroom sessions o Webinars o CBTs Begin with instruction for TOPs, BAs, TSPs webIntegrity Training/Implementation

12. 12 Classroom sessions o Train the trainer o Support regional locations to encourage participation o Presentation with hands-on time in webIntegrity tool o Limited to around 20 participants per session (10 per site when at Peak) webIntegrity Training/Implementation

13. 13 webIntegrity Training/Implementation

14. 14 Peak will release an enrollment process for the classroom sessions (first come, first serve) Other training approaches will be communicated in near future webIntegrity Training/Implementation

15. 15 Production access for TOPs, BAs, TSPs MARCH 7, 2016 webIntegrity Training/Implementation

16. 16 Expectations previously discussed: o Short o Targeted to Operations stakeholders o Topics  Phases  Functionality  Timelines FAQ Document

17. 17 1.What is the ECC? 2.Who is the vendor? 3.What does the ECC do? 4.What are the phases of the ECC project? 5.What are the inputs to ECC? 6.What are the outputs to ECC? 7.Who can use the ECC tool? 8.How will Peak use the ECC in its congestion mitigation approach? 9.What is the timeline for ECC development and deployment? FAQ – Questions Addressed

18. 18 Peak received consensus to move forward with webSAS integration as next phase of ECC project o PSE Access o Parallel Operations Working with OATI to change contract and develop specifications for development work webSAS Integration

19. 19 Benefits: o Real time factors vs Seasonal factors o Mappings more granular o Verification of ECC calculations against known product webSAS Integration

20. 20 Change Order signed before end of 2015 Development time estimated 30 weeks Demo site deployment and testing Summer 2016 Parallel Operations Late Summer - Fall 2016 Production Deployment Late 2016 webSAS Integration Timeline

21. 21 Peak proposes that we hold a face-to-face meeting in January 2016 o Discuss outstanding concerns with webSAS integration o Resume talks on curtailment methodology strawman  Suggestion that TF meet independent of Peak Future Meetings