Automatic Relay Setting Generator (ARSG) User Guide · 2019. 11. 5. · E.g., If 87L scheme for 2-terminal line is selected, the textboxes for remote CT and tap load will be displayed.

Automatic Relay Setting Generator (ARSG)

User Guide

Utility Automation Solutions LLC

2

NOTICE

ARSG is a computer program developed by Utility Automation Solutions, LLC. (UAS). The information in this document is subject to change without notice. Copyright@ 2018-2019 for Utility Automation Solutions, LLC (UAS). All rights reserved. HOW TO REACH UAS

Email: [email protected] Phone: (614)401-8641 Web Site: www.uauto.solutions

TABLE OF CONTENTS

1. INTRODUCTION ......................................................................................................... 3

2. INSTALLATION AND SETUP ......................................................................................... 4

2.1 INSTALLATION .................................................................................................................. 4

2.2 ARSG SETUP ...................................................................................................................... 5

3. AUTOMATED SETTING DOCUMENTS .......................................................................... 6

3.1 LINE PROTECTION ............................................................................................................. 6

4. AUTOMATED SETTING FILE UPDATE ......................................................................... 12

5. AUTOMATED ONELINER RELAY MODELING .............................................................. 12

6. AUTOMATED RELAY TEST FILE GENERATION ............................................................ 13

3

1. Introduction The Automatic Relay Setting Generator (ARSG) is a software program designed for protection engineers to develop relay settings in an automatic manner. The ASPEN Oneliner is used by ARSG to perform fault simulations. Based on the network data retrieved from Oneliner and the fault simulation results, ARSG will calculate the relay settings automatically. Meanwhile, the setting document in the form of Excel spreadsheet is generated. By using ARSG, the protection engineer only needs to review the settings in the setting document and make adjustment if necessary. The setting document itself is also a tool because it includes numerous functions to help the reviewer to check settings and coordination. The NERC PRC compliance evidence are embedded in the setting document. After the setting review process, the setting files of SEL and GE relays can be updated by using ARSG with a click of button. The Oneliner file can also be updated with new relay models per settings in the setting document. What’s more, the relay test plan (DOBLE .psx file) and test report can be generated by ARSG, which uses the apparent currents and voltages from fault simulations to check the relay response. In summary, ARSG has the following features: • Perform fault simulations and retrieve network data by using Oneliner automatically

• Calculate relay settings automatically per network data and fault simulation results

• Automatically generate relay setting document in the form of Excel spreadsheet and PDF

• Update relay setting files (*.rdb, *.urs, *.scd, *,selaprj) automatically

• Update ASPEN Oneliner file with new relay models automatically

• Generate relay test files automatically

• The automated relay settings can be adjusted by reviewer

• The setting spreadsheet includes coordination check functions

• The setting document contains detailed explanations of the main protection settings

• The setting document contains evidence for NERC PRC-023, NERC PRC-001 compliance

• The setting document includes illustrations of relay coordination to support NERC PRC-027

requirements

4

2. Installation and Setup

2.1 Installation

ARSG is delivered in the form of an executable installation file, e.g. ARSG_V1010_Installer.exe. After opening or double-clicking this file, the typical Windows program installation process will start. The first dialog is about License Agreement. If “I accept the agreement” is selected and the “Next” button is clicked, the dialog for ARSG destination folder will be shown, as illustrated below. The default installation folder is “C:\Program Files (x86)\ARSG”.

The next dialog will ask for ASPEN Oneliner Directory. Since ARSG uses Oneliner to perform fault simulations and to retrieve network data, the path to the Oneliner installation folder needs to be found by ARSG. The default Oneliner path is “C:\Program Files (x86)\ASPEN\1LPFv14”. If Oneliner was installed in a different directory, the full path of the Oneliner directory should be put in this dialog with the aid of “Browse…” button.

After ARSG is installed, there should be a desktop icon and an icon in Windows Start menu to launch ARSG.

5

2.2 ARSG Setup

After ARSG is launched, it will search the license file and check the license information. ARSG will become functional only if valid license information is verified. The license file may be put in any folder of the PC. If the license file could not be found in the default ARSG directory, the following dialog will be displayed when launching ARSG.

For ARSG corporate user, the license file is an encrypted .chk file. ARSG will use the information in the .chk file to find the license key on the corporate server.

For non-corporate user, a license key file (.key) on local PC is used to check license information. Except for trial key file, the license key file (.key) is generated per request file (.req) that user sent to UAS. The license request file (.req) is created by using ARSGLicRequest.exe, which can be found under ARSG installation directory. Alternatively, the request file can be created by using menu item Help - License Manager - Generate License Request File in ARSG main dialog. The key file is only valid for the PC that had generated the corresponding request file.

Since ARSG uses Oneliner to perform fault simulations, the path to the Oneliner API functions needs to be known by ARSG. ARSG will search the Oneliner folders automatically. If the Oneliner API directory could not be found somehow, user needs to find it by enter the path in a dialog launched from ARSG menu Help - Path of Python API Functions, as shown in below figure.

6

The default path for Oneliner API function is “C:\Program Files (x86)\ASPEN\1LPFv14\OlrxAPI”. Use “Browse” button to find the folder that contains the file olrxapi.dll.

3. Automated Setting Documents

For the first time use of ARSG, the preference should be checked. After clicking the “Preference” button on toolbar or the menu item File - Preference, a dialog will allow user to define the setting preference. Using line protection as example, the default overcurrent curve types, the limits of distance reach percentage, the default margins for overcurrent pickup etc. can be defined in the dialog. Note the “Oneliner Relay Group Tag Indicating Dual Pilot Schemes” must match that in Oneliner’s Preference. This option is used for coordination check because the installation of dual pilot schemes on the adjacent line can relax the requirements for coordination.

The ARSG main dialog has two panes. The left pane includes the treeview for protection objects and protection schemes. When a node in the treeview is selected, the corresponding dialog will be displayed in the right pane. If a functional button on the tool bar is clicked, the corresponding dialog will also be displayed in the right pane.

In each settings generation dialog, the Oneliner project file (.olr) needs to be found with the aid of “Browse” button.

3.1 2-terminal Line Protection

On the 2-terminal line relay setting dialog, the entries for Local Bus Name, Remote Bus Name and Tap Bus Name are used to identify the protected line in Oneliner file. The bus names must match

7

those in Oneliner exactly. If there is no tap bus for the line, the Tap Bus Name can be left blank. If there are multiple taps on the line, one of the tap bus names should be entered.

For different protection schemes, the setting dialogs will be slightly different. E.g., If 87L scheme for 2-terminal line is selected, the textboxes for remote CT and tap load will be displayed. If DCB or POTT scheme is selected, the textbox for remote CT and a checkbox “Use Automatic Settings for DCB/POTT at Remote Terminal” will be shown. If the checkbox is unchecked, the remote terminal relay settings associated with pilot scheme should be entered manually.

The Excel should be closed before clicking the button “Generate Settings and Setting Document”. After clicking this button, a progress bar will appear. After about 20 to 40s, the setting document in the form of Excel spreadsheet will be presented.

In the spreadsheet, the buttons labeled “Save as” and “PDF it” can be used to save the document with file name that includes bus names, voltage level, protection scheme and the date.

8

In the setting spreadsheet, the colored cells are used to facilitate setting review process. The cells highlighted yellow or orange can be changed by reviewer. The orange cell indicates that extra attention is needed. The green cells are used for fault simulation data. A gray cell cannot be modified because its value is Excel formula and it is protected. The spreadsheet also includes some basic setting check functions. A red cell is the alarm sign indicating wrong data or wrong setting. The pink cell gives warning sign indicating the setting might cause problem under certain condition. The color codes are summarized as the following,

Data generated automatically but can be changed by reviewer.

Data needs extra attention.

Data from ASPEN Oneliner Fault Simulation.

Data per Excel Formula that cannot be changed directly.

Alarm sign. There is problem with the data or setting.

Warning sign. The setting might cause problem under certain condition.

In the spreadsheet, each protection element has a section for explanations. There is a row for comment at the end of the section. The comment is expected if the reviewer has made any change. If change is made without comment, a red dot will be shown as a reminder. After the comment is added, the red dot will turn green. The following figure gives an example.

The line setting spreadsheet includes plots for 21P, 21G and 50G/51G elements. The adjacent line relay settings were retrieved from ASPEN Oneliner for settings calculation and coordination check. The characteristics of local relays and adjacent line relay are presented to show the coordination.

9

To avoid clutter, each type of protection (21P, 21G or 50G/51G) includes two figures and each figure shows two characteristic curves. One figure illustrates the coordination between the local relay and the selected downstream relay. Another one illustrates the coordination between the local relay and the selected upstream relay. When there are multiple relays to coordinate with, the adjacent line relay that brings the most challenge for coordination would be selected by ARSG. The reviewer can change the plot to show a different relay characteristic. After clicking the “Redraw” button next to the plot, a dialog including other relay settings will be displayed. By using the option buttons and the “confirm” button, the characteristic of a different relay will be shown against that of local relay.

In the figure for 50G/51G , the coordination can be visualized by using a line end 1LG fault, which is indicated by a dot on the curve. The relay operating time and the apparent current are displayed in the plot and in text form underneath the plot. In addition, a shifted curve in dash line is added to illustrate the coordination more clearly. Since each relay will see different apparent current, one of the curves is shifted to align the current with the other one for the same fault, such that reviewer can focus on the operating times of the two relays for the same fault. E.g., if the local relay’s shifted curve is above the downstream relay’s curve with good margins, the coordination is ok.

1 0

The “Redraw” button next to the overcurrent plot can bring up a setting dialog showing the local 50G/51G settings and the adjacent lines’ 50G/51G settings. Different from that for 21P or 21G, the overcurrent settings can be adjusted, and the corresponding figures can be updated per new settings after the “confirm” button is clicked.

Therefore, this dialog can help the reviewer to adjust the pickup setting or time dial setting of time delayed overcurrent relays quickly when doing coordination check. If adjustment to local relay has been made, the button “Save New Settings (Local) to Spreadsheet” will be enabled. After clicking on it, the 50G/51G settings on the spreadsheet will be updated per settings in the dialog.

At the end of line setting spreadsheet, there is a section named Verifications. In this section, the PRC-023-1 compliance check, PRC-001 reminder and pilot scheme coordination check are included. For PRC-023-1 compliance, if one of the 21P/50P/51P relay settings does not satisfy the requirement, a red box will be shown to give the alarm. The automated settings would not cause compliance issue. But since the reviewer can modify settings, such verification can help the reviewer to verify setting changes. Meanwhile, the calculations and flags in this section can provide evidence for NERC PRC-023-1 compliance.

1 1

The ARSG line setting dialog has two checkboxes for PRC-001. One is labeled “It is interconnection requiring PRC-001 process?” and another is labeled “The Settings for PRC001 have been received from the other utility and saved in ASPEN Oneliner?”. They are used for PRC-001 documentation. In the settings spreadsheet, the red-highlighted text is used as a reminder.

If the line protection uses DCB or POTT schemes, the coordination between local and remote terminal relay is important. In Verification section, the local and remote settings that are related to DCB or POTT are summarized and compared side by side, in secondary value and primary value. If a red cell is seen, it indicates there is coordination problem. Reviewer can enter the remote relay settings in yellow cells manually, or use the button to retrieve the settings from setting file(.urs or .rdb) automatically.

1 2

4. Automated Setting File Update

After the setting review process is finished, user can use ARSG to update relay setting files with the settings in the setting document. With corresponding tree node being selected, the button “Update Setting Files” on the toolbar will bring up the dialog in the right pane for setting file updates, as illustrated below. In the dialog, the setting document (.xlsm) and at least one setting file should be entered in corresponding textbox, with the aid of “Browse” button. There are three options for line relay settings, if “Keep the original setting file and create new setting file” is checked, the setting changes will be made to a copy of the setting file. Otherwise, the changes will be made directly to the setting file.

5. Automated Oneliner Relay Modeling

By using ARSG, the relay settings in the setting document can be transferred to Oneliner to update the network model with new relay models. After the “Update Oneliner” button on toolbar is clicked, the dialog for Oneliner Update will be shown in the right pane of the main dialog.

The Oneliner file and the setting document (.xlsm) should be entered in the corresponding textbox with the aid of “Browse” button. There are a few options for Oneliner update in this dialog. If “Create a copy of Oneliner file with new settings” is selected, the changes will be made on a copy of the original Oneliner file. Depending on the selection, both L90 settings or 411L settings may be added to Oneliner, or the settings of one relay can be added. The new relay model in Oneliner should have unique ID. The relay ID to be created would include user-defined prefix (maximum 11 characters), relay type (such as L90, 411L) and function ID (such as PDS, GOC). The prefix is defined by user in the dialog, the relay type and function ID will be defined by ARSG. Depending on the selection, the existing relay settings for the same line terminal can be retained or removed.

1 3

After clicking the button “Add Settings to Oneliner File”, the Oneliner file can be updated with new settings, or a new Oneliner file will be created,

Note: Because of the API function, the updated Oneliner file (.olr) will be in version 15 format. The version 15.0 of Oneliner will be released soon by ASPEN Inc. Before the release of Oneliner v15, the .olr file may need to be changed to version 14.x format. To change the format, just use Oneliner to open the .olr file and save it to another file name.

6. Automated Relay Test File Generation ASRG can also be used to generate relay test files. The relay test plan (Doble .psx file for now) and test report can be created automatically by using the apparent currents and voltages from automated fault simulations. After clicking the “Generate Test Files” on the toolbar, the corresponding dialog will be displayed in the right pane of the main dialog, as illustrated in the following figure.

In this dialog, the Oneliner file and a folder to stock test files need to be put in the corresponding textboxes with the aid of “Browse” buttons. The names of the line terminal buses, CT ratio, PT ratio and the maximum current of the test set are also required inputs. The adjacent bus/station names are required for the test plan since external faults should be used to test the relay. If there is no adjacent lines, the entry for Remote A(or B) station can be left blank. For each station name, two entries as needed - one of them must match the bus name in Oneliner, the other one is for report purpose. Because in many cases, the Oneliner bus name may not be the best name to be shown in the test report. The relay ID are free text, typically they should match those in the drawings. The maximum current output of the test set should be entered in this dialog as well. If the fault current is beyond the range of test set, ARSG will scale the currents and voltages such that the distance protection can still work as expected.

1 4

After the input of the required data is done, the button “Step 1: Select Faults” needs to be clicked to define the fault simulation cases. A fault selection dialog will be displayed, as illustrated in the following figure. In this dialog, a oneline diagram is included to show the fault locations. A list of fault cases is presented on this dialog. The fault type and fault location for each fault can be adjusted per test needs. The button “Add Faults” is used to add new fault cases in this list. To remove any fault case, just select “N/A” as “Location”. If any change is made to the fault list, the “Redraw” button should be clicked to update the Oneline diagram, which will be used in the test report.

1 5

After all the fault cases are defined, the “Confirm and Continue” button can be clicked to close the fault selection dialog. At this stage, the button “Step 2: Generate Test Files” in the main dialog will be enabled. The test plan file (.psx) and the test report file (.xlsm) will be created after the button is clicked. In the test plan file and test report file, each fault is identified by the Fault number that was defined in the fault selection dialog. The test report file includes three sheets, the “FaultData” sheet includes the apparent currents and voltages in primary values. The “InjectionVI’ sheet includes the corresponding currents and voltages in secondary value, which are also the outputs of the test set in the test plan. The “Test Results” sheet can be used by field technician to record the relay operating results.