Upload
kumar-amit
View
230
Download
0
Embed Size (px)
Citation preview
7/29/2019 Dppm v6 Without Redline
1/23
WECC Data Preparation
ManualFor Power Flow Base Cases and
Dynamic Stability Data
July 2009
REV. 6
7/29/2019 Dppm v6 Without Redline
2/23
I. INTRODUCTION.................................................................................................................................................................................................................1
7/29/2019 Dppm v6 Without Redline
3/23
7/29/2019 Dppm v6 Without Redline
4/23
Reporting Procedures
FAC-009-1: Establish and Communicate Facility Ratings
III. Data Requirements and Reporting Procedures
A. Data Requirements
The WECC staff, in concert with the System Review Work Group (SRWG) of the
Technical Studies Subcommittee (TSS), and other entities as appropriate, is
responsible for maintaining the appropriate DPM and managing the collection of thesteady-state and dynamic system modeling data required to comply with applicable
NERC Standards and Measurements. The data are collected periodically over a
calendar-year and solved base cases are maintained in a data base library which isavailable to all WECC members and currently located at
http://www.wecc.biz/committees/StandingCommittees/PCC/TSS/BaseCases/Pages/default.aspx..
The current base case compilation schedule is made available to WECC members inthe PCC Handbook under Section VI, TSS Activities. Section VI of the PCC
Handbook is available on the WECC web site athttp://www.wecc.biz/committees/StandingCommittees/PCC/TSS/SRWG/Shared
%20Documents/Forms/AllItems.aspx, under Data Compilation Schedules.
Facility owners are responsible for submitting the pertinent data on their solely- or
jointly-owned Facilities in a timely manner and in accordance with the current year
WECC Annual Study Program schedule, and the WECC Generating Unit ModelValidation Policy. Facility owners are required to comply with the following data
collection requirements and guidelines related to the accurate modeling of generation,transmission and load in WECC base cases.
WECC maintains a Master Dynamics File (MDF) for use in all stability simulations.The MDF contains model data for all dynamic devices in the WECC system Facility
http://www.wecc.biz/committees/StandingCommittees/PCC/TSS/SRWG/Shared%20Documents/Forms/AllItems.aspxhttp://www.wecc.biz/committees/StandingCommittees/PCC/TSS/SRWG/Shared%20Documents/Forms/AllItems.aspxhttp://www.wecc.biz/committees/StandingCommittees/PCC/TSS/SRWG/Shared%20Documents/Forms/AllItems.aspxhttp://www.wecc.biz/committees/StandingCommittees/PCC/TSS/SRWG/Shared%20Documents/Forms/AllItems.aspx7/29/2019 Dppm v6 Without Redline
5/23
B. Reporting Procedures
1. Steady State Data
WECC base cases are compiled relative to a base case compilation schedule that
is prepared each year and included in Section VI of the PCC Handbook (link isincluded in Section A above).
On the appropriate date, a data request letter will be prepared; specifying the next
case that is to be compiled. This letter will be distributed via email to the
Technical Studies Subcommittee (TSS) and the System Review Work Group(SRWG). The data request letter outlines desired system conditions, such as year
and season being modeled, load and generation levels, and path flow levels (if
requested). Steady state data, along with corresponding dynamics data, isrequested for the base case and must meet data submittal due dates from the base
case compilation schedule.
Facility owners are responsible to test and validate steady state power flow data
for any of their solely- or jointly-owned facilities to be modeled in power flowcases. Facility owners shall provide test and validation reports and steady state
power flow data to its Transmission Planner. Transmission Owners,Transmission Planners, Generator Owners and Resource Planners are responsible
to submit the steady state data to Area Coordinators without delay. AreaCoordinators are responsible to compile the initial power flow base case and
balance the in-area loads and resources and coordinate area interchange with
neighboring areas. Area Coordinators are also responsible to submit the initialsolved power flow base case with any updated and/or new dynamics data received
to WECC Staff on schedule. Data submittals are required in either GE PSLF epc
or sav file format in the version of the GE PSLF program currently accepted forproduction use. Data submittals shall be submitted to the WECC staff via email
7/29/2019 Dppm v6 Without Redline
6/23
Facility owners are responsible to test and validate dynamics data for any of their
solely- or jointly owned dynamic equipment to be modeled in power flow cases.
Facility owners shall provide test and validation reports to its TransmissionPlanner. Transmission Planner shall collect facility data and model data validation
reports from facility owners. Transmission Planner shall verify that the WECC-
approved model parameters provided by the facility owners are adequatelyvalidated by reviewing the test and validation reports; but Transmission Planner
shall not be responsible for any failure by facility owner to adequately validate
any WECC-approved model parameters provided by facility owner to theTransmission Planner. Transmission Planners shall submit to the WECC Staff
any dynamics data received from the facility owner for any new dynamicequipment to be modeled in power flow cases.
Dynamics data updates are also submitted via the WECC generator testingprogram. For the roles and responsibilities of the Generator Owner, the
Transmission Planner, and WECC, see the WECC Generating Unit Model
Validation Policy under 2006 Generator Test Policy in:http://www.wecc.biz/library/WECC%20Documents/Forms/AllItems.aspx?RootFolder=%2flibrary%2fWECC%20Documents%2fDocuments%20for%20Generators%2fGenerator%20Testing
%20Program&FolderCTID=&View=
%7bAF8E6257%2d3EB9%2d4A21%2d8853%2d6477737956B4%7d.
The most recent version of the MDF is available in the current year, and the GE
PSLF library at the following link:
http://www.wecc.biz/committees/StandingCommittees/PCC/TSS/BaseCases/Pages/default.aspx
IV. Steady State Power Flow Data Requirements
In order to provide consistency in data submittals and help avoid potential solutionproblems WECC members shall follow the guidelines below to the maximum extent
http://www.wecc.biz/committees/StandingCommittees/PCC/TSS/BaseCases/Pages/default.aspx%20http://www.wecc.biz/committees/StandingCommittees/PCC/TSS/BaseCases/Pages/default.aspx%207/29/2019 Dppm v6 Without Redline
7/23
5. DC Bus numbering should be coordinated with WECC Staff prior to model
submission.
B. Zones and facility owner numbers should be provided for each bus. All zone and
owner numbers used must be entered in the zone and owner tables. Generation
1. Generating Units (including synchronous condensers, pumped storage, etc.) shall
include: connection point, minimum and maximum Ratings (net Real andReactive Power), regulated bus and voltage set point, and equipment status.
2. Load netting of generation in power flow data should be minimized. If the
aggregate sum of generation on a bus exceeds 10 MVA it should not be netted.The total netted generation in an area should not exceed 5% of the areas totalgeneration.
3. Data entered for the power flow Pmax should accurately reflect the capability of
the unit, but under no circumstances should it be greater than the maximum
capability of the turbine, as represented by Pmax parameter in the dynamicturbine-governor model.Exceptions may be allowed for de-rated generators.
4. Generators with single unit Capacity of 10MVA or higher or facilities withaggregate capacity of 20MVA and larger and which are connected to the
transmission system by generator step-up transformer(s) to 60 kV or highervoltage shall be modeled individually with their respective step-up
transformers.
Collector based systems such as wind & solar farms connected to the transmission
system may be aggregated through 1) an equivalent generator, 2) a low voltage to
intermediate voltage transformer, 3) an equivalent collector circuit, and 4) thesubstation transformer between the collector and the transmission bus of 60kV or
a higher voltage. Reactive devices should be represented at the appropriatevoltage buses. Owners of any other generators determined by WECC, and the
7/29/2019 Dppm v6 Without Redline
8/23
C. Transmission Lines
1. AC Transmission Line or Circuit (overhead and underground)
requirements shall include: nominal voltage, impedance, line charging, Normaland Emergency Ratings (consistent with methodologies defined and Ratings
supplied per the current Reliability Standard FAC-008-0 and FAC-009-0)
equipment status, and metering locations.
2. DC Transmission Line (overhead and underground) requirements shallinclude at a minimum: line parameters, Normal and Emergency Ratings, control
parameters, rectifier data, and inverter data.
3. Transmission facilities represented should be consistent with current
facility owners plans and should represent the system under normal conditionsunless otherwise stated in the case description sheet.
4. Equivalent transmission system representations are discouraged.
However, any equivalency should yield almost identical performance in both
static and dynamic results compared to full representation. All equivalentbranches must have a circuit id of eq or 99. Line ratings should be provided
for any equivalent circuits. If no rating is available, then 9999 should be used.5. All transmission lines 115-kV and above should be modeled explicitly
except for very low impedance lines (see Item 10), the modeling of which hascaused numerical problems in running the power flow program. Significant
looped transmission less than 115-kV should also be modeled.
6. Transmission paths identified in the "Path Rating Catalog" should be
modeled in sufficient detail, such that users can calculate the flow on the path.
The power flow case should also accurately represent conditions that are used todetermine path ratings.
7. Facilities out of service for voltage control should be noted. Also,
7/29/2019 Dppm v6 Without Redline
9/23
11. The appropriate ratings of all facilities are required to determine if study
results meet the requirements of WECC disturbance-performance table and
NERC Standard TPL-001-0 Table 1 (Transmission System Standards Normaland Emergency Conditions). This includes but is not limited to system elements
such as transmission lines, series capacitors, and transformers. The rating of a
system facility (e.g., transmission line, transformer, etc.) shall not exceed therating of the most limiting series element in the facility, including terminal
connections and associated equipment. In cases where protection systems and
control setting constitute a loading limit on a facility, this limit shall become therating for that facility. (See NERC Standards FAC-008-1, R1.1)
D. Transformers
1. Transformer (voltage and phase-shifting) requirements shall include: nominal
voltages of windings, impedance, tap ratios (voltage and/or phase angle or tap
step size), regulated bus and voltage set point, Normal and Emergency Ratings
(consistent with methodologies defined and Ratings supplied per ReliabilityStandard FAC-008-0 and FAC-009-0.), and equipment status.
2. Transformers for which partial or no Tap Changing Under Load (TCUL) data hasbeen provided should not be modeled as TCUL transformers. The GE PSLF
program accepts partial TCUL data as input, but treats the transformer as a fixedtap transformer during solution. Problems may occur when the data records for
these transformers with partial data are converted to PTI.
3. For TCUL transformers, the step size reported should be small enough or the
voltage bandwidth large enough that the adjustment of a TCUL does not result in
the voltage at the controlled bus moving completely through the reportedbandwidth, thus causing solution problems at the bus.
4. For TCUL transformers, the maximum tap reported should be greater than the
minimum tap and the maximum step reported should be greater than the minimum
7/29/2019 Dppm v6 Without Redline
10/23
4. Loads of differing ownership, but at the same bus, can be represented
by separate load records with unique IDs. However, all loads at the same bus
must be specified as being in the same area as the bus.5. Generator station service load should be modeled explicitly and given
an id of SS to make it distinguishable from other loads.
F. Fixed Reactive Elements
1. Reactive Compensation (shunt and series capacitors and reactors)
requirements shall include: nominal Ratings, impedance, connection point, and
controller device.2. All existing fixed shunt elements should be modeled explicitly. If theshunt is not in service, then the status should be set to zero. This allows members
who may be unfamiliar with the number and amount of shunt devices in an area to
make voltage adjustments in that area if the need arises.
3. Fixed shunt elements that are directly connected to abus should be represented as bus shunts.
4. Fixed shunt elements that directly connect to and switch
with a branch should be represented as line shunts.
G. Switched Reactive Devices
1. Reactive Compensation (shunt and series capacitors and reactors)
requirements shall include: nominal Ratings, impedance, connection point, andcontroller device.
2. Switched shunt elements should be modeled explicitly. All availableswitchable elements should be listed on the data record.
3. When listing switchable elements in the data record, reactors should be
7/29/2019 Dppm v6 Without Redline
11/23
1. Interchange Schedules shall include existing and future Interchange Schedules
and/or assumptions.
2. All transactions between areas must be coordinated between areas.
3. Whenever reported interchanges between areas differ by more than 10 MW, theArea Coordinator for each area will be contacted. The Area Coordinators must
work out the discrepancy and report their solution to the WECC staff. For
reported interchanges between areas that differ by 10 MW or less, SRWG agreedthat the WECC staff may modify one or both of the interchange schedules so that
they agree.
4. The sum of net area interchanges for all areas must net to 0.
5. The total area interchange tolerance for an area should be 1.0.
6. Interchange schedules should reflect the objectives of the case. In particular, they
must include potential economy transfers and not be limited to contractual oranticipated commitments. Target levels specified refer to either actual or
scheduled flows.
J. Master Tie Line File
1. The Master Tie Line file is maintained by the WECC staff.
2. The Master Tie Line file is used in the compilation of all WECC base cases.
3. Efforts should be made to include in-service and out-of-service dates to all tie
lines so that the proper status of the tie line is easily determined.
4. Only tie line changes approved by the Area Coordinators from both areas
connected by the tie line will be made to the file.
5. Area numbers representing a member area should not be changed.
In addition to tie line information the Master Tie Line file contains area number zone
7/29/2019 Dppm v6 Without Redline
12/23
.A General Dynamic Modeling
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 reactance
and time constants), excitation systems, voltage regulators, turbine-governor systems,
power system stabilizers, and other associated generation equipment.
Estimated or typical manufacturers dynamics data, based on units of similar designand 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 1990
Approved dynamics models (including renewable generation) as recommended by theWECC MVWG to be used to represent dynamic equipment to be modeled in power
flow cases are provided in the Approved Dynamic Model Library document
(http://www.wecc.biz/library/default.aspx?RootFolder=%2flibrary%2fWECC%20Documents%2fDocuments%20for%20Generators%2fGenerator%20Testing
%20Program&FolderCTID=&View=%7b8D18396E%2d7F8B%2d4472%2dAB30%2d18D2A9576FF0%7d), and conform to the WECC Dynamic
Modeling Procedure(http://www.wecc.biz/committees/StandingCommittees/PCC/TSS/MVWG/Shared
%20Documents/WECC%20Dynamic%20Modeling%20Procedure.pdf). and conform
to the WECC Dynamic Modeling Procedure. Requests for new models that are not inthe Approved Dynamic Model Library list shall follow the WECC Dynamic
Modeling Procedure.
Where there is a difference between the requirements of this document and the
WECC Generating Unit Model Validation Policy, the WECC Generating Unit ModelValidation Policy shall preside.
7/29/2019 Dppm v6 Without Redline
13/23
6 PSS data should be submitted for all generators that have PSS and suitable
excitations systems, as defined in the report Criteria to Determine Excitation Systems
Suitability for PSS dated December 1992. The complete WECC Policy Statement on PowerSystem Stabilizers is available in the PCC Handbook on the WECC web site athttp://www.wecc.biz/library/WECC%20Documents/Documents%20for%20Generators/WECC_PSS-%20Policy-
Statement.pdf. Periodic testing and/or model validation of generating units in accordance to WECC Policies and Standards is required to facilitate the best
representation possible. See WECC Generating Unit Model Validation Policy.
.C Loads
1. Dynamics data representing electrical Demand characteristics as a function of
frequency and voltage shall be included.2. Dynamics data shall be consistent with the reported steady-state (power flow)
data supplied.
3. Explicit modeling representing voltage and frequency characteristics is
encouraged for each individual load; however, default zone or area records can be
utilized for buses not explicitly defined.
4. In addition to individual load modeling information provided for each load, a
default area load representation record should be provided for each area. Thiswill cover any new load that may have been added to the powerflow without
explicit load modeling information provided for the Master Dynamics File(MDF). This is to avoid the load representation defaulting to constant power (GE
program default).
5. If actual dynamic load characteristics are not available, load should be modeled as
constant current P, and constant impedance Q.
6. Default 20% induction motor models are created for every in-service load in the
power flow greater than 5 MW at load buses and 80 MW at generator buses. If a
different representation is desired for any load(s), it must be submitted to the
ff f i l i i h i il ( )
7/29/2019 Dppm v6 Without Redline
14/23
2. The pick-up and delay setting for each stage must be coordinated with the
previous stage.
3. Pertinent load data must be in the Master Dynamics File (MDF).
.F DC Lines, SVC, and DVAR systems
1. 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.
2. To the maximum extent possible, DC lines and SVC systems should be modeled
to accurately reflect actual system performance.3. DC Bus numbering should be coordinated with WECC Staff prior to model
submission.
VI. Facility Rating Requirements
Facility owners are responsible for submitting the applicable rating data to WECC Staff and
Area Coordinators. Seasonal variations in ratings shall be included as appropriate. Theratings shall be developed using the facility owners current facility ratings methodology that
was documented to meet NERC Reliability Standards FAC-008-1.
Complete facility rating data shall be provided on time, in accordance with the current year
WECC Annual Study Program schedule.
A. WECC Requirements
1. The appropriate ratings of all facilities are required to determine if study results meet
the requirements of the WECC disturbance-performance table and NERC Reliability StandardsTPL-001-0 Table 1 (Steady State Performance)... This includes but is not limited to system
elements such as transmission lines, series capacitors, and transformers.
7/29/2019 Dppm v6 Without Redline
15/23
3. The rating of a system facility (e.g. transmission line, transformer, etc.) shall notexceed the rating of the most limiting series element in the circuit or path of the
facility, including terminal connections and associated equipment. (See NERC
Standards FAC-008-1, R1.1).
4. In cases where protection systems and control settings constitute a loading limit on afacility, this limit shall become the rating for that facility.
5. Ratings of jointly-owned facilities shall be coordinated and provided on a consistent
basis.
7/29/2019 Dppm v6 Without Redline
16/23
Appendix I
LATE DATA PROCEDURE
The objective of the Late Data Procedure is to preserve the original schedule for the development
of base cases in accordance with each year's Data Bank Compilation Schedule and the CaseDescription sheet in the data request letter for each case. The Late Data Procedure describes
Area Coordinator and Staff data submittal responsibilities and actions to be taken for actual
delays or anticipated delays in the submittal of data or for the submittal of unusable data 1. ThisProcedure does not take effect until a data submittal date has been missed or, if prior to the
submittal date, there is sufficient reason to believe that a submittal date will be missed, or it isdetermined that the submitted data is not usable data.
Success of the case development program depends on timely and accurate data submittal, review
and support of the development of each base case. An Area Coordinator or Member System not
meeting a scheduled response date listed in the Data Bank Compilation Schedule section of theHandbook with a usable response could result in a delay in the case development schedule if left
uncorrected. An example of unusable data is data from two neighboring Area Coordinators
whose inter-area schedules do not match. Another example of unusable data is data with suchsignificant problems that it can not be used for the comment phase development process which,
therefore, delays the progress of the case development. Any unusable data received by the Area
Coordinator or the Staff must be corrected by the responsible party so as to not further impair theschedule or it will be rectified in accordance with this Late Data Procedure as will any late data
or anticipated late data.
Area Coordinator and Staff Responsibilities
It is the responsibility of each and every "data owner" to submit timely and accurate data in
accordance with the Data Bank Compilation Schedule and the Case Description sheet in the data
7/29/2019 Dppm v6 Without Redline
17/23
original schedule is maintained or not further impaired.
At the time the Area Coordinator takes over data submittal responsibility for the MemberSystem, the Area Coordinator will immediately notify the Staff. The Staff will then notify the
WECC Member Representative of the Member System with copies to the PCC and TSS
representatives of the Member System of the action taken. Copies shall also be sent to all AreaCoordinators and Sub-Coordinators directly involved. A letter shall also be sent to the PCC,
TSS and SRWG Chairs as well as all of TSS and SRWG with copies to the Operating Committee
(OC) and the Operating Transfer Capability Policy Group Study Group (OTCPGSG) when thecase involved is an operating case for OTC studies. The notification will consist of the nature
and extent of the action taken and the reasons for it. The Staff will take the same notificationaction if they themselves must exercise their late data responsibility in the interest of an Area
Coordinator.
Those who consistently abuse the base case development process by submitting late or unusable
data may be significantly compromising the reliability of the WECC transmission system whichmay eventually become a NERC compliance issue.
Back-Fitting of Late Data
The Late Data Procedure allows for an Area Coordinator or the Staff to take over data submittal
responsibilities for a delinquent entity in the event that entity is unable to submit usable data inaccordance with the defined schedule. If the delinquent entity's data should subsequently
become available, the data shall be submitted to the appropriate Area Coordinator or to the Staff
to partially or fully replace that which was previously submitted. The Staff may, however, refuse
to accept this back-fit data if, in their judgment, the back-fit data is no better than the dataalready in the case or if there would be unacceptable impairment of the schedule by accepting the
back-fit data.
7/29/2019 Dppm v6 Without Redline
18/23
Appendix II
AREA, ZONE, AND BUS NUMBER ASSIGNMENTS
Southwest Region
Area Number Range: 10-18
Zone Number Range: 100-199
Bus Number Range: 10000-19999Member System
Area No. Zone Range Area Name Member System Bus Range10 100-109 New Mexico PNM 10000-10999
120-139 TSGT 12000-12999LAC 13000-13999
NAPI, TNP
11 110-119 El Paso EPE 11000-11999
14 140-179 Arizona APS 14000-1499984000-85999
SRP,APA 15000-15999
TEP 16000-16999AEPC,Others 17000-17999
190-199 WALC 19000-19999
18 180-189 Nevada NEVP 18000-18999
Southern California Region
7/29/2019 Dppm v6 Without Redline
19/23
26 260-299 LADWP LDWP 26000-26999
BURB,GLEN 27000-27999Others 28000-28999
Northern California Region
Area Number Range: 30-39
Zone Number Range: 300-399
Bus Number Range: 30000-39999
Member SystemArea No. Zone Range Area Name Member System Bus Range
30 300-399 PG and E PG&E 30000-36999SMUD 37000-37499
WAPA SNR 37500-37899
REDDING 37900-37999NCPA 38000-38199
MID 38200-38399
TID 38400-38599CDWR 38600-38899
Others 38900-39999
Northwest Region
Area Number Range: 40-49Zone Number Range: 400-499
Bus Number Range: 40000-49999
7/29/2019 Dppm v6 Without Redline
20/23
AVA 48000-49999
Canadian Region
Area Number Range: 50-59
Zone Number Range: 500-599
Bus Number Range: 50000-59999
Member SystemArea No. Zone Range Area Name Member System Bus Range
50 500-519 B.C.Hydro BCHA 50000-51999
52 520-539 Fortis BC FBC 52000-53999
54 540-599 Alberta ESBI 54000-59999
Central Region
Area Number Range: 60-69Zone Number Range: 600-699
Bus Number Range: 60000-69999
Member SystemArea No. Zone Range Area Name Member System Bus Range
60 600-619 Idaho IPC 60000-60999
BPA,Others 61000-61999
7/29/2019 Dppm v6 Without Redline
21/23
70 700-729 PSColorado PSC 70000-70999
WPE 71000-71999
Eastern Region (cont.)
Area Number Range: 70-79
Zone Number Range: 700-799Bus Number Range: 70000-79999
Member SystemArea No. Zone Range Area Name Member System Bus Range
TSGT 72000-72999
73 730-799 WAPA R.M. WALM 73000-73999BHPL 74000-74999
PRPA 75000-75999
BEPC 76000-76999WAUC 79000-79999
7/29/2019 Dppm v6 Without Redline
22/23
7/29/2019 Dppm v6 Without Redline
23/23
II-2