document name model validation report for may 16, 2014 … validation report for may 16 2014 ras...

39
Document name Model Validation Report for May 16, 2014 RAS Event Category ( ) Regional Reliability Standard ( ) Regional Criteria ( ) Policy ( ) Guideline (X) Report or other ( ) Charter Document date August 12, 2014 Adopted/approved by M&VWG Date adopted/approved August 12, 2014 Custodian (entity responsible for maintenance and upkeep) JSIS Stored/filed Physical location: Web URL: http://www.wecc.biz/committees/StandingCommittees/PCC/TSS/M VWG/Shared%20Documents/MVWG%20Approved%20Documents/ Model%20Validation%20Report%20for%20May%2016%202014%20 RAS%20Event.pdf Previous name/number N/A Status (X) in effect ( ) usable, minor formatting/editing required ( ) modification needed ( ) superseded by _____________________ ( ) other _____________________________ ( ) obsolete/archived)

Upload: others

Post on 26-Dec-2019

5 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

Document name Model Validation Report for May 16, 2014 RAS Event

Category ( ) Regional Reliability Standard ( ) Regional Criteria ( ) Policy ( ) Guideline (X) Report or other ( ) Charter

Document date August 12, 2014 Adopted/approved by

M&VWG

Date adopted/approved

August 12, 2014

Custodian (entity responsible for maintenance and upkeep)

JSIS

Stored/filed Physical location:

Web URL: http://www.wecc.biz/committees/StandingCommittees/PCC/TSS/MVWG/Shared%20Documents/MVWG%20Approved%20Documents/Model%20Validation%20Report%20for%20May%2016%202014%20RAS%20Event.pdf

Previous name/number

N/A

Status (X) in effect ( ) usable, minor formatting/editing required ( ) modification needed ( ) superseded by _____________________ ( ) other _____________________________ ( ) obsolete/archived)

Page 2: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

1

WECC Joint Synchronized Information Subcommittee and WECC Modeling and Validation Work Group

Model Validation Studies for Pacific Northwest RAS Event that Occurred in the Western Interconnection at 23:18 on May 16, 2014

FINAL Report 8-12-2014

I. Conclusions and Recommendations

On May 16 2014, at 23:18:15.85, John Day - Grizzly #1 500-kV line tripped while John Day-Grizzly #2 line was out of service for construction. With both John Day – Grizzly lines out of service and COI flow at about 3,400 MW, the NW RAS operated as designed for the double line outage contingency and keyed 2,563 MW of gen drop at Grand Coulee, Wells, John Day, Biglow Canyon Wind and Dooley Wind. The Chief Joseph Braking Resistor was also inserted as designed. Kemano Unit #1 was tripped by Kemano RAS several seconds later. Springerville Unit #4 was tripped about 40 seconds later due to boiler instability.

The purpose of model validation studies is two-fold:

- Validate accuracy of power system models used in dynamic simulations - Performing “what if” sensitivity studies with respect to control actions

Based on the analysis and studies performed, the following conclusions and recommendations:

FREQUENCY RESPONSE

1. Findings: Generation tripping during May 16, 2014 event was comparable to the resource loss contingency for the Western Interconnection per NERC BAL-003-1 Reliability Standard. The interconnection frequency stayed well above 59.5 Hz level (lowest recorded dip was 59.72 Hz), and the interconnection frequency response was consistent with the historic baseline and well above the interconnection Frequency Response Obligation.

Page 3: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

2

MODELING

2. Findings: Simulated system frequency matched actual recordings quite well. Some discrepancies were observed in active power pick-up on major paths as well as responses of individual generators.

Recommendations: Analysis of individual generator responses may provide additional insight in the power pick-up discrepancies. An application has been developed by Eric Bakie at Idaho Power and MVWG to verify the generator frequency response using SCADA data. The application is available to WECC operating entities. WECC power plant frequency response has not been reviewed programmatically since 2003. WECC Power Plant Model Data Task Force will update and review the baseload flag information as needed.

3. Findings: Majority of operating West-Wide System Model is mapped to a WECC planning case, thereby greatly improving the development of a validation base case. However, major discrepancies exist in wind power plant representation between planning and operating models.

Recommendation: We encourage expedited reconciliation between planning and EMS models for wind power plants. We recommend consistent application of WECC Wind Power Plant Powerflow Modeling Guidelines for planning and operating models across WECC utilities.

4. Findings: Relatively large number of wind generators does not have dynamic models in the dynamic database. Significant amount of wind generation was on-line during May 16 event, and had to be load-netted in dynamic simulations.

Recommendation: MVWG and SRWG need to work with TPs on identifying missing wind power plant models. MVWG will develop a data request for wind and solar generation needed to produce “default” data sets. MVWG will test and provide interim “default” models to TPs until the generators owners provide unit-specific model data.

5. Findings: Reactive current compensation and cross-current compensation models are needed for sister units. This issue has been observed in 2012 and 2013 model validation studies.

Recommendation: MVWG needs to expedite the development and implementation of Cross-Current Compensation models.

Page 4: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

3

KEMANO

6. Findings: A response-based Kemano RAS operated on a power swing caused by Northwest RAS. There is no dynamic model for Kemano RAS to study potential interactions.

Recommendation: Modeling of response-based RAS schemes was identified as a top modeling priority from September 8, 2011 outage recommendations. Kemano RAS owners need to provide to MVWG information and ultimately a dynamic model for Kemano RAS scheme.

7. Findings: Studies show that the operation Kemano RAS operation may not have been necessary to preserve transient stability of Kemano – BC Hydro tie-line during May 16 event.

Recommendation: A response based scheme needs to balance reliability (operate when needed) and security (do not operate unnecessarily). Kemano RAS owners need to review the security of Kemano RAS in the context of this event.

8. Findings: Kemano generators play a very important role in dynamic behavior of the Western Interconnection. However, there is no adequate visibility of the Kemano dynamics, as the closest PMU at BCH’s Willingston 500.

Recommendation: Kemano owners to install PMUs to monitor:

- Kemano 287-kV bus frequency, bus voltage phasor, and current phasors, active and reactive power in each of Kemano power plant transformers

- Measurements used to initiate Kemano RAS

PMU data is to be streamed continuously at 30 samples per second to Peak Reliability RC, BC Hydro and neighboring utilities. Kemano owners to work with WECC JSIS and WISP and determining data requirements.

NORTHWEST RAS AND CHIEF JOSEPH BRAKING RESISTOR

9. Findings: Studies show that the operation of Chief Joseph braking resistor may not have been necessary to preserve system stability during May 16 event. Studies also indicate that Chief Joseph brake operation amplified power swing at Kemano.

Recommendation: Chief Joseph braking resistor is used to absorb accelerating energy during power swings. Operation of Chief Joseph brake may not have been needed during May 16 event.

Page 5: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

4

Chief Joseph brake is used as a safety net, and BPA needs to review security of the brake controller to minimize the unnecessary operations.

BPA also needs to provide a dynamic model for Chief Joseph controller.

SPRINGERVILLE #4 TRIP

10. Findings: Springerville unit#4 tripped on low frequency during May 16 event, although the frequency stayed well within the envelope of NERC PRC-024 Reliability Standard. System frequency for May 16 event is compared with simulated two Palo Verde outage. Two Palo Verde outage would have caused a lower system frequency than what was observed during May 16 RAS event, and therefore 2PV outage would have likely caused the trip of Springerville unit #4. Springerville#4 trip would have had minimum impact on system frequency nadir, and some impact power pick-up and voltages on California – Oregon Intertie.

Springerville #4 owners are taking steps to resolve issues that caused unit trip during May 16 event.

Page 6: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

5

II. May 16, 2014 Event Description

On May 16 2014, Friday, at 23:18:15.85, the John Day - Grizzly #1 500-kV line tripped while John Day-Grizzly #2 line was out of service for construction. With both John Day – Grizzly # 1 and #2 lines out of service, the NW RAS operated as designed for the double line outage contingency and keyed 2,563 MW of gen drop at Grand Coulee, Wells, John Day, Biglow Canyon Wind and Dooley Wind, and inserted the Chief Joseph Braking Resistor.

NW RAS generation trip included:

Plant Units MW Dropped

BIGLOW CANYON TOTAL GEN 419.4

DOOLEY WIND TOTAL GEN 183.1

GRAND_COULEE CKT2 TO G-6-9 236.5

GRAND_COULEE G20 471

GRAND_COULEE G21 508

JOHN_DAY G09 113

JOHN_DAY G12 112

JOHN_DAY G14 111

JOHN_DAY G16 114

WELLS G03 73.86

WELLS G05 73.85

WELLS G08 73.55

WELLS G09 73.75

TOTAL 2563

Kemano unit 1 tripped with approximately 110 MW. BC Hydro reported that the tripping of the Kemano unit was due to the combined frequency response of the eight Kemano generators, which were producing about 750 MW pre-disturbance with a net export into the BC Hydro system of 380 MW. The RAS on the Kemano-Kittimat 287-kV lines tripped one unit as designed (Kemano unit #1) when the net export from Kemano system to BC Hydro is greater than 420 MW.

Within approximately one minute of the NW Gen Drop, the Springerville unit #4 tripped with approximately 445 MW due to an apparent internal plant protection, although the system frequency was well within the NERC PRC-024 off-nominal frequency ride-through envelope. SRP reported that the Springerville unit #4 tripped off line due high furnace pressure and the loss of both ID Fans. SRP has identified potential “fixes” that could be applied to prevent the tripping of the unit for future frequency deviations (Springerville unit #4 also tripped during NW RAS event on January 29, 2014).

Page 7: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

6

The system frequency dropped down to 59.73 Hz during the event, which is well above the first level of the coordinated under-frequency load shedding program set at 59.5 Hz. No loss of load is reported during the event.

John Day – Grizzly #1 Line was restored at about 23:20:30, about 2 minutes after it was tripped.

Figure 1 shows a 3-minute recording of the system frequency during the event.

Figure 1: system frequency during May 16, 2014 disturbance.

59.7

59.75

59.8

59.85

59.9

59.95

60

60.05

23:18:00 23:18:15 23:18:30 23:18:45 23:19:00 23:19:15 23:19:30 23:19:45 23:20:00 23:20:15 23:20:30 23:20:45

Frequency

NW RAS = 2,563 MW

Kemano = 110 MW

Springerville = 445 MW

John Day – Grizzly #1back in service

Page 8: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

7

III. System Frequency Performance During May 16, 2014 Event

No loss of load has been reported during the event.

Figure 2: System frequency response – determining NERC Point A and Point B

Frequency response metrics are consistent the historic baseline, as highlighted in Figure 3.

Figure 3: historic frequency response baseline in the Western Interconnection: Red dots – frequency response is measured at Point B consistent with NERC BAL-003-1 methodology Blue diamonds – response is measured at frequency nadir Size of dots and diamonds is proportional to the size of the event

Page 9: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

8

Interconnection-wide frequency response performance is performed:

Frequency – Point A (initial) Hz 60.009 Frequency – Point B (settle) Hz 59.827 Frequency – Point C (nadir) Hz 59.720 Contingency (NW RAS+Kemano) MW 2,673 NERC Frequency Response Measure MW per 0.1 Hz 1,468 Nadir-based frequency response MW per 0.1 Hz 924 Western Interconnection total generation GW 97

The system frequency performance surpasses Frequency Response Obligation for Western Interconnection per NERC BAL-003-1, and consistent with historic baseline.

IV. Validation Base Case Development

2014 Light Summer WECC Operational Planning base case (planning case) is used as a starting point in the model validation studies.

Figure 4 shows a process diagram.

Figure 4: validation base case development process

WECC Modeling and Validation work group issued a data request for generation and key transmission flows prior to the event. Peak Reliability RC provided an operating West-wide System Model base case (WSM case) just prior to the disturbance. The operational information was mapped onto 2014 planning case. Regional loads were scaled to match the key tie-line flows. Also, dynamic simulation of event is performed directly using WSM and results are benchmarked against PMUs and 2014 planning case.

Planning Base Case(Bus-Brunch Representation)

Operating West-wide System Model for Event

(State Estimator Model, Breaker-Node Representation)

Planning Dynamic Database

Composite Load Model

Dynamic Simulation of an Event

WECC MVWG Data Request

Mapping Operating Data onto Planning Case

Page 10: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

9

V. Dynamic Model

2014 operational dynamic data base is used in the validation studies.

Wind Generation.

Large amount of wind generation was on-line during May 16 event. A significant number of wind generators in Tehachapi area had no dynamic models in WECC dynamic data base. Several hundred MWs of generators had to be “netted” in dynamic simulation. Wind generation models in Pacific Northwest were unstable due to model additions, and were replaced with stable data used in 2013 studies.

Reactive Current Compensation.

Reactive Current Compensation is required to maintain stability between two sister units connected to the same bus:

- XCOMP sign is changed from +0.052 to –0.052 for RI STUB, RI SOUTH, RI NORTH units - XCOMP sign is changed from +0.05 to –0.05 on MAGCORP units - XCOMP of –0.05 for Little Goose units

Cross-Current Compensation.

John Day and The Dalles generators went unstable during the simulation. John Day and The Dalles generators have Line Drop Compensation for voltage support and Cross-Current Compensation to ensure stability of sister units. Current generator models include Line Drop Compensation, but there is no Cross-Current Compensation model in PSLF. Not having CCOMP model is adequate as long as sister units are identical and have the same active and reactive power loading, as often set-up in planning cases. Operationally, units are often loaded at different levels, and therefore go unstable without CCOMP models. To mitigate the issue, John Day generators were re-dispatched to same “average” level.

SVSMO1 dynamic model is added for Keeler SVC

Composite Load Model

Composite load model records are developed using WECC Load Model Data Tool. Shoulder season hour 22 are used to estimate load composition.

Page 11: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

10

VI. Simulations

Simulated sequence of events:

Time (sec) Action 0 Open John Day – Grizzly 500-kV line #1 0.125 RAS Gendrop – Dooley, Biglow Canyon, Grand Coulee, Wells, and John Day 0.125 Close Chief Joseph braking resistor 0.64 Open Chief Joseph braking resistor 2.3 Trip Kemano unit #1 2.3 Malin MSC cap #1 tripped 2.65 Ostrander reactors are tripped 2.72 Pearl capacitors are inserted 2.88 Slatt shunt capacitors are inserted 5.3 Malin shunt reactor is inserted 32.9 Grizzly shunt reactor is inserted 40.9 Springerville Unit#4 tripped

*Initial report had Kemano tripping at about 7 seconds after the initial event. PMU data analysis and model validation indicate that the tripping occurred earlier

Figures M1 to M6 and S1show comparison between actual and simulated responses.

VII. West-Wide System Model Studies

West-Wide System Model (WSM) is a node breaker (full topology) state estimator model from Peak Reliability RC. GE PSLF version 19 has capabilities to read node-breaker power flow model and link it with the WECC dynamic database. Peak Reliability RC and WECC performed model validation studies using the state estimator snapshot taken prior to the event. Figures WSM-1 to WSM-6 compare (i) PSLF simulations done using bus-branch WECC planning model, (ii) PSLF simulations done using node-breaker WSM model, and (iii) actual PMU recordings. WSM model agrees with WECC planning model, and both capture the main features of the May 16 event reasonably well.

Page 12: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

11

VIII. Sensitivity Studies

Sensitivity “what if” studies are conducted once the system model is validated reasonably well

Kemano RAS:

Kemano RAS tripped Kemano unit #1 with 110 MW for a power swing following Pacific Northwest gen drop.

Questions:

a. Was Kemano RAS operation necessary during the May 16 conditions? b. Would the system remain stability and adequate performance if Kemano RAS did not operate on

May 16? c. Would a two Palo Verde outage trigger Kemano RAS operation?

May 16 sequence of events was simulated with and without Kemano tripping. Two Palo Verde outage was simulated on May 16 base case.

Conclusions and Recommendations:

a. There are no dynamic models to simulate Kemano RAS in dynamic simulations. Kemano owners are required to provide description of their RAS scheme and associated dynamic models.

b. Although Power swing at Kemano was relatively large, as suggested by Figure K1, Kemano RAS operation may not have been needed for the system stability during May 16 event, as seen from simulations in Figure K2.

c. Kemano RAS owners are suggested to look into improving security of their RAS scheme d. 2 Palo Verde outage caused a less severe power swing at Kemano compared to May 16 RAS

event, and not likely to initiate Kemano RAS operation (Figure K3).

Springerville #4 Trip

Springerville unit #4 tripped on May 16 due to boiler instability caused by low frequency about 40 seconds after the initiating event. The closest to Springerville PMU is one at Coronado 500-kV bus. Figure S1 shows a good agreement between actual and simulated voltages and frequencies at Coronado 500-kV substation.

Questions:

a. Would Springerville unit #4 trip for a 2 Palo Verde outage? b. What would have been the impact on California – Oregon Intertie should 2 Palo Verde outage

occurred and Springerville unit tripped after that

Studies:

Simulations of 2 Palo Verde outage were performed to compare the frequency at Springerville#4 with the frequency during May 16 RAS event.

Page 13: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

12

Simulations of 2 Palo Verde outage plus Springerville#4 trip were performed to determine any impact the additional generation would have had on the stability of California – Oregon Intertie.

Conclusions:

a. Springerville frequency would have been lower for 2 Palo Verde outage compared to system frequency during May 16 event, therefore it is very likely that Springerville unit would have tripped for 2 Palo Verde outage (Figure S3)

b. Springerville trip following 2 Palo Verde outage would have had some, but not significant, impact on the COI voltages and power pick-up (Figure S4)

Springerville#4 owners are working on resolving technical issues that resulted in the unit’s trip.

Interaction between Northwest RAS and Kemano RAS:

NW RAS dropped 2,500 MW of generation and initiated operation of Chief Joseph braking resistor, which created a power swing that resulted in the operation of Kemano RAS.

Questions:

a. Generator dropping amounts are determined based on planning studies, usually considering conservative system conditions. Given actual system conditions, was dropping of 2,500 MW of generation was necessary, or lower gen drop amount would have suffice?

b. What the impact of lower gen drop would have been on the Kemano power swing? c. What the impact of Chief Joseph braking resistor not operating would have been at Kemano

power swing?

Studies:

Simulations of May 16 event were performed without operation of Chief Joseph brake.

Simulations of May 16 event were performed with lower amount of NW RAS gen drop.

Conclusions and Recommendations:

a. Reducing amount of NW gen drop had minimum impact on Kemano power swing (Figure N1) b. Chief Joseph brake operation had observable impact on Kemano power swing (Figure N-2).

To answer whether a smaller amount of gen drop would have been sufficient under May 16 condition, a full set of contingency analysis would need to be done per NERC TPL standards, including thermal, voltage stability and dynamic simulations. The system performance must be met for line outages initiated by 3-phase faults, while May 16 event was high impedance fault with low fault current

BPA planning needs to consider improving the security of controller that operates Chief Joseph braking resistor to minimize the unnecessary operations.

Page 14: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

13

Kemano Power System Stabilizer

Kemano generators use dual-input Power System Stabilizers (PSS). The PSS synthesizes the integral of accelerating power from speed and power measurements. The calculation of PSS gain “Ks2” is dependent on generator inertia. It was observed during recent review of PSS settings conducted by Shawn Patterson and WECC JSIS that the calculations of Kemano PSS gains “Ks2” assume wrong generator inertia.

Question:

a. What would be the impact of changing the Kemano PSS gain “Ks2” to match generator inertia?

Table below shows generator inertia and associated PSS settings:

Kemano Generator Inertia, H

PSS washout ime constant, Tw

PSS Gain Ks2 to match H

PSS Gain Ks2 as is

G1 3.2 5 0.781 0.5 G2 4.74 5 0.527 0.33 G3 4.68 5 0.534 0.37 G4 3.2 5 0.781 0.5 G5 4.68 5 0.534 0.37 G6 5.25 5 0.476 0.33 G7 3.2 5 0.781 0.5 G8 5.25 5 0.476 0.33

Simulations were performed with new PSS settings. Study results are summarized in Figure KP1.

Conclusion:

a. Changing Kemano PSS gain “Ks2” would have had a slightly negative impact on Kemano power swing.

Kittimat Load Model Composition

Composite load model is used in the studies. Kittimat aluminum smelter is represented with default model, where 10% of load are induction motors driving frequency-dependent loads (pumps and fans), and 90% of load is constant resistance load. A sensitivity study is done with respect to a more demanding load characteristic, where 20% of loads are induction motors driving constant torque load, and 80% of load is constant current. No significant change in performance is observed in this study, as shown in Figure KIT1.

Page 15: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

14

Frequency Response Margin

Simulations were run where the amount of gen.drop is increased until the system frequency nadir approached 59.5 Hz, the level at which the coordinated under-frequency load shedding plan starts. We simulated up to 4,000 MW of generation dropping in Pacific Northwest, by tripping additional hydro-power generation at John Day and Chief Joseph. Figures E1 and E2 show frequency recordings in various parts of the interconnection, they all stay above 59.5 Hz level. Figure E3 shows voltages at key tie-lines which are known to be affected by gen.drop events. Voltages in Kemano area are affected the most by increased gen.drop under the studied condition. While the system frequencies stayed above 59.5 Hz, we do not suggest increasing the amount of gen.drop beyond the existing levels in the Western Interconnection.

Page 16: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

15

Figure M1: Simulated versus Actual Frequency

0 10 20 30 40 50 60 70 8059.7

59.75

59.8

59.85

59.9

59.95

60

60.05

60.1

Time (sec)

Freq

uenc

y (H

z)Malin Frequency

ActualSimulated

0 10 20 30 40 50 60 70 8059.7

59.75

59.8

59.85

59.9

59.95

60

60.05

60.1

Time (sec)

Freq

uenc

y (H

z)

Custer Frequency

ActualSimulated

Page 17: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

16

Figure M2: Simulated versus Actual Frequency

0 10 20 30 40 50 60 70 8059.7

59.75

59.8

59.85

59.9

59.95

60

60.05

60.1

Time (sec)

Freq

uenc

y (H

z)

Grand Coulee Frequency

ActualSimulated

0 10 20 30 40 50 60 70 8059.7

59.75

59.8

59.85

59.9

59.95

60

60.05

60.1

Time (sec)

Freq

uenc

y (H

z)

Sylmar Frequency

ActualSimulated

Page 18: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

17

Figure M3: Simulated versus Actual Voltages

0 10 20 30 40 50 60 70 80535

540

545

550

555

560

565

570

Time (sec)

Vol

tage

(kV

)

Malin Voltage

ActualSimulated

0 10 20 30 40 50 60 70 80530

535

540

545

550

555

560

565

570

Time (sec)

Vol

tage

(kV

)

Grizzly Voltage

ActualSimulated

Page 19: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

18

Figure M4: Simulated versus Actual Voltages

0 10 20 30 40 50 60 70 80525

530

535

540

545

550

555

560

Time (sec)

Vol

tage

(kV

)

Pearl Voltage

ActualSimulated

0 10 20 30 40 50 60 70 80532

534

536

538

540

542

544

546

548

550

Time (sec)

Vol

tage

(kV

)

Grand Coulee Voltage

ActualSimulated

Page 20: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

19

Figure M5: Simulated versus Actual Power Flows

0 10 20 30 40 50 60 70 801500

2000

2500

3000

3500

Time (sec)

Pow

er (

MW

)

COI Power

ActualSimulated

0 10 20 30 40 50 60 70 800

200

400

600

800

1000

1200

1400

Time (sec)

Pow

er (

MW

)

Custer - Ingledow Power

ActualSimulated

Page 21: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

20

Figure M6: Simulated versus Actual Phase Angles

0 10 20 30 40 50 60 70 8018

20

22

24

26

28

30

32

34

36

Time (sec)

Ang

le (D

EG)

John Day - Malin Angle

ActualSimulated

0 10 20 30 40 50 60 70 8025

30

35

40

45

50

Time (sec)

Ang

le (D

EG)

Grand Coulee - Malin Angle

ActualSimulated

Page 22: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

21

Figure WSM-1: Malin 500-kV Bus Frequency

Figure WSM-2: Custer 500-kV Bus Frequency

Page 23: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

22

Figure WSM-3: Malin 500-kV Bus Voltage

Figure WSM-4: Custer 500-kV Bus Voltage

1.06

1.07

1.08

1.09

1.1

1.11

1.12

1.13

1.14

1.15

0 10 20 30 40 50 60 70 80 90 100

MALIN VMAG PMU PSLF(Bus&Branch) PSLF(Node&Breaker)

Page 24: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

23

Figure WSM-5: Grand Coulee 500-kV Bus Voltage

Figure WSM-6: COI total power

1.06

1.065

1.07

1.075

1.08

1.085

1.09

1.095

1.1

1.105

0 10 20 30 40 50 60 70 80 90 100

G_COULEE VMAG PMU PSLF(Bus&Branch) PSLF(Node&Breaker)

0

500

1000

1500

2000

2500

3000

3500

4000

0 10 20 30 40 50 60 70 80 90 100

COI POWER PMU PSLF(Bus&Branch) PSLF(Node&Breaker)

Page 25: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

24

Figure K1: Simulated Kemano Dynamics during May 16 RAS event

0 10 20 30 40 50 60 70 80100

200

300

400

500

600

Time (sec)

Pow

er (

MW

)

Power out of Kemano

KIT-MINMIN-SKA

0 10 20 30 40 50 60 70 8059.4

59.6

59.8

60

60.2

Time (sec)

Spe

ed (

PU

)

Kemano Generator Speed

KMO3KMO7

0 10 20 30 40 50 60 70 800.9

0.95

1

1.05

1.1

1.15

Time (sec)

Vol

tage

(PU

)

Kemano Area Voltages

KMO287KIT287MIN287SKA287WSN500

Page 26: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

25

Figure K2: Comparison of Simulated Kemano Dynamics with Kemano RAS operating and not operating for May 16 condition

0 10 20 30 40 50 60 70 80100

200

300

400

500

600

Time (sec)

Pow

er (

MW

)

KIT-MIN Power Flow

KMO RAS OperatesKMO RAS Does Not Operate

0 10 20 30 40 50 60 70 800.85

0.9

0.95

1

1.05

1.1

Time (sec)

Vol

tage

(kV

)

MIN287 Voltage

KMO RAS OperatesKMO RAS Does Not Operate

Page 27: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

26

Figure K3: Comparison between May 16 RAS event and 2 Palo Verde as seen at Kemano

5 10 15 20 250.85

0.9

0.95

1

1.05

1.1

Time (sec)

Vol

tage

(kV

)

MIN-287-kV Voltage

May 16 as was2PV

5 10 15 20 25200

250

300

350

400

450

500

550

600

Time (sec)

Pow

er (

MW

)

KIT-MIN Power Flow

May 16 as was2PV

Page 28: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

27

Figure S1: Simulated versus Actual Coronado 500-kV Voltage and Frequency During May 16 Event

0 10 20 30 40 50 60 70 80525

530

535

540

545

Time (sec)

Vol

tage

(kV

)Coronado 500-kV Bus Voltage

ActualSimulated

0 10 20 30 40 50 60 70 8059.7

59.75

59.8

59.85

59.9

59.95

60

60.05

60.1

Time (sec)

Freq

uenc

y (H

z)

Coronado 500-kV Bus Frequency

ActualSimulated

Page 29: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

28

Figure S2: Simulated Springervile 4 Dynamics During May 16 RAS Event

0 10 20 30 40 50 60 70 801

1.02

1.04

1.06

Time (sec)

Vol

tage

(PU

)

Sprinerville 4 Voltages

POI 345-kVGenerator

0 10 20 30 40 50 60 70 8059.5

59.6

59.7

59.8

59.9

60

Time (sec)

Freq

uenc

y (H

z)

Sprinerville 4 Frequency

FrequencySpeed

0 10 20 30 40 50 60 70 80420

430

440

450

460

Time (sec)

Pow

er (

MW

)

Sprinerville 4 Power

ElectricalMechanical

Page 30: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

29

Figure S3: Comparison of Simulated Springervile Dynamics During May 16 RAS Event and 2 PV event

0 10 20 30 40 50 60 70 8059.65

59.7

59.75

59.8

59.85

59.9

59.95

60

60.05

Time (sec)

Freq

uenc

y (H

z)

Sprinerville 4 Frequency

RAS-2014-05-162 Palo Verde

0 10 20 30 40 50 60 70 80420

425

430

435

440

445

450

455

460

Time (sec)

Pow

er (

MW

)

Sprinerville 4 Electrical Power

RAS-2014-05-162 Palo Verde

Page 31: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

30

Figure S4: Comparison of Simulated Springervile Dynamics During May 16 RAS Event and 2 PV event

0 10 20 30 40 50 60 70 8059.6

59.7

59.8

59.9

60

Time (sec)

Freq

uenc

y (H

z)

System Frequency

2PV2PV+Springerville

0 10 20 30 40 50 60 70 80480

500

520

540

560

Time (sec)

Vol

tage

(kV

)

Malin 500-kV Bus Voltage

2PV2PV+Springerville

0 10 20 30 40 50 60 70 803000

3500

4000

4500

5000

Time (sec)

Pow

er (

MW

)

COI Power

2PV2PV+Springerville

Page 32: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

31

Figure N1: Sensitivity with respect to reducing NW RAS gen.drop

5 10 15 20 250.85

0.9

0.95

1

1.05

1.1

Time (sec)

Vol

tage

(kV

)

MIN-287-kV Voltage

OriginalReduced NW RAS

5 10 15 20 25200

250

300

350

400

450

500

550

600

Time (sec)

Pow

er (

MW

)

KIT-MIN Power Flow

OriginalReduced NW RAS

Page 33: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

32

Figure N2: Sensitivity with respect to operation of Chief Joseph braking resistor

5 10 15 20 250.85

0.9

0.95

1

1.05

1.1

Time (sec)

Vol

tage

(kV

)MIN-287-kV Voltage

OriginalNo brake

5 10 15 20 25200

250

300

350

400

450

500

550

600

Time (sec)

Pow

er (

MW

)

KIT-MIN Power Flow

OriginalNo brake

Page 34: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

33

Figure KP1: Sensitivity with respect to Kemano PSS settings

10 12 14 16 18 200.85

0.9

0.95

1

1.05

1.1

Time (sec)

Vol

tage

(kV

)MIN-287-kV Voltage

OriginalKMO PSS-Intertia Gain

10 12 14 16 18 20200

250

300

350

400

450

500

550

600

Time (sec)

Pow

er (

MW

)

KIT-MIN Power Flow

OriginalKMO PSS-Intertia Gain

Page 35: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

34

Figure KIT1: Sensitivity with respect to Kittimat Load Composition- Original: 90% constant impedance, 10% motors with Driven Load D=2- Conservative: 80% constant current, 20% motors with Driven Load

D=0

10 12 14 16 18 200.85

0.9

0.95

1

1.05

1.1

Time (sec)

Vol

tage

(kV

)MIN-287-kV Voltage

OriginalMore Conservative

10 12 14 16 18 20200

250

300

350

400

450

500

550

600

Time (sec)

Pow

er (

MW

)

KIT-MIN Power Flow

OriginalMore Conservative

Page 36: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

35

Figure E1: Impact of extreme generation drop

0 10 20 30 40 50 60 70 8059.5

59.6

59.7

59.8

59.9

60

60.1

Time (sec)

Freq

uenc

y (H

z)Malin 500-kV Frequency

0 10 20 30 40 50 60 70 8059.5

59.6

59.7

59.8

59.9

60

60.1

Time (sec)

Freq

uenc

y (H

z)

Coronado 500-kV Frequency

May 16 as was4,000 MW RAS Gendrop

May 16 as was4,000 MW RAS Gendrop

Page 37: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

36

Figure E2: Impact of extreme generation drop

0 10 20 30 40 50 60 70 8059.5

59.6

59.7

59.8

59.9

60

60.1

Time (sec)

Freq

uenc

y (H

z)Williston 500-kV Frequency

0 10 20 30 40 50 60 70 8059.5

59.6

59.7

59.8

59.9

60

60.1

Time (sec)

Freq

uenc

y (H

z)

Langdon 500-kV Frequency

May 16 as was4,000 MW RAS Gendrop

May 16 as was4,000 MW RAS Gendrop

Page 38: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

37

Figure E3: Impact of extreme generation drop

5 10 15 20 250.8

0.9

1

1.1

Time (sec)

Vol

tage

(PU

))MIN 287-kV Voltage

May 16 as was4,000 MW RAS Gendrop

5 10 15 20 250.95

1

1.05

1.1

Time (sec)

Vol

tage

(PU

))

Langdon 500-kV Voltage

May 16 as was4,000 MW RAS Gendrop

5 10 15 20 251

1.01

1.02

1.03

1.04

1.05

Time (sec)

Vol

tage

(PU

))

Great Falls 230-kV Voltage

May 16 as was4,000 MW RAS Gendrop

Page 39: Document name Model Validation Report for May 16, 2014 … Validation Report for May 16 2014 RAS Event.pdfplanning case, thereby greatly improving the development of a validation base

38

Figure E4: Impact of extreme generation drop

5 10 15 20 25-200

0

200

400

600

Time (sec)

Pow

er (

MW

)KIT-MIN Active Power

5 10 15 20 25-400

-200

0

200

400

600

Time (sec)

Pow

er (

MW

)

Langon-Cranbrook Active Power

5 10 15 20 25-100

0

100

200

300

Time (sec)

Pow

er (

MW

)

MATL Active Power

May 16 as was4,000 MW RAS Gendrop

May 16 as was4,000 MW RAS Gendrop

May 16 as was4,000 MW RAS Gendrop