System Analysis Data Manual

Transcription

NEW YORK
INDEPENDENT
SYSTEM OPERATOR
MANUAL 24
System Analysis Data
Manual
September 1999
new
l
york
l
independent
l
system
l
operator
This document was prepared by:
The New York Power Pool/
New York Independent System Operator
3890 Carman Rd
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 New York Power Pool/New York Independent System Operator
System Analysis Data Manual
Table of Contents
1. OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 PURPOSE AND SCOPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 NYISO DATA CLASSIFICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3 CONFIDENTIALITY OF DATA[PCP 5-0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3.1Disclosure of Confidential Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Class 1- Confidential Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Class 2- Non-Confidential Data: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.4 NYISO DATA BANK PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.4.1NYISO Data Bank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.4.2NYISO Data Bank Update Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
NYISO Actions: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
NYCA Facility Owners Actions: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.5 NPCC POWER FLOW BASE CASE DEVELOPMENT . . . . . . . . . . . . . . . . . . . . . . 11
NYISO Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Market Participants Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
NYISO Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
NPCC Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
NYISO Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
NPCC Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.6 FERC FORM 715: ANNUAL TRANSMISSION PLANNING AND EVALUATION
REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
NYISO Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Transmission Planning Advisory Subcommittee Actions . . . . . . . . . . . . . . . . . 15
NYISO Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2. PERFORMANCE DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 GENERATOR AVAILABILITY AND PERFORMANCE DATA [MP 13-3] . . . . . . .
2.1.1Generating Units To Be Reported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 GENERATOR AVAILABILITY DATA [MP 13-3 Appendices B and D] . . . . . . . . . .
2.2.1Unit Identification Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.2Unit Event Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.3Outage Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Planned Outages (PO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maintenance Outages (MO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scheduled Outage Extension (SE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Startup Failure (SF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unplanned Outage - Immediate (U1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unplanned Outage - Delayed (U2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unplanned Outage - Postponed (U3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.4Derating Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Planned Derating (PD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unplanned Derating - Immediate (D1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unplanned Derating - Delayed (D2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
17
17
18
18
18
19
19
19
19
19
20
20
20
20
21
21
22
Unplanned Derating - Postponed (D3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unplanned Derating - Deferred (D4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.5Changes in Event Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changes in Event Type Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
End of Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 GENERATING UNITS PERFORMANCE DATA [MP 13-3 App. D] . . . . . . . . . . . .
2.3.1Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gross Maximum Capacity (GMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gross Dependable Capacity (GDC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gross Actual Generation (GAG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Net Maximum Capacity (NMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Net Dependable Capacity (NDC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Net Actual Generation (NAG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2Unit Starting Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Attempted Unit Starts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Actual Unit Starts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 AVAILABILITY AND PERFORMANCE DATA REPORTING PROCEDURE . . . . .
Generator Owner Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reporting Data for Special Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22
22
22
23
24
24
24
24
25
25
25
25
25
25
26
26
26
26
26
3. SYSTEM NETWORK REPRESENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 NETWORK MODEL DATA [NYPP Data Bank App. G] . . . . . . . . . . . . . . . . . . . . . .
3.2 FACILITY RATINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 LOAD DATA [NYPP Data Bank, App. G] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 DYNAMICS MODELING DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.1Generator Dynamics Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
............................................................
1.1.2Generator Controls Dynamics Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
............................................................
1.1.3Network Dynamics Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.4Load Dynamics Model Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27
27
27
28
28
29
30
30
30
30
30
4. SYSTEM PROTECTION DATA [MP31-3] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 RELAY CHARACTERISTICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 CLEARING AND RECLOSING TIMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1Clearing Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2 Reclosing Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
31
33
33
33
4.3 SPECIAL PROTECTION SYSTEMS (SPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1 Special Protection Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2 Other Remedial Action Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.3 SPS Data Submission And Updating Procedures . . . . . . . . . . . . . . . . . . . . . . . . .
Transmission Owners Actions: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NYISO Actions: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4
POWER LINE CARRIER FREQUENCIES [MP 37-2] . . . . . . . . . . . . . . . . . .
4.4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2 UTC PLC Frequencies Database Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.3 UTC PLC Frequency Coordination Procedures . . . . . . . . . . . . . . . . . . . . . . . .
PLC Task Force Contact Actions: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NYISO Actions: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
34
34
35
35
35
36
36
37
37
37
37
PLC Task Force Contacts Actions: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NYISO Actions: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UTC Actions: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Retiring PLC Frequencies Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PLC Task Force Contact Action: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NYISO Action: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Annual Review of the PLC Frequencies Database . . . . . . . . . . . . . . . . . . . . . . .
UTC Action: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PLC Task Force Contact Action: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NYISO Action: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FAULT ANALYSIS DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Annual Review of the Short Circuit Representation . . . . . . . . . . . . . . . . . . . . . .
Transmission Owner Action: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NYISO Action: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38
38
38
38
38
39
39
39
39
39
40
40
40
40
40
5. REAL-TIME REPRESENTATION DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2
REAL-TIME SYSTEM REPRESENTATION DATA . . . . . . . . . . . . . . . . . .
.5.2.1 System Network Representation Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.5.2.2 Facilities Ratings Update Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.5.2.3 Dynamic Rating Updates [MP 20-4] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3
SYSTEM REPRESENTATION [MP 22-4] . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.1 Operating System Representation Definitions . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.2 System Representation Review Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NYISO Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NYISO Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42
42
42
42
43
43
43
44
44
44
4.4.4
4.4.5
4.5
4.5.1
4.5.2
Attachment A
NYISO DATA CONFIDENTIALITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Attachment B
NYISO POWERFLOW DATA BANK FORMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Attachment C
NYISO DYNAMIC RATING FACILITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
COMBINATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
SERIES ELEMENTS BETWEEN THE TWO TERMINALS LISTED . . . . . . 68
Attachment D
PROTECTION DATA LISTS AND FORMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Attachment E
NYISO RTSA DATA BASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Revision History
9/24/1999
Changed all instances of Transmission Provider/Provider’s to Transmission Owners.
4 OVERVIEW
This section provides a general description of the purpose of this manual,
NYISO planning and operating studies data use, and guidelines on safeguarding
the confidential data used in these studies.
1.1 PURPOSE AND SCOPE
This manual describes data required by the NYISO to carry out technical
analysis to support its mission of preserving the reliability of the New York
State Bulk Power System.
Some of the data that requires collection by the NYISO is in response to
mandates by recognized regulatory entities.
This manual identifies the data users and defines how data is to be submitted to
the NYISO including schedules for data collection.
Three major groups use the data defined by this manual:
•
NYISO Staff
•
Suppliers of data, including:
%
%
%
%
•
Transmission Owners
Generation Owners
Load Serving Entities
Other NYISO market participants
Receivers of data:
%
Government Agencies:
•
New York Public Service Commission (PSC)
•
U.S. Department of Energy (DOE)
•
Federal Energy Regulatory Commission (FERC)
%
Reliability Councils:
•
North American Electric Reliability Council (NERC)
•
Northeast Power Coordination Council (NPCC)
•
New York State Reliability Council (NYSRC)
Actual and forecast data of all the components including load are required to
analyze, study, and plan the interconnected electric system. Detailed data of
system components must be maintained and updated by the facility owners and
load-serving entities and provided to NYISO accurately and as needed for
system analysis and distribution.
NYISO Manual for System Analysis Data (rev.: 9/24/99)
Section 1 - Overview
7
Complete, accurate, and timely data is needed by the NYISO to prepare system
analyses to assess reliability of the NY State bulk power system, to determine
the need for system enhancements or reinforcements to insure the future
reliability of the NY State bulk power system
•
System analyses include steady-state, transient, and dynamic simulations of the
electrical networks. Data requirements for these system analyses include
information on system components, system configuration, facility ratings,
customer demands, and electric power transactions. Sections 2, 3, 4, and 5
describe specific data supplied by the NYCA facilities owners and collected by
the NYISO for these purposes.
1.2 NYISO DATA CLASSIFICATION
The NYISO system analysis data described in this manual is divided into:
•
Data for reliability assessment:
% Power Flow Data
% Stability Data
% System Protection Data
•
Data for Real-time security monitoring:
% Real-time System Representation Data
% Ratings of Facilities
%
1.3 CONFIDENTIALITY OF DATA[PCP 5-0]
This section summarizes guidelines for the review, maintenance, distribution and
disclosure of NYISO data classified as confidential and proprietary by the
NYISO Market Participants. Detailed rules and procedures concerning the
confidentiality of data are covered in the NYISO Manual for Customer
Services and Administration.
1.3.1Disclosure of Confidential Data
In order to perform studies for the NYCA bulk power system, various databases
are developed for use in computer simulations by the NYISO. These computer
simulations include reliability, power flow and stability programs.
Each of these databases contain certain portions of data considered confidential
as detailed in Attachment A to this manual.
Distribution or disclosure of confidential data to any other party by any means
including verbal, graphic and/or electronic is strictly prohibited without the prior
approval of the Market Participant. All planning data handled by the NYISO is
categorized according to the following:
8
Confidential
Planning Data
Class 1- Confidential Data
Data categorized as Class 1 is available only to members of NYISO planning
staff in strict adherence to the NYISO Code of Conduct and the following
limitations:
•
Data is available only to those NYISO planning staff members as deemed
appropriate by the NYISO Planning Committee. Under critical
circumstances, the NYISO Executive Director and/or his assigns may
designate eligibility for additional individuals as deemed necessary.
•
A list of the individuals that have access to confidential data is kept by the
NYISO Executive Director and submitted to the NYISO Planning
Committee when changes occur.
•
Confidential data may be released to regulatory bodies as identified in
section 1.1, or to NYISO consultants or vendors with the express approval
of the NYISO Planning Committee following these conditions:
% Execution of an appropriate confidentiality agreement or
% Submission of a trade secret status request.
The NYISO Executive Director or designee is responsible for the proper
execution of these agreements on behalf of the NYISO.
Class 2- Non-Confidential Data:
Non-confidential
Planning Data
Data categorized as Class 2 is as follows:
•
Data submitted pursuant to NYS PSC 6-106 filing, or other such public
records as required by various regulatory agencies.
•
System network representation (power flow and dynamics data)
•
System Protection data
•
Real-time power system data which is made available on a comparable basis
to all NYISO Market Participants in accordance with FERC Orders 888,
889, etc.
Attachment A summarizes several categories of data which are required as input
for the development and analysis of system reliability studies. These databases
may be made available to outside parties upon payment of a reasonable fee
established by the NYISO.
1.4 NYISO DATA BANK PROCEDURES
This section describes the NYISO processes used to maintain the necessary
network representation data to comply with NPCC, FERC and other oversight
agencies requirements.
1.4.1NYISO Data Bank
Definition:
The NYISO Data Bank serves as the NYISO main database for the New York
9
NYISO Data Bank
Control Area (NYCA) system study data required in order to simulate thermal,
voltage, and dynamic responses to contingencies, and to determine interface
transfer limits. The NYISO Data Bank maintains data for a period of up to
twenty years, beginning with the current year.
The NYISO Data Bank gives NYISO the ability and flexibility to build power
flow and dynamics cases as required. This includes regularly scheduled studies,
reviews and reports including:
•
NYISO Seasonal Operating Studies
•
NERC MMWG Power Flow Base Case Development process
•
FERC Form 715: Annual Transmission Planning and Evaluation Report
•
NPCC Triennial Review of Reliability
The NYISO Data Bank also allows the NYISO to prepare power flow base
cases for studies conducted in accordance with the Reliability Assessment
requirements or Transmisison Expansion.
1.4.2NYISO Data Bank Update Procedure
Due to the large quantity of data to be reviewed, the NYISO has scheduled the
annual review of all NYISO Data Bank data at different times throughout the
calendar year. The following review and update schedule is used:
Exhibit 1.1:
NYISO Data Bank
Data Review
Schedule
Data to Review and Update
Update
Time Frame
AC Lines
Transformers
Transformer Impedance Correction Tables
Branch Status
January 1 to
March 31
All Shunts
April 1 to April
30
All Generators including Generator Reactive Capability Curves
May 1 to
July 31
Dynamics Data
All equipment In Service and Out of Service dates
August 1 to
September 30
Buses
Loads
October 1 to
November 30
For a more detailed description of these data, see the NYISO Data Bank
Reference Manual.
The NYISO and the NYCA facility owners use the following annual procedure
to keep the NYISO Data Bank data up to date. The NYCA facility owners
include:
•
10
Transmission Owners
•
•
Generator Owners
Load Serving Entities (LSE)
NYISO Actions:
1. Assemble and distribute to each Transmission Owner, Generator owner and
LSE, their corresponding Data Bank data using the review and update
schedule.
2. Collect Data Bank changes submitted by the Transmission Owners,
Generator owners and LSEs.
3. Update the master NYISO Data Bank with the submitted changes.
4. In addition to NYCA data, maintain appropriate system representations and
associated data for neighboring systems from the NPCC SS-37 and NERC
MMWG representation and their participants.
5. At the completion of the review and update process, NYISO also distributes
during the month of December, a completed and updated NYISO Data Bank
for internal use of all facility owners.
NYCA Facility Owners Actions:
1. Maintain their respective systems representations and the data described by
this manual.
2. Review their NYISO Data Bank data within the prescribed time frame.
3. Notify the NYISO, within the prescribed time frames, of pertinent changes
to their data.
1.5 NPCC POWER FLOW BASE CASE DEVELOPMENT
In addition to the annual NYISO Data Bank review by all facility owners, the
NYISO is also responsible for compiling NYCA information to develop the
NPCC SS-37 Working Group Base Cases. These NPCC power flow base cases
are used by all NPCC members to develop other transmission planning and
operating studies. The NPCC SS-37 Working Group has representation from all
interested parties including Transmission Owners. These representatives are
known as Transmission Owner Data Bank contacts.
The following procedure describes the annual process followed by NYISO, the
Market Participants, and NPCC to collect the NPCC required power flow base
cases data for the NYCA. The Market Participants that will participate include:
NYISO Actions
1. Prepare the Data Bank load flow data for review during the month of
February.
2. Send load flow data to the Market Participant data contacts by March 1st.
11
Market Participants Action
3. Provide changes to the load flow data to the NYISO by March 31.
NYISO Actions
4. Update the Data Bank and prepare the proposed NYISO load flow
representations for the NPCC cases during the month of April.
5. Send the proposed NYISO load flow representations to the Market
Participant’s Data Bank contacts by May 1st.
6. Prepare the Data Bank dynamics data for review during the month of May.
7. Provide comments on the NYISO load flow representations to the NYISO
by May 31st.
NYISO Actions
8. Send the dynamics data to the Market Participant’s Data Bank contacts by
June 1st.
9. Revise load flow representations for NPCC cases and update the Data Bank
during the month of June.
10. Send the NYISO load flow representations to NPCC by June 30th.
11. Provide changes to dynamics data to the NYISO by June 30th.
NYISO Actions
12. Update the Data Bank dynamics data during the month of July.
NPCC Actions
13. Provide the NPCC Trial 1 load flow cases to the SS-37 by August 1st.
NYISO Actions
14. Review and test the Trial 1 cases and integrate the dynamics data during the
month of August.
15. Send revised NYISO load flow representations and dynamics data to NPCC
by August 31st.
NPCC Actions
16. Provide the NPCC Trial 2 load flow cases to SS-37 by October 1st.
NYISO Action
12
17. Review and test Trial 2 load flow and dynamics cases during the month of
October.
18. Send final comments on cases and data to NPCC by October 31st.
NPCC Actions
19. Issue final NPCC load flow and dynamics cases by December 1st.
Exhibit 1-2 shows a time line for the process used to collect the required data for
NPCC base case development.
13
Exhibit 1.2: NYISO Data Bank & NPCC Base Cases Development Process Time Line
14
1.6 FERC FORM 715: ANNUAL TRANSMISSION
PLANNING AND EVALUATION REPORT
The FERC Form 715, Annual Transmission Planning and Evaluation Report, is
required pursuant to Sections 213(b), 307(a) and 311 of the Federal Power Act
to provide information adequate to inform potential transmission customers,
state regulatory authorities and the public of potential transmission capacity and
known constraints, to support the FERC expanded responsibilities under 211,
212 and 213(a) of the Federal Power Act (as amended by the Energy Policy
Act), and to assist in rate or other regulatory proceedings.
The NYISO, as designated agent of the Transmission Owners of New York
State, is responsible for preparing the FERC Form 715- Part 2 report every year
using the following procedure:
NYISO Actions
1. Prepare the proposed FERC Form 715 power flow cases during the month
of January.
2. Send the proposed FERC Form 715 cases to the Transmission Planning
Advisory Subcommittee (TPAS) by January 31.
Transmission Planning Advisory Subcommittee Actions
3. Provide changes to the FERC Form 715 cases by February 28.
NYISO Action
4. Update the FERC Form 715 cases and NYISO data bank during the month
of March.
5. File the FERC Form 715 report with FERC by March 31 of each year.
Exhibit 1-3 shows a time line diagram with the steps and dates required to
submit these cases to the FERC.
15
Exhibit 1.3:
FERC 715 Report
Time Line
16
4 PERFORMANCE DATA
This section describes the NYISO data requirements for receiving and
maintaining availability and performance data for generating units connected to
the NYCA power system.
2.1 GENERATOR AVAILABILITY AND PERFORMANCE
DATA [MP 13-3]
The NYISO requires that Generator Owners report all actual reductions in the
ability of generating facilities connected to the New York State Transmission
System, serving load in New York State, located in New York State, or bidding
in the NYISO Capacity Market to generate at their scheduled or contracted
output.
Reductions in the capability of a unit for the following reasons do not have to be
reported:
•
Failure to be selected to provide energy in either the day ahead or hour
ahead energy market
•
Selection to provide energy at less than Dependable Maximum Net
Capability (DMNC)
•
Reduction in output due to provision of operating reserve
The NYISO unit outage data reporting procedures mimics the NERC
Generating Availability Data System (GADS) data submission procedures.
NERC GADS data can be submitted to the NYISO if all the NYISO data
requirements described in this section are met.
The NYISO also collects generating units performance data. The NYISO uses
unit availability and performance data in reliability assessment studies, and in
other applications requiring an estimate of available generating capacity.
Requirements and procedures for submitting these data are discussed in Section
2.3 and 2.4
2.1.1Generating Units To Be Reported
All generating units connected to the New York State Transmission system,
serving load in New York State, located in New York State, or bidding in the
NYISO Capacity Market that have a DMNC rating of 2 MW or more are
required to report availability data to the NYISO.
NYISO Manual for System Analysis Data (rev. 9/24/99)
Section 2 - Performance Data
17
2.2 GENERATOR AVAILABILITY DATA [MP 13-3
Appendices B and D]
Generator Owners will provide NYISO with two basic types of information
when reporting availability data:
•
Unit identification data
•
Unit event data
2.2.1 Unit Identification Data
This data consists of the following:
•
Unit owner (Company Name)
•
Unit name and number
•
NYISO Generator Unit Code or NERC ID
2.2.2 Unit Event Data
Unit events are divided in two major categories:
•
Outages including:
%
%
%
%
%
%
%
•
Planned Outages (PO)
Maintenance Outages (MO)
Scheduled Outage Extensions (SE)
Startup Failures (SF)
Unplanned Outage - Immediate (U1)
Unplanned Outage - Delayed (U2)
Unplanned Outage - Postponed (U3)
Deratings including:
%
%
%
%
%
Planned Derating (PD)
Unplanned Derating - Immediate (D1)
Unplanned Derating - Delayed (D2)
Unplanned Derating - Postponed (D3)
Unplanned Derating - Deferred (D4)
NERC also recognizes a reserve shutdown event, but the NYISO market based
rules do not. Only units with reserve capabilities for 30-minute nonsynchronized, 10-minute non-synchronized and spinning reserves are considered
as reserve units. Available but off-line units with longer starting times may
participate as Installed Capacity providers or submit bids as units with long-lead
times. NYISO requires that these units submit daily bids into the NYISO Dayahead market and submit to the NYISO qualification requirements, including
un-scheduled availability tests, to be considered as available units. See Section 5
of the NYISO Manual for Installed Capacity Requirements for more details.
18
2.2.3 Outage Event Types
An outage exists whenever the unit is not synchronized (i.e., not in service with
the system and not available for service). There are six distinct types of outages,
each depending on the extent to which the outage could have been postponed.
Planned Outages (PO)
Planned Outages are scheduled well in advance and are of a predetermined
duration. Turbine and boiler overhauls or inspections, testing, and nuclear
refueling are typical planned outages. Characteristically, planned outages are
planned well in advance and usually occur during those seasons of the year
when the peak demand on the system is lowest, have flexible start dates, have a
predetermined duration and occur only once or twice a year. These types of
outages are subject to the NYISO outage scheduling procedures. See Section 3
of the NYISO Manual for Outage Scheduling for more information on
scheduling these types of outages.
Maintenance Outages (MO)
This is an outage which can be deferred beyond the next weekend but requires
that the unit be removed from service before the next Planned Outage.
Characteristically, these Maintenance Outages may occur throughout the year,
have flexible start dates, are much shorter than planned outages, and may or
may not have a fixed duration. These outages are also subject to the NYISO
outage scheduling procedures.
Scheduled Outage Extension (SE)
This is the extension of a Planned Outage or Maintenance Outage beyond its
estimated completion date. Extensions are only recognized in instances where
the original scope of work requires more time to complete than originally
scheduled.
Extensions are not recognized in those instances where unexpected problems or
delays are encountered which render the unit out of service beyond the estimated
end date of the planned or maintenance outage. These delays must be reported as
Unplanned (Forced) Outages - Immediate or Startup Failure events. A
Scheduled Outage Extension, Unplanned Outage - Immediate or Startup Failure
must start at the time (month/day/hour/minute) of the end of the Planned Outage
or Maintenance Outage is reached.
Startup Failure (SF)
A Startup Failure is an outage that results from the inability to synchronize a
unit within a specified startup time period following an outage.
The startup time period for each unit is determined by the generator owner at the
time of bidding the service with the NYISO, is unique for each unit and depends
on the condition of the unit at the time of startup (hot, cold, standby, etc.). A
startup period begins with the command to start and ends when the unit is
19
synchronized. An Startup Failure begins when the problem preventing the unit
from synchronizing occurs. The Startup Failure ends when the unit is
synchronized, another Startup Failure occurs or the unit enters another
permissible outage state.
This is an outage that required immediate removal of a unit from service such as
immediate mechanical/electrical/hydraulic control system trips and immediate
operator initiated trips/shutdowns in response to unit alarms.
Unplanned Outage - Delayed (U2)
This is an outage which does not require immediate removal from service but
requires that a unit be removed from service within six hours.
Unplanned Outage - Postponed (U3)
This is an outage which can be postponed beyond six hours but which requires
the unit to be removed from service before the end of the next weekend.
2.2.4 Derating Event Types
A derating exists whenever a unit is limited to some power level that is less than
the unit's Net Maximum Capacity (except when the limitation occurs entirely
during an outage.) The cause of the limitation can be equipment failures,
regulatory restrictions, or other operating constraints.
Ambient deratings are not individually reported. Rather they are averaged for
the report period; this average value is then subtracted from the Net Maximum
Capacity and is reported with the performance data as the Net Dependable
Capacity.
For the purposes of these reporting instructions, as a minimum, deratings
meeting the following criteria shall be reported:
•
Report ALL discernible deratings EXCEPT those that meet BOTH of the
following conditions (a) and (b):
a.
Deratings that are less than 5 MW of the unit Net Maximum
Capacity; and
b.
are less than 4 hours in duration.
Deratings which for their full duration are masked by load following must be
reported as separate events.
Ambient Related
Losses
20
Ambient related losses, such as high cooling water intake temperatures, high air
temperatures to cooling towers, etc., are not to be reported as individual
deratings. These types of deratings usually vary in magnitude during the course
of the entire report period and would require an unjustified level of record
keeping. The magnitude of these losses will, therefore, be determined from the
difference in the Net Maximum Capacity and Net Dependable Capacity reported
for the unit during the period.
Derating that Vary
in Magnitude with
Time
Certain deratings, such as thermal discharge limits, stack emissions limits,
nuclear fuel limits, etc., vary in magnitude with time. These deratings may be
averaged over a month or a quarter and be reported once during that period
rather than at each occurrence.
When reporting these types of deratings the Generator owner must recognize
that these limitations would exist if the unit were not shut down, limited by a
more severe derating, or masked by a reserve shutdown.
Generator owners which do not wish to report varying magnitude continuous
deratings as a single average derating, as described above, may submit separate
event reports for each variance in the magnitude of the derating. The series of
reported event must, however, be continuous (i.e. the end date of the first
derating period must be exactly equal to the start date of the next derating
period, and so on).
Some deratings vary in magnitude but do so more abruptly and may not be
continuous. These situations would normally be reported as a number of
separate deratings for the same cause.
Derating Event
Types
There are five types of deratings, each depending on the degree to which the
initiation of the derating could have been postponed. Note that the criterion is
based upon the level of postponability which could have occurred. A subsequent
derating which further decreases the units available capacity must be reported
separately.
Deratings which occur entirely during an outage (or another derating of larger
magnitude) are not to be reported. Deratings whose start times overlap with
other events are to be reported as separate events. In these cases, the actual start
time of the derating should be reported, even though the start time may be within
the time period of the other event.
Planned Derating (PD)
This is a derating that is scheduled well in advance and is of a predetermined
duration. The actual start dates of the planned deratings are flexible, since they
are usually coordinated with periods of low peak or seasonal demands.
Periodic deratings for tests, such as weekly turbine valve tests, would not be
reported as planned deratings since there is no control over the season in which
they occur. These types of deratings would be classified as an Unplanned
Derating - Deferred.
Unplanned Derating - Immediate (D1)
21
This is a derating which requires immediate action for the reduction of capacity.
Unplanned Derating - Delayed (D2)
This is a derating which does not require an immediate reduction of capacity but
which requires a reduction of capacity within six hours.
Unplanned Derating - Postponed (D3)
This is a derating which can be postponed beyond six hours, but requires a
reduction of capacity before the end of the next weekend.
Unplanned Derating - Deferred (D4)
This is a derating which can be deferred beyond the end of the next weekend, but
requires a reduction in capacity before the next planned outage.
2.2.5 Changes in Event Type
Typically, outages retain their event type until the unit is synchronized. In some
cases the event type may change prior to synchronization. When an event type
change occurs, it could be reported as a new event. However, reporting these as
separate events requires extra effort and may lead to confusion. This is
particularly true when work begun before the Change In Event Type continues
beyond the time of the event type change. To minimize this additional reporting,
up to two changes in the event type can be requested on a previously reported
event. If more than two successive Change In Event Type occur, the third
change must be reported as a new event. Again, two Changes In Event Type
could be reported with this new event, and so on.
Using the matrix provided in Exhibit 2-1 and the following guidelines, select the
new event type that best identifies what the previous event type should be
changed to.
Exhibit 2-1:
Allowed Event
Type Changes
From/To
PO
PO
22
SE
U1
U2
U3
MO
In
Service
Yes
Yes
No
No
No
Yes
Yes
No
No
No
Yes
No
No
Yes
Yes
No
Yes
Yes
Yes
Yes
SE
No
U1
Yes
No
U2
Yes
No
Yes
U3
Yes
No
Yes
No
MO
Yes
Yes
Yes
No
No
Yes
In
Service
Yes
No
Yes
Yes
Yes
Yes
Legend:
PO = Planned Outage
SE = Scheduled Outage Extension
U1 = Unplanned Outage - Immediate
U2 = Unplanned Outage - Delayed
U3 = Unplanned Outage - Postponed
MO = Maintenance Outage
Changes in Event Type Guidelines
•
Planned Outage (PO)
% Change to this event type if a Planned Outage follows an Unplanned
Outage, or Maintenance Outage with no intervening unit
synchronization. Report the estimated time that the unit would have
been synchronized had the planned work not been done.
•
Maintenance (MO)
% Change to this event type if the unit remained shutdown to do
maintenance work following an Unplanned Outage. Report the
estimated time that the unit would have synchronized had the additional
maintenance work not been done.
•
Scheduled Outage Extension (SE)
% Change to this event type if a Planned Outage or Maintenance Outage
takes longer than originally scheduled, except because of a start up
failure, in which case U1 is used. Report the originally scheduled start
up time.
•
Startup Failure (SF)
% Change to this event type if a problem occurs during a unit start up that
prevents the unit from being brought from shutdown to synchronism
(i.e. a starting failure). Report the time that the unit should have
synchronized had the start up failure not occurred.
•
% Change to this event type if the outage required immediate removal of a
unit from service. This type of outage results from immediate
mechanical/electrical/hydraulic control systems trips and operatorinitiated trips in response to unit alarms.
% Report the time that the problem was discovered. If the same problem
were discovered during any other type of outage (Planned, Maintenance,
or Unplanned Outage) the event type is not changed. The original
outage type continues until a start up failure occurs or until the unit is
23
synchronized. Should the problem result in the extension of a Planned or
Maintenance Outage report it as a Scheduled Outage Extension (SE).
End of Event
For units reporting events only to NYISO but not to NERC under the GADS
procedures, only one event report should be submitted at the time the event ends.
If an event extends from one year to the next, two separate events should be
reported to the NYISO.
2.3 GENERATING UNITS PERFORMANCE DATA [MP
13-3 App. D]
***Note to NYISO Document Reviewers: Please confirm that NYISO will
keep collecting these data directly from the Generator Owners.***
The following unit performance data is collected by NYISO at least annually.
These data are used to calculate performance statistics. Both gross and net
values are requested. Net values are preferred but reporting gross data only is
acceptable. Reporting (either) gross and (or) net data depends on how the unit is
electrically metered. Some units are metered on a single basis (gross or net).
Enter your unit's data on the basis of how your unit is actually metered. If you
meter both gross and net, enter both values. If you meter on a single basis, but
can estimate the other, do so and enter the estimated value in the appropriate
field. The value you report, GROSS or NET, must be consistent with the
available capacity as a result of deratings reported as events.
2.3.1 Performance Data
The following unit performance data is collected by the NYISO:
•
Gross Maximum Capacity
•
Gross Dependable Capacity
•
Gross Actual Generation
•
Net Maximum Capacity
•
Net Dependable Capacity
•
Net Actual Generation
NERC definitions are used for each of these data types:
Gross Maximum Capacity (GMC)
The GMC is the maximum capacity the unit can sustain over a specified period
24
of time when not restricted by ambient conditions or deratings. To establish this
capacity, formal demonstration is required.
The GMC of a unit should change only as a result of a new performance test or
permanent unit modification. The GMC is never changed due to equipment
problems, even if they persist for a lengthy period of time unless the unit is
permanently modified as a result. If the unit is permanently modified, submit the
changes with adequate documentation to the NYISO.
Gross Dependable Capacity (GDC)
The GDC is the gross power level which the unit can sustain during a given
period if there are no equipment, operating or regulatory restrictions. By
definition, the GDC and GMC are modified for ambient limitations.
The GDC is the same in intent and purpose as the historically reported
Maximum Dependable Capacity (MDC).
Gross Actual Generation (GAG)
The GAG is the actual number of gross electrical megawatts (MWh) generated
by the unit during the reporting period.
For consistency in calculating statistics, if Gross Actual Generation is reported
GMC or GDC must also be reported. Similarly, if a gross capacity value is
reported, Gross Actual Generation must also be reported.
Net Maximum Capacity (NMC)
The NMC is the unit's GMC less any capacity (MW) utilized for that unit's
station service or auxiliary load.
Net Dependable Capacity (NDC)
The NDC is the unit's GDC less any capacity (MW) utilized for that unit's
station service or auxiliary load.
Net Actual Generation (NAG)
The NAG is the unit's GAG less any generation (MWh) utilized for that unit's
station service or auxiliary loads.
For consistency in calculating statistics, if Net Actual Generation is reported
(negative integer or positive integer), NMC or NDC must also be reported.
Similarly, if a net capacity value is reported, Net Actual Generation must also
be reported.
2.3.2 Unit Starting Characteristics
25
The data in this section are used to establish the manner in which the unit was
operated during the reporting period. This information is needed when sorting
data for use in special availability/reliability applications.
Attempted Unit Starts
These are the number of attempts made to bring the unit from shutdown to
synchronization during the period. Repeated failures to start for the same cause
without attempting corrective actions are considered a single attempt.
If startup attempts are abandoned and the unit is shut down for repairs and then
started at a future time, report two startup attempts.
Actual Unit Starts
These are the number of times the unit was actually synchronized during the
report period.
The number of actual unit starts must be less than or equal to the number of
attempted unit starts.
2.4 AVAILABILITY AND PERFORMANCE DATA
REPORTING PROCEDURE
Generation owners shall use the following procedure to report all the availability
and performance data described previously:
Generator Owner Actions
6. Report availability and performance data following the guidelines in
Sections 2.3 and 2.4.
7. Submit data annually in electronic format. Data for the previous year should
be received by April 15 of the subsequent year.
Reporting Data for Special Cases
For hydro units with telemetering available to the NYISO, the net hourly
generation shall be provided by the NYISO based on historical on-line system
data.
All other special cases are reviewed by NYISO on a case by case basis.
26
4 SYSTEM NETWORK REPRESENTATION
This section describes the data requirements for system studies. Data for
conducting planning and operating studies includes the power flow network
representation and the necessary supplementary model data for performing
stability analysis. The NYISO collects this data from all owners with facilities
connected to the NYCA. Facility owners must develop, and maintain data for
their facilities suitable for modeling both static (power flow) and dynamic
(stability) analysis. All facility owners must provide these data to NYISO in
accordance with these procedures.
3.1 NETWORK MODEL DATA [NYPP Data Bank App. G]
The NYISO requires all transmission facilities owners, generation owners, and
load serving entities with facilities connected to the NYCA to provide the
NYISO with the appropriate network modeling information. To maintain an
accurate network model in accordance with NPCC requirements, NYISO needs
data on:
•
AC Transmission facilities
•
DC Transmission facilities
•
Shunt devices
•
Transformers
•
Substation and switching station bus configurations
•
Generating stations and units
•
Static VAR compensators or synchronous condensors
•
FACTS devices
•
3.2 FACILITY RATINGS
This section discusses the importance of reporting accurate facility ratings. Two
important types of facility ratings are discussed:
Electrical facilities used in the production, transmission, storage, and delivery of
electricity shall be rated in compliance with NYISO Tie-Line Rating Guide.
This criteria applies to all ratings data required for network modeling and for
real-time applications. The base facility rating criteria is described below:
•
Facility owners shall document the methodology for determining facility
ratings, including delineation and justification of assumptions, standards,
and practices used in establishing the ratings. The documentation submitted
Section 3 - System Network Representation
27
to NYISO must state the ratings and their basis applicable to each of the six
base case model types described earlier in this manual.
•
Facility owners shall provide facility ratings (applicable normal and
emergency) for all facilities required for system modeling as defined in this
Procedure.
•
The rating of a system facility (e.g., transmission line, transformer, etc.)
shall not exceed the rating of the most limiting series element in the circuit
or path of the facility, including terminal connections and associated
equipment.
•
In cases where protection systems and control settings constitute a loading
limit on a facility, this limit shall become the rating for that facility.
•
Ratings of jointly owned facilities shall be coordinated and provided on a
consistent basis. The ratings submitted shall be agreed to through the
consensus of the facility owners.
•
Facility ratings should be based on or adhere to applicable national
electrical codes and electric industry rating practices consistent with good
engineering practice.
3.3 LOAD DATA [NYPP Data Bank, App. G]
NYISO requires that all Load Serving Entities and Transmission Owners
provide actual and forecast demand data for their respective customers for
steady state modeling at the bus load level.
The NYISO Data Bank bus load data provides for forecast loads for twenty (20)
years. In the first six (6) years (current plus next 5) data representing the
following loads shall be provided for each of the Summer and Winter capability
periods:
%
%
%
%
Coincident (NYISO) peak (MW and MVAr)
Independent peak (MW and MVAr)
Off-peak (light) load (MW and MVAr)
Nominal peak (MW and MVAr)
The off-peak load is defined as the minimum load expected on the day of the
system peak, and is generally 40-45% of the season peak. The nominal load is
the typical load level expected during Spring or Fall, and is generally 70-75% of
the season peak.
The remaining years (6 through 20) loads are the seasonal (summer and winter)
coincident peak (MW and MVAr) loads.
3.4 DYNAMICS MODELING DATA
28
Many dynamics models are developed by the Institute of Electrical and
Electronics Engineers (IEEE) [1-5]; however, many other models are not.
NYISO will provide data sheets for any standard dynamic model in NYISO’s
dynamics software upon request. Submission of dynamics data in the form of
raw data files for NYISO dynamics software is also accepted and encouraged.
For a few specialized devices, a computer simulation module for the
implementation of the model may also be needed. The NYISO uses the Power
Technologies, Inc. (PTI) PSS/e power system analysis program. Models
directly supported by the PSS/e program are described in the PSS/e Data
Exchange Manual.
The dynamics data required by the NYISO includes detailed equipment-specific
data for:
•
generators
•
excitation systems and voltage regulators
•
turbine-governor systems
•
power system stabilizers
•
relays and protection equipment (out of step, over-speed, etc) and
•
other control equipment or dynamic devices
This includes complete and accurate models of controls suitable for integration
with the analytical software. In no case shall other than unit-specific data be
used for generator units installed after 1990. Typical manufacturer's dynamics
data, based on units of similar design and characteristics, may be used when
unit-specific dynamics data cannot be obtained.
3.4.1 Generator Dynamics Data
NYISO requires a dynamic model for each generator connected to the NYCA .
The model for dynamic studies must be in a form usable by the dynamics
software employed by NYISO. For most generators, the following data items
constitute a complete dynamic model:
•
•
•
•
•
•
•
rotor type (solid or salient pole)
unsaturated values of synchronous, transient, and subtransient
reactances (Xd, Xq, Xd’, Xq’ (for solid rotors), Xd”) in per unit on
machine base
unsaturated value of leakage reactance (Xl) in per unit on machine base
transient and subtransient time constants (Tdo’, Tqo’ (for solid rotors),
Tdo”, Tqo”) in seconds
inertia constant (H) in per unit on machine base
shape of saturation curve (quadratic or exponential)
saturation factors (S1.0, S1.2)
29
Some generators may require a model which is not supported by a an available
model in the PSS/e model library. for such generators, the model must include
all data and be in a form usable by NYISO dynamics software.
3.4.2 Generator Controls Dynamics Data
Generators have many associated control systems, including excitation systems,
voltage regulators, turbine-governors, and power system stabilizers. The
number of different types of models for each category of control system is large,
and each model has different parameters associated with it. For each control
system on the generator, a model with all data must be supplied in a form usable
by NYISO dynamics software..
3.4.3 Network Dynamics Data
Transmission Owners must supply NYISO with the models for dynamic devices
on the transmission network. Examples of such devices include static var
compensators (SVCs),
synchronous condensors, FACTS controls, and monitoring relays. For each
such dynamic device, the Transmission Owner must supply NYISO with a
dynamic model and all associated data in a form usable by NYISO dynamics
software.
3.4.4 Load Dynamics Model Data
Some large loads include synchronous or induction motors, or other equipment
or characteristics that may have a significant impact on the dynamic response of
the New York State Power System. For each such device on the system, the
load serving entity must provide NYISO with a dynamics model and all
associated data in a form usable by NYISO dynamics software. Load serving
entities may consult their host Transmission Owner for guidance on which
loads, if any, need to be included in NYISO dynamic studies.
30
4. SYSTEM PROTECTION DATA [MP31-3]
The NYISO transmission system protection data are required to develop and
maintain functional models of the bulk power system protection devices which
can be used for dynamic simulation and for the coordination of protection
facilities with existing and proposed system reinforcements. Some of the data
are 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.
Transmission Owners system protection engineering staff provide data tot the
NYISO System Protection Coordinator. Data are required for all facilities
which are included in the NYISO-secured Transmission System as described in
the NYISO Manual for Transmission & Dispatching Operations.
Characteristics of protection equipment associated with NYISO-secured
Transmission System facilities are important for dynamic simulation and other
aspects of the NYISO operations. [This facilities list is also included as
Attachment D, Exhibit D-1 to this manual.]
4.1 RELAY CHARACTERISTICS
Protection systems are specifically modeled (rather than generically) when they
could operate within the scope of system dynamic simulations (power system
stability analyses).
Transmission line distance protection is represented in dynamic simulations.
However, when the actual relay system characteristics are not available, a
generic relay model may be used. Where appropriate, over-current or out-ofstep protection may also be modeled. Simplified data submission forms are
included in Attachment D, Exhibits D-2 and D-3.
Relay characteristics are required only for relays which 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 (see Section 4.2, below).
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.
Section 4 - System Protection Data
31
Definition:
Pilot Protection
Systems
Pilot protection systems are defined as those systems which 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 in Sections 4.2 and 4.3 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 form contained in
Attachment D, Exhibit D-2. If the relay schemes do not fit the form (only Mhodistance or reactance-distance relays) a combination of the forms presented in
Attachment D, Exhibit D-2 and Exhibit D-3 shall be used. If the Transmission
Owner already is using the Power Technologies, Inc., PSS/E program, then
PSS/E input forms can be used in place of the forms presented in Attachment D.
32
4.2 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.
4.2.1 Clearing Times
Transmission 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 the
NYISO staff when needed
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.
4.2.2 Reclosing Times
The following information is required by 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
33
•
Third Shot: Hot-bus/dead-line reclosing time in seconds
Data submission forms are included in Attachment D, Exhibit D-4. Reclosing
terms are used as defined in the NPCC Bulk Power System Reclosing Guide.
4.3 SPECIAL PROTECTION SYSTEMS (SPS)
Protection based systems that are designed to monitor special system conditions
can have an impact on system operation. 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)
4.3.1 Special Protection Systems
Definition:
Special Protection
System (SPS)
A Special Protection System (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.
Transmission 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 Transmission 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 which 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 which is
updated and posted annually by NPCC.
4.3.2 Other Remedial Action Systems
34
In addition to NPCC Special Protection Systems, NYISO Transmission Owners,
generation operators, load serving entities, or other participants may operate
other remedial action system which are similar in concept to SPS’s and which
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 ways in which a protection system
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 Transmission Owner that allows the TP
to mitigate a transmission security limitation
A protection system that limits the ability to load a facility to rated
Short Term Emergency (STE) cpability
The NYISO System Protection Coordinator notifies the Transmission Owner
SPAS Member when one of the above situations is detected and a System
Impacting Protection System report is required.
4.3.3 SPS Data Submission And Updating Procedures
The following procedures apply to all data described in the Sections 4.3.1 and
4.3.2 unless otherwise indicated.
Transmission Owners Actions:
8. Submit to the NYISO System Protection Coordinator updates to the
following data for all facilities listed in Attachment D, Exhibit D-1 by May
1st of each year or upon the implementation of a new System Impacting
Protection System:
c. Relay characteristics using the forms in Attachment D, Exhibit D-2 and
D-3
d. Clearing times using forms in Attachment C, Exhibit D-2 and D-3
e. Reclosing times using form in Attachment D, Exhibit D-4
9. Submit to the NYISO System Protection Coordinator the SPS report at least
three months before placing the SPS in service.
10. 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.
11. Some of the lines listed in Attachment D, Exhibit, Exhibit D-1 are the
interconnections with neighboring control areas. In these cases, the
Transmission Owner SPAS member is responsible for furnishing the data
for all terminals of the line.
NYISO Actions:
35
1. Once each year the NYISO System Protection Coordinator shall transmit all
data back to each Transmission Owner SPAS Member, for confirmation or
revision.
2. Use the SPS data in the dynamic simulation, thermal and voltage
contingency analysis studies.
3. Inform the Transmission 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 Transmission
Owner and NYISO personnel.
4.4
POWER LINE CARRIER FREQUENCIES [MP 37-2]
This section describes the procedure for coordination of Power Line Carrier
(PLC) Frequencies among Transmission Owners of the NYISO and neighboring
systems. As part of the coordination process, information is provided for
updating PLC databases maintained by the Utilities Telecommunications
Council (UTC).
4.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, NYISO participates as
part of a working group known as the Power Line Carrier Task Force or PLC
Task Force. This task force is comprised of 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.
UTC PLC Task
Force Contacts
Each Transmission 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 Transmission Owner contact to the
NYISO contact and System Protection Coordinator as soon as possible. NYISO
will report such changes to the UTC, SPAS, and all PLC Task Force contacts.
36
4.4.2 UTC PLC Frequencies Database Reports
Two UTC PLC Frequencies Database reports are available by contacting the
UTC. Turnaround time to receipt of any of the reports is about three working
days.
•
Individual Organization Report — This is a report of an individual
organization’s PLC frequencies. The PLC Frequency data is sorted by
substation, transmitter and associated receiver(s), and frequencies.
•
Interference Report — This report defines 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.
4.4.3 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
In all these cases, the PLC Frequency Data Report form is completed and sent to
NYISO. This form is shown as Exhibit D-5 in Attachment D to this manual.
All the information on this form must be completed and the applicable UTC
Transaction Code must be specified:
UTC PLC
Transaction Codes
•
Code A stands for “Addition of a frequency in service”
•
Code P stands for “Addition of a proposed frequency”
•
Code C stands for “Correction of information for a frequency in service”
PLC Task Force Contact Actions:
1. The Transmission Owner PLC Task Force contact shall initiate this process
by submitting a completed PLC Frequency Data Report to the NYISO.
This form shall be completed to indicate each new frequency or change.
NYISO Actions:
2. Upon receiving a completed PLC Frequency Data Report, the NYISO shall
send copies of the report to:
UTC Address
Other Transmission Owner PLC Task Force contacts
The Utilities Telecommunications Council
37
1140 Connecticut Avenue NW
Washington DC 20036
PLC Task Force Contacts Actions:
3. 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.
4. 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.
5. 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
forwarding to UTC.
NYISO Actions:
6. When frequencies are found satisfactory by all PLC Task Force contacts,
the NYISO shall send a memorandum to the PLC Task Force contacts
informing this result.
UTC Actions:
7. Upon receiving the PLC Frequency Data Report, the UTC will report other
potential conflicts to the affected Transmission 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.
4.4.4 Retiring PLC Frequencies Procedure
When Transmission 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 that stands for “deletion of an existing PLC frequency”.
It is not necessary for the Transmission Owner’s PLC Task Force contacts to
respond to the NYISO in the case of frequencies retired.
PLC Task Force Contact Action:
1. Initiate this process by submitting a completed PLC Frequency Data Report
38
to the NYISO. This form shall be completed to indicate each frequency
retired.
NYISO Action:
2. Upon receiving a completed PLC Frequency Data Report, the NYISO shall:
•
Send copies of the report to the PLC Task Force contacts
•
Send copies of the report to UTC at the address above
4.4.5 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.
UTC Action:
1. 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.
PLC Task Force Contact Action:
2. Review and revise the UTC database and send it directly to the UTC.
3. Send copies of the PLC Database revisions to the NYISO.
NYISO Action:
4. Send copies of received PLC Frequencies Database updates to all of the
other PLC Task Force contacts.
39
4.5
FAULT ANALYSIS DATA
This section describes the procedure for maintaining the NYISO Short Circuit
representation.
4.5.1 Introduction
The NYISO System Protection Coordinator shall maintain a uniform short
circuit representation for fault analysis. The Transmission 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 insure availability of this data for any necessary analyses required in a system
impact study in accordance with the NYISO Manual for Transmission
Expansion and Interconnection. 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.).
4.5.2 Annual Review of the Short Circuit Representation
Annually, the NYISO System Protection Coordinator initiates the review of the
NYISO Short Circuit Representation by sending to each Transmission Owners
SPAS representative a copy of their respective current data for review.
Transmission Owner Action:
Review and revise the short circuit database as appropriate and return it to the
NYISO System Protection Coordinator. This will include changes to existing
data or additions or deletions to the representation based on system changes
which have recently occurred or are planned for installation within the next
capability periods.
NYISO Action:
The NYISO System Protection Coordinator shall update the NYISO short
circuit representation as indicated.
The NYISO System Protection Coordinator shall make the representation
available to all Transmission Owners, other NYISO staff, or to such contractors
40
and consultants or regulatory agencies for purposes of conducting system
studies associated with transmission system reliability assessment.
41
4. REAL-TIME REPRESENTATION DATA
This section describes the data requirements, formats, and procedures used in
modeling and maintaining the NYISO/NYCA system representation used for
real-time analysis. The Real-Time Security Analysis (RTSA) model is also
used in the day-ahead Security Constrained Unit Commitment (SCUC) and
hour-ahead Balancing Market Evaluation (BME) processes.
5.2
REAL-TIME SYSTEM REPRESENTATION DATA
The NYISO real-time system representation data includes the following data
groups:
•
Station/bus data
•
Generator data
•
Transmission lines
•
Transformers
•
Load
•
Shunts
•
Switches
•
Ratings of Facilities
Attachment E of this manual contains sample of each of these data groups and
the RTSA Data Specifications.
.5.2.1 System Network Representation Data
The representational data in each of the data groups above must be provided to
model the NYISO-secured facilities to assure accurate modeling in real-time
system operation.
.5.2.2 Facilities Ratings Update Data
All facilities represented in the NYISO-secured system must be provided with
thermal rating data in accordance with the NYISO Tie Line Rating Guide.
Included in these ratings are the Normal, Long-time Emergency, and Short-time
Emergency ratings for each of the Summer and Winter capability periods. It is
the responsibility of the Transmission Owner to provide timely updates of these
facility ratings to the NYISO staff.
42
NYISO Manual for System Analysis Data ( rev.: 9/24/1999)
Section 5 - Real-Time Representation Data
Where a facility involves multiple ownership, each owning party shall provide
their respective ratings of their owned portion of the facility. The NYISO staff
shall coordinate the data to insure that the proper ratings are used.
.5.2.3 Dynamic Rating Updates [MP 20-4]
All transmission lines and power transformers included in the NYISO-secured
facilities system representation and those that have real power (MW)
telemetering transmitted to the NYISO control center are reviewed by the
NYISO Data Coordinator to determine which facilities are critical to system
security.
These facilities are included on the Dynamic Rating List as shown in
Attachment C of this manual.
Dynamic ratings are normally updated by coded messages sent to the NYISO
control center via computer to computer data links. (See NYISO Manual for
Control Center Requirements).
Updated ratings entered in the NYISO control center computer are used
immediately. The rating of a facility may be changed only by the Rating
Authority. (See Attachment C)
If computer facilities are not available, the NYISO Shift Supervisor may
manually enter dynamic ratings into the NYISO control center computer. upon
receipt of verbal instruction from the Rating Authority only.
A message is returned to the rating authority reporting the status of each update.
For jointly owned facilities within the NYISO, all involved parties receive notice
of all rating changes.
5.3
SYSTEM REPRESENTATION [MP 22-4]
The NYCA operating system representation is used for short-term and midrange system studies. These studies include:
•
Operating Studies Power Flow Base Case including:
•
•
•
•
interface thermal limit analysis
system studies for voltage limits
system dynamic analysis
NYISO Real-time System Applications
5.3.1 Operating System Representation Definitions
43
The following terms are used to describe different components of or references
to the operating system representation:
•
Level 5 Base Case: A power flow that contains the full extent of detail
available from the NYISO Data Bank for the appropriate season (summer
or winter) represented and is most suitable for Market Participant review.
•
The Seasonal Operating Studies Base Case: This is the level 5 or level 4
power flow base case used for establishing seasonal transfer limits, day
ahead analysis, and stability transfer and voltage limit development analysis.
•
Real-time System Representation: This is a power flow base case with a
reduced level of detail sufficient to represent the NYISO real-time system
which is used for:
% Security Constrained Unit Committment
% Balancing Market Evaluation
% Security Constrained Dispatch
•
System Representation Diagram: This is a one-line diagram graphically
portraying the facilities in the NYISO real-time system representation.
5.3.2 System Representation Review Procedure
The following procedure describes the process followed to review and edit the
NYISO RTSA System Representation.
NYISO Actions
The NYISO Operating Studies Task Force shall review the Level 5 power flow
base case prior to the start of each Seasonal Operating Study.
The NYISO Engineering staff shall review and update the RTSA representation
as necessary for changes corresponding to revisions to the operating study
representation.
5.3.3 Review of Real-time Contingencies & Monitored Lines
Upon completion of the annual review, the following actions are required.
NYISO Actions
Send to SOAS a copy of the real-time contingencies and monitored lines for
review. This includes the lists of multiple-circuit tower, bus-fault, and delayed
clearing contingencies, thunderstorm watch multiple element contingencies, and
any exceptions to the criteria.
SOAS approves the new list of real-time contingencies and monitored lines.
The NYISO Engineering staff modifies the contingency and monitored lines to
reflect any corrections.
44
NYISO Manual for System Analysis Data ( rev.: 9/24/1999)
Attachment A
NYISO DATA CONFIDENTIALITY
This attachment contains the NYISO confidentiality classification for system
planning databases and data.
Attachment A
45
Confidential Data
NYISO Data
A. PROMOD/MAPS/MWFLOW (data consistent withcurrent Yellow Book)
Unit Ratings
Variable O&M
Unit Startup Costs
SO2 Emission Costs
Heat Rates
Dispatch and Operating Factors
Transactions Prices
Utility Forecast Fuel Prices
Load Model
Transfer Limits
Full & Forced and Partial Outage Rates
Maintenance Schedule
B. RELIABILITY
Unit Ratings
Full & Partial Forced Outage Rates
Maintenance Schedules
Load Model
Transfer Limits
C. POWER FLOW/STABILITY DATA
Network Model
Load Model
Machine Stability Assessment Data
Generator Model
Fuel Cost/Heat Rate Cost Curves
Base Load Unit Dispatch Model Schedule
D. FORECAST DATA
Load Forecast
F. PROTECTION SYSTEM DATA
Relay Characteristics
Special Protection Systems
PLC Frequencies
(1) Class 1 is confidential.
Class 2 is non-confidential.
(2) Yellow Book is NYPP Load and Capacity Report
Class (1)
Non-Confidential Data
Required by
Regulations
Data to be supplied
in lieu of
confidential data
Frequency of
Update
2
1
1
1
1
1
1
1
2
2
2
2
$1/MWH
None
None
1994 Data
1994 Data
None
LRAC Study Prices
-
Annual Yellow Book (1)
Semi-Annual
Annual
As Requested by RPAS
Yes
No
No
No
No
No
No
Yes
No
Yes
No
No
2
2
2
2
2
-
Annual Yellow Book
Yes
No
No
No
No
2
2
2
2
1
2
None
-
Annual
Annual
Annual
Annual
Annual
Annual
Yes
Yes
No
Yes
No
No
2
-
Yes
Attachment B
NYISO POWERFLOW DATA BANK FORMS
The following forms describe the data contained in the NYISO Power Flow Data Bank.
Additional detail can be found in the NYISO Power Flow Data Bank Procedure Manual.
NYISO Manual for System Analysis Data
Attachment B
47
48
Attachment B
Attachment B
49
50
Attachment B
Attachment B
51
52
Attachment B
Attachment B
53
54
Attachment B
Attachment B
55
56
Attachment B
Attachment B
57
58
Attachment B
Attachment B
59
60
Attachment B
Attachment B
61
62
Attachment B
Attachment B
63
64
Attachment B
Attachment B
65
66
Attachment B
Attachment B
67
Attachment C
NYISO DYNAMIC RATING FACILITIES
The accompanying table designates those facilities that can be updated, and
designates which Transmission Owner is the Rating Authority for each facility.
When a facility is to be updated, the Rating Authority must address the facility
consistent with the form in which it is listed and shown in the operating system
representation. If a facility is listed as a combination (those parallel facilities
bussed at both ends and metered as a net), the combination rating must be
updated; if the facility is listed individually, the individual facility must be
updated.
Reductions in ratings which are caused by abnormal operating conditions, such
as a breaker out of service in a breaker and a half scheme, cooling reduced on a
facility normally forced cooled, etc., must also be reflected in the updated rating.
COMBINATIONS
In the case of a combination, the updating should address the combination for
the condition of all facilities in service. Programs at the NYISO modify that
combination rating to reflect the current status of relevant facilities that are out
of service.
SERIES ELEMENTS BETWEEN THE TWO TERMINALS LISTED
Ratings entered for a metered facility must reflect the most limiting element(s) in
the series path between the two terminals listed.
68
Attachment C
TABLES OF FACILITIES THAT CAN BE UPDATED DYNAMICALLY
(Listing by Rating Authority)
CONSOLIDATED EDISON COMPANY OF NEW YORK, INC.
SEE
NOTE
Astoria-Corona
34181
Astoria-Corona
34182
Astoria-Corona
34183
Astoria-Corona
34184
Astoria-Corona
34185
Astoria-Corona
34186
Astoria W.-Queensbridge
28241
28242
28243
28244
Astoria W.-N. Queens
34111
Astoria W.-N. Queens
34112
Branchburg-Ramapo
5018
2
Buchanan 345/138 (TA5)
95891
Buchanan-Eastview
W93
Buchanan-Millwood
W97
Buchanan-Millwood
W98
Buchanan-Millwood
96951
Buchanan-Millwood
96952
Corona-Jamaica
18001
Corona-Jamaica
18002
Dunwoodie-Dunwoodie N.
W74
2
Dunwoodie-Dunwoodie S.
W73
2
Dunwoodie-E. 179th St.
99153
Dunwoodie-Pleasantville
W89
W90
Dunwoodie-Rainey
71
Dunwoodie-Rainey
72
Dunwoodie-Sherman Creek
99031
Dunwoodie-Sherman Creek
99032
Dunwoodie-Shore Road
Y50
Eastview-Sprainbrook
W64
W65
W78
W79
Eastview 345/138 #1N
87873
Eastview 345/138 #1S
87871
Eastview 345/138 #2N
87874
Eastview 345/138 #2S St.
87872
E. Fishkill-Wood St.-Pleasantville
F38
E. Fishkill-Pleasantville
Y87
E. 13th St.-Farragut
45
46
B47
48
E. 13th St. 345/138
37372
E. 13th St. 345/138
37373
Attachment C
69
E. 13th St. 345/138
E. 13th St. 345/138
E. 13th St. 345/138
E. 13th St. 345/138
E. 13th St. 345/138
E. 13th St. 345/69
E. 179th St.-Hell Gate
E. 179th St.-Parkchester
Farragut-Gowanus
Farragut-Gowanus
Farragut-Hudson Avenue
Fox Hills-Freshkill
Fox Hills-Freshkill
Freshkill 345/138 (21191)
Freshkill 345/138 (21192)
Goethals-Freshkill
Goethals-Freshkill
Gowanus-Goethals
Gowanus-Greenwood
Gowanus-Greenwood
Gowanus 345/138 (42231)
Gowanus 345/138 (42232)
Greenwood-Fox Hills
Greenwood-Fox Hills
Hellgate-Astoria W.
Hellgate-Astoria W.
Hellgate-Astoria W.
Hellgate-Astoria W.
Hellgate-Astoria E.
Hellgate-Astoria E.
Hudson-Farragut
Hudson-Farragut
Hudson Ave.-Jamaica
Hudson Ave.-Jamaica
Jamaica-Lake Success
Jamaica-V.S.
Ladentown-Buchanan
Ladentown-W. Haverstraw
Ladentown-Bowline
Linden-Goethals
Long Mt.-Pleasant Valley
Millwood W.-Eastview
Millwood W.-Eastview
Millwood-Sprainbrook
Pleasant Valley-Wood Street
Pleasant Valley-Millwood
70
37374
37375
37376
37377
37378
44371
15053
15054
15055
38X01
38X02
38X03
38X04
41
42
32077
32078
32711
29211
29212
TA1
TB1
21
26
25
42231
42232
T2
T14
29231
29232
24051
24052
24053
24054
34051
34052
B3402
2
C3403
2
701
702
903
901L&M
Y88
67
68
A2253
2
398
W82
W99
W85
F30
F31
2
2
2
Attachment C
Pleasant Valley-E. Fishkill
Pleasant Valley-E. Fishkill
Pleasantville 345/13
Pleasantville 345/13
Queensbridge-Vernon
Queensbridge-Vernon
Rainey-Farragut
Rainey-Farragut
Rainey-Farragut
Rainey-Vernon
Rainey-Vernon
Ramapo PAR
Ramapo PAR
Ramapo-Buchanan
Ramapo-Ladentown
Rock Tavern-Ramapo
Sherman Creek-E. 179th St.
Sherman Creek-E. 179th St.
So. Mahwah-Ramapo
So. Mahwah-Ramapo
Sprainbrook-Dunwoodie
Sprainbrook-Dunwoodie (#S6)
Sprainbrook-Dunwoodie (#N7)
Sprainbrook-Tremont
Sprainbrook-W. 49th Street
Sprainbrook-W. 49th Street
Tremont 345/138
Tremont 345/138
Vernon-Greenwood
Vernon-Greenwood
Waldwick-So. Mahwah
Waldwick-So. Mahwah
W. 49th Street-E. 13th St.
W. 49th Street-E. 13th St.
Wood Street-Millwood
Wood St.-Pleasantville
F36
F37
#1
#2
31281
31282
61
62
63
36311
36312
#3500
#4500
Y94
W72
77
15031
15032
69
70
W75
99941
99942
X28
M51
M52
2
2
2
#11
#12
31231
31232
J3410
K3411
M54
M55
W80
Y86
CENTRAL HUDSON GAS & ELECTRIC CORPORATION
Coopers Corners - Rock Tavern
CCRT-34
Coopers Corners - Rock Tavern
CCRT-42
Fishkill-Sylvan Lake
A
Franklin-Sugarloaf
SJ&SD
Hurley 345/115
#1
Leeds-Hurley Avenue
301
Pleasant Valley 345/115
S1
Rock Tavern 345/115
#1
Roseton-E. Fishkill
RFK-305
Roseton-Hurley
303
Roseton-Rock Tavern
311
LONG ISLAND LIGHTING COMPANY
Barrett-Newbridge
Attachment C
461
3
1
2
2
71
E. Garden City-Newbridge
E. Garden City-Newbridge
E. Garden City PAR
E. Garden City PAR
E. Garden City 345/138
E. Garden City 345/138
Northport-Elwood
Northport-Elwood
Newbridge-Ruland
Newbridge-Ruland
Northport-Pilgrim
Northport-Pilgrim
Northport-Pilgrim
Norwalk Harbor-Northport
Ruland-Pilgrim
Ruland-Pilgrim
Shore Rd.-Lake Success
Shore Rd.-Lake Success
Shore Rd.-Glenwood
Shore Rd.-Glenwood
Shore Rd. 345/138
Shore Rd. 345/138
Syosset-Newbridge
Valley Stream-E. Garden City
Valley Stream-Barrett
Valley Stream-Barrett
Sprainbrook-E. Garden City
NIAGARA MOHAWK POWER CORPORATION
Alcoa Bus Tie
Adirondack-Porter
Adirondack-Porter
Alcoa-Browning
Alcoa-Dennison
Bear Swamp-Rotterdam
Beck-Packard
Beck-TSC
Beck-Harper
Beck-Lockport
Bennington-Hoosick
Berkshire-Alps
Blissville-Whitehall
Clay 345/115
Clay 345/115
Clay-Dewitt
Dennison-Sandstone
Dennison-Colton
Dewitt 345/115
Dunkirk 230/115
Dunkirk 230/115
Edic 345/230
Edic 345/115
Edic 345/115
72
462
463
#1
#2
#1
#2
678
681
561
562
672
677
679
1385A&B
661
662
367
368
365
366
#1
#2
558/559
262
291
292
Y49
R8105
11
12
13
12
E205
BP76
105
106
104
6
393
7
#1
#2
13
4
5
#2
#31
#41
#2(17)
#3(10)
#4(20)
2
2
2
2
2
Attachment C
Edic-Fraser
Edic-New Scotland
Elbridge-Lafayette
Elbridge-Hyatt
Elbridge 345/115
Erie-Dunkirk
Gardenville 230/115
Gardenville 230/115
Gardenville 230/115
Gardenville-Dunkirk
Gardenville-Dunkirk
Huntley-Gardenville
Huntley-Gardenville
Inghams
Inghams PAR
Inghams-Richfield Springs
Lafayette-Dewitt
Lafayette-Oakdale
Leeds-Pleasant Valley
Lockport-Batavia
Lockport-Batavia
Lockport-Oakfield
Lockport-Hinman
Lockport-Sweden
Lockport-Sweden
Lockport-Telegraph Road
Malone-Colton
Marcy-New Scotland
Mortimer-Elbridge
Mortimer-Elbridge
Mortimer-Pannell
Mortimer-Pannell
New Scotland 345/115
New Scotland 345/115
New Scotland-Alps
New Scotland-Leeds
New Scotland-Leeds
New Scotland-North Catskill
Niagara-Gardenville
Niagara-Lockport
Niagara-Lockport
Niagara-Lockport
Niagara-Packard
Niagara-Packard
Niagara-Packard
Niagara-Packard
Niagara-Packard
Niagara-Packard
Niagara-Packard
Nine Mile-Clay
Nine Mile-Scriba
Oswego-Elbridge
Attachment C
EF24-40
14
17
15
#1
68
#2
#3
#4
73
74
79
80
R81
#2
941(7)/942
22
4-36
91
92
107
108
112
100
111
113
114
4
UNS18
1
2
24
25
#1
#2
2
93
94
9
180
101
102
120
61
62
191
192
193
194
195
8
9
17
73
Oswego-Volney
Oswego-Volney
Packard 230/115
Packard 230/115
Packard 230/115
Packard-Huntley
Packard-Huntley
Pannell-Farmington
Porter 230/115
Porter 230/115
Porter-Inghams
Porter-Valley
Porter-Rotterdam
Porter-Rotterdam
Quaker-Sleight
Reynolds Rd. 345/115
Rotterdam 230/115
Rotterdam 230/115
Rotterdam 230/115
Scriba-FitzPatrick
Scriba-Volney
Scriba-Volney
Sweden-Mortimer
Sweden-Mortimer
Telegraph Road-Mortimer
Volney-Clay
Volney-Marcy
Warren-Falconer
11
12
#2
#3
#4
77
78
4
#1
#2
5
4
30
31
13
#2(1) 2
#6
#7
#8
10
20
21
111
113
114
6
19
171
NEW YORK STATE ELECTRIC & GAS CORPORATION
Andover-Palmeter
932
Clyde-State St.
971
Cobble Hill
115/34
Coopers Corners 345/115
#2
Coopers Corners 345/115
#3
Cortland-ETNA
947
East Sayre-No. Waverly
956
E. Towanda-Hillside
70
Elbridge-State St.
972
Farmington-Border City
977
Fraser-Coopers Corners
33
Fraser 345/115
#2
Gardenville 230/115
#6
Gardenville 230/115
#7
Gardenville 230 kV
T8
Gardenville 115 kV
T10&T11
1
Rd. 115/34
Hillside 230/115
#3
Hillside-Watercure
69
Homer City-Stolle Rd
37
2
Homer City-Watercure
30
Hyatt-Border City
979
Lennox-Goudey
952
74
Hamilton
Attachment C
Meyer 230/115
Meyer-Hillside
Niagara-Robinson Road
Oakdale 230/115
Oakdale 345/115
Oakdale 345/115
Oakdale-Fraser
Robinson Road 230/115
Robinson Rd.-Stolle Rd.
Stolle Rd. 345/115
Stolle Rd. 345/115
Stolle Rd.-Gardenville
Stolle Rd.-Meyer
Walden Ave. 115/12
Walden Ave. 115/12
Watercure Rd. 345/230
Watercure-Oakdale
Watercure-Oakdale
W. Woodbourne 115/69
Wood St. 345/115
Wood St. 345/115
#4
68
64
#1
#2
#3
32
#1
3
65
#3
#4
66
67
#1(923)
#2(924)
#1
31
71
#1
#1
#2
ORANGE & ROCKLAND UTILITIES, INC.
Ramapo 345/138
#1300
Ramapo 345/138
#2300
So. Mahwah 345/138
#258
Sugarloaf
11&5108 3
W. Haverstraw 345/138
#194
NEW YORK POWER AUTHORITY
Astoria-E 13th St.
Astoria-E 13th St.
Beck-Niagara
Beck-Niagara
Beck-Niagara
Clay-Edic
Clay-Edic
Fitz-Edic
Fraser-Gilboa
Gilboa-Leeds
Gilboa-New Scotland
Marcy-Coopers Corners
Marcy-Edic
Marcy
Marcy
Massena-Marcy
Moses-Adirondack
Moses-Adirondack
Moses-Massena
Moses-Massena
Moses-Massena
Moses-Willis
Moses-Willis
Attachment C
Q35L
Q35M
PA27
PA301
PA302
1-16
2-15
FE1
GF5-35
GL-3
GNS-1
UCC2-41
UE1-7
765/345 AT1
765/345 AT2
MSU1
1
2
MMS1
2
MMS2
2
MMS1&2
3
MW1
MW2
75
Niagara-Rochester (S80)
NR2
Niagara-Kintigh
NS1-38
Niagara 230/115
#AT1
Niagara 230/115
#AT2
Niagara 345/230
#3
Niagara 345/230
#4
Niagara 345/230
#5
Pannell-Clay
PC-1
Pannell-Clay
PC-2
Plattsburgh-Saranac
1
Kintigh-Rochester
SR1-39
Sta. 80-Pannell
RP-1
Sta. 80-Pannell
RP-2
St. Lawrence (Moses) 230/115
#1
#2
#3
#4
Saunders-Moses
L33P
2
Saunders-Moses
L34P
2
Vermont-Plattsburgh
PV-20
2
Willis-Plattsburgh
WP1
Willis-Plattsburgh
WP2
Willis 230/115
#1
Willis 230/115
#2
ROCHESTER GAS & ELECTRIC CORPORATION
Clyde-Niagara Mo. 115/34
Ginna-Pannell Rd.
912
Mortimer-Sta. 80
904
Pannell Rd. 345/115
#1
Pannell Rd. 345/115
#2
Quaker-Pannell Rd.
914
So. Perry BT Breaker
7X16272
Sta. 80 345/115
#1
Sta. 80 345/115
#2
2
Sta. 80 345/115
#3
2
Station 33-Mortimer
901
Station 82-Mortimer
7X8272
76
Attachment C
Attachment D
PROTECTION DATA LISTS AND FORMS
This attachment includes the following lists and forms:
•
Exhibit D-1: Facilities Requiring Relay Characteristics Reporting
•
Exhibit D-2: Clearing Times and Relay Characteristics Form
•
Exhibit D-3: Relay Characteristics Supplementary Data Submission Form
•
Exhibit D-4: Reclosing Data Forms
•
Exhibit D-5: Power Line Carrier Frequency Data Report
Attahment D
77
Exhibit D-1: Facilities Requiring Relay Characteristics Reporting
“X” in the “REVISED” column indicates a change or addition.
KV
TERMINAL
NAME
NUMBER
115
115
Plattsburgh
Sand Bar
Plattsburgh-Vermont
Plattsburgh-Vermont
PV-20
PV-20
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
Adirondack
Porter
Adirondack
Porter
Beck
Niagara
Beck
Packard
Dunkirk
South Ripley
Dunkirk
Gardenville
Dunkirk
Gardenville
Gardenville
Stolle Road
East Towanda
Hillside
Hillside
Watercure
Gardenville
Huntley
Gardenville
Huntley
Goethals
Linden
Hillside
Meyer
Adirondack
Moses
Adirondack
Moses
Massena
Moses
Massena
Moses
Moses
Plattsburg
Willis
Moses
Plattsburg
Willis
Adirondack-Porter
Adirondack-Porter
Adirondack-Porter
Adirondack-Porter
Beck-Niagara
Beck-Niagara
Beck-Packard
Beck-Packard
Dunkirk-South Ripley
Dunkirk-South Ripley
Gardenville-Dunkirk
Gardenville-Dunkirk
Gardenville-Dunkirk
Gardenville-Dunkirk
Gardenville-Stolle Road
Gardenville-Stolle Road
Hillside-East Towanda
Hillside-East Towanda
Hillside-Watercure
Hillside-Watercure
Huntley-Gardenville
Huntley-Gardenville
Huntley-Gardenville
Huntley-Gardenville
Linden-Goethals
Linden-Goethals
Meyer-Hillside
Meyer-Hillside
Moses-Adirondack
Moses-Adirondack
Moses-Adirondack
Moses-Adirondack
Moses-Massena
Moses-Massena
Moses-Massena
Moses-Massena
Moses-Willis-Plattsburg
11
11
12
12
PA27
PA27
BP76
BP76
68
68
73
73
74
74
66
66
70
70
69
69
79
79
80
80
A2253
A2253
68
68
MA-1
MA-1
MA-2
MA-2
MMS1
MMS1
MMS2
MMS2
MWP1
MWP1
MWP1
MWP2
MWP2
MWP2
78
REVISED
Attachment D
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
230
Niagara
Packard
Niagara
Packard
Niagara
Robinson Road
Huntley
Packard
Huntley
Packard
Porter
Rotterdam
Porter
Rotterdam
Robinson Road
Stolle Road
Bear Swamp
Rotterdam
Erie South
South Ripley
Moses
St.Lawrence TS
Moses
St.Lawrence TS
Meyer
Stolle Road
Oakdale
Watercure
Niagara-Packard
Niagara-Packard
Niagara-Packard
Niagara-Packard
Packard-Huntley
Packard-Huntley
Packard-Huntley
Packard-Huntley
Porter-Rotterdam
Porter-Rotterdam
Porter-Rotterdam
Porter-Rotterdam
Robinson Road-Stolle Road
Robinson Road-Stolle Road
Rotterdam-Bear Swamp
Rotterdam-Bear Swamp
South Ripley-Erie South
South Ripley-Erie South
St.Lawrence TS-Moses
Stolle Road-Meyer
Stolle Road-Meyer
Watercure-Oakdale
Watercure-Oakdale
61
61
62
62
64
64
77
77
78
78
30
30
31
31
65
65
E205W
E205W
69
69
L33P
L33P
L34P
L34P
67
67
71
71
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
Alps
Berkshire
Beck
Niagara
Beck
Niagara
Buchanan
Eastview
Buchanan
Millwood West
Buchanan
Millwood West
Clay
DeWitt
Clay
Edic
Clay
Edic
Coopers Corners
Rock Tavern
Coopers Corners
Rock Tavern
Alps-Berkshire
Alps-Berkshire
Beck-Niagara
Beck-Niagara
Beck-Niagara
Beck-Niagara
Buchanan-Eastview
Buchanan-Eastview
Buchanan-Millwood West
Clay-DeWitt
Clay-DeWitt
Clay-Edic
Clay-Edic
Clay-Edic
Clay-Edic
Coopers Corners-Rock Tavern
393
393
301
301
302
302
W93
W93
W97
W97
W98
W98
13
13
1-16
1-16
2-15
2-15
34
34
42
42
Attahment D
79
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
Dunwoodie
Pleasantville
Dunwoodie
Pleasantville
Dunwoodie
Rainey
Dunwoodie
Rainey
Dunwoodie
Shore Road
East 13 Street
Farragut
East 13 Street
Farragut
East 13 Street
Farragut
East 13 Street
Farragut
East 13 Street
Poletti
East 13 Street
Poletti
East Fishkill
Wood Street
East Fishkill
Wood Street
Eastview
Sprainbrook
Eastview
Sprainbrook
Eastview
Sprainbrook
Eastview
Sprainbrook
Edic
Fraser
Edic
Marcy
Edic
Marcy
Edic
New Scotland
Farragut
Gowanus
Farragut
Gowanus
Edic
Fitzpatrick
Fitzpatrick
Scriba
Coopers Corners
80
Dunwoodie-Rainey
Dunwoodie-Rainey
Dunwoodie-Rainey
Dunwoodie-Rainey
East 13 Street-Farragut
East 13 Street-Poletti
East Fishkill-Wood Street
Edic-Fraser
Edic-Fraser
Edic-Marcy
Edic-Marcy
Edic-Marcy
Edic-Marcy
Edic-New Scotland
Edic-New Scotland
Farragut-Gowanus
Farragut-Gowanus
Farragut-Gowanus
Farragut-Gowanus
Fitzpatrick-Edic
Fitzpatrick-Edic
Fitzpatrick-Scriba
Fitzpatrick-Scriba
W89
W89
W90
W90
71
71
72
72
Y50
Y50
45
45
46
46
47
47
48
48
Q35L
Q35L
Q35M
Q35M
F38
F38
F39
F39
W64
W64
W65
W65
W78
W78
W79
W79
40/
40/
UE1-7
UE1-7
UE2-5
UE2-5
14
14
41
41
42
42
FE-1
FE-1
FS-10
FS-10
33
Attachment D
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
Fraser
Fraser
Gilboa
Gilboa
Leeds
Gilboa
New Scotland
Fresh Kills
Goethals
Fresh Kills
Goethals
Goethals
Linden Cogeb
Goethals
Gowanus
Goethals
Gowanus
Farragut
Hudson
Farragut
Hudson
Hurley Ave.
Roseton
Buchanan
Indian Point 2
Buchanan South
Indian Point 3
Bowline 2
Ladentown
Buchanan South
Ladentown
Bowline 1
Ladentown
W Haverstraw
DeWitt
Lafayette
Lafayette
Oakdale
Hurley Ave.
Leeds
Leeds
Pleasant Valley
Leeds
Pleasant Valley
Coopers Corners
Marcy
Marcy
New Scotland
Eastview
Millwood West
Eastview
33
Fraser-Gilboa
GF5-35
Fraser-Gilboa
GF5-35
Gilboa-Leeds
GL3
Gilboa-Leeds
GL3
Gilboa-New Scotland
GNS1
Gilboa-New Scotland
GNS1
Goethals-Fresh Kills
21
21
22
22
Goethals-Linden Cogen
G23
Goethals-Linden Cogen
G23
Gowanus-Goethals
25
Gowanus-Goethals
25
Gowanus-Goethals
26
Gowanus-Goethals
26
Hudson-Farragut
B3402
Hudson-Farragut
B3402
Hudson-Farragut
C3403
Hudson-Farragut
C3403
Hurley Ave.-Roseton
303
Hurley Ave.-Roseton
303
Indian Point 2-Buchanan
W95
Indian Point 2-Buchanan
W95
Indian Point 3-Buchanan South
W96
Indian Point 3-Buchanan South
W96
Ladentown-Bowline 2
68
Ladentown-Bowline 2
68
Ladentown-Buchanan South
Y88
Ladentown-Buchanan South
Y88
Ladentown-W Haverstraw-Bowline 1 67/671
Lafayette-DeWitt
22
Lafayette-DeWitt
22
Lafayette-Oakdale
4/36
Lafayette-Oakdale
4/36
Leeds-Hurley Ave.
301
Leeds-Hurley Ave.
301
91
91
92
92
41
41
Marcy-New Scotland
UNS18
Marcy-New Scotland
UNS18
Millwood West-Eastview
W82
W82
W85
Attahment D
81
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
Millwood West
Eastview
Millwood West
Alps
New Scotland
Leeds
New Scotland
Leeds
New Scotland
Niagara
Rochester(St80)
Niagara
Somerset
Nine Mile Point 1
Scriba
Clay
Nine Mile Point
Fraser
Oakdale
Elbridge
Lafayette
Oswego
Oswego
Volney
Oswego
Volney
Clay
Pannell Road
Clay
Pannell Road
East Fishkill
Pleasant Valley
East Fishkill
Pleasant Valley
Long Mountain
Pleasant Valley
Pleasant Valley
Wood St.
Pleasant Valley
Wood St.
Dunwoodie
Pleasantville
Dunwoodie
Pleasantville
Farragut
Rainey
Farragut
Rainey
Farragut
Rainey
Rainey
82
New Scotland-Alps
New Scotland-Alps
New Scotland-Leeds
New Scotland-Leeds
New Scotland-Leeds
New Scotland-Leeds
Niagara-Rochester(St80)
Niagara-Rochester(St80)
Niagara-Somerset
Niagara-Somerset
Nine Mile Point 1-Scriba
Nine Mile Point 1-Scriba
Nine Mile Point-Clay
Nine Mile Point-Clay
Oakdale-Fraser
Oakdale-Fraser
Oswego-Elbridge-Lafayette
Oswego-Volney
Oswego-Volney
Oswego-Volney
Oswego-Volney
Pannell Road-Clay
Pannell Road-Clay
Pannell Road-Clay
Pannell Road-Clay
Pleasant Valley-East Fishkill
Pleasant Valley-Long Mountain
Pleasant Valley-Long Mountain
Pleasantville-Dunwoodie
Rainey-Farragut
Rainey-Farragut
Rainey-Farragut
Rainey-Farragut
Rainey-Farragut
Rainey-Farragut
Rainey-Ravenswood 3
W85
W99
W99
2
2
93
93
94
94
NR2
NR2
NS1/38
NS1/38
9
9
8
8
32
32
17
17
17
11
11
12
12
PC1
PC1
PC2
PC2
F36
F36
F37
F37
398
398
F30
F30
F31
F31
W89
W89
W90
W90
61
61
62
62
63
63
60L
Attachment D
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
345
Ravenswood 3
Rainey
Ravenswood 3
Buchanan North
Ramapo
Ladentown
Ramapo
Ramapo
South Mahwah
Ramapo
South Mahwah
Alps
Reynolds
Pannell Road
Rochester(St80)
Pannell Road
Rochester(St80)
Ramapo
Rock Tavern
East Fishkill
Roseton
Rock Tavern
Roseton
Scriba
Volney
Scriba
Volney
Rochester(St80)
Somerset
South Mahwah
Waldwick
South Mahwah
Waldwick
Dunwoodie
Sprainbrook
East Garden City
Sprainbrook
West 49 Street
West 49 Street
Sprainbrook
Sprainbrook
Homer City
Stolle Road
Clay
Volney
Marcy
Volney
Homer City
Watercure
Oakdale
Watercure
Rainey-Ravenswood 3
Rainey-Ravenswood 3
Rainey-Ravenswood 3
Ramapo-Buchanan North
Ramapo-Buchanan North
Ramapo-Ladentown
Ramapo-Ladentown
Ramapo-South Mahwah
Ramapo-South Mahwah
Ramapo-South Mahwah
Ramapo-South Mahwah
Reynolds-Alps
Reynolds-Alps
Rochester(St80)-Pannell Road
Rock Tavern-Ramapo
Rock Tavern-Ramapo
Roseton-East Fishkill
Roseton-East Fishkill
Roseton-Rock Tavern
Roseton-Rock Tavern
Scriba-Volney
Scriba-Volney
Scriba-Volney
Scriba-Volney
Somerset-Rochester(St80)
Somerset-Rochester(St80)
South Mahwah-Waldwick
Sprainbrook-East Garden City
Sprainbrook-East Garden City
Sprainbrook-West 49 Street
Sprainbrook-West 49 Street
Sprainbrook-West 49th St.
Sprainbrook-West 49th St.
Stolle Road-Homer City
Stolle Road-Homer City
Volney-Clay
Volney-Clay
Volney-Marcy
Volney-Marcy
Watercure-Homer City
Watercure-Homer City
Watercure-Oakdale
Watercure-Oakdale
Attahment D
60L
60M
60M
Y94
Y94
W72
W72
69/J3410
69/J3410
70/J3411
70/J3411
1
1
RP1
RP1
RP2
RP2
77
77
305
305
311
311
20
20
21
21
SR1/39
SR1/39
J3410
J3410
K3411
K3411
W75 L&M
W75 L&M
Y49
Y49
M51
M52
M51
M52
37
37
6
6
VU19
VU19
30
30
31
31
83
345
345
345
345
345
345
345
345
East 13 Street
West 49 Street
East 13 Street
West 49 Street
Millwood West
Wood St.
Millwood West
Wood St.
West 49 Street-East 13 Street
Wood St.-Millwood West
M54
M54
M55
M55
W80
W80
W81
W81
500
500
Branchburg
Ramapo
Branchburg-Ramapo
Branchburg-Ramapo
5018
5018
765
765
765
765
Chateauguay
Massena
Marcy
Massena
Massena-Chateauguay
Massena-Chateauguay
Massena-Marcy
Massena-Marcy
MSC7040
MSC7040
MSU-1
MSU-1
84
Attachment D
Exhibit D-2: Clearing Times and Relay Characteristics Form
Line No.
__________
Line Name
______________________________
Terminal
______________________________
Base Voltage
______________________________
Clearing Times Viewed from this Terminal
Near End Fault (in cycles)
___________
Far End Fault (in cycles)
___________
Protection
System 1
Protection
System 2
Type of Relay Scheme
(See abbreviations in VI.)
CT Ratio
___________
___________
___________
___________
PT Ratio
___________
___________
Which Zone initiates
Pilot Scheme?
___________
___________
Mark an "X" if data is
furnished on attached
supplementary form rather
than this form
___________
___________
Attahment D
85
Relay Characteristics (continued)
Protection
System 1
Protection
System 2
Zone 1
Angle of Max Torque
___________
(Enter 0 for reactance relay)
___________
Setting in Sec. Ohms
___________
___________
Offset in Sec. Ohms
___________
___________
Zone Time Delay (Cycles)
___________
___________
Setting in pri per unit
(100 MVA base)
___________
___________
Zone 2
Angle of Max Torque
___________
___________
___________
___________
Offset in Sec. Ohms
___________
___________
___________
___________
(100 MVA base)
___________
___________
Zone 3
Angle of Max Torque
___________
___________
___________
___________
Offset in Sec. Ohms
___________
___________
___________
___________
(100 MVA base)
___________
___________
Submitted by ____________________
86
Date ________________
Attachment D
Exhibit D-3: Relay Characteristics Supplementary Data Submission Form
Line No.
__________
Line Name
_________________________
Protection
Protection
System 1
System 2
Information is furnished
for (check one)
__________
__________
Submitted by______________________
Date_____________
______________
Attahment D
87
Exhibit D-4: Reclosing Data Forms
Line Number
Line Name
Terminal
NO
HIGH SPEED RECLOSING*
YES
IF YES,
BREAKER
RECLOSING TIME*
____ ____________ (s)
(cyc)
DELAYED RECLOSING*
FIRST SHOT - Hot bus dead line
(s)
If there is no hot bus dead line reclosing
at this end, i.e., reclosing is by
sync check only, or not at all, Check NO
SECOND SHOT - Hot bus dead line
(s)
If there is no second shot, check NO
THIRD SHOT - Hot bus dead line
(s)
If there is no third shot, check NO
Information from
______________________
Date
______________________
* Definitions of these terms are in the NPCC Bulk Power System Reclosing Guide.
88
Attachment D
Exhibit D-5: PLC Frequency Data Report
Attahment D
89
Attachment E
NYISO RTSA DATA BASE
This attachment contains the following exhibits:
90
•
Exhibit E-1: RTSA Data Base Forms
•
Exhibit E-2: RTSA Pointer File Specification
•
Exhibit E-3: NYISO Real-Time Data Base Change Request Form.
Attachment E
Exhibit E-1: RTSA Data Base Forms
Attachment E
91
Station Voltage Level Data
STANAME
STAKV
ASTORIA E
138
STATIONABB
BUSVDESR
ASTORIAE
BUSKV
BUSNUM
138
BUSAREA
55
BUSVMIN
143.52
1
BUSVMAX
0.85
LD31ZONE
1.15
15
AREANAME
SUBZONENAME
CE
CENY
ZONE_11NAME
BUSBB
1
BUSPTID
BUSPTID2
30165
0
N
VOLTPTID
VOLTNODE
11679
4
RTSAMODEL
MNTR - SCUC
Yes
EDCMODEL
EDCAREA
2
BUSVOLT
BUSANG
1.0081
-42.29
LOADMW__SU
N
ABBMODEL
Yes
Yes
MNTR - SA
N.Y.C.
BUSTYPE
MNTR - VTL
310
115
SHNTMW__SU
N
2
LOADMV__SU
SHNTMV__SU
0
0
BUSMXCS
BUSVCNTR
0
0
BUSVOLTCS
1
BUSVLIMS
0
STNID
1210
STNDIAG
1870
Generation Data
STANAME
STAKV
ARTHUR KILL
20
STATIONABB
BUSKV
FRESHKLS
GENMW
200
GENPMIN
0
1.03
5
GENCBUS
GENCNODE
51
5
23512
MGF
GENMVPTID
1
776
CE
GNAMEABB
UNIT_ID
AK 2
1
-55
6
26
ARTHR KL 2
343
FUELCODE
GENMWPTID
AREANAME
GENQMINL
20.6
GENPTID
GENNAME
GENPMAX
7
vskv
GENNODE
51
20
GENMV
VSPU
GENBUS
GENQMAXL
ABBMODEL
Yes
Yes
EDCMODEL
SCUCMODEL
Yes
Yes
1
GENQMINH
115
GENQMAXH
-55
115
OPTYPE
COSTCLASS
OPERATION
F
FIXED GEN
FIXED GEN
CNTGY - DFAX
T
CNTGY - SA
GENNOTF
GENNORM
B
C
GENSTAT
Y
COSTCURVE
0
GENMVA
1
CNTGY - SCUC
RTSAMODEL
GENOWNR
N
CNTGY - VTL
ZONEWTFCTR
N
SVC SLOPE / MVPFACT
0.00783
MWPFACT
5
GENCNFRM
T
1
GENCNTLS
GENTYPE
1
3
Transformer Data
STANAME
STAKV
ASTORIA 3
138
STATIONABB
XFRFBUS
ASTORIA3
59
XFRR
XFRCNTBUS
0.0644
20
XFRTBUS
2
0
AREANAME
BK 3N
CE
XFRTNODE
63
XFRB
XFRNAME
XFRCKT
3
XFRFT
0
XFRTYPE
1
XFRRATA
2
XFRRATB
2
XFRFA
0
XFRTAPPTID
XFRBBADD
XFRBULK
0
0
0
XFRTT
XFRTA
1.03
0
1
0
XFRRG
XFRDES
0
N
XFRNOTF
1.01
TAPMINPOS
C
XFRTMIN
1
XFRFMV
0
XFRTMW
1
XFRRATC
0
70124
XFRFMW
XFROWNR
XFRCNTNODE
59
XFRPTID
XFRFNODE
XFRG
BUSKV
20
138
XFRX
0.00182
STAKV
BUSKV
CNTGY-DFAX
MNTR - DFAX
0
XFRTMV
0
0
RTSAMODEL
ABBMODEL
Yes
Yes
XFRDSTEP
0.0078
F
CNTGY - SA
MNTR - SA
N
N
CNTGY - SCUC
MNTR - SCUC
N
N
CNTGY - VTL
MNTR - VTL
N
N
xfrhitapneutral
33
taphiset
17
xfrmtrnode
xfrlostakv
0
20
taploset
0
0
0.78
0
XFRNORM
C
138
xfrlotapneutral
17
Yes
20
1.157
xfrlodstep
ZONETIE
xfrhistakv
XFRTMAX
xfrhidstep
EDCMODEL
xfrmtrstakv
0.909
TAPMAXPOS
xfrhinode
2
xfrlonode
3
xfrltc
H
XFRCNTLS
XFRCNTSS
0
0
Transmission Line
STANAME
STATIONABB
STAKV
ASTORIA E
ASTORIAE
138
BUSKV
138
LFBUS
LFNODE
LTBUS
LTNODE
55
9
76
4
LINER
LINEX
0.00159
LNPTID
STAKV
CORONA
CORONA
138A
LNNAME
LINCKT
34186
6
25282
LNBULK
0.22
CNTY-DFAX
LINFMV
4296
LINTMV
6796
138
LNOWNR
1
LNNOTF
LNNORM
C
C
9296
MNTR - DFAX
T
CNTGY - SA
MNTR - SA
Y
Y
CNTY-SCUC
MNTR - SCUC
N
Y
RTSAMODEL
ABBMODEL
CNTGY - VTL
MNTR - VTL
Yes
Yes
N
N
EDCMODEL
Yes
BUSKV
LNBBADD
1796
LINTMW
STATIONABB
LINBTOT
0.00688
25282
LINFMW
STANAME
LINRATA
LINRATB
154
linnormlim
LINRATC
239
linltelim
387
linstelim
190727
193227
ZONETIE
TIELINEFLA
0
195727
LINSTAT
1
Load Data
STANAME
STATIONABB
STAKV
ASTORIA E
ASTORIAE
138
LOADBUS
LOADNODE
55
5
LOADMW
138
LOADNAME
LOADOWNR
N.QUEENS
1
LOADMV
310
BUSKV
115
LOADDFAX
LOADCNFRM
LOADNOTF
LOADNORM
F
T
B
C
LOADSCDP
LOADEDCAR
LOADCS
0
0
0
RTSAMODEL
ABBMODEL
Yes
Yes
SCUCMODEL
Yes
LOADPTID
80522
LOADMWPTID
0
LOADMVPTID
0
Shunt Data
STANAME
STATIONABB
STAKV
E.FISHKIL CE
EFISHKIL
345
SHNTBUS
SHNTNODE
108
16
SHNTMW
SHNTNAME
345
CAP #2
1
SHNTPTID
31335
SHNTNOTF
SHNTNORM
SHNTFLG
B
O
Y
SHNTDESV
135
354
SHNTQ
0
SHNTOWNR
SHNTMV
0
SHNTP
BUSKV
1.35
RTSAMODEL
ABBMODEL
Yes
Yes
vskv -generator
0
Switch Data
STANAME
STATIONABB
STAKV
ASTORIA E
ASTORIAE
138
BUSKV
SWOWNR
138
1
AREANAME
SWBUS
SWFNODE
55
SWTNODE
4
12
CE
SWPTID
SWNAME
14755
F6E
ABBMODEL
RTSAMODEL
SWNORM
SWSCHED
SWMONF
SWNOTF
Yes
Yes
C
CL
1
B
NYPP RATINGS UPDATE
LINE ID
305
MLF
CO
LINE NAME (no leading spaces in name)
K.V.
P.F.
UPDATE
CH
ROSETON-E.FISHKILL
345
100
11/02/92
PTID
272
COMMENT
25108
WIN NOR
CD
LIMITATION
SUM NOR
CD
LIMITATION
2527
G
CT
1935
G
CT
WIN LTE
CD
LIMITATION
SUM LTE
CD
LIMITATION
2958
G
CT
2742
G
CT
WIN STE
CD
LIMITATION
SUM STE
CD
LIMITATION
3137
G
CT
3137
G
CT
MAKE CURRENT RECORD HISTORICAL & CREATE
NEW RECORD
codedescription
INFO CODE
Exhibit E-2: RTSA Pointer File Specification
92
Attachment E
On-Line RTSA Pointer File Specification -con't
1. Switch pointer and device name data
Header: POINTER SWITCH DATA FOLLOW
Data record contains: Bus ID,FROM section, TO section, SCADA status pointer,
switch name, Company ID
Data format is: (A12,A8,I4,I4,I6,A10,A2,I1,30X,A1,A1)
Item
Bus ID
Section numbers
Status pointer ID
Switch name
Company ID
Monitored?
Notification Option
Columns
1:20
21:24;25:28
29:34
35:44
45:46
47
78
Variable
Normal Status
79
SWSTAN
Trailer: END OF POINTER SWITCH DATA
SWPTID
SWNAME
SWOWNR
SWMONT
SWNOTFY
Restrictions/Comments
Must be valid
Must be valid
Will override SWSCDA
New data
New data
New data (1/0 -> YES/NO)
New data ( Pre-Confirm Out Sched
A -> Y
Y
B -> Y
N
C -> N
Y
D -> N
N)
Override SWSTAN Open/Close
2. Transmission Line pointer and device name data
Header: POINTER TRANSMISSION LINE DATA FOLLOW
Data record contains: FROM section ID,TO section ID, SCADA status pointer,
transmission line name, Company ID, Normal Status
Data format is: (2(A12,A8,I4),I6,A10,A2,I7,I1,3X,A1,A1)
Item
FROM section ID
TO Section ID
Status pointer ID
Line name
Company ID
Big Board Address
Bulk Syst. Def.
Notification Option
Columns
1:24
25:48
49:54
55:64
65:66
67:73
74
78
Variable
Normal Status
79
LNSTAN
LNPTID
LNNAME
LNOWNR
LNBBADD
LNBULK
LNNOTFY
Trailer: END OF POINTER TRANSMISSION LINE DATA
Must be valid
Must be valid
New data
New data
New data
New data
New data
A -> Y
Y
B -> Y
N
C -> N
Y
D -> N
N)
New Data Open/Close
3. Transformer pointer and device name data
Header: POINTER TRANSFORMER DATA FOLLOW
Data record contains: FROM section ID,TO section ID, SCADA status pointer,
transformer name, Company ID, tap position pointer,
Normal Status
Data format is: (2(A12,A8,I3),I6,A10,A2,I5,I2,I5,I1,A1,A1)
Item
FROM section ID
TO Section ID
Status pointer ID
Transformer name
Company ID
XF Tap position ID
XF Tap Class ID
Big Board Address
Bulk Syst. Def.
Notification Option
Columns
1:23
25:46
47:52
53:62
63:64
65:69
70:71
72:76
77
78
Variable
Normal Status
79
XFSTAN
XFPTID
XFNAME
XFOWNR
XFTPTID
XFTPCLS
XFBBADD
XFBULK
XFNOTFY
Trailer: END OF POINTER TRANSFORMER DATA
Must be valid
Must be valid
New data
New data
New data
Override XFSCDA
New data
New data
New data
A -> Y
Y
B -> Y
N
C -> N
Y
D -> N
N
G -> Y
N)
New data Open/Close
4. Fixed Shunt pointer and device name data
Header: POINTER FIXED SHUNT DATA FOLLOW
Data record contains: Section ID, SCADA status pointer, fixed shunt name,
Company ID, Normal Status
Data format is: (A12,A8,I4,I6,A10,A2,35X,A1,A1)
Item
Section ID
Status pointer ID
Fixed Shunt name
Company ID
Notification Option
Columns
1:24
25:30
31:40
41:42
78
Variable
Normal Status
79
SHSTAN
SHPTID
SHNAME
SHOWNR
SHNOTFY
Trailer: END OF POINTER FIXED SHUNT DATA
Must be valid
New data
New data
New data
A -> Y
Y
B -> Y
N
C -> N
Y
D -> N
N)
New data Open/Close
5. DC Line pointer and device name data
Header: POINTER DC LINE DATA FOLLOW
Data record contains: FROM section ID,TO section ID, SCADA status
pointer, DC Line name, Company ID,Normal Status
Data format is: (2(A12,A8,I4),I6,A10,A2,I5,I1,5X,A1,A1)
Item
FROM section ID
TO Section ID
Status pointer ID
DC Line name
Company ID
Big Board Address
Bulk System
Notification Option
Columns
1:24
25:48
49:54
55:64
65:66
67:71
72
78
Variable
Normal Status
79
DCSTAN
Trailer: END OF POINTER DC LINE DATA
DCPTID
DCNAME
DCOWNR
DCBBADD
DCBULK
DCNOTFY
Must be valid
Must be valid
New data
New data
New data
New data
New data
A -> Y
Y
B -> Y
N
C -> N
Y
D -> N
N)
New data Open/Close
6. Generator pointer and device name data
Header: POINTER GENERATOR DATA FOLLOW
Data record contains: Section ID, SCADA status pointer, generator name, Company ID,
Data format is: (A12,A8,I4,I6,A10,A2,I6,29X,A1,A1)
Item
Section ID
Status pointer ID
Generator name
Company ID
Generator type ID
Generator DFAX Monitor
Notification Option
Columns
1:24
25:30
31:40
41:42
43:48
50
78
GNPTID
GNNAME
GNOWNR
GNTYID
GNMON
GNNOTFY
Normal Status
79
GNSTAN
Trailer: END OF POINTER GENERATOR DATA
Variable
Must be valid
New data
New data
New data
Overrides GNSCDA
New data (.T. or .F.)
A -> Y
Y
B -> Y
N
C -> N
Y
D -> N
N)
New data Open/Close
Generator type pointer,
7. Switched Shunt pointer and device name data
Header: POINTER SWITCHED SHUNT DATA FOLLOW
Data record contains:Section ID, SCADA status pointer, switched shunt name,
Company ID, Initial Q pointer, Normal Status
Data format is: (A12,A8,I4,I6,A10,A2,I6,29X,A1,A1)
Item
Section ID
Status pointer ID
Switched Shunt name
Company ID
Initial Q Ptr ID
Notification Option
Columns
1:24
25:30
31:40
41:42
43:48
78
Normal Status
79
Variable
Must be valid
SSPTID
New data
SSNAME
New data
SSOWNR
New data
SSQID Overrides SSSCDA
SSNOTFY
A -> Y
Y
B -> Y
N
C -> N
Y
D -> N
N)
SSSTAN
New data Open/Close
Trailer: END OF POINTER SWITCHED SHUNT DATA
8. Static VAR Compensator pointer and device name data
Header: POINTER SVC DATA FOLLOW
Data record contains: Section ID, SCADA status pointer, SVC name, Company ID,
Item
Section ID
Status pointer ID
SVC name
Company ID
Notification Option
Columns
1:24
25:30
31:40
41:42
78
Variable
Normal Status
79
SVSTAN
Trailer: END OF POINTER SVC DATA
SVPTID
SVNAME
SVOWNR
SVNOTFY
Must be valid
New data
New data
New data
A -> Y
Y
B -> Y
N
C -> N
Y
D -> N
N)
New data Open/Close
Normal Status
9. Load pointer and device name data
Header: POINTER LOAD DATA FOLLOW
Data record contains: Section ID, SCADA status pointer, Load name, Company ID
Item
Section ID
Status pointer ID
Load name
Company ID
Load DFAX Monitored
Load EDC Area
Load SCD MW
Notification Option
Columns
1:24
25:30
31:40
41:42
44
46:47
48:57
78
LOPTID
LONAME
LOOWNR
LOMON
LOEDCAR
LOSCDP
LONOTFY
Normal Status
79
LOSTAN
Trailer: END OF POINTER LOAD DATA
Variable
Must be valid
New data
New data
New data
New data (.T. or .F.)
New data
New data
A -> Y
Y
B -> Y
N
C -> N
Y
D -> N
N)
New data Open/Close
10. Meter pointer and parameter data
Header: POINTER METER DATA FOLLOW
Data record contains: Bus ID, Section IDs, Meter type, Full scale value,
SCADA pointer, Meter class
Data format is: (A12,A8,I4,I4,I2,F10.0,I6,I4)
Item
Bus ID
Section IDs (FM,TO)
Meter type
Full scale value
SCADA pointer
Meter class
Columns
1:20
21:24;25:28
29:30
31:40
41:46
47:50
Trailer: END OF POINTER METER DATA
Variable
MTPTTY
MTPTFS
MTPTID
MTPTMC
Must be valid
Must be valid
Overrides MTTYPE
Overrides MTFS
Overrides MTSCDA
Overrides MTCLAS
11. Bus Pointer Data
Header: POINTER BUS DATA FOLLOW
Data record contains: Bus ID, Big Board Representation, One Line Diagram Number, Status Pointer
Data format is: (A12,A8,1X,I1,1X,I5,I5,I6)
Item
Bus ID
B.B. Rep
BB Station Address
Station 1Line #
Status Pointer
Columns
1:20
22
24:28
30:34
35:40
Trailer: END OF POINTER BUS DATA
Variable
BUSBB
STNID
STNDIAG
BUSPTID
Must be valid
=1 -> If bus is on Big
12. Tap Position Class Pointer Data
Header: POINTER TAP POSITION CLASS DATA FOLLOW
Data record contains: Class ID, Min Position, Max Position
Data format is: (I2,1X,I4,1X,I4)
Item
Class ID
Min Position #
Max Position #
Columns
1:2
4:7
9:12
Variable
TPCLSMIN
TPCLSMAX
Trailer: END OF POINTER TAP POSITION CLASS DATA
13. Relay Pointer Data
Header: POINTER RELAY DATA FOLLOW
Data record contains: Section ID, SCADA status pointer, Load name, Company ID
Data format is: (A12,A8,I4,A17,2(F10.2)
Item
Section ID
Relay Name
Minimum Condition
Maximum Condition
Columns
1:24
25:41
42:51
52:61
Trailer: END OF POINTER RELAY DATA
Variable
Must be valid
RLNAME
Overrides RLMIN of Static
Overrides RLMAX of Static
Exhibit E-3: NYISO Real-Time Data Base Change Request Form.
Attachment E
93
NYCA REAL-TIME DATA BASE CHANGE REQUEST
Submitted by: ___________________
Date: _______________
Change Codes: (M)odify, (A)dd, or (D)elete
Device Codes: LN - Line
GN - Generator
SH - Cap/Reactor
SW - Disconnect/Switch/Breaker XF - Transformer LO - Load
SV - SVC
CODES
Chg
Dev
FROM
Station
TO
Station
kV
DEVICE
NAME
PTID
ASSOCIATED
DISC/SW/BKR
Database Change Control
NYISO Dept. Notifications
ADB Admin: _____________________
Security Analy: ___________________ Dispatcher: ______________
Coord: ____________________ DTS: ________________
94
DB Chg #: ____________________
Adv Appl Chg # __________
AA Chgd by: ___________ EDC Chgd by: ______ Outage
AA Chg Date: ___________ EDC Chg. Date: _______
Attachment E

System Analysis Data Manual

Transcription

Similar documents

connection

Control Center Requirements Manual March 2014

PDF - The Maxwell

to and print - LIGHTS OUT by Ted Koppel

Rocker Bank Air Eliminator Head for the Air Eliminator Model T2A

ACANTHUS TOWEL RING | 3430

Hajoca Corporation

2-line bar with safety leash instructions

September 4, 2016 Sunday Bulletin

Week of April 12, 2015 - Bethesda Church Of God