Data Preparation Tools and Dynamic Models for System Studies with Distributed Series Impedances and Distributed Static Series Compensators

Transcription

1 Data Preparation Tools and Dynamic Models for System Studies with Distributed Series Impedances and Distributed Static Series Compensators Presentation of Part 1 and Part 2 studies to MVWG Chifong Thomas Director, Transmission Planning and Strategy Smart Wires Inc. USA Anatoliy Meklin

2 Recent Developments for Smart Wires Completed installation of 90 PowerLine Guardian units as part of California EPIC Program in December 2015 using a helicopter installation method. Piloting our second-generation product, the Tower Router, at four utility partners in Energized installation under development Tower Router units on H-Frame Structure Helicopter installation tool PowerLine Guardians installed on 115 kv line Slide 2

3 Models and tools for Smart Wires System Performance Studies Models for Steady State Analysis The model for Steady State Simulations was developed by PowerWorld in the core of the PowerWorld Simulator. The program derives the number of modules to satisfy given objectives. DSR.p for PSLF, developed by USE. The program derives the number of modules to satisfy given objective, complying with the aggregated limitations for max/min impedances (for current limitation and regulation) and for max/min currents (for given impedance injection). A Python routine, also developed by USE for PSS/E. This Python routine provides similar functions as the DSR.p for PSLF. Steady State analyses to deploy Smart Wires technology can be performed with ordinary models of series reactors or phase shifting transformers. However, the process can be tedious and the specialized tools are developed to simply the studies. All steady state models and tools are indifferent to a dynamic process. Slide 3

4 Models and tools for Smart Wires System Performance Studies Dynamic Modeling Dynamic Models are needed for the SW devices, when accurate and fast module engagement is implemented, using the response-based control with local current relays and timers. Part 1 of the study justifies one possible local control setup with principals similar to the UFLS system. Due to the dynamic fluctuation prior to current settlement, the module engagement can be non-simultaneous, if module current and time settings are different. Furthermore, if some modules are injected a little earlier, other modules would be exposed to reduced current and may not trigger. Special dynamic models should be used to simulate the impact of module engagement on system performance. Development of the Dynamic Model is the urgent task for facilitating performance studies for systems with Smart Wire devices. The PSLF EPCMOD prototype of such a dynamic model was developed by SW and presented at the MVWG meeting in November The Part 2 of the SW study takes into account the MVWG recommendations. Slide 4

5 Recap - Detailed Dynamic Model Presented in November MVWG Meeting This model is for the most accurate studies and with a plenty of output. Requires appreciable additions in power flow and dynamic data for separate modeling of each module and surrounding line sections. Supported by the developed Data Builders. MVWG concern: The additions in PF cases could become critical in the future, when more lines will be equipped with the SW devices. MVWG recommendation: consider more generic modeling for ordinary studies to minimize data additions and eliminate convergence problems. Slide 5

6 Part 2 Study Generic Models (March 2016) Descriptions of the Model A and Model B types of local generic models. Working PSLF EPCMOD prototypes for both local models. Validity of the prototypes is verified by conducting many simulations, identical to conducted earlier (in Part 1) for the detailed model. Specifications of input and output parameters in the traditional form of specifications, used for PSLF dynamic models. Description, prototype program and specification for the remote control model. Modifications of the Excel based Data Builders to make them consistent with new dynamic models. The data preparation process is much simpler for the generic models, but the modified Data Builders could be still useful for the preparation of the initial set of data records. Comparison of the Detailed, A and B models and recommendations for their application. Slide 6

7 Generic Model A Model A does not need sectionalizing and changes in a PF case. All modules are fed by the same current, and each module insertion is modeled by changing line impedance or angle. Model A preserves the potential for counting irregularities of module setup and electrical parameters in the individual for each module invocations. Modules can be aggregated to switch in groups. Populating dynamic files by multiple invocations should not be critical with the increasing level of module aggregation. Model A does not have capability for monitoring flows and voltages in the points near actual individual module locations. Slide 7

8 Generic Model A Invocation Records for 13 Modules (11 arresting, 2 anti-stalling) EPCMOD "ROUND_MT" 230 "1 " "COTWD_E" 230 "1 " 1 : #9 "SW-inject-A.p" 39 "time_hold " 2.0 / (anti-stalling 2) "level_up" "level_down" "time_up" 20.0 "time_down" 80 "rmodule" 0 "xmodule" 0 "angmodule" 0.1 "counter_#" EPCMOD "ROUND_MT" 230 "1 " "COTWD_E" 230 "1 " 1 : #0 "SW-inject-A.p" 39 "time_hold " 2.0/ (anti-stalling 1) "level_up" "level_down" "time_up" 15.0 "time_down" 75 "rmodule" 0 "xmodule" 0 "angmodule" 0.1 "counter_#" EPCMOD "ROUND_MT" 230 "1 " "COTWD_E" 230 "1 " 1 : #0 "SW-inject-A.p" 39 "time_hold " 2.0 / (arresting 11) "level_up" 1000 "level_down" "time_up" 5.0 "time_down" 70 "rmodule" 0 "xmodule" 0 "angmodule" 0.1 "counter_#" EPCMOD "ROUND_MT" 230 "1 " "COTWD_E" 230 "1 " 1 : #0 "SW-inject-A.p" 39 "time_hold " 2.0 / (arresting 10) "level_up" "level_down" "time_up" 5.0 "time_down" 65 "rmodule" 0 "xmodule" 0 "angmodule" 0.1 "counter_#" EPCMOD "ROUND_MT" 230 "1 " "COTWD_E" 230 "1 " 1 : #0 "SW-inject-A.p" 39 "time_hold " 2.0 / (arresting 2) "level_up" "level_down" "time_up" 5.0 "time_down" 25 "rmodule" 0 "xmodule" 0 "angmodule" 0.1 "counter_#" EPCMOD "ROUND_MT" 230 "1 " "COTWD_E" 230 "1 " 1 : #0 "SW-inject-A.p" 39 "time_hold " 2.0 / (arresting 1) "level_up" "level_down" "time_up" 5.0 "time_down" 20 "rmodule" 0 "xmodule" 0 "angmodule" 0.1 "counter_#" Slide 8

9 Generic Model B Model B also does not need sectionalizing and changes in a PF case. Contrary to Model A, it does not include separate invocations for each module. The multi-module model is used for sequential module logic execution. Module setup and electrical parameters are calculated in Model B prior to execution for particular module, based on the generic setup, reflected in only one invocation record. Generic Model B invocation record (single record) EPCMOD "ROUND_MT" 230 "1 " "COTWD_E" 230 "1 " 1 : #9 "SW-inject-B.p" 39 / "arrest#" 11 "ar_levelmax" 1000 "ar_levelmin" 900 "ar_time" 5 / "an-stall#" 2 "an-stall_level" 900 "an-stall_tmax" 20 "an-stall_tmin" 15 / "rstr_level" 850 "rstr_tmax" 80.0 "rstr_tmin" 20.0 / "rmodule" 0 "xmodule" 0 "angmodule" 0.1 "counter_#" "time_hold" 2.0 Slide 9

10 Generic Model B Simplest data preparation process for the SW control system with uniform structure and identical types of modules Absence of the editable invocation records makes impossible accommodation of irregularities in module types and control system configuration. Model B limitation might be caused by the need of retaining time counting data for many modules. That is necessary for reactivation of the time counting process with data from previous integration steps. That is particularly important for the timers of the arresting modules, which can start in different moments due to differences in current settings. Five specific variables per module should be retained to facilitate the sequential execution. For module N: storage1-n - module status; storage2-n - time-up" timer triggering time; storage3-n - time_up" timer triggering flag; storage4-n - time_up timer start time, sec. storage5-n - time_down timer start time, sec. About 100 storage variables, available for EPCMODs in the existing versions of GE PSLF can accommodate only 20 modules (or groups of modules). Model A with separate EPCMOD invocations does not have such a limitation. This limitation, probably, would not exist for the models functioning in the core of GE PSLF, or with PSS/E and PowerWorld. Slide 10

11 Remote Control Model The remote model is for joint operation of local and remote control, providing additional loading of a line, which is in the same path with the overloaded line. The remote actions are specified in switching sequences along with disturbances and ordinary RAS. Remote model may allow flow increasing module engagement, if 1) there is a sufficient room for flow increase and 2) some modules are engaged on the overloaded line. Slide 11

12 Recommendation Based on the model comparison, Smart Wires recommends primary implementation of Generic Model A, which is applicable with any irregularities in module control setup and parameters, and a mixture of module types. Inclusion of both types of generic models in the core of the stability packages should be also considered because that would give the user a choice of using a model, which is more consistent with a study type, a control system structure and its irregularities. Data preparation for Model A is much simpler than for the Detailed Model. The modified Data Builders could be still useful for the preparation of the initial set of invocation records to be corrected to reflect irregularities and a mixture of module types. There is no need for a Model B Data Builder. Slide 12

13 Additional Steps As the WECC Criteria for Acceptance of New Dynamic Models guideline suggest, SW has developed working model prototypes with modifications, recommended by MVWG; conducted validation studies for different operating conditions, and submitted the required documents and descriptions. SW requests a final MVWG review of the presented materials and identification of additional SW actions for model inclusion in the WECC Approved Dynamic Model Library. SW expects that MVWG descriptions of the necessary actions would include answers to the following questions: Can a completely functional EPCMOD type of PSLF dynamic model be included in the Library, or should it be incorporated in the core of the program? If using EPCMOD is acceptable, what tasks of the GE PSLF team might be needed for model inclusion in the Library? (a GE PSLF expert review certainly can reveal more elegant construction of some model fragments). Are EPCMOD review or inclusion in the core activities a part of the PSLF maintenance or should it be financed separately? Can the PSLF version of the model be included in the Library prior to model development completion for PSS/E and PowerWorld? Slide 13