1. PI Data Frequency Response Model Validation Tool WECC MVWG Meeting June 2014 Eric Bakie

2. Introduction • Model Validation Needs • BPA PPMV Model Validation Tool • IPCO PPMV Model Validation Tool • Model Validation Examples Using PI Data • Lessons Learned • Future Work

3. Model Validation Needs • Equipment Level Model Validation • Generator Model, Exciter Model, Governor Model, PSS Model • Unit Level Model Validation (This Tool) • Baseline Model Development • Plant Level Model Validation • Aggregate Generation such as Wind and Solar • Interconnection Wide Model Validation • Post Event Analysis for Data Quality Screening • Independent Verification

4. BPA - FRresponse_v1r.xls

5. BPAPPMVa_SetBaseCase_v1b.p • Powerflow case with kV, MW, MVAR at POI matching initial conditions of disturbance record • EPCL is setup for one facility - one disturbance

6. BPAPPMVa_RunValidation_v1b.p • Validation Comparison of Model to Disturbance Recording • EPCL is setup for one validation run of one facility

7. Desired Play-In Validation Tool Features • Batch processing capability for model validation screening of multiple units • Ability to easily perform model validation screening process multiple events • Use PI Data and plot disturbance records for all units • Focus on governor modeling / frequency response • Automated file management system for generating the files needed to perform model validation using PSLF Play-In • Ability to re-run the process with modified dynamics data

8. Modified FRresponse_v1r.xlsDeveloped PIDataFrequencyResponseModelValidationTool.xlsm

9. Retained Plot Function

10. Separate Tab for each unit with disturbance data in PSLF Play-In format • Macro writes a (*.csv) file to the specified working directory for tab • Formatted for 2400s records Added *.csv Macro

11. Added *.dat Macro • Single Tab with SCADA Initial Conditions Data for each unit • Macro writes a (*.dat) text file to the specific working directory with bus number, bus name, base kV, ID, status, generator kV, MW, MVAR, and baseload flag status data for each unit represented in the spreadsheet tool

12. AddedSet BaseCase Batch (*.p) Macro • Macro writes a (*.p) text file containing the mailbox variables called by the Set Base Case batch EPCL • Only writes records for units that were on-line during the disturbance • Used to develop a powerflow case representative of the I.C. of the disturbance for each unit represented in the tool

13. AddedRun Validation Batch (*.p) Macro • Macro writes a (*.p) text file containing the mailbox variables called by the Run Validation batch EPCL • Only writes records for units that were on-line during the disturbance • Used to run PSLF Play-In for each unit represented in the tool

14. AddedGet Plot Data Batch (*.p) Macro • Macro writes a (*.p) text file containing the mailbox variables called by the Get Plot Data batch EPCL • Only writes records for units that were on-line during the disturbance • Used to convert channel file data to a tab delimited text file for each unit represented in the tool

15. AddedCreate Validation Files Macro • Writes all files needed for validation process to a user specified directory

16. PPMVa_SetBaseCase_PI_FR_batch_v0.p Template File (*.sav) PSLF EPCL to Match Boundary Conditions (*.p) Disturbance Data File (*.csv) Disturbance Case (*.sav) SCADA I.C. File (*.dat)

17. PPMVa_RunValidation_PI_FR_batch_v0.p Disturbance Case (*.sav) PSLF Play-In (*.p) Disturbance Data File (*.csv) Channel File (*.chf) Dynamics Data File (*.dyd)

18. PPMVa_GetPlotData_PI_FR_batch_v0.p PSLF Plot (*.p) Channel File (*.chf) Tab Delimited Text File (*.txt) SCADA I.C. (*.dat)

19. Example:Reasonable Model Performance

20. Example:Poor Model Performance

21. Example:PI Data – Unit Under Load ControlDynamics Data – Sustained Frequency Response • Red = Recording • Blue = Simulation • Modified hyg3 model Ki parameter • Added lcfb1 model

22. Cautions • SCADA update rate and deadband • PI update rate and deadband • Consider a wider view point using PI Data as compared to using test data for model validation • Use a magnifying glass instead of a microscope

23. Lessons Learned • Approach works for governor model validation • Bigger events to get outside of input data dead bands (SCADA and PI) provide better results • Good Tool for identifying undesired control behavior • Good Tool for identifying units represented with sustained frequency response but actually operate under load control • Good Tool for identifying suspect governor model parameters • Deadband (db1), dashpot reset time (tr)

24. Status • Generic Template and User’s Guide Complete • Validation Package now available via MVWG

25. Future Work • Research expanding the spreadsheet to run the same model validation process using the PowerWorld Play-In Function • Benchmark against PMU data • Webinar to demo the tool

26. Questions Eric Bakie, P.E. SYSTEM PLANNING ENGINEER Idaho Power | System Planning  (208) 388-5677  ebakie@idahopower.com