Branden Sudduth Director, Reliability Assessment and Performance Analysis

1. Branden SudduthDirector, Reliability Assessment and Performance Analysis Rocky Mountain Region PA/PC Meeting March 18-19, 2014 Denver, Colorado

2. Overview • The NERC Functional Model Overview • The Planning Coordinator • The Coverage Gap Issue in WECC • WECC Staff Observations • Planning Coordination Committee Effort • Planning Coordinator Survey Results

3. The NERC Functional Model and the Planning Coordinator

4. The NERC Reliability Functional Model • NERC Reliability Function Model version 5 • Functional Definitions and Functional Entities • Technical Document • Purpose: • Provide a framework for Standards development • Describe reliability functions and relationships between entities that are responsible for performing the tasks within the functions

5. Guiding Principles of the Model • The model must be complete – no gaps • No overlap for operation tasks • In certain instances, overlap for planning tasks is unavoidable • The model is a guideline – it does not address requirements for registration, delegation, or sharing responsibility

6. Function – Planning Reliability • Develop methodologies for planning analysis and simulation • Define information required for planning purposes and facilitate collection process • Evaluate, develop, document, and report plans for Planning Coordinator area • Coordinate with adjoining Planning Coordinators • Develop and maintain models

7. Functional Entity – Planning Coordinator • “The functional entity that coordinates, facilitates, integrates and evaluates (generally one year and beyond) transmission facility and service plans, and resource plans within a Planning Coordinator area and coordinates those plans with adjoining Planning Coordinator areas.” • Assesses longer-term reliability

8. Standards – Planning Coordinator • Standards applicable to the “Planning Authority” are applicable to the “Planning Coordinator” (pre-version 3 revision)

9. Standards – Planning Coordinator (cont.) • Some Applicable Reliability Standards • TPL-001 through 004 (System Performance) • FAC-002 (Coordination of Plans for New Facilities) • FAC-010 (System Operating Limits Methodology for the Planning Horizon) • MOD-016 (Actual and Forecast Demands, Net Energy for Load, Controllable DSM)

10. Organization Structure • NERC Functional Model is not always prescriptive on “who reports to who” • Depending on the specific function, reporting structure for a functional entity may change • Structure can vary greatly depending on interpretation by entity • Planning Coordinator definition is vague and Registration doesn’t help

11. The Planning Coordinator Gap Issue in WECC

12. Contributing Factors to the Problem • June 2007 • Mandatory Standards initially created chaos • “Checklist” registration with no review or coordination • Functional Model meant to be a one-size-fits-all solution – in many instances, WECC is “different” • Area Coordinators • Path Operators

13. Planning Coordinator Count by Region

14. Planning Coordinator Gaps Issue • Perceived reliability risk because: • Several entities do not know who their Planning Coordinator is or mistakenly assume another entity is performing this function for them • There is a lack of clarity in Functional Model around who should be a Planning Coordinator • There is no clear definition of a Planning Coordinator Area • There may be reliability functions not being performed because of gaps

15. WECC Staff Observations and PCC Efforts

16. WECC Staff Observations • In WECC, currently Planning Coordinator gaps create more of a compliance risk than a reliability risk • Many functions duplicative of Transmission Planner functions • Area Coordinators created for data collection • Interconnection-wide coordinated plans (UFLS) • The list of registered Planning Coordinators almost the same as list of registered Balancing Authorities

17. WECC Staff Observations (cont.) • Gaps not prevalent in regions where ISO/RTOs exist • Reluctance to be a Planning Coordinator is often tied to liability concerns • More Reliability Standards applicable to the Planning Coordinator are being developed…

18. MOD-032 Standard Development Update • Passed final ballot in December 2013 • NERC Board approval February 2014 • Requires data providers to submit power flow, dynamics, and short-circuit data to their Planning Coordinator and Transmission Planner

19. Base Case Data Submittal Process (current and general)

20. Base Case Data Submittal Process (MOD-032)

21. Planning Coordination Committee (PCC) Effort • October 2013: PCC asks WECC staff to develop a list mapping Transmission Owners and Generator Owners to Planning Coordinators • December 2013: System Review Work Group survey conducted to identify facilities not in a Planning Coordinator Area • PCs asked to respond to survey • Still collecting and compiling responses

22. Planning Coordinator Preliminary Survey Results as of 3-11-14

23. “Arizona” Area Unclaimed Buses

24. “Northwest” Area Unclaimed Buses

25. “Montana/WAPA UM” Area Unclaimed Buses

26. “PSCo/WAPA RM” Area Unclaimed Buses

27. “California” Area Unclaimed Buses

28. Branden Sudduth WECC branden@wecc.biz 801.883.6888 Questions?

29. Defining the Problem • What is the role of the Transmission Planner (TP) vs. Planning Coordinator (PC)? • Who should be a TP? • Who should be a PC? Who should they be a PC for? • How should TP and PC area boundaries be determined?

30. Formulating a Proposal • What concerns do entities have relative to being a PC? • How formalized should PC arrangements be? • What are a PC’s responsibilities for Generator Owners (non-TO)? • What can WECC do to help facilitate the resolution of PC gaps?

31. Review of Action Items