Experiences in Managing Settings

Bryan J Gwyn

National Grid USA

2

Instances that Trigger Setting Changes

Asset Replacement the relay is replaced as part of an asset replacement

program

Failure The relay fails in service and is replaced

Transmission Line Re-conductoring A transmission line is re-conductored and the line

impedance changes thus effecting the reach of distance relays

3

Instances that Trigger Setting Changes

Neighboring Utility Changes A neighboring utility changes the configuration of an

interconnection, such as adding a new station on an interconnecting transmission line, or upgrading facilities

Externally Mandated Changes An example is the North American Electric Reliability

Council (NERC) recommendation 21a following the August 14th Blackout of 2003. It requires that relay settings be reviewed to determine if they will trip on load under extreme emergency conditions. Relays that do not meet this requirement shall be reset, upgraded or replaced to mitigate the overreach

4

Instances that Trigger Setting Changes

Miss-operations A relay fails to operate or operates when it

should not have at the time of a power system fault. This could be attributed to setting errors or relay malfunctions

Temporary System Arrangements A transmission line may be reconfigured

temporarily during a construction project, such as a temporary line tap

5

Instances that Trigger Setting Changes

Setting Reviews Protection settings are reviewed after a long

period of time of no activity on a particular line and it is found that the settings are no longer adequate due to system configuration and load changes

New Connections Settings need to be changed due to a new load

or generation connection

6

Instances that Trigger Setting Changes

Manufacture recommendation or Alert Settings may need to be changed due to

firmware upgrades to solve a particular problem that has manifested itself.

7

Process for Managing Protection Settings

A Process currently being used at National Grid USA

8

Process for Managing Protection Settings- Objectives -

Consistency with Standards

1 & 3-Lines and Schematics

Calculation worksheets Microprocessor relay shell files

Protection Material

Documented NGrid Application

9

Process for Managing Protection Settings- Objectives -

Peer Reviews Part of ensuring that there is consistency with

standards and policies & training less experienced engineers

Assurance that correct setting is in relay How the setting is issued to the field and

loaded into the relay

10

Process for Managing Protection Settings

Create Setting&

Test Data

Review Standards

Review

Issue to Field

Load Settings

Commission

DownloadSettings &

Return to File

11

Process for Managing Protection Settings - Review Standards -

Engineer reviewsSetting policy & Standards

with Manager

Quality checkParticular methods

noted on Setting Review Record Sheet for each job

National Grid Standards

Create Setting&

Test Data

Review Standards

Review

Issue to Field

Load Settings

Commission

DownloadSettings &

Return to File

12

Process for Managing Protection Settings- Calculate Settings and Peer Review -

Create Setting&

Test Data

Review Standards

Review

Issue to Field

Load Settings

Commission

DownloadSettings &

Return to FileEngineer uses calculation and setting

templates from guideline To create setting -

not the last job settingNational Grid Application Guide

Quality checkPeer review

of calculations(informal meeting of peers for critique) -

Errors noted onSetting Review Record Sheet

Create Setting&

Test Data

Review Standards

Review

Issue to Field

Load Settings

Commission

DownloadSettings &

Return to File

13

Process for Managing Protection Settings

No settings are entered into a database

The setting file itself is treated as an object

Setting file follows a naming convention and can be tracked through the work flow cycle

Use of templates reduces risk of incorrect settings in unwanted functions

14

Process for Managing Protection Settings

A summary of the file is made at the end of the cycle for quick reference

If full setting details are needed the object setting file is accessed eliminating the need for a setting database

Setting review record sheet is kept for quality assurance and process improvement

15

Process for Managing Protection Settings- Issue Settings to Field -

Engineer issues electronic setting file to the Field with electronic cover sheet and

test data file to a Structured, controlled server shared drive Quality check

Standard naming convention used

1. Substation_Line or devise_Sys_yyy_mm_dd_setting file.mdb2. (same as above)_test.xls

3. (same as above)_memo page.xls

Field Supervisor A

Field Supervisor B

Create Setting&

Test Data

Review Standards

Review

Issue to Field

Load Settings

Commission

DownloadSettings &

Return to File

16

Process for Managing Protection Settings- Issue Settings to Field -

• Controlled access by Field Supervisor

• Read only to everyone else

17

Process for Managing Protection Settings- Loading Settings and Commissioning -

Field Supervisor assigns setting to Technician and

moves the electronic setting and test files to the

‘assigned’ file on the Server

Approved-pending file

1. Substation_Line or devise_Sys_yyy_mm_dd_setting file.mdb

2. (same as above)_test.xls3. (same as above)_memo page.xls

Assigned file

1. Substation_Line or devise_Sys_yyy_mm_dd_setting file.mdb

2. (same as above)_test.xls3. (same as above)_memo page.xls

Create Setting&

Test Data

Review Standards

Review

Issue to Field

Load Settings

Commission

DownloadSettings &

Return to File

18

Process for Managing Protection Settings- Loading Settings and Commissioning -

Assigned file

1. Substation_Line or devise_Sys_yyy_mm_dd_setting file.mdb

2. (same as above)_test.xls3. (same as above)_memo page.xls

Supervisor issues electronic

setting files to Technician – specifically

named files for specific

protection scheme

Create Setting&

Test Data

Review Standards

Review

Issue to Field

Load Settings

Commission

DownloadSettings &

Return to File

19

Process for Managing Protection Settings- Download Commissioned Settings & Return to Supervisor -

Downloaded file after commissioning

1. Substation_Line or devise_Sys_yyy_mm_dd_setting file.mdb

3. (same as above)_memo page.xls

Create Setting&

Test Data

Review Standards

Review

Issue to Field

Load Settings

Commission

DownloadSettings &

Return to File

Supervisor saves returned file to ‘current setting file’ on server by substation name and makes summary file for quick reference

Technician downloads setting after

commissioning and returns file to

Supervisor by locally agreed

method

20

Process for Managing Protection Settings- Controlled Read Only Access to Settings -

Field Supervisor

OperationsProtectionEngineer

21

Process for Managing Protection Settings

Setting file object can now be stored in recently installed Asset Information Management & System (AIMMS) along with protection relay data

AIMMS can replace the shared server files for storage and access

Relay Associated With Primary Asset (eg transformer)

Relay data(e.g. make, serial no., firmware version)

Relay setting file – Object(Substation_Line or devise_Sys_yyy_mm_dd_setting file.mdb)

Maintenance history(Scheduling, compliance reporting, auditing)