320 likes | 482 Views
Gordon Comegys Chair, System Review Work Group. SRWG Report to TSS April 26, 2012 Salt Lake City, UT. Approved at SRWG March Meeting. 2013 Base Case Compilation Schedule Data Preparation Manual revision SRWG Handbook revision Performance Log Item closures BCCS practice procedure.
E N D
Gordon ComegysChair, System Review Work Group SRWG Report to TSS April 26, 2012 Salt Lake City, UT
Approved at SRWG March Meeting • 2013 Base Case Compilation Schedule • Data Preparation Manual revision • SRWG Handbook revision • Performance Log Item closures • BCCS practice procedure
2013 Base Case Compilation Schedule • Same number of operations, planning, and scenario cases • 5 operations (heavy&lightsummer&winter, heavy spring) • 3 planning (5 year heavy summer&winter, 10 year heavy summer) • 3 scenario
2013 Base Case Compilation Schedule (continued) • Scenario Cases • TEPPC planning case • Description to be developed after experience with the 2012 22LSP-TEP case • 2024 Heavy Summer with Colorado,Utah, Northern Nevada stress for RAS study • 2014-15 Light Winter with high import into Southern Calif from Desert Southwest (delayed case from 2012 Study Program) • Recommend TSS Approval
SRWG Handbook Revision • Clarify • Info needed for resolution of log items • Procedure to exempt gen from PSS model requirement • Miscellaneous word changes • e.g. terminology consistent with standards- steady state and dynamic
SRWG Handbook Revision (continued) • To Do for future revision • Consolidate exceptions list with Reliability Subcommittee • Add procedure to remove from exceptions list • Recommend TSS Approval
Data Preparation Manual Revision • Substantive changes • Generator reactive capability curves if used for internal studies • Non-conforming load / scalable load flag • Allow netting more than 5% of an Area’s generation • Exempt station service load model if less than 1 MW
Data Preparation Manual Revision (continued) • Clarify • No equivalencingBES elements • Alpha characters in strings are treated as case insensitive • Typical dynamic data for planning cases is the posted MVWG approved document • All fields specified in the DPM are required • Only reference to optional fields is the requirement that, if populated, must conform to PSLF manual
Data Preparation Manual Revision (continued) • Considered, but not included in DPM • Upper case alpha characters in strings • No spaces in strings • Populate latitude/longitude fields for bus location • Populate generator type field • All WECC-0074 requirements addressed • Recommend TSS Approval
Disturbances for 2012 Annual Assessment • None submitted • Use same contingencies/switch decks from Montana/Idaho/Wyoming study 5 years ago • Report content contingent on task force
Performance Log Review • P11-01-NT • WAPA and DGT acknowledge the acceptance of the Post Transient Voltage exception of 7% by Deseret Generation and Transmission at Deserado Mine. TriState Generation and Transmission, by their current entries have already confirmed their acceptance for this area • SRWG approved placing the 7% deviation of the WECC exception list • P11-02-NT and P11-03-NT • SRWG approved closure of these log items (PNM and TriState), A re-study using case corrections and adjustments in the 2012HS3Sa case resolved all performance violations identified in the 2011 Study Program.
TEPPC and VGS Study Request • Advice to TEPPC on 22LSP1-TEP study • all N-1 outages 230kV and above is ok objective for powerflow screening • Auto generated single branch outages ok for first screening, then address contingency definitions with TP for flagged violations • Advice to VGS • Examine TEPPC results, then develop dynamic study strategy • Response will be from TSS
REP LOG March 29, 2012 PCC Meeting
Representation Log Review • total counts down by 281 (Transmission -103,Generation -178)
Representation Log Review • total counts down by 281 (stnds -187,non-stnds -94)
BCCS Implementation Process • Approved practice task to create project files for changing 12HS4 topology to 18HS2 topology • BCCS Assurance Team • NORTHWEST Area Coordinator • SOCALIF Area Coordinator • MONTANA Area Coordinator • Pacificorp-East Area Coordinator • Tri-State G&T • Avista
Project Status Update (con’t) • The BCCS will be a web-accessible, centralized database that automates existing processes. It will also provide a central location for maintaining base case information. This will increase the accuracy and timeliness of base case development. The BCCS will also provide a mechanism for supporting other WECC functions. The BCCS offers the following features and benefits:
Project Status Update (con’t) • Features • PSLF/PSSE platform compatibility • Change tracking • Automated error checking • Secure Web interface • Interchange coordination • Database flexibility
Project KEY Information should include: • Description label contents • Company, date • Interconnection Queue number • ISD, OSD, Phases • Project Status Milestones, • See next slide • Data Status Type • Location by State or Province • Dependencies (Project sequence) • Need input forms for populating this information Page 2 of 15
Project Model data • Rating updates are placed in Profiles • Transactions, firm transfers and generation schedules will be balanced within BCCS • These power schedules are placed in Net schedule Interchange Profiles Page 4 of 15
Develop Data Specifications • Consider Data Submission Schedules • annually or monthly • Profiles for designated seasons and years • Structure to store TPL Contingency lists • within BCCS • Control Access? • To improve program automation • Do we need this Page 7 of 15
Features needed for robust model solutions • Solution capability within BCCS • There is concern that overall solutions will be more difficult • Voltage profiles • for seasonal starting points • By area If/when needed: • Develop extended models • generator groups, reactive groups, branch groups • Consider specialized features • distributed slack • coordinated voltage and VAr control Page 10 of 15
Develop “BCCS implementation plan” • Determine Master Base Case time frame (tentatively 2012 HS) • Create Change file to 2012 case to create 2018 base • EPC, IDEV, EPCL, PYTHON, PRJ • Need out-service and in-service (verify) but is capable with the project file builder • PSSE currently does not have out of service dates. PSLF has this capability but it’s not certain the in-service and out-service dates will be converted in the project files. • Place Joe Smith on July 2012 SRWG meeting. Page 11 of 15
Develop “BCCS implementation plan” (con’t) • Project Naming, Structure • NERC compliance acronym_areano_projname(E.G., project name in annual progress report) • For example: Sce_24_dcr.prj • Submit a project description or translation file within the project files
Develop “BCCS implementation plan” (con’t) • Validate Master Base Case data • Define user responsibilities and access settings • Define file-naming specifications as needed • Define Project Naming specifications • Schedule training after contract closure • Obtain vendor tools for building data • Start developing Project Files • Steady State and Dynamic data are separate • Develop Seasonal Profile data • Bus-Load-Generation (including losses) • Net schedule and Interchange data • Device control • Develop rating files • Begin using BCCS
Data Submittal Process • Set schedule for base case compilation • Individual Contributors • Input Projects and Profiles • Validate accuracy • Area Coordinators review and approve data submittals Page 13 of 15
BCCS Status • The BCCS will be a web-accessible, centralized database that automates existing processes. It will also provide a central location for maintaining base case information. This will increase the accuracy and timeliness of base case development. The BCCS will also provide a mechanism for supporting other WECC functions. The BCCS offers the following features and benefits:
Base Case Issues Raised • 22LS1-S in 2011 study program specified maximum renewables WECC wide • Area Coordinators didn’t answer question on signoff sheet whether case description was met • Signoff sheet will be revised to make the question obvious • Missing, invalid, and incorrect Load Long_ID’s in 12HS4 • Request for new load Long_ID data sent to develop new dyd file for composite load model studies • New approved cases are not using the new SVC, Statcom, and TSC models (SVD types 5, 6, and 7) • Request that these new approved models be used • Decommissioned generators are still in approved case (status open)
Base Case Issues Raised (continued) • Some wind generators in MDF using obsolete MotorW dynamic model • Wind gen approved model list will change to exclude MotorW • Info only- baseload flag in powerflow will continue to be 1, but for transient stability simulations it should be changed to 2 • Baseload flag=2 allows generator overfrequency governor response and prevents underfrequency governor response • Baseload flag=1 prevents over and under frequency response, which is not correct for most generators
Issues for SRWG June 20-22 Meeting • Data Request Letter- require only new or changed data for both steady state and dynamic data (from WECC-0074 Criterion development) • SRWG Charter revision- add Vice Chair • Draft procedure for removal from Exceptions List • Solicit agenda items