Professional Documents
Culture Documents
ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
BAL-001-0
R1
Each Balancing Authority shall operate such that, on a rolling 12-month basis, the C8 Sec. 2.1 average of the clock-minute averages of the Balancing Authoritys Area Control Error (ACE) divided by 10B (B is the clock-minute average of the Balancing Authority Areas Frequency Bias) times the corresponding clock-minute averages of the Interconnections Frequency Error is less than a specific limit. This limit 1 2 is a constant derived from a targeted frequency bound (separately calculated for each Interconnection) that is reviewed and set as necessary by the NERC Operating Committee. The equation for ACE is: ACE = (NIA NIS) 10B (FA FS) IME (this section continues with other formulae and data specs).
The criteria to be used in monitoring the Control Performance of an individual Area or system require that: Control Performance Standard 1 (CPS1) over a given period, the average of the clock-minute averages of an Areas ACE divided by 10 times its bias multiplied by the corresponding clock-minute averages of frequency error shall be less than the targeted frequency bound established by NERC. This is expressed in the following equation: (the ensuing NPCC requirements match those required by NERC in their R1 section). 2.2 The criteria above will be deemed satisfactory if the rolling 12 month average compliance with CPS1 is not less than 100%. The NPCC objective is that these minimum Performance Standards, as established by NERC, will be met or exceeded.
No
TFCO
BAL-001-0
R2
Each Balancing Authority shall operate such that its average ACE for at least 90% of C8 Sec. 2.1 & clock ten- minute periods (6 non-overlapping periods per hour) during a calendar month 2.2 is within a specific limit, referred to as L10. It is the targeted root-mean-square (RMS) value of ten-minute average Frequency Error based on frequency performance over a given year. The bound, 10, is the same for every Balancing Authority Area within an Interconnection, and Bs is the sum of the Frequency Bias Settings of the Balancing Authority Areas in the respective Interconnection. For Balancing Authority Areas with variable bias, this is equal to the sum of the minimum Frequency Bias Settings. (this section continues with other formulae and data specs).
2.1 - Control Performance Standard 2 (CPS2) - The average ACE for each of the six 10-minute periods in an No hour must be within that Areas Allowable Limit of the Average Deviation (L10). (NPCC formulae and definitions which follow this agree with those of NERC). 2.2 The criteria above will be deemed satisfactory if the monthly compliance with CPS2 is not less than 90%. The NPCC objective is that these minimum Performance Standards, as established by NERC, will be met or exceeded.
No
TFCO
BAL-001-0
R3
Each BA providing Overlap Regulation Service shall evaluate Requirement R1 (CPS1) and Requirement R2 (CPS2) using the characteristics of the combined ACE and combined Frequency Bias Settings. Each BA providing Overlap Regulation Service shall evaluate Requirement R1 (CPS1) and Requirement R2 (CPS2) using the characteristics of the combined ACE and combined Frequency Bias Settings.
A6 Sec. 3.3
3.3 The reserve on Automatic Generation Control in each Area shall be sufficient to meet NERC control performance standards CPS1 and CPS2.
No
No
TFCO
BAL-001-0
R3
C8 Sec. 3.0
3.0 - Within 10 days after the end of each month, each Area representative will forward CPS1 and CPS2 compliance percentages to the NPCC Control Performance Working Group (CPWG). Within 20 days after the end of each month, the CPWG will forward the CPS1 and CPS2 compliance percentages to the NERC office for review by the NERC Performance Subcommittee. Within 20 days after the end of each month, the CPWG will prepare a running annual summary of the monthly compliance percentages for review by the NPCC TFCO. The TFCO will report annually, or more as required, to the RCC on the frequency of failures to achieve satisfactory control performance.
No
TFCO
BAL-001-0
R4
Any Balancing Authority receiving Overlap Regulation Service shall not have its control none performance evaluated (i.e. from a control performance perspective, the Balancing Authority has shifted all control requirements to the Balancing Authority providing Overlap Regulation Service). Each Balancing Authority shall have access to and/or operate Contingency Reserve to respond to Disturbances. Contingency Reserve may be supplied from generation, controllable load resources, or coordinated adjustments to Interchange Schedules. A6 Sec. 1.0
None
Yes
No
TFCO
BAL-002-0
R1
In the continuous operation of electric power systems, operating capacity is required to meet forecast load, No including an allowance for error, to provide protection against equipment failure which has a reasonably high probability of occurrence, and to provide adequate regulation of frequency and tie line power flow. The operating capacity in excess of that required for actual load is commonly referred to as operating reserve. This document establishes standard terminology and minimum requirements governing the amount, availability, distribution and shared activation of operating reserve. The objective is to ensure a high level of reliability in the NPCC Region that is, as a minimum, consistent with the Operating Policies and Standards specified by North American Electric Reliability Council (NERC).
Yes
TFCO
BAL-002-0
R1.1
A Balancing Authority may elect to fulfill its Contingency Reserve obligations by participating as a member of a Reserve Sharing Group. In such cases, the Reserve Sharing Group shall have the same responsibilities and obligations as each Balancing Authority with respect to monitoring and meeting the requirements of Standard BAL002.
A6 Sec. 3.8
3.8 - When an Area acquires operating reserve from another Area, the provider of the operating reserve shall No deliver an increase in energy equal to the amount of operating reserve acquired when the acquiring Area requests its activation. Unless the provider experiences its own contingency, the provider shall not initiate the curtailment of an existing or planned energy sale to any Area to support the activation of the operating reserve that was acquired until the contingent Area has recovered from the contingency. Under normal conditions, the recovery time of the contingent Area should not exceed the DCS requirement. Operating reserve acquired from another Area shall be sustainable as specified in section 3.7 above (1 hour).
Yes
TFCO
BAL-002-0
R1.1
A Balancing Authority may elect to fulfill its Contingency Reserve obligations by participating as a member of a Reserve Sharing Group. In such cases, the Reserve Sharing Group shall have the same responsibilities and obligations as each Balancing Authority with respect to monitoring and meeting the requirements of Standard BAL002. Each RRO, sub-Regional Reliability Organization or Reserve Sharing Group shall specify its Contingency Reserve policies, including (see R2.1, etc. below):
3.0 The NPCC Operating Reserve Criteria (A-06) and the Operating Reserve Criteria of all NPCC Areas and of PJM Members are not changed by any of the provisions of this Shared Activation of Ten Minute Reserve policy. Each Area maintains the ability to recover from its own loss of generationby deploying 10 minute reserve within fifteen minutes. Refer to R2.1, R2.2 etc. below No
Yes
TFCO
BAL-002-0
R2
A6
Yes
TFCO
Page 1 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
BAL-002-0
R2.1
3.1 The 10-minute reserve available to each Area shall at least equal its first contingency loss multiplied by No the Contingency Reserve Adjustment Factor for the most recently completed quarter (and shall be sustained for at least 1 hour) 3.2 The 30-minute reserve available to each Area shall at least equal one-half its second contingency loss (and shall be sustained for at least 1 hour). 3.3 The reserve on Automatic Generation Control in each Area shall be sufficient to meet NERC control performance standards CPS1 and CPS2. 3.4 100% of an Areas 10-minute reserve requirement shall be synchronized reserve except as described below. An Area shall adjust its synchronized reserve requirement based on its ability to recover from reportable events within 15 minutes.
Yes
TFCO
BAL-002-0 BAL-002-0
R2.2 R2.3
Its allocation among members The permissible mix of Operating Reserve Spinning and Operating Reserve Supplemental that may be included in Contingency Reserve.
A6 A6 Sec. 3.4
No
Yes Yes
TFCO TFCO
100 percent of an Area's ten-minute reserve requirement shall be synchronized reserve (SR) except as No described below. An Area shall adjust its SR requirement based on its ability to recover from reportable events within 15 min. This SR requirement may be decreased to a minimum of 25% of the ten-minute reserve requirement based upon the Area's past performance in returning its ACE to precontingency values, or to zero, in accordance with the following relationship: The SR requirement shall be decreased by 10 percent of the ten-minute requirement for every time a control area successfully returns its ACE to precontingency values, or to zero, following a reportable event where the resource loss is equal to or less than the magnitude of the first contingency loss. The SR requirement shall increase by 20 percent of the tenminute reserve requirement for every time an Area fails to return its ACE to precontingency values or to zero within 15 minutes followingThe maximum SR requirement shall be 100 percent of the Area's ten-minute reserve requirement.
BAL-002-0
R2.4
3.6 - Operating reserve available to an Area shall be distributed so as to ensure that it can be utilized without No exceeding individual element ratings or transfer limitations. 3.7 - Operating reserve available to an Area, if activated, shall be sustainable for at least one hour from the time of activation. None No
Yes
TFCO
BAL-002-0 BAL-002-0
R2.5 R2.6
The limitations, if any, upon the amount of interruptible load that may be included.
none
Yes Yes
TFCO TFCO
The same portion of resource capacity (e.g. reserves from jointly owned generation) shall A6 Sec. 4.2 not be counted more than once as Contingency Reserve by multiple Balancing Authorities.
Energy associated with operating reserve may be interchanged with the understanding that it is immediately No recallable. The energy associated with reserve that is utilized to meet AGC requirements to provide satisfactory system regulation shall not be sold. An Area acquiring energy sold out of the operating reserve of another Area: - Will not use this energy to augment its reserve. Resources displaced by the energy must remain available to cover for the curtailment of said energy at any time. - Must adjust its ten-minute reserve requirement to cover the larger of the Areas first contingency loss, or the largest sum of such energy purchases, which could be withdrawn at the same time due to a single contingency or event.
BAL-002-0
R3
Each Balancing Authority or Reserve Sharing Group shall activate sufficient Contingency Reserve to comply with the DCS.
C9 Sec. 1.0
BAL-002-0
R3.1
As a minimum, the Balancing Authority or Reserve Sharing Group shall carry at least A6 Sec. 3.1 enough Contingency Reserve to cover the most severe single contingency. All Balancing Authorities and Reserve Sharing Groups shall review, no less frequently than annually, their probable contingencies to determine their prospective most severe single contingencies.
NPCC-specific reporting requirements, beyond those required for meeting the NERC DCS, are specified in this document. The reporting methodology is designed to meet both NERC and NPCC reporting requirements The 10-minute reserve available to each Area shall at least equal its first contingency loss multiplied by the Contingency Reserve Adjustment Factor for the most recently completed quarter.
No
Yes
TFCO
Yes
NPCC is less stringent Yes because its criteria does not specify an annual review of the most severe single contingency. Yes
TFCO
BAL-002-0
R4
A Balancing Authority or Reserve Sharing Group shall meet the Disturbance Recovery Criterion within the Disturbance Recovery Period (DCS) for 100% of Reportable Disturbances. The Disturbance Recovery Criterion is (see R4.1, etc. below):
A6 Sec. 3.5
Areas within NPCC shall calculate and report compliance with the DCS Standard as stipulated in Document No C-09 Monitoring Procedures for Operating Reserve Criteria. The evaluation of DCS compliance for an Area shall utilize the NERC Disturbance Recovery Period of 15 minutes and shall meet the DCS requirements 100% of the time for reportable disturbances. This synchronized reserve requirement may be decreased to a minimum of 25 percent of the ten-minute reserve requirement based upon the Area's past performance in returning its Area Control Error (ACE) to precontingency values, or to zero, within fifteen minutes following loss of resource, in accordance with the following relationship: (various conditions are specified) No
TFCO
BAL-002-0
R4.1
A Balancing Authority shall return its ACE to zero if its ACE just prior to the Reportable A6 Sec. 3.4 Disturbance was positive or equal to zero. For negative initial ACE values just prior to the Disturbance, the Balancing Authority shall return ACE to its pre-Disturbance value.
Yes
TFCO
Page 2 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Yes Comment RRO Requirement? Task Force?
BAL-002-0
R4.2
The default Disturbance Recovery Period is 15 minutes after the start of a Reportable Disturbance. This period may be adjusted to better suit the needs of an Interconnection based on analysis approved by the NERC Operating Committee.
C9 Sec. 1.0
1. -The evaluation of DCS compliance for an Area should utilize the NERC Disturbance Recovery Period applicable at the time of the reportable event (15 minutes).
NPCC is more stringent Yes in that its shared activation of reserve permits an easier 10minute recovery from a disturbance as compared to the NERC 15-minute Requirement
TFCO
BAL-002-0
R4.2
The default Disturbance Recovery Period is 15 minutes after the start of a Reportable Disturbance. This period may be adjusted to better suit the needs of an Interconnection based on analysis approved by the NERC Operating Committee.
3.0 The (Shared Activation of 10-Minute Reserve) procedure provides for the shared recovery of sudden losses of generation or energy purchases by loading and sharing of ten (10) minute reserve and/or revising economy/recallable interchange schedules. 3.9 The provision for assistance via the Shared Activation of Ten-Minute Reserve Procedure shall be a Reportable Event (RE), except as noted in NPCC Document C-12. No
Yes
TFCO
BAL-002-0
R5
Each Reserve Sharing Group shall comply with the DCS. A Reserve Sharing Group A6 Sec. 3.9 shall be considered in a Reportable Disturbance condition whenever a group member has experienced a Reportable Disturbance and calls for the activation of Contingency Reserves from one or more other group members. (If a group member has experienced a Reportable Disturbance but does not call for reserve activation from other members of the Reserve Sharing Group, then that member shall report as a single Balancing Authority.) Compliance may be demonstrated by either of the following two methods (see R5.1 and R5.2 below): Each Reserve Sharing Group shall comply with the DCS. A Reserve Sharing Group C12 Sec. 4.7.1, shall be considered in a Reportable Disturbance condition whenever a group member 4.7.2 & 4.7.3 has experienced a Reportable Disturbance and calls for the activation of Contingency Reserves from one or more other group members. (If a group member has experienced a Reportable Disturbance but does not call for reserve activation from other members of the Reserve Sharing Group, then that member shall report as a single Balancing Authority.) Compliance may be demonstrated by either of the following two methods (see R5.1 and R5.2 below):
Yes
TFCO
BAL-002-0
R5
4.7.1 To determine compliance for Shared Activation Reserve (SAR) events a group ACE is calculated from the algebraic summation of the ACE values of all Areas participating in the SAR procedure. For compliance, the group ACE must cross zero (or return to the pre-contingency group ACE value if the initial group ACE value was negative just prior to the contingency) within the time(s) specified above from the start of the contingency, and, after all schedule changes have been implemented. 4.7.2 A SAR event exceeding either RE threshold is a reportable event for all participants in the procedure if the NYISO Shift Supervisor declares implementation of assistance in 5 minutes or less from the start of the contingency. 4.7.3 A SAR event exceeding either RE threshold is a reportable event only for the Contingent Area if the NYISO Shift Supervisor declares implementation of assistance after 5 minutes of the start of the contingency.
Yes
TFCO
BAL-002-0
R5.1
The Reserve Sharing Group reviews group ACE (or equivalent) and demonstrates compliance to the DCS. To be in compliance, the group ACE (or its equivalent) must meet the Disturbance Recovery Criterion after the schedule change(s) related to reserve sharing have been fully implemented, and within the Disturbance Recovery Period, or The Reserve Sharing Group reviews each members ACE in response to the activation of reserves. To be in compliance, a members ACE (or its equivalent) must meet the Disturbance Recovery Criterion after the schedule change(s) related to reserve sharing have been fully implemented, and within the Disturbance Recovery Period. A Balancing Authority or Reserve Sharing Group shall fully restore its Contingency Reserves within the Contingency Reserve Restoration Period for its Interconnection. The Contingency Reserve Restoration Period begins at the end of the Disturbance Recovery Period.
A6 Sec. 3.9 Refer to R5 above C12 Sec. 4.7.1, 4.7.2 & 4.7.3
No
Yes
TFCO
BAL-002-0
R5.2
A6 Sec. 3.9 Refer to R5 above C12 Sec. 4.7.1, 4.7.2 & 4.7.3
No
Yes
TFCO
BAL-002-0
R6
A6 Sec. 3.1
No
Yes
TFCO
BAL-002-0
R6.1
A6 Sec. 3.1
Each Area shall restore its ten-minute reserve within 105 minutes if it becomes deficient as a result of a No contingency that is a reportable event, as defined in NPCC Document C-09, Monitoring Procedures For Operating Reserve Criteria . Each Area shall restore its ten-minute reserve as soon as possible, and within 90 minutes if it becomes deficient and the deficiency is not a result of a contingency that is a reportable event. If an Area foresees that it cannot restore its ten-minute reserve within the times specified above, or extends beyond these times during operations, a NERC Energy Emergency Alert of the appropriate level shall be declared. This requirement shall be maintained at all times, except as noted in NPCC Document C-19, Procedures During Shortages of Operating Reserve .
Although not explicitly Yes stated, this is inferred by the 105-minute and 90minute time periods mentioned (and taking into account the 15minutes of response time allowed by NERC).
TFCO
BAL-002-0
R6.2
The default Contingency Reserve Restoration Period is 90 minutes. This period may be adjusted to better suit the reliability targets of the Interconnection based on analysis approved by the NERC Operating Committee.
A6 Sec. 3.1
No
Yes
TFCO
BAL-003-0
R1
BAL-003-0
R1.1
Each Balancing Authority shall review its Frequency Bias Settings by January 1 of each none year and recalculate its setting to reflect any change in the Frequency Response of the Balancing Authority Area. The Balancing Authority may change its Frequency Bias Setting, and the method used to none determine the setting, whenever any of the factors used to determine the current bias value change.
None
No
No
TFCO
None
No
No
TFCO
Page 3 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No No Comment RRO Requirement? Task Force?
BAL-003-0 BAL-003-0
R1.2 R2
Each Balancing Authority shall report its Frequency Bias Setting, and method for none determining that setting, to the NERC Operating Committee. Each Balancing Authority shall establish and maintain a Frequency Bias Setting that is as none close as practical to, or greater than, the Balancing Authoritys Frequency Response. Frequency Bias may be calculated several ways: The Balancing Authority may use a fixed Frequency Bias value which is based on a fixed, straight-line function of Tie Line deviation versus Frequency Deviation. The Balancing Authority shall determine the fixed value by observing and averaging the Frequency Response for several Disturbances during on-peak hours. The Balancing Authority may use a variable (linear or non-linear) bias value, which is based on a variable function of Tie Line deviation to Frequency Deviation. The Balancing Authority shall determine the variable frequency bias value by analyzing Frequency Response as it varies with factors such as load, generation, governor characteristics, and frequency. none
None None
No No
TFCO TFCO
BAL-003-0
R2.1
None
No
No
TFCO
BAL-003-0
R2.2
none
None
No
No
TFCO
BAL-003-0
Frequency Response and Bias Frequency Response and Bias Frequency Response and Bias
R3
BAL-003-0
R4
BAL-003-0
R4.1
Each Balancing Authority shall operate its Automatic Generation Control (AGC) on Tie none Line Frequency Bias, unless such operation is adverse to system or Interconnection reliability. Balancing Authorities that use Dynamic Scheduling or Pseudo-ties for jointly owned none units shall reflect their respective share of the unit governor droop response in their respective Frequency Bias Setting. Fixed schedules for Jointly Owned Units mandate that Balancing Authority (A) that none contains the Jointly Owned Unit must incorporate the respective share of the unit governor droop response for any Balancing Authorities that have fixed schedules (B and C). See the diagram below. The Balancing Authorities that have a fixed schedule (B and C) but do not contain the Jointly Owned Unit shall not include their share of the governor droop response in their Frequency Bias Setting. Balancing Authorities that serve native load shall have a monthly average Frequency Bias Setting that is at least 1% of the Balancing Authoritys estimated yearly peak demand per 0.1 Hz change. Balancing Authorities that do not serve native load shall have a monthly average Frequency Bias Setting that is at least 1% of its estimated maximum generation level in the coming year per 0.1 Hz change. A Balancing Authority that is performing Overlap Regulation Service shall increase its Frequency Bias Setting to match the frequency response of the entire area being controlled. A Balancing Authority shall not change its Frequency Bias Setting when performing Supplemental Regulation Service. Only a Reliability Coordinator shall be eligible to act as Interconnection Time Monitor. A single Reliability Coordinator in each Interconnection shall be designated by the NERC Operating Committee to serve as Interconnection Time Monitor. none
None
No
No
TFCO
None
No
No
TFCO
None
No
No
TFCO
BAL-003-0
Frequency Response and Bias Frequency Response and Bias Frequency Response and Bias Frequency Response and Bias
R4.2
None
No
No
TFCO
BAL-003-0
R5
none
None
No
No
TFCO
BAL-003-0
R5.1
none
None
No
No
TFCO
BAL-003-0
R6
none
None
No
No
TFCO
BAL-004-0
R1
none
None
No
No
TFCO
BAL-004-0
R2
BAL-004-0
R3
The Interconnection Time Monitor shall monitor Time Error and shall initiate or none None terminate corrective action orders in accordance with the NAESB Time Error Correction Procedure. Each Balancing Authority, when requested, shall participate in a Time Error Correction NPCC Regional The RC will communicate start and end times for time error corrections to the relevant Transmission by one of the following methods: Reliability Plan Operators and Balancing Authorities within its Reliability Area. Sec. 3.1.3.4
No
No
TFCO
No
No
TFCO
BAL-004-0 BAL-004-0
R3.1 R3.2
BAL-004-0
R4
The Balancing Authority shall offset its frequency schedule by 0.02 Hertz, leaving the Frequency Bias Setting normal; or (see R3.2 below) The Balancing Authority shall offset its Net Interchange Schedule (MW) by an amount equal to the computed bias contribution during a 0.02 Hertz Frequency Deviation (i.e. 20% of the Frequency Bias Setting). Any Reliability Coordinator in an Interconnection shall have the authority to request the Interconnection Time Monitor to terminate a Time Error Correction in progress, or a scheduled Time Error Correction that has not begun, for reliability considerations.
none none
None None
No No
No No
TFCO TFCO
RRP Sec. 4.2 & 4.2 - RC and TOP, GOP and BA shall not take any action or refrain from taking any action that would, 4.5.2 knowingly, lead to an emergency condition within their Area or a neighboring area. 4.5.2 NPCC RC who foresees a transmission problemwithin its RC Area shall issue an alert to all impacted TOP and BA in its RC Area, and all impacted RC within the Interconnection via the RCIS.
No
No
TFCO
Page 4 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
BAL-004-0
R4.1
Balancing Authorities that have reliability concerns with the execution of a Time Error Correction shall notify their Reliability Coordinator and request the termination of a Time Error Correction in progress.
C3 Sec. 2.1
It is the responsibility of the operator of any system or Area to inform the appropriate Security Coordinator, No other systems and Areas whenever it anticipates or experiences an emergency. The SC will assist the operator in dissemination of the information if requested. Prompt notice of such conditions should be communicated to: - the Interconnection through the NERC Interregional Emergency Telephone Networks neighboring utilities via SC Info System Each Area shall make every effort to always maintain total net interchange schedules. Each Area shall change No schedules as needed to maintain reliability. See R1 No
TFCO
BAL-005-0
Automatic Generation Control Automatic Generation Control Automatic Generation Control Automatic Generation Control Automatic Generation Control
R1
All generation, transmission, and load operating within an Interconnection must be included within the metered boundaries of a Balancing Authority Area.
A3 Sec. 3.2
No
TFCO
BAL-005-0
R1.1
BAL-005-0
R1.2
BAL-005-0
R1.3
Each Generator Operator with generation facilities operating in an Interconnection shall A3 Sec. 3.2 ensure that those generation facilities are included within the metered boundaries of a BA Area. Each Transmission Operator with transmission facilities operating in an Interconnection A3 Sec. 3.2 shall ensure that those transmission facilities are included within the metered boundaries of a BA Area. Each Load-Serving Entity with load operating in an Interconnection shall ensure that A3 Sec. 3.2 those loads are included within the metered boundaries of a Balancing Authority Area. Each Balancing Authority shall maintain Regulating Reserve that can be controlled by AGC to meet the Control Performance Standard. A6 Sec. 3.3
No
TFCO
See R1
No
No
TFCO
See R1
No
No
TFCO
BAL-005-0
R2
The reserve on AGC in each Area shall be sufficient to meet NERC control performance standards CPS1 and No CPS2. Except during significant frequency excursions as provided in NPCC Document A-3, Emergency Operation Criteria , automatic generation control equipment shall remain in service at all possible times to provide immediate response to sudden load changes or loss of generating equipment. 3.4 - Each Area shall maintain AGC equipment operational and in service except as stipulated in Section No 4.5. 4.2 - Accurate and reliable metering and indication of system frequency, breaker status, voltage levels and power flows (real and reactive for all tie lines and other critical elements) shall be available to the appropriate system operator(s). 4.3 - Reliable inter-Area and intra-Area voice communications shall be available for the reliability coordinators, control area operators, and system operators, as appropriate to their accountabilities, with a reliability at least equivalent to that provided by a dedicated and redundant circuit
No
TFCO
BAL-005-0
R3
A Balancing Authority providing Regulation Service shall ensure that adequate metering, A3 Sec. 3.4, communications, and control equipment are employed to prevent such service from 4.2 & 4.3 becoming a Burden on the Interconnection or other Balancing Authority Areas.
No
TFCO
BAL-005-0
R4
A Balancing Authority providing Regulation Service shall notify the Host Balancing Authority for whom it is controlling if it is unable to provide the service, as well as any Intermediate Balancing Authorities.
A3 Sec. 3.2, 3.4 3.2 - Each Area shall make every effort to always maintain total net interchange schedules. Each Area shall No & 3.8 change schedules as needed to maintain reliability. 3.4 - Each Area shall maintain AGC equipment operational and in service except as stipulated in Section 4.5. 3.8 - When an affected Area within NPCC is unable to correct a situation, a request for assistance from an Area or systems outside NPCC shall be made. Upon receiving a request for assistance to mitigate an emergency, an Area shall provide maximum reasonable assistance to any other Areas or systems outside of NPCC and shall act within the time frame that such assistance is required No
More Specificity
No
TFCO
BAL-005-0
R5
A Balancing Authority receiving Regulation Service shall ensure that backup plans are in NPCC Regional The RC shall monitor system frequency and its Balancing Authorities performance and direct any necessary place to provide replacement Regulation Service should the supplying Balancing Reliability Plan re-balancing to return to CPS and DCS compliance. The TOP and BA shall utilize all resources, including Authority no longer be able to provide this service. Sec. 3.1.3.5 shedding of firm load, as directed by its RC to relieve the emergent condition.
More Specificity
No
TFCO
BAL-005-0
R6
The Balancing Authoritys AGC shall compare total Net Actual Interchange to total Net none Scheduled Interchange plus Frequency Bias obligation to determine the BAs ACE. Single BA operating asynchronously may employ alternative ACE calculations such as (but not limited to) flat frequency control. If a BA is unable to calculate ACE for more than 30 minutes it shall notify its RC. The Balancing Authority shall operate AGC continuously unless such operation A3 Sec. 3.4 & adversely impacts the reliability of the Interconnection. If AGC has become inoperative, 4.5 the Balancing Authority shall use manual control to adjust generation to maintain the Net Scheduled Interchange.
None
Yes
No
TFCO
BAL-005-0
R7
3.4 - Each Area shall maintain AGC equipment operational and in service except as stipulated in Section 4.5. No 4.5 - A sustained frequency excursion of 0.2 Hertz is an indication of a major load-generation unbalance and possible formation of an island. It is important for the affected Area to reestablish a load-generation balance quickly, to restore frequency, and to allow islands to resynchronize as soon as possible. All automatic generation controls shall be removed from service at 59.8 Hertz on frequency decline and 60.2 Hertz on frequency increase. None None No No
NPCCdoes not specifically refer to manual control of the Net Scheduled Interchange if the AGC stops working
No
TFCO
BAL-005-0 BAL-005-0
R8 R8.1
The Balancing Authority shall ensure that data acquisition for and calculation of ACE occur at least every six seconds. Each BA shall provide redundant and independent frequency metering equipment that shall automatically activate upon detection of failure of the primary source. This overall installation shall provide a minimum availability of 99.95%. The BA shall include all Interchange Schedules with Adjacent BA in the calculation of Net Scheduled Interchange for the ACE equation.
none none
No No
TFCO TFCO
BAL-005-0
R9
none
None
No
No
TFCO
Page 5 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
BAL-005-0
R9.1
Balancing Authorities with a high voltage direct current (HVDC) link to another Balancing Authority connected asynchronously to their Interconnection may choose to omit the Interchange Schedule related to the HVDC link from the ACE equation if it is modeled as internal generation or load. The Balancing Authority shall include all Dynamic Schedules in the calculation of Net Scheduled Interchange for the ACE equation. Balancing Authorities shall include the effect of ramp rates, which shall be identical and agreed to between affected Balancing Authorities, in the Scheduled Interchange values to calculate ACE. Each Balancing Authority shall include all Tie Line flows with Adjacent Balancing Authority Areas in the ACE calculation. BA that share a tie shall ensure Tie Line MW metering is telemetered to both control centers, and emanates from a common, agreed-upon source using common primary metering equipment. Balancing Authorities shall ensure that megawatt-hour data is telemetered or reported at the end of each hour. BA shall ensure the power flow and ACE signals that are utilized for calculating BA performance or that are transmitted for Regulation Service are not filtered prior to transmission, except for the Anti-aliasing Filters of Tie Lines.
none
None
No
TFCO
BAL-005-0 BAL-005-0
Automatic Generation Control Automatic Generation Control Automatic Generation Control Automatic Generation Control
R10 R11
none none
None None
No No
No No
TFCO TFCO
BAL-005-0 BAL-005-0
R12 R12.1
none none
None None
No No
No No
TFCO TFCO
BAL-005-0
R12.2
none
None
No
No
TFCO
BAL-005-0
R12.3
BAL-005-0
R13
BA shall install common metering equipment where Dynamic Schedules or Pseudo-Ties none are implemented between two or more BA to deliver the output of Jointly Owned Units or to serve remote load. Each BA shall perform hourly error checks using Tie Line megawatt-hour meters with none common time synchronization to determine the accuracy of its control equipment. The BA shall adjust the component (e.g., Tie Line meter) of ACE that is in error (if known) or use the interchange meter error (IME) term of the ACE equation to compensate for any equipment error until repairs can be made. The Balancing Authority shall provide its operating personnel with sufficient instrumentation and data recording equipment to facilitate monitoring of control performance, generation response, and after-the-fact analysis of area performance. As a minimum, the Balancing Authority shall provide its operating personnel with real-time values for ACE, Interconnection frequency and Net Actual Interchange with each Adjacent Balancing Authority Area. The Balancing Authority shall provide its operating personnel with sufficient instrumentation and data recording equipment to facilitate monitoring of control performance, generation response, and after-the-fact analysis of area performance. As a minimum, the Balancing Authority shall provide its operating personnel with real-time values for ACE, Interconnection frequency and Net Actual Interchange with each Adjacent Balancing Authority Area. A3 Sec. 4.2
None
No
No
TFCO
None
No
No
TFCO
BAL-005-0
R14
4.2 - Accurate and reliable metering and indication of system frequency, breaker status, voltage levels and No power flows (real and reactive for all tie lines and other critical elements) shall be available to the appropriate system operator(s).
No
TFCO
BAL-005-0
R14
1.0 - This procedure describes the process to collect event data from three time frames: instantaneous, dynamic and steady state. The data in the first two frames is recorded by the various types of Disturbance Monitoring Equipment including Dynamic Recording Devices, Digital Fault Recorders and Sequence of Events Recorders. The pre-event data in the steady state time frame can be captured from real time databases.
No
No
TFCO
BAL-005-0
R15
The Balancing Authority shall provide adequate and reliable backup power supplies and RRP Sec. 4.7 shall periodically test these supplies at the Balancing Authoritys control center and other critical locations to ensure continuous operation of AGC and vital data recording equipment during loss of the normal power supply. The Balancing Authority shall sample data at least at the same periodicity with which ACE is calculated. The Balancing Authority shall flag missing or bad data for operator display and archival purposes. The Balancing Authority shall collect coincident data to the greatest practical extent, i.e., ACE, Interconnection frequency, Net Actual Interchange, and other data shall all be sampled at the same time. none
Each RC, TOP and BA shall have a plan to continue reliability operations in the event its primary control No center becomes inoperable. The contingency plan must meet the requirements specified in Reliability Standard EOP-008-0. The plan shall be reviewed and updated annually. Interim provisions must be included if it is expected to take more than one hour to implement the contingency plan for loss of primary control facility. None No
No
TFCO
BAL-005-0
R16
No
TFCO
BAL-005-0
R17
Each BA shall at least annually check and calibrate its time error and frequency devices none against a common reference. The BA shall adhere to the minimum values for measuring devices as listed below: Device (Accuracy) - Digital frequency transducer ( 0.001 Hz), MW, MVAR, and voltage transducer ( 0.25 % of full scale), Remote terminal unit ( 0.25 % of full scale), Potential transformer ( 0.30 % of full scale), Current transformer ( 0.50 % of full scale). Each Balancing Authority shall calculate and record hourly Inadvertent Interchange. Each Balancing Authority shall include all AC tie lines that connect to its Adjacent Balancing Authority Areas in its Inadvertent Interchange account. The Balancing Authority shall take into account interchange served by jointly owned generators. none none
None
No
No
TFCO
BAL-006-0 BAL-006-0
R1 R2
None None
No No
No No
TFCO TFCO
Page 6 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
BAL-006-0
Inadvertent Interchange
R3
Each Balancing Authority shall ensure all of its Balancing Authority Area none interconnection points are equipped with common megawatt-hour meters, with readings provided hourly to the control centers of Adjacent Balancing Authorities. Adjacent Balancing Authority Areas shall operate to a common Net Interchange none Schedule and Actual Net Interchange value and shall record these hourly quantities, with like values but opposite sign. Each Balancing Authority shall compute its Inadvertent Interchange based on the following: Each Balancing Authority, by the end of the next business day, shall agree with its Adjacent Balancing Authorities to: The hourly values of Net Interchange Schedule. The hourly integrated megawatt-hour values of Net Actual Interchange. none none none
None
No
TFCO
BAL-006-0
Inadvertent Interchange
R4
None
No
No
TFCO
No No No No
No No No No
BAL-006-0
Inadvertent Interchange
R4.3
Each Balancing Authority shall use the agreed-to daily and monthly accounting data to none compile its monthly accumulated Inadvertent Interchange for the On-Peak and Off- Peak hours of the month. A BA shall make after-the-fact corrections to the agreed-to daily and monthly accounting none data only as needed to reflect actual operating conditions (e.g. a meter being used for control was sending bad data). Changes or corrections based on non-reliability considerations shall not be reflected in the BAs Inadvertent Interchange. After-the-fact corrections to scheduled or actual values will not be accepted without agreement of the Adjacent BA(s). Adjacent BAs that cannot mutually agree upon their respective Net Actual Interchange None or Net Scheduled Interchange quantities by the 15th calendar day of the following month shall, for the purposes of dispute resolution, submit a report to their respective RRO Survey Contact. The report shall describe the nature and the cause of the dispute as well as a process for correcting the discrepancy. Each Reliability Coordinator, Balancing Authority, Transmission Operator, Generator Operator, and Load Serving Entity shall have procedures for the recognition of and for making their operating personnel aware of sabotage events on its facilities and multi-site sabotage affecting larger portions of the Interconnection.
None
No
No
TFCO
BAL-006-0
Inadvertent Interchange
R5
None
No
No
TFCO
CIP-001-0
Sabotage Reporting
R1
NPCC Regional Identical to NERC R1 Reliability Plan (August, 2005) RRP Sec. 4.8
No
No
TFCO
CIP-001-0
Sabotage Reporting
R2
Each Reliability Coordinator, Balancing Authority, Transmission Operator, Generator Operator, and Load Serving Entity shall have procedures for the communication of information concerning sabotage events to appropriate parties in the Interconnection. Each Reliability Coordinator, Balancing Authority, Transmission Operator, Generator Operator, and Load Serving Entity shall provide its operating personnel with sabotage response guidelines, including personnel to contact, for reporting disturbances due to sabotage events.
Identical to R2
No
No
TFCO
CIP-001-0
Sabotage Reporting
R3
Identical to R3
No
No
TFCO
CIP-001-0
Sabotage Reporting
R4
Each Reliability Coordinator, Balancing Authority, Transmission Operator, Generator RRP Sec. 4.8 Operator, and Load Serving Entity shall establish communications contacts, as applicable, with local Federal Bureau of Investigation (FBI) or Royal Canadian Mounted Police (RCMP) officials and develop reporting procedures as appropriate to their circumstances. Each Reliability Coordinator, TOP and BA shall provide adequate and reliable telecommunications facilities for the exchange of Interconnection and operating information (see R1.1, etc. below):
Identical to R4
No
No
TFCO
COM-001-0
Telecommunications
R1
NPCC Regional Each RC, TOP and BA shall provide adequate and reliable telecommunication facilities to ensure the Reliability Plan exchange of interconnection and operating information necessary to maintain reliability. (RRP) Sec. 6.3.1 A3 Sec. 4.2 & 4.3
No
No
TFIST
COM-001-0
Telecommunications
R1.1
Internally
4.2 Accurate and reliable metering and indication of system frequency, breaker status, voltage levels and No power flows (real and reactive for all tie lines and other critical elements) shall be available to the appropriate system operator(s). 4.3 - Reliable inter-Area and intra-Area voice communications shall be available for the RC, control area operators, and system operators, as appropriate to their accountabilities, with a reliability at least equivalent to that provided by a dedicated and redundant circuit. Each RC shall provide, or arrange provision for, data exchange to other RC or TOP and BA via a secure network. Each RC, TOP and BA shall provide adequate and reliable telecommunication facilities to ensure the exchange of interconnection and operating information necessary to maintain reliability. No No
No
TFIST
COM-001-0 COM-001-0
Telecommunications Telecommunications
R1.2 R1.3
Between the Reliability Coordinator and its Transmission Operators and Balancing RRP Sec. 6.3 Authorities. With other Reliability Coordinators, Transmission Operators, and Balancing Authorities RRP Sec. 6.3.1 as necessary to maintain reliability. Where applicable, these facilities shall be redundant and diversely routed.
No No
TFIST TFIST
COM-001-0
Telecommunications
R1.4
No
No
TFIST
Page 7 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
COM-001-0
Telecommunications
R2
Each RC, TOP and BA shall manage, alarm, test and/or actively monitor vital telecommunications facilities. Special attention shall be given to emergency telecoms facilities and equipment not used for routine communications. Each RC, TOP and BA shall provide a means to coordinate telecommunications among their respective areas. This coordination shall include the ability to investigate and recommend solutions to telecommunications problems within the area and with other areas.
No
TFIST
COM-001-0
Telecommunications
R3
none
None
No
No
TFIST
COM-001-0
Telecommunications
R4
Unless agreed to otherwise, each RC, TOP and BA shall use English as the language for none all communications between and among operating personnel responsible for the realtime generation control and operation of the interconnected BES. TOP and BA may use an alternate language for internal operations. Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall have written operating instructions and procedures to enable continued operation of the system during the loss of telecommunications facilities. A3 Sec. 4.4
None
No
No
TFIST
COM-001-0
Telecommunications
R5
A comprehensive set of operating limits for inter-Area and critical intra-Area interfaces, recognizing both normal and emergency transfer capabilities, shall be available to RC, control area operators and system operators as appropriate to their accountabilities. The circumstances under which each of these transfer capabilities may be used shall be clearly indicated by written instructions. None
No
No
TFIST
COM-001-0 COM-002-0
R6 R1
Each NERCNet User Organization shall adhere to the requirements in Attachment 1COM- 001-0, NERCNet Security Policy. Each Transmission Operator, Balancing Authority, and Generator Operator shall have communications (voice and data links) with appropriate Reliability Coordinators, Balancing Authorities, and Transmission Operators. Such communications shall be staffed and available for addressing a real-time emergency condition.
none
No No
TFIST TFIST
NPCC Regional 6.3.1 - Each RC, TOP and BA shall provide adequate and reliable telecommunication facilities to ensure the Reliability Plan exchange of interconnection and operating information necessary to maintain reliability. (RRP) Sec. 6.3.1 & 6.3.3
COM-002-0
R1
6.3.3 Facilities shall be subject to performance criteria to maintain the reliability of the BES within the NERC Standards. 4.2 Accurate and reliable metering and indication of system frequency, breaker status, voltage levels and power flows (real and reactive for all tie lines and other critical elements) shall be available to the appropriate system operator(s). 4.3 - Reliable inter-Area and intra-Area voice communications shall be available for the RC, control area operators, and system operators, as appropriate to their accountabilities, with a reliability at least equivalent to that provided by a dedicated and redundant circuit.
No
TFIST
COM-002-0
R2
Each Balancing Authority and Transmission Operator shall notify its RC, and all other C20 Sec. 5.2 & potentially affected BA and TOP through predetermined communication paths of any 5.2.4 condition that could threaten the reliability of its area or when firm load shedding is anticipated. The following information shall be conveyed to others in the Interconnection via an Interconnection-wide telecommunications system (see R2.1, etc. below): The Balancing Authority is unable to purchase capacity or energy to meet its demand and C20 Sec. 3.4 reserve requirements on a day-ahead or hour-by-hour basis.
5.2 Action of an Area Causing the Emergency: If an Area is having an adverse reliability impact in another No Area, it is required by NERC and NPCC Operating Policies to respond to requests for assistance from the Area in difficulty that remove or lessen the threat to its reliability, including: 5.2.4 Issue the appropriate NERC Energy Emergency Alert level and follow procedures in NERC Standard Emergency Preparedness and Operations EOP-002-0 Attachment 1. During a Regional Reserve Deficiency, the NYISO Shift Supervisor will(invoke 5.2.4 above) No
No
TFIST
COM-002-0
R2.1
No
TFIST
COM-002-0
R2.2
The Transmission Operator recognizes that potential or actual line loadings, and voltage C20 Sec. 4.2 & 4.2 When an Area is experiencing internal circuit or tie line loadings in excess of applicable operating or reactive levels are such that a single Contingency could threaten the reliability of the 4.3 limits.or 4.3 If an Area is experiencing abnormal voltage conditions The Area will invoke 5.2.4 Interconnection. (Once a single Contingency occurs, the Transmission Operator must above prepare for the next Contingency.) The Transmission Operator anticipates initiating a 3% or greater voltage reduction, C20 Sec. 5.0 public appeals for load curtailments, or firm load shedding for other than local problems. Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall RRP Sec. issue directives in a clear, concise, and definitive manner; shall ensure the recipient of 3.1.1.5 the directive repeats the information back correctly; and shall acknowledge the response as correct or repeat the original statement to resolve any misunderstandings. Each Transmission Operator, Balancing Authority, and Generator Operator shall have communications (voice and data links) with appropriate Reliability Coordinators, Balancing Authorities, and Transmission Operators. Such communications shall be staffed and available for addressing a real-time emergency condition.
No
No
TFIST
COM-002-0
R2.3
If preventative measures as outlined under Sections 3.0 and/or 4.0 have not been adequate, actions to contain No the emergency should then be taken (with the final step being to invoke 5.2.4 above) Each RC, TOP and BA shall issue directives in a clear, concise, and definitive manner; shall ensure the recipient of the directive repeats the information back correctly; and shall acknowledge the response as correct or repeat the original statement to resolve any misunderstandings. No
No
TFIST
COM-002-0
R3
No
TFIST
COM-002-1
TFCO
COM-002-1
R1
Balancing Authorities, and Transmission Operators. Such communications shall be staffed and available for addressing a real-time emergency condition.
TFCO
Page 8 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
COM-002-1
R1.1
Each Balancing Autority and Transmission Operator shall notify its Reliability Coordinator, and all other potentially affected Balancing Authorities and Transmission Operators through predetermined communication paths of any condition that could threaten the reliability of its area or when firm load shedding is anticipated. Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall issue directives in a clear, concise, and definitive manner; shall ensure the recipient of the directive repeats the information back correctly; and shall adckowledge the response as correct or repeat the original statement to resolve any misunderstandings. Balancing Authorities shall have operating agreements with adjacent Balancing A3 Sec. 3.8 Authorities that shall, at a minimum, contain provisions for emergency assistance, including provisions to obtain emergency assistance from remote Balancing Authorities. When an affected Area within NPCC is unable to correct a situation, a request for assistance from an Area or No systems outside NPCC shall be made. Upon receiving a request for assistance to mitigate an emergency, an Area shall provide maximum reasonable assistance to any other Areas or systems outside of NPCC and shall act within the time frame that such assistance is required (Note: Neighboring Areas will ensure suitable arrangements with the generating resources and / or transmission provider(s) in the Area are in place to be able to provide reasonable assistance.) Each Area must be capable of manually shedding at least fifty percent of its load in ten minutes or less. Insofar as practical, the first half of the load shed manually should not include load which is part of any automatic load shedding plan. No No
TFCO
COM-002-1
R2
TFCO
EOP-001-0
R1
TFCO
EOP-001-0
R2
The TOP shall have an emergency load reduction plan for all identified IROLs. The plan A3 Sec. 4.8 shall include the details on how the TOP will implement load reduction in sufficient amount and time to mitigate the IROL violation before system separation or collapse would occur. The load reduction plan must be capable of being implemented within 30 minutes. Each Transmission Operator and Balancing Authority shall (see following sections):
No
TFCO
EOP-001-0
R3
NPCC Regional RC, TOP, Generation Operators and BA are required to develop, maintain and implement a set of plans to Rel. Plan Sec. resolve operating emergencies. These plans must be coordinated with each other, as appropriate. 4.6.9 C20 Sec. 3.0
No
More Specificity
No
TFCO
EOP-001-0
R3.1
Develop, maintain, and implement a set of plans to mitigate operating emergencies for insufficient generating capacity .
Procedures to address shortages of the synchronized portion of 10-minute reserve, 30-minute reserve, No and 10-minute reserve that arise or are foreseen during actual operations are provided in this section. Areas are expected to commit adequate resources during the resource scheduling horizon (e.g., day-ahead Unit Commitment) to meet these requirements. Reasonable assistance shall be requested only after comparable action(s) has been implemented by the No requesting Area(s). Reasonable assistance shall normally consist of, in no implied order of priority: Redispatching generation, Curtailing non-firm energy transfers to non-affected Area, Purchasing capacity and energy on behalf of the Area experiencing the emergency, Redistribution or sharing of operating reserve, Implementing voltage reduction, etc. Each Area must be capable of manually shedding at least fifty percent of its load in ten minutes or less. No Insofar as practical, the first half of the load shed manually should not include load which is part of any automatic load shedding plan. Each Area shall have a system restoration plan in accordance with NPCC Criteria, Guides and Procedures No and in conjunction with the applicable NERC Operating Policies, Measures and Standards.
More Specificity
No
TFCO
EOP-001-0
R3.2
Develop, maintain, and implement a set of plans to mitigate operating emergencies on A3 Sec. 3.9 the transmission system.
More Specificity
No
TFCO
EOP-001-0
R3.3
A3 Sec. 4.8
More Specificity
No
TFCO
EOP-001-0
R3.4
A3 Sec. 4.10
A3 needs to be updated No to reflect the new NERC Version 0 Standards instead of Operating Policies. No
TFCO
EOP-001-0
R4
EOP-001-0
R4.1
EOP-001-0
R4.2
No Each Transmission Operator and Balancing Authority shall have emergency plans that RRP Sec. 4.6.9 RC, TOP, Generation Operators and BA are required to develop, maintain and implement a set of plans to will enable it to mitigate operating emergencies. At a minimum, Transmission resolve operating emergencies. These plans must be coordinated with each other, as appropriate. Operator and Balancing Authority emergency plans shall include (see following sections): C1 No Communications protocols to be used during emergencies. NPCC Emergency Preparedness Conference Call Procedures NPCC Security Conference Call Procedures This document outlines the participation and protocol to be used within NPCC when Conference Calls are used to deal with operational issues. A list of controlling actions to resolve the emergency . Load reduction, in sufficient A3 Sec. 4.1 & 4.1 Reliability Coordinators, control area operators and system operators shall have the responsibility and No quantity to resolve the emergency within NERC-established timelines, shall be one of the 3.9 authority to implement emergency procedures including curtailment of transactions and/or shedding of controlling actions. firm load. 3.9 - Reasonable assistance shall be requested only after comparable action(s) has been implemented by the requesting Area(s). Reasonable assistance shall normally consist of, in no implied order of priority: Redispatching generation, Curtailing non-firm energy transfers to non-affected Area, Voltage reduction, Reserve sharing, Purchasing capacity, etc. The tasks to be coordinated with and among adjacent Transmission Operators and Balancing Authorities. A3 Sec. 3.8 & 3.9 3.8 - When an affected Area within NPCC is unable to correct a situation, a request of assistance from an No Area or systems outside NPCC shall be made. 3.9 - Reasonable assistance shall be requested only after comparable action(s) has been implemented by the requesting Area(s). Reasonable assistance shall normally consist of, in no implied order of priority: Redispatching generation, Curtailing non-firm energy transfers to non-affected Area, Voltage reduction, Reserve sharing, Purchasing capacity, etc.
TFCO
No
TFCO
No
TFCO
EOP-001-0
R4.3
No
TFCO
Page 9 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
EOP-001-0
R4.4
10.1 - The Reliability Coordinator shall be staffed with adequately trained and NERC-Certified Reliability Coordinator operators, 24 hours/day, seven days/week. 10.2 Each Transmission Operator, Balancing Authority and RC shall staff all operating positions with personnel that are NERC-certified for the applicable functions. None
NPCC does not refer to either staffing levels or during emergency conditions.
No
TFCO
EOP-001-0
R5
Each Transmission Operator and Balancing Authority shall include the applicable elements in Attachment 1-EOP-001-0 when developing an emergency plan.
None
No
No
TFCO
EOP-001-0
R6
The Transmission Operator and Balancing Authority shall annually review and update None each emergency plan. The Transmission Operator and Balancing Authority shall provide a copy of its updated emergency plans to its Reliability Coordinator and to neighboring Transmission Operators and Balancing Authorities.
None
No
No
TFCO
EOP-001-0
R7
RRP Sec. 4.6.4 If the Reliability Coordinator determines that BA within its Area cannot comply with the Control Performance No The Transmission Operator and Balancing Authority shall coordinate its emergency or Disturbance Control Standards, then it must immediately declare an Energy Emergency and implement plans with other Transmission Operators and Balancing Authorities as appropriate. This remedies such as (see actions below): coordination includes the following steps, as applicable (see R7.1, R7.2 etc. below): The Transmission Operator and Balancing Authority shall establish and maintain reliable communications between interconnected systems. A3 Sec. 4.3 No Reliable inter-Area and intra-Area voice communications shall be available for the RC, control area operators and system operators, as appropriate to their accountabilities, with a reliability at least equivalent to that provided by a dedicated and redundant circuit. When an affected Area within NPCC is unable to correct a situation, a request of assistance from an Area or systems outside NPCC shall be made. Upon receiving a request for assistance to mitigate an emergency, an Area shall provide maximum reasonable assistance to any other Areas or systems outside NPCC To ensure that there is effective coordination for system reliability concerns, this document establishes procedures for the exchange of information regarding load/capacity forecasts, including firm sales and purchases, generator outage schedules, transmission outage schedules for those facilities that may have an adverse impact on adjacent Areas or Areas, or neighboring system or systems. Reasonable assistance shall consist of: - purchasing capacity and energy on behalf of the Area experiencing the emergency. Procedures for Solar Magnetic Disturbances Which Affect Electric Power Systems - This document is the NPCC operational guide on SMD (or GIC) and their possible effects on power systems, including recommended operating procedures to mitigate their impacts on the BPS No
No
TFCO
EOP-001-0
R7.1
No
TFCO
EOP-001-0
R7.2
The Transmission Operator and Balancing Authority shall arrange new interchange agreements to provide for emergency capacity or energy transfers if existing agreements cannot be used.
A3 Sec. 3.8
No
TFCO
EOP-001-0
R7.3
C1 Sec. 1.0 The Transmission Operator and Balancing Authority shall coordinate transmission and generator maintenance schedules to maximize capacity or conserve the fuel in short supply. (This includes water for hydro generators.)
No
No
TFCO
EOP-001-0
R7.4
The Transmission Operator and Balancing Authority shall arrange deliveries of electrical energy or fuel from remote systems through normal operating channels. none
A3 Sec. 3.9.4
No
No
TFCO
EOP-001-0
R8
C15
Yes
NPCC is more stringent No because there is no equivalent NERC Requirement (although NERC has a Geomagnetic Disturbance Reference Document dated Sept. 14, 2005
TFCO
EOP-002-0
R1
Each BA and RC shall have the responsibility and clear decision-making authority to take whatever actions are needed to ensure the reliability of its respective area and shall exercise specific authority to alleviate capacity and energy emergencies. Each Balancing Authority and Reliability Coordinator shall implement its capacity and energy emergency plan, when required and as appropriate, to reduce risks to the interconnected system.
NPCC Regional RC, BA and TOP have the responsibility and decision-making authority for maintaining the reliability of the Reliability Plan BES and shall exercise their specific authority to prevent or mitigate capacity and energy emergencies. Sec. 4.3
No
No
TFCO
EOP-002-0
R2
RRP Sec. 4.6.8 Specific instructions are provided in NPCC Document C-20 for the redistribution of Operating Reserve No among Areas when any Area is forecasting or experiencing an Operating Reserve deficiency. It describes the NYISOs role in coordinating the re-dispatch of available resources among Areas when the NPCC operating reserve becomes deficient. C-20 also outlines the obligations of each NPCC Area with respect to inter-Area Operating Reserve assistance. C20 Sec. 3.0 When an Area becomes deficient or forecasts a deficiency inreserves it should: a) inform the senior shift authority in each of the other Areas of NPCC b) initiate or request NPPC to initiate an NPCC Em.Prep.Conference Call No
No
TFCO
EOP-002-0
R3
A Balancing Authority that is experiencing an operating capacity or energy emergency shall communicate its current and future system conditions to its Reliability Coordinator and neighboring Balancing Authorities.
No
TFCO
EOP-002-0
R4
A Reliability Coordinator that is experiencing an operating capacity or energy emergency RRP Sec. 4.5.6 4.5.6 - During extended emergencies, NPCC RC are required to ensure that effective, timely and accurate shall communicate its current and future system conditions to neighboring areas. & 4.5.7 information is provided, as appropriate, to key entities such as media, government and regulatory bodies to facilitate public awareness and cooperation. 4.5.7 An RC that is forecasting a potential or experiencing an actual energy emergency within its RC Area shall initiate an EEA via RCIS. A Balancing Authority anticipating an operating capacity or energy emergency shall perform all actions necessary including bringing on all available generation, postponing equipment maintenance, scheduling interchange purchases in advance, and being prepared to reduce firm load. C20 Sec. 3.3
No
No
TFCO
EOP-002-0
R5
3.3 - If an Area is currently unable to meet its 10-minute reserve requirement or a deficiency is forecastedit No should issue an EEA, commit off-line supply resources, recall all applicable exports, obtain additional resources from outside the Area, consider public appeals, etc.
No
TFCO
Page 10 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
EOP-002-0
R5
4.4 A Balancing Authority and Transmission Operator operating with insufficient generation or transmission capacity must have the capability and authority to shed load rather than risk an uncontrolled failure of the interconnection as per requirements outlined in EOP-003-0. During a system emergency, the RC shall comply with NERC Control Performance and Disturbance Control No Standards. The RC may not rely on the frequency bias of the other Transmission Operators, Generation Operators and Balancing Authority provide energy during the emergency because doing so reduces the Interconnections ability to recover its frequency following additional generator failures.
No
TFCO
EOP-002-0
R6
A deficient Balancing Authority shall only use the assistance provided by the RRP Sec. 4.6.4 Interconnections frequency bias for the time needed to implement corrective actions. The Balancing Authority shall not unilaterally adjust generation in an attempt to return Interconnection frequency to normal beyond that supplied through frequency bias action and Interchange Schedule changes. Such unilateral adjustment may overload transmission facilities.
No
TFCO
EOP-002-0
R7
If the Balancing Authority cannot comply with the Control Performance and Disturbance RRP Sec. 4.6.4 If the Reliability Coordinator determines that BAs within is Area cannot comply with the Control Control Standards, then it shall immediately implement remedies to do so. These Performance or Disturbance Control Standards, then it must (see following sections): remedies include, but are not limited to (see R7.1, R7.2 etc. which follow): Loading all available generating capacity. Deploying all available operating reserve Interrupting interruptible load and exports Requesting emergency assistance from other Balancing Authorities. Declaring an Energy Emergency through its Reliability Coordinator C20 Sec. 3.3 C20 Sec. 3.3 C20 Sec. 3.3 Recall planned generator and transmission outages that will increase operating reserve or transfer capability Commit sufficient off-line supply-side resources to create additional 10-minute reserve.
No
No
TFCO
Capacity and Energy Emergencies Capacity and Energy Emergencies Capacity and Energy Emergencies Capacity and Energy Emergencies Capacity and Energy Emergencies Capacity and Energy Emergencies Capacity and Energy Emergencies
No No No No No
No No No No No No No
Include interruptible customers load that can be interrupted within 10 minutes in its 10-minute reserve and recall applicable exports respecting Area operating procedures. RRP Sec. 4.6.4 Implement remedies such as requesting assistance from other Reliability Coordinators. RRP Sec. 4.6.4 Immediately declare an Energy Emergency
Reducing load, through procedures such as public appeals, voltage reductions, curtailing RRP Sec. 4.6.4 interruptible loads and firm loads. Once the Balancing Authority has exhausted the steps listed in Requirement 7, or if these C20 Sec. 3.3 steps cannot be completed in sufficient time to resolve the emergency condition, the Balancing Authority shall (see R8.1 and R8.2 below): Manually shed firm load without delay to return its ACE to zero. C20 Sec. 3.3 RRP Sec. 4.4
Implementing load reduction through public appeals, voltage reductions, curtailing interruptible loads and No shedding firm loads If an Area is currently unable to meet its 10-minute reserve requirement or a deficiency is forecasted, and the No Area does not expect to restore its 10-minute reserve within the time specified in NPCC Document Operating Reserve Criteria (A-06), it should (see below): 3.3 - Issue the appropriate NERC Energy Emergency Alert level and follow procedures in NERC Standard Emergency Preparedness and Operations EOP-002-0 Attachment 1. 4.4 - A Balancing Authority and Transmission Operator operating with insufficient generation or transmission capacity must have the capability and authority to shed load rather than risk an uncontrolled failure of the interconnection as per requirements outlined in EOP-003-0 Issue the appropriate NERC Energy Emergency Alert level and follow procedures in NERC Standard Emergency Preparedness and Operations EOP-002-0 Attachment 1. If the Reliability Coordinator determines that BAs within is Area cannot comply with the Control Performance or Disturbance Control Standards, then it must immediately declare an Energy Emergency and implement remedies such as requesting assistance from other RC, or implementing load reductions through public appeals, voltage reductions, curtailing interruptible loads and shedding firm load to return ACE to acceptable criteria. None No
EOP-002-0 EOP-002-0
R8.1 R8.1
No No
TFCO TFCO
EOP-002-0
R8.2
Request the Reliability Coordinator to declare an Energy Emergency Alert in accordance C20 Sec. 3.3 with Attachment 1-EOP-002-0 Energy Emergency Alert Levels. A Reliability Coordinator that has any BA within its RC area experiencing a potential or RRP Sec. 4.6.4 actual Energy Emergency shall initiate an EEA as detailed in Attachment 1-EOP-002-0 Energy Emergency Alert Levels. The RC shall act to mitigate the emergency condition, including a request for emergency assistance if required. When a Transmission Service Provider expects to elevate the transmission service None priority of an Interchange Transaction from Priority 6 (Network Integration Transmission Service from Non-designated Resources) to Priority 7 (Network Integration Transmission Service from designated Network Resources) as permitted in its transmission tariff (See Attachment 1-IRO- 006-0 Transmission Loading Relief Procedure for explanation of Transmission Service Priorities) (see R10.1, R10.2):
No
No
TFCO
EOP-002-0
R9
No
No
TFCO
EOP-002-0
R10
Yes
No
TFCO
EOP-002-0
Capacity and Energy Emergencies Capacity and Energy Emergencies Capacity and Energy Emergencies Capacity and Energy Emergencies
R10.1
The deficient Load-Serving Entity shall request its Reliability Coordinator to initiate an Energy Emergency Alert in accordance with Attachment 1-EOP-002-0. The Reliability Coordinator shall submit the report to NERC for posting on the NERC Website, noting the expected total MW that may have its transmission service priority changed. The Reliability Coordinator shall use EEA 1 to forecast the change of the priority of transmission service of an Interchange Transaction on the system from Priority 6 to Priority 7. The Reliability Coordinator shall use EEA 2 to announce the change of the priority of transmission service of an Interchange Transaction on the system from Priority 6 to Priority 7.
None
None
Yes
No
TFCO
EOP-002-0
R10.2
None
None
Yes
No
TFCO
EOP-002-0
R10.3
none
None
No
No
TFCO
EOP-002-0
R10.4
none
None
No
No
TFCO
Page 11 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
EOP-002-0
This Attachment to EOP-002-0 provides the procedures by which a LSE can obtain RRP Sec. 4.5.7 A Reliability Coordinator that is forecasting a potential or experiencing an actual energy emergency within its No capacity and energy when it has exhausted all other options and can no longer provide its Reliability Coordinator Area shall initiate an Energy Emergency Alert via RCIS as detailed in EOP-002-0 customers expected energy requirements. NERC defines this situation as an Energy (Attachment 1). Emergency. NERC assumes that a capacity deficiency will manifest itself as an energy emergency. The EEA Procedure is initiated by the LSEs Reliability Coordinator, who declares various EEA levels as defined in Section B to provide assistance to the LSE.
No
TFCO
EOP-002-1
R1
Each Balancing Authority and Reliability Coorinator shall have the responsibility and clear decision-making authority to take whatever actions are needed to ensure the reliability of its respective area and shall exercise specific authority to alleviate capacity and energy emergencies. Each Balancing Authority shall implement its capacity and energy emergency plan, when required and as appropriate, to reduce risks to the interconnected system. A Balancing Authority that is experiencing an operating capacity or energy emergency shall communicate its current and future system conditions to its Reliability Coordinator and neighboring Balancing Authorities. A Balancing Authority anticipating an operating capacity or energy emergency shall perform all actions necessary including bringing on all available generation, postponing equipment maintenance, scheduling interchange purchases in advance, and being prepared to reduce firm load. A deficient Balancing Authority shall only use the assistance provided by the Interconnections frequency bias for the time needed to implement corrective actions. The Balancing Authority shall not unilaterally adjust generation in an attempt to return Interconnection frequency to normal beyond that supplied through frequency bias action and interchange Schedule changes. Such unilateral adjustment may overload transmission facilities. If the Balancing Authority cannot comply with the Control Performance and Disturbance Control Standards, then it shall immediately implement remedies to do so. These remedies include, but are not limited to: R6.1. Loading all available generating capacity. R6.2. Deploying all available operating reserve. R6.3. Interrupting interruptible load and exports R6.4. Requesting emergency assistance from other Balancing Authorities.
TFCO
EOP-002-1
R2
TFCO
EOP-002-1
R3
TFCO
EOP-002-1
R4
TFCO
EOP-002-1
R5
TFCO
EOP-002-1
R6
TFCO
R6.5. Declaring an Energy Emergency through its Reliability Coordinator; and R6.6. Reducing load, through procedures such as public appeals, voltage reductions, curtailing interruptible loads and firm loads. EOP-002-1 Capacity and Energy Emergencies R7 Once the Balancing Authority has exhausted the steps listed in Requirement 7, or if these steps cannot be completed in sufficient time to resolve the emergency condition, the Balancing Authority shall: R7.1. Manually shed firm load without delay to return its ACE to zero; and
TFCO TFCO
TFCO TFCO R7.2. Request the Reliability Coordinator to declare an Energy Emergency Alert in accordance with Attachment 1-EOP-002-0 Energy Emergency Alert Levels. EOP-002-1 Capacity and Energy Emergencies R8 A Reliability Coordinator that has any Balancing Authority within its Reliability Coordinator area experiencing a potential or actual Energy Emergency shall initiate an Energy Emergency Alert as detailed in Attachment 1-EOP-002-0 Energy Emergency Alert Levels. The Reliability Coordinator shall act to mitigate the emergency condition, including a request for emergency assistance if required. R9 When a Transmission Service Provider expects to elevate the transmission service priority of an Interchange Transaction from Priority 6 (Network Integration Transmission Service from Non-designated Resources) to Priority 7 (Network Integration Transmission Service from designated Network Resources) as permitted in its transmission tariff (See Attachment 1-IRO-006-0 Transmission Loading Relief Procedure for explanation of Transmission Service Priorities): TFCO R9.1. The deficient Load-Serving Entity shall request its Reliability Coordinator to initiate an Energy Emergency Alert in accordance with Attachment 1-EOP-002-0. TFCO TFCO
EOP-002-1
Page 12 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
EOP-003-0
R1
R9.2. The Reliability Coordinator shall submit the report to NERC for posting on the NERC Website, noting the expected total MW that may have its transmission service priority changed. R9.3. The Reliability Coordinator shall use EEA 1 to forecast the change of the priority of transmission service of an Interchange Transaction on the system from Priority 6 to Priority 7. R9.4. The Reliability Coordinator shall use EEA 2 to announce the change of the priority of transmission service of an Interchange Transaction on the system from Priority 6 to Priority 7. After taking all other remedial steps, a Transmission Operator or Balancing Authority NPCC Regional operating with insufficient generation or transmission capacity shall shed customer load Reliability Plan rather than risk an uncontrolled failure of components or cascading outages of the Sec. 4.5.7 Interconnection. Each Transmission Operator and Balancing Authority shall establish plans for automatic A3 Sec. 4.6 & load shedding for underfrequency or undervoltage conditions. 4.7
TFCO
TFCO
TFCO
A Reliability Coordinator that is forecasting a potential or experiencing an actual energy emergency within its No Reliability Coordinator Area shall initiate an Energy Emergency Alert via RCIS as detailed in EOP-002-0 Attachment 1 (Note: this document calls for LSE, TOP, BA and/or RC to initiate actions up to and including load shedding to relieve Energy Emergencies) 4.6 The intent of the Automatic Underfrequency Load Shedding program is to stabilize the system frequency in a Area during an event leading to declining frequency while recognizing the generation characteristics of each Area. 4.7 An Area may employ automatic under-voltage load shedding of selected loads to enhance power system security. No
No
TFCO
EOP-003-0
R2
No
TFCO
EOP-003-0
R3
Each Transmission Operator and Balancing Authority shall coordinate load shedding plans among other interconnected Transmission Operators and Balancing Authorities. A Transmission Operator or Balancing Authority shall consider one or more of these factors in designing an automatic load shedding scheme: frequency, rate of frequency decay, voltage level, rate of voltage decay, or power flow levels.
A3 Sec. 4.6
EOP-003-0
R4
The Automatic U/FLS program must be coordinated among the NPCC Areas. Each Area is required to carry No out the following unless an alternative plan is submitted by an Area for review by the NPCC TFCO and TFSS and approved by NPCC RCC 2.0 - Selection of underfrequency sensing devices should be on a threshold basis. Alternatively, rate of change No of frequency load shedding may be used when the requirements of the Area indicate that this method will achieve the intent of the load shedding program. Appropriate studies are necessary to determine the application and settings of the rate of change of frequency relays for a particular Area. 2.1 - In order for each Member System to shed approximately the same proportion of load, given the same frequency condition, all styles and manufacture of underfrequency relays must trip at essentially the same time. For electromechanical relays, time delay depends on rate of frequency decline, and it is not possible to achieve uniform response for different rates of decline. The recommendations in this guideline are based on the goal of a uniform response at a rate of frequency decline of 0.2 Hz per second.
No
TFCO
No
TFCO
EOP-003-0
R5
A Transmission Operator or Balancing Authority shall implement load shedding in steps A3 Sec. 4.6.1, established to minimize the risk of further uncontrolled separation, loss of generation, or 4.6.2 & 4.6.3 system shutdown. After a Transmission Operator or Balancing Authority Area separates from the Interconnection, if there is insufficient generating capacity to restore system frequency following automatic underfrequency load shedding, the Transmission Operator or Balancing Authority shall shed additional load. A3 Sec. 4.8
4.6.1 - Automatic load shedding of ten percent of its load at a nominal set point of 59.3 Hertz. 4.6.2 Automatic load shedding of an additional fifteen percent of its load at a nominal set point of 58.8 Hertz. 4.6.3 Underfrequency threshold relays shall be set to a nominal operating time of 0.30 second Each Area must be capable of manually shedding at least fifty percent of its load in ten minutes or less. Insofar as practical, the first half of the load shed manually should not include load which is part of any automatic load shedding plan. Care should be taken that manual load shedding plans do not interrupt transmission paths. The plan should include the capability of shedding load proportionately over the whole system, but it must also recognize that operating requirements may limit shedding to one part of a system.
No
No
TFCO
EOP-003-0
R6
No
No
TFCO
EOP-003-0
R7
The Transmission Operator and Balancing Authority shall coordinate automatic load shedding throughout their areas with underfrequency isolation of generating units, tripping of shunt capacitors, and other automatic actions that will occur under abnormal frequency, voltage, or power flow conditions.
A3 Sec. 4.9
Generators should not be tripped for under-frequency conditions in the area above the curve in Figure 1. It is No recognized that, in special cases, requirements may dictate generator trip in the region above the curve. In those cases, automatic load shedding additional to the amount set out in Section 4.6, equivalent to the amount of generation to be tripped, must be provided. Each Area must be capable of manually shedding at least fifty percent of its load in ten minutes or less. Insofar as practical, the first half of the load shed manually should not include load which is part of any automatic load shedding plan. No
No
TFCO
EOP-003-0
R8
Each Transmission Operator or Balancing Authority shall have plans for operatorA3 Sec. 4.8 controlled manual load shedding to respond to real-time emergencies. The Transmission Operator or Balancing Authority shall be capable of implementing the load shedding in a timeframe adequate for responding to the emergency. Each Regional Reliability Organization shall establish and maintain a Regional reporting B13 Sec. 1.0 procedure to facilitate preparation of preliminary and final disturbance reports.
No
TFCO
EOP-004-0
Disturbance Reporting
R1
This document establishes the TFCO requirements and guidelines for reporting system disturbances in order to meet the requirements of Items 7 and 8 of its Scope: Prepare an initial report on disturbances which affect more than one operating Area of NPCC. Review, with emphasis on inter-Area implications, initial reports of disturbances which affect a significant part of one Area. and Monitor the implementation of recommendations affecting operations, arising from analyses of disturbances. This document also sets out the guidelines of the TFCO for the review of reports of system disturbances external to NPCC from which lessons may be learned.
No
Yes
TFCO
EOP-004-0
Disturbance Reporting
R2
A Reliability Coordinator, Balancing Authority, Transmission Operator, Generator Operator or Load Serving Entity shall promptly analyze Bulk Electric System disturbances on its system or facilities.
B13 Sec. 2.1 & NPCC Disturbances requiring review are: - Any deliberate action takento reduce electricity demands to No 3.1 maintain reliability of BPS supply by firm load shedding - Any deliberate action takento reduce voltage Any bulk supply incident where equipment and customer outages in an Area exceed 300 MW for 15 minutes or longer - Any BPS incident where outages occur in more than one Areadue to the same event
No
TFCO
Page 13 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
EOP-004-0
Disturbance Reporting
R3
A Reliability Coordinator, Balancing Authority, Transmission Operator, Generator Operator or Load Serving Entity experiencing a reportable incident shall provide a preliminary written report to its Regional Reliability Organization and NERC.
Each Area shall: Forward within one working day, a completed copy of the attached NPCC Disturbance No Reporting Form or a similar summary to the NPCC office and to TFCO members and liaisons in other Areas, and, If deemed necessary by the TFCO Chairman, prepare and forward to NPCC staff, to TFCO members and liaisons in other Areas, within 1 month, a written report containing the chronology of events, analysis and recommendations for implementation and/or further study. For each NPCC Area disturbance requiring review and for each NPCC inter-Area disturbance, the TFCO Secretary will forward to the NERC office within one working day of receipt, a copy of each NPCC Disturbance Reporting Form as submitted to NPCC. Also, a copy of the written TFCO reports for disturbances will be forwarded within 1 week of acceptance by the RCC. No
NPCC should specify the No report also be sent to NERC (even though a report is sent to NERC in actual practice) NPCC does not specify a No procedure for handling events that are late in being recognized.
TFCO
EOP-004-0
Disturbance Reporting
R3.1
The affected Reliability Coordinator, BA, TOP, GOP or LSE shall submit within 24 hours of the disturbance or unusual occurrence either a copy of the report submitted to DOE, or, if no DOE report is required, a copy of the NERC IROL and Preliminary Disturbance Report form. Events that are not identified until some time after they occur shall be reported within 24 hours of being recognized .
TFCO
EOP-004-0
Disturbance Reporting
R3.2
Applicable reporting forms are provided in Attachments 1-EOP-004-0 and 2-EOP-004- B13 Sec. 3.2.1a Forward within one working day, a completed copy of the attached NPCC Disturbance Reporting Form or a 0. similar summary to the NPCC office and to TFCO members and liaisons in other Areas.
No
TFCO
EOP-004-0
Disturbance Reporting
R3.3
Under certain adverse conditions, e.g., severe weather, it may not be possible to assess the damage caused by a disturbance and issue a written IROL and Preliminary Disturbance Report within 24 hours. In such cases, the affected Reliability Coordinator, Balancing Authority, Transmission Operator, Generator Operator, or Load Serving Entity shall promptly notify its Regional Reliability Organization(s) and NERC, and verbally provide as much information as is available at that time. The affected RC, Balancing Authority, Transmission Operator, Generator Operator, or Load Serving Entity shall then provide timely, periodic verbal updates until adequate information is available to issue a written Preliminary Disturbance Report.
none
none
No
TFCO
EOP-004-0
Disturbance Reporting
R3.4
If, in the judgment of the Regional Reliability Organization, after consultation with the B13 Sec. 2.2.2, Reliability Coordinator, Balancing Authority, Transmission Operator, Generator 2.2.3 & 2.2.4 Operator, or Load Serving Entity in which a disturbance occurred, a final report is required, the affected Reliability Coordinator, Balancing Authority, Transmission Operator, Generator Operator, or Load Serving Entity shall prepare this report within 60 days. As a minimum, the final report shall have a discussion of the events and its cause, the conclusions reached, and recommendations to prevent recurrence of this type of event. The report shall be subject to Regional Reliability Organization approval.
2.2.2 - The TFCO Chairman may convene a meeting of the Task Force as soon as necessary upon receipt of the preliminary report(s) and, if an interim report is prepared, the TFCO Chairman will arrange for the forwarding of a summary interim report to the Reliability Coordinating Committee (RCC) within 1 day of receiving the interim report.
Yes
NPCC is more stringent Yes in requiring the final report within 30 days instead of 60 days.
TFCO
EOP-004-0
Disturbance Reporting
R3.4
If, in the judgment of the Regional Reliability Organization, after consultation with the 3.2.3 & Reliability Coordinator, Balancing Authority, Transmission Operator, Generator Operator, or Load Serving Entity in which a disturbance occurred, a final report is required, the affected Reliability Coordinator, Balancing Authority, Transmission Operator, Generator Operator, or Load Serving Entity shall prepare this report within 60 days. As a minimum, the final report shall have a discussion of the events and its cause, the conclusions reached, and recommendations to prevent recurrence of this type of event. The report shall be subject to Regional Reliability Organization approval.
2.2.3 - The TFCO will review the written report with emphasis on inter-Area implications, and will, if Yes deemed necessary, convene an ad hoc TFCO Disturbance Analysis Working Group (DAWG). The ad hoc TFCO DAWG will advise the TFCO of its findings within 30 days of the formation of the Working Group, including lessons to be learned from the incident and recommendations for appropriate actions.
NPCC is more stringent Yes in requiring the final report within 30 days instead of 60 days.
TFCO
EOP-004-0
Disturbance Reporting
R3.4
If, in the judgment of the Regional Reliability Organization, after consultation with the 3.2.4 (~same as 2.2.4 - The TFCO will review the written report and will advise the RCC of its findings, where appropriate. Reliability Coordinator, Balancing Authority, Transmission Operator, Generator above) Operator, or Load Serving Entity in which a disturbance occurred, a final report is required, the affected Reliability Coordinator, Balancing Authority, Transmission Operator, Generator Operator, or Load Serving Entity shall prepare this report within 60 days. As a minimum, the final report shall have a discussion of the events and its cause, the conclusions reached, and recommendations to prevent recurrence of this type of event. The report shall be subject to Regional Reliability Organization approval.
Yes
NPCC is more stringent Yes in requiring the final report within 30 days instead of 60 days.
TFCO
EOP-004-0
Disturbance Reporting
R4
When a BES disturbance occurs, the RRO shall make its representatives on the NERC B13 Sec. 3.2.3 Operating Committee and Disturbance Analysis Working Group available to the affected RC, BA, TOP, Generator Operator, or LSE immediately affected by the disturbance for the purpose of providing any needed assistance in the investigation and to assist in the preparation of a final report.
The TFCO will review the final report(s) and, if deemed necessary, convene an ad hoc TFCO DAWG. The No ad hoc TFCO DAWG will advise the TFCO within 30 days of the formation of the Working Group, including lessons to be learned from the incident, recommendations for appropriate action, and further study or implementation of corrective measures as required.
NPCC does not specify that the NPCC representatives on the NERC OC and NERC DAWG will be made available for the investigation.
Yes
TFCO
Page 14 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
EOP-004-0
Disturbance Reporting
R5
The RRO shall track and review the status of all final report recommendations at least twice each year to ensure they are being acted upon in a timely manner. If any recommendation has not been acted on within two years, or if RRO tracking and review indicates at any time that any recommendation is not being acted on with sufficient diligence, the RRO shall notify the NERC PC and OC of the status of the recommendation(s) and the steps the RRO has taken to accelerate implementation.
3.0 At each TFSP meeting, the TF will review all disturbances and protection misoperations reported since No the previous meeting. The minutes of the meeting shall record each disturbance and protection misoperation reviewed and the action taken
NPCC does not have a Yes time limit (like the 2year NERC limit) on completing recommendation arising from a disturbance report
TFCO
EOP-004-0
Disturbance Reporting
R5
The RRO shall track and review the status of all final report recommendations at least twice each year to ensure they are being acted upon in a timely manner. If any recommendation has not been acted on within two years, or if RRO tracking and review indicates at any time that any recommendation is not being acted on with sufficient diligence, the RRO shall notify the NERC PC and OC of the status of the recommendation(s) and the steps the RRO has taken to accelerate implementation.
B13 Sec. 6.2 & 6.2 Each recommendation contained in a TFCO review report for an NPCC Area disturbance requiring 6.3 review or NPCC inter-Area disturbance will be sent to other TF with recommendations for specific action.
No
NPCC does not have a Yes time limit (like the 2year NERC limit) on completing recommendation arising from a disturbance report
TFCO
EOP-004-0
Disturbance Reporting
R5
The RRO shall track and review the status of all final report recommendations at least twice each year to ensure they are being acted upon in a timely manner. If any recommendation has not been acted on within two years, or if RRO tracking and review indicates at any time that any recommendation is not being acted on with sufficient diligence, the RRO shall notify the NERC PC and OC of the status of the recommendation(s) and the steps the RRO has taken to accelerate implementation.
6.3 TFCO will be kept informed of the status of suggested recommendations through the Recommendation Tracking Data Base.
No
NPCC does not have a Yes time limit (like the 2year NERC limit) on completing recommendation arising from a disturbance report
TFCO
EOP-004-0
Disturbance Reporting
R6
none
Reviewable External Disturbances - Any bulk supply incident reported by a system external to NPCC, the report of which can be considered to contain experience of value to NPCC relative to the operational situations observed and the applicability of NPCC Criteria. (This section of B13 goes on to describe how NPCC goes about reviewing significant external disturbances for lessons learned )
Yes
NPCC is more stringent Yes because there is no equivalent NERC Requirement The requirements of NERC Attachment 1 in EOP-005-0 appear to have been met but nowhere does NPCC explicitly say that it meets the requirements of Attachment 1 No
TFCO
EOP-005-0
R1
Each Transmission Operator shall have a restoration plan to reestablish its electric system in a stable and orderly manner in the event of a partial or total shutdown of its system, including necessary operating instructions and procedures to cover emergency conditions, and the loss of vital telecommunications channels. Each Transmission Operator shall include the applicable elements listed in Attachment 1-EOP-005-0 in developing a restoration plan.
NPCC Regional After a system collapse, restoration shall begin when the RC and its affected TOP, Generation Operators and No Reliability Plan BA determine that they can proceed in an orderly and secure manner. RC and the affected TOP, GOP and Sec. 5.0 BA shall coordinate their restoration actions. High restoration priority shall be given to establishing the transmission system and restoration of off-site power to nuclear stations. Even though the restoration is to be expeditious, TOP, GOP and BA shall avoid any action that would cause a subsequent collapse of the BES. Customer load shall be restored as generation and transmission equipment becomes available, recognizing that load and generation must remain in balance at normal frequency.
TFCO
EOP-005-0
R2
Each Transmission Operator shall review and update its restoration plan at least annually A3 Sec. 4.10, and whenever it makes changes in the power system network, and shall correct 6.2 & 6.3.2 deficiencies found during the simulated restoration exercises.
4.10 Each Area shall have a system restoration plan in accordance with NPCC Criteria, Guides and No Procedures and in conjunction with applicable NERC Operating Policies, Measures & Standards. 6.2 Each Area shall annuallydeclare to NPCC that it has reviewed its list of key facilities .. submit any revisions to NPCC.
NPCC should update the No reference to NERC Standards as opposed to Policies (continued below) See R2 on previous page No
TFCO
EOP-005-0
R2
Each Transmission Operator shall review and update its restoration plan at least annually A3 Sec. 6.3.2 and whenever it makes changes in the power system network, and shall correct deficiencies found during the simulated restoration exercises.
Each facility owner shall report to the Area as per the reporting and test procedures prescribed in A3 Table 1 No and as scheduled by the CMAS. Within one month of the test completion, provide a written report outlining site location and date of test, test results and, if required, list reasons for failure, remedial actions to be undertaken and date by which work is to be completed. Subsequent retesting is to be carried out within the originally prescribed test interval. each Area shall maintain an inventory of key facilities and their critical components required for the energization of the basic minimum power system. Each Area shall include in the list of key facilities sufficient blackstart capability that is consistent with the strategy and priorities of their system restoration plan. In the event of a system blackout or loss of AC supply, the prompt restoration of the power system depends on the successful operation of critical components associated with key facilities. No
TFCO
EOP-005-0
R3
Each Transmission Operator shall develop restoration plans with a priority of restoring the integrity of the Interconnection.
A3 Sec. 4.10
No
TFCO
EOP-005-0
R4
EOP-005-0
R5
Each Transmission Operator shall coordinate its restoration plans with Balancing Authorities within its area, its Reliability Coordinator, and neighboring Transmission Operators and Balancing Authorities. Each Transmission Operator and Balancing Authority shall periodically test its telecommunication facilities needed to implement the restoration plan.
Reliability Coordinators and affected Transmission Operators, Generation Operators and Balancing Authority No shall coordinate their restoration actions. Testing of critical components associated with key facilities shall be performed at a frequency and for a duration that is sufficient to reasonably ensure that the critical components will function properly when isolated from all power sources not available during a partial or complete system blackout. As a minimum, the frequency and duration of testing is stated in Section 4.10.1 : 4.10.1.3 Substation and telecommunications backup power supplies batteries and generators 4.10.1.4 Control center and telecommunications center facilities No
No
TFCO
A3 Sec. 4.10
No
TFCO
Page 15 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
EOP-005-0
R6
Each Transmission Operator and Balancing Authority shall train its operating personnel A3 Sec. 4.10 in the implementation of the restoration plan. Such training shall include simulated exercises, if practicable.
System operators shall be knowledgeable of the strategy, priorities and procedures for implementing their system restoration plans
NPCC should No specifically say that training should be given in restoration plans and procedures No
TFCO
EOP-005-0
R7
Each Transmission Operator and Balancing Authority shall verify the restoration procedure by actual testing or by simulation.
6.3 Each facility owner/operator of key facilities containing critical components as identified by the Area shall complete the following: 6.3.1 Schedule and perform tests of key facilities in conformance with Area outage scheduling procedures and in accordance with Section 4.10.1 (test requirements).
No
TFCO
EOP-005-0
R8
Each Transmission Operator shall ensure the availability and location of black start capability within its area to meet the needs of the restoration plan.
A3 Sec. 4.10.1.1
No All facilities designated as having blackstart capability shall have this capability tested annually without dependencies on power sources not available during a partial or complete system blackout. Once the facility has been started, it shall continue to demonstrate the capability by operating in a stable condition while isolated from the power system for a minimum of ten minutes. The number of units within a facility that shall be blackstarted for this test is determined by the Area as needed by the Areas system restoration plan. Transmission egress capability to deliver blackstart generation to the next substation shall be verified
No
TFCO
EOP-005-0
R9
Following a disturbance in which one or more areas of the Bulk Electric System become RRP Sec. 5.4 isolated or blacked out, the affected Transmission Operators and Balancing Authorities shall begin immediately to return the Bulk Electric System to normal.
The Reliability Coordinator shall take actions in accordance with its restoration plan to restore normal operations once the operating emergency has been mitigated. Following a disturbance that caused the electrical isolation of one or more parts of the BES, control actions shall immediately be implemented to return the BES to normal (see below for TOP & BA actions).
No
No
TFCO
EOP-005-0
R9.1
EOP-005-0
R9.2
The affected Transmission Operators and Balancing Authorities shall work in RRP Sec. 5.4.1 Identical to R9.1 conjunction with their Reliability Coordinator(s) to determine the extent and condition of the isolated area(s). The affected Transmission Operators and Balancing Authorities shall take the necessary RRP Sec. 5.4.2 Identical to R9.2 with addition of a reference to the Reliability Coordinator actions to restore Bulk Electric System frequency to normal, including adjusting generation, placing additional generators online, or load shedding.
No
No
TFCO
No
No
TFCO
EOP-005-0
R9.3
The affected Balancing Authorities, working with their Reliability Coordinator(s), shall RRP Sec. 5.4.3 The RC shall immediately review the interchange schedules within the affected areas and make the necessary No immediately review the Interchange Schedules between those Balancing Authority Areas adjustments to facilitate restoration. The RC shall make all attempts to maintain the adjusted interchange or fragments of those Balancing Authority Areas within the separated area and make schedules irrespective of whether generation control is manual or automatic. adjustments as needed to facilitate the restoration. The affected BA shall make all attempts to maintain the adjusted Interchange Schedules, whether generation control is manual or automatic. The affected Transmission Operators shall give high priority to restoration of off-site power to nuclear stations. The affected Transmission Operators may resynchronize the isolated area(s) with the surrounding area(s) when the following conditions are met (see R9.5.1, etc. below): RRP Sec. 5.5 The affected TOPs and Balancing Authorities shall work in conjunction with their Reliability Coordinator to give the highest priority to restore the power supply to nuclear stations. No
No
TFCO
EOP-005-0
R9.4
No
TFCO
EOP-005-0
R9.5
RRP Sec. 5.5.4 The RC shall approve, communicate and coordinate the re-synchronization of major system islands or synchronization points so that the adjacent RC Areas are not burdened. Re-synchronization must consider voltage, frequency, phase angle, the size of the area being reconnected and the capacity of the transmission lines affecting the reconnection. RRP Sec. 5.4.4 See answer to R9.5 above See answer to R9.5 above
No
No
TFCO
EOP-005-0 EOP-005-0
R9.5.1 R9.5.2
No No
No No
TFCO TFCO
EOP-005-0 EOP-005-0
R9.5.3 R9.5.4
The size of the area being reconnected and the capacity of the transmission lines effecting RRP Sec. 5.4.4 the reconnection and the number of synchronizing points across the system are considered. Reliability Coordinator(s) and adjacent areas are notified and Reliability Coordinator RRP Sec. 5.4.4 approval is given. Load is shed in neighboring areas, if required, to permit successful interconnected system RRP Sec. 5.6 restoration.
See answer to R9.5 above The Reliability Coordinator, if necessary, shall direct the TOPs to reduce demand and shed firm load in their Area to assist the restoration process of a neighboring Area. The affected TOP may resynchronize the isolated area(s) with the surrounding area(s) when the following conditions are met: Load is shed in neighboring areas, if required, to permit successful interconnected system restoration.
No No
No No
TFCO TFCO
EOP-006-0
R1
Each Reliability Coordinator shall be aware of the restoration plan of each Transmission NPCC Regional The Reliability Coordinator shall be aware of and have a copy of the restoration plan of each Transmission Operator in its Reliability Coordinator Area in accordance with NERC and regional Reliability Plan Operator in its Reliability Coordinator Area in accordance with NERC and Regional requirements. requirements. (RRP) Sec. 5.2
No
No
TFCO
EOP-006-0
R2
The Reliability Coordinator shall monitor restoration progress and coordinate any needed RRP Sec. 5.2 assistance.
During system restoration, the RC shall monitor restoration progress and coordinate any needed assistance.
No
No
TFCO
Page 16 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
EOP-006-0
R3
The Reliability Coordinator shall have a Reliability Coordinator Area restoration plan that provides coordination between individual Transmission Operator restoration plans and that ensures reliability is maintained during system restoration events.
After a system collapse, restoration shall begin when the RC and its affected TOP, Generation Operators and No BA determine that they can proceed in an orderly and secure manner. RC and affected TOP, GOP and BA shall coordinate their restoration actions. Even though the restoration is to be expeditious, TOP, GOP and BA shall avoid any action that would cause a subsequent collapse of the BES. Customer load shall be restored as generation and transmission equipment becomes available, recognizing that load and generation must remain in balance at normal frequency. Identical to R4 No
No
TFCO
EOP-006-0
R4
The Reliability Coordinator shall serve as the primary contact for disseminating information regarding restoration to neighboring Reliability Coordinators and Transmission Operators or Balancing Authorities not immediately involved in restoration. Reliability Coordinators shall approve, communicate, and coordinate the resynchronizing of major system islands or synchronizing points so as not to cause a Burden on adjacent Transmission Operator, Balancing Authority, or Reliability Coordinator Areas. The Reliability Coordinator shall take actions to restore normal operations once an operating emergency has been mitigated in accordance with its restoration plan.
No
TFCO
EOP-006-0
R5
Identical to R5
No
No
TFCO
EOP-006-0
R6
The Reliability Coordinator shall take actions in accordance with its restoration plan to restore normal operations once the operating emergency has been mitigated. Following a disturbance that caused the electrical isolation of one or more parts of the BES, control actions shall be immediately implemented to return the BES to normal.
No
No
TFCO
EOP-007-0
R1
Each RRO shall establish and maintain a system BCP, as part of an overall coordinated Regional SRP. The Regional SRP shall include requirements for verification through analysis how system blackstart generating units shall perform their intended functions and shall be sufficient to meet SRP expectations. The RRO shall coordinate with and among other RRO as appropriate in the development of its BCP. The BCP shall include (see R1.1, etc. below): A requirement to have a database that contains all blackstart generators designated for use in an SRP within the respective areas. This database shall be updated on an annual basis. The database shall include the name, location, megawatt capacity, type of unit, latest date of test, and starting method.
NPCC Regional A System Blackstart Capability Plan (BCP) is necessary to ensure that the quantity and location of system No Reliability Plan blackstart generators are sufficient and that they can perform their expected functions as specified in overall (RRP) Sec. 4.9 coordinated Regional System Restoration Plans (SRP). Additional wording in this Section is identical to R1 at the left.
Yes
TFCO
EOP-007-0
R1.1
A3 Sec. 4.10 & 4.10 - Each Area shall maintain an inventory of key facilities and their critical components required for the 6.2 energization of the basic minimum power system. Each Area shall include in the list of key facilities sufficient blackstart capability that is consistent with the strategy and priorities of their system restoration plan. 6.2 - Each Area shall, annually, as scheduled by the NPCC CMAS, declare to NPCC that it has reviewed its list of key facilities and associated critical components and submit any revisions to NPCC. A3 Sec. 4.10.1.1
No
Yes
TFCO
EOP-007-0
R1.2
A requirement to demonstrate that blackstart units perform their intended functions as required in the Regional SRP. This requirement can be met through either simulation or testing. The BCP must consider the availability of designated BCP units and initial transmission switching requirements.
No All facilities designated as having blackstart capability shall have this capability tested annually without dependencies on power sources not available during a partial or complete system blackout. Once the facility has been started, it shall continue to demonstrate the capability by operating in a stable condition while isolated from the power system for a minimum of ten minutes. Transmission egress capability to deliver blackstart generation to the next substation shall be verified . See below No
Yes
TFCO
EOP-007-0
Establish, Maintain and Document a Regional Blackstart Capability Plan Establish, Maintain and Document a Regional Blackstart Capability Plan
R1.3
Blackstart unit testing requirements including, but not limited to (see R1.3.1, etc. below): A3 Sec. 4.10.1.1
Yes
TFCO
EOP-007-0
R1.3.1
A3 Sec. 4.10.1.1
All facilities designated as having blackstart capability shall have this capability tested annually. The number of units within a facility that shall be blackstarted for this test is determined by the Area as needed by the Areas system restoration plan.
No
NPCC does not specify Yes that a minimum one third of the units be tested each year Yes
TFCO
EOP-007-0
R1.3.2
Type of test required, including the requirement to start when isolated from the system. A3 Sec. 4.10.1.1
All facilities designated as having blackstart capability shall have this capability tested annually without dependencies on power sources not available during a partial or complete system blackout . Once the facility has been started, it shall continue to demonstrate the capability by operating in a stable condition while isolated from the power system for a minimum of ten minutes Once the facility has been started, it shall continue to demonstrate the capability by operating in a stable condition while isolated from the power system for a minimum of ten minutes.
No
TFCO
EOP-007-0
Establish, Maintain and Document a Regional Blackstart Capability Plan Establish, Maintain and Document a Regional Blackstart Capability Plan Establish, Maintain and Document a Regional Blackstart Capability Plan
R1.3.3
A3 Sec. 4.10.1.1
No
Yes
TFCO
EOP-007-0
R1.4
A requirement to review and update the Regional BCP at least every five years.
none
None
No
Yes
TFCO
EOP-007-0
R2
The Regional Reliability Organization shall provide documentation of its system BCPs to NERC within 30 calendar days of a request.
A3 Sec. 6.4
Each Area shall review reports submitted by its owner / operators and annually submit a declaration of compliance to NPCC, within sixty days of a request, for the previous calendar year. Each Area shall maintain records for the lesser of, three years or the testing interval, to facilitate random audits and ensure compliance to the testing program.
No
NPCC requires a 60 day Yes reporting period instead of the 30 days required by NERC
TFCO
Page 17 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
EOP-008-0
R1
Each Reliability Coordinator, Transmission Operator and Balancing Authority shall have NPCC Regional a plan to continue reliability operations in the event its control center becomes Reliability Plan inoperable. The contingency plan must meet the following requirements (see R1.1, etc. (RRP) Sec. 4.7 below):
Each Reliability Coordinator, Transmission Operator and Balancing Authority shall have a plan to continue reliability operations in the event its control center becomes inoperable. The contingency plan must meet the requirements specified in Reliability Standard EOP-008-0 . The plan shall be reviewed and updated annually. Interim provisions must be included if it is expected to take more than one hour to implement the contingency plan for loss of primary control facility. See answer to R1 above.
No
TFCO
EOP-008-0
Plans for Loss of Control Center Functionality Plans for Loss of Control Center Functionality Plans for Loss of Control Center Functionality
R1.1
The contingency plan shall not rely on data or voice communication from the primary control facility to be viable.
No
No
TFCO
EOP-008-0
R1.2
EOP-008-0
R1.3
The plan shall include procedures and responsibilities for providing basic tie line control RRP Sec. 4.7 and procedures and for maintaining the status of all inter-area schedules, such that there is an hourly accounting of all schedules. The contingency plan must address monitoring and control of critical transmission RRP Sec. 4.7 facilities, generation control, voltage control, time and frequency control, control of critical substation devices, and logging of significant power system events. The plan shall list the critical facilities. The plan shall include procedures and responsibilities for maintaining basic voice communication capabilities with other areas. The plan shall include procedures and responsibilities for conducting periodic tests, at least annually, to ensure viability of the plan. The plan shall include procedures and responsibilities for providing annual training to ensure that operating personnel are able to implement the contingency plans. The plan shall be reviewed and updated annually. RRP Sec. 4.7
No
No
TFCO
No
No
TFCO
EOP-008-0
Plans for Loss of Control Center Functionality Plans for Loss of Control Center Functionality Plans for Loss of Control Center Functionality Plans for Loss of Control Center Functionality Plans for Loss of Control Center Functionality Documentation of Blackstart Generating Unit Test Results
R1.4
No
No
TFCO
EOP-008-0
R1.5
No
No
TFCO
EOP-008-0
R1.6
No
No
TFCO
EOP-008-0
R1.7
No
No
TFCO
EOP-008-0
R1.8
Interim provisions must be included if it is expected to take more than one hour to implement the contingency plan for loss of primary control facility. The Generator Operator of each blackstart generating unit shall test the startup and operation of each system blackstart generating unit identified in the BCP as required in the Regional BCP (Reliability Standard EOP-007-0_R1). Testing records shall include the dates of the tests, the duration of the tests, and an indication of whether the tests met Regional BCP requirements.
No
No
TFCO
EOP-009-0
R1
A3 Sec. 4.10 & 4.10 - Each Area shall have a system restoration plan in accordance with NPCC Criteria, Guides and 4.10.1.1 Procedures, and in conjunction with applicable NERC Operating Policies, Measures and Standards. In the event of a system blackout or loss of AC supply, the prompt restoration of the power system depends on the successful operation of critical components associated with key facilities. Testing of critical components associated with key facilities shall be performed at a frequency and for a duration that is sufficient to reasonably ensure that the critical components will function properly when isolated from all power sources not available during a partial or complete system blackout. As a minimum, this frequency and duration of testing is stated in Section 4.10.1: 4.10.1.1 - All facilities designated as having blackstart capability shall have this capability tested annually. Once the facility has been started, it shall continue to demonstrate the capability by operating in a stable condition while isolated from the power system for a minimum of 10 minutes
No
No
TFCO
EOP-009-0
R2
The Generator Owner or Generator Operator shall provide documentation of the test results of the startup and operation of each blackstart generating unit to the Regional Reliability Organizations and upon request to NERC.
A3 Sec. 6.4
Each Area shall review reports submitted by its owner / operators and annually submit a declaration of No compliance to NPCC, within sixty days of a request, for the previous calendar year. Each Area shall maintain records for the lesser of, three years or the testing interval, to facilitate random audits and ensure compliance to the testing program. Generation and Transmission Facility Owners must develop, and maintain data for their facilities suitable for load flow and dynamics modeling and analysis as required by the NPCC Working Groups. Facilities owners must also develop and maintain short-circuit data. Facility owners must provide this data, in a suitable format, on request. Data provided by facility owners must comply with the NERC MMWG and SDDWG Procedural Documents and the procedures herein. No NPCC does not specify compliance with the latest NERC Facility Connection Requirements.
No
TFCO
FAC-001-0
R1
The Transmission Owner shall document, maintain, and publish facility connection C29 Sec. 2.2 requirements to ensure compliance with NERC Reliability Standards and applicable Regional Reliability Organization, subregional, Power Pool, and individual Transmission Owner planning criteria and facility connection requirements. The Transmission Owners facility connection requirements shall address connection requirements for (refer to R1.1, etc. below): Generation facilities Transmission facilities End User facilities C29 Sec. 2.2 C29 Sec. 2.2 C29 Sec. 2.3
No
TFSS
No No
No No No
Load-serving entities shall provide actual and forecast demands for their respective customers for steady state No and dynamics system modeling in a timely manner. Purchasers, sellers, marketers and load-serving entities shall provide their existing and future contracted firm (non-recallable reserved) capacity transactions (including sources, sinks, amounts, duration, associated transmission, etc.) for s-state and dyn. sys. model. in a timely manner.
Page 18 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
FAC-001-0
R2
The Transmission Owners facility connection requirements shall address, but are not limited to, the following items (refer to R2.1 below):
NERC Planning Standards Section II.C, (Facility Ratings), contains the following Standard: S1 Electrical No facilities used in the production, transmission, storage and delivery of electricity shall be rated in compliance with applicable Regional, sub-regional, power pool, and individual system planning criteria and guides.
NPCC does not require No that facility connection requirements meet the new Version 0 Standards, replacing the Planning Standards
TFSS
FAC-001-0
R2.1
Provide a written summary of its plans to achieve the required system performance as described above throughout the planning horizon (refer to R2.1.1, R2.1.2, etc. below): Procedures for coordinated joint studies of new facilities and their impacts on the interconnected transmission systems.
none
None
No
No
TFSS
FAC-001-0
R2.1.1
B4 Sec. 4.0
Each Area is required to present an annual transmission review to TFSS. However, the review presented by the Area may be one of three types: a Comprehensive (or Full) Review, an Intermediate (or Partial) Review, or an Interim Review (the type of Review depending on the extent of the system changes ). None
No
No
TFSS
FAC-001-0
R2.1.2
Procedures for notification of new or modified facilities to others (those responsible for the reliability of the interconnected transmission systems) as soon as feasible. Voltage level and MW and MVAR capacity or demand at point of connection.
none
No
No
TFSS
FAC-001-0
R2.1.3
C29 Sec. 3.1 & 3.1 Facility owners shall document the methodology for determining facility ratings, including delineation No 3.2 and justification of assumptions, standards, and practices used in establishing the ratings. The documentation must state the ratings and their basis applicable to each of the six base case model types (summer peak, winter peak, etc.) as defined in the MMWG Procedural Manual. 3.2 Facility owners shall provide facility ratings (applicable normal and emergency) for all facilities required for system modeling (as defined in this Procedure) to NPCC appropriate for base case development as requested in a timely fashion.
No
TFSS
Facility Connection Requirements Facility Connection Requirements Facility Connection Requirements Facility Connection Requirements Facility Connection Requirements Facility Connection Requirements Facility Connection Requirements Facility Connection Requirements
Breaker duty and surge protection System protection and coordination Metering and telecommunications Grounding and safety issues Insulation and insulation coordination Voltage, Reactive Power, and power factor control.
None In cases where protection systems and control settings constitute a loading limit on a facility, this limit shall become the rating for that facility None None None None None
No No No No No No No
No No No No No No No No
C29 Sec. 3.3. & 3.3 The rating of a system facility (eg. Transmission line, transformer, etc.) shall not exceed the rating of the No 3.6 most limiting series element in the circuit or path of the facility, including terminal connections and associated equipment. 3.6 Facility ratings should be based on or adhere to applicable national electrical codes and electric industry rating practices consistent with good engineering practice. none none None None No No
FAC-001-0 FAC-001-0
No NPCC does not require No this in terms of Facility Connection requirements See R2.1.13 above See R2.1.13 above No No No No
TFSS TFSS
Facility Connection Requirements Facility Connection Requirements Facility Connection Requirements Facility Connection Requirements
R2.1.14 Operational issues ( abnormal frequency and voltages) R2.1.15 Inspection requirements for existing or new facilities R2.1.16 Communications and procedures during normal and emergency operating conditions. R3 The Transmission Owner shall maintain and update its facility connection requirements as required. The Transmission Owner shall make documentation of these requirements available to the users of the transmission system, the Regional Reliability Organization, and NERC on request (five business days).
No No No
C29 Sec. 3.1 & 3.1 Facility owners shall document the methodology for determining facility ratings, including delineation No 3.2 and justification of assumptions, standards, and practices used in establishing the ratings. The documentation must state the ratings and their basis applicable to each of the six base case model types (summer peak, winter peak, etc.) as defined in the MMWG Procedural Manual. 3.2 Facility owners shall provide facility ratings (applicable normal and emergency) for all facilities required for system modeling (as defined in this Procedure) to NPCC appropriate for base case development as requested in a timely fashion.
Page 19 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
FAC-002-0
R1
The Generator Owner, Transmission Owner, Distribution Provider, and Load-Serving C29 Sec. 2.2 Entity seeking to integrate generation facilities, transmission facilities, and electricity enduser facilities shall each coordinate and cooperate on its assessments with its Transmission Planner and Planning Authority. The assessment shall include (see R1.1, R1.2, etc. below): Evaluation of the reliability impact of the new facilities and their connections on the interconnected transmission systems. B4 Sec. 4.0
Generation and Transmission Facility Owners must develop, and maintain data for their facilities suitable for load flow and dynamics modeling and analysis as required by the NPCC Working Groups. Facilities owners must also develop and maintain short-circuit data. Facility owners must provide this data, in a suitable format, on request. Data provided by facility owners must comply with the NERC MMWG and SDDWG Procedural Documents and the procedures herein. Each Area is required to present an annual transmission review to TFSS. However, the review presented by the Area may be one of three types: a Comprehensive (or Full) Review, an Intermediate (or Partial) Review, or an Interim Review (type of Review depending on the extent.. changes ). 2.2 - Refer to the above words in response to R1.
NPCC does not specify compliance with the latest NERC Facility Connection Requirements.
No
TFSS
FAC-002-0
Coordination of Plans For New Generation, Transmission and EndUser Coordination of Plans For New Generation, Transmission and EndUser
R1.1
No
No
TFSS
FAC-002-0
R1.2
Ensurance of compliance with NERC Reliability Standards and applicable Regional, subregional, Power Pool, and individual system planning criteria and facility connection requirements.
No
NPCC may need to revise its FAC requirements, they are less specific than the new Version 0 Standards
No
TFSS
FAC-002-0
Coordination of Plans For New Generation, Transmission and EndUser Coordination of Plans For New Generation, Transmission and EndUser
R1.2
A2 Sec. 1.0
1.0 Criteria described in this document are to be used in the design and operation of the BPS. These criteria meet or exceed the NERC Policies and Standards. These criteria are applicable to all entities which are part of or make use of the BPS. Each Area is required to present an annual transmission review to TFSS. However, the review presented by the Area may be one of three types: a Comprehensive (or Full) Review, an Intermediate (or Partial) Review, or an Interim Review (the type of Review depending on the extent of the system changes ). No
No
TFSS
FAC-002-0
R1.3
Evidence that the parties involved in the assessment have coordinated and cooperated on B4 Sec. 4.0 the assessment of the reliability impacts of new facilities on the interconnected transmission systems. While these studies may be performed independently, the results shall be jointly evaluated and coordinated by the entities involved.
NPCCs Facility No Requirements deal more with Area to NPCC relations rather than TOP, BA, GOP and LSE relations with each other.
TFSS
FAC-002-0
R1.4
Evidence that the assessment included steady-state, short-circuit, and dynamics studies as A2 Sec. 5.1, 5.2 5.1 (Stability Assessment) - Stability of the BPS shall be maintained during and following the most severe of No necessary to evaluate system performance in accordance with Reliability Standard TPL- & 5.3 the contingencies stated below 5.2 (Steady State Assessment) Each Area shall design its system in 001-0. accordance with these criteria and its own control procedures and criteria, and coordinate these with adjacent Areas and control areas. 5.3 (Fault Current Assessment) Each Area shall establish procedures and implement a system design that ensures equipment capabilities are adequate for fault current levels with all transmission and generation facilities in service for all potential operating conditions, and coordinate these procedures with adjacent Areas and Regions.
NPCC criteria doesnt specifically state that these criteria apply to Generation Owner, Transmission Owner, Distribution Provider and LSE relations with their Transmission Planner and Planning Authority.
No
TFSS
FAC-002-0
R1.5
Documentation that the assessment included study assumptions, system performance, alternatives considered, and jointly coordinated recommendations.
B4 Sec. 4.0
Each Area is required to present an annual transmission review to TFSS. However, the review presented by the Area may be one of three types: a Comprehensive (or Full) Review, an Intermediate (or Partial) Review, or an Interim Review (the type of Review depending on the extent of the system changes ).
No
NPCC Criteria doesnt deal with internal Area relations to the TOP or to the new Version 0 Standards
No
TFSS
FAC-002-0
R2
The Planning Authority, Transmission Planner, Generator Owner, Transmission Owner, none Load- Serving Entity, and Distribution Provider shall each retain its documentation (of its evaluation of the reliability impact of the new facilities and their connections on the interconnected transmission systems) for three years and shall provide the documentation to the Regional Reliability Organization(s) Regional Reliability Organization(s) and NERC on request (within 30 calendar days).
None
Yes
No
TFSS
FAC-003-0
R1
Each Transmission Owner shall have a vegetation management program to prevent transmission line contact with vegetation. The vegetation management program shall include the following three elements (see R1.1, R1.2, etc. below):
NPCC Regional Transmission Owners shall have vegetation management program to prevent transmission line contact with Reliability Plan vegetation, and to ensure that certain vegetation-related outages are reported to the appropriate Reliability (August, 2005) Coordinators Regional Reliability Organization. Sec. 9.0
No
No
TFCO
No No No
No No No
Page 20 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
FAC-003-0
R2
Each Transmission Owner shall report to its Regional Reliability Organization all vegetation related outages on transmission circuits 200 kV and higher and any other lower voltage lines designated by the Regional Reliability Organization to be critical to the reliability of the electric system.
All vegetation-related trips on lines of 200 kV or higher and any other lower voltage lines designated by NPCC (TFCO) to be critical to the reliability of the electric system will be reported by each RC to NPCC on a monthly basis by the 20th of the following month.
Yes
TFCO
FAC-003-1
R1 The Transmission Owner shall prepare, and keep current, a formal transmission vegetation management program (TVMP). The TVMP shall include the Transmission Owners objectives, practices, approved procedures, and work specifications R1.1 The TVMP shall define a schedule for and the type (aerial, ground) of ROW vegetation inspections. This schedule should be flexible enough to adjust for changing conditions. The inspection schedule shall be based on the anticipated growth of vegetation and any other environmental or operational factors that could impact the relationship of vegetation to the Transmission Owners transmission lines.
TFCO
FAC-003-1
TFCO
FAC-003-1
R1.2 The Transmission Owner, in the TVMP, shall identify and document clearances between vegetation and any overhead, ungrounded supply conductors, taking into consideration transmission line voltage, the effects of ambient temperature on conductor sag under maximum design loading, and the effects of wind velocities on conductor sway. Specifically, the Transmission Owner shall establish clearances to be achieved at the time of vegetation management work identified herein as Clearance 1, and shall also establish and maintain a set of clearances identified herein as Clearance 2 to prevent flashover between vegetation and overhead ungrounded supply conductors.
TFCO
FAC-003-1
R1.2.1 Clearance 1 The Transmission Owner shall determine and document appropriate clearance distances to be achieved at the time of transmission vegetation management work based upon local conditions and the expected time frame in which the Transmission Owner plans to return for future vegetation management work. Local conditions may include, but are not limited to: operating voltage, appropriate vegetation management techniques, fire risk, reasonably anticipated tree and conductor movement, species types and growth rates, species failure characteristics, local climate and rainfall patterns, line terrain and elevation, location of the vegetation within the span, and worker approach distance requirements. Clearance 1 distances shall be greater than those defined by Clearance 2 below.
TFCO
FAC-003-1
R1.2.2 Clearance 2 The Transmission Owner shall determine and document specific radial clearances to be maintained between vegetation and conductors under all rated electrical operating conditions. These minimum clearance distances are necessary to prevent flashover between vegetation and conductors and will vary due to such factors as altitude and operating voltage. These Transmission Owner-specific minimum clearance distances shall be no less than those set forth in the Institute of Electrical and Electronics Engineers (IEEE) Standard 516-2003 (Guide for Maintenance Methods on Energized Power Lines) and as specified in its Section 4.2.2.3, Minimum Air Insulation Distances without Tools in the Air Gap. R1.2.2.1 Where transmission system transient overvoltage factors are not known, clearances shall be derived from Table 5, IEEE 516-2003, phase-to-ground distances, with appropriate altitude correction factors applied. R1.2.2.2 Where transmission system transient overvoltage factors are known, clearances shall be derived from Table 7, IEEE 516-2003, phase-to-phase voltages, with appropriate altitude correction factors applied. R1.3 All personnel directly involved in the design and implementation of the TVMP shall hold appropriate qualifications and training, as defined by the Transmission Owner, to perform their duties. R1.4 Each Transmission Owner shall develop mitigation measures to achieve sufficient clearances for the protection of the transmission facilities when it identifies locations on the ROW where the Transmission Owner is restricted from attaining the clearances specified in Requirement 1.2.1. R1.5 Each Transmission Owner shall establish and document a process for the immediate communication of vegetation conditions that present an imminent threat of a transmission line outage. This is so that action (temporary reduction in line rating, switching line out of service, etc.) may be taken until the threat is relieved.
TFCO
FAC-003-1
Vegetation Management Program Vegetation Management Program Vegetation Management Program Vegetation Management Program
TFCO
FAC-003-1
TFCO
FAC-003-1
TFCO
FAC-003-1
TFCO
FAC-003-1
TFCO
Page 21 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
FAC-003-1
R2
TFCO
FAC-003-1
R3
FAC-003-1
R3.1
The Transmission Owner shall create and implement an annual plan for vegetation management work to ensure the reliability of the system. The plan shall describe the methods used, such as manual clearing, mechanical clearing, herbicide treatment, or other actions. The plan should be flexible enough to adjust to changing conditions, taking into consideration anticipated growth of vegetation and all other environmental factors that may have an impact on the reliability of the transmission systems. Adjustments to the plan shall be documented as they occur. The plan should take into consideration the time required to obtain permissions or permits from landowners or regulatory authorities. Each Transmission Owner shall have systems and procedures for documenting and tracking the planned vegetation management work and ensuring that the vegetation management work was completed according to work specifications. The Transmission Owner shall report quarterly to its RRO, or the RROs designee, sustained transmission line outages determined by the Transmission Owner to have been caused by vegetation. Multiple sustained outages on an individual line, if caused by the same vegetation, shall be reported as one outage regardless of the actual number of outages within a 24-hour period.
TFCO
TFCO
FAC-003-1
R3.2 The Transmission Owner is not required to report to the RRO, or the RROs designee, certain sustained transmission line outages caused by vegetation: (1) Vegetation related outages that result from vegetation falling into lines from outside the ROW that result from natural disasters shall not be considered reportable (examples of disasters that could create non-reportable outages include, but are not limited to, earthquakes, fires, tornados, hurricanes, landslides, wind shear, major storms as defined either by the Transmission Owner or an applicable regulatory body, ice storms, and floods), and (2) Vegetation-related outages due to human or animal activity shall not be considered reportable (examples of human or animal activity that could cause a non-reportable outage include, but are not limited to, logging, animal severing tree, vehicle contact with tree, arboricultural activities or horticultural or agricultural activities, or removal or digging of vegetation). The outage information provided by the Transmission Owner to the RRO, or the RROs designee, shall include at a minimum: the name of the circuit(s) outaged, the date, time and duration of the outage; a description of the cause of the outage; other pertinent comments; and any countermeasures taken by the Transmission Owner. An outage shall be categorized as one of the following: Category 1 Grow-ins: Outages caused by vegetation growing into lines from vegetation inside and/or outside of the ROW; Category 2 Fall-ins: Outages caused by vegetation falling into lines from inside the ROW; Category 3 Fall-ins: Outages caused by vegetation falling into lines from outside the ROW. The RRO shall report the outage information provided to it by Transmission Owner's, as required by Requirement 3, quarterly to NERC, as well as any actions taken by the RRO as a result of any of the reported outages. The Transmission Owner and Generator Owner shall each document the methodology(ies) used to determine its electrical equipment and Facility Ratings. Further, the methodology(ies) shall comply with applicable Regional Reliability Organization requirements. The documentation shall address and include (see R1.1 below): C29 Sec. 3.1 & 3.1 - Facility owners shall document the methodology for determining facility ratings, including delineation No 3.0 and justification of assumptions, standards, and practices used in establishing the ratings. The documentation must state the ratings and their basis applicable to each of the six base case model types (summer peak, winter peak, etc.) as defined in the MMWG Procedural Manual. 3.0 - Electrical facilities used in the production, transmission, storage and delivery of electricity shall be rated in compliance with applicable Regional, sub-regional, power pool, and individual system planning criteria and guides. No
TFCO
FAC-003-1
R3.3
TFCO
FAC-003-1
R3.4
FAC-003-1
R4
FAC-004-0
R1
TFSS
FAC-004-0
FAC-004-0
FAC-004-0
Methodologies for Determining Electrical Facility Ratings Methodologies for Determining Electrical Facility Ratings Methodologies for Determining Electrical Facility Ratings
R1.1
The methodology(ies) used to determine equipment and Facility Rating of the items listed for both normal and emergency conditions (see R1.1.1, R1.1.2, etc. below): Transmission circuits.
Facility owners shall provide facility ratings (applicable normal and emergency) for all facilities required for system modeling to NPCC appropriate for base case development as requested in a timely fashion. AC Transmission Line or Circuit (overhead and underground)
No
No
TFSS
R1.1.1
No
No
TFSS
R1.1.2
Transformers
No
No
TFSS
Page 22 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
FAC-004-0
FAC-004-0
Methodologies for Determining Electrical Facility Ratings Methodologies for Determining Electrical Facility Ratings
R1.1.3
C29 Sec. 2.2.10 Reactive Compensation (shunt and series capacitors and reactors)
No
TFSS
R1.1.4
Yes
NPCC is more stringent No by including breakers, CTs etc. as part of its Line or Transformer rating assessments. NERC does not mention rating a Bus at all
TFSS
FAC-004-0
FAC-004-0
FAC-004-0
FAC-004-0
FAC-004-0
FAC-004-0
FAC-004-0
Methodologies for Determining Electrical Facility Ratings Methodologies for Determining Electrical Facility Ratings Methodologies for Determining Electrical Facility Ratings Methodologies for Determining Electrical Facility Ratings Methodologies for Determining Electrical Facility Ratings Methodologies for Determining Electrical Facility Ratings Methodologies for Determining Electrical Facility Ratings Methodologies for Determining Electrical Facility Ratings Electrical Facility Ratings for System Modeling
R1.1.5
VAR compensators
C29 Sec. 2.2.11 Detailed dynamics data for all other facilities of significance and pertinent to dynamic simulations such as static-var compensators, FACTS devices, synchronous motors, HVDC facilities, relays loads, etc. C29 Sec. 2.2.11 See R1.1.5 above
No
No
TFSS
R1.1.6
No
No
TFSS
R1.1.7
C29 Sec. 2.2.12 Models of protective relays characteristics on all major interfaces
No
No
TFSS
R1.2
The Rating of a facility shall not exceed the Rating(s) of the most Limiting Element(s) in C29 Sec. 3.3 the circuit, 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 and jointly-operated facilities shall be coordinated among the joint owners and joint operators resulting in a single set of Ratings. C29 Sec. 3.4
No
No
TFSS
R1.3
Identical to R1.3
No
No
TFSS
R1.4
Identical to R1.4
No
No
TFSS
R1.5
The documentation shall identify the assumptions used to determine each of the C29 Sec. 3.1 equipment and Facility Ratings, including references to industry Rating practices and standards (e.g., ANSI, IEEE, etc.). Seasonal Ratings and variations in assumptions shall be included. The Transmission Owner and Generator Owner shall provide documentation of the methodology(ies) used to determine its transmission equipment and Facility Ratings to the RRO(s) and NERC on request (30 calendar days). The transmission Owner, and Generator Owner shall each have on file or be able to readily provide, a document or database identifying the Normal and Emergency Ratings of all of its transmission facilities (e.g., lines, transformers, terminal equipment, and storage devices) that are part of the interconnected transmission systems. Seasonal variations in Ratings shall be included as appropriate. The Ratings shall be consistent with the entitys methodology(ies) for determining Facility Ratings and shall be updated as facility changes occur. C29 Sec. 3.2
Facility owners shall document the methodology for determining facility ratings, including justification of No assumptions, standards and practices used in establishing the ratings. The documentation must state the ratings and their basis applicable to each of the six base case model types (summer peak, winter peak, etc.) as defined in the MMWG Manual. Facility owners shall provide facility ratings (applicable normal and emergency) for all facilities required for system modeling to NPCC appropriate for base case development as requested in a timely fashion. The requirement to submit data to NERC is being fulfilled through the NPCC base case development effort. Yes NPCC does not specify 30 days
No
TFSS
FAC-004-0
R2
No
TFSS
FAC-005-0
R1
C29 Sec. 3.2 & 3.2 Facility owners shall provide facility ratings (applicable normal and emergency) for all facilities No 3.1 required for system modeling (as defined in this Procedure) to NPCC appropriate for base case development as requested in a timely fashion. 3.1 The documentation must state the ratings and their basis applicable to each of the six base case model types (summer peak, winter peak, etc.) as defined in the MMWG Procedural Manual. C29 Sec. 3.1 & 3.1 - Facility owners shall document the methodology for determining facility ratings, including delineation No 3.0 and justification of assumptions, standards, and practices used in establishing the ratings. The documentation must state the ratings and their basis applicable to each of the six base case model types (sum. peak, wint. peak, etc.) as defined in the MMWG PMan. 3.0 - Electrical facilities used in the production, transmission, storage and delivery of electricity shall be rated in compliance with applicable Regional, sub-regional, power pool, and individual system planning criteria and guides. C29 Sec. 2.2 Generation and Transmission Facility Owners must develop, and maintain data for their facilities suitable for load flow and dynamics modeling and analysis as required by the NPCC Working Groups. Facilities owners must also develop and maintain short-circuit data. Facility owners must provide this data, in a suitable format, on request. Data provided must comply with the NERC MMWG and SDDWG Procedural Documents and this Procedure. Yes NPCC is less stringent because it does not specify a 30-day time limit on data provision.
No
TFSS
FAC-005-0
R1.1
No
TFSS
FAC-005-0
R2
The Transmission Owner and Generator Owner shall provide the Normal and Emergency Facility Ratings of all its transmission facilities to the Regional Reliability Organization(s) and NERC on request (30 calendar days).
No
TFSS
FAC-008-1
R1 The Transmission Owner and Generator Owner shall each document its current methodology used for developing Facility Ratings (Facility Ratings Methodology) of its solely and jointly owned Facilities. The methodology shall include all of the following:
TFSS
TFSS R1.1. A statement that a Facility Rating shall equal the most limiting applicable Equipment Rating of the individual equipment that comprises that Facility. R1.2. The method by which the Rating (of major BES equipment that comprises a Facility) is determined.
TFSS
Page 23 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
R1.2.1. The scope of equipment addressed shall include, but not be limited to, generators, transmission conductors, transformers, relay protective devices, terminal equipment, and series and shunt compensation devices. R1.2.2. The scope of Ratings addressed shall include, as a minimum, both Normal and Emergency Ratings. R1.3. Consideration of the following: R1.3.1. Ratings provided by equipment manufacturers. R1.3.2. Design Criteria (e.g., including applicable references to industry Rating practices such as manufacturers warranty, IEEE, ANSI or other Standards). R1.3.3. Ambient conditions. R1.3.4. Operating limitations. R1.3.5. Other assumptions. FAC-008-1 Facility Ratings Methodology R2 The Transmission Owner and Generator Owner shall each make its Facility Ratings Methodology available for inspection and technical review by those Reliability Coordinators, Transmission Operators, Transmission Planners, and Planning Authorities that have responsibility for the area in which the associated Facilities are located, within 15 business days of receipt of a request. R3 Establish and communicate Facility Ratings R1 The Transmission Owner and Generator Owner shall each establish Facility Ratings for its solely and jointly owned Facilities that are consistent with the associated Facility Ratings Methodology. The Transmission Owner and Generator Owner shall each provide Facility Ratings for its solely and jointly owned Facilities that are existing Facilities, new Facilities, modifications to existing Facilities and re-ratings of existing Facilities to its associated Reliability Coordinator(s), Planning Authority(ies), Transmission Planner(s), and Transmission Operator(s) as scheduled by such requesting entities. FAC-012-1 Transfert Capability Methodology R1 The Reliability Coordinator and Planning Authority shall each document its current methodology used for developing its inter-regional and intra-regional Transfer Capabilities (Transfer Capability Methodology). The Transfer Capability Methodology shall include all of the following: R1.1. A statement that Transfer Capabilities shall respect all applicable System Operating Limits (SOLs). R1.2. A definition stating whether the methodology is applicable to the planning horizon or the operating horizon. R1.3. A description of how each of the following is addressed, including any reliability margins applied to reflect uncertainty with projected BES conditions: R1.3.1. Transmission system topology R1.3.2. System demand R1.3.3. Generation dispatch FAC-012-1 Transfert Capability Methodology R2 R1.3.4. Current and projected transmission uses The Reliability Coordinator shall issue its Transfer Capability Methodology, and any changes to that methodology, prior to the effectiveness of such changes, to all of the following: R2.1. Each Adjacent Reliability Coordinator and each Reliability Coordinator that indicated a reliability-related need for the methodology. R2.2. Each Planning Authority and Transmission Planner that models any portion of the Reliability Coordinators Reliability Coordinator Area. R2.3. Each Transmission Operator that operates in the Reliability Coordinator Area. FAC-012-1 Transfert Capability Methodology R3 The Planning Authority shall issue its Transfer Capability Methodology, and any changes to that methodology, prior to the effectiveness of such changes, to all of the following: R3.1. Each Transmission Planner that works in the Planning Authoritys Planning Authority Area. R3.2. Each Adjacent Planning Authority and each Planning Authority that indicated a reliability-related need for the methodology. R3.3. Each Reliability Coordinator and Transmission Operator that operates any portion of the Planning Authoritys Planning Authority Area.
TFSS
FAC-008-1 FAC-009-1
TFSS TFSS
R2
TFSS
TFSS
Page 24 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
FAC-012-1
R4 If a recipient of the Transfer Capability Methodology provides documented technical comments on the methodology, the Reliability Coordinator or Planning Authority shall provide a documented response to that recipient within 45 calendar days of receipt of those comments. The response shall indicate whether a change will be made to the Transfer Capability Methodology and, if no change will be made to that Transfer Capability Methodology, the reason why. The Reliability Coordinator and Planning Authority shall each establish a set of interregional and intra-regional Transfer Capabilities that is consistent with its current Transfer Capability Methodology.
TFSS
FAC-013-1
Establish and Communicate Transfer Capabilities Establish and Communicate Transfer Capabilities
R1
TFSS
TFSS FAC-013-1 R2 The Reliability Coordinator and Planning Authority shall each provide its inter-regional and intra-regional Transfer Capabilities to those entities that have a reliability-related need for such Transfer Capabilities and make a written request that includes a schedule for delivery of such Transfer Capabilities as follows: TFSS R2.1. The Reliability Coordinator shall provide its Transfer Capabilities to its associated Regional Reliability Organization(s), to its adjacent Reliability Coordinators, and to the Transmission Operators, Transmission Service Providers and Planning Authorities that work in its Reliability Coordinator Area. R2.2. The Planning Authority shall provide its Transfer Capabilities to its associated Reliability Coordinator(s) and Regional Reliability Organization(s), and to the Transmission Planners and Transmission Service Provider(s) that work in its Planning Authority Area. The Load-serving Purchasing-Selling Entity shall be responsible for ensuring Tags are submitted for: All Interchange Transactions that are between Balancing Authority Areas All transfers that are entirely within a Balancing Authority Area using Point-to-Point Transmission Service (including all grandfathered and non-Order 888 Point-to-Point Transmission Service). All Dynamic Schedules at the expected average MW profile for each hour. The Sink Balancing Authority shall be responsible for ensuring a Tag is provided: TFSS TFSS
Interchange Transaction Tagging Interchange Transaction Tagging Interchange Transaction Tagging Interchange Transaction Tagging Interchange Transaction Tagging Interchange Transaction Tagging Interchange Transaction Tagging
R1 R1.1 R1.2
No No No
No No No
none none
No No No No
No No No No
If a Purchasing-Selling Entity is not involved in the Transaction, such as delivery from a none jointly owned generator. To replace unexpected generation loss, such as through prearranged reserve sharing none agreements or other arrangements. If the duration of the Emergency Transaction to replace the generation loss is less than 60 minutes, then the Transaction shall be exempt from Tagging. All bilateral inadvertent interchange payback. none
INT-001-0 INT-001-0
Interchange Transaction Tagging Interchange Transaction Tagging Interchange Transaction Tagging Interchange Transaction Tagging
R2.3 R3
None None
No No
No No
TFCO TFCO
The Purchasing Selling Entity responsible for submitting the Tag shall submit all Tags to none the Sink BA according to timing tables in Attachment 1-INT-001-0. The Balancing Authority or Purchasing-Selling Entity responsible for submitting the Tag none shall include the reliability data listed in Attachment 2-INT-001-0 in the Tag. Each Purchasing-Selling Entity with title to an Interchange Transaction shall have, or shall arrange to have, personnel directly and immediately available for notification of Interchange Transaction changes. These personnel shall be available from the time that the title to the Interchange Transaction is acquired until the Interchange Transaction has been completed. The Sink Balancing Authority shall ensure that all Tags and any modifications to Tags are provided via a secure network to the following entities on the Scheduling Path: none
INT-001-0
R4
None
No
No
TFCO
INT-001-0
R5
None
No
No
TFCO
INT-002-0
Interchange Transaction Tag Communication and Reliability Assessment Interchange Transaction Tag Communication and Reliability Assessment Interchange Transaction Tag Communication and Reliability Assessment
R1
none
None
No
No
TFCO
INT-002-0
R1.1
none
None
No
No
TFCO
INT-002-0
R1.2
none
None
No
No
TFCO
Page 25 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
INT-002-0
Interchange Transaction Tag Communication and Reliability Assessment Interchange Transaction Tag Communication and Reliability Assessment Interchange Transaction Tag Communication and Reliability Assessment Interchange Transaction Tag Communication and Reliability Assessment
R1.3
none
None
No
TFCO
INT-002-0
R1.4
none
None
No
No
TFCO
INT-002-0
R1.5
Transmission Operators and Reliability Coordinators who may receive the information through Reliability analysis services.
none
None
No
No
TFCO
INT-002-0
R2
Transmission Service Providers on the Scheduling Path shall be responsible for assessing and approving or denying the Interchange Transaction based on established reliability criteria and adequacy of Interconnected Operating Services and transmission rights as well as the reasonableness of the Interchange Transaction Tag. The Transmission Service Provider shall verify and assess: Valid OASIS reservation number or transmission contract identifier.
none
None
No
No
TFCO
INT-002-0
Interchange Transaction Tag Communication and Reliability Assessment Interchange Transaction Tag Communication and Reliability Assessment Interchange Transaction Tag Communication and Reliability Assessment Interchange Transaction Tag Communication and Reliability Assessment Interchange Transaction Tag Communication and Reliability Assessment Interchange Transaction Tag Communication and Reliability Assessment Interchange Transaction Tag Communication and Reliability Assessment Interchange Transaction Tag Communication and Reliability Assessment Interchange Transaction Tag Communication and Reliability Assessment Interchange Transaction Tag Communication and Reliability Assessment Interchange Transaction Tag Communication and Reliability Assessment Interchange Transaction Tag Communication and Reliability Assessment
R2.1
none
None
No
No
TFCO
INT-002-0
R2.2
none
None
No
No
TFCO
INT-002-0
R2.3
none
None
No
No
TFCO
INT-002-0
R2.4
none
None
No
No
TFCO
INT-002-0
R2.5
none
None
No
No
TFCO
INT-002-0
R2.6
Loss accounting.
none
None
No
No
TFCO
INT-002-0
R3
Balancing Authorities on the Scheduling Path shall be responsible for assessing and approving or denying the Interchange Transaction. The Balancing Authority shall verify and assess (see R3.1, R3.2, etc. below): Transaction start and end time.
none
None
No
No
TFCO
INT-002-0
R3.1
none
None
No
No
TFCO
INT-002-0
R3.2
none
None
No
No
TFCO
INT-002-0
R3.3
none
None
No
No
TFCO
INT-002-0
R3.4
none
None
No
No
TFCO
INT-002-0
R4
Each Balancing Authority and Transmission Service Provider on the Scheduling Path shall communicate their approval or denial of the Interchange Transaction to the Sink Balancing Authority.
none
None
No
No
TFCO
Page 26 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
INT-002-0
R5
Upon receipt of approvals or denials from all of the individual Balancing Authorities and none Transmission Service Providers, the Sink Balancing Authority shall communicate the composite approval status of the Interchange Transaction to the Purchasing-Selling Entity and all other Balancing Authorities and Transmission Service Providers on the Scheduling Path and through the Reliability Each Receiving Balancing Authority shall confirm Interchange Schedules with the none Sending Balancing Authority prior to implementation in the Balancing Authoritys ACE equation. The Sending Balancing Authority and Receiving Balancing Authority shall agree on: none
None
No
TFCO
INT-003-0
Interchange Transaction Implementation Interchange Transaction Implementation Interchange Transaction Implementation Interchange Transaction Implementation Interchange Transaction Implementation
R1
None
No
No
TFCO
INT-003-0
R1.1
None
No
No
TFCO
INT-003-0
R1.1.1
none
None
No
No
TFCO
INT-003-0
R1.1.2
Energy profile.
none
None
No
No
TFCO
INT-003-0
R1.1.3
Ramp start time and duration (Balancing Authorities shall use the Ramp duration none established for their Interconnection unless they agree to an alternative Ramp duration.) Default Ramps durations are as follows: Default Ramp duration for the Eastern Interconnection shall be 10 minutes equally across the Interchange Schedule start and end times. Default Ramp duration for the Western Interconnection shall be 20 minutes equally across the Interchange Schedule start and end times. Ramp durations for Interchange Schedules implemented for compliance with NERCs DCS (recovery from a disturbance condition) and Interchange Transaction curtailment in response to line loading relief procedures may be shorter than the above defaults, but must be identical for the Sending and Receiving BAs.
None
No
No
TFCO
INT-003-0
R1.2
If a high voltage direct current (HVDC) tie is on the Scheduling Path, then the Sending Balancing Authorities and Receiving Balancing Authorities shall coordinate the Interchange Schedule with the Transmission Operator of the HVDC tie. Balancing Authorities that implement Interchange Schedules that cross an Interconnection boundary shall use the same start time and Ramp durations. Balancing Authorities shall implement Interchange Schedules only with Adjacent Balancing Authorities. Balancing Authorities shall begin and end Interchange Schedules at a time agreed to by the Source Balancing Authority, Sink Balancing Authority, and Intermediate Balancing Authorities. The Sink BA shall be responsible for initiating implementation of each Interchange Transaction as tagged. Upon receiving composite approval from the Sink BA, each BA on the scheduling path shall enter confirmed Schedules into its ACE equation. Balancing Authorities shall operate such that Interchange Schedules do not knowingly cause any other systems to violate established operating criteria. BA shall operate such that the maximum Net Interchange Schedule between any two BAs does not exceed the lesser of: The total capacity of both the owned and arranged-for transmission facilities in service for any Transmission Service Provider along the path, or The established network TTC between BAs, which considers other transmission facilities available to them under specific arrangements, and the overall physical constraints of the transmission network. If a Reliability Coordinator, TOP, or Source or Sink Balancing Authority, due to a reliability event, needs to modify an Interchange Transaction that is in progress or scheduled to be started, the entity shall, within 60 minutes of the start of the emergency Transaction, modify the Interchange Transaction tag, and shall communicate the modification to the Sink Balancing Authority. Reliability events may include: Transmission Loading Relief procedure curtailment - East. Inter.
none
None
No
No
TFCO
INT-003-0
Interchange Transaction Implementation Interchange Transaction Implementation Interchange Transaction Implementation Interchange Transaction Implementation
R1.3
none
None
No
No
TFCO
INT-003-0
R2
none
None
No
No
TFCO
INT-003-0
R3
none
None
No
No
TFCO
INT-003-0
R4
none
None
No
No
TFCO
INT-003-0
Interchange Transaction Implementation Interchange Transaction Implementation Interchange Transaction Implementation Interchange Transaction Implementation Interchange Transaction Modifications
R5
none
None
No
No
TFCO
INT-003-0
R6
none
None
No
No
TFCO
INT-003-0
R6.1
none
None
No
No
TFCO
INT-003-0
R6.2
none
None
No
No
TFCO
INT-004-0
R1
none
None
No
No
TFCO
INT-004-0
R1.1
No
No
TFCO
Page 27 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
INT-004-0
R1.2
Interconnection, regional, or local overload relief or congestion management procedures. C20 Sec. 4.2.1
Implement local congestion management procedures including but not limited to: adjust internal generation, transfer load, adjust phase angle regulators and redeployment of reactive reserves.
No
TFCO
INT-004-0
R1.3
NPCC Regional When an SOL or IROL violation is imminent, RC must be aware that TLR procedures may not be timely. In Reliability Plan such circumstances the RC have the authority and obligation to immediately direct their TOP, GOP and BA Sec. 4.6.3 to re-dispatch generation, reconfigure transmission or reduce system demand
No
No
TFCO
INT-004-0
Interchange Transaction Modifications Interchange Transaction Modifications Interchange Transaction Modifications Interchange Transaction Modifications Interchange Transaction Modifications Interchange Transaction Modifications
R1.4
Loss of generation.
C1 Sec. III
Items of particular concern that can be discussed during Emergency Preparedness Conference Calls may No include: - largest first and second contingencies - expected available operating reserve capacity deficiencies None No
No
TFCO
INT-004-0
R1.5
Loss of load.
none
No
TFCO
INT-004-0
R2
A Generator Operator or Load Serving Entity may request the Host Balancing Authority none to modify an Interchange Transaction due to loss of generation or Load. When a loss of generation necessitates curtailing Interchange Transactions, the Source Balancing Authority shall coordinate the modifications to the appropriate tags. none
None
No
No
TFCO
INT-004-0
R2.1
None
No
No
TFCO
INT-004-0
R2.2
When a loss of Load necessitates curtailing Interchange Transactions, the Sink Balancing none Authority shall coordinate the modifications to the appropriate tags. Upon receipt of modification to an Interchange Transaction as described in Requirement none R1, the Sink Balancing Authority (Source Balancing Authority in the case of a loss of generation) shall communicate the modified information about the Interchange Transaction, including its composite approval status, to all Balancing Authorities and Transmission Service Providers on the Transaction path and the Purchasing-Selling Entity responsible for the Transaction. At such time as the reliability event allows for the reloading of the transaction, the entity none that initiated the curtailment shall release the limit on the Interchange Transaction tag to allow reloading the transaction and shall communicate the release of the limit to the Sink Balancing Authority. The Purchasing-Selling Entity responsible for tagging a Dynamic Interchange Schedule none shall ensure the tag is updated for the next available scheduling hour and future hours when any one of the following occur: The average energy profile in an hour is greater than 250 MW and in that hour the actual none hourly integrated energy deviates from the hourly average energy profile indicated on the tag by more than +10%. The average energy profile in an hour is less than or equal to 250 MW and in that hour none the actual hourly integrated energy deviates from the hourly average energy profile indicated on the tag by more than +25 megawatt-hours. A Reliability Coordinator or Transmission Operator determines the deviation, regardless of magnitude, to be a reliability concern and notifies the Purchasing-Selling Entity of that determination and the reasons. Each Regional Reliability Organization, subregion, or interregional coordinating group shall establish one or more Reliability Coordinators to continuously assess transmission reliability and coordinate emergency operations among the operating entities within the region and across the regional boundaries. none
None
No
No
TFCO
INT-004-0
R3
None
No
No
TFCO
INT-004-0
R4
None
No
No
TFCO
INT-004-0
R5
None
No
No
TFCO
INT-004-0
R5.1
None
No
No
TFCO
INT-004-0
R5.2
None
No
No
TFCO
INT-004-0
R5.3
None
No
No
TFCO
IRO-001-0
R1
NPCC Regional Identical to NERC R1 Reliability Plan (August, 2005), Sec. 2.1.1
No
Yes
TFCO
IRO-001-0
R2
The Reliability Coordinator shall comply with a regional reliability plan approved by the NPCC Regional NERC Operating Committee. Reliability Plan (August, 2005), Executive Summary
The NPCC Regional Reliability Plan (RRP) describes the procedures, practices and requirements No implemented to ensure reliable operation of the Bulk Electric System within the NPCC Region. Among other things, it Identifies the regional entities that are registered with the NERC in accordance with the NERC Reliability Functional Model and Reliability Standards and summarizes the operating functions that will be performed by that Entity.
No
TFCO
IRO-001-0
R3
The Reliability Coordinator shall have clear decision-making authority to act and to RRP Sec. 2.1.3 direct actions to be taken by Transmission Operators, Balancing Authorities, Generator Operators, Transmission Service Providers, Load-Serving Entities, and PurchasingSelling Entities within its Reliability Coordinator Area to preserve the integrity and reliability of the Bulk Electric System. These actions shall be taken without delay, but no longer than 30 minutes.
Identical to R3
No
No
TFCO
Page 28 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
IRO-001-0
R4
Reliability Coordinators that delegate tasks to other entities shall have formal operating RRP Sec. 2.1.3 agreements with each entity to which tasks are delegated. The Reliability Coordinator shall verify that all delegated tasks are understood, communicated, and addressed within its Reliability Coordinator Area. All responsibilities for complying with NERC and regional standards applicable to Reliability Coordinators shall remain with the Reliability Coordinator. The Reliability Coordinator shall list within its reliability plan all entities to which the Reliability Coordinator has delegated required tasks. none
Identical to R4
No
TFCO
IRO-001-0
Reliability Coordination Responsibilities and Authorities Reliability Coordination Responsibilities and Authorities Reliability Coordination Responsibilities and Authorities
R5
None
No
No
TFCO
IRO-001-0
R6
The Reliability Coordinator shall verify that all delegated tasks are carried out by NERC certified Reliability Coordinator operating personnel.
Identical to R6
No
No
TFCO
IRO-001-0
R7
The Reliability Coordinator shall have clear, comprehensive coordination agreements with adjacent Reliability Coordinators to ensure that System Operating Limit or Interconnection Reliability Operating Limit violation mitigation requiring actions in adjacent Reliability Coordinator Areas are coordinated.
The Reliability Coordinator shall have clear, comprehensive coordination agreements with adjacent Reliability Coordinators to ensure that the actions of adjacent RC Areas are coordinated to mitigate SOL or IROL violations.
No
No
TFCO
IRO-001-0
R8
Transmission Operators, Balancing Authorities, Generator Operators, Transmission RRP Sec. 2.3.2 Identical to R8 Service Providers, Load-Serving Entities, and Purchasing-Selling Entities shall comply with Reliability Coordinator directives unless such actions would violate safety, equipment, or regulatory or statutory requirements. Under these circumstances, the Transmission Operator, Balancing Authority, Generator Operator, Transmission Service Provider, Load-Serving Entity, or Purchasing-Selling Entity shall immediately inform the Reliability Coordinator of the inability to perform the directive so that the Reliability Coordinator may implement alternate remedial actions.
No
No
TFCO
IRO-001-0
R9
The Reliability Coordinator shall act in the interests of reliability for the overall Reliability Coordinator Area and the Interconnection before the interests of any other entity. Each Reliability Coordinator shall have adequate communications facilities (voice and data links) to appropriate entities within its Reliability Coordinator Area. These communications facilities shall be staffed and available to act in addressing a real-time emergency condition.
No
No
TFCO
IRO-002-0
R1
NPCC Regional Identical to NERC R1 Reliability Plan (August, 2005) RRP Sec. 7.2
No
No
TFCO
IRO-002-0
R2
Each Reliability Coordinator shall determine the data requirements to support its reliability coordination tasks and shall request such data from its Transmission Operators, Balancing Authorities, Transmission Owners, Generation Owners, Generation Operators, and Load- Serving Entities, or adjacent Reliability Coordinators.
Identical to R2
No
No
TFCO
IRO-002-0
R3
Each Reliability Coordinator or its Transmission Operators and Balancing Authorities RRP Sec. 6.3 shall provide, or arrange provisions for, data exchange to other Reliability Coordinators or Transmission Operators and Balancing Authorities via a secure network.
Identical to R3 except added or its Transmission Operators and Balancing Authorities in the opening line.
Yes
No
TFCO
IRO-002-0
R4
Each Reliability Coordinator shall have multi-directional communications capabilities RRP Sec. 6.3 with its Transmission Operators and Balancing Authorities, and with neighboring and 6.3.1 Reliability Coordinators, for both voice and data exchange as required to meet reliability needs of the Interconnection.
Sec. 6.3 Identical to R3 above. Sec. 6.3.1 Each Reliability Coordinator, TOP and BA shall provide adequate and reliable telecommunications facilities to ensure the exchange of interconnection and operating information necessary to maintain reliability. Where applicable these facilities shall be redundant and diversely routed
No
No
TFCO
IRO-002-0
R5
Each Reliability Coordinator shall have detailed real-time monitoring capability of its RC RRP Sec. 6.3.2 Area and sufficient monitoring capability of its surrounding RC Areas to ensure that potential or actual SOL or IROL violations are identified. Each RC shall have monitoring systems that provide information that can be easily understood and interpreted by the RC operating personnel, giving particular emphasis to alarm management and awareness systems, automated data transfers, and synchronized information systems, over a redundant and highly reliable infrastructure.
Identical to R5
No
No
TFCO
Page 29 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
IRO-002-0
R6
Each Reliability Coordinator shall monitor Bulk Electric System elements (generators, RRP Sec. 6.4 transmission lines, buses, transformers, breakers, etc.) that could result in SOL or IROL violations within its Reliability Coordinator Area. Each Reliability Coordinator shall monitor both real and reactive power system flows, and operating reserves, and the status of Bulk Electric System elements that are or could be critical to SOLs and IROLs and system restoration requirements within its RC Area. Each Reliability Coordinator shall have adequate analysis tools such as state estimation, RRP Sec. 7.1 pre and post-contingency analysis capabilities (thermal, stability, and voltage), and widearea overview displays. Each Reliability Coordinator shall continuously monitor its RC Area. Each RC shall have RRP Sec. 7.3 provisions for backup facilities that shall be exercised if the main monitoring system is unavailable. Each RC shall ensure SOL and IROL monitoring and derivations continue if the main monitoring system is unavailable. Each Reliability Coordinator shall control its Reliability Coordinator analysis tools, including approvals for planned maintenance. Each Reliability Coordinator shall have procedures in place to mitigate the effects of analysis tool outages. Each Reliability Coordinator shall monitor all Bulk Electric System facilities, which may include sub-transmission information, within its Reliability Coordinator Area and adjacent Reliability Coordinator Areas, as necessary to ensure that, at any time, regardless of prior planned or unplanned events, the Reliability Coordinator is able to determine any potential System Operating Limit and Interconnection Reliability Operating Limit violations within its Reliability Coordinator Area. none
Appendix B contains a Table that summarizes the monitoring and coordination done within NPCC and with neighboring Regions. Level I involves Inter-Area, Level II involves Regional and Level II involves InterArea/Inter-Regional monitoring and coordination.
No
TFCO
IRO-002-0
R7
Identical to R7
No
No
TFCO
IRO-002-0
R8
Identical to R8
No
No
TFCO
IRO-002-0
R9
none
No
No
TFCO
IRO-003-0
R1
NPCC Regional Identical to NERC R1 Reliability Plan (August, 2005) RRP Sec. 3.1.1.7
No
No
TFCO
IRO-003-0
R2
When a Reliability Coordinator is aware of an operational concern, such as declining RRP voltages, excessive reactive flows, or an IROL violation, in a neighboring Reliability Sec.3.1.1.8 Coordinator Area, it shall contact the Reliability Coordinator in whose area the operational concern was observed. The two Reliability Coordinators shall coordinate any actions, including emergency assistance, required to mitigate the operational concern. Each Reliability Coordinator shall know the current status of all critical facilities whose RRP Sec. failure, degradation or disconnection could result in an SOL or IROL violation. 3.1.1.7 Reliability Coordinators shall also know the status of any facilities that may be required to assist area restoration objectives.
Identical to R2
No
No
TFCO
IRO-003-0
R3
Identical to R3
No
No
TFCO
IRO-003-1
R1 Each Reliability Coordinator shall monitor all Bulk Electric System facilities, which may include sub-transmission information, within its Reliability Coordinator Area and adjacent Reliability Coordinator Areas, as necessary to ensure that, at any time, regardless of prior planned or unplanned events, the Reliability Coordinator is able to determine any potential System Operating Limit and Interconnection Reliability Operating Limit violations within its Reliability Coordinator Area. R2 Each Reliability Coordinator shall know the current status of all critical facilities whose failure, degradation or disconnection could result in an SOL or IROL violation. Reliability Coordinators shall also know the status of any facilities that may be required to assist area restoration objectives. Each Reliability Coordinator shall conduct next-day reliability analyses for its Reliability Coordinator Area to ensure that the Bulk Electric System can be operated reliably in anticipated normal and Contingency event conditions. The Reliability Coordinator shall conduct Contingency analysis studies to identify potential interface and other SOL and IROL violations, including overloaded transmission lines and transfs., volt. and stab. limits, etc.
TFCO
IRO-003-1
TFCO
IRO-004-0
R1
NPCC Regional Identical to NERC R1 Reliability Plan (August, 2005) RRP Sec. 3.1.2.1 & 3.1.2.1.1 Identical to R2
No
No
TFCO
IRO-004-0
R2
Each Reliability Coordinator shall pay particular attention to parallel flows to ensure one RRP Sec. Reliability Coordinator Area does not place an unacceptable or undue Burden on an 3.1.1.3 adjacent Reliability Coordinator Area. Each Reliability Coordinator shall, in conjunction with its TOP and BA, develop action plans that may be required, including reconfiguration of the transmission system, redispatching of generation, reduction or curtailment of Interchange Transactions, or reducing load to return transmission loading to within acceptable SOLs or IROLs. RRP Sec. 3.1.2.3
No
No
TFCO
IRO-004-0
R3
Identical to R3
No
No
TFCO
Page 30 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
IRO-004-0
R4
Each Transmission Operator, Balancing Authority, Transmission Owner, Generator RRP Sec. Owner, Generator Operator, and Load-Serving Entity in the Reliability Coordinator Area 3.1.2.2 shall provide information required for system studies, such as critical facility status, Load, generation, operating reserve projections, and known Interchange Transactions. This information shall be available by 1200 Central Standard Time for the Eastern Interconnection and 1200 Pacific Standard Time for the Western Interconnection.
No
TFCO
IRO-004-0
R5
Each Reliability Coordinator shall share the results of its system studies, when RRP Sec. conditions warrant or upon request, with other Reliability Coordinators and with 3.1.2.4 Transmission Operators, Balancing Authorities, and Transmission Service Providers within its Reliability Coordinator Area. The RC shall make study results available no later than 1500 Central Standard Time for the Eastern Interconnection and 1500 Pacific Standard Time for the Western Interconnection, unless circumstances warrant otherwise.
No
No
TFCO
IRO-004-0
R6
When conditions warrant, the Reliability Coordinator shall initiate a conference call or other appropriate communications to address the results of its reliability analyses.
RRP Sec. 6.5.2 NPCC has procedures in place to initiate an emergency conference call whenever one or more RC feel it would serve to preclude or mitigate and emergency. The steps and procedures for these calls are included in NPCC Document C-01 Operational Planning Coordination.
No
No
TFCO
IRO-004-0
R7
If the results of these studies indicate potential SOL or IROL violations, the Reliability RRP Sec. Coordinator shall issue the appropriate alerts via the Reliability Coordinator Information 3.1.2.5 System (RCIS) and direct its Transmission Operators, Balancing Authorities and Transmission Service Providers to take any necessary action the Reliability Coordinator deems appropriate to address the potential SOL or IROL violation. Each Transmission Operator, BA and Transmission Service Provider shall comply with RRP Sec. the directives of its RC based on the next day assessments in the same manner in which it 3.1.2.6 would comply during real time operating events.
Identical to R7 except it starts with the words If after applying all possible mitigation action plans, the study No results indicate.
No
TFCO
IRO-004-0
R8
Identical to R8
No
No
TFCO
IRO-004-1
R1 Each Reliability Coordinator shall conduct next-day reliability analyses for its Reliability Coordinator Area to ensure that the Bulk Electric System can be operated reliably in anticipated normal and Contingency event conditions. The Reliability Coordinator shall conduct Contingency analysis studies to identify potential interface and other SOL and IROL violations, including overloaded transmission lines and transformers, voltage and stability limits, etc. R2 Each Reliability Coordinator shall pay particular attention to parallel flows to ensure one Reliability Coordinator Area does not place an unacceptable or undue Burden on an adjacent Reliability Coordinator Area. R3 Each Reliability Coordinator shall, in conjunction with its Transmission Operators and Balancing Authorities, develop action plans that may be required, including reconfiguration of the transmission system, re-dispatching of generation, reduction or curtailment of Interchange Transactions, or reducing load to return transmission loading to within acceptable SOLs or IROLs. R4 Each Transmission Operator, Balancing Authority, Transmission Owner, Generator Owner, Generator Operator, and Load-Serving Entity in the Reliability Coordinator Area shall provide information required for system studies, such as critical facility status, Load, generation, operating reserve projections, and known Interchange Transactions. This information shall be available by 1200 Central Standard Time for the Eastern Interconnection and 1200 Pacific Standard Time for the Western Interconnection.
TFCO
IRO-004-1
TFCO
IRO-004-1
TFCO
IRO-004-1
TFCO
IRO-004-1
R5 Each Reliability Coordinator shall share the results of its system studies, when conditions warrant or upon request, with other Reliability Coordinators and with Transmission Operators, Balancing Authorities, and Transmission Service Providers within its Reliability Coordinator Area. The Reliability Coordinator shall make study results available no later than 1500 Central Standard Time for the Eastern Interconnection and 1500 Pacific Standard Time for the Western Interconnection, unless circumstances warrant otherwise R6 If the results of these studies indicate potential SOL or IROL violations, the Reliability Coordinator shall direct its Transmission Operators, Balancing Authorities and Transmission Service Providers to take any necessary action the Reliability Coordinator deems appropriate to address the potential SOL or IROL violation.
TFCO
IRO-004-1
TFCO
Page 31 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
IRO-005-0
R1
Each Reliability Coordinator shall monitor its Reliability Coordinator Area parameters, including but not limited to the following (see R1.1, 1.2 etc. below):
NPCC Regional Reliability Plan (August, 2005) RRP Sec. 3.1.3.2 RRP Sec. 3.1.3.2
The Reliability Coordinator shall be continuously aware of operating conditions within its RC Area and include this information in its reliability assessments. To accomplish this objective the RC shall monitor its parameters that may have significant impacts on its RC Area parameters, including but not limited to the following, where applicable:
No
TFCO
IRO-005-0
R1.1
Current status of Bulk Electric System elements (transmission or generation including critical auxiliaries such as Automatic Voltage Regulators and Special Protection Systems) and system loading.
No
No
TFCO
IRO-005-0
R1.2
Current pre-contingency element conditions (voltage, thermal, or stability), including any RRP Sec. applicable mitigation plans to alleviate SOL or IROL violations, including the plans 3.1.3.2 viability and scope. Current post-contingency element conditions (voltage, thermal, or stability), including RRP Sec. any applicable mitigation plans to alleviate SOL or IROL violations, including the plans 3.1.3.2 viability and scope.
No
No
TFCO
IRO-005-0
R1.3
Operating Reserve: The RC is required to monitor BA parameters to ensure that the required amount of Operating Reserve is provided and available as required to meet NERC CPS and DCS requirements. If necessary, the RC shall direct the BA in its RC Area to arrange for assistance from neighboring areas. The RC shall issue EEA, as needed, and at the request of LSEs. Reacti The RC is required to monitor its Areas parameters to ensure that sufficient reactive resources are available to maintain voltage within normal limits for pre-disturbance conditions, and within applicable emergency limits for the system conditions that exist following the cont. Capac Cap. and energy adequacy conditions as per NPCC Documents B-09 and C-07.
No
No
TFCO
IRO-005-0
R1.4
No
No
TFCO
IRO-005-0
R1.5
No
No
TFCO
IRO-005-0
R1.6
Current ACE for all its Balancing Authorities, per NPCC Document C-39.
No
No
TFCO
IRO-005-0
R1.7
No
No
TFCO
IRO-005-0
R1.8
Identical to R1.8
No
No
TFCO
IRO-005-0
R1.9
Planned transmission or generation outages, per NPCC Documents A-03 and C-13.
No
No
TFCO
IRO-005-0
R1.10
Contingency events.
Identical to R1.10
No
No
TFCO
IRO-005-0
R2
Each Reliability Coordinator shall be aware of all Interchange Transactions that wheel through, source, or sink in its Reliability Coordinator Area, and make that Interchange Transaction information available to all Reliability Coordinators in the Interconnection.
Identical to R2 with the words via the Interchange Distribution Calculator (IDC) tacked onto the end of it.
No
No
TFCO
IRO-005-0
R3
As portions of the transmission system approach or exceed SOLs or IROLs, the RC shall RRP Sec. work with its TOP and BA to evaluate and assess any additional Interchange Schedules that would violate those limits. If a potential or actual IROL violation cannot be avoided through proactive intervention, the RC shall initiate control actions or emergency procedures to relieve the violation without delay, and no longer than 30 minutes. The RC shall ensure all resources, including load shedding, are available to address a potential or actual IROL violation. Each Reliability Coordinator shall monitor its Balancing Authorities parameters to ensure that the required amount of operating reserves is provided and available as required to meet the CPS and DCS requirements. If necessary, the RC shall direct the Balancing Authorities in the RC Area to arrange for assistance from neighboring BA. The RC shall issue Energy Emergency Alerts as needed and at the request of its Balancing Authorities and Load-Serving Entities.
No
No
TFCO
IRO-005-0
R4
No
No
TFCO
Page 32 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
IRO-005-0
R5
Each Reliability Coordinator shall identify the cause of any potential or actual SOL or RRP Sec. 4.6.3 Identical to R5 IROL violations. The RC shall initiate the control action or emergency procedure to relieve the potential or actual IROL violation without delay, and no longer than 30 minutes. The RC shall be able to utilize all resources, including load shedding, to address an IROL violation. Each Reliability Coordinator shall ensure its TOP and BA are aware of Geo-Magnetic RRP Sec. Disturbance (GMD) forecast information and assist as needed in the development of any 3.1.3.4 required response plans. The Reliability Coordinator shall participate in NERC hotline discussions, assist in the assessment of reliability of the overall interconnected system, and coordinate actions in anticipated or actual emergency situations. The RC shall disseminate such information within its RC Area, as required. Identical to R6 and also includes a provision to communicate the start and end of Time Error Corrections to its relevant TOP and BA.
No
TFCO
IRO-005-0
R6
No
No
TFCO
IRO-005-0
R7
RRP Sec. 4.5.3 RC use the NERC Hotline to disseminate information and exercise coordination with other RC. Appropriate No & 4.5.4 information in then relayed to individual BA and TOP within their RC Area. For emergencies that involve or affect the BES or when time is of essence in (dealing with) the emergency, RC are required to use the NERC Hotline. Identical to R8 No
No
TFCO
IRO-005-0
R8
Each Reliability Coordinator shall monitor system frequency and its Balancing RRP Sec. Authorities performance and direct any necessary rebalancing to return to CPS and DCS 3.1.3.5 compliance. The Transmission Operators and Balancing Authorities shall utilize all resources, including firm load shedding, as directed by its Reliability Coordinator to relieve the emergent condition. The Reliability Coordinator shall coordinate with other Reliability Coordinators and RRP Sec. Transmission Operators, Balancing Authorities, and Generator Operators as needed to 3.1.1.8 develop and implement action plans to mitigate potential or actual SOL, IROL, CPS, or DCS violations. The Reliability Coordinator shall coordinate pending generation and transmission maintenance outages with other Reliability Coordinators and Transmission Operators, Balancing Authorities, and Generator Operators as needed in both the real time and next-day reliability analysis timeframes.
No
TFCO
IRO-005-0
R9
First sentence is identical to first sentence of R9. Second sentence in RRP reads: This includes coordination No of pending generation and transmission maintenance outages in both the real-time and next-day time frames. It also includes coordination of any actions, including emergency assistance, required to mitigate any operational concerns.
No
TFCO
IRO-005-0
R10
As necessary, the Reliability Coordinator shall assist the Balancing Authorities in its Reliability Coordinator Area in arranging for assistance from neighboring Reliability Coordinator Areas or Balancing Authorities.
If necessary, the RC shall direct the BA in its RC Area to arrange for assistance from neighboring areas. The No RC shall issue Energy Emergency Alerts, as needed, and at the request of Load Serving Entities.
No
TFCO
IRO-005-0
R11
The Reliability Coordinator shall identify sources of large Area Control Errors that may RRP Sec. be contributing to Frequency Error, Time Error, or Inadvertent Interchange and shall 3.1.3.5 discuss corrective actions with the appropriate Balancing Authority. If a Frequency Error, Time Error, or inadvertent problem occurs outside of the Reliability Coordinator Area, the Reliability Coordinator shall initiate a NERC hotline call to discuss the Frequency Error, Time Error, or Inadvertent Interchange with other Reliability Coordinators. The Reliability Coordinator shall direct its Balancing Authority to comply with CPS and DCS. Whenever a Special Protection System that may have an inter-Balancing Authority, inter- RRP Sec. Transmission Operator, or inter-Reliability Coordinator Area impact (e.g., could 3.1.3.6 potentially affect transmission flows resulting in a SOL or IROL violation) is armed, the RC shall be aware of the impact of the operation of that SPS on inter-area flows. The TOP shall immediately inform the RC of the status of the SPS including any degradation or potential failure to operate as expected. Each Reliability Coordinator shall ensure that all TOP, BA, Generator Operators, TSP, RRP Sec. LSE, and Purchasing-Selling Entities operate to prevent the likelihood that a disturbance, 3.1.1.3 action, or nonaction in its RC Area will result in a SOL or IROL violation in another area of the Interconnection. In instances where there is a difference in derived limits, the RC and its TOP, BA, Generator Operators, TSP, LSE, and Purchasing-Selling Entities shall always operate the Bulk Electric System to the most limiting parameter.
Identical to R11
No
No
TFCO
IRO-005-0
R12
Identical to R12
No
No
TFCO
IRO-005-0
R13
No
No
TFCO
IRO-005-0
R14
Each Reliability Coordinator shall make known to Transmission Service Providers within its Reliability Coordinator Area, SOLs or IROLs within its wide-area view. The Transmission Service Providers shall respect these SOLs or IROLs in accordance with filed tariffs and regional Total Transfer Calculation and Available Transfer Calculation processes.
Identical to R14 except the second sentence starts: The TSP shall respect these SOLs or IROLs in the determination of transfer capabilities, in accordance with.
No
No
TFCO
Page 33 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
IRO-005-0
R15
Each Reliability Coordinator who foresees a transmission problem (such as an SOL or RRP Sec. IROL violation, loss of reactive reserves, etc.) within its RC Area shall issue an alert to all impacted Transmission Operators and Balancing Authorities in its RCArea, and all impacted RC within the Interconnection via the Reliability Coordinator Information System (RCIS) without delay. The receiving RC shall disseminate this information to its impacted TOP and BA. The RC shall notify all impacted Transmission Operators, Balancing Authorities, and RC when the transmission problem has been mitigated.
Identical to R15
No
TFCO
IRO-005-0
R16
Each Reliability Coordinator shall confirm reliability assessment results and determine RRP Sec. the effects within its own and adjacent Reliability Coordinator Areas. The Reliability 3.1.2.4 & Coordinator shall discuss options to mitigate potential or actual SOL or IROL violations 3.1.2.5 and take actions as necessary to always act in the best interests of the Interconnection at all times.
3.1.2.4 When conditions warrant or upon request, the RC shall share the results of its system studies with No TOP, BA and TSP within its RC Area or with other RC. Study results for the next day shall be available no later than 1600 EST, unless circumstances warrant otherwise. When required, the RC shall initiate a conference call or other appropriate communications to address the results of its reliability analysis. 3.1.2.5 If after applying all possible mitigation action plans, the study results indicate potential SOL or IROL violation, the RC shall issue the appropriate alerts via the RCIS and direct its TOP, BA and TSP to take the necessary actions that the RC deems appropriate to address the potential SOL or IROL violation
No
TFCO
IRO-005-0
R17
When an IROL or SOL is exceeded, the Reliability Coordinator shall evaluate the local RRP Sec. 4.6.3 and wide-area impacts, both real-time and post-contingency, and determine if the actions being taken are appropriate and sufficient to return the system to within IROL in thirty minutes. If the actions being taken are not appropriate or sufficient, the Reliability Coordinator shall direct the Transmission Operator, Balancing Authority, Generator Operator, or Load-Serving Entity to return the system to within IROL or SOL.
When an SOL or IROL violation is imminent, RCs must be aware that TLR procedures may not be able to Yes address the violation in a timely fashion. In such circumstances the RC have the authority and obligation to immediately direct their TOP, Generation Operators and BA to re-dispatch generation, reconfigure transmission, manage interchange transactions or reduce system demand which may include shedding of firm load. These actions shall be used in conjunction with the TLR procedure to restore the system to normal state. The RC shall coordinate these emergency control actions with other RC as needed. These actions are described in NPCC Documents A-03 and C-20.
NPCC criteria is more No stringent in that it clarifies that the TLR procedure is sometimes not the appropriate tool to use when dealing with SOL or IROL situations.
TFCO
IRO-005-1
R1 Each Reliability Coordinator shall monitor its Reliability Coordinator Area parameters, including but not limited to the following: R1.1. Current status of Bulk Electric System elements (transmission or generation including critical auxiliaries such as Automatic Voltage Regulators and Special Protection Systems) and system loading. R1.2. Current pre-contingency element conditions (voltage, thermal, or stability), including any applicable mitigation plans to alleviate SOL or IROL violations, including the plans viability and scope. R1.3. Current post-contingency element conditions (voltage, thermal, or stability), including any applicable mitigation plans to alleviate SOL or IROL violations, including the plans viability and scope. R1.4. System real and reactive reserves (actual versus required). R1.5. Capacity and energy adequacy conditions. R1.6. Current ACE for all its Balancing Authorities. R1.7. Current local or Transmission Loading Relief procedures in effect. R1.8. Planned generation dispatches. R1.9. Planned transmission or generation outages. R1.10. Contingency events.
TFCO
TFCO
TFCO
TFCO
IRO-005-1
R2 Each Reliability Coordinator shall be aware of all Interchange Transactions that wheel through, source, or sink in its Reliability Coordinator Area, and make that Interchange Transaction information available to all Reliability Coordinators in the Interconnection. R3 As portions of the transmission system approach or exceed SOLs or IROLs, the Reliability Coordinator shall work with its Transmission Operators and Balancing Authorities to evaluate and assess any additional Interchange Schedules that would violate those limits. If a potential or actual IROL violation cannot be avoided through proactive intervention, the Reliability Coordinator shall initiate control actions or emergency procedures to relieve the violation without delay, and no longer than 30 minutes. The Reliability Coordinator shall ensure all resources, including load shedding, are available to address a potential or actual IROL violation.
IRO-005-1
TFCO
Page 34 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
IRO-005-1
R4 Each Reliability Coordinator shall monitor its Balancing Authorities parameters to ensure that the required amount of operating reserves is provided and available as required to meet the Control Performance Standard and Disturbance Control Standard requirements. If necessary, the Reliability Coordinator shall direct the Balancing Authorities in the Reliability Coordinator Area to arrange for assistance from neighboring Balancing Authorities. The Reliability Coordinator shall issue Energy Emergency Alerts as needed and at the request of its Balancing Authorities and LoadServing Entities. R5 Each Reliability Coordinator shall identify the cause of any potential or actual SOL or IROL violations. The Reliability Coordinator shall initiate the control action or emergency procedure to relieve the potential or actual IROL violation without delay, and no longer than 30 minutes. The Reliability Coordinator shall be able to utilize all resources, including load shedding, to address an IROL violation.
TFCO
IRO-005-1
TFCO
IRO-005-1
R6 Each Reliability Coordinator shall ensure its Transmission Operators and Balancing Authorities are aware of Geo-Magnetic Disturbance (GMD) forecast information and assist as needed in the development of any required response plans.
TFCO
IRO-005-1
R7 The Reliability Coordinator shall disseminate information within its Reliability Coordinator Area, as required. R8 Each Reliability Coordinator shall monitor system frequency and its Balancing Authorities performance and direct any necessary rebalancing to return to CPS and DCS compliance. The Transmission Operators and Balancing Authorities shall utilize all resources, including firm load shedding, as directed by its Reliability Coordinator to relieve the emergent condition. R9 The Reliability Coordinator shall coordinate with Transmission Operators, Balancing Authorities, and Generator Operators as needed to develop and implement action plans to mitigate potential or actual SOL, IROL, CPS, or DCS violations. The Reliability Coordinator shall coordinate pending generation and transmission maintenance outages with Transmission Operators, Balancing Authorities, and Generator Operators as needed in both the real time and next-day reliability analysis timeframes. As necessary, the Reliability Coordinator shall assist the Balancing Authorities in its Reliability Coordinator Area in arranging for assistance from neighboring Reliability Coordinator Areas or Balancing Authorities. The Reliability Coordinator shall identify sources of large Area Control Errors that may be contributing to Frequency Error, Time Error, or Inadvertent Interchange and shall discuss corrective actions with the appropriate Balancing Authority. The Reliability Coordinator shall direct its Balancing Authority to comply with CPS and DCS. R12 Whenever a Special Protection System that may have an inter-Balancing Authority, or inter-Transmission Operator impact (e.g., could potentially affect transmission flows resulting in a SOL or IROL violation) is armed, the Reliability Coordinators shall be aware of the impact of the operation of that Special Protection System on inter-area flows. The Transmission Operator shall immediately inform the Reliability Coordinator of the status of the Special Protection System including any degradation or potential failure to operate as expected. R13 Each Reliability Coordinator shall ensure that all Transmission Operators, Balancing Authorities, Generator Operators, Transmission Service Providers, Load-Serving Entities, and Purchasing-Selling Entities operate to prevent the likelihood that a disturbance, action, or nonaction in its Reliability Coordinator Area will result in a SOL or IROL violation in another area of the Interconnection. In instances where there is a difference in derived limits, the Reliability Coordinator and its Transmission Operators, Balancing Authorities, Generator Operators, Transmission Service Providers, LoadServing Entities, and Purchasing-Selling Entities shall always operate the Bulk Electric System to the most limiting parameter.
TFCO
IRO-005-1
TFCO
IRO-005-1
TFCO
IRO-005-1
R10
TFCO
IRO-005-1
R11
TFCO
IRO-005-1
TFCO
IRO-005-1
TFCO
IRO-005-1
R14
Each Reliability Coordinator shall make known to Transmission Service Providers within its Reliability Coordinator Area, SOLs or IROLs within its wide-area view. The Transmission Service Providers shall respect these SOLs or IROLs in accordance with filed tariffs and regional Total Transfer Calculation and Available Transfer Calculation processes.
TFCO
Page 35 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
IRO-005-1
R15 Each Reliability Coordinator who foresees a transmission problem (such as an SOL or IROL violation, loss of reactive reserves, etc.) within its Reliability Coordinator Area shall issue an alert to all impacted Transmission Operators and Balancing Authorities in its Reliability Coordinator Area without delay. The receiving Reliability Coordinator shall disseminate this information to its impacted Transmission Operators and Balancing Authorities. The Reliability Coordinator shall notify all impacted Transmission Operators, Balancing Authorities, when the transmission problem has been mitigated.
TFCO
IRO-005-1
R16 Each Reliability Coordinator shall confirm reliability assessment results and determine the effects within its own and adjacent Reliability Coordinator Areas. The Reliability Coordinator shall discuss options to mitigate potential or actual SOL or IROL violations and take actions as necessary to always act in the best interests of the Interconnection at all times. R17 When an IROL or SOL is exceeded, the Reliability Coordinator shall evaluate the local and wide-area impacts, both real-time and post-contingency, and determine if the actions being taken are appropriate and sufficient to return the system to within IROL in thirty minutes. If the actions being taken are not appropriate or sufficient, the Reliability Coordinator shall direct the Transmission Operator, Balancing Authority, Generator Operator, or Load-Serving Entity to return the system to within IROL or SOL. A Reliability Coordinator shall take appropriate actions in accordance with established NPCC Regional Identical to NERC R1 policies, procedures, authority, and expectations to relieve transmission loading. Reliability Plan (August, 2005) RRP Sec. 3.1.1.6 A Reliability Coordinator experiencing a potential or actual SOL or IROL violation RRP Sec. within its Reliability Coordinator Area shall, at its discretion, select from either a local 3.1.3.3.2 (Regional, Interregional, or subregional) transmission loading relief procedure or an Interconnection-wide procedure. As portions of the transmission system approach or exceed SOLs or IROLs, the RC shall work with its TOP and BA to evaluate and assess any additional Interchange Schedules that would violate those limits. If the potential or actual SOL or IROL violation cannot be avoided through proactive intervention, the RC shall initiate control actions or emergency procedures to relieve the violation consistent with Reliability Standard. All resources, including shedding of firm load shall be available to the RC to address a potential or actual SOL or IROL violation. As described in R2 above.
TFCO
IRO-005-1
TFCO
IRO-006-1
R1
No
No
TFCO
IRO-006-1
R2
No
No
TFCO
IRO-006-1
R2.1
R2.1 - The Interconnection-wide Transmission Loading Relief (TLR) procedure for use in the Eastern Interconnection is provided in Attachment 1-IRO-006-0.
No
NPCC generally utilizes No local methods of dealing with transmission loading relief rather than the Interconnection-wide methods specified here.
TFCO
IRO-006-1
Reliability Coordination Transmission Loading Relief Reliability Coordination Transmission Loading Relief Reliability Coordination Transmission Loading Relief Reliability Coordination Transmission Loading Relief
R2.2
R2.2 - The equivalent Interconnection-wide transmission loading relief procedure for use in the Western Interconnection is the WSCC Unscheduled Flow Mitigation Plan.
No
TFCO
IRO-006-1
R2.3
R2.3 - The Interconnection-wide transmission loading relief procedure for use in ERCOT is provided as Section 7 of the ERCOT Protocols.
No
TFCO
IRO-006-1
R3
The Reliability Coordinator may use local transmission loading relief or congestion C-20 Sec. 4.2 management procedures, provided the Transmission Operator experiencing the potential or actual SOL or IROL violation is a party to those procedures. A Reliability Coordinator may implement a local transmission loading relief or congestion management procedure simultaneously with an Interconnection-wide procedure. However, the RC shall follow the curtailments as directed by the Interconnection-wide procedure. A RC desiring to use a local procedure as a substitute for curtailments as directed by the Interconnection-wide procedure shall have such use approved by the NERC Operating Committee.
When an Area is experiencing internal circuit or tie line loading in excess of applicable operating limits, the following steps should be implemented as required and appropriate based on industry-wide and/or local procedures : adjust generation transfer load adjust PARs etc.
No
No
TFCO
IRO-006-1
R4
C-20 Sec. 4.2.6 Step 4.2.6 of the NPCC local procedures is:
No
Note: The individual procedures used by the NPCC Reliability Coordinators have been approved by the NERC Operating Committee.
No
TFCO
IRO-006-1
R5
When implemented, all RC shall comply with the provisions of the Interconnection-wide none procedure including, for example, action by RC in other Interconnections to curtail an Interchange Transaction that crosses an Interconnection boundary.
None
No
No
TFCO
Page 36 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
IRO-006-1
Reliability Coordination Transmission Loading Relief Procedures, Processes, or Plans to Support Coordination Between Reliability Coordinators
R6
During the implementation of relief procedures, and up to the point that emergency none action is necessary, RC and BA shall comply with interchange scheduling standards INT001 through INT-004.
None
No
TFCO
IRO-014-1
R1 The Reliability Coordinator shall have Operating Procedures, Processes, or Plans in place for activities that require notification, exchange of information or coordination of actions with one or more other Reliability Coordinators to support Interconnection reliability. These Operating Procedures, Processes, or Plans shall address Scenarios that affect other Reliability Coordinator Areas as well as those developed in coordination with other Reliability Coordinators. R1.1. These Operating Procedures, Processes, or Plans shall collectively address, as a minimum, the following: R1.1.1. Communications and notifications, including the conditions1 under which one Reliability Coordinator notifies other Reliability Coordinators; the process to follow in making those notifications; and the data and information to be exchanged with other Reliability Coordinators. R1.1.2. Energy and capacity shortages. R1.1.3. Planned or unplanned outage information. R1.1.4. Voltage control, including the coordination of reactive resources for voltage control. R1.1.5. Coordination of information exchange to support reliability assessments. R1.1.6. Authority to act to prevent and mitigate instances of causing Adverse Reliability Impacts to other Reliability Coordinator Areas.
TFCO
TFCO TFCO
IRO-014-1
R2 Each Reliability Coordinators Operating Procedure, Process, or Plan that requires one or more other Reliability Coordinators to take action (e.g., make notifications, exchange information, or coordinate actions) shall be: R2.1. Agreed to by all the Reliability Coordinators required to take the indicated action(s). R2.2. Distributed to all Reliability Coordinators that are required to take the indicated action(s). R3 A Reliability Coordinators Operating Procedures, Processes, or Plans developed to support a Reliability Coordinator-to-Reliability Coordinator Operating Procedure, Process, or Plan shall include: R3.1. A reference to the associated Reliability Coordinator-to-Reliability Coordinator Operating Procedure, Process, or Plan. R3.2. The agreed-upon actions from the associated Reliability Coordinator-to-Reliability Coordinator Operating Procedure, Process, or Plan.
IRO-014-1
TFCO TFCO
IRO-014-1
R4
TFCO
Each of the Operating Procedures, Processes, and Plans addressed in Reliability Standard IRO-014 Requirement 1 and Requirement 3 shall: R4.1. Include version control number or date. R4.2. Include a distribution list. R4.3. Be reviewed, at least once every three years, and updated if needed. TFCO TFCO TFCO TFCO The Reliability Coordinator shall follow its Operating Procedures, Processes, or Plans for making notifications and exchanging reliability-related information with other Reliability Coordinators. R1.1. The Reliability Coordinator shall make notifications to other Reliability Coordinators of conditions in its Reliability Coordinator Area that may impact other Reliability Coordinator Areas. R2
IRO-015-1
R1
TFCO
IRO-015-1
TFCO
The Reliability Coordinator shall participate in agreed upon conference calls and other communication forums with adjacent Reliability Coordinators. R2.1. The frequency of these conference calls shall be agreed upon by all involved Reliability Coordinators and shall be at least weekly.
TFCO
Page 37 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
IRO-015-1
Procedures, Processes, or Plans to Support Coordination Between Reliability Coordinators Coordination of Real-time Activities Between Reliability Coordinators
R3
TFCO
The Reliability Coordinator shall provide reliability-related information as requested by other Reliability Coordinators. R1 The Reliability Coordinator that identifies a potential, expected, or actual problem that requires the actions of one or more other Reliability Coordinators shall contact the other Reliability Coordinator(s) to confirm that there is a problem and then discuss options and decide upon a solution to prevent or resolve the identified problem. TFCO R1.1. If the involved Reliability Coordinators agree on the problem and the actions to take to prevent or mitigate the system condition, each involved Reliability Coordinator shall implement the agreed-upon solution, and notify the involved Reliability Coordinators of the action(s) taken. R1.2. If the involved Reliability Coordinators cannot agree on the problem(s) each Reliability Coordinator shall re-evaluate the causes of the disagreement (bad data, status, study results, tools, etc.). R1.2.1. If time permits, this re-evaluation shall be done before taking corrective actions. TFCO R1.2.2. If time does not permit, then each Reliability Coordinator shall operate as though the problem(s) exist(s) until the conflicting system status is resolved. R1.3. If the involved Reliability Coordinators cannot agree on the solution, the more conservative solution shall be implemented. TFCO
IRO-016-1
TFCO
TFCO
TFCO TFCO
IRO-016-1
Coordination of Real-time Activities Between Reliability Coordinators Documentation of Total Transfer Capability and Available Transfer Capability Calculation Methodologies
R2 The Reliability Coordinator shall document (via operator logs or other data sources) its actions taken for either the event or for the disagreement on the problem(s) or for both. Each Regional Reliability Organization, in conjunction with its members, shall develop and document a Regional TTC and ATC methodology. (Certain systems that are not required to post ATC values are exempt from this standard.) The Regional Reliability Organizations TTC and ATC methodology shall include each of the following nine items, and shall explain its use in determining TTC and ATC values:
MOD-001-0
R1
NPCC CO-13 Per Methodology Regional Methodology & Guidelines For Forecasting TTC & ATC (RMGF T&A)
No
Yes
TFCO
MOD-001-0
Documentation of Total Transfer Capability and Available Transfer Capability Calculation Methodologies Documentation of Total Transfer Capability and Available Transfer Capability Calculation Methodologies Documentation of Total Transfer Capability and Available Transfer Capability Calculation Methodologies Documentation of Total Transfer Capability and Available Transfer Capability Calculation Methodologies
R1.1
RMGF T&A
Per Methodology
No
Yes
TFCO
MOD-001-0
R1.2
An accounting for how the reservations and schedules for firm (non-recallable) and non- RMGF T&A firm (recallable) transfers, both within and outside the TSPs system, are included.
Per Methodology
No
Yes
TFCO
MOD-001-0
R1.3
An accounting for the ultimate points of power injection (sources) and power extraction RMGF T&A (sinks) in TTC and ATC calculations.
Per Methodology
No
Yes
TFCO
MOD-001-0
R1.4
A description of how incomplete or so-called partial path transmission reservations are addressed. (Incomplete or partial path transmission reservations are those for which all transmission reservations necessary to complete the transmission path from ultimate source to ultimate sink are not identifiable due to differing reservation priorities, durations, or because the reservations have not all been made.)
RMGF T&A
Per Methodology
No
Yes
TFCO
Page 38 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
MOD-001-0
Documentation of Total Transfer Capability and Available Transfer Capability Calculation Methodologies Documentation of Total Transfer Capability and Available Transfer Capability Calculation Methodologies Documentation of Total Transfer Capability and Available Transfer Capability Calculation Methodologies Documentation of Total Transfer Capability and Available Transfer Capability Calculation Methodologies Documentation of Total Transfer Capability and Available Transfer Capability Calculation Methodologies Documentation of Total Transfer Capability and Available Transfer Capability Calculation Methodologies
R1.5
A requirement that TTC and ATC values shall be determined and posted as follows:
RMGF T&A Per Methodology and the NPCC TTC & ATC web site. NPCC TTC & ATC Web Site
Yes
TFCO
MOD-001-0
R1.5.1
RMGF T&A
Per Methodology
No
Yes
TFCO
MOD-001-0
R1.5.2
Daily values for day 8 through the first month at least once per week.
RMGF T&A
Per Methodology
No
Yes
TFCO
MOD-001-0
R1.5.3
RMGF T&A
Per Methodology
No
Yes
TFCO
MOD-001-0
R1.6
Indication of the treatment and level of customer demands, including interruptible demands.
none
None
No
Yes
TFCO
MOD-001-0
R1.7
A specification of how system conditions, limiting facilities, contingencies, transmission NPCC Regional reservations, energy schedules, and other data needed by Transmission Service Providers Reliability Plan for the calculation of TTC and ATC values are shared and used within the Regional Sec. 3.1.1.4 Reliability Organization and with neighboring interconnected electric systems, including adjacent systems, subregions, and Regional Reliability Organizations. In addition, specify how this information is to be used to determine TTC and ATC values. If some data is not used, provide an explanation.
3.1.1.4 The Reliability Coordinator shall make known to Transmission Service Providers within its No Reliability Coordinator Area, SOLs and IROLs within its wide-area view. The TSP shall respect these SOLs and IROLs in the determination of transfer capabilities, in accordance with filed tariffs and/or regional TTC/ATC calculation processes.
Yes
TFCO
MOD-001-0
Documentation of Total Transfer Capability and Available Transfer Capability Calculation Methodologies
R1.7
A specification of how system conditions, limiting facilities, contingencies, transmission RMGF T&A Per Methodology and the NPCC TTC & ATC web site. reservations, energy schedules, and other data needed by Transmission Service Providers NPCC TTC & for the calculation of TTC and ATC values are shared and used within the Regional ATC Web Site Reliability Organization and with neighboring interconnected electric systems, including adjacent systems, subregions, and Regional Reliability Organizations. In addition, specify how this information is to be used to determine TTC and ATC values. If some data is not used, provide an explanation.
No
Yes
TFCO
MOD-001-0
Documentation of Total Transfer Capability and Available Transfer Capability Calculation Methodologies Documentation of Total Transfer Capability and Available Transfer Capability Calculation Methodologies Documentation of Total Transfer Capability and Available Transfer Capability Calculation Methodologies
R1.8
A description of how the assumptions for and the calculations of TTC and ATC values change over different time (such as hourly, daily, and monthly) horizons.
RMGF T&A
Per Methodology
No
Yes
TFCO
MOD-001-0
R1.9
A description of the Regional Reliability Organizations practice on the netting of transmission reservations for purposes of TTC and ATC determination.
RMGF T&A
Per Methodology
No
Yes
TFCO
MOD-001-0
R2
The Regional Reliability Organization shall make the most recent version of the documentation of its TTC and ATC methodology available on a web site accessible by NERC, the Regional Reliability Organizations, and transmission users.
NPCC TTC & Per NPCC TTC & ATC web site. ATC Web Site
No
Yes
TFCO
Page 39 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
MOD-002-0
Review of Transmission Service Provider Total Transfer Capability and Available Transfer Capability Calculations and Results
R1
Each Regional Reliability Organization, in conjunction with its members, shall develop and implement a procedure to periodically review (at least annually) and ensure that the TTC and ATC calculations and resulting values of member Transmission Service Providers comply with the Regional TTC and ATC methodology and applicable Regional criteria.
Scope of NPCC Per Working Group CO-13 (WG on the Coordination of ATC Calculation & Posting ) none
CO-13 Scope
Yes
TFCO
MOD-002-0
Review of Transmission Service Provider Total Transfer Capability and Available Transfer Capability Calculations and Results Review of Transmission Service Provider Total Transfer Capability and Available Transfer Capability Calculations and Results Regional Procedure for Input on Total Transfer Capability and Available Transfer Capability Methodologies and Values
R2
Each Regional Reliability Organization shall document the results of its periodic reviews none of TTC and ATC.
No
NPCC does not have a Yes formal Regional review. CO-13 meets and discusses issues regularly
TFCO
MOD-002-0
R3
The Regional Reliability Organization shall provide the results of its most current reviews of TTC and ATC to NERC on request (within 30 calendar days).
none
none
No
Yes
TFCO
MOD-003-0
R1
Each Regional Reliability Organization, in conjunction with its members, shall develop and document a procedure on how transmission users can input their concerns or questions regarding the TTC and ATC methodology and values of the Transmission Service Provider(s), and how these concerns or questions will be addressed. The Regional Reliability Organizations procedure shall specify the following:
NPCC TTC & Per the NPCC TTC & ATC web site. ATC Web Site
No
Yes
TFCO
MOD-003-0
Regional Procedure for Input on Total Transfer Capability and Available Transfer Capability Methodologies and Values
R1.1
The name, telephone number and email address of a contact person to whom concerns are to be addressed.
No
Yes
TFCO
MOD-003-0
Regional Procedure for Input on Total Transfer Capability and Available Transfer Capability Methodologies and Values
R1.2
NPCC CO-13 Per Methodology Regional Methodology & Guidelines For Forecasting TTC & ATC (RMGF T&A)
No
Yes
TFCO
MOD-003-0
Regional Procedure for Input on Total Transfer Capability and Available Transfer Capability Methodologies and Values
R1.3
The manner in which the response will be communicated (e.g., email, letter, telephone, etc).
RMGF T&A Per Methodology and the NPCC TTC & ATC web site. NPCC TTC & ATC Web Site
No
Yes
TFCO
MOD-003-0
Regional Procedure for Input on Total Transfer Capability and Available Transfer Capability Methodologies and Values
R1.4
No
Yes
TFCO
MOD-003-0
Regional Procedure for Input on Total Transfer Capability and Available Transfer Capability Methodologies and Values
R2
The Regional Reliability Organization shall post on a web site that is accessible by the Regional Reliability Organizations, NERC, and transmission users, its procedure for receiving and addressing concerns about the TTC and ATC methodology and TTC and ATC values of member Transmission Service Providers.
No
Yes
TFCO
Page 40 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
MOD-004-0
R1
Each Regional Reliability Organization, in conjunction with its members, shall develop none and document a Regional CBM methodology. The Regional Reliability Organizations CBM methodology shall include each of the following ten items, and shall explain its use in determining CBM value. Other items that are Regional Reliability Organization specific or that are considered in each respective Regional Reliability Organization methodology shall also be explained along with their use in determining CBM values.
Yes
TFCO
MOD-004-0
Documentation of Regional Reliability Organization Capacity Benefit Margin Methodologies Documentation of Regional Reliability Organization Capacity Benefit Margin Methodologies
R1.1
Specify that the method used by each Regional Reliability Organization member to none determine its generation reliability requirements as the basis for CBM shall be consistent with its generation planning criteria.
No
Yes
TFCO
MOD-004-0
R1.2
Specify the frequency of calculation of the generation reliability requirement and associated CBM values.
NPCC CO-13 Needs to be added to our TTC/ATC Methodology Regional Methodology & Guidelines For Forecasting TTC & ATC (RMGF T&A) WG CP-8 Review of Interconnection Assistance & Reliability Benefits
No
Yes
TFCO
MOD-004-0
Documentation of Regional Reliability Organization Capacity Benefit Margin Methodologies Documentation of Regional Reliability Organization Capacity Benefit Margin Methodologies Documentation of Regional Reliability Organization Capacity Benefit Margin Methodologies Documentation of Regional Reliability Organization Capacity Benefit Margin Methodologies Documentation of Regional Reliability Organization Capacity Benefit Margin Methodologies Documentation of Regional Reliability Organization Capacity Benefit Margin Methodologies Documentation of Regional Reliability Organization Capacity Benefit Margin Methodologies
R1.3
Require that generation unit outages considered in a TSPs CBM calculation be restricted to those units within the Transmission Service Providers system.
RMGF T&A
Per Methodology
No
Yes
TFCO
MOD-004-0
R1.4
Require that CBM be preserved only on the TSPs System where the Load-Serving Entitys Load is located (i.e., CBM is an import quantity only).
RMGF T&A
Per Methodology
No
Yes
TFCO
MOD-004-0
R1.5
Describe the inclusion or exclusion rationale for generation resources of each LoadServing Entity including those generation resources not directly connected to the Transmission Service Providers system but serving Load-Serving Entity loads connected to the Transmission Service Providers system.
RMGF T&A
Per Methodology
No
Yes
TFCO
MOD-004-0
R1.6
Describe the inclusion or exclusion rationale for generation connected to the RMGF T&A Transmission Service Providers system but not obligated to serve Native/Network Load connected to the Transmission Service Providers system.
Per Methodology
No
Yes
TFCO
MOD-004-0
R1.7
Describe the formal process and rationale for the Regional Reliability Organization to grant any variances to individual Transmission Service Providers from the Regional Reliability Organizations CBM methodology.
A1 Criteria for Members may request the lead Task Force, at any time, to review and revise the Criteria, or portions thereof, Review & and have the right to enter into the NPCC Appeals and Dispute Resolution Process for non-compliance Approval of issues. Documents) RMGF T&A Per Methodology
No
Yes
TFCO
MOD-004-0
R1.8
Specify the relationship of CBM to the generation reliability requirement and the allocation of the CBM values to the appropriate transmission facilities. The sum of the CBM values allocated to all interfaces shall not exceed that portion of the generation reliability requirement that is to be provided by outside resources. Describe the inclusion or exclusion rationale for the loads of each Load-Serving Entity, including interruptible demands and buy-through contracts (type of service contract that offers the customer the option to be interrupted or to accept a higher rate for service under certain conditions).
No
Yes
TFCO
MOD-004-0
R1.9
RMGF T&A
Per Methodology
No
Yes
TFCO
Page 41 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
MOD-004-0
Documentation of Regional Reliability Organization Capacity Benefit Margin Methodologies Documentation of Regional Reliability Organization Capacity Benefit Margin Methodologies Procedure for Verifying Capacity Benefit Margin Values
R1.10
Describe the inclusion or exclusion rationale for generation reserve sharing arrangements in the CBM values.
RMGF T&A
Per Methodology
Yes
TFCO
MOD-004-0
R2
The Regional Reliability Organization shall make the most recent version of the RMGF T&A Per Methodology and the NPCC TTC & ATC web site. documentation of its CBM methodology available on a website accessible by NERC, the NPCC TTC & Regional Reliability Organizations, and transmission users. ATC Web Site
No
Yes
TFCO
MOD-005-0
R1
Each Regional Reliability Organization, in conjunction with its members, shall develop and implement a procedure to review (at least annually) the CBM calculations and the resulting values of member Transmission Service Providers to ensure that they comply with the Regional Reliability Organizations CBM methodology. The procedure shall include the following four requirements:
none
None
No
NPCC has no A, B, Yes C or RD requirements available and Working Group CO13 Regional Methodology & Guidelines For Forecasting TTC & ATC does not have a formal review of CBM
TFCO
MOD-005-0
MOD-005-0
Procedure for Verifying Capacity Benefit Margin Values Procedure for Verifying Capacity Benefit Margin Values
R1.1
Indicate the frequency under which the verification review shall be implemented.
none
none
No
Yes
TFCO
R1.2
Require review of the process by which CBM values are updated, and their frequency of NPCC CO-13 Per Methodology update, to ensure that the most current CBM values are available to transmission users. Regional Methodology & Guidelines For Forecasting TTC & ATC (RMG T&A)
No
Yes
TFCO
MOD-005-0
R1.3
Require review of the consistency of the Transmission Service Providers CBM RMGF T&A components with its published planning criteria. A CBM value is considered consistent with published planning criteria if the components that comprise CBM are addressed in the planning criteria. The methodology used to determine and apply CBM does not have to involve the same mechanics as the planning process, but the same uncertainties must be considered and any simplifying assumptions explained. Require CBM values to be periodically updated (at least annually) and available to the Regional Reliability Organizations, NERC, and transmission users. Each Regional Reliability Organization shall document its CBM procedure and shall make its CBM review procedure available to NERC on request (within 30 calendar days). The Regional Reliability Organization shall provide documentation of the results of the most current implementation of its CBM review procedure to NERC on request (within 30 calendar days). RMGF T&A
Per Methodology
No
TFCO
MOD-005-0
MOD-005-0
MOD-005-0
Procedure for Verifying Capacity Benefit Margin Values Procedure for Verifying Capacity Benefit Margin Values Procedure for Verifying Capacity Benefit Margin Values Procedure for the Use of Capacity Benefit Margin Values
R1.4
Per Methodology
No
NPCC WG CO-13 does Yes not currently review this NPCC WG CO-13 does Yes not currently review this NPCC WG CO-13 presently does not review or verify CBM values Yes
TFCO
R2
RMGF T&A
Per Methodology
No
TFCO
R3
none
None
No
TFCO
MOD-006-0
R1
Each Transmission Service Provider shall document its procedure on the use of Capacity NPCC CO-13 Per Methodology Benefit Margin (CBM) (scheduling of energy against a CBM preservation). The Regional procedure shall include the following three components: Methodology & Guidelines For Forecasting TTC & ATC (RMGF T&A)
No
No
TFCO
MOD-006-0
R1.1
Require that CBM be used only after the following steps have been taken (as time RMGF T&A permits): all non-firm sales have been terminated, Direct-Control Load Management has been implemented, and customer interruptible demands have been interrupted. CBM may be used to reestablish Operating Reserves.
Per Methodology
No
No
TFCO
Page 42 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
MOD-006-0
Procedure for the Use of Capacity Benefit Margin Values Procedure for the Use of Capacity Benefit Margin Values Procedure for the Use of Capacity Benefit Margin Values Documentation of the Use of Capacity Benefit Margin
R1.2
Require that CBM shall only be used if the Load-Serving Entity calling for its use is experiencing a generation deficiency and its Transmission Service Provider is also experiencing Transmission Constraints relative to imports of energy on its trans.system. Describe the conditions under which CBM may be available as Non-Firm Transmission Service. Each Transmission Service Provider shall make its CBM use procedure available on a web site accessible by the Regional Reliability Organizations, NERC, and transmission users.
RMGF T&A
Per Methodology
No
TFCO
MOD-006-0
R1.3
RMGF T&A
Per Methodology
No
No
TFCO
MOD-006-0
R2
RMGF T&A Per Methodology and the NPCC TTC & ATC web site. NPCC TTC & ATC Web Site None
No
No
TFCO
MOD-007-0
R1
Each Transmission Service Provider that uses CBM shall report (to the Regional none Reliability Organization, NERC and the transmission users) the use of CBM by the LoadServing Entities Loads on its system, except for CBM sales as Non-Firm Transmission Service. (This use of CBM shall be consistent with the Transmission Service Providers procedure for use of CBM.) The Transmission Service Provider shall post the following three items within 15 none calendar days after the use of CBM for an Energy Emergency. This posting shall be on a web site accessible by the Regional Reliability Organizations, NERC, and transmission users. Circumstances. None
No
No
TFCO
MOD-007-0
R2
none
No
No
TFCO
MOD-007-0
Documentation of the Use of Capacity Benefit Margin Documentation of the Use of Capacity Benefit Margin Documentation of the Use of Capacity Benefit Margin Documentation and Control of Each Regional Transmission Reliability Margin Methodology
R2.1
none
No
No
TFCO
MOD-007-0
R2.2
Duration
none
none
No
No
TFCO
MOD-007-0
R2.3
none
None
Yes
No
TFCO
MOD-008-0
R1
Each Regional Reliability Organization, in conjunction with its members, shall develop and document a Regional TRM methodology. The Regions TRM methodology shall specify or describe each of the following five items, and shall explain its use, if any, in determining TRM values. Other items that are Region-specific or that are considered in each respective Regional methodology shall also be explained along with their use in determining TRM values.
NPCC CO-13 Per Methodology Regional Methodology & Guidelines For Forecasting TTC & ATC (RMGF T&A)
No
Yes
TFCO
MOD-008-0
Documentation and Control of Each Regional Transmission Reliability Margin Methodology Documentation and Control of Each Regional Transmission Reliability Margin Methodology Documentation and Control of Each Regional Transmission Reliability Margin Methodology
R1.1
RMGF T&A
Per Methodology
No
Yes
TFCO
MOD-008-0
R1.2
Specify how TRM values are incorporated into Available Transfer Capability calculations.
RMGF T&A
Per Methodology
No
Yes
TFCO
MOD-008-0
R1.3
Specify the uncertainties accounted for in TRM and the methods used to determine their RMGF T&A impacts on the TRM values. Any component of uncertainty, other than those identified in MOD-008-0_R1.3.1 through MOD-008-0_R1.3.7, shall benefit the interconnected transmission systems as a whole before they shall be permitted to be included in TRM calculations. The components of uncertainty identified in MOD-008- 0_R1.3.1 through MOD-008-0_R1.3.7, if applied, shall be accounted for solely in TRM and not CBM.
Per Methodology
No
Yes
TFCO
MOD-008-0
R1.3.1
Aggregate Load forecast error (not included in determining generation reliability requirements).
RMGF T&A
Per Methodology
No
Yes
TFCO
Page 43 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
MOD-008-0
Documentation and Control of Each Regional Transmission Reliability Margin Methodology Documentation and Control of Each Regional Transmission Reliability Margin Methodology Documentation and Control of Each Regional Transmission Reliability Margin Methodology Documentation and Control of Each Regional Transmission Reliability Margin Methodology Documentation and Control of Each Regional Transmission Reliability Margin Methodology Documentation and Control of Each Regional Transmission Reliability Margin Methodology Documentation and Control of Each Regional Transmission Reliability Margin Methodology Documentation and Control of Each Regional Transmission Reliability Margin Methodology Documentation and Control of Each Regional Transmission Reliability Margin Methodology Documentation and Control of Each Regional Transmission Reliability Margin Methodology Documentation and Control of Each Regional Transmission Reliability Margin Methodology Procedure for Verifying Transmission Reliability Margin Values
R1.3.2
RMGF T&A
Per Methodology
Yes
TFCO
MOD-008-0
R1.3.3
Variations in facility Loadings due to balancing of generation within a Balancing Authority Area.
RMGF T&A
Per Methodology
No
Yes
TFCO
MOD-008-0
R1.3.4
RMGF T&A
Per Methodology
No
Yes
TFCO
MOD-008-0
R1.3.5
RMGF T&A
Per Methodology
No
Yes
TFCO
MOD-008-0
R1.3.6
RMGF T&A
Per Methodology
No
Yes
TFCO
MOD-008-0
R1.3.7
RMGF T&A
Per Methodology
No
Yes
TFCO
MOD-008-0
R1.3.8
Short-term System Operator response (Operating Reserve actions not exceeding a 59minute window).
RMGF T&A
Per Methodology
No
Yes
TFCO
MOD-008-0
R1.4
Describe the conditions, if any, under which TRM may be available to the market as Non- RMGF T&A Firm Transmission Service.
Per Methodology
No
Yes
TFCO
MOD-008-0
R1.5
Describe the formal process for the Regional Reliability Organization to grant any variances to individual Transmission Service Providers from the Regional TRM methodology.
A1 Criteria for A1 - Members may request the lead Task Force, at any time, to review and revise the Criteria, or portions Review & thereof, and have the right to enter into the NPCC Appeals and Dispute Resolution Process for nonApproval of compliance issues. Documents) NPCC TTC & Per the NPCC TTC & ATC web site. ATC Web Site
No
Yes
TFCO
MOD-008-0
R1.5
Describe the formal process for the Regional Reliability Organization to grant any variances to individual Transmission Service Providers from the Regional TRM methodology.
No
Yes
TFCO
MOD-008-0
R2
The Regional Reliability Organization shall make its most recent version of the NPCC TTC & Per the NPCC TTC & ATC web site. documentation of its TRM methodology available on a web site accessible by NERC, the ATC Web Site Regional Reliability Organizations, and transmission users.
No
Yes
TFCO
MOD-009-0
R1
Each Regional Reliability Organization, in conjunction with its members, shall develop and implement a procedure to review Transmission Reliability Margin (TRM) calculations and resulting values of member Transmission Service Providers to ensure they comply with the Regional TRM methodology, and are periodically updated and available to transmission users. This procedure shall include the following four required elements:
NPCC CO-13 Needs to be added to our TTC/ATC Methodology Regional Methodology & Guidelines For Forecasting TTC & ATC (RMGF T&A)
No
TFCO
Page 44 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
MOD-009-0
Procedure for Verifying Transmission Reliability Margin Values Procedure for Verifying Transmission Reliability Margin Values Procedure for Verifying Transmission Reliability Margin Values
R1.1
Indicate the frequency under which the verification review shall be implemented.
none
Working Group CO-13 is not currently conducting reviews of TRM Working Group CO-13 only reviews methodology on an asneeded basis Working Group CO-13 is not currently conducting reviews of TRM
Yes
TFCO
MOD-009-0
R1.2
Require review of the process by which TRM values are updated, and their frequency of none update, to ensure that the most current TRM values are available to transmission users.
No
Yes
TFCO
MOD-009-0
R1.3
Require review of the consistency of the Transmission Service Providers TRM components with its published planning criteria. A TRM value is considered consistent with published planning criteria if the same components that comprise TRM are also addressed in the planning criteria. The methodology used to determine and apply TRM does not have to involve the same mechanics as the planning process, but the same uncertainties must be considered and any simplifying assumption explained.
none
No
Yes
TFCO
MOD-009-0
R1.4
Require TRM values to be periodically updated (at least prior to each season winter, spring, summer, and fall), as necessary, and made available to the Regional Reliability Organizations, NERC, and transmission users.
NPCC CO-13 Needs to be added to our TTC/ATC Methodology Regional Methodology & Guidelines For Forecasting TTC & ATC (RMGF T&A)
No
Yes
TFCO
MOD-009-0
Procedure for Verifying Transmission Reliability Margin Values Procedure for Verifying Transmission Reliability Margin Values Steady-State Data for Modeling and Simulation of the Interconnected Transmission System
R2
The Regional Reliability Organization shall make documentation of its Regional TRM review procedure available to NERC on request (within 30 calendar days).
none
No
Working Group CO-13 is not currently conducting reviews of TRM Working Group CO-13 is not currently conducting reviews of TRM
Yes
TFCO
MOD-009-0
R3
The Regional Reliability Organization shall make documentation of the results of the none most current implementation of its TRM review procedure available to NERC on request (within 30 calendar days). The Transmission Owners, Transmission Planners, Generator Owners, and Resource C29 Sec. 1.0 Planners (specified in the data requirements and reporting procedures of MOD-0110_R1) shall provide appropriate equipment characteristics, system data, and existing and future Interchange Schedules in compliance with its respective Interconnection Regional steady-state modeling and simulation data requirements and reporting procedures as defined in Reliability Standard MOD-011-0_R1.
No
Yes
TFCO
MOD-010-0
R1
Actual The detailed data of system components will be maintained and updated by the purchasers, sellers, No marketers and load-serving entities and provided to NPCC accurately and timely as needed for system analysis and distribution. This data may be required on an aggregated independent system operator, power pool, individual system or on a dispersed substation basis for system modeling and reliability analysis. Complete, accurate and timely data is needed for system analyses to ensure the adequacy and security of the interconnected transmission systems, to meet projected customer demands and to determine the need for system enhancements or reinforcements. System analyses include steady-state, transient and dynamic simulations of the electrical networks. Data requirements include electric power transactions, system components, system configuration and customer demands.
No
TFSS
MOD-010-0
Steady-State Data for Modeling and Simulation of the Interconnected Transmission System
R2
The Transmission Owners, Transmission Planners, Generator Owners, and Resource C29 Sec. 2.2 & Planners (specified in the data requirements and reporting procedures of MOD-0112.3 0_R1) shall provide this steady-state modeling and simulation data to the Regional Reliability Organizations, NERC, and those entities specified within Reliability Standard MOD-011-0_R1. If no schedule exists, then these entities shall provide the data on request (30 calendar days).
No 2.2 Generation and Transmission Facility Owners must develop and maintain data for their facilities suitable for load flow and dynamic modeling and analysis as required by the NPCC Working Groups. Facilities owners must also develop and maintain short-circuit data. Facility owners must provide this data, in a suitable format, on request. Data providedmust comply with the NERC MMWG and SSDDWG Procedural Documents and the procedures herein. 2.3 Load-serving entities shall provide actual and forecast demands for their respective customers for steady state and dynamics system modeling in a timely manner. Purchasers, sellers, marketers and load-serving entities shall provide their existing and future contracted firm (non-recallable reserved) capacity transactions (including sources, sinks, amounts, duration, associated transmission, etc.) for steady-state and dynamics modeling in a timely manner.
No
TFSS
Page 45 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
MOD-011-0
R1
The Regional Reliability Organizations within an Interconnection, in conjunction with A2 Sec. 1.0 the Transmission Owners, Transmission Planners, Generator Owners, and Resource Planners, shall develop comprehensive steady-state data requirements and reporting procedures needed to model and analyze the steady-state conditions for each of the NERC Interconnections: Eastern, Western, and ERCOT. Within an Interconnection, the Regional Reliability Organization shall jointly coordinate the development of the data requirements and reporting procedures for that Interconnection. The Interconnection-wide requirements shall include the following steady-state data requirements (see R1.1, R1.2, etc. below):
Through its committees and task forces, the Council shall conduct regional and interregional studies, and assess and monitor Area studies and operations to assure conformance to the criteria.
Yes
TFSS
MOD-011-0
Maintenance and Distribution of SteadyState Data Requirements and Reporting Procedures Maintenance and Distribution of SteadyState Data Requirements and Reporting Procedures
R1.1
Bus (substation): name, nominal voltage, electrical demand supplied (consistent with the C29 Sec. 2.2.1, 2.2.1 (applies to Generation facilities) Bus (substation and switching stations): names, nominal voltage No aggregated and dispersed substation demand data supplied per Reliability Standards 2.2.7 & 2.3 and location. 2.2.7 (applies to Transmission facilities) identical to 2.2.1 above. 2.3 Load-serving entities MOD-016-0, MOD-017-0, and MOD-020-0), and location. shall provide actual and forecast demands for their respective customers for steady state and dynamics system modeling in a timely manner. Generating Units (including synchronous condensers, pumped storage, etc.): location, minimum and maximum Ratings (net Real and Reactive Power), regulated bus and voltage set point, and equipment status. C29 Sec. 2.2.2 Generating Units (including synchronous condensers, pumped storage, etc.): location, minimum and maximum Ratings (gross Real and Reactive Power), regulated bus and voltage set point, maintenance requirements as appropriate to the analysis, station service and auxiliary loads and dynamics data. No
Yes
TFSS
MOD-011-0
R1.2
NPCC specifies gross Yes quantities instead of net, but compensates for this by also requiring station service load data.
TFSS
MOD-011-0
Maintenance and Distribution of SteadyState Data Requirements and Reporting Procedures Maintenance and Distribution of SteadyState Data Requirements and Reporting Procedures
R1.3
AC Transmission Line or Circuit (overhead and underground): nominal voltage, impedance, line charging, Normal and Emergency Ratings (consistent with methodologies defined and Ratings supplied per Reliability Standard FAC-004-0 and FAC-005-0 ) equipment status, and metering locations. DC Transmission Line (overhead and underground): line parameters, Normal and Emergency Ratings, control parameters, rectifier data, and inverter data.
AC Transmission Line or Circuit (overhead and underground): nominal voltage, impedance, line charging, nominal and emergency ratings based on the most limiting element in the circuit, maintenance requirements as appropriate to the analysis and metering locations.
No
Yes
TFSS
MOD-011-0
R1.4
C29 Sec. 2.2.11 Detailed dynamics data for all other facilities of significance and pertinent to dynamic simulations such as static-var compensators, FACTS devices, synchronous motors, HVdc facilities, relay loads, etc. Data must include complete and accurate controls models suitable for integration.
No
NPCC only calls for Yes dynamics data on these facilities instead of steady state as required by MOD-011-0 Yes
TFSS
MOD-011-0
Maintenance and Distribution of SteadyState Data Requirements and Reporting Procedures Maintenance and Distribution of SteadyState Data Requirements and Reporting Procedures Maintenance and Distribution of SteadyState Data Requirements and Reporting Procedures Maintenance and Distribution of SteadyState Data Requirements and Reporting Procedures
R1.5
Transformer (voltage and phase-shifting): nominal voltages of windings, impedance, tap C29 Sec. 2.2.3 ratios (voltage and/or phase angle or tap step size), regulated bus and voltage set point, & 2.2.9 Normal and Emergency Ratings (consistent with methodologies defined and Ratings supplied per Reliability Standard FAC-004-0 and FAC-005-0.), and equipment status. Reactive Compensation (shunt and series capacitors and reactors): nominal Ratings, impedance, percent compensation, connection point, and controller device.
2.2.3 (applies to Generator facilities) -Transformer (voltage and phase-shifting): nominal voltages of windings, impedance, tap ratios (voltage and/or phase angle or tap step size), regulated bus and voltage set point, Normal and Emergency Ratings and maintenance requirements as appropriate to the analysis. 2.2.9 (applies to Transmission facilities) Identical to 2.2.3 above.
No
TFSS
MOD-011-0
R1.6
No
Yes
TFSS
MOD-011-0
R1.7
Purchasers, sellers, marketers and load-serving entities shall provide their existing and future contrated firm (non-recallable reserved) capacity transactions (including sources, sinks, amounts, duration, associated transmission, etc.) for steady-state and dynamics system modeling in a timely fashion.
No
Yes
TFSS
MOD-011-0
R2
The Regional Reliability Organizations within an Interconnection shall document their Interconnections steady-state data requirements and reporting procedures, shall review those data requirements and reporting procedures (at least every five years), and shall make the data requirements and reporting procedures available on request ( within five business days) to Regional Reliability Organizations, NERC, and all users of the interconnected transmission systems.
The NPCC Base Case Development (BCD) Working Group (SS-37) will develop a library of base case load No flow and dynamics models each year for internal use by NPCC, its members and NERC Multiregional Modeling Working Group. The TFSS, to meet the needs of the members and other groups, will establish the individual cases, which collectively comprise the library, each year. This annual development of base cases will serve as the main vehicle by which system data is collected and disseminated for internal use by NPCC and its members. It is expected that the system(s) conducting a study may find it necessary to expand and/or update the representation of system conditions and facilities in the area of particular concern.
NPCC does not have a requirement that the information must be made available within 5 business days.
Yes
TFSS
Page 46 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
MOD-012-0
Dynamics Data for Modeling and Simulation of the Interconnected Transmission System
R1
The Transmission Owners, Transmission Planners, Generator Owners, and Resource Planners (specified in the data requirements and reporting procedures of MOD-0130_R1) shall provide appropriate equipment characteristics and system data in compliance with the respective Interconnection-wide Regional dynamics system modeling and simulation data requirements and reporting procedures as defined in Reliability Standard MOD-013-0_R1.
Actual and forecast data of all the components including load are required to analyze, study and plan the No interconnected electric system. The detailed data of system components will be maintained and updated by the purchasers, sellers, marketers and load-serving entities and provided to NPCC accurately and timely as needed for system analysis and distribution. This data may be required on an aggregated independent system operator, power pool, individual system or on a dispersed substation basis for system modeling and reliability analysis. Complete, accurate and timely data is needed for system analyses to ensure the adequacy and security of the interconnected transmission systems, to meet projected customer demands and to determine the need for system enhancements or reinforcements. System analyses include steady-state, transient and dynamic simulations of the electrical networks. Data requirements include electric power transactions, system components, system configuration and customer demands.
Yes
TFSS
MOD-012-0
Dynamics Data for Modeling and Simulation of the Interconnected Transmission System
R2
The Transmission Owners, Transmission Planners, Generator Owners, and Resource Planners (specified in the data requirements and reporting procedures of MOD-0130_R1) shall provide dynamics system modeling and simulation data to its Regional Reliability Organization(s), NERC, and those entities specified within the applicable reporting procedures identified in Reliability Standard MOD-013-0_R1. If no schedule exists, then these entities shall provide data on request (30 calendar days).
C29 Sec. 2.2 & 2.2 Generation and Transmission Facility Owners must develop and maintain data for their facilities No 2.3 suitable for load flow and dynamic modeling and analysis as required by the NPCC Working Groups. Facilities owners must also develop and maintain short-circuit data. Facility owners must provide this data, in a suitable format, on request. Data providedmust comply with the NERC MMWG and SSDDWG Procedural Documents and the procedures herein. 2.3 Load-serving entities shall provide actual and forecast demands for their respective customers for steady state and dynamics system modeling in a timely manner. Purchasers, sellers, marketers and load-serving entities shall provide their existing and future contracted firm (non-recallable reserved) capacity transactions (including sources, sinks, amounts, duration, associated transmission, etc.) for steady-state and dynamics modeling in a timely manner.
Yes
TFSS
MOD-013-0
R1
The Regional Reliability Organization, in coordination with its Transmission Owners, A2 Sec. 1.0 Transmission Planners, Generator Owners, and Resource Planners, shall develop comprehensive dynamics data requirements and reporting procedures needed to model and analyze the dynamic behavior or response of each of the NERC Interconnections: Eastern, Western, and ERCOT. Within an Interconnection, the Regional Reliability Organizations shall jointly coordinate on the development of the data requirements and reporting procedures for that Interconnection. Each set of Interconnection-wide dynamics data requirements shall include the following dynamics data requirements:
Through its committees and task forces, the Council shall conduct regional and interregional studies, and assess and monitor Area studies and operations to assure conformance to the criteria.
No
Yes
TFSS
MOD-013-0
R1.1
Unit-specific dynamics data shall be reported for generators and synchronous condensers C29 Sec. 2.2.4 (including, as appropriate to the model, items such as inertia constant, damping coefficient, saturation parameters, and direct and quadrature axes reactances and time constants), excitation systems, voltage regulators, turbine-governor systems, power system stabilizers, and other associated generation equipment. Estimated or typical manufacturers dynamics data, based on units of similar design and C29 Sec. 2.2.5 characteristics, may be submitted when unit-specific dynamics data cannot be obtained. & 2.2.4 In no case shall other than unit-specific data be reported for generator units installed after 1990. The Interconnection-wide requirements shall specify unit size thresholds for permitting: The use of non-detailed vs. detailed models, The netting of small generating units with bus load, and The combining of multiple generating units at one plant. C29 Sec. 2.1.6
Detailed unit-specific dynamics data for generators, excitation systems, voltage regulators, turbine-governor systems, power system stabilizers, relays and protection equipment (out-of-step, overspeed, etc.) and other associated equipment. This includes complete and accurate models of controls suitable for integration with the analytical software.
No
Yes
TFSS
MOD-013-0
Maintenance and Distribution of Dynamics Data Requirements and Reporting Procedures Maintenance and Distribution of Dynamics Data Requirements and Reporting Procedures
R1.1.1
2.2.5 Typical manufacturers dynamics data, based on units of similar design and characteristics, may be No used when unit-specific dynamics data cannot be obtained. 2.2.4 In no case shall other than unit-specific data be used for generator units installed after 1990.
Yes
TFSS
MOD-013-0
R1.1.2
Representation of Units and Plants Units at a particular bus may be lumped together and represented as one No unit when they have the same electrical and control characteristics. Units that are lumped together should be rated less than 50 MVA each and the units lumped together at any location should have a combined rating of not more than 300 MVA. Units or plants rated less than 20 MVA may be netted with loads. The netting or lumping of units and plants in excess of the guidelines above is acceptable only when such representations are deemed acceptable for systems studies in the judgment of the Areas affected.
Yes
TFSS
MOD-013-0
Maintenance and Distribution of Dynamics Data Requirements and Reporting Procedures Maintenance and Distribution of Dynamics Data Requirements and Reporting Procedures
R1.2
Device specific dynamics data shall be reported for dynamic devices, including, among others, static VAR controllers, high voltage direct current systems, flexible AC transmission systems, and static compensators.
C29 Sec. 2.2.11 Detailed dynamics data for all other facilities of significance and pertinent to dynamic simulations such as static-var compensators, FACTS devices, synchronous motors, HVdc facilities, relay loads, etc. Data must include complete and accurate controls models suitable for integration.
No
Yes
TFSS
MOD-013-0
R1.3
Dynamics data representing electrical demand characteristics as a function of frequency C18 Sec. 3.0 and voltage.
Each Area shall specify the appropriate Area load representation (e.g. P and Q as a function of voltage) for use in NPCC reliability studies. This applies to long term stability test or post-transient loadflow as well as transient stability tests.
No
Yes
TFSS
Page 47 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
MOD-013-0
R1.4
Dynamics data shall be consistent with the reported steady-state (power flow) data supplied per Reliability Standard MOD-010-0_R1.
ActualActual and forecast data of all the components including load are required to analyze, study and plan No the interconnected electric system. The detailed data of system components will be maintained and updated by the purchasers, sellers, marketers and load-serving entities and provided to NPCC accurately and timely as needed for system analysis and distribution. This data may be required on an aggregated independent system operator, power pool, individual system or on a dispersed substation basis for system modeling and reliability analysis. Complete, accurate and timely data is needed for system analyses to ensure the adequacy and security of the interconnected transmission systems, to meet projected customer demands and to determine the need for system enhancements or reinforcements. System analyses include steady-state, transient and dynamic simulations of the electrical networks. Data requirements include electric power transactions, system components, system configuration and customer demands.
Yes
TFSS
MOD-013-0
R2
The Regional Reliability Organization shall participate in the documentation of its C29 Sec. 2.0 Interconnections data requirements and reporting procedures and, shall participate in the review of those data requirements and reporting procedures (at least every five years), and shall provide those data requirements and reporting procedures to Regional Reliability Organizations, NERC, and all users of the Interconnected systems on request (within five business days).
The NPCC Base Case Development (BCD) Working Group (SS-37) will develop a library of base case load No flow and dynamics models each year for internal use by NPCC, its members and NERC Multiregional Modeling Working Group. The TFSS, to meet the needs of the members and other groups, will establish the individual cases, which collectively comprise the library, each year. This annual development of base cases will serve as the main vehicle by which system data is collected and disseminated for internal use by NPCC and its members. It is expected that the system(s) conducting a study may find it necessary to expand and/or update the representation of system conditions and facilities in the area of particular concern.
NPCC does not have a requirement that the information must be made available within 5 business days
Yes
TFSS
MOD-014-0
R1
The Regional Reliability Organization(s) within each Interconnection shall coordinate C29 Sec. 2.0 and jointly develop and maintain a library of solved (converged) Interconnection-specific steady state system models. The Interconnection-specific models shall include near- and longer-term planning horizons that are representative of system conditions for projected seasonal peak, minimum, and other appropriate system demand levels.
The NPCC Base Case Development (BCD) Working Group (SS-37) will develop a library of base case load No flow and dynamics models each year for internal use by NPCC, its members and NERC Multiregional Modeling Working Group. The TFSS, to meet the needs of the members and other groups, will establish the individual cases, which collectively comprise the library, each year. This annual development of base cases will serve as the main vehicle by which system data is collected and disseminated for internal use by NPCC and its members. It is expected that the system(s) conducting a study may find it necessary to expand and/or update the representation of system conditions and facilities in the area of particular concern.
Yes
TFSS
MOD-014-0
R2
The Regional Reliability Organization(s) within each Interconnection shall coordinate and jointly develop steady-state system models annually for selected study years, as determined by the Regional Reliability Organizations within its Interconnection. The Regional Reliability Organization shall provide the most recent solved (converged) Interconnection-specific steady state models to NERC in accordance with each Interconnections schedule for submission.
B4 Sec. 1.0
B4 Sec. 1.0 - NPCC has established a Reliability Assessment Program to bring together work done by Yes the Council, its member systems and Areas relevant to the assessment of bulk power system reliability. As part of the Reliability Assessment Program, the Task Force on System Studies (TFSS) is charged on an ongoing basis with conducting periodic reviews of the reliability of the planned bulk power transmission system of each Area of NPCC and the transmission interconnections to other Areas . The purpose of these reviews is to determine whether each Areas planned bulk power transmission system is in conformance with the NPCC Basic Criteria for Design and Operation of Interconnected Power Systems (Document A-2). Since it is NPCCs intention that the Basic Criteria be consistent with the NERC Planning Standards , conformance with the NPCC Basic Criteria assures consistency with the NERC Planning Standards . The data and models should be provided to members on request .
NPCC should update this Yes requirement to refer to the Version0 Standards instead of the old NERC Planning Standards. Also, NPCC should specifically state that the information will be made available to NERC on request (although this is implied by the existing words in R1 above)
TFSS
MOD-014-0
R2
The Regional Reliability Organization(s) within each Interconnection shall coordinate and jointly develop steady-state system models annually for selected study years, as determined by the Regional Reliability Organizations within its Interconnection. The Regional Reliability Organization shall provide the most recent solved (converged) Interconnection-specific steady state models to NERC in accordance with each Interconnections schedule for submission.
B4 Sec. 1.0
B4 Sec. 1.0 (continued) - To assist the TFSS in carrying out this charge, each NPCC Area shall conduct an No annual assessment of the reliability of the planned bulk power transmission system within the Area and the transmission interconnections to other Areas (an Area Transmission Review), in accordance with these Guidelines, and present a report of this assessment to the TFSS for review. Each Area is also responsible for providing an annual report to the Compliance Monitoring and Assessment Subcommittee in regard to its Area Transmission Review in accordance with the NPCC Reliability Compliance and Enforcement Program (Document A-8). B8 Introduction As part of the NPCC Reliability Assessment Program, the Task Force on Coordination of Planning is charged, on an ongoing basis, with conducting reviews of resource adequacy of each Area of NPCC. Resources refer to the total contributions provided by supply-side and demand-side facilities and/or actions. The NPCC Base Case Development (BCD) Working Group (SS-37) will develop a library of base case load No flow and dynamics models each year for internal use by NPCC, its members and NERC Multiregional Modeling Working Group. The TFSS, to meet the needs of the members and other groups, will establish the individual cases, which collectively comprise the library, each year. This annual development of base cases will serve as the main vehicle by which system data is collected and disseminated for internal use by NPCC and its members. It is expected that the system(s) conducting a study may find it necessary to expand and/or update the representation of system conditions and facilities in the area of particular concern.
Yes
TFSS
MOD-014-0
R2
Yes
TFSS
MOD-015-0
R1
The Regional Reliability Organization(s) within each Interconnection shall coordinate and jointly develop and maintain a library of initialized (with no Faults or system Disturbances) Interconnection-specific dynamics system models linked to the steadystate system models, as appropriate, of Reliability Standard MOD-014-0_R1.
Yes
TFSS
Page 48 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
MOD-015-0
R1.1
The Regional Reliability Organization(s) shall develop Interconnection-specific C29 Sec. 2.0 dynamics system models for at least two timeframes (present or near-term model and a future or longer-term model), and additional seasonal and demand level models, as necessary, to analyze the dynamic response of that Interconnection. The Regional Reliability Organization(s) shall develop Interconnection-specific B4 Sec. 2.0 dynamics system models for at least two timeframes (present or near-term model and a future or longer-term model), and additional seasonal and demand level models, as necessary, to analyze the dynamic response of that Interconnection.
Yes
TFSS
MOD-015-0
R1.1
B4 Sec. 2.0 - The purpose of the presentation associated with an Area Transmission Review is to No demonstrate that the Areas planned transmission system, based on its projection of available resources, is in conformance with the NPCC Basic Criteria . By such a presentation, the Task Force will satisfy itself that the criteria have been met and, in general, that the reliability of the NPCC Interconnected Systems will be maintained. Analysis of this material should include a review of Special Protection Systems, as well as an assessment of the potential for widespread cascading due to overloads, instability or voltage collapse . In addition, the potential consequences of failure or misoperation of Dynamic Control Systems should be addressed. B4 Sec. 3.0 - It is suggested that a study year of 4 to 6 years from the reporting date is a realistic one, both from the viewpoint of minimum lead times required for construction, and the ability to alter plans or facilities. No
Yes
TFSS
MOD-015-0
R1.1
The Regional Reliability Organization(s) shall develop Interconnection-specific dynamics system models for at least two timeframes (present or near-term model and a future or longer-term model), and additional seasonal and demand level models, as necessary, to analyze the dynamic response of that Interconnection.
B4 Sec.3.0
Yes
TFSS
MOD-015-0
R2
The Regional Reliability Organization(s) within each Interconnection shall develop B4 Sec. 1.0, Interconnection dynamics system models for their Interconnection annually for selected study years as determined by the Regional Reliability Organization(s) within each Interconnection and shall provide the most recent initialized (approximately 25 seconds, no-fault) models to NERC in accordance with each Interconnections schedule for submission. The Regional Reliability Organization(s) within each Interconnection shall develop B4 Sec. 1.0 Interconnection dynamics system models for their Interconnection annually for selected study years as determined by the Regional Reliability Organization(s) within each Interconnection and shall provide the most recent initialized (approximately 25 seconds, no-fault) models to NERC in accordance with each Interconnections schedule for submission.
B4 Sec. 1.0 - each NPCC Area shall conduct an annual assessment of the reliability of the planned bulk No power transmission system within the Area and the transmission interconnections to other Areas (an Area Transmission Review), in accordance with these Guidelines, and present a report of this assessment to the TFSS for review. Each Area is also responsible for providing an annual report to the Compliance Monitoring and Assessment Subcommittee in regard to its Area Transmission Review in accordance with the NPCC Reliability Compliance and Enforcement Program. The format of Area Transmission Reviews requires: No
NPCCs document-(this Yes part of B4 is OK but see next page for the relevant sections of concern)
TFSS
MOD-015-0
R2
NPCC does not specify Yes the length of time for a dynamics run and also does not specify that the information must be made available to NERC
TFSS
MOD-015-0
R2
The Regional Reliability Organization(s) within each Interconnection shall develop 5.1.2b Interconnection dynamics system models for their Interconnection annually for selected study years as determined by the Regional Reliability Organization(s) within each Interconnection and shall provide the most recent initialized (approximately 25 seconds, no-fault) models to NERC in accordance with each Interconnections schedule for submission.
No
NPCC does not specify Yes the length of time for a dynamics run and also does not specify that the information must be made available to NERC
TFSS
MOD-015-0
R2
The Regional Reliability Organization(s) within each Interconnection shall develop 5.1.2c Interconnection dynamics system models for their Interconnection annually for selected study years as determined by the Regional Reliability Organization(s) within each Interconnection and shall provide the most recent initialized (approximately 25 seconds, no-fault) models to NERC in accordance with each Interconnections schedule for submission.
No
NPCC does not specify Yes the length of time for a dynamics run and also does not specify that the information must be made available to NERC
TFSS
MOD-015-0
R2
The Regional Reliability Organization(s) within each Interconnection shall develop 5.1.2d Interconnection dynamics system models for their Interconnection annually for selected study years as determined by the Regional Reliability Organization(s) within each Interconnection and shall provide the most recent initialized (approximately 25 seconds, no-fault) models to NERC in accordance with each Interconnections schedule for submission.
No
NPCC does not specify Yes the length of time for a dynamics run and also does not specify that the information must be made available to NERC
TFSS
MOD-015-0
R2
The Regional Reliability Organization(s) within each Interconnection shall develop C29 Sec. 2.0 Interconnection dynamics system models for their Interconnection annually for selected study years as determined by the Regional Reliability Organization(s) within each Interconnection and shall provide the most recent initialized (approximately 25 seconds, no-fault) models to NERC in accordance with each Interconnections schedule for submission.
C29 Sec. 2.0 The data and models should be provided to members on request.
No
NPCC does not specify Yes the length of time for a dynamics run and also does not specify that the information must be made available to NERC
TFSS
Page 49 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
MOD-016-0
Documentation of Data Reporting Requirements for Actual and Forecast Demands, Net Energy for Load, and Controllable Demand-Side Management
R1
The Planning Authority and Regional Reliability Organization shall have documentation none identifying the scope and details of the actual and forecast (a) Demand data, (b) Net Energy for Load data, and (c) controllable DSM data to be reported for system modeling and reliability analyses.
None
Yes
TFSS
MOD-016-0
Documentation of Data Reporting Requirements for Actual and Forecast Demands, Net Energy for Load, and Controllable Demand-Side Management
R1.1
The aggregated and dispersed data submittal requirements shall ensure that consistent data is supplied for Reliability Standards TPL-005-0, TPL-006-0, MOD-010-0, MOD011-0, MOD-012-0, MOD-013-0, MOD-014-0, MOD-015-0, MOD-016, MOD-0170, MOD-018-0, MOD-019-0, MOD-020-0, and MOD-021-0.
None
none
No
Yes
TFSS
MOD-016-0
Documentation of Data Reporting Requirements for Actual and Forecast Demands, Net Energy for Load, and Controllable Demand-Side Management
R2
The documentation of the scope and details of the data reporting requirements shall be available on request (five business days).
none
None
Yes
Yes
TFSS
MOD-017-0
Aggregated Actual and Forecast Demands and Net Energy for Load
R1
The Load-Serving Entity, Planning Authority and Resource Planner shall each provide none the following information annually on an aggregated Regional, subregional, Power Pool, individual system, or Load-Serving Entity basis to NERC, the Regional Reliability Organizations, and any other entities specified by the documentation in Standard MOD016-0_R1. Integrated hourly demands in megawatts (MW) for the prior year. none
None
No
No
TFSS
MOD-017-0
MOD-017-0
MOD-017-0
MOD-017-0
MOD-018-0
Aggregated Actual and Forecast Demands and Net Energy for Load Aggregated Actual and Forecast Demands and Net Energy for Load Aggregated Actual and Forecast Demands and Net Energy for Load Aggregated Actual and Forecast Demands and Net Energy for Load Treatment of Non-member Demand Data and How Uncertainties are Addressed in the Forecasts of Demand and Net Energy for Load Treatment of Non-member Demand Data and How Uncertainties are Addressed in the Forecasts of Demand and Net Energy for Load Treatment of Non-member Demand Data and How Uncertainties are Addressed in the Forecasts of Demand and Net Energy for Load
R1.1
none
No
No
TFSS
R1.2
Monthly and annual peak hour actual demands in MW and Net Energy for Load in gigawatthours (GWh) for the prior year. Monthly peak hour forecast demands in MW and Net Energy for Load in GWh for the next two years.
none
none
No
No
TFSS
R1.3
none
none
No
No
TFSS
R1.4
Annual Peak hour forecast demands (summer and winter) in MW and annual Net Energy none for load in GWh for at least five years and up to ten years into the future, as requested. The Load-Serving Entity, Planning Authority, Transmission Planner and Resource none Planners report of actual and forecast demand data (reported on either an aggregated or dispersed basis) shall:
none
No
No
TFSS
R1
None
No
No
TFSS
MOD-018-0
R1.1
Indicate whether the demand data of nonmember entities within an area or Regional Reliability Organization are included, and
none
none
No
No
TFSS
MOD-018-0
R1.2
Address assumptions, methods, and the manner in which uncertainties are treated in the forecasts of aggregated peak demands and Net Energy for Load.
None
none
No
No
TFSS
Page 50 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
MOD-018-0
Treatment of Non-member Demand Data and How Uncertainties are Addressed in the Forecasts of Demand and Net Energy for Load Treatment of Non-member Demand Data and How Uncertainties are Addressed in the Forecasts of Demand and Net Energy for Load Reporting of Interruptible Demands and Direct Control Load Management
R1.3
Items (MOD-018-0_R1.1) and (MOD-018-0_R1.2) shall be addressed as described in the reporting procedures developed for Standard MOD-016-0_R1.
none
None
No
TFSS
MOD-018-0
R2
The Load-Serving Entity, Planning Authority, Transmission Planner and Resource Planner shall each report data associated with Reliability Standard MOD-018-0_R1 to NERC, the Regional Reliability Organization, Load-Serving Entity, Planning Authority, and Resource Planner on request (within 30 calendar days).
none
None
No
No
TFSS
MOD-019-0
R1
The Load-Serving Entity, Planning Authority, Transmission Planner, and Resource Planner shall each provide annually its forecasts of interruptible demands and Direct Control Load Management (DCLM) data for at least five years and up to ten years into the future, as requested, for summer and winter peak system conditions to NERC, the Regional Reliability Organizations, and other entities (Load-Serving Entities, Planning Authorities, and Resource Planners) as specified by the documentation in Reliability Standard MOD-016-0_R1.
none
None
No
No
TFSS
MOD-020-0
Providing Interruptible Demands and Direct Control Load Management Data to System Operators and Reliability Coordinators Documentation of the Accounting Methodology for the Effects of Controllable Demand-Side Management in Demand and Energy Forecasts
R1
The Load-Serving Entity, Transmission Planner, and Resource Planner shall each make none known its amount of interruptible demands and Direct Control Load Management (DCLM) to Transmission Operators, Balancing Authorities, and Reliability Coordinators on request within 30 calendar days.
NonN
No
No
TFSS
MOD-021-0
R1
The Load-Serving Entity Transmission Planner and Resource Planners forecasts shall each clearly document how the Demand and energy effects of DSM programs (such as conservation, time-of-use rates, interruptible Demands, and Direct Control Load Management) are addressed.
none
None None
No
No
TFSS
MOD-021-0
Documentation of the Accounting Methodology for the Effects of Controllable Demand-Side Management in Demand and Energy Forecasts
R2
The Load-Serving Entity, Transmission Planner and Resource Planner shall each include None information detailing how Demand-Side Management measures are addressed in the forecasts of its Peak Demand and annual Net Energy for Load in the data reporting procedures of Standard MOD-016-0_R1.
None
No
No
TFSS
MOD-021-0
Documentation of the Accounting Methodology for the Effects of Controllable Demand-Side Management in Demand and Energy Forecasts
R3
The Load-Serving Entity, Transmission Planner and Resource Planner shall each make documentation on the treatment of its DSM programs available to NERC on request (within 30 calendar days).
none
None
Yes
No
TFSS
MOD-024-1
R1 The Regional Reliability Organization shall establish and maintain procedures to address verification of generator gross and net Real Power capability. These procedures shall include the following: R1.1. Generating unit exemption Criteria including documentation of those units that are exempt from a portion or all of these procedures. R1.2. Criteria for reporting generating unit auxiliary loads. R1.3. Acceptable methods for model and data verification, including any applicable conditions under which the data should be verified. Such methods can include use of manufacturer data, commissioning data, performance tracking, and testing, etc.
TFSS
TFSS R1.4. Periodicity and schedule of model and data verification and reporting. R1.5. Information to be verified and reported: R1.5.1. Seasonal gross and net Real Power generating capabilities. TFSS TFSS
Page 51 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
R1.5.2. Real power requirements of auxiliary loads. R1.5.3. Method of verification, including date and conditions. MOD-024-1 Verification of Generator Gross and Net Real Power Capability R2 The Regional Reliability Organization shall provide its generator gross and net Real Power capability verification and reporting procedures, and any changes to those procedures, to the Generator Owners, Generator Operators, Transmission Operators, Planning Authorities, and Transmission Planners affected by the procedure within 30 calendar days of the approval. R3 The Generator Owner shall follow its Regional Reliability Organizations procedures for verifying and reporting its gross and net Real Power generating capability per R1. R1 The Regional Reliability Organization shall establish and maintain procedures to address verification of generator gross and net Reactive Power capability. These procedures shall include the following: R1.1. Generating unit exemption Criteria including documentation of those units that are exempt from a portion or all of these procedures. R1.2. Criteria for reporting generating unit auxiliary loads. R1.3. Acceptable methods for model and data verification, including any applicable conditions under which the data should be verified. Such methods can include use of commissioning data, performance tracking, engineering analysis, testing, etc.
MOD-024-1
Verification of Generator Gross and Net Real Power Capability Verification of Generator Gross and Net Reactive Power Capability
TFSS
MOD-025-1
TFCO
TFCO R1.4. Periodicity and schedule of model and data verification and reporting. R1.5. Information to be reported: R1.5.1. Verified maximum gross and net Reactive Power capability (both lagging and leading) at Seasonal Real Power generating capabilities as reported in accordance with Reliability Standard MOD-024 Requirement 1.5.1. R1.5.2. Verified Reactive Power limitations, such as generator terminal voltage limitations, shorted rotor turns, etc. R1.5.3. Verified Reactive Power of auxiliary loads. R1.5.4. Method of verification, including date and conditions. MOD-025-1 Verification of Generator Gross and Net Reactive Power Capability R2 The Regional Reliability Organization shall provide its generator gross and net Reactive Power capability verification and reporting procedures, and any changes to those procedures, to the Generator Owners, Generator Operators, Transmission Operators, Planning Authorities, and Transmission Planners affected by the procedure within 30 calendar days of the approval. R3 The Generator Owner shall follow its Regional Reliability Organizations procedures for verifying and reporting its gross and net Reactive Power generating capability per R1. TFCO TFCO TFCO TFCO PER-001-0 Operating Personnel Responsibility and Authority Operating Personnel Training R1 Each Transmission Operator and Balancing Authority shall provide operating personnel A3 Sec. 4.1 with the responsibility and authority to implement real-time actions to ensure the stable and reliable operation of the Bulk Electric System. Each Transmission Operator and Balancing Authority shall be staffed with adequately trained operating personnel. R Reliability Coordinators, control area operators and system operators shall have the responsibility to implement emergency procedures including the curtailment of transactions and/or shedding of firm load. No No TFCO TFCO TFCO TFCO
MOD-025-1
PER-002-0
R1
NPCC Regional All RC, TOP and BA shall have a process in place to verify that all System Operators have successfully Reliability Plan achieved all of the required training objectives and that their training progress is documented. Sec. 10.5.3
No
No
TFCO
PER-002-0
R2
Each Transmission Operator and Balancing Authority shall have a training program for all operating personnel that are in (refer to R2.1 and R2.2 below):
NPCC Regional Each TOP, BA and RC shall staff all operating positions that meet either one or both of the following criteria No Reliability Plan with personnel that are NERC-certified for the applicable functions (see responses below): Sec. 10.2
No
TFCO
PER-002-0
R2.1
Positions that have the primary responsibility, either directly or through communications RRP Sec. 10.2 with others, for the real-time operation of the interconnected Bulk Electric System. Positions directly responsible for complying with NERC standards. RRP Sec. 10.2
Identical to R2.1
No
No
TFCO
PER-002-0
R2.2
Identical to R2.2
No
No
TFCO
Page 52 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
PER-002-0
R3
PER-002-0
R3.1
For personnel identified in Requirement R2, the Transmission Operator and Balancing RRP Sec. 10.5 Authority shall provide a training program meeting the following criteria ( refer to R 3.1, R3.2, etc. below): A set of training program objectives must be defined, based on NERC and Regional RRP Sec. Reliability Organization standards, entity operating procedures, and applicable 10.5.1 regulatory requirements. These objectives shall reference the knowledge and competencies needed to apply those standards, procedures, and requirements to normal, emergency, and restoration conditions for the TOP and BA operating positions. The training program must include a plan for the initial and continuing training of Transmission Operator and Balancing Authority operating personnel. That plan shall address knowledge and competencies required for reliable system operations. The training program must include training time for all Transmission Operator and Balancing Authority operating personnel to ensure their operating proficiency. RRP Sec. 10.5.2
No
TFCO
All RC, TOP and BA shall provide their System Operators with a coordinated training program that is designed to promote the reliable operation of the BES. This program shall include objectives based on the NERC Standards, NPCC Criteria, Guidelines and Procedures and applicable regulatory requirements.
No
No
TFCO
PER-002-0
R3.2
All TOP and BA shall have a plan for initial and continuing training that addresses required knowledge and competencies and their application in System Operations.
No
No
TFCO
PER-002-0
R3.3
All RC, TOP and BA shall provide their System Operators with a coordinated training program that is designed to promote the reliable operation of the BES.
No
NPCC does not specify No that training time will be made AVAILABLE to the Operators No No
TFCO
PER-002-0 PER-002-0
R3.4 R4
Training staff must be identified, and the staff must be competent in both knowledge of system operations and instructional capabilities. For personnel identified in Requirement R2, each Transmission Operator and Balancing Authority shall provide its operating personnel at least five days per year of training and drills using realistic simulations of system emergencies, in addition to other training required to maintain qualified operating personnel.
Identical to R3.4
No
TFCO TFCO
All RC, TOP and BA shall provide their System Operators with a minimum of 5 days per year of training and No drills using realistic simulations of system emergencies, in addition to other training required to maintain qualified operating personnel.
PER-003-0
R1
Each Transmission Operator, Balancing Authority, and Reliability Coordinator shall staff NPCC Regional Each TOP, BA and RC shall staff all operating positions that meet both of the following criteria with all operating positions that meet both of the following criteria with personnel that are Reliability Plan personnel that are NERC certified for the applicable functions (refer to the responses below): NERC certified for the applicable functions (refer to R1.1 and R1.2 below): Sec. 2.4.1
No
No
TFCO
PER-003-0
R1.1
Positions that have the primary responsibility, either directly or through communications RRP Sec. 2.4.1 Identical to R1.1 with others, for the real-time operation of the interconnected Bulk Electric System. (i) Positions directly responsible for complying with NERC standards. RRP Sec. 2.4.1 Identical to R1.2 (ii) Each Reliability Coordinator shall be staffed with adequately trained and NERC-certified NPCC Regional Identical to R1 Reliability Coordinator operators, 24 hours per day, seven days per week. Reliability Plan (Aug. 2005) Sec. 10.1
No
No
TFCO
PER-003-0 PER-004-0
R1.2 R1
No No
No No
TFCO TFCO
PER-004-0
R2
All Reliability Coordinator operating personnel shall each complete a minimum of five days per year of training and drills using realistic simulations of system emergencies, in addition to other training required to maintain qualified operating personnel.
RC operating personnel shall have an extensive understanding of the BA, TOP and Generation Operators No within the RC Area, including operating staff, operating practices and procedures, restoration priorities and objectives, outage plans, equipment capabilities, and operational restrictions (note: 5 days of training already covered in response to PER-002-0, R4) 10.3 - RC operating personnel shall have an extensive understanding of the BA, TOP and GOP within the RC No Area, including the operating staff, operating practices and procedures, restoration priorities and objectives, outage plans, equipment capabilities and operational restrictions. III 2 Monitor the Wide Area and observe IROL. Wide Area monitoring is described as the ability to monitor the complete RC Area, including critical flow and status information from adjacent RC Areas Identical to R4 No
No
TFCO
PER-004-0
R3
Reliability Coordinator operating personnel shall have a comprehensive understanding of RRP Sec. 10.3 the Reliability Coordinator Area and interactions with neighboring Reliability & Coordinator Areas. Reliability Coordinator operating personnel shall have a comprehensive understanding of III 2 the Reliability Coordinator Area and interactions with neighboring Reliability Coordinator Areas. Reliability Coordinator operating personnel shall have an extensive understanding of the RRP Sec. 10.1 Balancing Authorities, Transmission Operators, and Generation Operators within the Reliability Coordinator Area, including the operating staff, operating practices and procedures, restoration priorities and objectives, outage plans, equipment capabilities, and operational restrictions. Reliability Coordinator operating personnel shall place particular attention on SOLs and RRP Sec. 10.3 IROLs and inter-tie facility limits. The Reliability Coordinator shall ensure protocols are in place to allow Reliability Coordinator operating personnel to have the best available information at all times. Each Transmission Operator, Balancing Authority, and Generator Operator shall be familiar with the purpose and limitations of protection system schemes applied in its area. none
No
TFCO
PER-004-0
R3
No
TFCO
PER-004-0
R4
No
No
TFCO
PER-004-0
R5
Identical to R5
No
No
TFCO
PRC-001-0
System ProtectionCoordination
R1
None
No
No
TFSP
Page 53 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
PRC-001-0
R2
Each Generator Operator and Transmission Operator shall notify reliability entities of relay or equipment failures as follows (see R2.1 and R2.2 below):
none
None
No
TFSP
PRC-001-0
R2.1
PRC-001-0
R2.2
If a protective relay or equipment failure reduces system reliability, the Generator none Operator shall notify its TOP and Host BA. The GOP shall take corrective action as soon as possible. If a protective relay or equipment failure reduces system reliability, the Transmission none Operator shall notify its Reliability Coordinator and affected TOP and BA. The Transmission Operator shall take corrective action as soon as possible. A Generator Operator or Transmission Operator shall coordinate new protective systems and changes as follows (see R3.1 and R3.2 below): C22 Sec. 1.0
None
No
No
TFSP
None
No
No
TFSP
PRC-001-0
System ProtectionCoordination
R3
In accordance with the concluding paragraph of the BPS Protection Criteria (A-5)the member system shall No provide the TFSP with advance notification of any of its new BPS protection facilities , or significant changes in its existing BPS protection facilities. The member system shall also provide TFSP with advance notification of non-member protection facilities See R3 above No
No
TFSP
PRC-001-0
System ProtectionCoordination
R3.1
Each Generator Operator shall coordinate all new protective systems and all protective system changes with its Transmission Operator and Host Balancing Authority.
The NPCC criteria does No not specify that the TOP and BA must be notified The NPCC criteria does No not specify that the TOP and BA must be notified NPCC criteria states a report is only required when requested No
TFSP
PRC-001-0
System ProtectionCoordination
R3.2
Each Transmission Operator shall coordinate all new protective systems and all protective system changes with neighboring Transmission Operators and Balancing Authorities. Each Transmission Operator shall coordinate protection systems on major transmission lines and interconnections with neighboring Generator Operators, TOP and Balancing Authorities. A Generator Operator or Transmission Operator shall coordinate changes in generation, transmission, load or operating conditions that could require changes in the protection systems of others (see R5.1 and R5.2 below): Each GOP shall notify its TOP in advance of changes in generation or operating conditions that could require changes in the Transmission Operators protection systems. Each TOP shall notify neighboring TOP in advance of changes in generation, transmission, load, or operating conditions that could require changes in the other TOPs protection systems. Each TOP and BA shall monitor the status of each Special Protection System in their area, and shall notify affected TOP and BA of each change in status.
See R3 above
No
TFSP
PRC-001-0
System ProtectionCoordination
R4
A presentation will be made to the TFSP on new facilities or a modification to an existing facility when requested by either a member system or TFSP.
No
TFSP
PRC-001-0
System ProtectionCoordination
R5
No
No
TFSP
PRC-001-0
R5.1
No
No
TFSP
PRC-001-0
R5.2
No
No
TFSP
PRC-001-0
R6
NPCC Regional the RC shall monitor its parameters that may have significant impacts on its RC Area parameters, Reliability Plan including: - current status of BES including AVRs and SPS schemes Sec. 3.1.3.2
No
NPCC does not No specifically call for TOP and BA to notify each other and the RC NPCC is more stringent No because there is no equivalent NERC Requirement
TFSP
PRC-001-0
System ProtectionCoordination
R7
none
A5 Sec. 2.4
Operating Time - Bulk power system protection shall take corrective action within times determined by studies with due regard to security, dependability and selectivity.
Yes
TFSP
A5 Sec.2.4.2
Adequate time margin should be provided taking into account study inaccuracies, differences in equipment, and protection operating times. In cases where clearing times are deliberately extended,-consideration must be given to the following: - Effect on system stability or reduction of stability margins. - Possibility of causing or increasing damage to equipment and subsequent extended repair and/or outage time - Effect of disturbances on service to customers Equipment and Design Considerations this section deals with the detailed protection considerations involving CTs, VTs, Logic Systems, Microprocessor-based equipment and software, Batteries, Station Service supplies, Circuit Breakers, Telecommunication, Control Cables and Wiring, Environment and Grounding. Specific application Considerations-this section deals with the specific protection requirements of Transmission Lines, Transmission Stations, Breaker Failure, Generating Stations, UFLS, HVdc, Capacitor Banks and SVCs Yes NPCC is more stringent No because there is no equivalent NERC Requirement NPCC is more stringent because there is no equivalent NERC Requirement TFSP
PRC-001-0
System ProtectionCoordination
R8
none
A5 Sec. 3.0
A5 Sec.4.0
Yes
Page 54 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
PRC-002-0
R1
The Regional Reliability Organization shall develop comprehensive requirements for the C25 Sec. 1.0 installation of Disturbance monitoring equipment to ensure data is available to determine system performance and the causes of System Disturbances. The comprehensive requirements shall include all of the following (see R1.1, R1.2, etc. below): Type of data recording capability (e.g., sequence-of-event, Fault recording, dynamic Disturbance recording). C25 Sec. 1.0
This Procedure provides a mechanism to collect power system event data following a power system disturbance for the purpose of analyzing the performance of the system components and dynamic performance of the NPCC bulk power system.
Yes
TFCP TFSP
PRC-002-0
R1.1
This procedure describes the process to collect event data from three time frames: instantaneous, dynamic and No steady state. The data in the first two time frames is recorded by the various types of Disturbance Monitoring Equipment including Dynamic Recording Devices (DRDs), Digital Fault Recorders (DFRs) and Sequence of Events Recorders (SERs). Pre-event data in the steady state time frame can be captured from real time data bases. See below for details No
Yes
TFCP TFSP
PRC-002-0
Define and Document Disturbance Monitoring Equipment Requirements Define and Document Disturbance Monitoring Equipment Requirements
R1.2
Equipment characteristics including but not limited to (see R1.2.1, R1.2.2, etc. below):
A5 & C25
Yes
TFCP TFSP
PRC-002-0
R1.2.1
DRDs record data as RMS values of power system quantities sampled several times per second and collected No for a period of time that ranges from 20 seconds to continuous. The power system dynamic phenomena that are examined using DRD data last for many seconds. When DRD data is requested it will normally be requested from all locations which produced recordings of the event. DFRs record data as instantaneous values of power system quantities collected many times per cycle for a period of time on the order of seconds. This data is used in the analysis of protection system and circuit breaker operation. SERs capture data consisting of a list of times of occurrence of station events. Event and fault recording capability should be provided to the maximum practical extent to permit analysis of No system disturbances and protection system performance. It is recommended that these devices be time synchronized. 5.0 - The format of (real time dynamic recordings) will be provided at the discretion of the data provider. No Areas providing data customarily have the results in a graphic format such as time plots. Other forms may be exchanged upon mutual agreement of the data requestor and the data provider. Raw data may be available, and may be exchanged upon mutual agreement . The preferred format for exchange of raw data is the IEEE PSRC Comtrade format, with an IEEE PSRC recommended filename. 6.0 The preferred method for transferring (steady state conditions from EMS history) system information is No in PTI PSS/E raw data or IEEE common format.
Yes
TFCP TFSP
PRC-002-0
Define and Document Disturbance Monitoring Equipment Requirements Define and Document Disturbance Monitoring Equipment Requirements
R1.2.2
A5 Sec. 2.7.2
Yes
TFCP TFSP
PRC-002-0
R1.2.3
Yes
TFCP TFSP
PRC-002-0
Define and Document Disturbance Monitoring Equipment Requirements Define and Document Disturbance Monitoring Equipment Requirements
R1.2.3
Yes
TFCP TFSP
PRC-002-0
R1.2.4
C5 Sec. 6.0
A data requester may ask that steady state, pre-event, system data be captured for a particular event. This is data normally maintained through EMS data acquisition. These systems provide a convenient means by which to snap a power flow from real time data. All available data that is required to establish a base case power flow model should be provided. This Procedure provides a mechanism to collect power system event data following a power system disturbance for the purpose of analyzing the performance of the system components and dynamic performance of the NPCC BPS. Refer to R1.3 above
No
NPCC does not specify triggering requirements for DRDs and DFRs.
Yes
TFCP TFSP
PRC-002-0
Define and Document Disturbance Monitoring Equipment Requirements Define and Document Disturbance Monitoring Equipment Requirements Define and Document Disturbance Monitoring Equipment Requirements Define and Document Disturbance Monitoring Equipment Requirements Define and Document Disturbance Monitoring Equipment Requirements Define and Document Disturbance Monitoring Equipment Requirements
R1.3
Monitoring, recording, and reporting capabilities of the equipment (see R1.3.1, etc. below):
No
NPCC does not specify which quantities should be recorded. See R1.3 above
Yes
TFCP TFSP
PRC-002-0
R1.3.1
Voltage
No
Yes
TFCP TFSP
PRC-002-0
R1.3.2
Current
No
Yes
TFCP TFSP
PRC-002-0
R1.3.3
Frequency
No
Yes
TFCP TFSP
PRC-002-0
R1.3.4
No
Yes
TFCP TFSP
PRC-002-0
R1.4
Data retention capabilities (e.g., length of time data is to be available for retrieval).
Data collected from an event are retained for a period of not less than 1 year. The data will be supplied as soon as practical and within 30 days.
No
Yes
TFCP TFSP
Page 55 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
PRC-002-0
Define and Document Disturbance Monitoring Equipment Requirements Define and Document Disturbance Monitoring Equipment Requirements Define and Document Disturbance Monitoring Equipment Requirements Define and Document Disturbance Monitoring Equipment Requirements Define and Document Disturbance Monitoring Equipment Requirements Define and Document Disturbance Monitoring Equipment Requirements Define and Document Disturbance Monitoring Equipment Requirements Define and Document Disturbance Monitoring Equipment Requirements Regional Procedure for Transmission Protection System Misoperations
R1.5
Regional coverage requirements (e.g., by voltage, geographic area, electric area or subarea).
This Procedure provides a mechanism to collect power system event data following a power system disturbance for the purpose of analyzing the performance of the system components and dynamic performance of the NPCC bulk power system. Event and fault recording capability shall be provided to the extent required to permit analysis of system disturbances and protection performance.
Yes
TFCP TFSP
PRC-002-0
R1.6
A5 Sec. 2.7.2
No
Yes
TFCP TFSP
PRC-002-0
R1.6.1
Substations.
A5 Sec. 2.7.2
No
Yes
TFCP TFSP
PRC-002-0
R1.6.2
Transmission lines
A5 Sec. 2.7.2
No
TFCP TFSP
PRC-002-0
R1.6.3
Generators
A5 Sec. 2.7.2
No
Yes
TFCP TFSP
PRC-002-0
R1.7
The testing and maintenance of DRDs, DFRs and SERs is to be performed in accordance with the member system testing and maintenance practices.
No
Yes
TFCP TFSP
PRC-002-0
R1.8
Requirements for periodic (at least every five years) updating, review, and approval of the Regional requirements.
none
None
No
Yes
TFCP TFSP
PRC-002-0
R2
The Regional Reliability Organization shall provide its requirements for the installation of Disturbance monitoring equipment to other Regional Reliability Organizations and NERC on request (30 calendar days).
none
None
No
Yes
TFCP TFSP
PRC-003-0
R1
Each Regional Reliability Organization shall establish, document and maintain its B21 Sec. 1.0 procedures for review, analysis, and mitigation of transmission and generation Protection System Misoperations. These procedures shall include the following elements (see R1.1, R1.2, etc. below):
Analysis of bulk power system protection operations shall be undertaken and the required information shall be supplied to the Area according to policies established in each Area.
No
Yes
TFSP
PRC-003-0
R1.1
R1.1. Requirements for monitoring and analysis of all transmission protective device misoperations.
Each NPCC Area is required to keep a record of all misoperations of protection systems and special protection systems on their bulk power systems. Included are misoperations of: - protection systems for transmission lines, buses, transformers, generators, shunt or series compensating devices, and other bulk power system elements, - protection systems for breaker failure - protection systems for the NPCC automatic underfrequency load shedding program, and - special protection systems.
No
Yes
TFSP
PRC-003-0
R1.2
No All protection system and special protection system misoperations shall be analyzed in accordance with Area policies to determine the cause and the corrective action to be taken. The minimum information to be recorded for each misoperation includes: - identification of the BPS elements affected - date and time of the event - cause of event, if known - identification of protection system(s) involved - identification of the protection systems that misoperated - identification of the cause(s) of misoperation, if known identification of the affected hardware/software components of the protection system(s) or special protection system(s) and/or the associated switching devices - the corrective actions taken or planned.
More Specificity
Yes
TFSP
PRC-003-0
Regional Procedure for Transmission Protection System Misoperations Regional Procedure for Transmission Protection System Misoperations
R1.3
Process for review, analysis follow up, and documentation of Corrective Action Plans for B21 Sec. 3.0 Misoperations.
PRC-003-0
R1.4
Identification of the Regional Reliability Organization group responsible for the procedure and the process for Regional Reliability Organization approval of the procedure.
No Each Area shall keep a record of the above information for each misoperation. Analyses should be undertaken and recorded within 60 days of the occurrence of the event in accordance with Area policies. The recorded information shall be maintained such that the Areas can report it to NPCC within thirty days from the date of a request. If any analysis indicates that an addition, clarification, or modification to the NPCC Protection Criteria, No Guides or Procedures should be considered, a report must be furnished to the Task Force on System Protection (TFSP) as soon as possible. In addition, any incident of general interest should be reported to the TFSP at its next scheduled meeting.
More Specificity
Yes
TFSP
Yes
TFSP
Page 56 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
PRC-003-0
A misoperation is considered to be one in which one or more specified protective functions: did not occur No as intended by the protection system design, or did not occur within the time intended by the protection system design, or occurred for an initiating event for which they were not intended by the protection system design to occur, or occurred for no initiating event. None No
Yes
TFSP
PRC-003-0
Regional Procedure for Transmission Protection System Misoperations Regional Procedure for Transmission Protection System Misoperations
R2
Each Regional Reliability Organization shall maintain and periodically update documentation of its procedures for review, analysis, reporting and mitigation of transmission and generation Protection System Misoperations. Each Regional Reliability Organization shall distribute procedure in Requirement 1 and any changes to those procedures, to the affected Transmission Owners, Distribution Providers that own transmission Protection Systems, and Generator Owners within 30 calendar days of approval of those procedures.
none
Yes
TFSP
PRC-003-0
R3
TFSP
PRC-003-1
Regional Procedure for Analysis of Misoperations of Transmission and Generation Protection Systems
R1 Each Regional Reliability Organization shall establish, document and maintain its procedures for, review, analysis, reporting and mitigation of transmission and generation Protection System Misoperations. These procedures shall include the following elements: R1.1. The Protection Systems to be reviewed and analyzed for Misoperations (due to their potential impact on BES reliability). R1.2. Data reporting requirements (periodicity and format) for Misoperations. R1.3. Process for review, analysis follow up, and documentation of Corrective Action Plans for Misoperations. R1.4. Identification of the Regional Reliability Organization group responsible for the procedures and the process for approval of the procedures.
TFSP
PRC-003-1
Regional Procedure for Analysis of Misoperations of Transmission and Generation Protection Systems Regional Procedure for Analysis of Misoperations of Transmission and Generation Protection Systems Analysis and Reporting of Transmission Protection System Misoperations
R2
TFSP
Each Regional Reliability Organization shall maintain and periodically update documentation of its procedures for review, analysis, reporting, and mitigation of transmission and generation Protection System Misoperations. R3 Each Regional Reliability Organization shall distribute procedures in Requirement 1 and any changes to those procedures, to the affected Transmission Owners, Distribution Providers that own transmission Protection Systems, and Generator Owners within 30 calendar days of approval of those procedures. The Transmission Owner and any Distribution Provider that owns a transmission B21 Sec. 3.0 protection system shall each analyze its transmission Protection System Misoperations and shall develop and implement Corrective Action Plan to avoid future Misoperation of a similar nature according to the Regional Reliability Organization's procedures developed for Reliability Standard PRC-003 Requirement 1. TFSP
PRC-003-1
PRC-004-0
R1
All protection system and special protection system misoperations shall be analyzed in accordance with Area policies to determine the cause and the corrective action to be taken.
No
No
TFSP
PRC-004-0
R2
The Generator Owner shall analyze its generator Protection System Misoperations, and shall develop and implement a Corrective Action Plan to avoid future Misoperations of a similar nature according to the Regional Reliability Organization's procedures developed for PRC-003 R1. The Transmission Owner, any Distribution Provider that owns a transmission Protection B21 Sec. 3.0 System and the Generator Owner shall each provide to its Regional Reliability Organization documentation of its Misoperations analyses and Corrective Actions Plan according to the Regional Reliability Organizations procedures PRC-003 R1. No Each Area shall keep a record of the above information for each misoperation. Analyses should be undertaken and recorded within 60 days of the occurrence of the event in accordance with Area policies. The recorded information shall be maintained such that the Areas can report it to NPCC within thirty days from the date of a request. NPCC has no No documentation with mention of the reporting requirements to NERC. TFSP
PRC-004-0
R3
PRC-004-1 Analysis and Mitigation of Transmission and Generation Protection System Misoperations
R1 The Transmission Owner and any Distribution Provider that owns a transmission Protection System shall each analyze its transmission Protection System Misoperations and shall develop and implement a Corrective Action Plan to avoid future Misoperations of a similar nature according to the Regional Reliability Organizations procedures developed for Reliability Standard PRC-003 Requirement 1.
Page 57 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
PRC-004-1 Analysis and Mitigation of Transmission and Generation Protection System Misoperations PRC-004-1 Analysis and Mitigation of Transmission and Generation Protection System Misoperations Transmission Protection System Maintenance and Testing
R2 The Generator Owner shall analyze its generator Protection System Misoperations, and shall develop and implement a Corrective Action Plan to avoid future Misoperations of a similar nature according to the Regional Reliability Organizations procedures developed for PRC-003 R1. R3 The Transmission Owner, any Distribution Provider that owns a transmission Protection System, and the Generator Owner shall each provide to its Regional Reliability Organization, documentation of its Misoperations analyses and Corrective Action Plans according to the Regional Reliability Organizations procedures developed for PRC-003 R1. Each Transmission Owner and any Distribution Provider that owns a transmission A4 Sec. 1.0 Protection System and each Generator Owner that owns a generation Protection System shall have a Protection System maintenance and testing program for Protection Systems that affect the reliability of the BES. The program shall include: (see R1.1, etc. below):
TFSP
TFSP
PRC-005-0
R1
This document establishes the minimum maintenance objectives and recommends maintenance practices for No protection of the NPCC bulk power system, including Type I special protection systems and protection required for the NPCC Automatic Underfrequency Load Shedding Program. Automatic underfrequency load shedding protection systems and generator underfrequency tripping relays are not generally located at bulk power system stations; however, they have a direct effect on the operation of the bulk power system during major emergencies, and as such they are subject to this Criteria. Refer to R1.1.1, etc. below No
No
TFSP
PRC-005-0
Transmission Protection System Maintenance and Testing Transmission Protection System Maintenance and Testing Transmission Protection System Maintenance and Testing Transmission Protection System Maintenance and Testing Transmission Protection System Maintenance and Testing Transmission Protection System Maintenance and Testing Transmission Protection System Maintenance and Testing
R1.1
Transmission protection system identification shall include but are not limited to (see R1.1.1, R1.1.2, etc. below):
A4 Sec. 2.0
No
TFSP
PRC-005-0
R1.1.1
Relays
A4 Sec. 2.0
Minimum periodic maintenance of each protection group includes: - making visual inspections - verifying inputs and outputs - confirming that the intended version of software is installed (microprocessor-based relays)-verifying operating characteristics - verifying the integrity of current and voltage transformers and associated circuitry
No
No
TFSP
PRC-005-0
R1.1.2
Instrument transformers
A4 Sec. 2.0
No
No
TFSP
PRC-005-0
R1.1.3
A4 Sec. 2.0
No
No
TFSP
PRC-005-0
R1.1.4
Batteries
A4 Sec. 3.0
On batteries and chargers, verify proper operation and general condition every month.
No
No
TFSP
PRC-005-0
R1.2
A4 Sec. 2.0
All of the above shall be performed on a maintenance interval not exceeding that specified in Table 1 for bulk No power system protection groups.
NPCC does not show the No basis for the testing intervals in Table 1 No
TFSP
PRC-005-0
R1.3
A4 Sec. 2.0
Minimum periodic maintenance of each protection group shall consist of verifying that the protection group is No capable of performing its intended protection function. This includes: making visual inspections, verifying inputs and outputs, confirming that the intended version of software is installed verifying operating characteristics, verifying the integrity of CTs VTs and associated circuitry, verifying the proper performance of communications systems, etc.
TFSP
PRC-005-0
Transmission Protection System Maintenance and Testing Transmission Protection System Maintenance and Testing Transmission Protection System Maintenance and Testing Transmission Protection System Maintenance and Testing
R1.4
none
None
No
No
TFSP
PRC-005-0
R1.5
none
None
No
No
TFSP
PRC-005-0
R1.6
none
None
No
No
TFSP
PRC-005-0
R2
Each Transmission Owner and any Distribution Provider that owns a transmission Protection System and each Generator Owner that owns a generation Protection System shall provide documentation of its Protection System maintenance and testing program and the implementation of that program to its Regional Reliability Organization on request (within 30 calendar days). The documentation of the program shall include:
A8 Appendix A4.1
Specifies that Protection system owners shall implement a protection system maintenance and testing program that fulfills the requirements of the NPCC Maintenance Criteria for Bulk Power System Protection (Document A-4). It also requires that they report annually to NPCC, no later than 6 months after the end of the reporting period. At present, a reporting period is equal to the prior calendar year.
No
No
TFSP
Page 58 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
R2.1 Evidence Protection System devices were maintained and tested within the defined intervals. R2.2 Date each Protection System device was last tested/maintained. PRC-005-0 Transmission Protection System Maintenance and Testing R3 none B23 Guide for Maintenance of Microprocessor Based Protection Relays: - The use of computer based technology Yes for protective relays has influenced what is considered sufficient for periodic maintenance of microprocessorbased relays. The purpose of this document is to provide guidance for the maintenance of microprocessorbased protective relays as required in Section 2 of NPCC Maintenance Criteria for Bulk Power System Protection, Document A-4 on verifying operating characteristics NPCC is more stringent No by providing a guide to establish testing criteria for this new technology introduced into the protective relaying field TFSP
PRC-005-1
R1 Each Transmission Owner and any Distribution Provider that owns a transmission Protection System and each Generator Owner that owns a generation Protection System shall have a Protection System maintenance and testing program for Protection Systems that affect the reliability of the BES. The program shall include: R1.1. Maintenance and testing intervals and their basis. R1.2. Summary of maintenance and testing procedures.
TFSP
PRC-005-1
R2 Each Transmission Owner and any Distribution Provider that owns a transmission Protection System and each Generator Owner that owns a generation Protection System shall provide documentation of its Protection System maintenance and testing program and the implementation of that program to its Regional Reliability Organization on request (within 30 calendar days). The documentation of the program implementation shall include: R2.1. Evidence Protection System devices were maintained and tested within the defined intervals.
TFSP TFSP B7 Sec. 1.0 The NPCC Emergency Operation Criteria (Document A-3) sets forth the requirements for automatic underfrequency load shedding and automatic underfrequency load shedding associated with generator underfrequency tripping. This guide presents relay application and testing requirements necessary to accomplish the objectives of Document A-3. No Yes TFSS
PRC-006-0
R1
R2.2. Date each Protection System device was last tested/maintained. Each Regional Reliability Organization shall develop, coordinate, and document an UFLS program, which shall include the following (see R1.1, etc. below):
PRC-006-0
Development and Documentation of RRO Underfrequency Loadshedding Programs Development and Documentation of RRO Underfrequency Loadshedding Programs Development and Documentation of RRO Underfrequency Loadshedding Programs Development and Documentation of RRO Underfrequency Loadshedding Programs Development and Documentation of RRO Underfrequency Loadshedding Programs Development and Documentation of RRO Underfrequency Loadshedding Programs
R1.1
Requirements for coordination of UFLS programs within the subregions, Regional Reliability Organization and, where appropriate, among Regional Reliability Organizations.
A3 Sec. 4.6
The Automatic Underfrequency Load Shedding Program must be coordinated among the NPCC Areas. Each No Area is required to carry out the following unless an alternative plan is submitted by an Area for review by the NPCC Task Forces on Coordination of Operation and System Studies and approved by the NPCC Reliability Coordinating Committee: See below for details No
Yes
TFSS
PRC-006-0
R1.2
Design details shall include, but are not limited to (see R1.2.1, R1.2.2, etc. below):
A3 Sec. 4.6
Yes
TFSS
PRC-006-0
R1.2.1
A3 Sec. 4.6.1
4.6.1 - Automatic load shedding of 10% of its load at a nominal set point of 59.3 Hz.
No
Yes
TFSS
PRC-006-0
R1.2.1
A3 Sec. 4.6.2
4.6.2 - Automatic load shedding of an additional 15% of its load at a nominal set point of 58.8 Hertz.
No
Yes
TFSS
PRC-006-0
R1.2.2
No
Yes
TFSS
PRC-006-0
R1.2.3
A3 Sec. 4.6.3
Underfrequency threshold relays shall be set to a nominal operating time of 0.30 second, from the time when No frequency passes through the set point to the time of circuit breaker trip initiation (including any communications time delay), when the rate of frequency decay is 0.2 Hertz per second.
Yes
TFSS
Page 59 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
PRC-006-0
R1.2.4
Generation protection.
A3 Sec. 4.9
Generators should not be tripped for under-frequency conditions in the area above the curve in Figure 1. It is recognized that, in special cases, requirements may dictate generator trip in the region above the curve. In those cases, automatic load shedding additional to the amount set out in Section 4.6, equivalent to the amount of generation to be tripped, must be provided. Such cases shall be reviewed by the Task Force on Coordination of Operation. None No
Yes
TFSS
PRC-006-0
Development and Documentation of RRO Underfrequency Loadshedding Programs Development and Documentation of RRO Underfrequency Loadshedding Programs Development and Documentation of RRO Underfrequency Loadshedding Programs Development and Documentation of RRO Underfrequency Loadshedding Programs Development and Documentation of RRO Underfrequency Loadshedding Programs Development and Documentation of RRO Underfrequency Loadshedding Programs Development and Documentation of RRO Underfrequency Loadshedding Programs Development and Documentation of RRO Underfrequency Loadshedding Programs Development and Documentation of RRO Underfrequency Loadshedding Programs Development and Documentation of RRO Underfrequency Loadshedding Programs Development and Documentation of RRO Underfrequency Loadshedding Programs Development and Documentation of RRO Underfrequency Loadshedding Programs
R1.2.5
none
Yes
TFSS
PRC-006-0
R1.2.6
Islanding schemes
none
None
No
Yes
TFSS
PRC-006-0
R1.2.7
none
None
No
Yes
TFSS
PRC-006-0
R1.2.8
Any other schemes that are part of or impact the UFLS programs.
none
None
No
Yes
TFSS
PRC-006-0
R1.3
A Regional Reliability Organization UFLS program database. This database shall be A2 Sec. 2.0 updated as specified in the Regional Reliability Organization program (but at least every five years) and shall include sufficient information to model the UFLS program in dynamic simulations of the interconnected transmission systems. A Regional Reliability Organization UFLS program database. This database shall be B7 Sec. 4.0 updated as specified in the Regional Reliability Organization program (but at least every five years) and shall include sufficient information to model the UFLS program in dynamic simulations of the interconnected transmission systems. Assessment and documentation of the effectiveness of the design and implementation of A3 Sec. 4.6 the Regional UFLS program. This assessment shall be conducted periodically and shall (at least every five years or as required by changes in system conditions) include, but not be limited to (see R1.4.1, etc. below): Assessment and documentation of the effectiveness of the design and implementation of NRAP the Regional UFLS program. This assessment shall be conducted periodically and shall (at least every five years or as required by changes in system conditions) include, but not be limited to (see R1.4.1, etc. below): A review of the frequency set points and timing,
2.0 Data needed to analyze and model the electric system and its component facilities must be developed, maintained and made available for use in interconnected operating and planning studies, including data for fault level analysis.
No
Yes
TFSS
PRC-006-0
R1.3
4.0 - The NPCC Reliability Compliance and Enforcement Program (Document A-8) requires periodic review by each NPCC Area of their automatic underfrequency load shedding capability and generator underfrequency tripping. This review shall be documented in a manner and form designated by the Compliance Monitoring and Assessment Subcommittee. 4. 6 - Studies shall be performed by each Area to ensure satisfactory voltage and loading conditions after automatic load shedding.
No
Yes
TFSS
PRC-006-0
R1.4
No
Yes
TFSS
PRC-006-0
R1.4
NPCC Reliability Assessment Program (NRAP) requires a review of UFLS every 3 years.
No
Yes
TFSS
PRC-006-0
R1.4.1
No
Yes
TFSS
PRC-006-0
R1.4.2
Dynamic simulation of possible Disturbance that cause the Region or portions of the Region to experience the largest imbalance between Demand (Load) and generation.
No
Yes
TFSS
PRC-006-0
R2
The RRO shall provide documentation of its UFLS program and its database information none to NERC on request (within 30 calendar days).
None
No
Yes
TFSS
PRC-006-0
R3
The Regional Reliability Organization shall provide documentation of the assessment of none its UFLS program to NERC on request (within 30 calendar days).
None
No
Yes
TFSS
Page 60 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
PRC-007-0
Assuring Consistency of Entity Underfrequency Load Shedding Programs with RRO Underfrequency Load Shedding Program Requirements
R1
The Transmission Owner and Distribution Provider, with a UFLS program (as required A3 Sec. 4.6 by its Regional Reliability Organization) shall ensure that its UFLS program is consistent with its Regional Reliability Organizations UFLS program requirements.
The intent of the Automatic Underfrequency Load Shedding program is to stabilize the system frequency in No an Area during an event leading to declining frequency while recognizing the generation characteristics in each Area. The goal of the program is to arrest the system frequency decline and to return the frequency to at least 58.5 Hertz in ten seconds or less and to at least 59.5 Hertz in thirty seconds or less, for a generation deficiency of up to 25% of the load. The UFLS program must be coordinated among the NPCC Areas. Each Area is required to carry out the following unless an alternative plan is submitted by an Area for review by the NPCC Task Forces on Coordination of Operation and System Studies and approved by the NPCC Reliability Coordinating Committee: (etc.) The NPCC Reliability Compliance and Enforcement Program requires periodic review by each NPCC Area No of their automatic UFLS capability and generator underfrequency tripping. This review shall be documented in a manner and form designated by the Compliance Monitoring and Assessment Subcommittee.
No
TFSS
PRC-007-0
Assuring Consistency of Entity Underfrequency Load Shedding Programs with RRO Underfrequency Load Shedding Program Requirements
R2
The Transmission Owner, TOP, Distribution Provider, and LSE that owns or operates a UFLS program (as required by its RRO) shall provide, and annually update, its underfrequency data as necessary for its RRO to maintain and update a UFLS program database.
B7 Sec. 4.0
No
TFSS
PRC-007-0
Assuring Consistency of Entity Underfrequency Load Shedding Programs with RRO Underfrequency Load Shedding Program Requirements
R3
The Transmission Owner and Distribution Provider that owns a UFLS program (as A8 Template required by its Regional Reliability Organization) shall provide its documentation of that A3-1 UFLS program to its Regional Reliability Organization on request (30 calendar days).
Requires that each NPCC Area shall plan and implement an UFLS program as specified in section 4.6 of the Yes NPCC Emergency Operation Criteria (Document A3) Each Area must report annually as to whether it is in 100% compliance with the requirements of A3.
NPCC is less stringent because provision of documentation within a 30-day period is not specified.
No
TFSS
PRC-008-0
R1
The Transmission Owner and Distribution Provider with a UFLS program (as required A4 Sec. 4.0 by its Regional Reliability Organization) shall have a UFLS equipment maintenance and testing program in place. This UFLS equipment maintenance and testing program shall include UFLS equipment identification, the schedule for UFLS equipment testing, and the schedule for UFLS equipment maintenance.
Trip testing for protection required by the NPCC Automatic Underfrequency Load Shedding Program need No not be performed more frequently than the trip test for other protection on the same breaker. Because of the distributed nature of this load shedding protection, random failures to trip do not compromise the objectives of the NPCC Automatic Underfrequency Load Shedding Program.
NPCC believes the No distributed nature of UFLS equipment makes it unnecessary to test the relays on a rigid schedule, so long as each relay is tested at the same time as its associated breaker/protection stricken by CP9 on February 27, 2006 NPCC has no mention of No a 30-day reporting limit to either NPCC or NERC No
TFSS
PRC-008-0
Implementation and Documentation of Underfrequency Load Shedding Equipment Maintenance Program Analysis and Documentation of Underfrequency Load Shedding Performance Following an Underfrequency Event
R2
The Transmission Owner and Distribution Provider with a UFLS program (as required B7 Sec. 4.0 by its Regional Reliability Organization) shall implement its UFLS equipment maintenance and testing program and shall provide UFLS maintenance and testing program results to its Regional Reliability Organization and NERC on request (within 30 calendar days). The Transmission Owner, TOP, LSE and Distribution Provider that owns or operates a B13 Sec. 2.0 UFLS program (as required by its RRO) shall analyze and document its UFLS program performance in accordance with its RROs UFLS program. The analysis shall address the performance of UFLS equipment and program effectiveness following system events resulting in system frequency excursions below the initializing set points of the UFLS program. The analysis shall include, but not be limited to (see R1.1, etc. below):
The NPCC Reliability Compliance and Enforcement Program requires periodic review by each NPCC Area No of their automatic UFLS capability and generator underfrequency tripping. This review shall be documented in a manner and form designated by the Compliance Monitoring and Assessment Subcommittee.
TFSS
PRC-009-0
R1
An NPCC AREA Disturbance Requiring Review is defined and quantified by either or all of the following: - No Any deliberate action taken within an Area to reduce electricity demands to maintain reliability of bulk power supply by firm load shedding, and/or - any deliberate action taken within an Area to reduce voltage and/or Any bulk supply incident where equipment and customer outages occur wholly within an Area, and where the customer outages exceed 300 MW for 15 minutes or longer.
TFSS
PRC-009-0
Analysis and Documentation of Underfrequency Load Shedding Performance Following an Underfrequency Event Analysis and Documentation of Underfrequency Load Shedding Performance Following an Underfrequency Event Analysis and Documentation of Underfrequency Load Shedding Performance Following an Underfrequency Event
R1.1
Forward within one working day, a completed copy of the attached NPCC Disturbance Reporting Form or a similar summary to the NPCC office and to TFCO members and liaisons in other Areas, and, if deemed necessary by the TFCO Chair, prepare and forward to NPCC staff, to TFCO members and liaisons in other Areas, within 1 month, a written report containing the chronology of events, any. and recs.for Impl.and/or further study. None
No
No
TFSS
PRC-009-0
R1.2
none
No
No
TFSS
PRC-009-0
R1.3
none
None
No
No
TFSS
Page 61 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
PRC-009-0
Analysis and Documentation of Underfrequency Load Shedding Performance Following an Underfrequency Event Analysis and Documentation of Underfrequency Load Shedding Performance Following an Underfrequency Event Assessment of the Design and Effectiveness of Undervoltage Load Shedding Program
R1.4
If deemed necessary by the TFCO Chairman, (the Area must) prepare and forward to NPCC staff, to TFCO members and liaisons in other Areas, within 1 month, a written report containing the chronology of events, analysis and recommendations for implementation and/or further study.
A summary of the No findings need only be sent out if deemed necessary by the TFCO Chairman No
TFSS
PRC-009-0
R2
The Transmission Owner, Transmission Operator, Load-Serving Entity, and Distribution none Provider that owns or operates a UFLS program (as required by its Regional Reliability Organization) shall provide documentation of the analysis of the UFLS program to its Regional Reliability Organization and NERC on request 90 calendar days after the system event. The Load-Serving Entity, Transmission Owner, Transmission Operator, and Distribution B4 Sec. 4.0 Provider that owns or operates a UVLS program shall periodically (at least every five years or as required by changes in system conditions) conduct and document an assessment of the effectiveness of the UVLS program. This assessment shall be conducted with the associated Transmission Planner(s) and Planning Authority(ies).
None
No
TFSS
PRC-010-0
R1
A Comprehensive Review is a through assessment of the Areas entire Bulk Power Transmission System, and No includes sufficient analyses to fully address all aspects of an Area review as described in Section 5.0. A Comprehensive Review is required of each Area every five years. TFSS may require an Area to present a Comprehensive Review in less than five years if changes in the Areas planned facilities or forecasted system conditions (system changes) warrant it.
NPCC does not No specifically state that a review of the UVLS program is a requirement of the Comprehensive Review. No
TFSS
PRC-010-0
Assessment of the Design and Effectiveness of Undervoltage Load Shedding Program Assessment of the Design and Effectiveness of Undervoltage Load Shedding Program Assessment of the Design and Effectiveness of Undervoltage Load Shedding Program Assessment of the Design and Effectiveness of Undervoltage Load Shedding Program Assessment of the Design and Effectiveness of Undervoltage Load Shedding Program Undervoltage Load Shedding System Maintenance and Testing
R1.1
This assessment shall include, but is not limited to (see R1.1.1, R1.1.2, etc. below):
No
TFSS
PRC-010-0
R1.1.1
Coordination of the UVLS programs with other protection and control systems in the Region and with other Regional Reliability Organizations, as appropriate.
A3 Sec. 4.7
An Area may employ automatic under-voltage load shedding of selected loads to enhance power system security.
No
No
TFSS
PRC-010-0
R1.1.2
Simulations that demonstrate that the UVLS programs performance is consistent with Reliability Standards TPL-001-0, TPL-002-0, TPL-003-0 and TPL-004-0.
none
None
No
No
TFSS
PRC-010-0
R1.1.3
none
None
Yes
No
TFSS
PRC-010-0
R2
The Load-Serving Entity, Transmission Owner, Transmission Operator, and Distribution none Provider that owns or operates a UVLS program shall provide documentation of its current UVLS program assessment to its Regional Reliability Organization and NERC on request (30 calendar days). The Transmission Owner and Distribution Provider that owns a UVLS system shall have A4 Sec. 1.0 a UVLS equipment maintenance and testing program in place. This program shall include (see R1.1, etc. below):
None
Yes
No
TFSS
PRC-011-0
R1
This document establishes the minimum maintenance objectives and recommends maintenance practices for No protection of the NPCC bulk power system, including Type I special protection systems and protection required for the NPCC Automatic Underfrequency Load Shedding Program. Automatic underfrequency load shedding protection systems and generator underfrequency tripping relays are not generally located at bulk power system stations; however, they have a direct effect on the operation of the bulk power system during major emergencies, and as such they are subject to this Criteria.
NPCC does not No specifically mention UVLS, but it would be considered one of the BPS protection systems, depending on its particular application. No
TFSP
PRC-011-0
Undervoltage Load Shedding System Maintenance and Testing Undervoltage Load Shedding System Maintenance and Testing Undervoltage Load Shedding System Maintenance and Testing Undervoltage Load Shedding System Maintenance and Testing
R1.1
The UVLS system identification which shall include but is not limited to (see R1.1.1, R1.1.2, etc. below):
A4 Sec. 2.0
No
TFSP
PRC-011-0
R1.1.1
Relays
A4 Sec. 2.0
Minimum periodic maintenance of each protection group includes: - making visual inspections - verifying inputs and outputs - confirming that the intended version of software is installed (microprocessor-based relays) -verifying operating characteristics - verifying the integrity of current and voltage transformers and associated circuitry
No
No
TFSP
PRC-011-0
R1.1.2
Instrument transformers
A4 Sec. 2.0
No
No
TFSP
PRC-011-0
R1.1.3
A4 Sec. 2.0
No
No
TFSP
Page 62 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
PRC-011-0
Undervoltage Load Shedding System Maintenance and Testing Undervoltage Load Shedding System Maintenance and Testing
R1.1.4
Batteries
A4 Sec. 3.0
On batteries and chargers, verify proper operation and general condition every month.
No
TFSP
PRC-011-0
R1.2
A4 Sec. 2.0
All of the above shall be performed on a maintenance interval not exceeding that specified in Table 1 for bulk power system protection groups. (Note: UVLS would fall in the All Other Protection Groups category)
No
NPCC doesnt specify the basis for the testing intervals in Table 1 is not provided
No
TFSP
PRC-011-0
R1.3
A4 Sec. 2.0
No Minimum periodic maintenance of each protection group shall consist of verifying that the protection group is capable of performing its intended protection function. This includes: making visual inspections, verifying inputs and outputs, confirming that the intended version of software is installed verifying operating characteristics, verifying the integrity of CTs VTs and associated circuitry, verifying the proper performance of communications systems, etc.
No
TFSP
PRC-011-0
Undervoltage Load Shedding System Maintenance and Testing Undervoltage Load Shedding System Maintenance and Testing Undervoltage Load Shedding System Maintenance and Testing Undervoltage Load Shedding System Maintenance and Testing
R1.4
none
None
No
No
TFSP
PRC-011-0
R1.5
none
None
No
No
TFSP
PRC-011-0
R1.6
none
None
No
No
TFSP
PRC-011-0
R2
The Transmission Owner, Generator Owner, and Distribution Provider that owns a A8 Appendix transmission protection system shall provide documentation of its transmission A4.1 protection system program and its implementation to the appropriate Regional Reliability Organization and NERC on request (within 30 calendar days).
Specifies that Protection system owners shall implement a protection system maintenance and testing program that fulfills the requirements of the NPCC Maintenance Criteria for Bulk Power System Protection (Document A-4). It also requires that they report annually to NPCC, no later than 6 months after the end of the reporting period. At present, a reporting period is equal to the prior calendar year.
No
No
TFSP
PRC-012-0
R1
Each Regional Reliability Organization with a Transmission Owner, Generator Owner, A11 Sec. 1.0.1, 1.0.1 - This document establishes the protection criteria, and recommends minimum design objectives and No or Distribution Providers that uses or is planning to use an SPS shall have a documented 1.0.2 & 1.0.3 practices, for Special Protection Systems. It is not intended to be a design specification. It is a statement of Regional Reliability Organization SPS review procedure to ensure that SPSs comply the objectives to be observed when developing design specifications for Special Protection Systems. with Regional criteria and NERC Reliability Standards. The Regional SPS review procedure shall include (see R1.1, etc. below): Each Regional Reliability Organization with a Transmission Owner, Generator Owner, A11 Sec. 1.0.2 or Distribution Providers that uses or is planning to use an SPS shall have a documented Regional Reliability Organization SPS review procedure to ensure that SPSs comply with Regional criteria and NERC Reliability Standards. The Regional SPS review procedure shall include (see R1.1, etc. below): Each Regional Reliability Organization with a Transmission Owner, Generator Owner, A11 Sec. 1.0.3 or Distribution Providers that uses or is planning to use an SPS shall have a documented Regional Reliability Organization SPS review procedure to ensure that SPSs comply with Regional criteria and NERC Reliability Standards. The Regional SPS review procedure shall include (see R1.1, etc. below): Description of the process for submitting a proposed SPS for Regional Reliability Organization review. A11 Sec. 5.0 1.0.2 - These criteria apply to all new Special Protection Systems (SPSs). It is recognized that SPSs existed No prior to the establishment of these criteria and the predecessor Guideline. It is the responsibility of individual member systems to assess their existing SPSs and to ensure that modifications are made such that, in their judgment, the intent of these criteria are met. Similar judgment shall be used with respect to an SPS existing at the time of revision to these criteria. 1.0.3 - Close coordination must be maintained among system planning, design, operating, maintenance and No protection functions, since both initially and throughout their life cycle, SPSs are a multi-discipline concern.
Yes
TFCP
PRC-012-0
R1
Yes
TFCP
PRC-012-0
R1
Yes
TFCP
PRC-012-0
R1.1
Each new or modified Special Protection System must be reported to NPCC in accordance with the Procedure for NPCC Review of New or Modified Special Protection Systems (SPS) (Document C-16). In addition, each new or modified Type I or Type II Special Protection System must be reported to the Task Force on System Protection in accordance with the Procedure for Reporting and Reviewing Proposed Protection Systems for the Bulk Power System (Document C-22). 2.3 Data needed to analyze and model the electric system and its component facilities must be developed, maintained and made available for use in interconnected operating and planning studies.
No
Yes
TFCP
PRC-012-0
Special Protection System Review Procedure Special Protection System Review Procedure
R1.2
Requirements to provide data that describes design, operation, and modeling of an SPS.
A2 Sec. 2.3
No
Yes
TFCP
PRC-012-0
R1.2
Requirements to provide data that describes design, operation, and modeling of an SPS.
B4 Sec. 2.0
No 2.0 - The purpose of the presentation associated with an Area Transmission Review is to demonstrate that the Areas planned transmission system, based on its projection of available resources, is in conformance with the NPCC Basic Criteria . By such a presentation, the Task Force will satisfy itself that the criteria have been met and, in general, that the reliability of the NPCC Interconnected Systems will be maintained. Analysis of this material should include a review of SPS
Yes
TFCP
Page 63 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
PRC-012-0
R1.3
Requirements to demonstrate that the SPS shall be designed so that a single SPS A5 Sec. 2.1.1 component failure, when the SPS was intended to operate, does not prevent the interconnected transmission system from meeting the performance requirements defined in Reliability Standards TPL-001-0, TPL-002-0, and TPL-003-0. Requirements to demonstrate that the SPS shall be designed so that a single SPS C16 Sec. 3.a component failure, when the SPS was intended to operate, does not prevent the interconnected transmission system from meeting the performance requirements defined in Reliability Standards TPL-001-0, TPL-002-0, and TPL-003-0. Requirements to demonstrate that the inadvertent operation of an SPS shall meet the same performance requirement (TPL-001-0, TPL-002-0, and TPL-003-0) as that required of the contingency for which it was designed, and not exceed TPL-003-0. C16 Sec. 3.b
2.1.1 - Except as noted in Sections 2.1.4, 2.1.5, 4.5.2, 4.7, and 4.8.1 all elements of the bulk power system No must be protected by two protection groups, each of which is independently capable of performing the specified protective function for that element. This requirement also applies during energization of the element. 3.a TFSP will confirm the failure modes of the SPS, and whether or not the SPS complies with the NPCC system protection standards. No
Yes
TFCP
PRC-012-0
R1.3
Yes
TFCP
PRC-012-0
R1.4
TFSS will review the analysis that the proposing entity has performed. The purpose of the review will be to No assess the SPS is in conformance with the Basic Criteria for Design and Operation of Interconnected Power Systems (A2) and to determine the inter-Area or inter-Regional consequences of either a failure of the SPS to operate when and how it is required or an inadvertent or unintended operation of the SPS. If necessary, TFSS will request that the proposing entity conduct additional studies. An SPS should be designed to operate only for conditions which require its specific protective or control actions. A misoperation is considered to be one in which one or more specified protective functions: did not occur as intended by the protection system design, or did not occur within the time intended by the protection system design, or occurred for an initiating event for which they were not intended by the protection system design to occur, or occurred for no initiating event. No
Yes
TFCP
PRC-012-0
Special Protection System Review Procedure Special Protection System Review Procedure
R1.5
Requirements to demonstrate the proposed SPS will coordinate with other protection and A11 Sec. 2.2.2 control systems and applicable Regional Reliability Organization Emergency procedures. RRO definition of misoperation B21 Sec. 2.0
Yes
TFCP
PRC-012-0
R1.6
No
Yes
TFCP
PRC-012-0
R1.7
Requirements for analysis and documentation of corrective action plans for all SPS misoperations.
No All protection system and special protection system misoperations shall be analyzed in accordance with Area policies to determine the cause and the corrective action to be taken. The minimum information to be recorded for each misoperation includes (others as well as ): - identification of the affected hardware/software components of the protection system(s) or SPS(s) and/or the associated switching devices 1.0 -Allowing for sufficient lead time to ensure an orderly review, the entity will notify the Chairman of the No Task Force on Coordination of Planning (TFCP) of its proposal to install a new SPS or modify and existing SPS. The entity will send copies of the complete notification to the TFCO and the TFSP. This notification will include statements that describe possible failure modes and whether misoperation, unintended operation or failure of the SPS would have local, inter-Area or inter-Regional consequences, when the SPS is planned for service, how long it is expected to remain in-service, the specific contingencies(s) for which it is designed to operate and whether the SPS will be designed according to the NPCC BPS Protection Criteria and the SPS Criteria . 3.d TFCP will prepare an overall summary for the Reliability Coordinating Council. This summary will include the findings of the other Task Forces and whether there are any objections to the modification or installation of a new SPS 3.e The RCC will review the summary report and act on the proposal No
Yes
TFCP
PRC-012-0
R1.8
Identification of the Regional Reliability Organization group responsible for the Regional C16 Sec. 1.0 Reliability Organizations review procedure and the process for Regional Reliability Organization approval of the procedure.
Yes
TFCP
PRC-012-0
Special Protection System Review Procedure Special Protection System Review Procedure Special Protection System Review Procedure
R1.8
PRC-012-0
R1.8
PRC-012-0
R1.9
Identification of the Regional Reliability Organization group responsible for the Regional C16 Sec. 3.d Reliability Organizations review procedure and the process for Regional Reliability Organization approval of the procedure. Identification of the Regional Reliability Organization group responsible for the Regional C16 Sec. 3e Reliability Organizations review procedure and the process for Regional Reliability Organization approval of the procedure. Determination, as appropriate, of maintenance and testing requirements. A4 Sec. 1.0
Yes
TFCP
No
Yes
TFCP
This document establishes the minimum maintenance objectives and recommends maintenance practices for No protection of the NPCC bulk power system, including Type I special protection systems and protection required for the NPCC Automatic Underfrequency Load Shedding Program. Automatic underfrequency load shedding protection systems and generator underfrequen-cy tripping relays are not generally located at bulk power system stations; however, they have a direct effect on the operation of the bulk power system during major emergencies, and as such they are subject to this Criteria. Each new or modified SPS must be reported to NPCC in accordance with the Procedure for NPCC Review of New or Modified Special Protection Systems (SPS) (C-16). In addition, each new or modified Type I or Type II Special Protection System must be reported to the TFSP in accordance with the Procedure for Reporting and Reviewing Proposed Protection Systems for the BPS (C-22). No
Yes
TFCP
PRC-012-0
R2
The Regional Reliability Organization shall provide affected Regional Reliability Organizations and NERC with documentation of its SPS review procedure on request (within 30 calendar days).
NPCC criteria has no Yes language related to SPS reporting to other entities
TFCP
PRC-012-0
R3
none
Equipment and Design Considerations this section deals with the detailed special protection system Yes considerations involving CTs, VTs, Logic Systems, Microprocessor-based equipment and software, Batteries, Station Service supplies, Circuit Breakers, Telecommunication, Control Cables and Wiring, Environment and Grounding. Specific Application Considerations this section deals with the specific special protection system requirements of dealing with Breaker Failure events. Yes
NPCC is more stringent Yes because there is no equivalent NERC Requirement NPCC is more stringent Yes because there is no equivalent NERC Requirement
TFCP
PRC-012-0
R4
none
TFCP
Page 64 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
PRC-013-0
R1
The Regional Reliability Organization that has a Transmission Owner, Generator Owner, C19 Sec. 3f & or Distribution Provider with an SPS installed shall maintain an SPS database. The 3g database shall include the following types of information (see R1.1, etc. below):
3f The TFCP will notify the RCC, all the Task Forces, the CMAS, the proposing entity and other member systems of the outcome of the review. Upon NPCC approval of the type and compliance with Criteria, the SPS may be deployed.
Yes
TFCP
PRC-013-0
R1
The Regional Reliability Organization that has a Transmission Owner, Generator Owner, C19 Sec. 3g or Distribution Provider with an SPS installed shall maintain an SPS database. The database shall include the following types of information (see R1.1, etc. below): Design Objectives - Contingencies and system conditions for which the SPS was designed, NPCC List of Special Protection Systems NPCC List of Special Protection Systems NPCC List of Special Protection Systems none
No
Yes
TFCP
PRC-013-0
R1.1
This list is maintained by the Task Force on System Studies and is forwarded to the TFCP following annual No updates. It contains information on the Type of SPS, its Name and NPCC number, the Area in which it is located, what the initiating contingency is, what actions are taken and what percentage of time it is Armed. See R1.1 above No
Yes
TFCP
PRC-013-0
R1.2
Yes
TFCP
PRC-013-0
R1.3
Modeling - Information on detection logic or relay settings that control operation of the SPS.
No
Yes
TFCP
PRC-013-0
R2
The RRO shall provide to affected RRO(s) and NERC documentation of its database or the information therein on request (within 30 calendar days). The Regional Reliability Organization shall assess the operation, coordination, and effectiveness of all SPSs installed in its Region at least once every five years for compliance with NERC Reliability Standards and Regional criteria.
None
Yes
Yes
TFCP
PRC-014-0
R1
B4 Sec. 2.0
No 2.0 - The purpose of the presentation associated with an Area Transmission Review is to demonstrate that the Areas planned transmission system, based on its projection of available resources, is in conformance with the NPCC Basic Criteria . By such a presentation, the Task Force will satisfy itself that the criteria have been met and, in general, that the reliability of the NPCC Interconnected Systems will be maintained. Analysis of this material should include a review of Special Protection Systems, as well as an assessment of the potential for widespread cascading due to overloads, instability or voltage collapse.
Yes
TFSS
PRC-014-0
R1
The Regional Reliability Organization shall assess the operation, coordination, and effectiveness of all SPSs installed in its Region at least once every five years for compliance with NERC Reliability Standards and Regional criteria. The Regional Reliability Organization shall provide either a summary report or a detailed report of its assessment of the operation, coordination, and effectiveness of all SPSs installed in its Region to affected Regional Reliability Organizations or NERC on request (within 30 calendar days).
B4 Sec. 4.0
4.0 A Comprehensive Review is required of each Area at least every five years.
No
Yes
TFSS
PRC-014-0
R2
B4 Sec. 7.4
Upon completion of an Area Review, TFSS will report the results of the review to the Task Force on Coordination of Planning, who in turn will report to the Reliability Coordinating Committee.
No
NPCC does not require Yes that SPS reviews be available for other RROs and NERC within 30 days Yes
TFSS
PRC-014-0
R3
The documentation of the Regional Reliability Organizations SPS assessment shall include the following elements (see R3.1, R3.2, etc. below):
B4 Sec. 6.0
The documentation required for a Comprehensive or Intermediate Review should be in the form of a report addressing each of the elements of the above presentation format. The report should be accompanied by the Areas bulk power system map and one-line diagram, summary tables, figures, and appendices, as appropriate. The report may include references to other studies performed by the Area or by utilities within the Area that are relevant to the Area review, with appropriate excerpts from those studies. A Comprehensive Review is required of each Area at least every five years (performed by the Area ).
No
TFSS
PRC-014-0 PRC-014-0
R3.1 R3.2
Identification of group conducting the assessment and the date the assessment was performed. Study years, system conditions, and contingencies analyzed in the technical studies on which the assessment is based and when those technical studies were performed.
B4 Sec. 4.0
No
Yes Yes
TFSS TFSS
B4 Sec. 5.1.5a, a) A Comprehensive Review should review all the existing, new, and modified SPSs included in its No b, & d transmission plan. b) For those SPSs whose failure or misoperation has an inter-Area or interregional effect, discuss and/or refer to appropriate load flow and stability studies analyzing the consequences. d) Where an SPS which was formerly considered to have only local consequences is identified as having the potential for inter-Area effects, for the time period being reviewed, the TFSS should notify the TFCP, TFSP and TFCO. In such instances a complete review of the SPS should be made. If the results of the Area Review indicates that the Areas planned bulk power transmission system is not in conformance with the NPCC Basic Criteria , TFSS will request the Area to develop a plan to achieve conformance with the Criteria. If the Area Review indicates an overall bulk power system reliability concern (not specific to the Areas planned bulk power transmission system), TFSS will consider what additional studies may be necessary to address the concern, and prepare a summary discussion and recommendation to the Task Force on Coordination of Planning. This review by the TFSS does not alter Area and/or Company responsibilities with respect to their system's conformity with the NPCC Basic Criteria . No
PRC-014-0
R3.3
Identification of SPSs that were found not to comply with NERC standards and Regional B4 Sec. 7.2 Reliability Organization criteria. Discussion of any coordination problems found between a SPS and other protection and control systems. B4 Sec. 7.3
Yes
TFSS
PRC-014-0
R3.4
No
TFSS
PRC-014-0
R3.5
B4 Sec. 2.0
No
TFSS
Page 65 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
PRC-015-0
Special Protection System Data and Documentation Special Protection System Data and Documentation
R1
PRC-015-0
R1
The Transmission Owner, Generator Owner, and Distribution Provider that owns an SPS A11 Sec. 5.0 shall maintain a list of and provide data for existing and proposed SPSs as specified in Reliability Standard PRC-013-0_R1. The Transmission Owner, Generator Owner, and Distribution Provider that owns an SPS A2 Sec. 2.3 shall maintain a list of and provide data for existing and proposed SPSs as specified in Reliability Standard PRC-013-0_R1.
5.0 Each new or modified Special Protection System must be reported to NPCC in accordance with the Procedure for NPCC Review of New or Modified Special Protection Systems (SPS) (Document C-16). In addition, each new or modified Type I or Type II Special Protection System must be reported to the Task Force on System Protection in accordance with the Procedure for Reporting and Reviewing Proposed Protection Systems for the Bulk Power System (Document C-22). 3g Data needed to analyze and model the electric system and its component facilities must be developed, maintained and made available for use in interconnected operating and planning studies, including data fault level analysis. Areas and member systems shall maintain and submit, as needed, data in accordance with applicable NPCC Procedures.
No
TFSS
No
No
TFSS
PRC-015-0
R2
The Transmission Owner, Generator Owner, and Distribution Provider that owns an SPS shall have evidence it reviewed new or functionally modified SPSs in accordance with the Regional Reliability Organizations procedures as defined in Reliability Standard PRC-012-0_R1 prior to being placed in service.
No 1.0 If an entity concludes that a new SPS or a modification of an existing SPS will be required which affects the BPS, the following procedure is to be followed to obtain concurrence from NPCC. Allowing for sufficient lead time to ensure an orderly review, the entity will notify the Chairman of the TFCP of its proposal to install a new SPS or modify and existing SPS. The entity will send copies of the complete notification to the TFCO and the TFSP. This notification will include statements that describe possible failure modes and whether misoperation, unintended operation or failure of the SPS would have local, interArea or inter-Regional consequences, when the SPS is planned for service, how long it is expected to remain in-service, the specific contingencies(s) for which it is designed to operate and whether the SPS will be designed according to the NPCC BPS Protection Criteria and the SPS Criteria .
No
TFSS
PRC-015-0
R2
The Transmission Owner, Generator Owner, and Distribution Provider that owns an SPS shall have evidence it reviewed new or functionally modified SPSs in accordance with the Regional Reliability Organizations procedures as defined in Reliability Standard PRC-012-0_R1 prior to being placed in service.
C16 Sec.2d
2d If the TFSS review concludes that the SPS could have inter-Area or inter-Regional consequences, they will inform TFCP. TFCP will arrange for an overall NPCC review as detailed in Step 3.
No
No
TFSS
PRC-015-0
R3
The Transmission Owner, Generator Owner, and Distribution Provider that owns an SPS none shall provide documentation of SPS data and the results of Studies that show compliance of new or functionally modified SPSs with NERC Reliability Standards and Regional Reliability Organization criteria to affected Regional Reliability Organizations and NERC on request (within 30 calendar days). The Transmission Owner, Generator Owner, and Distribution Provider that owns an SPS B21 Sec. 3.0 shall analyze its SPS operations and maintain a record of all misoperations in accordance with the Regional SPS review procedure specified in Reliability Standard PRC-0120_R1.
None
No
No
TFSS
PRC-016-0
R1
All protection system and special protection system misoperations shall be analyzed in accordance with Area policies to determine the cause and the corrective action to be taken. The minimum information to be recorded for each misoperation includes (others as well as ): - identification of the BPS elements identification of the affected hardware/software components of the protection system(s) or SPS(s) and/or the associated switching devices - the corrective action(s) taken or planned. Each Area shall keep a record of the above information for each misoperation.
No
No
TFSP
PRC-016-0
R2
The Transmission Owner, Generator Owner, and Distribution Provider that owns an SPS B21 Sec. 3.0 shall take corrective actions to avoid future misoperations.
3.0 - At each TFSP meeting, the TF will review all misops reported to it since the previous meeting. The minutes of the meeting shall record each misop. reviewed and the action taken or planned. TFSP will follow up on the planned corrective actions through its Action Item List to ensure that the planned actions are implemented. 2.0 This reviewdoes not alter Area and/or Company responsibilities with respect to their systems compliance with the NPCC Basic Criteria .
No
No
TFSP
PRC-016-0
R2
The Transmission Owner, Generator Owner, and Distribution Provider that owns an SPS B4 Sec. 2.0 shall take corrective actions to avoid future misoperations. The Transmission Owner, Generator Owner, and Distribution Provider that owns an SPS B21 Sec. 3.0 shall provide documentation of the misoperation analyses and the corrective action plans to its Regional Reliability Organization and NERC on request (within 90 calendar days).
No
No
TFSP
PRC-016-0
R3
Yes Each Area shall keep a record of the above information for each misoperation. Analyses should be undertaken and recorded within 60 days of the occurrence of the event in accordance with Area policies. The recorded information shall be maintained such that the Areas can report it to NPCC within thirty days from the date of a request.
NPCC is less stringent in No that there is no mention of the reporting requirements to NERC.
TFSP
PRC-017-0
R1
The Transmission Owner, Generator Owner, and Distribution Provider that owns an SPS A4 Sec. 1.0 shall have a system maintenance and testing program(s) in place. The program(s) shall include (see R1.1, etc. below):
This document establishes the minimum maintenance objectives and recommends maintenance practices for No protection of the NPCC bulk power system, including Type I special protection systems and protection required for the NPCC Automatic Underfrequency Load Shedding Program. Automatic underfrequency load shedding protection systems and generator underfrequency tripping relays are not generally located at bulk power system stations; however, they have a direct effect on the operation of the bulk power system during major emergencies, and as such they are subject to this Criteria. Refer to R1.1.1, R1.1.2, etc. below No
No
TFSP
PRC-017-0
Special Protection System Maintenance and Testing Special Protection System Maintenance and Testing
R1.1
SPS identification shall include but is not limited to (see R1.1.1, R1.1.2, etc. below):
A4 Sec. 2.0
No
TFSP
PRC-017-0
R1.1.1
Relays
A4 Sec. 2.0
Minimum periodic maintenance of each protection group includes: - making visual inspections - verifying inputs and outputs - confirming that the intended version of software is installed (microprocessor-based relays) -verifying operating characteristics
No
No
TFSP
Page 66 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
PRC-017-0
Special Protection System Maintenance and Testing Special Protection System Maintenance and Testing Special Protection System Maintenance and Testing Special Protection System Maintenance and Testing
R1.1.2
Instrument transformers
A4 Sec. 2.0
- verifying the integrity of current and voltage transformers and associated circuitry
No
TFSP
PRC-017-0
R1.1.3
A4 Sec. 2.0
No
No
TFSP
PRC-017-0
R1.1.4
Batteries
A4 Sec. 3.0
On batteries and chargers, verify proper operation and general condition every month.
No
No
TFSP
PRC-017-0
R1.2
A4 Sec. 2.0
All of the above shall be performed on a maintenance interval not exceeding that specified in Table 1 for bulk power system protection groups. (Note: SPS would fall in the All Other Protection Groups category)
No
NPCC doesnt specify the basis for the testing intervals in Table 1 is not provided
No
TFSP
PRC-017-0
R1.3
A4 Sec. 2.0
Minimum periodic maintenance of each protection group shall consist of verifying that the protection group is capable of performing its intended protection function. This includes: making visual inspections, verifying inputs and outputs, confirming that the intended version of software is installed verifying operating characteristics, verifying the integrity of CTs VTs and associated circuitry, verifying the proper performance of communications systems, etc.
No
No
TFSP
PRC-017-0
Special Protection System Maintenance and Testing Special Protection System Maintenance and Testing Special Protection System Maintenance and Testing Special Protection System Maintenance and Testing
R1.4
none
None
No
No
TFSP
PRC-017-0
R1.5
none
None
No
No
TFSP
PRC-017-0
R1.6
none
None
No
No
TFSP
PRC-017-0
R2
The Transmission Owner, Generator Owner, and Distribution Provider that owns a A8 Appendix transmission protection system shall provide documentation of its transmission A4.1 protection system program and its implementation to the appropriate Regional Reliability Organization and NERC on request (within 30 calendar days). The Regional Reliability Organization shall establish, maintain and annually update a database for UVLS programs implemented by entities within the region to mitigate the risk of voltage collapse or voltage instability in the BES. This database shall include the following items: R1.1. Owner and operator of the UVLS program. R1.2. Size and location of customer load, or percent of connected load, to be interrupted. R1.3. Corresponding voltage set points and overall scheme clearing times. R1.4. Time delay from initiation to trip signal. R1.5. Breaker operating times. R1.6. Any other schemes that are part of or impact the UVLS programs such as related generation protection, islanding schemes, automatic load restoration schemes, UFLS and Special Protection Systems. The Regional Reliability Organization shall provide the information in its UVLS database to the Planning Authority, the Transmission Planner, or other Regional Reliability Organizations and to NERC within 30 calendar days of a request. Each Transmission Owner and Distribution Provider that owns a UVLS program to mitigate the risk of voltage collapse or voltage instability in the BES shall annually update its UVLS data to support the Regional UVLS program database. The following data shall be provided to the Regional Reliability Organization for each installed UVLS system: R1.1. Size and location of customer load, or percent of connected lead, to be interrupted. R1.2. Corresponding voltage set points and overall scheme clearing times. R1.3. Time delay from initiation to trip signal. R1.4. Breaker operating times. R1.5. Any other schemes that are part of or impact the UVLS programs such as related generation protection, islanding schemes, automatic load restoration schemes, UFLS and Special Protection Systems.
Specifies that Protection system owners shall implement a protection system maintenance and testing program that fulfills the requirements of the NPCC Maintenance Criteria for Bulk Power System Protection (Document A-4). It also requires that they report annually to NPCC, no later than 6 months after the end of the reporting period. At present, a reporting period is equal to the prior calendar year.
No
No
TFSP
PRC-020-1
R1
TFSP
PRC-010-1
Undervoltage Load Shedding Program Database Undervoltage Load Shedding Program Database
R2
TFSP
PRC-021-1
R1
TFSP
Page 67 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
PRC-021-1
PRC-022-1
Undervoltage Load Shedding Program Performance Undervoltage Load Shedding Program Performance
R2
R1
Each Transmission Owner and Distribution Provider that owns a UVLS program shall provide its UVLS program data to the Regional Reliability Organization with 30 calendar days of a request. Each Transmission Operator, Load-Serving Entity, and Distribution Provider that operates a UVLS program to mitigate the risk of voltage collapse or voltage instability in the BES shall analyze and document all UVLS operations and Misoperations. The analysis shall include: R1.1. A description of the event including initiating conditions. R1.2. A review of the UVLS set points and tripping times. R1.3. A simulation of the event, if deemed appropriate by the Regional Reliability Organization. For most events, analysis of sequence of events may be sufficient and dynamic simulations may not be needed. R1.4. A summary of the findings. R1.5. For any Misoperation, a Corrective Action Plan to avoid future Misoperations of a similar nature. Each Transmission Operator, Load-Serving Entity, and Distribution Provider that operates a UVLS program shall provide documentation of its analysis of the UVLS program performance to its Regional Reliability Organization within 9i0 calendar days of a request. Each Transmission Operator shall have the responsibility and clear decision-making A3 Sec. 4.1 authority to take whatever actions are needed to ensure the reliability of its area and shall exercise specific authority to alleviate operating emergencies. Reliability Coordinators, control area operators, and system operators shall have the responsibility and authority to implement emergency procedures including the curtailment of transactions and / or shedding of firm load. No NPCC documents do not No use the Functional Model language for op. entities but the intent of the instructs. is clear
TFSP
TFSP
PRC-022-1
R2
TOP-001-0
R1
TFCO
TOP-001-0
R2
Each TOP shall take immediate actions to alleviate operating emergencies including curtailing transmission service or energy schedules, operating equipment (e.g., generators, phase shifters, breakers), shedding firm load, etc. Each TOP, BA and GOP shall comply with reliability directives issued by the RC, and each BA and GOP shall comply with reliability directives issued by the TOP, unless such actions would violate safety, equipment, regulatory or statutory requirements. Under these circumstances the TOP, BA or GOP shall immediately inform the RC or TOP of the inability to perform the directive so that the RC or TOP can implement other remedial actions.
A3 Sec. 4.1
Reliability Coordinators, control area operators, and system operators shall have the responsibility and authority to implement emergency procedures including the curtailment of transactions and / or shedding of firm load.
No
No
TFCO
TOP-001-0
R3
No
No
TFCO
TOP-001-0
R4
Each Distribution Provider and Load Serving Entity shall comply with all reliability A3 Sec. 4.1 directives issued by the Transmission Operator, including shedding firm load, unless such actions would violate safety, equipment, regulatory or statutory requirements. Under these circumstances, the Distribution Provider or Load Serving Entity shall immediately inform the Transmission Operator of the inability to perform the directive so that the Transmission Operator can implement alternate remedial actions.
Reliability Coordinators, control area operators, and system operators shall have the responsibility and authority to implement emergency procedures including the curtailment of transactions and / or shedding of firm load.
No
NPCC documents do not No specifically address the requirements expected of Distribution Providers or Load Serving Entities
TFCO
TOP-001-0
R5
Each Transmission Operator shall inform its Reliability Coordinator and any other potentially affected Transmission Operators of real time or anticipated emergency conditions, and take actions to avoid, when possible, or mitigate the emergency.
A3 Sec. 4.1
Reliability Coordinators, control area operators, and system operators shall have the responsibility and authority to implement emergency procedures including the curtailment of transactions and / or shedding of firm load.
No
NPCC documents No contain no reference to TOP informing its RC, even in the NPCC Regional Reliability Plan No
TFCO
TOP-001-0
R6
Each Transmission Operator, Balancing Authority, and Generator Operator shall render A3 Sec. 3.8 all available emergency assistance to others as requested, provided that the requesting entity has implemented its comparable emergency procedures, unless such actions would violate safety, equipment, or regulatory or statutory requirements.
When an affected Area within NPCC is unable to correct a situation, a request for assistance from an Area or No systems outside NPCC shall be made. Upon receiving a request for assistance to mitigate an emergency, an Area shall provide maximum reasonable assistance to any other Areas or systems outside of NPCC and shall act within the time frame that such assistance is required (Note: Neighboring Areas will ensure suitable arrangements with the generating resources and / or transmission provider(s) in the Area are in place to be able to provide reasonable assistance). No
TFCO
TOP-001-0
Reliability Responsibility and Authorities Reliability Responsibility and Authorities Reliability Responsibility and Authorities
R7
TOP-001-0
R7
TOP-001-0
R7.1
Each Transmission Operator and Generator Operator shall not remove Bulk Electric System facilities from service if removing those facilities would burden neighboring systems unless (see R7.1, etc. below): Each Transmission Operator and Generator Operator shall not remove Bulk Electric System facilities from service if removing those facilities would burden neighboring systems unless (see R7.1, etc. below): For a generator outage, the GOP shall notify and coordinate with the Transmission Operator. The TOP shall notify the Reliability Coordinator and other affected TOP, and coordinate the impact of removing the Bulk Electric System facility
RRP Sec. 4.6.2 4.6.2 NPCC TOP and GOP are required to notify and coordinate with their RC and adjacent TOP before removing BES facilities from service if removing those facilities would burden a neighboring Area. RRP Sec. 4.2 4.2 RC and TOP, GOP and BA shall not take any action or refrain from taking any action hat would, knowingly, lead to an emergency condition within their Area or a neighboring area.
No
TFCO
No
No
TFCO
RRP Sec. 4.6.2 NPCC TOP and GOP are required to notify and coordinate with their RC and adjacent TOP before removing No BES facilities from service if removing those facilities would burden a neighboring Area.
No
TFCO
Page 68 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
TOP-001-0
R7.2
For a transmission facility, the Transmission Operator shall notify and coordinate with its RRP Sec. 4.6.2 NPCC TOP and GOP are required to notify and coordinate with their RC and adjacent TOP before removing No Reliability Coordinator. The TOP shall notify other affected TOP, and coordinate the BES facilities from service if removing those facilities would burden a neighboring Area. impact of removing the Bulk Electric System facility. When time does not permit such notifications and coordination, or when immediate RRP Sec. 4.6.2 action is required to prevent a hazard to the public, lengthy customer service interruption, or damage to facilities, the Generator Operator shall notify the Transmission Operator, and the Transmission Operator shall notify its Reliability Coordinator and adjacent Transmission Operators, at the earliest possible time. During a system emergency, the Balancing Authority and Transmission Operator shall A3 Sec. 3.6 immediately take action to restore the Real and Reactive Power Balance. If the Balancing Authority or Transmission Operator is unable to restore Real and Reactive Power Balance it shall request emergency assistance from the Reliability Coordinator. If corrective action or emergency assistance is not adequate to mitigate the Real and Reactive Power Balance, then the Reliability Coordinator, Balancing Authority, and Transmission Operator shall implement firm load shedding. When immediate emergency action is required to remove a BES facility from service, the GOP shall notify No and coordinate with the TOP and its RC. The TOP shall notify and coordinate with its RC and adjacent TOP at the earliest possible time. NPCC Document C-13 provides notification procedures for removal from service of critical facilities as well as a list of critical facilities that, if removed from service, may directly or indirectly burden a neighboring TOP. 3.6 - A trending of voltage through normal maximum or minimum values is an indication of insufficient real No or reactive control in an Area. The affected Area must quickly restore the real and reactive power balance between load and source.
No
TFCO
TOP-001-0
R7.3
No
TFCO
TOP-001-0
R8
No
TFCO
TOP-001-0
R8
During a system emergency, the Balancing Authority and Transmission Operator shall RRP Sec. 4.6.5 immediately take action to restore the Real and Reactive Power Balance. If the Balancing Authority or Transmission Operator is unable to restore Real and Reactive Power Balance it shall request emergency assistance from the Reliability Coordinator. If corrective action or emergency assistance is not adequate to mitigate the Real and Reactive Power Balance, then the Reliability Coordinator, Balancing Authority, and Transmission Operator shall implement firm load shedding.
4.6.5 When an Area is experiencing abnormal voltage conditions, its RC is required to immediately take No action to restore the reactive power balance. The RC is required to implement corrective control actions, which include requesting emergency assistance. If these actions are still not adequate to mitigate the reactive power imbalance then the RC is required to take all necessary steps to relieve the abnormal voltage conditions including firm load shedding per VAR-001-0, R6.
No
TFCO
TOP-002-0
R1
Each Balancing Authority and Transmission Operator shall maintain a set of current plans that are designed to evaluate options and set procedures for reliable operation through a reasonable future time period. In addition, each Balancing Authority and Transmission Operator shall be responsible for using available personnel and system equipment to implement these plans to ensure that interconnected system reliability will be maintained. Each Balancing Authority and Transmission Operator shall maintain a set of current plans that are designed to evaluate options and set procedures for reliable operation through a reasonable future time period. In addition, each Balancing Authority and Transmission Operator shall be responsible for using available personnel and system equipment to implement these plans to ensure that interconnected system reliability will be maintained. Each Balancing Authority and Transmission Operator shall maintain a set of current plans that are designed to evaluate options and set procedures for reliable operation through a reasonable future time period. In addition, each Balancing Authority and Transmission Operator shall be responsible for using available personnel and system equipment to implement these plans to ensure that interconnected system reliability will be maintained. Each Balancing Authority and Transmission Operator shall maintain a set of current plans that are designed to evaluate options and set procedures for reliable operation through a reasonable future time period. In addition, each Balancing Authority and Transmission Operator shall be responsible for using available personnel and system equipment to implement these plans to ensure that interconnected system reliability will be maintained. Each Balancing Authority and Transmission Operator shall maintain a set of current plans that are designed to evaluate options and set procedures for reliable operation through a reasonable future time period. In addition, each Balancing Authority and Transmission Operator shall be responsible for using available personnel and system equipment to implement these plans to ensure that interconnected system reliability will be maintained. Each Balancing Authority and Transmission Operator shall ensure its operating personnel participate in the system planning and design study processes, so that these studies contain the operating personnel perspective and system operating personnel are aware of the planning purpose.
The characteristics of a reliable bulk power system include adequate resources, planned and implemented, No to reliably meet projected customer electricity demand and energy requirements. Trans. systems that are part of an interconnected network must be designed and constructed to reliably deliver electricity from the generation resources to the customer. Application of these principles implies:
No
TFCO
TOP-002-0
R1
A2 Sec. 1.0 a
a)
A balanced relationship should be maintained among the type, size, capacity, and location of resources No
No
TFCO
TOP-002-0
R1
A2 Sec. 1.0 b
b) A balanced relationship among transmission system elements should be maintained to avoid excessive No dependence on any one transmission circuit, structure, right-of-way, or sub.
No
TFCO
TOP-002-0
R1
A2 Sec. 1.0 c
c) Transmission systems should provide flexibility in switching arrangements, voltage control, and other control measures to promote reliable system operation
No
No
TFCO
TOP-002-0
R1
B4 Sec. 1.0
B4 each Area shall conduct an annual assessment of the reliability of the planned BPS within the Area and the interconnections to other Areas
No
No
TFCO
TOP-002-0
R2
A2 Sec. 1.0
A2 Sec. 1.0 - Through its committees and task forces, the Council shall conduct regional and interregional studies, and assess and monitor Area studies and operations to assure conformance to the criteria.
No
NPCC is not clear that No operating personnel participate in the process except by reference to TFCO in the last page of both A2 and B4 documents.
TFCO
Page 69 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
TOP-002-0
R2
Each Balancing Authority and Transmission Operator shall ensure its operating personnel participate in the system planning and design study processes, so that these studies contain the operating personnel perspective and system operating personnel are aware of the planning purpose. Each Balancing Authority and Transmission Operator shall ensure its operating personnel participate in the system planning and design study processes, so that these studies contain the operating personnel perspective and system operating personnel are aware of the planning purpose.
A2 last page
A2 last page - Reviewed for concurrence by: Task Force on Coordination of Operations, TFSP, TFSS and TFEMT Chairman
No
TFCO
TOP-002-0
R2
B4 last page
B4 last page - Reviewed for concurrence by: Task Force on Coordination of Operations and TFCP
No
No
TFCO
TOP-002-0
R3
Each Load Serving Entity and Generator Operator shall coordinate (where confidentiality A2 Sec. 4.0 agreements allow) its current-day, next-day, and seasonal operations with its Host Balancing Authority and Transmission Service Provider. Each Balancing Authority and Transmission Service Provider shall coordinate its current-day, next-day, and seasonal operations with its Transmission Operator. Each Balancing Authority and Transmission Operator shall coordinate (where confidentiality agreements allow) its current-day, next-day, and seasonal planning and operations with neighboring Balancing Authorities and Transmission Operators and with its Reliability Coordinator, so that normal Interconnection operation will proceed in an orderly and consistent manner. NPCC Regional Reliability Plan Sec. 3.1.1.8 & 3.1.2.1
Each Area shall make every effort to schedule outages and deratings of resources in such a manner that the No available resources, with due allowance for forced outages and deratings, will be adequate to meet the Area's forecasted load and reserve requirements, in accordance with the NPCC Document A-6. For consistent evaluation and reporting of resource adequacy, it is necessary to measure the net capability of generating units and loads utilized as a resource of each Area on a regular basis. 3.1.1.8 The RC shall coordinate with other RC and TOP, BA and GOP as needed to develop and No implement action plans to mitigate potential or actual SO, IROL, CPS or DCS violations. This includes coordination of pending generation and transmission maintenance outages in both the real-time and next-day time frames. It also includes coordination of any actions, including emergency assistance, required to mitigate any operational concerns. 3.1.2.1 The RC shall conduct next-day reliability analysis for its RC Area to ensure that the BES can be operated reliably in anticipated normal and post contingency conditions.
No
TFCO
TOP-002-0
R4
No
TFCO
TOP-002-0
R5
Each Balancing Authority and Transmission Operator shall plan to meet scheduled system configuration, generation dispatch, interchange scheduling and demand patterns.
3.1.2.2 Each TOP, BA, Transmission Owner, Generation Owner, GOP and LSE in the RC Area shall provide to their RC all information required for system studies, such as critical facility status, load, generation, Operating Reserve projections and known interchange transactions. 3.1.2.3 The RC shall, in conjunction with its TOP and BA, develop action plans that address operational concerns by reconfiguring the transmission system, redispatching generation, etc.
No
No
TFCO
TOP-002-0
R5
Each Balancing Authority and Transmission Operator shall plan to meet scheduled system configuration, generation dispatch, interchange scheduling and demand patterns. Each Balancing Authority and Transmission Operator shall plan to meet unscheduled changes in system configuration and generation dispatch (at a minimum N-1 Contingency planning) in accordance with NERC, Regional Reliability Organization, subregional, and local reliability requirements. Each Balancing Authority and Transmission Operator shall plan to meet unscheduled changes in system configuration and generation dispatch (at a minimum N-1 Contingency planning) in accordance with NERC, Regional Reliability Organization, subregional, and local reliability requirements.
No
No
TFCO
TOP-002-0
R6
TOP-002-0
R6
A2 Sec. 5.0
4.0 - Each Area shall make every effort to schedule outages and deratings of resources in such a manner that No the available resources, with due allowance for forced outages and deratings, will be adequate to meet the Area's forecasted load and reserve requirements, in accordance with the NPCC Operating Reserve Criteria (Document A-6). 5.0 - The portion of the bulk power system in each Area and of each member system shall be designed with No sufficient transmission capability to serve forecasted loads under the conditions noted in Sections 5.1 and 5.2. These criteria will also apply after any critical generator, transmission circuit, transformer, series or shunt compensating device or HVdc pole has already been lost, assuming that the Area generation and power flows are adjusted between outages by the use of ten-minute reserve and where available, phase angle regulator control and HVdc control. Anticipated transfers of power from one Area to another, as well as within Areas, shall be considered in the design of inter-Area and intra-Area transmission facilities.
No
TFCO
No
TFCO
TOP-002-0
R7
Each Balancing Authority shall plan to meet capacity and energy reserve requirements, including the deliverability/capability for any single Contingency.
Same as R6 above
No
No
TFCO
TOP-002-0
R8
Each Balancing Authority shall plan to meet voltage and/or reactive limits, including the A2 Sec. 5.2 a deliverability/capability for any single contingency.
a - Reactive power capacity with adequate reserves and appropriate controls shall be installed in each Area to maintain voltages within normal limits for predisturbance conditions, and within applicable emergency limits for the system conditions that exist following the contingencies specified in 5.1 b - Line and equipment loadings shall be within normal limits for predisturbance conditions and within applicable emergency limits for the system conditions that exist following the contingencies specified in 5.1 The NERC/OC Monitoring Standards which apply during electric power operation are: - Control Performance Standard 1 (CPS1) - Control Performance Standard 2 (CPS2) The NERC/OC and NPCC objective is that each control area meets or exceeds the above CPS1 and CPS2 Standards.
No
No
TFCO
TOP-002-0
R8
Each Balancing Authority shall plan to meet voltage and/or reactive limits, including the A2 Sec. 5.2 b deliverability/capability for any single contingency. Each Balancing Authority shall plan to meet Interchange Schedules and ramps. B2 Sec. 2.0
No
No
TFCO
TOP-002-0
R9
No
No
TFCO
TOP-002-0
R10
Each Balancing Authority and Transmission Operator shall plan to meet all System Operating Limits (SOLs) and Interconnection Reliability Operating Limits (IROLs).
RRP Sec. 4.6.3 Following a contingency that results in a SOL or IROL violation, NPCC RC are required to direct their TOP, No GOP and BA to return the transmission system to within the SOL and IROL as soon as possible, within 30 minutes, as indicated in IRO-005-0, R5.
No
TFCO
Page 70 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
TOP-002-0
R11
The Transmission Operator shall perform seasonal, next-day, and current-day Bulk A2 Sec. 2.2 Electric System studies to determine SOLs. Neighboring Transmission Operators shall utilize identical SOLs for common facilities. The Transmission Operator shall update these Bulk Electric System studies as necessary to reflect current system conditions; and shall make the results of Bulk Electric System studies available to the Transmission Operators, Balancing Authorities (subject confidentiality requirements), and to its Reliability Coordinator.
Coordination among and within the Areas of NPCC is essential to the reliability of interconnected operations. No Timely information concerning system conditions shall be transmitted by the NPCC Areas to other Areas or systems as needed to assure reliable operation of the bulk power system. The operating criteria represent the application of the design criteria to inter-Area, intra-Area (inter-system) and intra-system operation. The operating criteria define the minimum level of reliability that shall apply to inter-Area operation. Where interArea reliability is affected, each Area shall establish limits and operate so that the contingencies stated in Sec. 6.1 and 6.2 can be withstood without causing a significant adverse impact on other Areas.
No
TFCO
TOP-002-0
R12
The Transmission Service Provider shall include known SOLs or IROLs within its area and neighboring areas in the determination of transfer capabilities, in accordance with filed tariffs and/or regional Total Transfer Capability and Available Transfer Capability calculation processes.
CO-13 Per Methodology Regional Methodology & Guidelines For Forecasting TTC & ATC (RMGF T&A)
No
No
TFCO
TOP-002-0
R13
At the request of the Balancing Authority or Transmission Operator, a Generator Operator shall perform generating real and reactive capability verification that shall include, among other variables, weather, ambient air and water conditions, and fuel quality and quantity, and provide the results to the Balancing Authority or Transmission Operator operating personnel as requested. At the request of the Balancing Authority or Transmission Operator, a Generator Operator shall perform generating real and reactive capability verification that shall include, among other variables, weather, ambient air and water conditions, and fuel quality and quantity, and provide the results to the Balancing Authority or Transmission Operator operating personnel as requested. Generator Operators shall, without any intentional time delay, notify their Balancing Authority and Transmission Operator of changes in capabilities and characteristics including but not limited to (see R14.1 & 14.2 below): Changes in real and reactive output capabilities.
B9 Sec. 1.0
1.0 - The following guide for rating generating capability for each seasonal period (summer & winter), shall be used by members of the NPCC for the purpose of determining and reporting the Net Capability of generating units claimed as operable capability in their respective Areas.
No
No
TFCO
TOP-002-0
R13
B9 Sec. 2.1.1
2.1.1 - The Net Capability of a generating unit for the purpose of this guide is defined as the megawatt output No at the generator terminals, at the power factor normally expected for that unit, at the time of the seasonal peak load, minus the auxiliary electric power requirements necessary to operate the unit at maximum output and minus a fair portion of the common service load (e.g., fuel handling, lighting) required to run multiple unit generating stations. Each TOP, BA, Transmission Owner, Generation Owner, GOP and LSE in the RC Area shall provide to their No RC all information required for system studies, such as critical facility status, load, generation, Operating Reserve projections and known interchange transactions. Same as above No
No
TFCO
TOP-002-0
R14
No
TFCO
TOP-002-0
R14.1
NPCC does not have No criteria regarding notification of changes in reactive output capabilities. By implication, this No means that the TOP and GOP must be aware of and reporting this information to the RC
TFCO
TOP-002-0
R14.2
The RC shall monitor parameters that my have significant impacts on its RC Area parameters, including but not limited to the following, where applicable: Current status of BES including AVRs and SPS schemes
No
TFCO
TOP-002-0
R15
Generation Operators shall, at the request of the Balancing Authority or Transmission Operator, provide a forecast of expected real power output to assist in operations planning (e.g., a seven-day forecast of real output).
The security coordinators of the NPCC control Areas must have access to the security data specified in this No procedure in order to adequately assess the reliability of the NPCC BPS. All users of the electric systems, including market participants, must supply such data to the security coordinators of the NPCC Control Areas. Coordination among and within the Areas of NPCC is essential to the reliability of interconnected operations. Timely information concerning system conditions shall be transmitted by the NPCC Areas to the other Areas or systems as needed to assure reliable operation of the BPS. One aspect of this coordination is to ensure that adjacent Areas and neighboring systems are advised on a regular basis of expected operating conditions, including generator, transmission and system protection, including Type I SPS, outages that may materially reduce the ability of an Area to contribute to the reliable operation of the interconnected system, or to receive and/or render assistance to another Area or neighboring system.
NPCC is still using the No outdated term security coordinators in this document instead of Reliability Coordinators.
TFCO
TOP-002-0
R16
Subject to standards of conduct and confidentiality agreements, Transmission Operators shall, without any intentional time delay, notify their Reliability Coordinator and Balancing Authority of changes in capabilities and characteristics including but not limited to (see R16.1 and R16.2 below):
No
No
TFCO
Page 71 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
TOP-002-0
R16.1
No An Area will not normally remove from service any transmission facility, which might have a reliability impact on an adjacent Area or neighboring system without prior notification to and appropriate review by that Area or system. However, in the event of an emergency condition, each Area may take action as deemed appropriate: other Areas or systems should be notified immediately. none No NPCC does not require notification for changes in transmission capability, only for removal from service.
No
TFCO
TOP-002-0
R16.2
none
No
TFCO
TOP-002-0
R17
Balancing Authorities and TOP shall, without any intentional time delay, communicate the information described in the requirements R1 to R16 above to their RC. Neighboring Balancing Authorities, TOP, GOP, TSP and LSE shall use uniform line identifiers when referring to transmission facilities of an interconnected network. Each Balancing Authority and Transmission Operator shall maintain accurate computer models utilized for analyzing and planning system operations.
None
none
No
No
TFCO
TOP-002-0
R18
None
none
No
No
TFCO
TOP-002-0
R19
A2 Sec. 2.3
For reliability purposes, Areas shall share and coordinate forecast system information and real time No information to enable and enhance the analysis and modeling of the interconnected BPS by security application software on EMS. Each member within an NPCC Area shall provide needed information to its Area representative as required. Analysis and modeling of the interconnected power system is required for reliable design and operation. Data needed to analyze and model the electric system and its component facilities must be developed, maintained, and made available for use in interconnected operating and planning studies, including data for fault level analysis.
More Specificity
No
TFCO
TOP-003-0
R1
Generator Operators and Transmission Operators shall provide planned outage information (see R1.1, R1.2 and R1.3 below):
NPCC Regional Each TOP, BA, Transmission Owner, Generation Owner, GOP and LSE in the RC Area shall provide to their No Reliability Plan RC all information required for system studies, such as critical facility status, load, generation, Operating Sec. 3.1.2.2 Reserve projections and known interchange transactions.
No
TFCO
TOP-003-0
R1.1
Each Generator Operator shall provide outage information daily to its TOP for scheduled NPCC Regional See R1 above generator outages planned for the next day (any foreseen outage of a generator greater Reliability Plan than 50 MW). The TOP shall establish the outage reporting requirements. Sec. 3.1.2.2
No
NPCC does not specify No that TOP sets the outage reporting requirements and does not set a limit on unit size for reporting
TFCO
TOP-003-0
R1.2
Each TOP shall provide outage information daily to its RC, and to affected BA and TOP NPCC Regional See R1 above for scheduled generator and BES outages planned for the next day (any foreseen outage Reliability Plan of a transmission line or transformer greater than 100 kV or generator greater than 50 Sec. 3.1.2.2 MW) that may collectively cause or contribute to an SOL or IROL violation or a regional operating area limitation. The RC shall establish the outage reporting requirements.
No
NPCC does not specify No that the RC sets the outage reporting requirements and it does not specify 100 kV as a transmission reporting threshold No
TFCO
TOP-003-0
R1.3
Such information shall be available by 1200 Central Standard Time for the Eastern Interconnection and 1200 Pacific Standard Time for the Western Interconnection. Each Transmission Operator, Balancing Authority, and Generator Operator shall plan and coordinate scheduled outages of system voltage regulating equipment, such as automatic voltage regulators on generators, supplementary excitation control, synchronous condensers, shunt and series capacitors, reactors, etc., among affected Balancing Authorities and Transmission Operators as required. Each Transmission Operator, Balancing Authority, and Generator Operator shall plan and coordinate scheduled outages of system voltage regulating equipment, such as automatic voltage regulators on generators, supplementary excitation control, synchronous condensers, shunt and series capacitors, reactors, etc., among affected Balancing Authorities and Transmission Operators as required. Each TOP, BA, and GOP shall plan and coordinate scheduled outages of telemetering and control equipment and associated communication channels between the affected areas.
This information shall be available by 1200 Central Standard Time for the Eastern Interconnection.
No
TFCO
TOP-003-0
R2
3.1.3.2 - Reactive Reserves: The RC is required to monitor its Areas parameters to ensure that sufficient reactive resources are available to maintain voltage within normal limits for pre-disturbance conditions , and within emergency limits for the system conditions that exist following the contingencies.
No
No
TFCO
TOP-003-0
R2
4.2.1 NPCC Document A-2requires that scheduled outages of transmission facilities that affect interArea reliability be coordinated sufficiently in advance of the outage to permit the affected Areas to maintain reliability.
No
No
TFCO
TOP-003-0
R3
None
None
No
No
TFCO
Page 72 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
TOP-003-0
R4
Each Reliability Coordinator shall resolve any scheduling of potential reliability conflicts.
The RC shall coordinate with other RC and TOP, BA and GOP as needed to develop and implement action plans to mitigate potential or actual SOL, IROL, CPS or DCS violations. This includes coordination of pending generation and transmission maintenance outages in both the real time and next day time frames. It also includes coordination of any actions, including emergency assistance, required to mitigate any operational concerns.
No
TFCO
TOP-004-0
Transmission Operations
R1
Each Transmission Operator shall operate within the Interconnection Reliability Operating Limits (IROLs) and System Operating Limits (SOLs).
NPCC Regional The RC and TOP shall have sufficient real time information and analysis tools to determine potential SOL or Reliability Plan IROL violations. This analysis shall be conducted in all operating timeframes. The RC shall use the results (RRP) Sec. of these analyses to determine the causes of the violations and identify mitigating actions. 4.6.3
No
No
TFCO
TOP-004-0
Transmission Operations
R2
Each Transmission Operator shall operate so that instability, uncontrolled separation, or A2 Sec. 1.0 cascading outages will not occur as a result of the most severe single contingency.
The objective of these criteria is to provide a design-based approach to ensure the BPS is designed and No operated to a level of reliability such that the loss of a major portion of the system, or unintentional separation of a major portion of the system, will not result from any design cont. referenced in Sect 5.1 and 5.2. In NPCC the technique for assuring the reliability of the BPS is to require that it be designed and operated to withstand representative contingencies as specified in these criteria. No Extreme contingency assessment recognizes that the BPS can be subjected to events which exceed, in severity, the contingencies listed in Section 5.1. One of the objectives of extreme contingency assessment is to determine, through planning studies, the effects of extreme contingencies on system performance in order to obtain an indication of system strength No
No
TFCO
TOP-004-0
Transmission Operations
R3
Each Transmission Operator shall, when practical, operate to protect against instability, uncontrolled separation, or cascading outages resulting from multiple outages, as specified by Regional Reliability Organization policy.
A2 Sec. 7.0
No
TFCO
TOP-004-0
Transmission Operations
R4
. If a Transmission Operator enters an unknown operating state (i.e. any state for which valid operating limits have not been determined), it will be considered to be in an emergency and shall restore operations to respect proven reliable power system limits within 30 minutes. Each Transmission Operator shall make every effort to remain connected to the Interconnection. If the Transmission Operator determines that by remaining interconnected, it is in imminent danger of violating an IROL or SOL, the Transmission Operator may take such actions, as it deems necessary, to protect its area.
RRP Sec. 4.6.1 If the TOP enters an unknown operating state (i.e. any state for which valid operating limits have not been determined), it will be considered to be in emergency and shall restore operations to respect proven reliable power system limits within 30 minutes. C20 Sec. 5.0 If preventative measures as outlined under sections 3.0 and/or 4.0 have not been adequate, actions to contain an emergency should then be taken. These actions should apply to both the Area or Areas causing the emergency (if identifiable) and the Area or Areas experiencing the emergency. The following is thus a continuation of the preventative measures implemented in sections 3.0 and/or 4.0 above. Steps include: shed firm load or reject generation - communicate that ties may be opened - open tie lines to prevent damage - issue the appropriate NERC EEA as per EOP-002-0 Attachment 1
No
TFCO
TOP-004-0
Transmission Operations
R5
No
No
TFCO
TOP-004-0
Transmission Operations
R6
TOP, individually and jointly with other TOP, shall develop, maintain, and implement A3 Sec. 1.0 formal policies and procedures to provide for transmission reliability. These policies and procedures shall address the execution and coordination of activities that impact interand intra-Regional reliability, including (refer to R6.1, etc. below): Equipment ratings. A2 Sec. 5.2b
The purpose of these criteria is to present the basic factors to be considered in formulating plans and No procedures to be followed in an emergency or during conditions which could lead to an emergency, in order to facilitate mutual assistance and coordination within NPCC. Objectives, principles and requirements are presented to assist the Area formulating plans and procedures to achieve desired results. 5.2b Line and equipment loadings shall be within normal limits for predisturbance conditions and within No applicable emergency limits for the system conditions that exist following the contingencies specified in 5.1 4.2 When an Area is experiencing internal circuit or tie line loading in excess of applicable operating No limits, the following steps should be implemented as required and appropriate, based on industry-wide and/or local procedures: (congestion management, recall equipment outages, use TLR, load shed, etc.)
No
TFCO
TOP-004-0
Transmission Operations
R6.1
No
TFCO
TOP-004-0
Transmission Operations
R6.1
Equipment ratings.
No
TFCO
TOP-004-0 TOP-004-0
R6.2 R6.3
Monitoring and controlling voltage levels and real and reactive power flows. Switching transmission elements.
If an Area is experiencing abnormal voltage conditions, it should implement the steps provided in NPCC No Document B-3 Guidelines for Inter-Area Voltage Control RRP Sec. 4.6.2 NPCC TOP and GOP are required to notify and coordinate with their RC and adjacent TOP before removing No BES facilities from service if removing those facilities would burden a neighboring Area. A2 Sec. 6.0 Scheduled outages of facilities that affect inter-Area reliability shall be coordinated sufficiently in advance of No the outage to permit the affected Areas to maintain reliability. Each Area shall notify adjacent Areas of scheduled or forced outages of any facility on the NPCC Transmission Facilities List and of any other condition which may impact on inter-Area reliability. No
No No
TFCO TFCO
TOP-004-0
Transmission Operations
R6.4
No
TFCO
TOP-004-0
Transmission Operations
R6.5
RRP Sec. 4.6.3 The RC and TOP shall have sufficient real time information and analysis tools to determine potential SOL or IROL violations. This analysis shall be conducted in all operating timeframes. The RC shall use the results of these analyses to determine the causes of the violations and identify mitigating actions. C20 Sec. 4.2
No
TFCO
TOP-004-0
Transmission Operations
R6.6
TOP-004-0
Transmission Operations
R6.6
4.2 When an Area is experiencing internal circuit or tie line loading in excess of applicable operating limits, No the following steps should be implemented as required and appropriate based on industry-wide and/or local procedures (final two steps below): C20 Sec. 4.2.10 4.2.10 The Area or Areas causing the overload (if identifiable) must adjust generation or perform actions No up to and including load shedding to keep loading below applicable operating limits. C20 Sec.4.2.11 4.2.11 The Area experiencing the overload must, when effective, open circuits or implement load shedding No to return the load on elements to within applicable operating limits.
No
TFCO
No
TFCO
TOP-004-0
Transmission Operations
R6.6
No
TFCO
Page 73 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
TOP-005-0
R1
Each Transmission Operator and Balancing Authority shall provide its Reliability Coordinator with the operating data that the Reliability Coordinator requires to perform operational reliability assessments and to coordinate reliable operations within the Reliability Coordinator Area. Each Transmission Operator and Balancing Authority shall provide its Reliability Coordinator with the operating data that the Reliability Coordinator requires to perform operational reliability assessments and to coordinate reliable operations within the Reliability Coordinator Area.
NPCC Regional 4.6.3 - The RC and TOP shall have sufficient real time information and analysis tools to determine potential Reliability Plan SOL or IROL violations. This analysis shall be conducted in all operating timeframes. The RC shall use the (RRP) Sec. results of these analyses to determine the causes of the violations and identify mitigating actions. 4.6.3 NPCC Regional 3.1.1.1 The RC shall conduct system assessment based on thermal, volt. and stab. limits to coordinate real Reliability Plan time and next day operations within appl. SOL and IROL. The RC shall ensure that its Wide Area view is (RRP) modeled coordinated operations. Sec.3.1.1.1 None
No
TFCO
TOP-005-0
R1
No
No
TFCO
TOP-005-0
R1.1
Each Reliability Coordinator shall identify the data requirements from the list in none Attachment 1-TOP-005-0 Electric System Reliability Data and any additional operating information requirements relating to operation of the bulk power system within the RC Area.
No
No
TFCO
TOP-005-0
R2
TOP-005-0
R3
As a condition of receiving data from the Interregional Security Network (ISN), each RRP Sec. 2.2.3 Identical to R2 ISN data recipient shall sign the NERC Confidentiality Agreement for Electric System .Data Upon request, each Reliability Coordinator shall, via the ISN or equivalent system, RRP Sec. 6.3 6.3 Each RC shall provide, or arrange provisions for, data exchange to other RC or TOP and BA via a exchange with other Reliability Coordinators operating data that are necessary to allow secure network. the Reliability Coordinators to perform operational reliability assessments and coordinate reliable operations. Reliability Coordinators shall share with each other the types of data listed in Attachment 1- TOP-005-0 Electric System Reliability Data, unless otherwise agreed to. RRP Sec. 7.2 Upon request, each BA and TOP shall provide to other BA and TOP with immediate RRP 6.4 Level responsibility for operational reliability, the operating data that are necessary to allow IIIa these BA and TOP to perform operational reliability assessments and to coordinate reliable operations. BA and TOP shall provide the types of data as listed in Attachment 1TOP-005-0 Electric System Reliability Data, unless otherwise agreed to by the BA and TOP with immediate responsibility for operational reliability. Each Purchasing-Selling Entity shall provide information as requested by its Host C13 Sec. 1.0 Balancing Authorities and Transmission Operators to enable them to conduct operational reliability assessments and coordinate reliable operations. 7.2 Each RC shall have adequate communications facilities (voice and data links) to appropriate entities within its RC Area. Through use of the ISN, Reliability Coordinators, Transmission Operators and Balancing Authorities will share specific operating information relevant to Inter-Regional operation as prescribed by NERC Reliability Standard TOP-006-0 such as Inter-tie flows, line and flowgate limits, ACE, generator status, load and frequency.
No
No
TFCO
No
NPCC criteria does not specify that Attachment 1-TOP-005-0 must be met.
No
TFCO
TOP-005-0 TOP-005-0
R3 R4
No No NPCC criteria does not specify that Attachment 1-TOP-005-0 must be met. No
TFCO TFCO
TOP-005-0
R5
The security coordinators of the NPCC control Areas must have access to the security data specified in this procedure in order to adequately assess the reliability of the NPCC bulk power system. All users of the electric systems, including market participants, must supply such data to the security coordinators of the NPCC Control Areas. Coordination among and within the Areas of NPCC is essential to the reliability of interconnected operations.
No
NPCC wording does not No refer to the Functional Model entities but its meaning is still clear.
TFCO
TOP-005-1
R1
Each Transmission Operator and Balancing Authority shall provide its Reliability Coordinator with the operating data that the Reliability Coordinator requires to perform operational reliability assessments and to coordinate reliable operations within the Reliability Coordinator Area. Each Reliability Coordinator shall identify the data requirements from the list in Attachment 1-TOP-005-0 Electric System Reliability Data and any additional operating information requirements relating to operation of the bulk power system within the Reliability Coordinator Area. As a condition of receiving data from the Interregional Security Network (ISN), each ISN data recipient shall sign the NERC Confidentiality Agreement for Electric System Reliability Data.
TFCO
TOP-005-1
R1.1
TFCO
TOP-005-1
R2
TFCO
TOP-005-1
R3 Upon request, each Balancing Authority and Transmission Operator shall provide to other Balancing Authorities and Transmission Operators with immediate responsibility for operational reliability, the operating data that are necessary to allow these Balancing Authorities and Transmission Operators to perform operational reliability assessments and to coordinate reliable operations. Balancing Authorities and Transmission Operators shall provide the types of data as listed in Attachment 1-TOP-005-0 Electric System Reliability Data, unless otherwise agreed to by the Balancing Authorities and Transmission Operators with immediate responsibility for operational reliability. Each Purchasing-Selling Entity shall provide information as requested by its Host Balancing Authorities and Transmission Operators to enable them to conduct operational reliability assessments and coordinate reliable operations.
TFCO
TOP-005-1
R4
TFCO TFCO
Page 74 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
TOP-006-0
R1
Each Transmission Operator and Balancing Authority shall know the status of all generation and transmission resources available for use.
NPCC Regional Monitoring and coordination for most operating concerns between RC, TOP and BA either within the Region No Reliability Plan or with TCs, TOPs and BAs in other Regions, are carried out by the RC. This includes both foreseen and (RRP) Sec. 6.4 unforeseen events. Through the use of the ISN, RC, TOP and BA will share specific operating information relevant to Inter-Regional operation as prescribed by NERC Reliability Standard TOP-006-0 such as Inter-tie flows, line and flowgate limits, ACE, generator status, load and frequency. For reliability purposes, Areas shall share and coordinate forecast system information and real time information to enable and enhance the analysis and modeling of the interconnected BPS by security application software on EMS. Each member within an NPCC Area shall provide needed information to its Area representatives as requiredData needed to analyze and model the elect. sys. and its component facilities must be developed, maintained and made available for use in interconn. operating and planning studies. No
No
TFCO
TOP-006-0
R1.1
Each Generator Operator shall inform its Host Balancing Authority and the Transmission A2 Sec. 2.3 Operator of all generation resources available for use.
NPCC does not No specifically say that Generation Operators must give information to the host TOP and BA No
TFCO
TOP-006-0
R1.2
Each Transmission Operator and Balancing Authority shall inform the Reliability Coordinator and other affected Balancing Authorities and Transmission Operators of all generation and transmission resources available for use. Each Transmission Operator and Balancing Authority shall inform the Reliability Coordinator and other affected Balancing Authorities and Transmission Operators of all generation and transmission resources available for use.
6.4 Each of the five Areas in NPCC (New York, New England, Ontario, Quebec and the Maritimes) No monitors and controls operating problems and events affecting reliability within their jurisdiction. Each TOP and BA is responsible for notifying their respective RC of any abnormal conditions that require InterArea/Regional action. 2.3 - For reliability purposes, Areas shall share and coordinate forecast system information and real time No information to enable and enhance the analysis and modeling of the interconnected BPS by security application software on EMS. Each member within an NPCC Area shall provide needed information to its Area representatives as requiredData needed to analyze and model the electric system and its component facilities must be developed, maintained and made available for use in interconnected operating and planning studies. Each Area shall develop, and operate in accordance with, its own voltage control procedures and criteria. No Area procedures and criteria shall be consistent with NPCC and NERC Criteria and Guidelines. Adjacent Areas should be familiar with each others criteria and procedures. Areas shall mutually agree upon procedures for inter-Area voltage control. Whether inter-Area voltage control is carried out through specific or general procedures, the following should be considered and applied: to effectively coordinate voltage control, location and placement of metering for reactive power resources and voltage controller status must be consistent between adjacent Areas. availability of voltage regulating transformers in proximity of tie lines reactive reserve of on-line generators shunt reactive device availability and switching strategy static VAR compensator availability, reactive reserve, and control strategy tie line reactive losses as a function of real power transfer etc.
TFCO
TOP-006-0
R1.2
A2 Sec. 2.3
No
TFCO
TOP-006-0
R2
Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall B3 Sec. 2.0 monitor applicable transmission line status, real and reactive power flows, voltage, loadtap-changer settings, and status of rotating and static reactive resources.
No
TFCO
TOP-006-0
R3
TOP-006-0
R4
TOP-006-0
R5
Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall provide appropriate technical information concerning protective relays to their operating personnel. Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall have information, including weather forecasts and past load patterns, available to predict the systems near-term load pattern. Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall use monitoring equipment to bring to the attention of operating personnel important deviations in operating conditions and to indicate, if appropriate, the need for corrective action.
none
None
No
No
TFCO
none
None
No
No
TFCO
6.2 Each RC shall determine the data requirements to support its RC tasks and shall request such data from No its TOP, BA, Transmission Owners, Generation Owners, GOP and LSE or adjacent RCs.
No
TFCO
TOP-006-0
R5
Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall use RRP Sec. 6.2, monitoring equipment to bring to the attention of operating personnel important 6.3.2 & 7.1 deviations in operating conditions and to indicate, if appropriate, the need for corrective action.
6.3.2 Each RC shall have detailed real-time monitoring capability of its RC Area and sufficient monitoring No capability of surrounding RC Areas to ensure that potential or actual SOL or IROL violations are identified. Each RC shall have monitoring systems that provide information that can be easily understood and interpreted by the RC operating personnel, giving particular attention to alarm management and awareness systems 7.1 Each RC shall have adequate analysis tools such as state estimation, pre and post-contingency analysis capabilities (thermal, stability and voltage), and wide-area overview displays (NPCC B-12 and C-17)
No
TFCO
TOP-006-0
R5
No
TFCO
TOP-006-0
R6
Each Balancing Authority and Transmission Operator shall use sufficient metering of suitable range, accuracy and sampling rate (if applicable) to ensure accurate and timely monitoring of operating conditions under both normal and emergency situations.
A3 Sec. 4.2
4.2 Accurate and reliable metering and indication of system frequency, breaker status, voltage levels and No power flows (real and reactive for all tie lines and other critical elements) shall be available to the appropriate system operator(s).
No
TFCO
Monitoring System Conditions Monitoring System Conditions Monitoring System Conditions Reporting SOL and IROL Violations
R6 R7 R7 Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall monitor system frequency. Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall monitor system frequency.
RRP Sec. 6.3.2 6.3.2 See R5 above RRP Sec. 3.1.3.5 A3 Sec. 4.2 3.1.3.5 The RC shall monitor system frequency and the performance of its BA and direct any necessary re- No balancing to return CPS and DCS compliance. 4.2 Accurate and reliable metering and indication of system frequency, breaker status, voltage levels and No power flows (real and reactive for all tie lines and other critical elements) shall be available to the appropriate system operator(s). 4.2 When an Area is experiencing internal circuit or tie line loading in excess of applicable operating limits, No the following steps should be implemented as required and appropriate based on industry-wide and/or local procedures (partial listing of steps is itemized below):
No No No
TOP-007-0
R1
A Transmission Operator shall inform its Reliability Coordinator when an IROL or SOL C20 Sec. 4.2, has been exceeded and the actions being taken to return the system to within limits.
No
TFCO
Page 75 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
TOP-007-0
Reporting SOL and IROL Violations Reporting SOL and IROL Violations Reporting SOL and IROL Violations Reporting SOL and IROL Violations
R1
A Transmission Operator shall inform its Reliability Coordinator when an IROL or SOL 4.2.6, has been exceeded and the actions being taken to return the system to within limits. A Transmission Operator shall inform its Reliability Coordinator when an IROL or SOL 4.2.8, has been exceeded and the actions being taken to return the system to within limits. A Transmission Operator shall inform its Reliability Coordinator when an IROL or SOL 4.2.10 has been exceeded and the actions being taken to return the system to within limits. Following a Contingency or other event that results in an IROL violation, the Transmission Operator shall return its transmission system to within IROL as soon as possible, but not longer than 30 minutes. none
No
TFCO
TOP-007-0
R1
4.2.8 Establish communication with areas inside and/or outside NPCC and request relief
No
No
TFCO
TOP-007-0
R1
4.2.10 The Area or Areas causing the overload (if identifiable) must adjust generation or perform actions up to and including load shedding to keep loading below applicable operating limits. None
No
No
TFCO
TOP-007-0
R2
No
NPCC Documents No contain no reference to a 30-minute requirement for TOP, only for the RC in the Regional Reliability Plan No
TFCO
TOP-007-0
Reporting SOL and IROL Violations Reporting SOL and IROL Violations Response to Transmission Limit Violations Response to Transmission Limit Violations Response to Transmission Limit Violations
R3
A TOP shall take all appropriate actions up to and including shedding firm load, or directing the shedding of firm load, in order to comply with Requirement R2.
C20 Sec. 4.2.10 The Area or Areas causing the overload (if identifiable) must adjust generation or perform actions up to and including load shedding to keep loading below applicable operating limits.
No
TFCO
TOP-007-0
R4
TOP-008-0
R1
TOP-008-0
R1
The Reliability Coordinator shall evaluate actions taken to address an IROL or SOL RRP Sec. violation and, if the actions taken are not appropriate or sufficient, direct actions required 3.1.1.6 to return the system to within limits. The Transmission Operator experiencing or contributing to an IROL or SOL violation C20 Sec. 4.2.10 shall take immediate steps to relieve the condition, which may include shedding firm load. 4.2.11
The RC shall identify the cause of the potential or actual SOL or IROL violation and initiate the control action No or emergency procedure to relieve the potential or actual SOL or IROL violation consistent with NERC Reliability Standard. 4.2.10 - The Area or Areas causing the overload (if identifiable) must adjust generation or perform actions No up to and including load shedding to keep loading below applicable operating limits. 4.2.11 The Area experiencing the overload must, when effective, open circuits or implement load shedding No to return the load on elements to within applicable operating limits. The RC shall ensure that all its TOP, BA, GOP, TSP, LSE and Purchasing-Selling Entities operate to prevent No the likelihood that a disturbance, action or non-action in its RC Area will result in a SOL or IROL violation in another Area of the Interconnection. In instances where the derived operating limits differ from one Area to another, the RC and its TOP, BA, GOP, TSP, LSE and PSE shall always operate the BES to the most limiting parameter. If an Area is in an emergency because of conditions in another Area, it should implement any of the following No actions that removes or lessens the threat to reliability:
No
TFCO
No
TFCO
No
TFCO
TOP-008-0
R2
Each Transmission Operator shall operate to prevent the likelihood that a disturbance, action, or inaction will result in an IROL or SOL violation in its area or another area of the Interconnection. In instances where there is a difference in derived operating limits, the Transmission Operator shall always operate the Bulk Electric System to the most limiting parameter.
No
TFCO
TOP-008-0
R3
The Transmission Operator shall disconnect the affected facility if the overload on a C20 Sec. transmission facility or abnormal voltage or reactive condition persists and equipment is endangered. In doing so, the Transmission Operator shall notify its Reliability Coordinator and all neighboring Transmission Operators impacted by the disconnection prior to switching, if time permits, otherwise, immediately thereafter. The Transmission Operator shall disconnect the affected facility if the overload on a 5.1 transmission facility or abnormal voltage or reactive condition persists and equipment is endangered. In doing so, the Transmission Operator shall notify its Reliability Coordinator and all neighboring Transmission Operators impacted by the disconnection prior to switching, if time permits, otherwise, immediately thereafter.
No
TFCO
TOP-008-0
R3
- Attempt to identify the specific cause(s) and communicate with relevant Areas. Request assistance if required. - Shed firm load or reject generation as appropriate. - Communicate (if time permits) to the adjacent Area that the tie lines will be opened if immediate action is not taken to alleviate the emergency. Open tie lines to prevent damage to equipment, if necessary. - Issue the appropriate NERC EEA level and follow procedures in NERC Standard Emergency Preparedness and Operations EOP-002-0 Attachment 1
No
No
TFCO
TOP-008-0
R4
The Transmission Operator shall have sufficient information and analysis tools to determine the cause(s) of SOL violations. This analysis shall be conducted in all operating timeframes. The TOP shall use the results of these analyses to immediately mitigate the SOL violation.
RRP Sec. 4.6.3 The RC and Transmission Operator shall have sufficient real time information and analysis tools to determine No potential SOL or IROL violations. This analysis shall be conducted in all operating timeframes. The RC shall use the results of these analyses to determine the causes of the violations and identify mitigating actions. Refer to R1.1, etc. below No
No
TFCO
TPL-001-0
R1
The Planning Authority and Transmission Planner shall each demonstrate through a valid Refer to assessment that its portion of the interconnected transmission system is planned such sections below that, with all transmission facilities in service and with normal (pre-contingency) operating procedures in effect, the Network can be operated to supply projected customer demands and projected Firm (non- recallable reserved) Transmission Services at all Demand levels over the range of forecast system demands, under the conditions defined in Category A of Table I. To be considered valid, the Planning Authority and Transmission Planner assessments shall (refer to R1.1, etc. below):
No
TFCP
TPL-001-0
R1.1
Be made annually
B-4 Section 4.0 Each Area is required to present an annual transmission review to TFSS. However, the review presented by No the Area may be one of three types: A Comprehensive (or Full) Review, an Intermediate (or Partial) Review, or an Interim Review.
No
TFCP
Page 76 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
TPL-001-0
R1.2
Be conducted for near-term (years one through five) and longer-term (years six through ten) planning horizons.
It is suggested that a study year of 4 to 6 years from the reporting date is a realistic one, both from the viewpoint of minimum lead times required for construction, and the ability to alter plans or facilities.
NPCC only suggests a No desired time frame for the studies. R1.3.1 & R1.3.3 below conflict with R1.2 in that they do NOT require studies out to a 10 year planning horizon. NPCC is OK with 6 yrs.
TFCP
TPL-001-0
R1.3
Be supported by a current or past study and/or system simulation testing that addresses each of the following categories (R1.3.1, R1.3.2 etc.), showing system performance following Category A of Table 1 (no contingencies). The specific elements selected (from each of the following categories) shall be acceptable to the associated Regional Reliability Organization(s). Cover critical system conditions and study years as deemed appropriate by the entity performing the study.
Reactive power capacity with adequate reserves and appropriate controls shall be installed in each Area to maintain voltages within normal limits for predisturbance conditions
No
No
TFCP
TPL-001-0
R1.3.1
B4 Sec. 3.0
B4 Sec. 3.0 - It is suggested that a study year of 4 to 6 years from the reporting date is a realistic one, both No from the viewpoint of minimum lead times required for construction, and the ability to alter plans or facilities.
NERC appears to have No left some room for interpretation here with the words study years as deemed appropriate by the entity performing the studies. NPCC has deemed that 4-6 years out is appropriate rather than the 10 years specified by NERC in R1.2
TFCP
TPL-001-0
System Performance Under Normal (No Contingency) Conditions System Performance Under Normal (No Contingency) Conditions System Performance Under Normal (No Contingency) Conditions System Performance Under Normal (No Contingency) Conditions System Performance Under Normal (No Contingency) Conditions System Performance Under Normal (No Contingency) Conditions System Performance Under Normal (No Contingency) Conditions System Performance Under Normal (No Contingency) Conditions System Performance Under Normal (No Contingency) Conditions
R1.3.1
Cover critical system conditions and study years as deemed appropriate by the entity performing the study.
B4 Sec. 4.0
B4 Sec. 4.0 - Each Area is required to present an annual transmission review to TFSS. However, the review No presented by the Area may be one of three types: a Comprehensive (or Full) Review, an Intermediate (or Partial) Review, or an Interim Review. Each Area is required to present an annual transmission review to TFSS. However, the review presented by No the Area may be one of three types: a Comprehensive (or Full) Review, an Intermediate (or Partial) Review, or an Interim Review. It is suggested that a study year of 4 to 6 years from the reporting date is a realistic one, both from the viewpoint of minimum lead times required for construction, and the ability to alter plans or facilities. No
No
TFCP
TPL-001-0
R1.3.2
Be conducted annually unless changes to system conditions do not warrant such analyses. B4 Sec. 4.0
No
TFCP
TPL-001-0
R1.3.3
Be conducted beyond the five-year horizon only as needed to address identified marginal B4 Sec. 3.0 conditions that may have longer lead-time solutions.
No
TFCP
TPL-001-0
R1.3.4
A2 Sec. 2.2
Coordination among and within the Areas of NPCC is essential to the reliability of interconnected operations. No Timely information concerning system conditions shall be transmitted by the NPCC Areas to other Areas or systems as needed to assure reliable operation of the bulk power system. A2 Sec. 2.1 - With due allowance for maintenance and forced outages, design studies will assume power flow No conditions with applicable transfers, load and generation conditions which stress the system. Transfer capability studies will be based on the load and generation conditions expected to exist for the period under study. B4 Sec. 5.1.2b - Include plots of "base case" load flows with all lines in service for the various conditions studied, e.g., peak, off-peak, and heavy transfers. No
No
TFCP
TPL-001-0
R1.3.5
A2 Sec. 2.1
No
TFCP
TPL-001-0
R1.3.5
B4 Sec. 5.1.2b
No
TFCP
TPL-001-0
R1.3.6
Be performed for selected demand levels over the range of forecast system demands.
B4 Sec. 5.1.2b
Include plots of "base case" load flows with all lines in service for the various conditions studied, e.g., peak, off-peak, and heavy transfers.
No
No
TFCP
TPL-001-0
R1.3.7
Demonstrate that system performance meets Table 1 for Category A (no contingencies). A2 Sec. 5.2a
A2 Sec. 5.2a - Reactive power capacity with adequate reserves and appropriate controls shall be installed in each Area to maintain voltages within normal limits for predisturbance conditions.
No
No
TFCP
TPL-001-0
R1.3.7
Demonstrate that system performance meets Table 1 for Category A (no contingencies). A2 Sec. 5.2b
A2 Sec. 5.2b - Line and equipment loadings shall be within normal limits for predisturbance conditions.
No
No
TFCP
Page 77 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
TPL-001-0
System Performance Under Normal (No Contingency) Conditions System Performance Under Normal (No Contingency) Conditions System Performance Under Normal (No Contingency) Conditions System Performance Under Normal (No Contingency) Conditions System Performance Under Normal (No Contingency) Conditions System Performance Under Normal (No Contingency) Conditions System Performance Under Normal (No Contingency) Conditions System Performance Under Normal (No Contingency) Conditions
R1.3.8
B4 Sec. 5.2.2
An Interim Review will consider Changes in Facilities (Existing and Planned) and Forecasted System Conditions Since the Last Comprehensive Review.
No
TFCP
TPL-001-0
R1.3.9
Include Reactive Power resources to ensure that adequate reactive resources are available to meet system performance.
A2 Sec. 5.2a
A2 Sec. 5.2a - Reactive power capacity with adequate reserves and appropriate controls shall be installed in each Area to maintain voltages within normal limits for predisturbance conditions.
No
No
TFCP
TPL-001-0
R1.3.9
Include Reactive Power resources to ensure that adequate reactive resources are available to meet system performance.
B4 Sec. 5.1.2a
B4 Sec. 5.1.2a - Discuss the adequacy of voltage performance and voltage control capability for the planned bulk power transmission system.
No
No
TFCP
TPL-001-0
R1.4
Address any planned upgrades needed to meet the performance requirements of Category B4 Sec. 5.1.2b A.
B4 Sec. 5.1.2b - Discuss the load flows showing the effect of major planned changes on the system.
No
No
TFCP
TPL-001-0
R1.4
Address any planned upgrades needed to meet the performance requirements of Category B4 Sec. 7.0 Part B4 Sec. 7.0 Part 2 - If the results of the Area Review indicates that the Areas planned bulk power A. 2 transmission system is not in conformance with the NPCC Basic Criteria , TFSS will request the Area to develop a plan to achieve conformance with the Criteria. When system simulations indicate an inability of the systems to respond as prescribed in Reliability Standard TPL-001-0 R1, the Planning Authority and Transmission Planner shall each (see R2.1 & R2.2 below for details): Provide a written summary of its plans to achieve the required system performance as described above throughout the planning horizon (see below): B4 Sec. 7.0 Once an Area has presented its Review report to the TFSS, TFSS will review the Areas report and any supporting documentation and (see following sections):
No
No
TFCP
TPL-001-0
R2
No
No
TFCP
TPL-001-0
R2.1
B4 Sec. 7.0 Part Consider whether to accept the report as complete and in full conformance with these Guidelines. If the 1a report is found to be unacceptable, TFSS will indicate to the Area the specific areas of deficiency, and request the Area to address those deficiencies. none none
No
No
TFCP
TPL-001-0
R2.1.1
No
NPCC has no specific requirement for the details of the corrective plan (although broad corrective actions are required as per R2.1 above). NPCC has no specific requirement for the details of the corrective plan (although broad corrective actions are required as per R2.1 above). NPCC has no specific requirement for the details of the corrective plan (although broad corrective actions are required as per R2.1 above).
No
TFCP
TPL-001-0
R2.1.2
none
none
No
No
TFCP
TPL-001-0
R2.1.3
none
none
No
No
TFCP
TPL-001-0
System Performance Under Normal (No Contingency) Conditions System Performance Under Normal (No Contingency) Conditions
R2.2
Review, in subsequent annual assessments, (where sufficient lead time exists), the continuing need for identified system facilities. Detailed implementation plans are not needed The Planning Authority and Transmission Planner shall each document the results of these reliability assessments and corrective plans and shall annually provide these to its respective NERC Regional Reliability Organization(s), as required by the Regional Reliability Organization
B4 Sec. 4.0
Each Area is required to present an annual transmission review to TFSS. However, the review presented by No the Area may be one of three types: a Comprehensive (or Full) Review, an Intermediate (or Partial) Review, or an Interim Review. Each Area is required to present an annual transmission review to TFSS. However, the review presented by No the Area may be one of three types: a Comprehensive (or Full) Review, an Intermediate (or Partial) Review, or an Interim Review.
No
TFCP
TPL-001-0
R3
B4 Sec. 4.0
No
TFCP
Page 78 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
TPL-002-0
System Performance Following Loss of a Single Bulk Electric System Element (Category B),
R1
The Planning Authority and Transmission Planner shall each demonstrate through a valid Refer to R1.1, assessment that its portion of the interconnected transmission system is planned such etc. below that, with all transmission facilities in service and with normal (pre-contingency) operating procedures in effect, the Network can be operated to supply projected customer demands and projected Firm (non- recallable reserved) Transmission Services at all Demand levels over the range of forecast system demands, under the conditions defined in Category B of Table I. To be considered valid, the Planning Authority and Transmission Planner assessments shall (see R1.1, R1.2, etc. below):
No
TFCP
TPL-002-0
System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B),
R1.1
Be made annually
B-4 Section 4.0 Each Area is required to present an annual transmission review to TFSS. However, the review presented by No the Area may be one of three types: A Comprehensive (or Full) Review, an Intermediate (or Partial) Review, or an Interim Review.
No
TFCP
TPL-002-0
R1.2
Be conducted for near-term (years one through five) and longer-term (years six through ten) planning horizons.
It is suggested that a study year of 4 to 6 years from the reporting date is a realistic one, both from the viewpoint of minimum lead times required for construction, and the ability to alter plans or facilities.
No
NPCC only suggests a No desired time frame for the studies. R1.3.4 below conflicts with R1.2 in that it does NOT require studies out to a 10 year planning horizon. NPCC is OK with 6 yrs.
TFCP
TPL-002-0
System Performance Following Loss of a Single Bulk Electric System Element (Category B),
R1.3
Be supported by a current or past study and/or system simulation testing that addresses each of the following categories (R1.3.1, R1.3.2 etc.), showing system performance following Category B of Table 1 (single contingencies). The specific elements selected (from each of the following categories) shall be acceptable to the associated Regional Reliability Organization(s).
Reactive power capacity with adequate reserves and appropriate controls shall be installed in each Area to maintain voltages within normal limits for pre-disturbance conditions, and within applicable emergency limits for the system conditions that exist following the contingencies specified in 5.1
No
No
TFCP
TPL-002-0
System Performance Following Loss of a Single Bulk Electric System Element (Category B),
R1.3.1
Be performed and evaluated only for those Category B contingencies that would produce A2 Sec. 5.1 & the more severe System results or impacts. The rationale for the contingencies selected 6.2 for evaluation shall be available as supporting information. An explanation of why the remaining simulations would produce less severe system results shall be available as supporting information.
A2 Sec. 5.1 & 6.2 - Stability of the bulk power system shall be maintained during and following the most severe of the contingencies stated below, with due regard to reclosing.
No
No
TFCP
TPL-002-0
System Performance Following Loss of a Single Bulk Electric System Element (Category B),
R1.3.1
Be performed and evaluated only for those Category B contingencies that would produce B4 Sec. 5.1.2c B4 Sec. 5.1.2c - Discuss and/or refer to significant studies showing the effect on the system of contingencies No the more severe System results or impacts. The rationale for the contingencies selected as specified in Section 5.1 of the Basic Criteria , entitled "Stability Assessment" and report on the most for evaluation shall be available as supporting information. An explanation of why the severe contingencies remaining simulations would produce less severe system results shall be available as supporting information. Cover critical system conditions and study years as deemed appropriate by the responsible entity B4 Sec. 3.0 B4 Sec. 3.0 - It is suggested that a study year of 4 to 6 years from the reporting date is a realistic one, both No from the viewpoint of minimum lead times required for construction, and the ability to alter plans or facilities.
No
TFCP
TPL-002-0
System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B),
R1.3.2
No
TFCP
TPL-002-0
R1.3.2
Cover critical system conditions and study years as deemed appropriate by the responsible entity
B4 Sec. 4.0
B4 Sec. 4.0 - Each Area is required to present an annual transmission review to TFSS. However, the review No presented by the Area may be one of three types: a Comprehensive (or Full) Review, an Intermediate (or Partial) Review, or an Interim Review.
No
TFCP
TPL-002-0
R1.3.3
Be conducted annually unless changes to system conditions do not warrant such analyses B4 Sec. 4.0
Each Area is required to present an annual transmission review to TFSS. However, the review presented by No the Area may be one of three types: a Comprehensive (or Full) Review, an Intermediate (or Partial) Review, or an Interim Review.
No
TFCP
TPL-002-0
R1.3.4
Be conducted beyond the five-year horizon only as needed to address identified marginal B4 Sec. 3.0 conditions that may have longer lead-time solutions.
It is suggested that a study year of 4 to 6 years from the reporting date is a realistic one, both from the viewpoint of minimum lead times required for construction, and the ability to alter plans or facilities.
No
No
TFCP
Page 79 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
TPL-002-0
System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B),
R1.3.5
A2 Sec. 2.1
A2 Sec. 2.1 - With due allowance for maintenance and forced outages, design studies will assume power flow No conditions with applicable transfers, load and generation conditions which stress the system. Transfer capability studies will be based on the load and generation conditions expected to exist for the period under study. B4 Sec. 5.1.2b - Include plots of "base case" load flows with all lines in service for the various conditions studied, e.g., peak, off-peak, and heavy transfers. No
No
TFCP
TPL-002-0
R1.3.5
B4 Sec. 5.1.2b
No
TFCP
TPL-002-0
R1.3.6
Be performed and evaluated for selected demand levels over the range of forecast system B4 Sec. 5.1.2b demands.
Include plots of "base case" load flows with all lines in service for the various conditions studied, e.g., peak, off-peak, and heavy transfers.
No
No
TFCP
TPL-002-0
R1.3.7
A2 Sec. 5.2
A2 Sec. 5.2 - Reactive power capacity with adequate reserves and appropriate controls shall be installed in each Area to maintain voltages, line and equipment loadings within applicable emergency limits for the system conditions that exist following the contingencies specified in 5.1 .
No
No
TFCP
TPL-002-0
R1.3.8
B4 Sec. 5.2.2
An Interim Review will consider Changes in Facilities (Existing and Planned) and Forecasted System Conditions Since the Last Comprehensive Review.
No
No
TFCP
TPL-002-0
R1.3.9
Include Reactive Power resources to ensure that adequate reactive resources are available to meet system performance.
A2 Sec. 5.2a
A2 Sec. 5.2a - Reactive power capacity with adequate reserves and appropriate controls shall be installed in each Area to maintain voltages within applicable emergency limits for the system conditions that exist following the contingencies specified in 5.1.
No
No
TFCP
TPL-002-0
R1.3.9
Include Reactive Power resources to ensure that adequate reactive resources are available to meet system performance.
B4 Sec. 5.1.2b
B4 Sec. 5.1.2b - Discuss the adequacy of voltage performance and voltage control capability for the planned bulk power transmission system.
No
No
TFCP
TPL-002-0
R1.3.10 Include the effects of existing and planned protection systems, including any backup or redundant systems.
Stability of the bulk power system shall be maintained during and following the most severe of the contingencies stated below. For each of the contingencies below that involves a fault, stability shall be maintained when the simulation is based on fault clearing initiated by the system A protection group, and also shall be maintained when the simulation is based on fault clearing initiated by the system B protection group.
Yes
NPCC is more stringent No in that it requires that both A and B protection systems be capable of maintaining stability.
TFCP
TPL-002-0
System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B),
Sec. 5.1.5a - A Comprehensive Review should review all the existing, new, and modified SPSs included in its transmission plan.
No
No
TFCP
TPL-002-0
5.1.6
Sec. 5.1.6 - For those DCSs whose failure or misoperation may have an inter-Area or interregional effect, discuss and/or refer to appropriate stability studies analyzing the consequences of such failure or misoperation in accordance with the Joint Working Group (JWG)-1 report, "Technical Considerations and Suggested Methodology for the Performance Evaluation of Dynamic Control Systems".
No
No
TFCP
TPL-002-0
R1.3.12 Include the planned (including maintenance) outage of any bulk electric equipment (including protection systems or their components) at those demand levels for which planned (including maintenance) outages are performed.
A2 Sec. 6.0
Scheduled outages of facilities that affect inter-Area reliability shall be coordinated sufficiently in advance of No the outage to permit the affected Areas to maintain reliability. Each Area shall notify adjacent Areas of scheduled or forced outages of any facility on the NPCC Transmission Facilities List and of any other condition which may impact on inter-Area reliability. B4 Sec. 5.1.2b - Discuss the load flows showing the effect of major planned changes on the system. No
No
TFCP
TPL-002-0
R1.4
Address any planned upgrades needed to meet the performance requirements of Category B4 Sec. 5.1.2b B Table I.
No
TFCP
TPL-002-0
R1.4
Address any planned upgrades needed to meet the performance requirements of Category B4 Sec. 7.0 Part B4 Sec. 7.0 Part 2 - If the results of the Area Review indicates that the Areas planned bulk power B Table I. 2 transmission system is not in conformance with the NPCC Basic Criteria , TFSS will request the Area to develop a plan to achieve conformance with the Criteria.
No
No
TFCP
Page 80 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
TPL-002-0
System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B),
R1.5
Requires that stability must be maintained, and flows/voltages be within emergency ratings following the contingencies specified by NPCC that are equivalent to the NERC Category B contingencies.
No
TFCP
TPL-002-0
R2
When system simulations indicate an inability of the systems to respond as prescribed in Reliability Standard TPL-002-0 R1, the Planning Authority and Transmission Planner shall each (see R2.1 & R2.2 below for details):
B4 Sec. 7.0
Once an Area has presented its Review report to the TFSS, TFSS will review the Areas report and any supporting documentation and (see following sections):
No
No
TFCP
TPL-002-0
R2.1
Provide a written summary of its plans to achieve the required system performance as described above throughout the planning horizon (see below):
B4 Sec. 7.0 Part Consider whether to accept the report as complete and in full conformance with these Guidelines. If the 1a report is found to be unacceptable, TFSS will indicate to the Area the specific areas of deficiency, and request the Area to address those deficiencies.
No
No
TFCP
TPL-002-0
R2.1.1
none
none
No
NPCC does not have a No specific requirement for the details of the corrective plan (although broad corrective actions are required as per R2.1 above).
TFCP
TPL-002-0
System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Single Bulk Electric System Element (Category B), System Performance Following Loss of a Two or More Bulk Electric System Element (Category),
R2.1.2
No
TFCP
TPL-002-0
R2.1.3
No
TFCP
TPL-002-0
R2.2
Review, in subsequent annual assessments, (where sufficient lead time exists), the continuing need for identified system facilities. Detailed implementation plans are not needed
B4 Sec. 4.0
Each Area is required to present an annual transmission review to TFSS. However, the review presented by the Area may be one of three types: a Comprehensive (or Full) Review, an Intermediate (or Partial) Review, or an Interim Review.
No
No
TFCP
TPL-002-0
R3
The Planning Authority and Transmission Planner shall each document the results of these reliability assessments and corrective plans and shall annually provide these to its respective NERC Regional Reliability Organization(s), as required by the Regional Reliability Organization
B4 Sec. 4.0
Each Area is required to present an annual transmission review to TFSS. However, the review presented by the Area may be one of three types: a Comprehensive (or Full) Review, an Intermediate (or Partial) Review, or an Interim Review.
No
No
TFCP
TPL-003-0
R1
The PA and TPl shall each demonstrate through a valid assessment that its portion of the See below interconnected transmission system is planned such that, with all transmission facilities in service and with normal (pre-contingency) operating procedures in effect, the Network can be operated to supply projected customer demands and projected Firm (nonrecallable reserved) Transmission Services at all Demand levels over the range of forecast system demands, under the conditions defined in Category C of Table I. The controlled interruption of customer Demand, the planned removal of generators, or the Curtailment of firm power transfers may be necessary to meet this standard. To be considered valid, the PA and Transmission Planner assessments shall (see R1.1, R1.2 etc. below): Be made annually B4 Sec. 4.0
See below
No
No
TFCP
TPL-003-0
System Performance Following Loss of a Two or More Bulk Electric System Element (Category),
R1.1
Each Area is required to present an annual transmission review to TFSS. However, the review.may be Comprehensive (Full), an Intermediate (Partial), or an Interim Review.
No
No
TFCP
Page 81 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
TPL-003-0
System Performance Following Loss of a Two or More Bulk Electric System Element (Category),
R1.2
Be conducted for near-term (years one through five) and longer-term (years six through ten) planning horizons.
It is suggested that a study year of 4 to 6 years from the reporting date is a realistic one, both from the viewpoint of minimum lead times required for construction, and the ability to alter plans or facilities.
NPCC only suggests a No desired time frame for the studies. R1.3.4 below conflicts with R1.2 in that it does NOT require studies out to a 10 year planning horizon. NPCC is OK with 6 yrs.
TFCP
TPL-003-0
System Performance Following Loss of a Two or More Bulk Electric System Element (Category),
R1.3
Be supported by a current or past study and/or system simulation testing that addresses A-2 Sec. 5.0 each of the following categories (R1.3.1, R1.3.2 etc.), showing system performance following Category C of Table 1 (multiple contingencies). The specific elements selected (from each of the following categories) shall be acceptable to the associated Regional Reliability Organization(s).
The portion of the bulk power system in each Area and of each member system shall be designed with No sufficient transmission capability to serve forecasted loads under the conditions noted in Sections 5.1 and 5.2. These criteria will also apply after any critical generator, transmission circuit, transformer, series or shunt compensating device or HVdc pole has already been lost, assuming that the Area generation and power flows are adjusted between outages by the use of ten-minute reserve and where available, phase angle regulator control and HVdc control.
Note: See separate No document at the start of this TPL section which compares the NERC Table 1 contingencies with the NPCC A-2 contingencies. Category C contingencies in NPCC are those described by A2 Sec. 5.1a, b, c, e & f
TFCP
TPL-003-0
System Performance Following Loss of a Two or More Bulk Electric System Element (Category),
R1.3.1
Be performed and evaluated only for those Category C contingencies that would produce A2 Sec. 5.1 & the more severe System results or impacts. The rationale for the contingencies selected 6.2 for evaluation shall be available as supporting information. An explanation of why the remaining simulations would produce less severe system results shall be available as supporting information.
A2 Sec. 5.1 & 6.2 - Stability of the bulk power system shall be maintained during and following the most severe of the contingencies stated below, with due regard to reclosing.
No
No
TFCP
TPL-003-0
System Performance Following Loss of a Two or More Bulk Electric System Element (Category),
R1.3.1
Be performed and evaluated only for those Category C contingencies that would produce B4 Sec. 5.1.2c B4 Sec. 5.1.2c - Discuss and/or refer to significant studies showing the effect on the system of contingencies No the more severe System results or impacts. The rationale for the contingencies selected as specified in Section 5.1 of the Basic Criteria , entitled "Stability Assessment" and report on the most for evaluation shall be available as supporting information. An explanation of why the severe contingencies in the following manner remaining simulations would produce less severe system results shall be available as supporting information. Cover critical system conditions and study years as deemed appropriate by the responsible entity B4 Sec. 3.0 B4 Sec. 3.0 - It is suggested that a study year of 4 to 6 years from the reporting date is a realistic one, both No from the viewpoint of minimum lead times required for construction, and the ability to alter plans or facilities.
No
TFCP
TPL-003-0
System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category),
R1.3.2
No
TFCP
TPL-003-0
R1.3.3
Be conducted annually unless changes to system conditions do not warrant such analyses
B4 Sec. 4.0
Each Area is required to present an annual transmission review to TFSS. However, the review presented by No the Area may be one of three types: a Comprehensive (or Full) Review, an Intermediate (or Partial) Review, or an Interim Review.
No
TFCP
TPL-003-0
R1.3.4
Be conducted beyond the five-year horizon only as needed to address identified marginal conditions that may have longer lead-time solutions.
B4 Sec. 3.0
It is suggested that a study year of 4 to 6 years from the reporting date is a realistic one, both from the viewpoint of minimum lead times required for construction, and the ability to alter plans or facilities.
No
No
TFCP
TPL-003-0
R1.3.5
A2 Sec. 2.1
A2 Sec. 2.1 - With due allowance for maintenance and forced outages, design studies will assume power flow No conditions with applicable transfers, load and generation conditions which stress the system. Transfer capability studies will be based on the load and generation conditions expected to exist for the period under study. B4 Sec. 5.1.2b - Include plots of "base case" load flows with all lines in service for the various conditions studied, e.g., peak, off-peak, and heavy transfers. No
No
TFCP
TPL-003-0
R1.3.5
B4 Sec. 5.1.2b
No
TFCP
TPL-003-0
R1.3.6
Be performed and evaluated for selected demand levels over the range of forecast system B4 Sec. 5.1.2b demands.
Include plots of "base case" load flows with all lines in service for the various conditions studied, e.g., peak, off-peak, and heavy transfers.
No
No
TFCP
Page 82 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
TPL-003-0
System Performance Following Loss of a Two or More Bulk Electric System Element (Category),
R1.3.7
A2 Sec. 5.0
The p A portion of the bulk power system in each Area and of each member system shall be designed with No sufficient transmission capability to serve forecasted loads under the conditions noted in Sections 5.1 and 5.2. These criteria will also apply after any critical generator, transmission circuit, transformer, series or shunt compensating device or HVdc pole has already been lost, assuming that the Area generation and power flows are adjusted between outages by the use of ten-min.reserve and where available, phase angle regulator control and HVdc ctrl., anticipated transfers of pwr from one Area to another, as well as within Areas, shall be cons. in the design of inter-Area and intra-Area transmission facilities. Trans. transfer ..shall be determined in accordance w/Sec. 5.1 & 5.2. An Interim Review will consider Changes in Facilities (Existing and Planned) and Forecasted System Conditions Since the Last Comprehensive Review. No
No
TFCP
TPL-003-0
System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category),
R1.3.8
B4 Sec. 5.2.2
No
TFCP
TPL-003-0
R1.3.9
Include Reactive Power resources to ensure that adequate reactive resources are available to meet system performance.
A2 Sec. 5.2a
A2 Sec. 5.2a - Reactive power capacity with adequate reserves and appropriate controls shall be installed in each Area to maintain voltages within applicable emergency limits for the system conditions that exist following the contingencies specified in 5.1.
No
No
TFCP
TPL-003-0
R1.3.9
Include Reactive Power resources to ensure that adequate reactive resources are available to meet system performance.
B4 Sec. 5.1.2b
B4 Sec. 5.1.2b - Discuss the adequacy of voltage performance and voltage control capability for the planned bulk power transmission system.
No
No
TFCP
TPL-003-0
R1.3.10 Include the effects of existing and planned protection systems, including any backup or redundant systems.
Stability of the bulk power system shall be maintained during and following the most severe of the contingencies stated below. For each of the contingencies below that involves a fault, stability shall be maintained when the simulation is based on fault clearing initiated by the system A protection group, and also shall be maintained when the simulation is based on fault clearing initiated by the system B protection group.
Yes
NPCC is more stringent No in that it requires that both A and B protection systems be capable of maintaining stability.
TFCP
TPL-003-0
System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category),
Sec. 5.1.5a - A Comprehensive Review should review all the existing, new, and modified SPSs included in its transmission plan.
No
No
TFCP
TPL-003-0
5.1.6
Sec. 5.1.6 - For those DCSs whose failure or misoperation may have an inter-Area or interregional effect, discuss and/or refer to appropriate stability studies analyzing the consequences of such failure or misoperation in accordance with the Joint Working Group (JWG)-1 report, "Technical Considerations and Suggested Methodology for the Performance Evaluation of Dynamic Control Systems". Scheduled outages of facilities that affect inter-Area reliability shall be coordinated sufficiently in advance of the outage to permit the affected Areas to maintain reliability. Each Area shall notify adjacent Areas of scheduled or forced outages of any facility on the NPCC Transmission Facilities List and of any other condition which may impact on inter-Area reliability. B4 Sec. 5.1.2b - Discuss the load flows showing the effect of major planned changes on the system.
No
No
TFCP
TPL-003-0
R1.3.12 Include the planned (including maintenance) outage of any bulk electric equipment (including protection systems or their components) at those demand levels for which planned (including maintenance) outages are performed.
A2 Sec. 6.0
No
No
TFCP
TPL-003-0
R1.4
Address any planned upgrades needed to meet the performance requirements of Category C.
B4 Sec. 5.1.2b
No
No
TFCP
TPL-003-0
R1.4
Address any planned upgrades needed to meet the performance requirements of Category C.
B4 Sec. 7.0 Part B4 Sec. 7.0 Part 2 - If the results of the Area Review indicates that the Areas planned bulk power 2 transmission system is not in conformance with the NPCC Basic Criteria , TFSS will request the Area to develop a plan to achieve conformance with the Criteria.
No
No
TFCP
TPL-003-0
R1.5
Requires that stability must be maintained, and flows/voltages be within emergency ratings following the contingencies specified by NPCC that are equivalent to the NERC Category C contingencies.
No
No
TFCP
TPL-003-0
R2
When system simulations indicate an inability of the systems to respond as prescribed in Reliability Standard TPL-003-0 R1, the Planning Authority and Transmission Planner shall each (see R2.1 & R2.2 below for details):
B4 Sec. 7.0
Once an Area has presented its Review report to the TFSS, TFSS will review the Areas report and any supporting documentation and (see following sections):
No
No
TFCP
Page 83 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
TPL-003-0
System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category),
R2.1
Provide a written summary of its plans to achieve the required system performance B4 Sec. 7.0 Part Part 1a - Consider whether to accept the report as complete and in full conformance with these Guidelines. If No 1a as described above throughout the planning horizon (see below): the report is found to be unacceptable, TFSS will indicate to the Area the specific areas of deficiency, and request the Area to address those deficiencies.
No
TFCP
TPL-003-0
R2.1
Provide a written summary of its plans to achieve the required system performance B4 Sec. 7.0 Part Part 2 - If the results of the Area Review indicates that the Areas planned bulk power transmission system is No 2 as described above throughout the planning horizon (see below): not in conformance with the NPCC Basic Criteria , TFSS will request the Area to develop a plan to achieve conformance with the Criteria
No
TFCP
TPL-003-0
R2.1.1
none
none
No
NPCC does not have a No specific requirement for the details of the corrective plan (although broad corrective actions are required as per R2.1 above).
TFCP
TPL-003-0
System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Loss of a Two or More Bulk Electric System Element (Category),
R2.1.2
No
TFCP
TPL-003-0
R2.1.3
No
TFCP
TPL-003-0
R2.2
Review, in subsequent annual assessments, (where sufficient lead time exists), the continuing need for identified system facilities. Detailed implementation plans are not needed
B4 Sec. 4.0
Each Area is required to present an annual transmission review to TFSS. However, the review presented by the Area may be one of three types: a Comprehensive (or Full) Review, an Intermediate (or Partial) Review, or an Interim Review.
No
No
TFCP
TPL-003-0
R3
The Planning Authority and Transmission Planner shall each document the results of these reliability assessments and corrective plans and shall annually provide these to its respective NERC Regional Reliability Organization(s) , as required by the Regional Reliability Organization none
B4 Sec. 4.0
Each Area is required to present an annual transmission review to TFSS . However, the review presented by the Area may be one of three types: a Comprehensive (or Full) Review, an Intermediate (or Partial) Review, or an Interim Review.
No
No
TFCP
TPL-003-0
R4
B4 Sec. 5.1.7
5.1.7 - Review any exclusions granted under the NPCC Guidelines for Requesting Exclusions to Sections Yes 5.1(b) and 6.1(b) of the NPCC Basic Criteria for Design and Operation of Interconnected Power Systems (Document B-10). A Comprehensive Review should address all exclusions, but an Intermediate Review may focus on just those exclusions that may have been impacted by system changes since they were last reviewed.
NPCC is more stringent No in having a mechanism for reviewing cases where exclusions from having to comply with the Basic Design Criteria are requested by a member organization.
TFCP
TPL-003-0
System Performance Following Loss of a Two or More Bulk Electric System Element (Category), System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D), R1
none
B10
B10 Guidelines for Requesting Exclusions to Sections 5.1 (b) and 6.1 (b) of the NPCC Basic Criteria for Design and Operation of Interconnected Power Systems
Yes
No
TFCP
TPL-004-0
The Planning Authority and Transmission Planner shall each demonstrate through a valid A2 Sec. 7.0 assessment that its portion of the interconnected transmission system is evaluated for the risks and consequences of a number of each of the extreme contingencies that are listed under Category D of Table I. To be valid, the Planning Authoritys and Transmission Planners assessment shall (see R1.1, etc. below for the details):
Extreme contingency assessment recognizes that the bulk power system can be subjected to events which Yes exceed, in severity, the contingencies listed in Section 5.1. One of the objectives of extreme contingency assessment is to determine, through planning studies, the effects of extreme contingencies on system performance. This is done in order to obtain an indication of system strength, or to determine the extent of a widespread system disturbance, even though extreme contingencies do have low probabilities of occurrence. The specified extreme contingencies listed below are intended to serve as a means of identifying some of those particular situations that could result in widespread bulk power system shutdown.
NPCC is more stringent No as per the details in the separate document comparing NERC Table I to NPCC A2 Sections 5.1, 6.1, 6.2 and 7.0
TFCP
Page 84 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
TPL-004-0
System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D), System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D),
R1.1
Be made annually
B4 Section 4.0
No
TFCP
TPL-004-0
R1.2
B4, Sec. 3.0 - It is suggested that a study year of 4 to 6 years from the reporting date is a realistic one, both No from the viewpoint of minimum lead times required for construction, and the ability to alter plans or facilities.
NPCC only suggests a No desired time frame for the studies. Also, NPCC does not specifically say to study years one through five. However, requirement B4 Sec. 4.0 calls for annual updates of previous 4-6 year reviews so, by default, these reviews should catch any significant changes that need to be studied in more detail.
TFCP
TPL-004-0
System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D), System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D),
R1.2
B4 Section 4.0
B4, Sec. 4.0 - Each Area is required to present an annual transmission review to TFSS.
No
No
TFCP
TPL-004-0
R1.3
Be supported by a current or past study and/or system simulation testing that addresses A2 Sec. 7.0 each of the following categories (R1.3.1, R1.3.2 etc.), showing system performance following Category D of Table 1 (multiple contingencies). The specific elements selected (from each of the following categories) shall be acceptable to the associated Regional Reliability Organization(s).
The specified extreme contingencies listed below are intended to serve as a means of identifying some of those particular situations that could result in widespread bulk power system shutdown.Assessment of the extreme contingencies listed below should examine post contingency steady state conditions, as well as stability, overload cascading and voltage collapse.
Yes
Note: The separate No document comparing NERC Table I Category D contingencies with NPCC A2 extreme contingencies (listed in Sec. 7.0) shows that NPCC is more stringent by requiring a study of loss of fuel delivery to multiple plants.
TFCP
TPL-004-0
System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D), System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D), System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D), System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D),
R1.3.1
Be performed and evaluated only for those Category D contingencies that would produce the more severe system results or impacts. The rationale for the contingencies selected for evaluation shall be available as supporting information. An explanation of why the remaining simulations would produce less severe system results shall be available as supporting information. Be performed and evaluated only for those Category D contingencies that would produce the more severe system results or impacts. The rationale for the contingencies selected for evaluation shall be available as supporting information. An explanation of why the remaining simulations would produce less severe system results shall be available as supporting information. Be performed and evaluated only for those Category D contingencies that would produce the more severe system results or impacts. The rationale for the contingencies selected for evaluation shall be available as supporting information. An explanation of why the remaining simulations would produce less severe system results shall be available as supporting information. Cover critical system conditions and study years as deemed appropriate by the responsible entity
B4 Sec. 5.1.3a 5.1.3a) Discuss the scope of the analyses. The analyses conducted for a Comprehensive Review should be thorough, but an Intermediate Review may focus on specific areas of the system, specific system conditions, or a more limited set of critical contingencies.
No
No
TFCP
TPL-004-0
R1.3.1
B4 Sec. 5.1.3b b) Discuss and/or refer to significant load flow studies showing the base case and the post fault conditions for No the contingencies as specified in Section 7.0 of the Basic Criteria , entitled "Extreme Contingency Assessment". Report on the most severe contingencies tested
No
TFCP
TPL-004-0
R1.3.1
B4 Sec. 5.1.3c c) Discuss and/or refer to significant stability studies showing the effect on the system of contingencies. Report on the most severe contingencies tested
No
No
TFCP
TPL-004-0
R1.3.2
B4 Sec. 3.0
B4 Sec. 3.0 - It is suggested that a study year of 4 to 6 years from the reporting date is a realistic one, both No from the viewpoint of minimum lead times required for construction, and the ability to alter plans or facilities.
No
TFCP
Page 85 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
TPL-004-0
System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D), System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D), System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D), System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D), System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D), System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D),
R1.3.3
Be conducted annually unless changes to system conditions do not warrant such analyses B4 Sec. 4.0
Each Area is required to present an annual transmission review to TFSS. However, the review presented by No the Area may be one of three types: a Comprehensive (or Full) Review, an Intermediate (or Partial) Review, or an Interim Review.
No
TFCP
TPL-004-0
R1.3.4
A2 Sec. 7.0
Assessment of the extreme contingencies listed below should examine post contingency steady state conditions, as well as stability, overload cascading and voltage collapse. Pre-contingency load flows chosen for analysis should reflect reasonable power transfer conditions within Areas, or from Area to Area.
No
No
TFCP
TPL-004-0
R1.3.5
B4 Sec. 5.2.2.
Interim reviews are to include Changes in Facilities (Existing and Planned) and Forecasted System Conditions Since the Last Comprehensive Review
No
No
TFCP
TPL-004-0
R1.3.6
Include Reactive Power resources to ensure that adequate reactive resources are available to meet system performance.
A2 Sec. 5.2a
A2 Sec. 5.2a - Reactive power capacity with adequate reserves and appropriate controls shall be installed in each Area to maintain voltages within applicable emergency limits for the system conditions that exist following the contingencies specified in 5.1.
No
No
TFCP
TPL-004-0
R1.3.6
Include Reactive Power resources to ensure that adequate reactive resources are available to meet system performance.
B4 Sec. 5.1.2b
B4 Sec. 5.1.2b - Discuss the adequacy of voltage performance and voltage control capability for the planned bulk power transmission system.
No
No
TFCP
TPL-004-0
R1.3.7
Include the effects of existing and planned protection systems, including any backup or redundant systems.
Stability of the bulk power system shall be maintained during and following the most severe of the contingencies stated below. For each of the contingencies below that involves a fault, stability shall be maintained when the simulation is based on fault clearing initiated by the system A protection group, and also shall be maintained when the simulation is based on fault clearing initiated by the system B protection group.
Yes
NPCC is more stringent No in that it requires that both A and B protection systems be capable of maintaining stability.
TFCP
TPL-004-0
System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D), System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D), System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D), System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D),
R1.3.7
Sec. 5.1.5a - A Comprehensive Review should review all the existing, new, and modified SPSs included in its transmission plan.
No
No
TFCP
TPL-004-0
R1.3.8
5.1.6
Sec. 5.1.6 - For those DCSs whose failure or misoperation may have an inter-Area or interregional effect, discuss and/or refer to appropriate stability studies analyzing the consequences of such failure or misoperation in accordance with the Joint Working Group (JWG)-1 report, "Technical Considerations and Suggested Methodology for the Performance Evaluation of Dynamic Control Systems".
No
TFCP
TPL-004-0
R1.3.9
Include the planned (including maintenance) outage of any bulk electric equipment (including protection systems or their components) at those demand levels for which planned (including maintenance) outages are performed.
A2 Sec. 6.0
Scheduled outages of facilities that affect inter-Area reliability shall be coordinated sufficiently in advance of No the outage to permit the affected Areas to maintain reliability. Each Area shall notify adjacent Areas of scheduled or forced outages of any facility on the NPCC Transmission Facilities List and of any other condition which may impact on inter-Area reliability.
No
TFCP
TPL-004-0
R1.4
A2 Sec. 7.0
The specified extreme contingencies listed below are intended to serve as a means of identifying some of those particular situations that could result in widespread bulk power system shutdown. Assessment of the extreme contingencies listed below should examine post contingency steady state conditions, as well as stability, overload cascading and voltage collapse.
Yes
NERC Category D No contingencies are covered by NPCC A2 contingencies 6.1 b & e, 7.0 a, b, c, d, e, f, g & h. Contingency 7.0 i (loss of fuel delivery to multiple plants) is more stringent because it is not required by NERC
TFCP
Page 86 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Comment RRO Requirement? Task Force?
TPL-004-0
System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Element (Category D), Regional and Interregional Self-Assessment Reliability Reports
R2
The Planning Authority and Transmission Planner shall each document the results of these reliability assessments and corrective plans and shall annually provide these to its respective NERC Regional Reliability Organization(s), as required by the Regional Reliability Organization
B4 Sec. 4.0
Each Area is required to present an annual transmission review to TFSS. However, the review presented by No the Area may be one of three types: a Comprehensive (or Full) Review, an Intermediate (or Partial) Review, or an Interim Review.
No
TFCP
TPL-005-0
R1
Each Regional Reliability Organization shall annually conduct reliability assessments of its respective existing and planned Regional Bulk Electric System (generation and transmission facilities) for (see R1.1, etc. below):
A2 Sec. 1.0
It is the responsibility of each Area to ascertain that its portion of the bulk power system is designed and operated in conformance with these criteria. The Council provides a forum for coordinating the design and operations of its five Areas. Through its committees and task forces, the Council shall conduct regional and interregional studies, and assess and monitor Area studies and operations to assure conformance to the criteria.
No
Yes
TFCP
TPL-005-0
Regional and Interregional Self-Assessment Reliability Reports Regional and Interregional Self-Assessment Reliability Reports Regional and Interregional Self-Assessment Reliability Reports Regional and Interregional Self-Assessment Reliability Reports Regional and Interregional Self-Assessment Reliability Reports Regional and Interregional Self-Assessment Reliability Reports Regional and Interregional Self-Assessment Reliability Reports
R1.1
B4 Sec. 4.0 4.0 - Each Area is required to present an annual transmission review to TFSS. However, the review Working presented by the Area may be one of three types: a Comprehensive (or Full) Review, an Intermediate (or Groups CP-8 & Partial) Review, or an Interim Review and only covers a future year. CO-12 none none
No
Yes
TFCP
TPL-005-0
R1.1.1
Winter
No
Yes
TFCP
TPL-005-0
R1.1.2
Summer
none
none
No
Yes
TFCP
TPL-005-0
R1.1.3
none
None
No
Yes
TFCP
TPL-005-0
R1.2
Near-term planning horizons (years one through five). Detailed assessments shall be conducted.
none
None
No
NRAP calls for TFSS to Yes do this every 3 years via WG SS-38 through its Scope NRAP calls for TFSS to Yes do this every 3 years via WG SS-38 through its Scope The present MEN Yes (MAAC-ECAR-NPCC) studies may be changed to include MAACReliability First-NPCC, depending on the outcome of changes in the mid-west.
TFCP
TPL-005-0
R1.3
Longer-term planning horizons (years six through ten). Assessment shall focus on the analysis of trends in resources and transmission Adequacy, other industry trends and developments, and reliability concerns.
none
None
No
TFCP
TPL-005-0
R1.4
Inter-Regional reliability assessments to demonstrate that the performance of these none systems is in compliance with NERC Reliability Standards TPL-001-0, TPL-002-0, TPL003-0, TPL-004-0 and respective Regional transmission and generation criteria. These assessments shall also identify key reliability issues and the risks and uncertainties affecting Adequacy and Security.
None
No
TFCP
TPL-005-0
R2
The Regional Reliability Organization shall provide its Regional and Inter-Regional seasonal, near-term, and longer-term reliability assessments to NERC on an annual basis.
none
None
No
SS-37 feeds model Yes information to NERC Multiregional Modeling Working Group. CP-8 Resource and Adequacy Reviews are available.
TFCP
TPL-005-0
Regional and Interregional Self-Assessment Reliability Reports Regional and Interregional Self-Assessment Reliability Reports Regional and Interregional Self-Assessment Reliability Reports
R3
The RRO shall perform special reliability assessments as requested by NERC or the NERC Board of Trustees under their specific directions and criteria. Such assessments may include, but are not limited to: Security Assessments
none
None
No
NPCC meets this Requirement on an as needed/requested basis. NPCC meets this Requirement on an as needed/requested basis. NPCC meets this Requirement on an as needed/requested basis.
Yes
TFCP
TPL-005-0
R3.1
none
None
No
Yes
TFCP
TPL-005-0
R3.2
Operational Assessments
none
None
No
Yes
TFCP
Page 87 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
TPL-005-0
Regional and Interregional Self-Assessment Reliability Reports Regional and Interregional Self-Assessment Reliability Reports Regional and Interregional Self-Assessment Reliability Reports Regional and Interregional Self-Assessment Reliability Reports Data from the Regional Reliability Organization Needed to Assess Reliability
R3.3
none
None
NPCC meets this Requirement on an as needed/requested basis. NPCC meets this Requirement on an as needed/requested basis. NPCC meets this Requirement on an as needed/requested basis. NPCC meets this Requirement on an as needed/requested basis. NPCC submits data through EIA 411 and 860 collection efforts yearly and to the NERC Reliability Assessment Subcommittee annually
Yes
TFCP
TPL-005-0
R3.4
none
None
No
Yes
TFCP
TPL-005-0
R3.5
none
None
No
Yes
TFCP
TPL-005-0
R3.6
Reliability impacts of new or proposed legislation that affects, has affected, or has the potential to affect the Adequacy of the interconnected BES in North America.
none
None
No
Yes
TFCP
TPL-006-0
R1
Each Regional Reliability Organization shall provide, as requested (seasonally, annually, none or as otherwise specified) by NERC, system data, including past, existing, and future facility and Bulk Electric System data, reports, and system performance information, necessary to assess reliability and compliance with the NERC Reliability Standards and the respective Regional planning criteria. The facility and Bulk Electric System data, reports, and system performance information shall include, but not be limited to, one or more of the following types of information as outlined below:
None
No
Yes
TFCP
TPL-006-0
R1.1
Electric Demand and Net Energy for Load (actual and projected demands and Net Energy for Load, forecast methodologies, forecast assumptions and uncertainties, and treatment of Demand-Side Management.)
none
None
No
NPCC submits data through EIA 411 and 860 collection efforts yearly and to the NERC Reliability Assessment Subcommittee annually
Yes
TFCP
TPL-006-0
Data from the Regional Reliability Organization Needed to Assess Reliability Data from the Regional Reliability Organization Needed to Assess Reliability Data from the Regional Reliability Organization Needed to Assess Reliability Data from the Regional Reliability Organization Needed to Assess Reliability Data from the Regional Reliability Organization Needed to Assess Reliability Data from the Regional Reliability Organization Needed to Assess Reliability 1200 Cyber Security Policy 1201 Cyber Security Policy
R1.2
Resource Adequacy and supporting information (Regional assessment reports, existing and planned resource data, resource availability and characteristics, and fuel types and requirements.) Demand-Side resources and their characteristics (program ratings, effects on annual system loads and load shapes, contractual arrangements, and program durations.)
none
None
No
Yes
TFCP
TPL-006-0
R1.3
none
None
No
Yes
TFCP
TPL-006-0
R1.4
Supply-side resources and their characteristics (existing and planned generator units, Ratings, performance characteristics, fuel types and availability, and real and reactive capabilities.)
none
None
No
Yes
TFCP
TPL-006-0
R1.5
Transmission system and supporting information (thermal, voltage, and Stability Limits, none contingency analyses, system restoration, system modeling and data requirements, and protection systems.) System operations and supporting information (extreme weather impacts, Interchange Transactions, and Congestion impacts on the reliability of the interconnected Bulk Electric Systems.) Environmental and regulatory issues and impacts (air and water quality issues, and impacts of existing, new, and proposed regulations and legislation. none
None
No
Yes
TFCP
TPL-006-0
R1.6
None
No
Yes
TFCP
TPL-006-0
R1.7
none
None
No
Yes
TFCP
Retire in June 2006 R1.1 The entity performing the reliability authority, balancing authority, interchange authority, transmission service provider, transmission operator, generator, or load-serving entity function shall create and maintain a cyber security policy for implementation of this Standard. NPCC Regional Identical to R1.1 Reliability Plan (August, 2005) RRP Sec. 8.1 No Retire in June 2006
TFIST TFIST
Page 88 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
R1.2 The responsible entity shall assign a member of senior management with responsibility for leading and managing the entitys cyber security program. This person must authorize any deviation or exception from the requirements of this Standard. Justification for any such deviation or exemption must be documented.
none
none
TFIST
R1 The entity performing the reliability authority, balancing authority, interchange authority, transmission service provider, transmission operator, generator, or load-serving entity function shall identify its critical cyber assets.
Identical to R1
No
TFIST
R1 The entity performing the reliability authority, balancing authority, interchange authority, transmission service provider, transmission operator, generator, or load-serving entity function shall identify its electronic security perimeter(s). R1 The entity performing the reliability authority, balancing authority, interchange authority, transmission service provider, transmission operator, generator, or load-serving entity function shall identify and implement electronic access controls for access to critical cyber assets within the electronic security perimeter.
Identical to R1
No
TFIST
Identical to R1
No
TFIST
R1
R1
1207 Personnel
R1
R1
R1
R1
1211 Training
R1
The entity performing the reliability authority, balancing authority, interchange authority, RRP Sec. 8.5.1 transmission service provider, transmission operator, generator, or load-serving entity function shall identify its physical security perimeter(s) for the protection of critical cyber assets. RRP Sec. 8.5.3 The entity performing the reliability authority, balancing authority, interchange authority, transmission service provider, transmission operator, generator, or load-serving entity function shall identify and implement physical access controls for access to critical cyber assets within the physical security perimeter(s). RRP Sec. 8.5.3 The entity performing the reliability authority, balancing authority, interchange authority, transmission service provider, transmission operator, generator, or load-serving entity function shall identify all personnel, including contractors and service vendors, granted electronic or physical access to critical cyber assets. The entity performing the reliability authority, balancing authority, interchange authority, RRP Sec. 8.5.4 transmission service provider, transmission operator, generator, or load-serving entity function shall monitor physical access to critical cyber assets 24 hours a day, 7 days a week. RRP Sec. 8.5.5 The entity performing the reliability authority, BA, interchange authority, TSP, TOP, generator, or LSE function shall monitor electronic access to critical cyber assets 24 hours a day, 7 days a week. RRP Sec. 8.6 The entity performing the reliability authority, BA, interchange authority, TSP, TOP, generator, or LSE function shall protect information associated with critical cyber assets and the policies and practices used to keep them secure. RRP Sec. 8.6.1 The entity performing the reliability authority, BA, interchange authority, TSP, TOP, generator, or LSE function shall train personnel commensurate with their access to critical cyber assets. The training shall address, at a minimum: the cyber security policy, physical and electronic access controls to critical cyber assets, the release of critical cyber asset information, potential threat incident reporting, and action plans and procedures to recover or re-establish critical cyber assets following a cyber security incident. Training shall be conducted upon initial employment and reviewed annually.
Identical to R1
No
TFIST
Identical to R1
No
TFIST
Identical to R1
No
TFIST
Identical to R1
No
TFIST
Identical to R1
No
TFIST
Identical to R1
No
TFIST
Identical to R1
No
TFIST
R1 The entity performing the reliability authority, BA, interchange authority, TSP, TOP, generator, or LSE function shall establish systems management policies and procedures for configuring and securing critical cyber assets. At a minimum, these policies and procedures shall address: (a list of 11 specific Requirements follows including passwords, firewalls, un-used ports, anti-virus software, etc.).
RRP Sec. 8.6.2 Identical to R1 except no specific mention is made of the 11 detailed items.
No
NPCC makes no mention of the 11 specific subRequirements of this Standard- Retire in June 2006 Retire in June 2006
TFIST
R1 The entity performing the reliability authority, BA, interchange authority, TSP, TOP, generator, or LSE function shall establish test procedures and acceptance Criteria to ensure that critical cyber assets installed or modified comply with the security requirements in this Standard. Test procedures shall require that testing and acceptance be conducted in an isolated test environment.
No
TFIST
R1 The entity performing the reliability authority, BA, interchange authority, TSP, TOP, generator, or LSE function shall define electronic incident response actions, including roles and responsibilities assigned by individual or job function.
No
TFIST
Page 89 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) No Comment RRO Requirement? Task Force?
R1 The entity performing the reliability authority, BA, interchange authority, TSP, TOP, generator, or LSE function shall define physical incident response actions, including roles and responsibilities assigned by individual or job function. R1 The entity performing the reliability authority, BA, interchange authority, TSP, TOP, generator, or LSE function shall create action plans and procedures to recover or reestablish critical cyber assets following a cyber security incident. Each responsible entity shall exercise these plans at least annually. The plans and procedures shall define roles and responsibilities by individual or job function. Each Transmission Operator, individually and jointly with other Transmission Operators, shall ensure that formal policies and procedures are developed, maintained, and implemented for monitoring and controlling voltage levels and MVAR flows within their individual areas and with the areas of neighboring Transmission Operators.
TFIST
Identical to R1
No
TFIST
VAR-001-0
R1
NPCC Regional Adjacent Reliability Coordinator Areas are required to be familiar with each others voltage criteria and Reliability Plan procedures and mutually agree upon procedures for inter-Reliability Coordinator Area voltage control. (August, 2005) RRP Sec. 4.6.6
No
No
TFCP
VAR-001-0
R2
Each Transmission Operator shall acquire sufficient reactive resources within its area to A2 Sec. 6.1 protect the voltage levels under normal and Contingency conditions. This includes the Transmission Operators share of the reactive requirements of interconnecting transmission circuits. Each Purchasing-Selling Entity shall arrange for (self-provide or purchase) reactive resources to satisfy its reactive requirements identified by its Transmission Service Provider. Refer to R2 above
Reactive power resources shall be maintained in each Area in order to maintain voltages within normal limits No for predisturb. conditions, and within applicable emerg. limits for the sys. conds. that exist following the cont. specified in the foregoing. Adjoining Areas shall mutually agree upon proc. of inter-Area voltage control. Refer to R2 above No NPCC Areas have Market Rules requiring purchase of sufficient Reactive Reserves
No
TFCP
VAR-001-0
R3
No
TFCP
VAR-001-0
R4
The Transmission Operator shall know the status of all transmission reactive power resources, including the status of voltage regulators and power system stabilizers.
The Reliability Coordinator shall continuously be aware of operating conditions within its RC Areaincluding: Current status of BES including AVRs and SPS schemes Reactive Reserves the RC is required to monitor it Areas parameters to ensure that sufficient reactive resources are available to maintain voltages within normal limits for pre-disturbance conditions and within emergency limits following contingencies
No
NPCC RRP does not No specifically mention that the Transmission Operators must also do this. No
TFCP
VAR-001-0
R5
The Transmission Operator shall be able to operate or direct the operation of devices necessary to regulate transmission voltage and reactive flow. Each Transmission Operator shall operate or direct the operation of capacitive and inductive reactive resources within its area including reactive generation scheduling; transmission line and reactive resource switching; and, if necessary, load shedding to maintain system and Interconnection voltages within established limits. Each Transmission Operator shall maintain reactive resources to support its voltage under first Contingency conditions.
B3 Sec. 3.1.1
VAR-001-0
R6
Ea Each Area shall provide for the supply and control of its reactive regulation requirements, including reactive reserve so that applicable emergency voltage levels can be maintained following NPPC Normal Criteria contingencies. B3 Sec. 3.1.1 & 3.1.1 - Each Area shall provide for the supply and control of its reactive regulation requirements, including 3.2.1 reactive reserve so that applicable emergency voltage levels can be maintained following NPPC Normal Criteria contingencies. 3.2.1 If the BPS voltage is rapidly decaying, the Area causing the decay shall immediately implement all possible action, including the shedding of firm load, to correct the problem. A2 Sec. 6.1 Reactive power resources shall be maintained in each Area in order to maintain voltages within normal limits for predisturbance conditions, and within applicable emergency limits for the system conditions that exist following the contingencies specified in the foregoing. none
No
TFCP
No
No
TFCP
VAR-001-0
R7
No
No
TFCP
VAR-001-0
R7.1
Each Transmission Operator shall disperse and locate the reactive resources so that the resources can be applied effectively and quickly when Contingencies occur.
none
No
No
TFCP
VAR-001-0
R8
Each Transmission Operator shall correct IROL or SOL violations resulting from RRP Sec. 4.5.4 4.5.4 For emergencies and near emergency situations that involve or affect the BES or when time is of No reactive resource deficiencies (IROL violations must be corrected within 30 minutes) & 4.6.3 essence in recognition, prevention, mitigation or resolution of the emergency, RC are required to use the and complete the required IROL or SOL violation reporting . NERC Hotline as indicated in IRO-005-0, R7 Reliability Coordination Current Day Operations. 4.6.3 Following a contingency that results in a SOL or IROL violation, NPCC RCs are required to direct their TOP, GOP and BA to return the transmission system to within SOL or IROL as soon as possible and within 30 minutes. Each Generator Operator shall provide information to its TOP on the status of all generation reactive power resources, including the status of voltage regulators and power system stabilizers. When a generators voltage regulator is out of service, the Generator Operator shall maintain the generator field excitation at a level to maintain Interconnection and generator stability. The Transmission Operator shall direct corrective action, including load reduction, necessary to prevent voltage collapse when reactive resources are insufficient. none None No
No
TFCP
VAR-001-0
Voltage and Reactive Control Voltage and Reactive Control Voltage and Reactive Control
R9
No
TFCP
VAR-001-0
R9.1
none
None
No
No
TFCP
VAR-001-0
R10
B3 Sec. 3.2.1 & 3.2.1 - If the BPS voltage is rapidly decaying, the Area causing the decay shall immediately implement all No 3.2.2 possible action, including the shedding of firm load, to correct the problem. 3.2.2 When an Area anticipates or is experiencing an abnormal, but stable, or gradually changing BPS voltage condition, it shall implement steps to correct the situation (including shedding of firm load if necessary).
No
TFCP
Page 90 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Yes Comment RRO Requirement? Task Force?
EOP-001-0
R8
None
C15
Procedures for Solar Magnetic Disturbances Which Affect Electric Power Systems - This document is the NPCC operational guide on SMD (or GIC) and their possible effects on power systems, including recommended operating procedures to mitigate their impacts on the BPS
NPCC is more stringent because there is no equivalent NERC Requirement (although NERC has a Geomagnetic Disturbance Reference Document dated Sept. 14, 2005
TFCO
EOP-004-0
Disturbance Reporting
R3.4
If, in the judgment of the Regional Reliability Organization, after consultation with the B13 Sec. 2.2.2, Reliability Coordinator, Balancing Authority, Transmission Operator, Generator Operator, or Load Serving Entity in which a disturbance occurred, a final report is required, the affected Reliability Coordinator, Balancing Authority, Transmission Operator, Generator Operator, or Load Serving Entity shall prepare this report within 60 days. As a minimum, the final report shall have a discussion of the events and its cause, the conclusions reached, and recommendations to prevent recurrence of this type of event. The report shall be subject to Regional Reliability Organization approval.
2.2.2 - The TFCO Chairman may convene a meeting of the Task Force as soon as necessary upon receipt of the preliminary report(s) and, if an interim report is prepared, the TFCO Chairman will arrange for the forwarding of a summary interim report to the Reliability Coordinating Committee (RCC) within 1 day of receiving the interim report.
Yes
NPCC is more stringent in requiring the final report within 30 days instead of 60 days.
TFCO
EOP-004-0
Disturbance Reporting
R3.4
If, in the judgment of the Regional Reliability Organization, after consultation with the B13 Sec. 2.2.3 Reliability Coordinator, Balancing Authority, Transmission Operator, Generator Operator, or Load Serving Entity in which a disturbance occurred, a final report is required, the affected Reliability Coordinator, Balancing Authority, Transmission Operator, Generator Operator, or Load Serving Entity shall prepare this report within 60 days. As a minimum, the final report shall have a discussion of the events and its cause, the conclusions reached, and recommendations to prevent recurrence of this type of event. The report shall be subject to Regional Reliability Organization approval.
2.2.3 - The TFCO will review the written report with emphasis on inter-Area implications, and will, if deemed necessary, convene an ad hoc TFCO Disturbance Analysis Working Group (DAWG). The ad hoc TFCO DAWG will advise the TFCO of its findings within 30 days of the formation of the Working Group, including lessons to be learned from the incident and recommendations for appropriate actions.
TFCO
FAC-004-0
R1.1.4
The methodology(ies) used to determine equipment and Facility Rating of the items listed for both normal and emergency conditions (see R1.1.1, R1.1.2, etc. below): Terminal equipment (e.g., switches, breakers, current transformers, etc).
Yes
NPCC is more stringent by including breakers, CTs etc. as part of its Line or Transformer rating assessments. NERC does not mention rating a Bus at all
TFSS
IRO-002-0
Each Reliability Coordinator or its Transmission Operators and Balancing RRP Sec. 6.3 Authorities shall provide, or arrange provisions for, data exchange to other Reliability Coordinators or Transmission Operators and Balancing Authorities via a secure network.
Identical to R3 except NPCC added or its Transmission Operators and Balancing Authorities in the opening Yes line.
TFCO
IRO-005-0
R17
When an IROL or SOL is exceeded, the Reliability Coordinator shall evaluate the local RRP Sec. 4.6.3 and wide-area impacts, both real-time and post-contingency, and determine if the actions being taken are appropriate and sufficient to return the system to within IROL in thirty minutes. If the actions being taken are not appropriate or sufficient, the Reliability Coordinator shall direct the Transmission Operator, Balancing Authority, Generator Operator, or Load-Serving Entity to return the system to within IROL or SOL.
When an SOL or IROL violation is imminent, RCs must be aware that TLR procedures may not be able to Yes address the violation in a timely fashion. In such circumstances the RC have the authority and obligation to immediately direct their TOP, Generation Operators and BA to re-dispatch generation, reconfigure transmission, manage interchange transactions or reduce system demand which may include shedding of firm load. These actions shall be used in conjunction with the TLR procedure to restore the system to normal state. The RC shall coordinate these emergency control actions with other RC as needed. These actions are described in NPCC Documents A-03 and C-20.
NPCC criteria is more stringent in that it clarifies that the TLR procedure is sometimes not the appropriate tool to use when dealing with SOL or IROL situations.
TFCO
MOD-014-0
R3
none
A2 Sec. 3.0
Each Areas probability (or risk) of disconnecting any firm load due to resource deficiencies shall be, on Yes average, not more than once in ten years. Compliance with this criteria shall be evaluated probabilistically, such that the loss of load expectation (LOLE) of disconnecting firm load due to resource deficiencies shall be, on average, no more than 0.1 day per year.
NPCC is more stringent because NERC has no equivalent Requirement to limit the risk of firm load disconnection due to resource issues.
TFSS
PRC-001-0
R7
none
A5 Sec. 2.4
Operating Time - Bulk power system protection shall take corrective action within times determined by studies with due regard to security, dependability and selectivity. Adequate time margin should be provided taking into account study inaccuracies, differences in equipment, and protection operating times.
Yes
TFSP
Page 91 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Yes Comment RRO Requirement? Task Force?
PRC-001-0
R8
none
A5 Sec. 3.0
Equipment and Design Considerations this section deals with the detailed protection considerations involving CTs, VTs, Logic Systems, Microprocessor-based equipment and software, Batteries, Station Service supplies, Circuit Breakers, Telecommunication, Control Cables and Wiring, Environment and Grounding. Specific Application Considerations this section deals with the specific protection requirements of Transmission Lines, Transmission Stations, Breaker Failure, Generating Stations, UFLS, HVdc, Capacitor Banks and SVCs
NPCC is more stringent because there is no equivalent NERC Requirement NPCC is more stringent because there is no equivalent NERC Requirement NPCC is more stringent by providing a guide to establish testing criteria for this newer technology introduced into the protective relaying field
TFSP
PRC-001-0
R9
none
A5 Sec. 4.0
Yes
TFSP
PRC-005-0
R3
none
B23
Guide for Maintenance of Microprocessor Based Protection Relays: - The use of computer based technology Yes for protective relays has influenced what is considered sufficient for periodic maintenance of microprocessorbased relays. The purpose of this document is to provide guidance for the maintenance of microprocessorbased protective relays as required in Section 2 of NPCC Maintenance Criteria for Bulk Power System Protection, Document A-4 on verifying operating characteristics
TFSP
PRC-012-0
R3
None
Equipment and Design Considerations this section deals with the detailed special protection system Yes considerations involving CTs, VTs, Logic Systems, Microprocessor-based equipment and software, Batteries, Station Service supplies, Circuit Breakers, Telecommunication, Control Cables and
NPCC is more stringent because there is no equivalent NERC Requirement NPCC is more stringent because there is no equivalent NERC Requirement
TFSP
PRC-012-0
R4
none
Specific Application Considerations this section deals with the specific special protection system requirements of dealing with Breaker Failure events.
Yes
TFSP
Category Single Line Ground (SLG) or 3-Phase Fault with Normal Clearing: 1. Generator 2. B faults Transmission Circuit 3. Transformer
A2 Sec. 5.1a
A2 Sec. 5.1a A permanent 3-phase fault on any Generator, Transmission Circuit, Transformer or Bus Section with Normal Fault Clearing.
Yes
TFCP
Must withstand loss of two transmission circuits for a single fault. Must withstand a SLG fault with a Stuck breaker Must withstand a 3Phase Bus fault (NERC only requires a SLG Bus fault and allows Loss of Demand or Transfer Curtailments to deal with it) TPL Contingency Table I Event resulting in loss of a Single Element Category Single Line Ground (SLG) or 3-Phase Fault with Normal Clearing: 1. Generator 2. B faults Transmission Circuit 3. Transformer A2 Sec. 5.1b A2 Sec. 5.1b Simultaneous permanent phase-to-ground faults on different phases of each of two adjacent circuits on a multiple circuit tower with Normal Fault Clearing. Must withstand loss of two transmission circuits for a single fault. Must withstand a SLG fault with a Stuck breaker Must withstand a 3Phase Bus fault (NERC only requires a SLG Bus fault and allows Loss of Demand or Transfer Curtailments to deal with it) NPCC is more stringent in requiring withstanding the loss of both DC poles. TFCP
A2 Sec. 5.1f
Simultaneous permanent loss of both poles of a direct current bipolar facility without an AC fault.
Yes
TFCP
Page 92 of 186
156150660.xls.ms_office
STD # NERC Version 0 Reliability Standard Require Reliability Standard Requirement Language ment NPCC Document # NPCC Document Language Regional Difference (Yes/No) Yes Comment RRO Requirement? Task Force?
A2 Sec. 5.1a A Permanent 3-phase fault on any Generator, Transmission Circuit, Transformer or Bus Section with Normal Fault Clearing.
NPCC is more stringent in that the Bus fault can be 3-Phase instead of SLG and no allowance is made in NPCC for planned/controlled Loss of Demand or Curtailment of Transfers to deal with the results.
TFCP
Event(s) resulting in the loss of two or more (multiple) elements Event(s) resulting in the loss of two or more (multiple) elements
Category C Category Bipolar Block, with Normal Clearing: 4. Bipolar (DC) Line Fault (non 3-Ph) with C Normal Clearing 5. Any two circuits of a multiple-circuit tower line A2 Sec. 5.1f and 5.1b
A2 Sec. 6.1e A permanent SLG fault on a Circuit Breaker with Normal Clearing (Normal Clearing for this condition may not always be high speed) Sec. 5.1f Simultaneous permanent loss of both poles of a direct current bipolar facility without an AC fault Yes NPCC is more stringent for DC trips because it covers loss of both DC bipoles for a non-fault condition. NPCC is more stringent for loss of two circuits on a common tower because it does not allow for planned/controlled Loss of Demand or Curtailment of Transfers to deal with the results.
TFCP
TFCP
Sec. 1b Simultaneous permanent phase-to-ground faults on different phases of each of two adjacent circuits on a multiple circuit tower with Normal Fault Clearing.
TFCP
Event(s) resulting in the loss of two or more (multiple) elements Event(s) resulting in the loss of two or more (multiple) elements System Performance Following Loss of a Single Bulk Electric System Element (Category B),
No none equivalen t No none equivalen t R3.1.10 Include the effects of existing and planned protection systems, including any backup or redundant systems.
A2 Sec. 7.0i
Sudden loss of fuel delivery system to multiple plants, (i.e. gas pipeline contingencies, including both gas transmission lines and gas mains).
Yes
TFCP
A2 Sec. 8.0
Extreme System Condition Assessment (ESCA): - The bulk power system can be subjected to wide range of Yes other than normal system conditions that have low probability of occurrence. One of the objectives of ESCA is to determine, through planning studies, the impact of these conditions on expected steady-state and dynamic system performance. Stability of the bulk power system shall be maintained during and following the most severe of the contingencies stated below. For each of the contingencies below that involves a fault, stability shall be maintained when the simulation is based on fault clearing initiated by the system A protection group, and also shall be maintained when the simulation is based on fault clearing initiated by the system B protection group. Yes
TFCP
NPCC is more stringent in that it requires that both A and B protection systems be capable of maintaining stability.
TFCP
TPL-003-0
R4
none
B4 Sec. 5.1.7
5.1.7 - Review any exclusions granted under the NPCC Guidelines for Requesting Exclusions to Sections Yes 5.1(b) and 6.1(b) of the NPCC Basic Criteria for Design and Operation of Interconnected Power Systems (Document B-10). A Comprehensive Review should address all exclusions, but an Intermediate Review may focus on just those exclusions that may have been impacted by system changes since they were last reviewed.
NPCC is more stringent in having a mechanism for reviewing cases where exclusions from having to comply with the Basic Design Criteria are requested by a member organization.
TFSS
TPL-003-0
R4
none
B10
B10 Guidelines for Requesting Exclusions to Sections 5.1 (b) and 6.1 (b) of the NPCC Basic Criteria for Design and Operation of Interconnected Power Systems
Yes
NPCC is more stringent in having a mechanism for reviewing cases where exclusions from having to comply with the Basic Design Criteria are requested by a member organization.
TFSS
Page 93 of 186
156150660.xls.ms_office
Violation Risk Factor
Low
Low
Low
Low
Low
High
Medium
Page 94 of 186
156150660.xls.ms_office
Violation Risk Factor
Medium
Medium Medium
Medium
Medium Medium
High
High
High
High
Page 95 of 186
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
Medium
Medium
Medium
Page 96 of 186
156150660.xls.ms_office
Violation Risk Factor
Medium
Medium (CCC Low) Medium (CCC Low) Medium (CCC Low) Medium
Low
Low
Low
Low Low
Low
Page 97 of 186
156150660.xls.ms_office
Violation Risk Factor
Low
Medium
Medium
Medium
Medium
High
High
High
Medium
High
High
High
Page 98 of 186
156150660.xls.ms_office
Violation Risk Factor
High
High High
High
High
Medium
High
High
Medium
Medium
Low
Low Low
Page 99 of 186
156150660.xls.ms_office
Violation Risk Factor
Low
Low
Low
Low
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
Low
Medium
156150660.xls.ms_office
Violation Risk Factor
Low
Low
Low
Low
Low
Low
Low
Low
156150660.xls.ms_office
Violation Risk Factor
Low
Low
Low
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
High High
High High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
high only because of R 1.2's importance high only because of R 1.2's importance
high only because of R 1.2's importance high only because of R 1.2's importance Low
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
High
Low
Medium
156150660.xls.ms_office
Violation Risk Factor
Medium
Medium
Medium
Medium
Medium
Medium Medium
156150660.xls.ms_office
Violation Risk Factor
Medium
Medium
Medium
Medium
Medium
Medium
Medium
Low
High
156150660.xls.ms_office
Violation Risk Factor
Low
156150660.xls.ms_office
Violation Risk Factor
Low
Low
Low
Low
156150660.xls.ms_office
Violation Risk Factor
Low
Low
Low
Low
Low
Medium
Medium
Low
Low
Low
Low
medium
Low
156150660.xls.ms_office
Violation Risk Factor
156150660.xls.ms_office
Violation Risk Factor
High High
High
High
Medium
Medium
Medium
156150660.xls.ms_office
Violation Risk Factor
Medium
Medium
Medium
High
High
High
High
High
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
Low
Low
Low
High
Low
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
Low
High
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
156150660.xls.ms_office
Violation Risk Factor
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
156150660.xls.ms_office
Violation Risk Factor
Low
Low
Low
Low
Low
156150660.xls.ms_office
Violation Risk Factor
Low
Low
Low
Low
Low
Low
Low
Low
Low
Low
156150660.xls.ms_office
Violation Risk Factor
Low
Low
Low
Low
Low
Low
Low
Low
Low
156150660.xls.ms_office
Violation Risk Factor
Low
Low
Low
Low
Low
Low
Low
Low
Low
Low
156150660.xls.ms_office
Violation Risk Factor
Low
Low
Low
Low
Low
Low
Low
Low
Low
Low
Low
156150660.xls.ms_office
Violation Risk Factor
Low
Low
Low
Low
Low
Low
Low
Low
Low
Low
Low
Low
Low
156150660.xls.ms_office
Violation Risk Factor
Low
Low
Low
Low
Low
Low
Low
Low
Low
Low
Low
Low
156150660.xls.ms_office
Violation Risk Factor
Low
Low
Low
Low
Low
Low
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
Low
156150660.xls.ms_office
Violation Risk Factor
Low
Low
Low
Low
156150660.xls.ms_office
Violation Risk Factor
Low
Low
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
Low
Low
Low
Low
Low
Low
Low
Low
Low
Low
Low
156150660.xls.ms_office
Violation Risk Factor
Low
Low
Low
Low
Low
Low
Low
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High High
High
High
High High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
Low
Low
Low
Low
Low
Low
156150660.xls.ms_office
Violation Risk Factor
Low
Low
High
Low
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
High
High
Low
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
High
High
Low
Low
156150660.xls.ms_office
Violation Risk Factor
High
Low
Low
High
Medium
156150660.xls.ms_office
Violation Risk Factor
Low
Medium
Medium
Medium
Medium
Medium
Low
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
Low
High
156150660.xls.ms_office
Violation Risk Factor
Low
Low
Low
156150660.xls.ms_office
Violation Risk Factor
Low
Low
Low
Low
Low
Low
Medium
Low
Low
Low
Low Low
Low
Low
Low
156150660.xls.ms_office
Violation Risk Factor
Medium
Medium
Medium
Medium
Low
High
High
Low
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
Low
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
High High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
Low
High
High High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
156150660.xls.ms_office
Violation Risk Factor
Low
Low
156150660.xls.ms_office
Violation Risk Factor
156150660.xls.ms_office
Violation Risk Factor
156150660.xls.ms_office
Violation Risk Factor
156150660.xls.ms_office
Violation Risk Factor
156150660.xls.ms_office
Violation Risk Factor
156150660.xls.ms_office
Violation Risk Factor
Medium
156150660.xls.ms_office
Violation Risk Factor
156150660.xls.ms_office
Violation Risk Factor
156150660.xls.ms_office
Violation Risk Factor
Medium
Medium
Medium
Medium
Medium
Medium
Medium
Medium
Medium
Medium
Medium
156150660.xls.ms_office
Violation Risk Factor
Medium
Medium
Medium
Medium
Medium
Medium
Medium
Medium
Medium
Medium
Medium
Medium
156150660.xls.ms_office
Violation Risk Factor
156150660.xls.ms_office
Violation Risk Factor
High
High
High
High
High
High
High
High
High
High
High
High
156150660.xls.ms_office
Violation Risk Factor
156150660.xls.ms_office
Violation Risk Factor
156150660.xls.ms_office
Violation Risk Factor