WECC Data Preparation Manual

For Power Flow Base Cases and Dynamic Stability Data July 2009
REV. 6

System Review Work Group Technical Studies Subcommittee

I. INTRODUCTION.................................................................................................................................................................................................................1

I.

Introduction The Western Electricity Coordinating Council (WECC) power system is designed and operated in accordance with the NERC Reliability Standards and WECC Regional Reliability Standards. In order to make this possible, power flow and stability studies are performed 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. Also, the accuracy of study results is extremely important for WECCs Annual 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 those that would be measured on the actual power system under the same conditions. If study results are pessimistic due to inaccurate representation, members shall be unnecessarily limited in the use of their system and may make uneconomic decisions regarding operation and/or system expansion. If study results are optimistic due to inaccurate representation, system reliability may be at risk. Members are encouraged to represent their systems in sufficient detail such that the impact of disturbances, whether internal or external to their own systems, can be adequately evaluated. The level of detail represented should be the level used by each member in conducting their own internal bulk transmission system studies or facility ratings studies. To accomplish this, every attempt should be made to provide accurate representation of all system elements. It is recognized that a greater level of detail is needed for conducting local area studies, but this additional detail should be added by the individual member once a case is complete. It is important that the level of detail be sufficient to accurately determine system conditions and path ratings. This data preparation manual (DPM) is intended to be criteria to be used by WECC Members, which covers power flow and stability data requirements and levels of compliance with NERC Reliability Standards. In addition to this document, the System Review Work Group (SRWG) maintains a handbook, which outlines the guidelines and responsibilities of SRWG members. The SRWG Handbook contains numerous documents pertaining to the overall data preparation and submittal procedure. It is not our intent here to duplicate the information contained in the SRWG Handbook. II. NERC Reliability Standards

This DPM is intended to help implement and support the following NERC Reliability Standards: MOD-010-0: Steady-State Data for Modeling and Simulation of the Interconnected Transmission System. MOD-011-0: Steady-State Data Requirements and Reporting Procedures MOD-012-0: Dynamics Data for Modeling and Simulation of the Interconnected Transmission System. MOD-013-0: Maintenance and Distribution of Dynamics Data Requirements and
1

Reporting Procedures FAC-009-1:

Establish and Communicate Facility Ratings

Data Requirements and Reporting Procedures 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 the steady-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 is available 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 in the PCC Handbook under Section VI, TSS Activities. Section VI of the PCC Handbook is available on the WECC web site at
http://www.wecc.biz/committees/StandingCommittees/PCC/TSS/SRWG/Shared %20Documents/Forms/AllItems.aspx, under Data Compilation Schedules.

A. Data Requirements

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 Model Validation 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 owners are responsible for submitting changes or updates for their solely- or jointlyowned facilities to the MDF as required by approved WECC Policies and Standards to keep the file up to date. Data obtained as a result of the generator testing program will be added to the MDF as it is received once the data have passed the standard data checking routines as developed by the Modeling Validation Work Group (MVWG). Generator Owners must submit dynamics data to the respective Transmission Planner for the Generator Owners machines being added or modified to the power flow representation. Such dynamic data shall be in GE PSLF format and an approved MVWG model. A Late Data Procedure has been implemented to preserve the original Data Bank Compilation Schedule and to track late data and keep TSS and PCC notified in the event late data threatens to impact the scheduled distribution of the data sets. Appendix I contains a copy of the Late Data Procedure. The power flow data used to establish "Accepted WECC Path Ratings" shall not use a level of detail greater than the level represented in WECC base cases unless the path rating sponsor(s) agrees to include the greater level of detail in WECC base cases. The intent is to provide a means for others to verify all such ratings.
2

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 is included 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, is requested 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 flow cases. 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. Area Coordinators 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 initial solved 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 for production use. Data submittals shall be submitted to the WECC staff via email to [email protected]. Once the WECC staff compiles the base case and ensures that the Master Dynamics File initializes correctly, the base case and associated materials are posted on the WECC web site for review. An email of notification of the case posting is sent out to WECC members. Comments to the base case are due back to the WECC staff after two weeks for a planning case or three weeks for an operating case. Comments are preferred in either GE epc or epcl format but will also be accepted as a list in text file format if not too extensive. The WECC staff implements the requested comments to the base case and posts the approved base case on the WECC web site in the base case library. 2. Dynamics Data Dynamics data for the entire WECC interconnection is kept in a database called the Master Dynamics File (MDF). Its critical that this file be maintained and updated as soon as new or updated dynamics data is available. Every base case data request letter includes an additional request for updated dynamics data. This includes dynamics data for generators, motors, UFLS and UVLS models, load representation models, DC lines and any other dynamic equipment modeled in the power flow.
3

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 Transmission Planner. Transmission Planner shall collect facility data and model data validation reports from facility owners. Transmission Planner shall verify that the WECCapproved model parameters provided by the facility owners are adequately validated 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 the Transmission Planner. Transmission Planners shall submit to the WECC Staff any dynamics data received from the facility owner for any new dynamic equipment to be modeled in power flow cases. Dynamics data updates are also submitted via the WECC generator testing program. 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 solution problems, WECC members shall follow the guidelines below to the maximum extent possible. However, it is recognized that there may be circumstances that warrant deviations from the guidelines. For these situations, members are requested to provide the rationale for exceptions to SRWG. A. Bus 1. Bus (substation) requirements shall include: name, nominal voltage, electrical demand supplied (consistent with the aggregated and dispersed substation demand data supplied per Reliability Standards MOD-016-0, MOD-017-0, and MOD-0200), and location. 2. Duplication of bus names within same kV class must be avoided in the base cases. When adding a new bus check to see that the new bus name and kV are not already in use. 3. Bus names and numbers should remain consistent from case to case. 4. Bus numbers should be in the designated range for the area that the bus is being added to. A list of areas and the designated area number and bus ranges is included as Appendix II.
4

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 and Reactive Power), regulated bus and voltage set point, and equipment status. 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 total generation. 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 dynamic turbine-governor model. Exceptions may be allowed for de-rated generators.
4.

2.

3.

Generators with single unit Capacity of 10MVA or higher or facilities with aggregate capacity of 20MVA and larger and which are connected to the transmission system by generator step-up transformer(s) to 60 kV or higher voltage 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) the substation transformer between the collector and the transmission bus of 60kV or a higher voltage. Reactive devices should be represented at the appropriate voltage buses. Owners of any other generators determined by WECC, and the TO, to impact the transmission system will be required to submit modeling data. See "WECC Wind Power Plant Power Flow Modeling Guide -May 2008."

5.

Generator representation must be consistent in both the power flow and stability data files. Retired generators should be deleted from power flow case and Master Dynamics File. Out of service units should not be deleted from the case. Status of out-ofservice units should be set to 0.

6.

7. Remote regulation of a bus voltage, just for the sake of convenience, should be avoided. Generators should regulate to represent actual system operation. 8. Generators that cannot respond to low frequency with additional mechanical power (baseloaded units) must have their baseload flag set to 1 in the GE PSLF program. If the GE PSLF program is not used, a list of baseloaded units must be supplied with each base case data submittal.
5

C.

Transmission Lines
1.

AC Transmission Line or Circuit (overhead and underground) requirements shall include: nominal voltage, impedance, line charging, Normal and 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 shall include 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 conditions unless 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 equivalent branches 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 has caused 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 to determine path ratings. 7. Facilities out of service for voltage control should be noted. Also, anticipated outages (for maintenance or uprates) should be represented. This is particularly important in operating cases. 8. System elements such as series capacitors and shunt reactors that are represented as part of a transmission line should be clearly identified. For example, multiple section lines can be used to model series capacitors. 9. The sections of any multi-section line must be numbered consecutively starting with number 1. 10. The use of bus ties and low impedance lines is discouraged. Sometimes they may be necessary to overcome modeling limitations, but their use for "accounting" purposes is strongly discouraged. Bus ties should not be connected to generator buses, buses where an SVD is modeled, or DC buses. This will cause solution problems. When bus ties are necessary, the impedance should be R=0.0 p.u., and X=0.00029 p.u. or less. No value of charging (G or B) is allowed on lines having less than the jumper threshold impedance. In no instance should a closed loop be made with ties that are less than the threshold impedance. In addition, bus ties must not be used to connect different areas.
6

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 Normal and 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 the rating 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 the rating 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 Reliability Standard FAC-008-0 and FAC-009-0.), and equipment status.

2. Transformers for which partial or no Tap Changing Under Load (TCUL) data has been provided should not be modeled as TCUL transformers. The GE PSLF program accepts partial TCUL data as input, but treats the transformer as a fixed tap 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 reported bandwidth, 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 step. For regulating phase shifting transformers, the maximum phase shift angle reported should be greater than the minimum phase shift angle, and the maximum desired flow should be greater than the minimum flow. 5. TCUL transformers should not regulate remote buses just for the sake of convenience. The "from" or "to" bus should be the regulated bus to cut down on solution problems.
E.

Loads 1. The load level modeled for a case should reflect the conditions of the season that the case intends to represent.
2.

Any generators less than 10 MVA that are modeled as negative load must have an ID of nt in the power flow data.
3.

Loads should be represented accurately and include dynamic properties when available. Individual motors larger than 10 MVA should be modeled individually
7

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 the shunt 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 a bus 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, and controller device. 2. Switched shunt elements should be modeled explicitly. All available switchable elements should be listed on the data record.
3.

When listing switchable elements in the data record, reactors should be listed first, followed by capacitors. 4. Switched shunt devices should be modeled with a sufficient bandwidth such that switching of a shunt element does not move the voltage at the bus completely through the bandwidth, thus causing solution problems at the bus. It is recommended that the minimum value of Vband specified be .02, resulting in a 4% voltage bandwidth. 5. The initial shunt value reported in the base case should be attainable through the switched shunt elements listed on the data record. (The value should be the sum of a possible combination of individual elements). H. Back to Back DC Ties 1. Back to back DC ties should be represented as generation in the powerflow, but netted in stability data. The record should include an ID designation of dc on the generator record. I. Area Interchange
8

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, the Area 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 agreed that 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 or anticipated 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 number, owner number, transaction data, DC bus, DC line, and DC converter information. Members desiring changes to these parameters must make a separate request for the Master Tie Line file to be changed. V. Dynamic Stability Data Requirements The WECC staff, in concert with the SRWG, MVWG and other entities as appropriate, are responsible for maintaining the appropriate DPMand managing the collection of the dynamic system modeling data required to comply with the applicable NERC Standards and Measurements. In order to provide consistency in data submittals and help avoid potential solution problems, WECC members shall follow the guidelines below to the maximum extent possible. However, it is recognized that there may be circumstances that warrant deviations from the guidelines. For these situations, members are requested to provide the rationale for exceptions to SRWG and MVWG. In all cases, the dynamic model must be consistent in both the power flow model and the dynamics data. The facility owners are responsible for providing the data for their solely- or jointly owned facilities in the format specified and for the accuracy of these data.
9

.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 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 1990 Approved dynamics models (including renewable generation) as recommended by the WECC 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 in the 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 Model Validation Policy shall preside. .B Generation 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. If design data is unavailable from the manufacturer 3 months prior to the installation date, estimated or typical manufacturers data, based on excitation systems of similar design and characteristics, shall be provided. Load netting of generation in the dynamics data should be avoided, with the exception of back-to-back DC ties. See Section IV.H of this document. All generators and synchronous condensers should be modeled in accordance with MVWG procedures and policies. The stability data should reflect the true output capability of the machine. Data entered for the power flow Pmax should accurately reflect the capability of the unit, but in no circumstances should it be greater than the maximum capability of the turbine, as represented by the Pmax parameter in the dynamic turbine-governor model.
10

3 4 5

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 Power System Stabilizers is available in the PCC Handbook on the WECC web site at
http://www.wecc.biz/library/WECC%20Documents/Documents%20for%20Generators/WECC_PSS-%20PolicyStatement.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. This will 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 WECC staff for inclusion in the Master Dynamics File (MDF). .D Under Frequency Load Shedding 1. Under frequency load shedding records should be included for all loads that have under frequency relays on the interconnected system. 2. The pickup frequency of each stage must be lower than that of the previous stage. UFLS must comply with WECC coordinated off nominal requirements as specified in the document found at the following link in order to satisfy NERC Standard PRC-006-0: http://www.wecc.biz/library/WECC%20Documents/Miscellaneous
%20Operating%20and%20Planning%20Policies%20and%20Procedures/Off%20Nominal %20Frequency.pdf

3.

Pertinent load data must be in the Master Dynamics File (MDF).

.E Under Voltage Load Shedding 1. Under voltage load shedding records should be included for all loads that have under voltage relays on the interconnected system.

11

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. The ratings 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 Standards TPL-001-0 Table 1 (Steady State Performance)... This includes but is not limited to system elements such as transmission lines, series capacitors, and transformers.
2.

WECC seasonal base cases shall model the seasonal ratings that correspond to the season of the base case. Table 1 Facility Ratings modeled in Power Flow Base Cases

The following table includes required (in BOLD) and recommended line ratings for the GE program: Rating 1 2 3 4

Summer Normal Summer Emergency Winter Normal Winter Emergency

Rating 5 6 7 8

Fall Normal Fall Emergency Spring Normal Spring Emergency

When using the PTI program, the corresponding seasonal normal and emergency ratings should be used for the season of the case; PTI cases will use ratings 1 and 2
for the season of the case. If directed by the Area Coordinator, the WECC staff will move ratings 1 & 2 into the appropriate seasonal ratings columns for the PSLF Base Case being developed.
12

3.

The rating of a system facility (e.g. transmission line, transformer, etc.) shall not exceed 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 a facility, this limit shall become the rating for that facility. 5. Ratings of jointly-owned facilities shall be coordinated and provided on a consistent basis.

13

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 Case Description 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 data1. This Procedure 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 is determined 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 the Handbook 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 such significant 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 the schedule 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 request letter. If, however, in the judgment of the Area Coordinator, it appears that the original schedule will be impaired due to late data submittal or submittal of unusable data, it will be the responsibility of the Area Coordinator to provide the data for the Member System for the case in question. A schedule can be impaired either by data being submitted after the scheduled due date or with the submittal of unusable data even if it is submitted on time. In either instance, there is potential for schedule impairment. If, in the judgment of the WECC Staff, it appears that the schedule will be impaired due to lack of usable data response by the Area Coordinator, it will be the responsibility of the WECC Staff to provide the data for the case in question. Actions to be Taken There are two actions specified by this procedure in the event that the Area Coordinator or the Staff has to exercise their late data responsibilities for a delinquent entity. The first is the action of assuming the responsibility for submitting the data and the second is the notification of such action. If the Staff or the Area Coordinator takes over the responsibility for the submittal of data for the delinquent entity, the data to be submitted should always be the best data available in the judgment of the person submitting the data. The data should be submitted in such a way that the
I-14

original schedule is maintained or not further impaired. At the time the Area Coordinator takes over data submittal responsibility for the Member System, 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 Area Coordinators 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 the case 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 notification action 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 which may 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 in accordance 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 data already in the case or if there would be unacceptable impairment of the schedule by accepting the back-fit data. -----------------------------------------------------------------------------------------------------------1

Unusable Data is being defined as data that has been submitted for use in a power flow/dynamic study case that produces unreasonable power flow/initialization results as may be determined by unreasonable solution results, significant run-time data errors being reported or a diverging power flow solution; data that clearly does not meet the objectives of the case for which the data is being submitted.

I-15

Appendix II AREA, ZONE, AND BUS NUMBER ASSIGNMENTS Southwest Region Area Number Range: Zone Number Range: Bus Number Range: Area No. 10 Zone Range 100-109 120-139 10-18 100-199 10000-19999 Area Name New Mexico Member System PNM TSGT LAC NAPI, TNP EPE APS SRP,APA TEP AEPC,Others WALC Nevada NEVP Member System Bus Range 10000-10999 12000-12999 13000-13999 11000-11999 14000-14999 84000-85999 15000-15999 16000-16999 17000-17999 19000-19999 18000-18999

11 14

110-119 140-179

El Paso Arizona

190-199 18 180-189

Southern California Region Area Number Range: Zone Number Range: Bus Number Range: Area No. 20 21 22 24 Zone Range 200-209 210-219 220-239 240-259 20-29 200-299 20000-29999 Area Name Mexico-CFE Imperialca SanDiego SoCalif Member System CFE IID SDGE Others SCE Member System Bus Range 20000-20999 21000-21999 22000-22999 23000-23999 24000-24999 94000-95999 29000-29999

CDWR, MWD,Others25000-25999
II-1

26

260-299

LADWP

LDWP BURB,GLEN Others

26000-26999 27000-27999 28000-28999

Northern California Region Area Number Range: Zone Number Range: Bus Number Range: Area No. 30 Zone Range 300-399 30-39 300-399 30000-39999 Area Name PG and E Member System PG&E SMUD WAPA SNR REDDING NCPA MID TID CDWR Others Member System Bus Range 30000-36999 37000-37499 37500-37899 37900-37999 38000-38199 38200-38399 38400-38599 38600-38899 38900-39999

Northwest Region Area Number Range: Zone Number Range: Bus Number Range: Area No. 40 Zone Range 400-499 40-49 400-499 40000-49999 Area Name Northwest Member System BPA, other Federal, WPPSS Detailed Federal hydro PSE PGE Not used PACW SNPD GCPD EWEB SCL TCL CHPD Others- Public Others Private or IOU
II-2

Member System Bus Range 40000-41699 41700-41999 42000-42999 43000-43999 44000-44499 44500-45599 45600-45999 46000-46199 46200-46399 46400-46599 46600-46799 46800-46999 47000-47499 47500-47999

AVA

48000-49999

Canadian Region Area Number Range: Zone Number Range: Bus Number Range: Area No. 50 52 54 Central Region Area Number Range: Zone Number Range: Bus Number Range: Area No. 60 62 63 64 65 Zone Range 600-619 620-629 630-639 640-649 650-699 60-69 600-699 60000-69999 Area Name Idaho Montana WAPA U.M. Sierra Pace Member System IPC BPA,Others NWMT WAUM SPP Member System Bus Range 60000-60999 61000-61999 62000-62999 63000-63999 64000-64999 Zone Range 500-519 520-539 540-599 50-59 500-599 50000-59999 Area Name B.C.Hydro Fortis BC Alberta Member System BCHA FBC ESBI Member System Bus Range 50000-51999 52000-53999 54000-59999

PACE-UT 65000-65999 PACE-WY 66000-66999 DGT,UAMP,UMPA 67000-69999

Eastern Region Area Number Range: Zone Number Range: Bus Number Range: Area No. Zone Range 70-79 700-799 70000-79999 Area Name
II-3

Member System

Member System Bus Range

70

700-729

PSColorado

PSC WPE

70000-70999 71000-71999

Eastern Region (cont.) Area Number Range: Zone Number Range: Bus Number Range: Area No. 73 Zone Range 730-799

70-79 700-799 70000-79999 Area Name WAPA R.M. Member System TSGT WALM BHPL PRPA BEPC WAUC Member System Bus Range 72000-72999 73000-73999 74000-74999 75000-75999 76000-76999 79000-79999

II-4

Appendix III Typical Machine Data for Inclusion in the MDF As Member Systems become aware of incorrect data in the Master Dynamics File (MDF) they are urged to submit corrections to the Staff through their Area Coordinator. As the Staff receives updates they will be added to the MDF. This process will insure an up-to-date MDF which reflects the best available data. Members wishing to represent machines not currently in the MDF should submit full machine data in GE format for inclusion in the MDF. Classical representation and load netting should not be used. If data are not available for the machine, either because the machine is not yet built or is owned by another entity, the following typical data developed by GE for inclusion in interconnection studies should be used.

II-2