System Protection Manual

MANUAL 33
System Protection Manual

October 2009
Version:
1.0
Revision Date:
10/29/2009
Committee Acceptance:
12/10/2009
This document was prepared by:

NYISO Operations Engineering Staff
New York Independent System Operator

3890 Carman Road
Schenectady, NY 12303
(518) 356-6060
www.nyiso.com
Disclaimer
The information contained within this manual, along with the other NYISO manuals, is intended
to be used for informational purposes and is subject to change. The NYISO is not responsible for
the user’s reliance on these publications or for any erroneous or misleading material.
©
Copyright 1999-2009 New York Independent System Operator
NYISO SYSTEM PROTECTION MANUAL
Table of Contents
Table of Figures ......................................................................................................................... vi
Table of Tables .......................................................................................................................... vi
Revision History .........................................................................................................................vii
1. Reporting Transmission and Generation Protection System Operations and Protection
System Performance .......................................................................................................... 1-1
1.1 Scope ........................................................................................................................................1-1
1.2 Data Collection and Reporting ..................................................................................................1-1
1.2.1 Transmission Owner Collection Schedule..................................................................1-1
1.2.2 Generation Owner Collection Schedule .....................................................................1-1
1.3 Transmission of Data and Discussion of Results......................................................................1-1
1.3.1 Transmission Owners .................................................................................................1-2
1.3.2 Generation Owners.....................................................................................................1-2
1.4 Information Collected and Data Format ....................................................................................1-2
1.5 Data Collection ..........................................................................................................................1-3
1.6 Follow-Up Actions .....................................................................................................................1-3
1.7 Interpretations ...........................................................................................................................1-4
1.8 Information Requested by NPCC..............................................................................................1-4
1.9 References ................................................................................................................................1-4
2. Application of Disturbance Monitoring Equipment (DME) .............................................. 2-1
2.1 Definitions..................................................................................................................................2-1
2.2 Specification and Settings of DME............................................................................................2-1
2.3 Time Zone .................................................................................................................................2-1
2.4 Survey of DME Equipment........................................................................................................2-2
2.5 Sharing of DME Data ................................................................................................................2-2
2.6 Other .........................................................................................................................................2-2
2.7 References ................................................................................................................................2-2
3. System Protection Data ...................................................................................................... 3-1
3.1 Relay Characteristics ................................................................................................................3-1
3.2 Pilot Protection Systems ...........................................................................................................3-1
3.3 Clearing and Reclosing Times ..................................................................................................3-2
3.3.1 Clearing Times............................................................................................................3-2
3.3.2 Reclosing Times .........................................................................................................3-2
3.3.3 Special Protection Systems ........................................................................................3-3
3.3.4 Special Protection Systems ........................................................................................3-3
3.3.5 Other Remedial Action Systems.................................................................................3-3
3.3.6 SPS Data Submission and Updating Procedures ......................................................3-4
3.3.6.1 Facility Equipment Owner Actions.....................................................................3-4
3.3.6.2 NYISO Actions...................................................................................................3-4
3.4 Power Line Carrier Frequencies ...............................................................................................3-5
3.4.1 Introduction .................................................................................................................3-5
3.4.2 UTC PLC Task Force Contacts ..................................................................................3-5
NYISO Operations Engineering Staff iii

Version 1.0 10/29/2009
3.4.3 UTC PLC Frequencies Database Reports .................................................................3-5

3.4.4 UTC PLC Frequency Coordination Procedures .........................................................3-5
3.4.4.1 PLC Task Force Contact Actions ......................................................................3-6
3.4.4.2 NYISO Actions...................................................................................................3-6
3.4.4.4 NYISO Actions...................................................................................................3-6
3.4.4.6 UTC Actions.......................................................................................................3-7
3.4.5 Procedures for Retiring PLC Frequencies..................................................................3-7
3.4.5.1 PLC Task Force Contact Action ........................................................................3-7
3.4.5.2 NYISO Action.....................................................................................................3-7
3.4.6 Annual Review of the PLC Frequencies Database ....................................................3-7
3.4.6.1 UTC Action ........................................................................................................3-7
3.4.6.3 NYISO Action.....................................................................................................3-8
3.5 Short-Circuit Fault Analysis Data ..............................................................................................3-8
3.5.1 Introduction .................................................................................................................3-8
3.5.2 Annual Review of Short-Circuit Representation .........................................................3-8
3.5.2.1 Facility Equipment Owner Action.......................................................................3-8
3.5.2.2 NYISO Action.....................................................................................................3-8
4. Automatic Underfrequency Load Shedding Reporting and Compliance ....................... 4-1
4.1 Entities.......................................................................................................................................4-1
4.2 Schedule ...................................................................................................................................4-1
4.3 Computation of Load.................................................................................................................4-2
4.4 Format .......................................................................................................................................4-2
4.5 Notifications...............................................................................................................................4-3
4.6 References ................................................................................................................................4-3
5. System Protection Maintenance Reporting ...................................................................... 5-1
5.1 Scope ........................................................................................................................................5-1
5.2 Compliance Reporting...............................................................................................................5-1
5.3 Maintenance Reporting .............................................................................................................5-1
5.4 Report Review...........................................................................................................................5-1
5.5 Reference..................................................................................................................................5-2
Appendix A. Guide for the Selection of Power Line Carrier Frequencies........................... A-1
A.1. Introduction............................................................................................................................... A-1
A.2. PLC Modulation Techniques .................................................................................................... A-1
A.2.1. Amplitude Modulated Keyed Systems ....................................................................... A-1
A.2.2. Frequent Shift Keyed Systems .................................................................................. A-1
A.2.3. Single Side Band Systems ........................................................................................ A-2
A.3. General PLC Application Criteria ............................................................................................. A-2
A.3.1. Trapping and Coupling .............................................................................................. A-2
A.3.2. Factors Affecting Frequency Selection ...................................................................... A-2
A.4. Frequency Spacing by Equipment Type .................................................................................. A-3
A.4.1. On-Off (AM) Blocking Carrier..................................................................................... A-3
A.4.2. Frequency Shift (FSK) ............................................................................................... A-4
A.4.3. Single Sideband......................................................................................................... A-4
iv NYISO Operations Engineering Staff

Version 1.0 10/29/2009
A.5. References ............................................................................................................................... A-6

Appendix B. Protection System Performance (PSP) Reporting Instructions ..................... B-1
B.1. Introduction............................................................................................................................... B-1
B.2. Discussion ................................................................................................................................ B-1
B.3. General Instructions ................................................................................................................. B-2
B.4. Coding Instructions .................................................................................................................. B-3
B.4.1. Participant .................................................................................................................. B-3
B.4.2. File Number ............................................................................................................... B-3
B.4.3. Date/Time .................................................................................................................. B-4
B.4.4. Event.......................................................................................................................... B-4
B.4.4.1. Initiating Condition ............................................................................................ B-4
B.4.4.2. Resulting Condition........................................................................................... B-4
B.4.4.3. Element/Location .............................................................................................. B-4
B.4.4.4. Circuit/Equipment ............................................................................................. B-4
B.4.4.5. Auto Restore..................................................................................................... B-4
B.4.4.6. Auto Reclose .................................................................................................... B-4
B.4.4.7. High-Side Voltage............................................................................................. B-4
B.4.4.8. Station............................................................................................................... B-4
B.4.4.9. Protection System I.D. ...................................................................................... B-5
B.4.4.10. Protection System Operations.......................................................................... B-5
B.4.5. Pilot System Packages .............................................................................................. B-6
B.4.5.1. Line Package .................................................................................................... B-6
B.4.5.2. DTT Package.................................................................................................... B-6
B.4.6. Comments.................................................................................................................. B-7
B.4.7. Submitted By.............................................................................................................. B-7
Appendix C. Forms .................................................................................................................. C-1
C.1. Relay Characteristics Form...................................................................................................... C-2
C.2. Clearing Times Form................................................................................................................ C-4
C.3. Reclosing Data Form ............................................................................................................... C-5
NYISO Operations Engineering Staff v

Version 1.0 10/29/2009
Table of Figures
Reserved for future use.
Table of Tables
Table A.1 ON – OFF Carrier Frequency Spacing ....................................................................... A-4

Table A.2 FSK Carrier Frequency Spacing................................................................................. A-4
Table A.3 Single-Sideband Equipment Operating Parameters................................................... A-6
Table B.1 Event Table ................................................................................................................ B-7
Table B.2 Incorrect Personnel Table .......................................................................................... B-8
Table B.3 Incorrect Relay Table ................................................................................................. B-9
vi NYISO Operations Engineering Staff

Version 1.0 10/29/2009
Revision History
Version Date Revisions
1.0 10/29/2009 Initial Release
NYISO Operations Engineering Staff vii

Version 1.0 10/29/2009
This page intentionally blank.
viii NYISO Operations Engineering Staff

Version 1.0 10/29/2009
1. R EPORTING T RANSMISSION AND

G ENERATION P ROTECTION S YSTEM
O PERATIONS AND P ROTECTION S YSTEM
P ERFORMANCE
The processes outlined below are intended to fulfill the requirements for reporting and analyzing
Bulk Power System (BPS) protection system operations as assigned to the New York
Independent System Operator (NYISO) System Protection Advisory Subcommittee (SPAS).
These processes are in compliance with applicable NPCC Procedures and NERC Standards,
which are listed as references
1.1 Scope
The NYISO SPAS has been assigned the responsibility of analyzing BPS Protection System
Performance (PSP) and maintaining a record of all BPS protection system operations. This
function was initiated mainly so that the benefits of these experiences would be shared
among SPAS members.
1.2 Data Collection and Reporting

NYISO staff facilitates the data collection and analysis of the results with the New York
Control Area (NYCA) Transmission and Generation Owners on a quarterly basis.
On or about the 20th day of the last month of each quarter, NYISO staff shall initiate a
reminder via e-mail to those individuals identified by each BPS Transmission Owner and
Generation Owner as their Protection System Performance (PSP) contact. The reminder
shall set forth the collection schedule. The collection schedule is normally as outlined in the
following two subsections.
1.2.1 Transmission Owner Collection Schedule

Protection System Performance (PSP) data for each quarter shall be transmitted to NYISO
staff by e-mail on or before the 20th of the month that follows each quarter.
1.2.2 Generation Owner Collection Schedule

Generation Operations data for each quarter shall be transmitted to NYISO staff by e-mail
on or before the 20th of the month that follows each quarter.
1.3 Transmission of Data and Discussion of Results

The quarterly data is then discussed and analyzed at the next regularly scheduled SPAS
meeting. For this reason, SPAS meetings are normally scheduled shortly after the PSP data
NYISO Operations Engineering Staff 1-1

Version 1.0 10/29/2009
is due. This schedule may be adjusted in some quarters due to constraints such as
conflicting meetings.
1.3.1 Transmission Owners

Each Transmission owner representative shall have transmitted a PSP system (.xls) file
containing reports on all reportable operations for the previous quarter, and .pdf files for
each of the incorrect operations during that quarter, as outlined in section 1.2.1. At the
SPAS meeting, each Transmission owner representative shall review for the sub-committee
each of the incorrect operations during that quarter. Each review shall include electronic
projection of the report file by NYISO staff. In cases where the determination of correct or
incorrect is in doubt, the SPAS will review the report and make a determination.
1.3.2 Generation Owners

Generation Owner representatives are encouraged to attend the SPAS meetings to discuss
their operations; however, due to the relatively few generation-related protective system
operations, it is acceptable for the Generation Owners to simply submit a written report and
be available by phone to discuss the operations, if deemed necessary by NYISO staff and/or
the SPAS. NYISO staff shall summarize the results from the previous quarter and provide a
verbal report on any operation judged to be incorrect. In cases where the determination of
correct or incorrect is in doubt, the SPAS will review the report and make a determination.
1.4 Information Collected and Data Format

Software for reporting events, called the NYISO PSP System, shall be distributed by
NYISO staff. As a minimum, the following information shall be reported:
Transmission Owner Name
File Number
Date and Time of Event
Initiating Condition
Resulting Condition
Element/Location
Auto Restored (Y or N) and Auto Reclosed (Y or N)
High Side Voltage
Station
Protection System ID
Protection System Operation, Number, and Code
Pilot System Line Code
Pilot System DTT Code
Comments
1-2 NYISO Operations Engineering Staff

Version 1.0 10/29/2009
Name of Individual Making Report

NYISO PSP data includes data on operations of both conventional protections systems and
Special Protection Systems (SPS).
Collection methods are subject to updates and revisions as required.

A format for reporting events will be distributed by NYISO staff. As a minimum, the
following information shall be reported on this form.
Date of Report
Date of Operation
Time of Operation
Time Synchronization Source
Equipment Removed from Service
Root Cause Protection Function
Correct or Incorrect
Explanation and Corrective Action Plan for Incorrect Operations
Name of Individual Making Report
Plant Name and Unit Number
1.5 Data Collection

New York State Transmission Owners shall use a Microsoft® Access database to collect
and transmit the PSP data to the NYISO. In addition, those operations that receive an
“incorrect” code shall be transmitted to NYISO staff in the form of .pdf files.

New York State Generation Owners shall use the Microsoft Word format provided each
quarter by NYISO staff.
1.6 Follow-Up Actions

NYISO staff will archive the incorrect report .pdf files as they are received in advance of
each SPAS meeting. These are subject to NPCC or NERC audit.

Version 1.0 10/29/2009
Any items that are incomplete or remaining under investigation should be documented in
the SPAS meeting minutes and action items list and addressed at subsequent SPAS
meetings until the items are closed.
Any mitigation plans should be presented to SPAS and documented in the SPAS meeting
minutes and action items list and addressed at subsequent SPAS meetings until the items
are closed.
1.7 Interpretations
Questions of interpretation should be brought for discussion at the SPAS meeting
immediately following the quarter during which the event occurred. Such discussions may
result in rules or interpretations being added to this manual or subsequent Technical
Bulletins.
1.8 Information Requested by NPCC

NPCC B-21 requires that analysis of misoperations shall be initiated by Generation Owners
and Transmission Owners, and that the required information shall be supplied to the Area
(NYISO) in accordance with policies established in each Area. Generation Owners and
Transmission Owners are also required, under certain circumstances, to supply results of
their analysis to NPCC. Please see the most recent version of NPCC B-21 for details.
1.9 References
NPCC B-21, “Guide for Monitoring of Protection System Misoperations,” July 14,
2004, or most recent version, available at the following address:
http://www.npcc.org/
NERC PRC-003-1, “Regional Procedure for Analysis of Misoperations of
Transmission and Generation Protection Systems,” or most recent version, available
at the following address:
http://www.nerc.com/
NERC PRC-004-1, “Analysis and Mitigation of Transmission and Generation
Protection System Misoperations,” or most recent version, available at the following
address:
NERC PRC-016-0, “Special Protection System Misoperations,” or most recent
version, available at the following address:

Version 1.0 10/29/2009
2. A PPLICATION OF D ISTURBANCE
M ONITORING E QUIPMENT (DME)
Disturbance Monitoring Equipment (DME) as used in this document includes, but is not
necessarily limited to, dynamic disturbance recorders, digital fault recorders, and phasor
measurement units.
The NYCA has long been a pioneer in the effective application of DME and continues to be
exemplary in its ability to effectively use DME to accomplish the three main purposes: (1) model
validation, (2) disturbance investigation, and (3) assessment of system protection performance.
The NYCA has also been an active participant in preparation of the various DME-related
documents of the IEEE, North American Electric Reliability Corporation (NERC), the Northeast
Power Coordinating Council, Inc. (NPCC), and the New York State Reliability Council
(NYSRC); several of the most important documents are listed in the section 2.7, “References,”
below. This Manual addresses only those items that are not already covered in the applicable
documents of NERC, NPCC, and NYSRC.
2.1 Definitions
DME – Disturbance Monitoring Equipment
DDR – Dynamic Disturbance Recorder
DFR – Digital Fault Recorder
PMU – Phasor Measurement Unit
NYISO – The New York Independent System Operator, an Area Reliability Coordinator
TO – Transmission Owner
GO – Generation Owner
2.2 Specification and Settings of DME

This subject is well covered in NPCC and NERC documents. The following are additional
items not covered in these documents:
DDRs and DFRs should automatically extend records when a re-trigger occurs while a
recording is in progress.
Any new DME shall have PMU-capability.
2.3 Time Zone

The NYISO prefers that DDRs and DFRs be set to Universal Time Zone (UTZ).
In the event DDRs and/or DFRs are set to local time, records transmitted to the NYISO
shall contain the hours offset from UTC in the file name consistent with the IEEE C37.232
Standard.

Version 1.0 10/29/2009
2.4 Survey of DME Equipment

NYISO staff shall survey the status of DME in the NYCA approximately every two years.
This activity shall be coincident with a NPCC survey if a NPCC survey is undertaken.
2.5 Sharing of DME Data

Through applicable NYISO Tariffs and Market Participant agreements, the NYISO has the
right to ask for any DME data needed to fulfill its functions as Reliability Coordinator.
When necessary, the NYISO will request individual DME records or files from TOs and
GOs.
Individual records/files furnished as part of a disturbance investigation shall be in IEEE
COMTRADE format, and file names shall be in accordance with IEEE C37.232-2007
convention, except by agreement among the parties involved. Depending on the volume of
data, the NYISO may request individual records be forwarded electronically, or that a
group of files or records be placed on a CD or DVD and shipped to the NYISO by express
delivery service.
2.6 Other
DME installed by New York TOs and GOs shall be operated and maintained in accordance
with the requirements of NPCC Criteria A-15 and NERC Standard PRC-018-1.
Consideration should be given to consultation with NYISO staff in regard to DME
locations and configuration.
2.7 References
NYSRC Rule C-R5, “Disturbance Recording”
NPCC Criteria A-15, “Disturbance Monitoring Equipment Criteria”
NERC Standard PRC-002-1, “Define and Document Disturbance Monitoring
Equipment Requirements”
NERC Standard PRC-018-1, “Disturbance Monitoring Equipment Installation and
Data Reporting”
NPCC Guideline B-25, “Guide to Time Synchronization of Substation Equipment”
NPCC Guideline B-26, “Guide for Application of Disturbance Recording
Equipment”
IEEE C37.111-1999, “IEEE Standard for Common Format for Transient Data
Exchange (COMTRADE) for Power Systems”
IEEE C37.232-2007, “IEEE Recommended Practice for Naming Time Sequence
Data Files”

Version 1.0 10/29/2009

Version 1.0 10/29/2009
3. S YSTEM P ROTECTION D ATA

Transmission system protection data is required to develop and maintain functional models of
the transmission and generation BPS protection devices that can be used for dynamic simulation
and for the coordination of protection facilities with the existing and proposed system
reinforcements. Some of the data is also required for other aspects of power system operation
and operating studies, such as thermal and voltage contingency analysis. This section describes
the requirements and procedures for reporting this data to the NYISO.
Facility Equipment owners’ system protection engineering staff shall provide data to the NYISO
System Protection Coordinator upon request. In general, the time period allowed for such data
request is 30 days; however, in special circumstances, a shorter time period may be necessary.
Characteristics of protection equipment associated with NYISO-secured Transmission System
facilities are important for dynamic simulation and other aspects of NYISO operations.
3.1 Relay Characteristics

Protection systems may be specifically (rather than generically) modeled when they could
operate within the scope of system dynamic simulations (power system stability analyses).
When the actual relay system characteristics are not available, a generic relay model may be
used. When appropriate, over-current or out-of-step protection may also be modeled. A
simplified data submission form is included in this manual as the Relay Characteristics
Form, found on page C-2.
Relay characteristics are required only for relays that could trip for an apparent three-phase
fault (e.g., a power swing) to evaluate the possibility of additional trips during the post-
transient swing following the clearing of the fault.
Relay characteristics are not used for the purpose of determining clearing times or for the
primary clearing of a fault, in the dynamic simulation. Appropriate clearing times are
determined by the design of the protection groups on each transmission facility and are
reported separately. Please see the Clearing Times Form, included in this manual on page
C-4.
Margins should not be applied to the relay characteristic data. In the course of the study
analyses, margins may be applied to the relay characteristics when relay actions are
evaluated as part of a stability simulation.
3.2 Pilot Protection Systems

Pilot protection systems are defined as those systems that utilize a communications channel
in comparing fault conditions at the line terminals of a transmission line to determine
whether the fault is internal or external to that particular line section.
The procedures described in this manual shall be used by the Transmission Owners to
prepare and submit the protection systems relay characteristics data to the NYISO. The
relay data should be furnished on the Relay Characteristics Form, found on page C-2. If the
relay schemes do not lend themselves to this form (only Mho-distance or reactance-distance

Version 1.0 10/29/2009
relays), separate pages shall be attached. If the Facility Equipment owner is using the Power
Technologies, Inc. PSS/E program, then PSS/E input forms may be attached to the Relay
Characteristics Form.
3.3 Clearing and Reclosing Times

Estimated protection system clearing times are required for all ISO-secured facilities. Data
on automatic closing of circuit breakers without operator initiation (known as reclosing) is
required for the transmission facilities that have high-speed reclosing and/or hot-bus/dead-
line reclosing.
3.3.1 Clearing Times

Facility Equipment owners shall use the following assumptions when calculating the fault
clearing times to be submitted to the NYISO:
Maximum system short-circuit capacity.
Faults are solid, three-phase faults.
Use both near-end and far-end line faults.
Do not consider bus faults when computing transmission-line clearing times.
All relays operate correctly, that is, the operating time used is that of the faster of
two redundant protection groups.
Speed of operation of circuit breakers and relay equipment is the nominal speed
quoted by the manufacturer.
Clearing time is a single value, from fault inception until breaker clearing.
For pilot systems, communication time is included for far-end faults.
No margin shall be added to the clearing times.
Clearing times for single phase to ground faults may be requested by NYISO staff
when needed.
3.3.2 Reclosing Times

The following information is required by the NYISO for reclosing relay protection data:
High speed reclosing times
Relay reclosing time in seconds
Breaker reclosing time in cycles
Delayed reclosing times in seconds
First Shot: Hot-bus/dead-line reclosing time in seconds
Second Shot: Hot-bus/dead-line reclosing time in seconds
Third Shot: Hot-bus/dead-line reclosing time in seconds
A data submission form is included in this manual as the Reclosing Data Form, found on
page C-5. Reclosing terms are used as defined in the NPCC document, “Guide for the
Application of Auto Reclosing to the Bulk Power Systems,” Document B-1.

Version 1.0 10/29/2009
3.3.3 Special Protection Systems

Protection-based systems that are designed to monitor special system conditions can have
an impact on system operation. The NYISO requires that the following protection systems
be described and reported to the NYISO according to the guidelines of this section:
Special Protection Systems (NPCC definition)
Other Remedial Action Systems (NYISO definition)
3.3.4 Special Protection Systems

An SPS is defined by NPCC as a protection system designed to detect abnormal system
conditions and take corrective action other than the isolation of faulted elements.
Facility Equipment owners are required to prepare and submit to the NYISO an SPS
description that includes but is not limited to the following information about the SPS:
Initiating incident (SPS trigger or triggers)
Resulting action
Total clearing time
Reason for use
Percent of time in service
NPCC classification
This information shall be provided by the Facility Equipment owner’s System Protection
Advisory Subcommittee (SPAS) member to the NYISO System Protection Coordinator in
accordance with NPCC Criteria.
An SPS description shall be prepared for any SPS that is located within the NYCA or
involves any ISO-secured facility or tie line between the NYCA and a neighboring control
area.
The NPCC Task Force on System Protection maintains an SPS list that is updated and
posted annually by NPCC.
3.3.5 Other Remedial Action Systems

In addition to NPCC SPSs, NYISO TOs, GOs, Load-Serving Entities (LSEs), or other
participants may operate other remedial action systems that are similar in concept to SPSs
and that may have an effect on NYCA operations, even though the scheme does not fit the
NPCC definition of an SPS. These systems must also be described and reported to the
NYISO. Some examples of protection systems could have an effect on NYCA operations
are:
A protection system included in transient stability simulations that effects the results
of the simulation
A protection system that causes a change in operating limits
A protection system used by a Facility Equipment owner that allows the
Transmission Provider to mitigate a transmission security limitation

Version 1.0 10/29/2009
A protection system that limits the ability to load a facility to rated Short-Term
Emergency (STE) capability
The NYISO System Protection Coordinator notifies the Facility Equipment owner SPAS
Member when one of the above situations is detected and a NYISO System Impacting
Protection Memo System report is required.
3.3.6 SPS Data Submission and Updating Procedures

The following procedures apply to all data described in the sections 3.4.1 and 3.4.2 unless
otherwise indicated.
3.3.6.1 Facility Equipment Owner Actions

1. Submit to the NYISO System Protection Coordinator updates to the following data
for all facilities found to be Bulk Power system facilities by NPCC criteria A-10,
upon the implementation of a new System Impacting Protection System, or upon
NYISO request:
a. Relay characteristics using the Relay Characteristics Form found on page C-2 of
this manual.
b. Clearing times using the Clearing Times Form, found on page C-4 of this
manual.
c. Reclosing times using the Reclosing Data Form, found on page C-5 of this
manual.
2. Submit to the NYISO System Protection Coordinator the SPS report at least three
months before placing the SPS in service.
3. Submit SPS data for all new or modified transmission facilities not later than three
months prior to the scheduled in-service date of the protection system. If setting
changes are made, the data shall be furnished upon implementation.
4. In the case of transmission lines which are interconnections with neighboring
control areas, the TO SPAS representative shall submit data for all terminals of the
line.
3.3.6.2 NYISO Actions

1. Once each year the NYISO System Protection Coordinator will transmit all data
back to each TO SPAS Representative for confirmation or revision.
2. Use the SPS data in the dynamic simulation, thermal, and voltage contingency
analysis studies.
3. Inform the Facility Equipment owner SPAS member when SPS conditions are
present and a new report is needed.
4. When the review is complete, the NYISO shall issue updates to the NYISO
Protection Memo document and distribute to appropriate Facility Equipment owner
and NYISO personnel.

Version 1.0 10/29/2009
3.4 Power Line Carrier Frequencies

This section describes the procedure for coordination of Power Line Carrier (PLC)
Frequencies among Facility Equipment owners of NYISO and neighboring systems. As part
of the coordination process, information is provided for updating PLC databases maintained
by the Utilities Telecommunications Council (UTC).
3.4.1 Introduction
Coordination of PLC frequencies within New York State is the responsibility of the NYISO
successor group to the System Protection Advisory Subcommittee (SPAS).
In order to carry out these coordination responsibilities, the NYISO participates as part of a
working group known as the Power Line Carrier Task Force, or PLC Task Force. This task
force comprises designated UTC PLC Data Base Contacts and the NYISO System
Protection Coordinator.
The PLC Task force originally collected and supplied information on New York PLC
facilities to NERC, which later turned over to UTC the responsibility of maintaining the
PLC Database.
3.4.2 UTC PLC Task Force Contacts

Each Facility Equipment owner designates a PLC Task Force contact to represent it. A list
of the New York PLC Task Force contacts is maintained by the NYISO.
This list is distributed annually to all PLC Task Force contacts and to SPAS. Changes to
this list must be reported by the Equipment owner contact to the NYISO contact and
System Protection Coordinator as soon as possible. The NYISO will report such changes to
the SPAS and all PLC Task Force contacts.
3.4.3 UTC PLC Frequencies Database Reports

Two UTC PLC Frequencies Database reports are available by contacting the UTC. Turn
around time for receipt of any of the reports is approximately three working days.
Individual Organization Report — Details an individual organization’s PLC
frequencies. The PLC Frequency data is sorted by substation, transmitter and
associated receiver(s), and frequencies.
Interference Report — Details any PLC or licensed user frequencies that are within
potential interference distance or frequency range of a proposed or in-use PLC
frequency. The criteria used for interference distance is 50 miles.
3.4.4 UTC PLC Frequency Coordination Procedures

The PLC frequency coordination procedure applies in the following cases:
To request addition of a new PLC frequency for immediate or future use
To request a current frequency change

Version 1.0 10/29/2009
In all these cases, the PLC Frequency Data Report form is completed and sent to the
NYISO. The instructions for forms PLC1 and PLC2, and the forms themselves, are
available on the UTC Web site at this address:
http://www.utc.org/utc/plc-forms-instructions
All the information on Form PLC2 form must be completed, and the applicable UTC
Transaction Code for this form must be specified. All transmitter information entered for
the first time shall be designated as transaction code A or P.
Add in service A
Add in proposed P
Correction C
Delete D
3.4.4.1 PLC Task Force Contact Actions

The Facility Equipment owner PLC Task Force contact shall initiate the process by
submitting a completed PLC Frequency Data Report and forwarding such report to the
NYISO. The form shall be completed to indicate each new frequency or change.

Upon receiving a completed PLC Frequency Data Report, the NYISO shall send copies of
the report to the PLC Task Force Contacts.

1. Within 31 days of receipt of a new PLC Frequency Data Report, each PLC Task
Force contact shall advise the NYISO by written memorandum of the concurrence
or objection with the proposed PLC frequency or frequencies.
2. If there is a conflict, the involved parties shall attempt to work out the difficulty by
holding meetings, where necessary, to negotiate solutions to PLC frequency
coordination problems.
3. If the approved frequencies resulting from these discussions are different than those
originally submitted, the appropriate PLC Task Force contact shall resubmit a
revised PLC Frequency Data Report to the NYISO for redistribution to the PLC
Task Force Contacts.

When frequencies are found satisfactory by all PLC Task Force contacts, the NYISO shall
notify the Facility Equipment owner of this result.

The Facility Equipment owner PLC Task Force contact that originated the Frequency
Report shall send it to the current designated contact at the UTC. At this time the address is
as follows:

Version 1.0 10/29/2009
Kathleen Fitzpatrick
United Telecom Council
1901 Pennsylvania Ave NW #500
Washington, DC 20006
kathleen.fitzpatrick@utc.org
3.4.4.6 UTC Actions

Upon receiving the PLC Frequency Data Report, the UTC will report other potential
conflicts to the affected Facility Equipment owner PLC Task Force contacts.
If the transaction code was to add a proposed new frequency (P), UTC will report on
potential conflicts to the affected TP Contact only and not to other users of the low-
frequency radio spectrum.
If the transaction code was to add a frequency already in service, UTC will report the
potential conflict to all the PLC Task Force contacts and users of the low-frequency
radio spectrum.
3.4.5 Procedures for Retiring PLC Frequencies

When Facility Equipment owners decide to retire a PLC frequency from the UTC PLC
database, the same PLC Frequency Data Report is submitted to the NYISO. In this case the
applicable UTC Transaction Code is:
Code D, standing for “deletion of an existing PLC frequency.”
It is not necessary for the Facility Equipment owner’s PLC Task Force contact to respond
to the NYISO in the case of f retired requencies.
3.4.5.1 PLC Task Force Contact Action

Initiate the process by submitting a completed PLC Frequency Data Report to the NYISO.
This form shall be completed to indicate each frequency retired. A copy of this form shall
be sent to the UTC at the address above.
3.4.5.2 NYISO Action

Upon receiving a completed PLC Frequency Data Report, the NYISO shall send copies of
the report to the PLC Task Force contacts.
3.4.6 Annual Review of the PLC Frequencies Database

In addition to the coordination and database update procedures defined, an annual review is
required of the UTC database for accuracy.
3.4.6.1 UTC Action

Annually, UTC initiates the review of the PLC Frequencies Database by sending to each
PLC Task Force contact a copy of their respective UTC data for review.

Version 1.0 10/29/2009

1. Review and revise the UTC database and send it directly to the UTC.
2. Send copies of the PLC Database revisions to the NYISO.

Send copies of received PLC Frequencies Database updates to all of the other PLC Task
Force contacts.
3.5 Short-Circuit Fault Analysis Data

This section describes the procedure for maintaining the NYISO Short-Circuit
representation.
3.5.1 Introduction
The NYISO System and Resource Planning department Protection Coordinator shall
maintain a uniform short-circuit representation for fault analysis. The Equipment owners
shall periodically review and update their respective portions of the representation. It is
necessary for the NYISO to maintain a current short-circuit representation to ensure
availability of this data for any necessary analyses required in a system impact study in
accordance with the NYISO Transmission Expansion and Interconnection Manual
(http://www.nyiso.com/public/documents/manuals/planning.jsp?maxDisplay=20) and other
industry Standards. Voltage and dynamic stability studies for either system reliability or
operating security also need accurate fault analysis data.
The NYISO uses the ASPEN One-Liner program; however, new data or modifications to
existing data may be submitted in any of the standard data formats used by the industry
(e.g., PSS/e, CAPE, etc.).
3.5.2 Annual Review of Short-Circuit Representation

Annually, the NYISO System and Resource Planning department Protection Coordinator
initiates the review of the NYISO Short-Circuit Representation by sending to each Facility
Equipment owner’s SPAS representative a copy of their respective current data for review.
3.5.2.1 Facility Equipment Owner Action

Review and revise the short-circuit database as appropriate and return it to the person
defined by the NYISO System and Resource Planning department Protection Coordinator.
This will include changes to existing data or additions or deletions to the representation
based on system changes that have recently occurred or are planned for installation within
the next capability period.

The NYISO System and Resource Planning department Protection Coordinator shall update
the NYISO short-circuit representation as indicated.

Version 1.0 10/29/2009
The NYISO System and Resource Planning department Protection Coordinator shall make
the representation available to all Facility Equipment owners, other NYISO staff, or to such
contractors and consultants or regulatory agencies for purposes of conducting system
studies associated with transmission system reliability assessment.

Version 1.0 10/29/2009

Version 1.0 10/29/2009
4. A UTOMATIC U NDERFREQUENCY L OAD

S HEDDING R EPORTING AND C OMPLIANCE
The NYISO SPAS has been assigned the responsibility of collecting Under Frequency Load
Shedding (UFLS) data and monitoring compliance with NPCC Criteria document D-12, Section
5.2, “Automatic Underfrequency Load Shedding.” In addition to monitoring compliance with D-
2, the data is also used in supporting compliance with the NYSRC Rule F-R8, “Load Shedding
Allocation,” and for simulations involving action of UFLS. This section describes how the data
collection and compliance monitoring will be carried out.
4.1 Entities
NYISO (as Area Reliability Coordinator) – NYISO staff will initiate the request and
collect the data and compliance statements.
UFLS Entity – Generally, the New York Area UFLS Entities are the same as the New York
Area TOs; however, this term may also apply to a Transmission Operator, Distribution
Provider, and/or LSE that is required to own or operate a UFLS program.
4.2 Schedule
In order to support collection of the NPCC D-12 compliance data, NYISO staff will send an
inquiry by e-mail on or about April 1 of each year to the SPAS Participants and
representatives designated by the UFLS Entity for this purpose. This e-mail inquiry will
request data sufficient to perform analysis of compliance with the following table from D-
12:
Table 1 - UFLS Parameters for the Eastern interconnection Portion of the NPCC
Total Operating Time

Threshold Setting Block Size
(1) (2)
Stage 1 59.5 Hz 7 percent 300 ms

Stage 5 (anti-stall) 59.5 Hz 2 percent 10 s
Notes:
(1) Total operating time is the load-weighted average for all load to be shed within a Balancing Authority area,
with maximum deviation for any load limited to ±50 ms.
(2) Minimum UFLS relay operating time=100ms.
The e-mail inquiry will request data sufficient to perform analysis with the following
statement in D-12:

Version 1.0 10/29/2009
D-12, 5.4 “Generators shall not be tripped for under-frequency conditions in the
area above the curve in Figure 1, except as provided for in Sections 5.4.1 and
5.4.2.” (Figure 1 is included in D-12 following section 7.)
The e-mail inquiry will specify the UFLS Entity response time, which shall be at least 30
days.
In parallel with the activity described herein, the NYISO will also be collecting data
directly from GOs.
4.3 Computation of Load

The intent of D-12, section 5.2, is for an Area to stabilize the frequency during an
underfrequency condition, by automatically shedding approximately ten and fifteen percent
of its load at the time of the event.
The intent of D-12, section 5.4, is to preserve the stability of an island, if formed, by
providing compensatory load shedding for generators that do not conform to Figure 1, and
thus could interfere with the operation of the underfrequency load-shedding program.
For these purposes, the amounts of load shedding shall be reported coincident with the
individual UFLS Entity’s integrated hourly peak from the previous summer. That is, the
individual UFLS Entity shall total its UFLS circuit loads at the time of the Entity's previous
year’s integrated hourly summer peak, and report the amount of load that would have been
shed at each UFLS step, in both megawatts and as a percentage of the peak.
The load-shedding amounts reported for 5.2.1 must not include load shedding provided as
compensation for non-conforming generators, in 5.4. That is, the same loading shedding
may not be reported for purposes of both 5.2 and 5.4.
Additional background material in NPCC D-12 should be consulted before certifying
compliance.
The calculations shall be retained for a period of two years after making this report.
4.4 Format
A format for reporting compliance will be distributed with the e-mail inquiry. The
following information will be reported on this form:
Name of UFLS Entity
Date of report
Name of the individual making the report on behalf of the Entity
For Section 5.2.1 of D-12:
Previous year’s summer integrated hourly peak load
UFLS at each step, expressed as both megawatts and percentage of Entity’s peak,
including those steps provided that are beyond the NPCC-mandated steps
For Section 5.4 of D-12:
List of generators that do not conform with NPCC D-12.

Version 1.0 10/29/2009
For each such non-conforming generator, the generator megawatt rating, trip setting
in Hertz, and time delay in seconds.
Compensatory load shedding for each such non-conforming generator, with the
megawatts load shedding and trip setting in Hertz.
Non-conforming generators with a rating below 20 MW may be reported in groups
with other generators of the same settings.
Compensatory load shedding for generators that have been reported in groups may
also be grouped.
Overall Compliance:
A statement of compliance with NPCC D-12
4.5 Notifications
At the completion of the data collection, the NYISO will prepare an Area Compliance
Report. This report will be completed within 60 days of the initial data request, and copies
will be sent to the appropriate NPCC entity or group and the NYCA UFLS Entities. (This is
necessary as PRC-007 places the obligation on each UFLS entity to “ensure that its UFLS
program is consistent with its RRO TFLS program requirement.”)
4.6 References
NPCC D-12, “UFLS Program Requirements,” June 29, 2009, or most recent version,
available at:
http://www.npcc.org/documents/regStandards/Directories.aspx
“UFLS Implementation Plan,” June 29, 2009, available at:
http://www.npcc.org/documents/regStandards/Directories.aspx
NPCC B-7, “Automatic Underfrequency Load Shedding Program,” September 4
2008, or most recent version, available at
http://www.npcc.org/documents/regStandards/Guide.aspx
NERC Standard PRC-007-0, “Assuring Consistency with Regional UFLS Program
Requirements,” Requirement R1, available at:
http://www.nerc.com.
NYSRC Rule F-R8, “Load Shedding Allocation,” available at:
http://www.nysrc.org.

Version 1.0 10/29/2009

Version 1.0 10/29/2009
5. S YSTEM P ROTECTION M AINTENANCE

R EPORTING
The NYISO SPAS has been assigned to monitor compliance with NPCC directory D-3
“Maintenance Criteria for Bulk Power System Protection.” As part of this process, TOs and GOs
report their ability to comply with the NPCC D-3 requirements on a quarterly basis. This
document describes how this process is carried out by SPAS including functions of the reporting
of TOs and GO and of NYISO staff.
5.1 Scope
The NYISO SPAS has been assigned the responsibility of monitoring compliance with the
relay maintenance criteria set forth in NPCC directory D-3.
5.2 Compliance Reporting

Prior to January 1 of each year, NYISO staff will send an e-mail to the TOs and GOs
reminding them their annual compliance statement for January 1 is due by January 20. The
TOs and GOs shall respond to the Reliability Compliance Mailbox at
reliability_compliance@nyiso.com with a statement of full compliance or compliance with
exceptions as of January 1. Reports shall list the BPS elements that exist at each BPS
station. Exceptions are individual BPS elements with any system protection component
capable of tripping that element that has not been maintained in accordance with D-3 as of
the end of the 4th quarter. In the case of transmission line elements, each terminal shall be
reported as a separate item. Along with their statement, TOs and GOs shall provide a
revised test date for each exception.
5.3 Maintenance Reporting

Prior to April 1, July 1, and October 1 of each year, NYISO staff will send an e-mail to the
TOs and GOs reminding them their quarterly maintenance report is due on April 20, July
20, and October 20, respectively. The TOs and GOs shall respond to the Reliability
Compliance Mailbox at reliability_compliance@nyiso.com. On these dates, TOs and GOs
shall report on maintenance backlog items, which are BPS elements that have not been
maintained within the applicable time period described in D-3, as of the end of the previous
quarter. In the case of transmission line elements, each terminal shall be reported as a
separate item.
5.4 Report Review

A summary of these reports shall be reviewed at the SPAS meeting immediately following
the due date. Subsequent to the SPAS meeting, the SPAS Chair shall send a summary
report to the NYISO Operating Committee Chair.

Version 1.0 10/29/2009
5.5 Reference
NPCC Regional Reliability Reference Directory 3, “Maintenance Criteria for Bulk
Power System Protection,” July 11, 2008

Version 1.0 10/29/2009
A.
Appendix A. Guide for the Selection of Power Line Carrier

Frequencies
A.
A.1. Introduction
This appendix establishes minimum guidelines to provide a uniform method of selecting
power line carrier (PLC) frequencies within the New York Control Area (NYCA).
Procedures used by the Transmission owners to notify necessary parties of PLC frequency
changes and additions and to keep the Utilities Telecommunications Council (UTC) PLC
database current can be found in the section 3.4.4 of this manual.
PLC spectrum conservation has been a major concern within the power utility business for
many years. These guidelines have been developed to conserve spectrum while staying
within industry-established frequency separation limits to minimize interference between
channels.
It is assumed that the user of this manual is familiar with the application of power line
carrier systems.
A periodic review of these guidelines may be necessary, however, as dictated by changes in
equipment technology.
A.2. PLC Modulation Techniques

Three types of modulation techniques that utilize the PLC frequency spectrum of 10 to 490
kHz are in general use, namely Amplitude Modulated Keyed Systems, Frequent Shift
Keyed Systems, and Single Side Band Systems, described in further detail in the following
three subsections.
A.2.1. Amplitude Modulated Keyed Systems

On-Off amplitude modulated (AM) keyed PLC systems are usually used for blocking relay
schemes. This type of system may also serve a second function of transmitting voice over
the power lines via AM. The PLC frequency is usually off (no PLC signal transmitted).
A.2.2. Frequent Shift Keyed Systems

Frequency shift keyed (FSK) power line carrier systems are used for unblocking and
transfer-tripping relay schemes. This type of PLC system always transmits at least one
signal, sometimes at reduced levels to avoid possible interference. During tripping
operations, full transmitter power (exalted signal level) is used. FSK – PLC systems are
generally preferred over AM – PLC systems, as they allow the system to be continuously
monitored.
NYISO Operations Engineering Staff A-1

Version 1.0 10/29/2009
A.2.3. Single Side Band Systems

Single side band (SSB) suppressed AM carrier is used for multi-function PLC
communications. SSB systems are typically four-channel systems (4-kHz Bandwidth
channels). This is done by the “upshifting” of audio tone and/or baseband frequencies to
line frequencies. The channels can be used for various functions including relaying (audio
tone and/or baseband), voice, telemetry, and SCADA communications.
When considering frequency separation guidelines, the requirements of both the SSB –
PLC system as well as the specific needs of the communications systems utilizing SSB –
PLC should be considered.
A.3. General PLC Application Criteria
A.3.1. Trapping and Coupling

If a single frequency is to be used, a single-frequency high Q trap is recommended,
as wideband traps do not provide as much isolation.
When using a two-frequency line trap, maintain a minimum frequency separation of
25 kHz or 25% of the higher frequency, whichever is greater.
If two or more closely spaced frequencies are employed, locate the entire group on
the upper (higher-frequency) trap skirt of a single-frequency trap if a high Q trap is
used. As an alternate, use a low Q single frequency trap (Q ≈ 10) or a wideband trap
of 1,000 ohms, minimum.
In general, use the center phase for single-phase coupling when there are no
transpositions and modal analysis permits.
When trapping a relatively long line, the use of three traps is recommended at the tap
point if the trapped line is ¼ wavelength of the operating frequency or if the tap is a
transformer bank resulting in high PLC attenuation.
Line traps in all three phases may be treated as the equivalent of one line section of
PLC separation within the operating frequency range of the traps.
Use of multiple series and parallel L/C tuner combinations (via line tuning units or
high power filters) is recommended to provide isolation between widely separated
transmitter/receiver groups and also to reduce bandwidth of outgoing and incoming
RF energy.
Use reactive/skewed hybrids to isolate closely spaced transmitter/receiver
combinations. Use resistive hybrids to isolate two closely spaced transmitters.
A.3.2. Factors Affecting Frequency Selection

A tap point of a line should not be considered as a bus when determining the number
of line sections.
An auto-transformer may be treated as the equivalent of one line section.
Avoid second harmonic frequencies on the same bus and for at least two line
sections.
A-2 NYISO Operations Engineering Staff

Version 1.0 10/29/2009
Use lower frequencies on longer lines and higher frequencies on shorter lines. A
“short line” is one with an attenuation (line and coupling losses) less than 10 dB or a
physical length of approximately 20 miles or less. A “long line” is one with an
attenuation more than 10 dB or a physical length in excess of 20 miles. Use the
highest frequency possible while maintaining adequate operating margins to save the
lower frequency spectrum for use on long lines.
Avoid PLC frequencies that correspond to low multiples of λ /2 or λ /4 (half or
quarter wavelength of PLC frequencies, respectively) on short overhead lines.
Use frequencies that correspond to an odd multiple of λ /8 on overhead lines with
low attenuation.
Use narrow band equipment where speed is not a constraint.
Use power below 10 W where possible (i.e., 1-W guard, 10-W trip) to minimize
interference taking into account “bad” weather requirements (i.e., increasing noise
and attenuation) of the PLC system.
Unless otherwise noted, parallel lines not terminating on the same bus will be treated
as though they were, for PLC frequency selection purposes.
When PLC frequencies are to be applied to power cables, great care should be taken
to minimize PLC losses due to the low characteristic impedance of the cable, series
impedance mismatch at the coupling point, and standing wave reflections. This can
often be done by using lower PLC frequencies, using PLC frequencies at λ /2 or
multiples thereof, and by using extra-hi C coupling capacitors.
Although this guide identifies guidelines for PLC frequency selection, the following
additional points require consideration to ensure proper PLC system operations:
¾ Receiver Sensitivity
¾ Signal-to-Noise Ratio Requirements
¾ Receiver Selectivity
¾ Operating Margin, Including Transposition and Other Modal Loses
¾ Bad Weather Conditions
¾ Coordination with Adjacent Utilities
¾ Use of Voice Channels
¾ Line Tuners and Other Auxiliary Coupling Equipment Losses
A.4. Frequency Spacing by Equipment Type
A.4.1. On-Off (AM) Blocking Carrier

1. In general, minimum frequency separations for all lines terminating at the same bus
in the Table A.1, below:

Version 1.0 10/29/2009
Table A.1 ON – OFF Carrier Frequency Spacing
Solid State
Tube Type Crystal Synthesized
Controlled Wide Band Narrow Band
Without Voice 10 Hz 4 kHz 4 Hz 2 kHz

Channel
With Voice Channel 6 kHz 4 Hz 4 kHz
The equipment manufacturers' instruction books should be consulted for more

detailed information.
2. Repeat frequency no sooner than two buses away.
3. When ON-OFF and frequency-shift equipment is applied on the same bus, the
greater minimum separation shall prevail.
A.4.2. Frequency Shift (FSK)

1. In general, minimum frequency separations for non-voice applications are indicated
in the Table A.2, below:
Table A.2 FSK Carrier Frequency Spacing
Extra Wide Band Wide Band Narrow Band
Typical Band-Width 1000 Hz 500 Hz 200 Hz
One-Way Channel 2000 Hz 1000 Hz 500 Hz

Spacing
Two-Way Channel 4000 Hz 2000 Hz 1000 Hz
Spacing
The equipment manufacturers' instruction books should be consulted for more

detailed information.
Frequency separations apply between:
a. All lines terminating on the same bus and one bus away;
b. Transmitters and receivers located on lines parallel to the subject line; and
c. Transmitters and receivers one bus away from lines parallel to the subject line.
2. Repeated frequency no sooner than two buses away. A received signal should be at
least 40 dB above an interfering signal of the same frequency.
A.4.3. Single Sideband

1. General (SSB) Frequency Selection Guidelines

Version 1.0 10/29/2009
a. Transmitters connected to different lines on the same bus, using adjacent

frequency bands and transmitting signals of equal power, should have 15 dB of
isolation between them to minimize inter-modulation products. If the
transmitters have different output power then 15 dB plus the difference in power
should be used as the isolation guideline.
b. Receivers connected to different lines on the same bus, using adjacent frequency
bands, and receiving signals of equal power should have at least 3 dB of
isolation between them. If receiver levels are different, 3 dB plus the difference
in power should be used as the isolation guideline [Adjacent SSB (receivers)
channels typically have an inherent 50 dB of isolation due to the SSB
modulation / demodulation process.]
c. Transceiver systems using the same frequency band should have 50 dB of
isolation between a transmitter of one system and the receiver of the second
system. Typically, a line section and two buses will offer this degree of
isolation.
d. Transceiver systems on different lines on the same bus and using adjacent
frequencies should have 25 dB of isolation between the transmitter of one
system and the receiver of the second system. In addition, the transmitted
level(s) should be 3 dB below the intended receive levels at the input to the local
receiver.
e. A 4-kHz “guard band” between transmitter and/or receiver frequency bands
offers approximately 10 dB of isolation.
f. If two SSB – PLC systems are to be placed on the same line(s), they should be
interconnected with high-pass/low-pass filter networks with the crossover
occurring at approximately 30 dB below the transmitter signal levels.
g. In general, it is assumed that there is 10 – 15 dB of isolation across a bus.
h. Traps with a minimum impedance of 1,000 ohms should be used whenever
possible as a frequency conservation measure.
2. SSB – PLC Frequency Selection Guidelines for Various Typical Functions are
covered in Table A.3, following. These functions include:
a. Baseband Relaying
• Directional Comparison Blocking and Unblocking – AM and FSK
• Phase Comparison – AM and FSK
• Transfer Trip – FSK
b. Audio Tone Functions
• Relaying
• SCADA
• Voice
• Telemetry

Version 1.0 10/29/2009
Table A.3 Single-Sideband Equipment Operating Parameters
Signal to Nominal Nominal

Channel Operating Max. Rec.
Equipment Type Noise Ratio Spacing Bandwidth
Speed Margin Sens.
Required (See Note) Freq. Shift
On/Off
3 ms 15-20 dB 15 dB
(Baseband)
25-30 ms 0 dB 25 dB 500 Hz 200 Hz 5 mV
FSK Transmitter Trip 7 ms 5 dB 25 dB 1500 Hz 500 Hz 15 mV
(Baseband)
4 ms 7 dB 25 dB 3000 Hz 1000 Hz 15 mV
6 ms 5 dB 10 dB 1000 Hz 480 Hz
FSK Transmitter Trip
9 ms 0 dB 10 dB 340 Hz 170 Hz
(Audio Tones) 16 ms -3 dB 10 dB 170 Hz 85 Hz
Tones for Data 15 ms
Voice w/o Comp. 30 ms
Voice w/ Comp. 15 ms
SSB 4.5 dBm
Note: Function of Rec. Bandwidth (Typically 55 dB)
A.5. References
Dowty RFL Industries, Communications Division. The PLC Handbook (PLC-79-1).
Boonton, NJ: Dowty RFL Industries, Inc., 1979.
General Electric Company, Power Systems Management Business Dept. PLC
Applications Guide – Protective Relaying Channels (GET-6920). Malvern, PA:
General Electric Company, 1985.
General Electric Company, Technology Center. Application Guide Relaying
Communications Channels (GET-8034). Malvern, PA: General Electric Company,
1993
IEEE: Power Systems Communications Committee. IEEE Guide for Power-Line
Carrier Applications (ANSI/IEEE Std 643-2004). New York: IEEE, 2005.
Ray, Roger E. “Channel Considerations for Power Line Carrier (RPL 83-3).” Coral
Springs, FL: Westinghouse Electric Corporation, 1983.
IEEE: PSRC H9, “Special Considerations in Applying Power Line Carrier for
Protective Relaying,” available at:
www.pes-psrc.org/

Version 1.0 10/29/2009
B.
Appendix B. Protection System Performance (PSP) Reporting

Instructions
Protection System Performance (PSP) Working Group, November 1994

DRAFT – Edited and Reformatted by JWI, April 28, 2008
Changes made and “Notes” added to Page 11, JWI, July 9, 2008
Updated items in introduction and in “Notes” on page 11, JWI, October 21, 2008
B.
B.1. Introduction
The System Protection Advisory Subcommittee (SPAS) has been collecting protection
system performance data for the Bulk Power System (BPS) for many years. In late 1988,
the Protection System Performance (PSP) Working Group was established to evaluate this
data and to evaluated the established procedure. This report format and procedure is the
result of the efforts of the working group to improve the reporting process.
B.2. Discussion
The protection system has been categorized into three areas to better define the reporting
procedure. A protection group consists of individual relays and communication packages
and their associated instrument transformers, d.c., and trip coil equipments. The protection
system is composed of a combination of protection groups, i.e., the primary and secondary
protection groups. The entire system, from the instrument transformer to the breakers, will
be referenced as a protection system. For the purpose of the PSP reporting system, a two
terminal transmission line has two protection systems, one at each end. Protection System
Performance reporting is on a per-terminal basis. Each terminal, should be reported
separately. For example, a two-terminal transmission line fault that is cleared correctly
normally will be counted as two “correct” protection system operations. Redundant
protection groups are considered to be one protection system; if any or all of the protection
groups operate correctly to clear a fault, the PSP will be recorded as one “correct”
operation.
If there is a known misoperation of a protection group that did not compromise the
performance of the protection system as a whole, then the misoperation should result in an
incorrect code.
Protection System Performance data records are necessary only for automatic operations
involving BPS facilities. A separate PSP record should be completed for each event. An
event is defined as any set of conditions, resulting in the unscheduled operation of the
protection system. Operations that occur during commissioning, before the protection
system is turned over to System Operations, should not be reported. A single PSP record
should be used to record from the initiating condition to the auto reclosing. Subsequent
relay operations should receive individual PSP records. Operations resulting from manual
NYISO Operations Engineering Staff B-1

Version 1.0 10/29/2009
or supervisory close will be considered a separate event, whether the manual or supervisory
close occurs during or after the auto reclose cycle. Additional comments describing the
event should be listed at the bottom of each report. It is important that all reports that
contain incorrect operations have sufficient comments to facilitate analysis and assessment
of preventative strategies.
A single event could cascade into additional events, such as a transformer failure due to a
through fault or a breaker failure. A new PSP report should be filed for each additional
event. A breaker failure is the failure of a breaker to open correctly. For this condition, the
PSP should be coded as incorrect because the intended breaker failed to clear the fault
(Code IBR in section B.4). The first event cascades into a second event, which is entered on
an additional report with an initiating condition entered an equipment failure. If a line
terminal trips, automatically recloses, and trips again, count two operations, but consider
the sequence to be all part of the same event.
In tabulating the year's operations, it was decided to categorize the Disturbance- and Non-
Disturbance–Initiated events separately. For this purpose, a disturbance is defined as an
unplanned event that causes an abnormal system condition or any perturbation to the
electric system.
B.3. General Instructions

Each member system will report on operations of their own relays/circuit breakers. It is the
responsibility of each member to coordinate multiple PSP reports that have a common
initiating event. Operations at a “foreign terminal” are not to be reported. For this purpose,
a foreign terminal is defined to be the tie line terminal outside New York.
Each member should evaluate their own operations that are coded “incorrect” to determine
the underlying cause of the error. The cause of personnel-initiated operations should be
reviewed closely by the individual members. Operations that result from an incorrect
application, setting, or equipment failure should not be credited to field personnel. If a
condition exists that causes an operation when correct work practices are being followed,
then the operation should be coded “incorrect” due to the ultimate cause of the event. If the
work practice or procedure is incorrect, then the error should be charged to whatever group
is responsible for establishing the procedure. If a technician causes a misoperation as a
result of not following proper work practices, it should be coded as a personnel error.
Personnel: Personnel-initiated events are generally to be coded N (non-disturbance), except
in the case of an error that actually results in a power system disturbance. A primary circuit
switching error that causes a disturbance may still result in the correct operation of the
protection system. An operation initiated by errors made by personnel while working on a
protection system would be coded “incorrect.” Personnel listings in section B.4 refer to the
functions being performed at the time of the misoperation. These listings are not necessarily
job titles.
Controls: Operations originating with power plant, static VAr compensator, and HVdc
control systems will not be reported. This includes reverse power sequential tripping
schemes. Also, operations initiated by the loss of oil pressure in a cable or a water pump
within a cooling system will not require a PSP report. Reclosing information has been
B-2 NYISO Operations Engineering Staff

Version 1.0 10/29/2009
included on the PSP report strictly for the purpose of gathering data on automatic
restoration. Although it is normally considered part of the protection system, the reclosing
relay is not necessary for clearing faults. Failure of a reclosing relay to operate shall not be
considered an incorrect operation for the purposes of filling out a PSP report. Also, breaker
trips caused by low gas or low air-pressure controls will not be reported. Breaker pole
disagreements that initiate breaker failure protection system tripping of adjacent/remote
breakers should be reported.
An entry of “U.I. ” (Under Investigation) in section B.4 indicates an event that is
unresolved. This event will not be counted until a finalized record has been submitted.
Pilot: If a line fault is cleared by a time-delayed backup relay, and this line has pilot
protection, it should be considered that the pilot group failed to operate correctly and the
protection system failed to operate in its design time. Thus, the protection system operation
should be coded “incorrect” at the slow-tripping terminal. Likewise a pilot group overtrip
will also be recorded as a single protection system “incorrect” at the tripping terminal.
These “incorrects” will be coded “ICO, ” for Incorrect Communications.
Direct Transfer Trip: If, during routine testing, an erroneous direct transfer trip signal is
sent and trips a breaker(s) at a remote station, the PSP procedure will be initiated by the
receiving end utility in conjunction with the sending end utility. Two reports will result:
The receiving end utility reports a correct protection system operation at its terminal, and
the sending end utility reports the personnel incorrect at its terminal. A transmission line
terminal that trips or fails to trip due to direct transfer trip channel noise (no fault detection
devices participating at the receiving terminal, no sending terminal participation) is to be
coded as incorrect "I-CO," at the receiving terminal.
B.4. Coding Instructions
B.4.1. Participant
CE – Consolidated Edison Company of New York, Inc.
CH – Central Hudson Gas and Electric Corporation
LI – Long Island Power Authority
NG – National Grid
NY – New York State Electric and Gas Corporation
OR – Orange and Rockland Utilities, Inc.
PA – New York Power Authority
RG – Rochester Gas and Electric Corporation
B.4.2. File Number

Each participant will use consecutive numbers beginning with |_._.1|.

Version 1.0 10/29/2009
B.4.3. Date/Time
Date |M.M| |D.D| |Y.Y|
Time |H.H| |M.M|
Time should be stated in twenty-four hour format local time, i.e., EDT or EST, whichever is
in effect.
(Seconds and milliseconds will be added in the future.)
B.4.4. Event
B.4.4.1. Initiating Condition
The root cause regardless of whether the operation being described involves a power
system fault. The prefix on the field designates whether it was a power system disturbance
(D) or not (N). A full listing of the required inputs for this field can be found in the Event
Table, on page B-7.
B.4.4.2. Resulting Condition

This condition can include a specific fault or power swing. The prefix on the field
designates whether it was transient (T) or permanent (P). A full listing of the required
inputs for this field can be found in the Event Table, on page B-7.
B.4.4.3. Element/Location
The element at or on which the initiating event occurred. A full listing of the required
inputs for this field can be found in the Event Table, on page B-7. The
identification/location of this element can be included in the comments.
B.4.4.4. Circuit/Equipment
Affected BPS element or failed breaker.
B.4.4.5. Auto Restore

Auto Restore records whether the affected circuit/equipment on both ends, if appropriate,
was successfully restored to service without an operator taking action. (Y/N)
B.4.4.6. Auto Reclose

Auto Reclose indicates whether an auto reclose was attempted. This item with the previous
item will confirm the success of the auto-reclose attempt. (Y/N)
B.4.4.7. High-Side Voltage

Voltage level of circuit/equipment above. For a transformer use high-side voltage.
B.4.4.8. Station
Location of the protection system listed in the following item.

Version 1.0 10/29/2009
B.4.4.9. Protection System I.D.

Identification of the BPS Protection System that operated for the given event. This is not
used for statistical purposes but is mainly for the NYPP member to describe what operated.
Enter the breaker or breakers that operated or some other description that, to you, most
closely identifies what operated.
B.4.4.10. Protection System Operations

This is a three-part entry:
No (abbreviation for number) Count one (1) in this column for each protection system
operation at each line terminal. The entry should always be one (1) or greater.
Code as follows:
|C._._| Correct
|I.A.P| Incorrect – APplication
|I.S.S| Incorrect – Setting Specification
|I.S.A| Incorrect – Setting Applied
|I.E.N| Incorrect –- ENvironment at protection system
|I.C.T| Incorrect – Current Transformer
|I.V.T| Incorrect – Voltage Transformer, including fuses
|I.C.W| Incorrect – Cable and Wiring
|I.B.A| Incorrect – BAttery/Charger/DC fuses
|I.R.#| Incorrect – Relay
The incorrect relay entries to replace the #’s are listed in Table B.3. Incorrect includes
failure of protection system to operate in design time.
|I.C.O| Incorrect – COmmunication (Complete Line Package and/or DTT
Package)
|I.N.L| Incorrect – Not Listed
|I.U.N| Incorrect – UNknown
|I.B.R| Incorrect – BReaker
|I.U.I| Incorrect – Under Investigation
|I.T.P| Incorrect – Test: Plan, hardware, software
|I.P.#| Incorrect – Personnel
The incorrect personnel entries to replace the #’s are listed in the Incorrect-Personnel Table
which follows.

Version 1.0 10/29/2009
B.4.5. Pilot System Packages

This section is to be used to evaluate the pilot systems associated with Bulk Power
protection schemes only when there is an incorrect protection system operation due to
communications. Use a separate line to report each communications package operation.
B.4.5.1. Line Package
This is used to evaluate “line pilot” schemes, i.e., whether communication signals were sent
and/or received.
This is a three-part entry, consisting of:
|I._._._| Incorrect (There is no reporting for corrects. Incorrect includes failure to
operate.)
Communications Medium
|_.C._._| power line Carrier
|_.T._._| Telephone type circuit
|_.M._._| Microwave
|_.F._._| Fiber optic
Pilot Protective System
|_._.B.C| Blocking Carrier
|_._.P.C| Phase Comparison
|_._.U.B| UnBlocking
|_._.D.U| Direct Underreaching
|_._.P.U| Permissive Underreaching
|_._.P.O| Permissive Overreaching
|_._.P.W| Pilot Wire (Current Differential)
B.4.5.2. DTT Package

This is used to evaluate “direct transfer trip” schemes, such as transformer, bus, breaker
failure protection, or SPSs.
This is a two-part entry, the same as the first two parts of the Line entry:
|I._| Incorrect (There is no reporting for corrects. Incorrect includes failure to operate.)
Communications Medium
|_.C| power line Carrier
|_.T| Telephone type circuit
|_.M| Microwave
|_.F| Fiber optic

Version 1.0 10/29/2009
B.4.6. Comments
Comments should be entered to describe the event.
B.4.7. Submitted By
Person responsible for submitting the record and the date completed.
Table B.1 Event Table
EVENT TABLE
INITIATING CONDITION RESULTING CONDITION ELEMENT
(D) DISTURBANCE (T) TRANSIENT

(N) NON-DISTURBANCE (P) PERMANENT
ANIMALS 3 PHASE BREAKER
COMMUNICATIONS DOUBLE PH-GND BUS
CONST. EQUIPMENT NO-FAULT CABLE
CONTROLS OPEN PHASE CAPACITOR
EQUIPMENT FAILURE PHASE TO GND CONDUCTOR
EXTERNAL EVENT PHASE TO PHASE CONVERTER VALVES

(REMOTE)
FIRE POWER SWING CT
LIGHTNING UNKNOWN FUSE
OTHER GENERATOR
PERSONNEL OVER EXCITATION INSULATOR
PROCEDURE NONE
RELAY PHASE-SHIFTER
SWITCHING POTHEAD
TREE PT
UNKNOWN REACTOR
VEHICLE STRUCTURE
VIBRATION SURGE ARRESTOR
WEATHER SWITCH
TRANSFORMER
UNKNOWN
Note: Add initiating condition “tower construction.”

Version 1.0 10/29/2009
Table B.2 Incorrect Personnel Table
INCORRECT-PERSONNEL TABLE
P1 WIRING INVOLVED IN WIRING IN OR AROUND THE

SUBSTATION
P2 RELAY CALIBRATION INVOLVED WITH RELAY CALIBRATION See NOTE
P3 RELAY TRIP TESTING PERFORMING TRIP TEST See NOTE
P4 CONSTRUCTION UTILITY WORKER
P5 CONSTRUCTION NON-UTILITY WORKER
P6 COMMUNICATIONS UTILITY WORKER
P7 COMMUNICATIONS NON-UTILITY WORKER
P8 OPERATING/SWITCHING INVOLVED WITH SWITCHING PROCEDURES
P9 OTHER OR UNKNOWN
Note: Codes IP2 and IP3 are not misoperations as defined by NPCC and NERC. The NPCC definition is contained in
document B-21, revised 09/04/2008, and the current NERC definition is contained in the NERC “Glossary of Terms
Used in Reliability Documents,” dated February 12, 2008. The NERC definition is under revision.
Note: Add P Code for Commissioning Testing In-Service Checks.

Version 1.0 10/29/2009
Table B.3 Incorrect Relay Table
INCORRECT-RELAY TABLE
IR1 MISSING PART
IR2 VENDOR DOCUMENTATION
IR9 OTHER
IRA ELECTROMECHANICAL RELAY ALIGNMENT DRIFT (ALIGNMENT IS OTHER THAN SETTING)
IRB ELECTROMECHANICAL RELAY COMPONENT FAILURE NOT COVERED BY SERVICE LETTER
IRC ELECTROMECHANICAL RELAY COMPONENT FAILURE COVERED BY SERVICE LETTER
IRD ELECTROMECHANICAL RELAY CALIBRATION DRIFT
IRF ELECTROMECHANICAL RELAY INTERNAL CONNECTION

IRG ELECTROMECHANICAL RELAY CONTAMINATION
IRH ELECTROMECHANICAL RELAY UNKNOWN
IRJ SOLID STATE RELAY COMPONENT FAILURE NOT COVERED BY SERVICE LETTER
IRK SOLID STATE RELAY COMPONENT FAILURE COVERED BY SERVICE LETTER
IRL SOLID STATE RELAY CALIBRATION DRIFT

IRM SOLID STATE RELAY INTERNAL CONNECTION
IRN SOLID STATE RELAY CONTAMINATION

IRO SOLID STATE RELAY UNKNOWN
IRQ MICROPROCESSOR RELAY COMPONENT FAILURE NOT COVERED BY SERVICE LETTER
IRR MICROPROCESSOR RELAY COMPONENT COVERED BY SERVICE LETTER
IRS MICROPROCESSOR RELAY CALIBRATION DRIFT
IRT MICROPROCESSOR RELAY INTERNAL CONNECTION
IRU MICROPROCESSOR RELAY CONTAMINATION
IRV MICROPROCESSOR RELAY SOFTWARE PROBLEM DUE TO CODING/ALGORITHM ERROR
IRW MICROPROCESSOR RELAY SOFTWARE PROBLEM DUE TO FIRMWARE OR SOFTWARE

COMPATIBILITY PROBLEM
IRX MICROPROCESSOR RELAY UNKNOWN
Note: Add IR Code for CCVT Transient.

Version 1.0 10/29/2009

Version 1.0 10/29/2009
C.
Appendix C. Forms
Relay Characteristics Form

Clearing Times Form
Reclosing Data Form
C.
NYISO Operations Engineering Staff C-1

Version 1.0 10/29/2009
C.1. Relay Characteristics Form
Line No.
Line Name
Terminal
Base Voltage
Submitted by Date
Protection System 1 Protection System 2
Type of Relay Scheme
CT Ratio
PT Ratio
Which Zone initiates Pilot Scheme?

Zone 1
Angle of Max Torque
(Enter 0 for reactance relay)
Setting in Secondary Ohms
Offset in Secondary Ohms

Setting in Primary per unit
(100 MVA base)

Zone 2
Angle of Max Torque


(100 MVA base)
C-2 NYISO Operations Engineering Staff

Version 1.0 10/29/2009

Zone 3
Angle of Max Torque

(100 MVA base)
Please attach RX plot with notations, or any other information necessary to describe protection systems for modeling.
Number of pages attached

Version 1.0 10/29/2009
C.2. Clearing Times Form
Line No.
Line Name
Terminal
Base Voltage
Submitted by Date
Clearing Times Viewed from the Terminal
Near End Fault (in cycles)
Far End Fault (in cycles)

Version 1.0 10/29/2009
C.3. Reclosing Data Form
Line No.
Line Name
Terminal
Base Voltage
Submitted by Date
IF YES, BREAKER
NO YES RECLOSING TIME*
HIGH SPEED RECLOSING*
DELAYED RECLOSING*
FIRST SHOT – Hot bus dead line
If there is no hot bus dead line reclosing at this end, i.e.,
reclosing is by sync check only, or not at all, choose NO.
SECOND SHOT – Hot bus dead line

If there is no second shot, choose NO.
THIRD SHOT – Hot bus dead line

If there is no third shot, choose NO.
* Definitions of terms are in the NPCC Bulk Power System Reclosing Guide, Document B-1, dated 03/11/2009.

Version 1.0 10/29/2009

Version 1.0 10/29/2009

System Protection Manual

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

System Protection Manual

Caricato da

Copyright:

Formati disponibili

MANUAL 33

System Protection Manual

This document was prepared by:

New York Independent System Operator

NYISO Operations Engineering Staff iii

3.4.3 UTC PLC Frequencies Database Reports .................................................................3-5

iv NYISO Operations Engineering Staff

A.5. References ............................................................................................................................... A-6

NYISO Operations Engineering Staff v

Table A.1 ON – OFF Carrier Frequency Spacing ....................................................................... A-4

vi NYISO Operations Engineering Staff

Version Date Revisions

1.0 10/29/2009 Initial Release

NYISO Operations Engineering Staff vii

This page intentionally blank.

viii NYISO Operations Engineering Staff

1. R EPORTING T RANSMISSION AND

1.2 Data Collection and Reporting

1.2.1 Transmission Owner Collection Schedule

1.2.2 Generation Owner Collection Schedule

1.3 Transmission of Data and Discussion of Results

NYISO Operations Engineering Staff 1-1

1.3.1 Transmission Owners

1.3.2 Generation Owners

1.4 Information Collected and Data Format

1.4.1 Transmission Owners

1-2 NYISO Operations Engineering Staff

 Name of Individual Making Report

1.4.2 Generation Owners

1.5 Data Collection

1.5.1 Transmission Owners

1.5.2 Generation Owners

1.6 Follow-Up Actions

NYISO Operations Engineering Staff 1-3

1.8 Information Requested by NPCC

1-4 NYISO Operations Engineering Staff

2.2 Specification and Settings of DME

2.3 Time Zone

NYISO Operations Engineering Staff 2-1

2.4 Survey of DME Equipment

2.5 Sharing of DME Data

2-2 NYISO Operations Engineering Staff

This page intentionally blank.

NYISO Operations Engineering Staff 2-3

3. S YSTEM P ROTECTION D ATA

3.1 Relay Characteristics

3.2 Pilot Protection Systems

NYISO Operations Engineering Staff 3-1

3.3 Clearing and Reclosing Times

3.3.1 Clearing Times

3.3.2 Reclosing Times

3-2 NYISO Operations Engineering Staff

3.3.3 Special Protection Systems

3.3.4 Special Protection Systems

3.3.5 Other Remedial Action Systems

NYISO Operations Engineering Staff 3-3

3.3.6 SPS Data Submission and Updating Procedures

3.3.6.1 Facility Equipment Owner Actions

3.3.6.2 NYISO Actions

3-4 NYISO Operations Engineering Staff

3.4 Power Line Carrier Frequencies

3.4.2 UTC PLC Task Force Contacts

3.4.3 UTC PLC Frequencies Database Reports

Name of Individual Making Report