WECC Criterion MOD-(11 and 13)-WECC-CRT-1.1

Transcription

1 WECC Criterion MOD-(11 and 13)-WECC-CRT-1.1 A. Introduction 1. Title: Steady State and Dynamic Data Requirements 2. Number: MOD-(11 and 13)-WECC-CRT Purpose: To establish the consistent data requirements and reporting procedures whereby data is collected and reported to create an accurate modeling of the Western Interconnection. 4. Applicability: This document was developed pursuant to North American Electric Reliability Corporation (NERC) Reliability Standard MOD (Standard MOD Regional Steady-State Data Requirements and Reporting Procedures) and (MOD (Standard MOD RRO Dynamics Data Requirements and Reporting Procedures). Violation of this document may result in a violation of NERC Reliability Standards MOD and MOD Violation of NERC Reliability Standard(s) MOD and/or MOD may result in financial penalties imposed by NERC Functional Entities: Transmission Owner Transmission Planner Generator Owner Resource Planner Reliability Assurer 5. Effective Date: July 1, Background: The Western Interconnection is designed and operated in accordance with NERC Reliability Standards and Western Electricity Coordinating Council (WECC) Regional Reliability Standards and Criteria. In order to make this possible, WECC staff and members perform power flow and stability studies using computer models of the power system. The accuracy of these models is a key factor in preserving system reliability and affects significant economic decisions regarding system expansion and operation while also meeting the requirements of WECC s annual system study program, WECC regional studies, and WECC path rating studies. Since the decisions based on the results of system studies are of such importance, system representation must be sufficiently accurate to ensure that system parameters measured in simulating a disturbance are close to WESTERN ELECTRICITY COORDINATING COUNCIL 155 North 400 West, Suite 200 Salt Lake City, Utah

2 MOD-(11 and 13)-WECC-CRT-1.1 Steady State and Dynamic Data Requirements Page 2 of 14 those that would be measured on the actual power system under the same conditions.

3 MOD-(11 and 13)-WECC-CRT-1.1 Steady State and Dynamic Data Requirements Page 3 of 14 B. Requirements and Measures WR1. The Reliability Assurer (WECC) shall verify the System Review Work Group (SRWG), or its successor, develops and documents both comprehensive steady-state and comprehensive dynamic data requirements, and reporting procedures for the Western Interconnection to meet the steady-state data requirements listed in Attachment A (Steady State Data Requirements) and dynamic data requirements list in Attached B (Dynamic Data Requirements) of this document. WM1. The Reliability Assurer (WECC) shall have and produce upon request, evidence that it verified SRWG, or its successor, developed and documented both comprehensive steady-state and comprehensive dynamic data requirements, and reporting procedures for the Western Interconnection to meet the steady-state data requirements listed in Attachment A and dynamic data requirements listed in Attachment B of this document, as required in WR1 above. Evidence may include, but is not limited to, production of documentation from the SRWG, or its successor, indicating the required development and documentation was completed. WR2. The Reliability Assurer (WECC) shall designate the SRWG, or its successor, as the entity responsible to develop for the Western Interconnection any additional steady-state and dynamic data requirements not otherwise specified by NERC. WM2. The Reliability Assurer (WECC) shall have and produce upon request, evidence that it designated the SRWG, or its successor, as the entity responsible to develop for the Western Interconnection any additional steady-state and dynamic data requirements, as required in WR2 above, not otherwise specified by NERC. Evidence may include, but is not limited to, any form of documented or recorded communication between WECC Staff and the chair of the SRWG, or its successor, indicating the designation was made. WR3. The Reliability Assurer (WECC) shall designate the Planning Coordination Committee, or its successor, as the entity responsible to approve the development of both comprehensive steady-state and comprehensive dynamic data requirements, and reporting procedures, within the Western Interconnection, as developed by the SRWG, or its successor. WM3. The Reliability Assurer (WECC) shall produce evidence that it designated the Planning Coordination Committee, or its successor, as the entity responsible to approve the development of both steady-state and comprehensive dynamic data requirements, and reporting procedures, within the Western Interconnection, as developed by the SRWG, or its successor, as required in WR3 above. Evidence of the Planning Coordination Committee s approval of the SRWG s development of the steady-state and dynamic data requirements and reporting procedures, may include, but is not limited to, production of any form of documented or recorded communication between the Reliability Assurer (WECC) and the Chair of the Planning Coordination Committee indicating the required content.

4 MOD-(11 and 13)-WECC-CRT-1.1 Steady State and Dynamic Data Requirements Page 4 of 14 WR4. The Reliability Assurer (WECC) shall review this document, no less than each five years, by causing to be filed a WECC Standard Authorization Request Form (or its successor), for the purpose of reviewing the data requirements and reporting procedures addressed herein. WM4. The Reliability Assurer (WECC) shall have and provide upon request, evidence that it reviewed this document, no less than each five years, by causing to be filed a WECC Standard Authorization Request Form (or its successor), for the purpose of reviewing the data requirements and reporting procedures addressed herein, as required in WR4. Evidence may include, but is not limited to, production of the WECC Standard Authorization Form (or its successor) indicating that the scope of the request included review of the data requirements and reporting procedures contained in this document. (The five-year period for review begins on the Effective Date of this document.) WR5. The Reliability Assurer (WECC) shall post on the WECC Web site each steady-state and dynamic data request required by this document, to include, at a minimum, each of the following elements: 5.1. A statement of the purpose for which the case will be developed 5.2. The case year 5.3. The case season 5.4. The case load, generation and interchange requirements 5.5. Required due dates for data submitted to the Reliability Assurer (WECC). WM5. The Reliability Assurer (WECC) shall have and produce upon request, evidence that it posted on the WECC Web site, each steady-state and dynamic data request required by this document, to include each of the elements listed in WR5 above. Evidence may include, but is not limited to, documentation from the WECC Web site or other search engine indicating the posting took place to include the required content. WR6. The Reliability Assurer (WECC) shall post on the WECC Web site each steady-state and dynamic data request, as referred to in WR5 above, at least eight weeks prior to the required due dates for data submittal back to the Reliability Assurer (WECC). WM6. The Reliability Assurer (WECC) shall have and produce upon request, evidence that it posted, on the WECC Web site, each steady-state and dynamic data request, as referred to in WR5 above, at least eight weeks prior to the required due dates for data submittal back to the Reliability Assurer (WECC), as is required in WR6. Evidence may include, but is not limited to, documentation from the WECC Web site or other search engine indicating the posting took place to include the required content. WR7. Each Transmission Owner, Transmission Planner, Generator Owner and Resource Planner as specified in the Functional Entity column of Attachment A of this document, shall submit to the Reliability Assurer (WECC) the data specified in the Data Required column of

5 MOD-(11 and 13)-WECC-CRT-1.1 Steady State and Dynamic Data Requirements Page 5 of 14 Attachment A of this document, in accordance with the due dates for data submittal to the Reliability Assurer (WECC) specified in WR5 above. WM7. Each Transmission Owner, Transmission Planner, Generator Owner and Resource Planner as specified in the Functional Entity column of Attachment A of this document, shall have and produce upon request, evidence that data was submitted to the Reliability Assurer (WECC), as required in WR7 above, reflecting the Data Required specified in the Data Required column of Attachment A of this document, in accordance with the due dates for data submittal specified in WR5 above. Evidence shall include, but not be limited to, production of or other notification process communicated to the Reliability Assurer (WECC) indicating inclusion of the data specified from the Data Required column of Attachment A and that the date dispatched met the required due date. WR8. Each Transmission Owner, Transmission Planner, Generator Owner, and Resource Planner as specified in the Functional Entity column of Attachment B of this document, shall submit to the Reliability Assurer (WECC) the data specified in the Data Required column of Attachment B of this document, in accordance with the due dates for data submittal to the Reliability Assurer (WECC) specified in WR5 above. WM8. Each Transmission Owner, Transmission Planner, Generator Owner, and Resource Planner as specified in the Functional Entity column of Attachment B of this document, shall have and produce upon request, evidence, as required in WR8 above, that data was submitted to the Reliability Assurer (WECC) reflecting the information specified in the Data Required column of Attachment B of this document, in accordance with the due dates for data submittal specified in WR5 above. Evidence shall include, but not be limited to, production of or other notification process communicated to the Reliability Assurer (WECC) indicating inclusion of the data specified from the Data Required column of Attachment B and that the date dispatched met the required due date. A report of No change is acceptable where there is no new or different data to report. WR9. Each Generator Owner shall submit to the Reliability Assurer (WECC), the generator data required on Attachments A and B in accordance with the following size-threshold criteria: If the individual generator unit capacity is 10 MVA or larger, and is connected to the WECC transmission system at 60 kv or higher, then steady-state data shall be submitted for each generator in accordance with the requirement stated at Attachment A, NERC Requirement, R1.2, and dynamics data shall be submitted for each generator in accordance with all of Attachment B (excluding Attachment B, NERC Requirement, R1.4. ). If the aggregated generator unit capacity is 20 MVA or larger, and is connected to the WECC transmission system at 60 kv or higher, and is not a collector based generation facility, then steady-state data shall be submitted for each individual generator in

6 MOD-(11 and 13)-WECC-CRT-1.1 Steady State and Dynamic Data Requirements Page 6 of 14 accordance with Attachment A, NERC Requirement, R1.2, and dynamics data shall be submitted for each generator in accordance with all of Attachment B, excluding Attachment B, NERC Requirement, R1.4.. (Wind and solar farms are an example of a collector-based generation facility.) If the aggregated generation capacity is 20 MVA or larger, and is connected to the WECC transmission system at 60 kv or higher, and is a collector based generation facility, then steady-state data shall be submitted in accordance with Attachment A, NERC Requirement, R1.2, and dynamics data shall be submitted in accordance with all of Attachment B (excluding Attachment B, NERC Requirement, R1.4. ) for the aggregated generation capacity as a single-unit generator model. (Wind and solar farms are an example of a collector-based generation facility.) All other generating facilities shall either be netted with bus load and steady-state data shall be submitted in accordance with Attachment A, NERC Requirement, R1.1b; or, steady-state data shall be submitted in accordance with Attachment A, NERC Requirement R1.2. WM9. Each Generator Owner shall have and produce upon request, evidence that it submitted to the Reliability Assurer (WECC) the generator data required on Attachments A and B, in accordance with the threshold(s) specified in WR9 above. Evidence may include, but is not limited to, production of the data that was submitted reflecting the information specified in the Data Required column of Attachment A and Attachment B of this document in accordance with the threshold(s) specified in WR9 above. WR10. Each Transmission Owner, Transmission Planner, Generator Owner and Resource Planner shall submit steady-state data in accordance with Attachment A, and dynamic data in accordance with Attachment B that is consistent with submitted steady-state data. WM10. Each Transmission Owner, Transmission Planner, Generator Owner and Resource Planner shall have and produce upon request, evidence that it submitted steadystate data in accordance with Attachment A, and dynamic data in accordance with Attachment B that is consistent with submitted steady-state data, as required in WR10. (For example, if Attachment A called for Bus Name and Attachment B also calls for the same Bus Name, the data submitted for both must be identical i.e. consistent.) WR11. The Reliability Assurer (WECC) shall post on the WECC Web site the approved solved and solvable base-case data and supporting documentation. WM11. The Reliability Assurer (WECC) shall have and produce upon request, evidence that it posted on the WECC Web site the approved solved and solvable base-case data and supporting documentation for the posted base-case, as required in WR11 above. Evidence may include, but is not limited to, documentation from the WECC Web site

7 MOD-(11 and 13)-WECC-CRT-1.1 Steady State and Dynamic Data Requirements Page 7 of 14 or other search engine indicating the posting took place to include the required content.

8 MOD-(11 and 13)-WECC-CRT-1.1 Steady State and Dynamic Data Requirements Page 8 of 14 Version History Version Date Action Change Tracking 1 June 25, 2013 WECC Board of Directors Approved Developed as WECC Initial version 1.1 January 28, 2016 Errata A missing space was added to the Purpose statement. To eliminate ambiguity and allow the document to remain current with categorization changes, the lower-case use of the term criterion was replaced with the lower-case term document in the Purpose statement, WR1/WM1, WR4/WM4, WR5/WM5, WR7/WM, WR8/WM8, WM9, and, Attachments A and B. In WR4 and WM4, the phrase WECC Standards/Regional Criterion Request Form was updated to WECC Standard Authorization Request Form to reflect the existing form title, and the free-standing term Request was replaced with the lower case use as Request is not a defined term (typo). 1.1 April 1, 2016 No Change Converted to new template 1.1 June 15, 2016 WSC Approved Retirement The WECC-0119 drafting team requested retirement of MOD-(11 and 13)-WECC-CRT-1.1, Steady State and Dynamic Data Requirements (WECC MOD CRT) coincide with the July 1, 2016 effective date of NERC Standard MOD-032-1, Data for Power System Modeling and Analysis (MOD-032) because the requirements of the WECC MOD CRT are either no longer required or have been moved to MOD July 1, 2016 Retired No further activity The Procedures grant the WSC the authority to retire the WECC CRT on its own initiative when the reliability-related substance is addressed in a separate NERC Standard and retirement of the WECC CRT would not cause a reliability Gap. The MOD-032 Background Section as approved by FERC, MOD-032 states: MOD is a consolidation and replacement of [MOD- 011 and MOD-013] and it requires data submission by applicable data owners to their respective Transmission Planners and Planning Coordinators to support the Interconnection-wide case building process in their Interconnection. (Emphasis added.) Disclaimer

9 MOD-(11 and 13)-WECC-CRT-1.1 Steady State and Dynamic Data Requirements Page 9 of 14 WECC receives data used in its analyses from a wide variety of sources. WECC strives to source its data from reliable entities and undertakes reasonable efforts to validate the accuracy of the data used. WECC believes the data contained herein and used in its analyses is accurate and reliable. However, WECC disclaims any and all representations, guarantees, warranties, and liability for the information contained herein and any use thereof. Persons who use and rely on the information contained herein do so at their own risk.

10 MOD-(11 and 13)-WECC-CRT-1.1 Steady State and Dynamic Data Requirements Page 10 of 14 Attachments Attachment A Steady State Data Requirements (SSDR) The WECC Steady State Data Requirements (SSDR) contains the minimum acceptable steady state data requirements to meet the requirements of NERC Standard Requirements R1.1 through R1.7. Each Responsible Entity listed in the Responsible Entity column below shall submit the below requested information in accordance with this document. The System Review Work Group may add to but not subtract from this list upon approval by the Planning Coordination Committee. The below minimum list is established by NERC Standard. NERC Requirement Data Required Functional Entity The below stated Functional Entity shall provide the steady state data described in the Data Required column. R1.1a R1.1b R1.2 Bus (substation): name and nominal voltage supplied per Reliability Standards MOD-016-0, MOD-017-0, and MOD-020-0), and location. Bus (substation): electrical demand supplied (consistent with the aggregated and dispersed substation demand data supplied per Reliability Standards MOD-016-0, MOD-017-0, and MOD-020-0). Generating Units (including synchronous condensers, pumped storage, etc.): location, minimum and maximum Ratings (net Real and Reactive Power), regulated bus and voltage set point, and equipment status. transmission facility represented and each Generator Owner of the Each Resource Planner of the transmission facility represented and each Generator Owner of the transmission facility represented and each Generator Owner of the R1.3 AC Transmission Line or Circuit (overhead and underground): nominal voltage, impedance, line charging, Normal and Emergency Ratings transmission facility represented and each Generator Owner of the

12 MOD-(11 and 13)-WECC-CRT-1.1 Steady State and Dynamic Data Requirements Page 12 of 14 Attachment B Dynamic Data Requirements (DDR) The WECC Dynamic Data Requirements (DDR) contains the minimum acceptable dynamic data requirements to meet the requirements of NERC Standard Requirements R1.1 through R1.5. Each Responsible Entity listed in the Responsible Entity column below shall submit the below requested information in accordance with this document. The System Review Work Group may add to but not subtract from this list upon approval by the Planning Coordination Committee. The below minimum list is established by NERC Standards. NERC Requirement Data Required Functional Entity R1.1 Design data shall be provided for new or refurbished excitation systems (for synchronous generators and synchronous condensers) at least three months prior to the installation date. The below stated Functional Entity shall provide the dynamic data described in the Data Required column. transmission facility represented and each Generator Owner of the R1.1.1 If design data is unavailable from the manufacturer 3 months prior to the installation date, estimated or typical manufacturer s data, based on excitation systems of similar design and characteristics, shall be provided. transmission facility represented and each Generator Owner of the R1.2 Unit-specific dynamics data shall be reported for generators and synchronous condensers (including, as appropriate to the model, items such as inertia constant, damping coefficient, saturation parameters, and direct and quadrature axes reactances and time constants), excitation systems, voltage regulators, turbine-governor systems, power system stabilizers, and other associated generation equipment. transmission facility represented and each Generator Owner of the

13 MOD-(11 and 13)-WECC-CRT-1.1 Steady State and Dynamic Data Requirements Page 13 of 14 R1.2.1 Estimated or typical manufacturer s dynamics data, based on units of similar design and characteristics, may be submitted when unit-specific dynamics data cannot be obtained. In no case shall other than unit-specific data be reported for generator units installed after transmission facility represented and each Generator Owner of the R1.2.2 The Interconnection-wide requirements shall specify unit size thresholds for permitting: 1) The use of non-detailed vs. detailed models, 2) The netting of small generating units with bus load, and 3) The combining of multiple generating units at one plant. Refer to WR9 above. (The Functional Entity as identified in WR9 is the Reliability Assurer.) R1.3 Device specific dynamics data shall be reported for dynamic devices, including, among others, static VAR controllers, high voltage direct current systems, flexible AC transmission systems, and static compensators. transmission facility represented and each Generator Owner of the R1.4 Dynamics data representing electrical Demand characteristics as a function of frequency and voltage. Transmission Owner R1.5 Dynamics data shall be consistent with the reported steady-state (power flow) data supplied per Reliability Standard MOD-010 Requirement 1. Refer to WR10 above.

14 MOD-(11 and 13)-WECC-CRT-1.1 Steady State and Dynamic Data Requirements Page 14 of 14 Rationale A Rationale section is optional. If Rationale Boxes were used during the development of this project, the content of those boxes appears below. This document was developed on the then-existing versions of the below listed documents: MOD-11-0 Regional Steady State Data Requirements and Reporting Procedures MOD-13-1 RRO Dynamic Data Requirements and Reporting Procedures WECC Data Preparation Manual System Review Work Group (SRWG) Handbook

California Independent System Operator & Hetch Hetchy Water and Power of the City and County of San Francisco Joint Transmission Planning Base Case Preparation Process This is a living document. Please

Unofficial Comment Form Project 2007-11 Disturbance Monitoring Please DO NOT use this form for submitting comments. Please use the electronic form to submit comments on the Standard Authorization Request

This standard was reviewed and approved by key managers on. Officer approval of this revision is not required. 1.0 SCOPE 1.1 This guide applies to the interconnection of a generating plant with the Oncor

The PSNsim is hardware simulator that simulates all parts of power system from generation to utilization. The PSNsim is a scaled down model of the real power system that provides an experimental environment

Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Description of Current Draft

Improvement and Power District Original Sheet No. F-1 ATTACHMENT F Form of Service Agreement for Wholesale Network Integration Transmission Service 1.0 This Form of Service Agreement for Wholesale Network

SPP RTO Compliance Forum Western Area Power Administration March 11, 2015 Mark Buchholz WAPA Upper Great Plains Region Compliance Manager What is Western? One of four Power Marketing Administration within

Summary of FERC Order No. 791 On November 22, 2013, the Federal Energy Regulatory Commission ( FERC or Commission ) issued Order No. 791 adopting a rule that approved Version 5 of the Critical Infrastructure

A. Introduction 1. Title: Cyber Security Personnel & Training 2. Number: CIP-004-6 3. Purpose: To minimize the risk against compromise that could lead to misoperation or instability in the Bulk Electric

LAB1 INTRODUCTION TO PSS/E EE461: POWER SYSTEMS COLORADO STATE UNIVERSITY PURPOSE: The purpose of this lab is to introduce PSS/E. This lab will introduce the following aspects of PSS/E: Introduction to

THE INTERCONNECTION HANDBOOK Southern California Edison Company Rev. 8 This document is controlled by the originating SCE T&D organization. When downloaded and printed, this document becomes UNCONTROLLED,

NERC Cybersecurity Compliance Stephen M. Spina February 26, 2013 www.morganlewis.com Cyber Attacks on Energy Infrastructure Continue According to DHS, the energy sector was the focus of 40% of the reported

POWER SYSTEM SECURITY CONCEPTS 1.1 INTRODUCTION The Power System needs to be operationally secure, i.e. with minimal probability of blackout and equipment damage. An important component of power system

Grid Operations - Program 39 Program Description Program Overview In many ways, today's power system must be operated to meet objectives for which it was not explicitly designed. Today's transmission system

A. Introduction 1. Title: Cyber Security Personnel & Training 2. Number: CIP-004-5.1 3. Purpose: To minimize the risk against compromise that could lead to misoperation or instability in the BES from individuals

Categorizing Cyber Systems An Approach Based on BES Reliability Functions NERC Cyber Security Standards Drafting Team for Order 706 06/15/2009 Team CATEGORIZING CYBER SYSTEMS: AN APPROACH BASED ON IMPACT

Exhibit RMP (RTL-1) BEFORE THE PUBLIC SERVICE COMMISSION OF THE STATE OF UTAH ROCKY MOUNTAIN POWER Exhibit Accompanying Direct Testimony of Rick T. Link May 31, 2017 Pre-Issuance Bidders Conference Presentation

July, 2015 Copies of this document are available for free in electronic format at the following website: www.rainforest-alliance.org Please send your comments or suggestions concerning this document to

Assessing Reliability in the Western Interconnection Vijay Satyal and Byron Woertz, WECC 2 Overview Who/What is WECC? Current state of the Interconnection Assessing reliability 2017 2034 Stakeholder collaboration

TransWest Express and Gateway South Co-developed by four leading entities: Arizona Public Service PacifiCorp National Grid Wyoming Infrastructure Authority Regional Stakeholder Meeting January 23, 2008

Guidelines for Submitting NERC Reliability Standards Required Documents to the SPP Reliability Coordinator and the SPP Balancing Authority Version 1 Revision History Version Effective Date Summary of Revisions

Document E203 2013 Building Information Modeling and Digital Data Exhibit This Exhibit dated the day of in the year is incorporated into the agreement (the Agreement ) between the Parties for the following

Outage Coordination External Workshop Jason Ausmus Manager, Operations Planning Outage Coordination Course 8 total CEHs for this course To get the CEHs, you will need to: o Be present for the entire class

Protection System Misoperation Data Collection Industry Comments on the Draft Section 1600 Data Request July 30, 2014 Question 1 Is the data requested similar in substance and form to the data presently

Council on Dairy Cattle Breeding General Auditing Guidelines Effective January 1, 2010 Version 10.0 The purpose of this manual is to ensure the accuracy and uniformity of all records included in the national

A guide on PowerWorld Simulator ver. 12.0 This tutorial has been developed to aid the undergraduate and graduate students at the University of Cyprus to learn the basic features of PowerWorld. It is not