Planning Tools Subgroup Discussion

1. Planning Tools SubgroupDiscussion SRWG July 6-8, 2011 Calgary, Alberta, Canada

2. Goals for the whole SRWG discussion • Summarize PTS discussion • Process summary • Area Coordinator Specifications • Discuss Transmission Planning needs • Express needs in terms of Specifications • Make a preliminary list of Cases to be developed • Year horizons, seasons, loading scenarios • Transition • Describe steps to move to BCCS methodology

3. RFP Section 1.4 Business Needs Reasons for developing the BCCS : • Improving the base case development process • Improving base case data management (validation, tracking, notification)

4. RFP Section 1.4 Business Needs In more specific detail, BCCS functional goals are to: • Centralized, auditable, queryable database system • Produce more cases annually • Support multiple power flow simulation platforms • Expand planning timeframes beyond 10 years • Interface with the WSM • Interface with other WECC software, such as Economic models used by TEPPC • Produce WECC reports • Loads and Resources balance summaries • Others as needed

6. Base Case Coordination System - Basic Structure System Data in various formats Time-stamped project definitions • Future facilities • Generator Data • Short Circuit data • Load Forecasts BCCS Database • Database Contents: • 10-years (or more) • 4 seasons • Heavy and Light • Committed Projects • Proposed Projects • Future Generators • Capabilities: • Data entry • Case change • Solution engine • Audit & Check • Notifications • Confidentiality • Case Creation: • Select year/season • Select Loading • Select scenario • Solve and validate • Posted WECC Cases • User-specified Cases

7. Base Case Creation Process BCCS Database • Case description • Year/season • Loading scenario • AS-OF date • Rating table • Device status table • Path Definitions • Project files • Load & Resource Tables • Load scenario • Generation • Save/recall info User Selection • Following user selections and settings • Retrieve specified data into BCCS system topology • Apply time-stamped project definitions • Save result with the BCCS database • Optionally, output standard-format flat file base case data Assemble Base Case Solve and validate • Post WECC Cases • User-specified Cases

8. Existing Process Effort • Users send to Area Coordinators • Transaction and Interchange totals • Load and Loss data • Generator Schedules for load and reserves • Updated Ratings, Topology, Status, Bus data • All in a change file referenced to Starting Case

9. Existing Process Effort • Area Coordinators • combine sub-area submittals • check load and losses • check load–generation balance • develop and report net interchange • check area tie-line definitions and data • run case to observe N-0 performance • notify contributors of any performance violations

10. BCCS Process Effort Users • Create Project Files from Case Comparisons • Create Bus Load and Generation profiles • Create Device-Control profiles • Create Net Schedule and Interchange profiles • Build and Test the Case • select predefined Profiles • Select Projects to be included • receive automated evidence of submittal

11. BCCS Process Effort • Area Coordinators • Approve updates and data submittals • Build Case and verify Solution • Run N-0 report • Notify WECC of completion • WECC Staff • Build case based on data in the BCCS • Post Case

12. BCCS Process 2012 Topology Master Base Case

13. Project Model Effective date

14. Project Data Contents Line attributes : • ID and name • connectivity & status • configuration • parameters • seasonal ratings • other (e.g. owner) Bus attributes: • ID and name • connectivity & status • parameters • ratings (voltage settings) • other (e.g., voltage class)

15. Project Data Contents Transformer attributes: • ID and name • connectivity & status • configuration • parameters • tap • seasonal ratings • other (e.g. owner) Generator attributes: • ID and name • connectivity & status • parameters • capability curve • seasonal dispatch • dynamic models (WECC accepted or generic model) • other attributes (e.g., owner)

16. Project File Created Manually Project file

17. Project File from Case Comparison Case One Compare Cases Project file Case Two

18. Case Building Process

19. Data requirements • User responsibilities • Load forecasts [power factor, MW/MVAr] • Probability level [SRWG prefers 1-in-2] • Monthly or seasonal ; On-peak / Off-peak • Coincidental load forecasts are intended • Build monthly gen & load matrix • Submit data annually • Profiles for designated seasons and years

20. Data requirements • Define areas for scenarios • Pre-Determine busload and generation • MRO develops company workbooks first • WECC may be able to do this within BCCS • Project files Effective dates monthly • Determine what WECC requires (Nov11 agenda) • ACs are to ensure that case updates for their area do not affect case solubility • We could consider using an alternative base case

21. Discussion: Are special features needed for robust model solutions? • extended models • generator groups, reactive groups, branch groups • specialized features • distributed slack • coordinated voltage and VAr control • MBC within BCCS must be solved • Voltage profiles • for seasonal starting points • By each area • Consider differences between solution engines in BCCS solution development • TT will set agenda for a teleconference on Solution Capability

22. Stress Case Development • Discussion: Do we need stress case capability in BCCS? • Are stress cases included in BCCS Requirements? • Data-Yes • Stress case processing - No

23. Functional and Structural Requirements in the BCCS RFP

24. 2.10 BCC Methodology BCC capabilities described in Section 2.10 that will be needed but do not appear to be within the existing Project File Builder feature. • 1. a way to adjust the system for scenario configurations. This includes defining ways to stress paths (2.10.4.3). • 2. a way to define interfaces as sets of lines and transformers (2.10.13.11). This would also facilitate documenting how rated paths may be stressed, and creating stress cases. • 3. for certain network changes, we need process control capability. This would include being able to insert a network solution after every few changes or as needed (2.10.7.2) • 4. an option to adjust area interchange automatically as new values for generation and load are entered (2.10.10.1). This, combined with ability to specify and adjust transfers between areas|zones|regions (2.10.13.7), would give a more complete picture of load and resource balance, and would facilitate interface for other WECC reporting.

25. 2.10 BCC Methodology BCC capabilities that may be needed but are not characteristic functionality of the Project File feature. 5. a way to extract an area|zone|owner|region to a reduced equivalent (2.10.13.16) 6. a way to merge (or overwrite) data from one case into another (2.10.13.9). This would enable a user to work with an reduced equivalent file to set up and test a case, then enter changes into the BCCS without inserting the reduced system data into another case first. There may also be ways to filter input by area or by owner to accomplish this. 7. a way to store and retrieve named contingency lists (2.10.13.13) 8. a way to store and retrieve performance criteria (voltage|dV|overload) by area|zone|owner|region (2.10.14.1) 9. WECC-staff specified standard data checks (2.10.14.6)

26. Scenarios – Two types • Standard Cases- combinations of load, generation, topology, and project data • handled through user selection of data as it exists in the database • Stress scenarios – data is adjusted to represent extreme conditions • Flow scenarios to stress transmission paths • Load scenarios to estimate loads beyond the years represented in BCCS data

27. Needed for Load Scenarios • separate load and generation forecast for each load scenario, or • user defined load scaling factors and/or other procedures to extrapolate load values • methodology for scheduling generation to meet load by Balancing Area • associated conditional criteria to manage system adjustments with selected load levels

28. Needed for Stress Scenarios • a mechanism for grouping buses (busgroup) • a mechanism for identifying busgroup load and generation • source and sink definitions • a methodology for scheduling flows between busgroups • load scaling or generator dispatch priority • phase-shifter settings • accepted path limit values • a mechanism for defining and applying conditional criteria • a procedure for optimizing generation and device settings to achieve specified flows subject to defined conditional criteria

29. We do need stress cases • Stresses that affect WECC regional system wide • DC intertie • Clockwise flow • Counter-clockwise flow • TSS must define the problem in a separate process

30. Discussion: What is needed for “Transmission Planning” • Case series (next slide) • Data maintainability, security, audit trail • Version control • Isolate specified area • More?

31. Determine WECC Case Series SRWG assignment: • Look at MRO descriptions (MRO series shown above) • Submit proposals for case series requirements • Discuss at November SRWG meeting

32. Transition to BCCS (Preliminary)

33. Transition to BCCS • Select WECC Master Base Case topology • 2012 existing topology starting point • Clean-up MBC model to get the most accurate representation for summer 2012 • Projects and Profiles • Project Files • Phases, Status Gates • BusLoadGeneration profiles • Device-Control profiles • Net Schedule and Interchange profiles • Joint generators

34. Transition to BCCS Develop Project files • A project includes all the data and information needed to represent a planned change in the system • Reference all case-building processes to a starting case • Projects should represent groups of related-facilities • Grouping Project change files by month and year • Project files must contain individual project elements that comprise a project, not just an IDV of all changes to a particular case • Convert all case addition, modification, deletion to Project files • Define gates for projects (Conceptual, Permitting, Construction, Completed)

35. Transition to BCCS Dynamic data in Project files • Project files reference dynamic files • Incremental dynamic model update files • Whenever the project is applied, the referenced (incremental) dynamic file is applied • Work is underway (by Siemens-PTI) to model dynamics directly in MOD

36. Transition to BCCS • Submit projects (schedule TBD) • 5-year timeframe first • then 10-year timeframe • Submit and acquire AC/WECC approval for Projects • Starting with 2012 WECC MBC topology • Apply Project Files dated up to the Case Date • Add BusLoadGeneration profiles • Add Device-Control profiles • Add Net Schedule and Interchange

37. Project Status Gates See MRO Case Builder document for more information. There may be some relation to the 3-phase rating process steps

38. Transition to BCCS • Vendor delivers 1st version of BCCS • Vendor provides training on how to build, submit, populate and maintain: • Master Base Case (seed or reference) • Projects • Profiles • load forecasts • generation patterns • interchange schedules • Training may occur in segments or combined

39. Transition to BCCS Populate the BCCS with Vendor assistance • Designated data submitters input load forecasts, generation schedules, and Projects • WECC staff input existing dynamic model sets

40. Transition to BCCS Vendor delivers 2nd version of BCCS and provides training on how to: • build, review, approve and release cases (power flow and dynamics) WECC staff builds cases Submitter review and approval (1-5 passes)

41. Transition to BCCS WECC staff releases first official case set using BCCS Future: Convert Modeling AREAS to Balancing Areas • Set up a joint ops/planning Task Force to map areas to BAs • Redefine AREA tie-lines to BA tie-lines • propose numbering and naming for the balancing areas.

42. Additional Issues • Define users and approval hierarchy • Groups that provide data • Generation Owner • Transmission Owner • Resource Planner • Municipal and non-registered facility information? • Data approvers • Area Coordinators • Transmission Planners • Specify data checks to be performed