Home › Active Standard › PRC-006-5 — Automatic Underfrequency Load Shedding

PRC-006-5 — Automatic Underfrequency Load Shedding

Purpose
To establish design and documentation requirements for automatic underfrequency load shedding (UFLS) programs to arrest declining frequency, assist recovery of frequency following underfrequency events and provide last resort system preservation measures.

Applicability

  • Planning Coordinators
  • UFLS entities shall mean all entities that are responsible for the ownership, operation, or control of UFLS equipment as required by the UFLS program established by the Planning Coordinators. Such entities may include one or more of the following:
    • Transmission Owners
    • Distribution Providers
    • UFLS-Only Distribution Providers
  • Transmission Owners that own Elements identified in the UFLS program established by the Planning Coordinators.

Effective Date
See Implementation Plan

Requirements and Measures
R1. Each Planning Coordinator shall develop and document criteria, including consideration of historical events and system studies, to select portions of the Bulk Electric System (BES), including interconnected portions of the BES in adjacent Planning Coordinator areas and Regional Entity areas that may form islands. [VRF: Medium][Time Horizon: Long-term Planning]

M1. Each Planning Coordinator shall have evidence such as reports, or other documentation of its criteria to select portions of the Bulk Electric System that may form islands including how system studies and historical events were considered to develop the criteria per Requirement R1.

R2. Each Planning Coordinator shall identify one or more islands to serve as a basis for designing its UFLS program including: [VRF: Medium][Time Horizon: Long-term Planning]

2.1. Those islands selected by applying the criteria in Requirement R1, and
2.2. Any portions of the BES designed to detach from the Interconnection (planned islands) as a result of the operation of a relay scheme or Special Protection System, and
2.3. A single island that includes all portions of the BES in either the Regional Entity area or the Interconnection in which the Planning Coordinator’s area resides. If a Planning Coordinator’s area resides in multiple Regional Entity areas, each of those Regional Entity areas shall be identified as an island. Planning Coordinators may adjust island boundaries to differ from Regional Entity area boundaries by mutual consent where necessary for the sole purpose of producing contiguous regional islands more suitable for simulation.

M2. Each Planning Coordinator shall have evidence such as reports, memorandums, e-mails, or other documentation supporting its identification of an island(s) as a basis for designing a UFLS program that meet the criteria in Requirement R2, Parts 2.1 through 2.3.

R3. Each Planning Coordinator shall develop a UFLS program, including notification of and a schedule for implementation by UFLS entities within its area, that meets the following performance characteristics in simulations of underfrequency conditions resulting from an imbalance scenario, where an imbalance = [(load — actual generation output) / (load)], of up to 25 percent within the identified island(s). [VRF: High][Time Horizon: Long-term Planning]

3.1. Frequency shall remain above the Underfrequency Performance Characteristic curve in PRC-006-5 – Attachment 1, either for 60 seconds or until a steady-state condition between 59.3 Hz and 60.7 Hz is reached, and
3.2. Frequency shall remain below the Overfrequency Performance Characteristic curve in PRC-006-5 – Attachment 1, either for 60 seconds or until a steady-state condition between 59.3 Hz and 60.7 Hz is reached, and
3.3. Volts per Hz (V/Hz) shall not exceed 1.18 per unit for longer than two seconds cumulatively per simulated event, and shall not exceed 1.10 per unit for longer than 45 seconds cumulatively per simulated event at each generator bus and generator step-up transformer high-side bus associated with each of the following:

• Individual generating units greater than 20 MVA (gross nameplate rating) directly connected to the BES
• Generating plants/facilities greater than 75 MVA (gross aggregate nameplate rating) directly connected to the BES
• Facilities consisting of one or more units connected to the BES at a common bus with total generation above 75 MVA gross nameplate rating.

M3. Each Planning Coordinator shall have evidence such as reports, memorandums, e-mails, program plans, or other documentation of its UFLS program, including the

R4. Each Planning Coordinator shall conduct and document a UFLS design assessment at least once every five years that determines through dynamic simulation whether the UFLS program design meets the performance characteristics in Requirement R3 for each island identified in Requirement R2. The simulation shall model each of the following: [VRF: High][Time Horizon: Long-term Planning]

4.1. Underfrequency trip settings of individual generating units greater than 20 MVA (gross nameplate rating) directly connected to the BES that trip above the Generator Underfrequency Trip Modeling curve in PRC-006-5 – Attachment 1.
4.2. Underfrequency trip settings of generating plants/facilities greater than 75 MVA (gross aggregate nameplate rating) directly connected to the BES that trip above the Generator Underfrequency Trip Modeling curve in PRC-006-5 – Attachment 1.
4.3. Underfrequency trip settings of any facility consisting of one or more units connected to the BES at a common bus with total generation above 75 MVA (gross nameplate rating) that trip above the Generator Underfrequency Trip Modeling curve in PRC-006-5 – Attachment 1.
4.4. Overfrequency trip settings of individual generating units greater than 20 MVA (gross nameplate rating) directly connected to the BES that trip below the Generator Overfrequency Trip Modeling curve in PRC-006-5 — Attachment 1.
4.5. Overfrequency trip settings of generating plants/facilities greater than 75 MVA (gross aggregate nameplate rating) directly connected to the BES that trip below the Generator Overfrequency Trip Modeling curve in PRC-006-5 — Attachment 1.
4.6. Overfrequency trip settings of any facility consisting of one or more units connected to the BES at a common bus with total generation above 75 MVA (gross nameplate rating) that trip below the Generator Overfrequency Trip Modeling curve in PRC-006-5 — Attachment 1.
4.7. Any automatic Load restoration that impacts frequency stabilization and operates within the duration of the simulations run for the assessment.

M4. Each Planning Coordinator shall have dated evidence such as reports, dynamic simulation models and results, or other dated documentation of its UFLS design assessment that demonstrates it meets Requirement R4, Parts 4.1 through 4.7.

R5. Each Planning Coordinator, whose area or portions of whose area is part of an island identified by it or another Planning Coordinator which includes multiple Planning Coordinator areas or portions of those areas, shall coordinate its UFLS program design with all other Planning Coordinators whose areas or portions of whose areas are also part of the same identified island through one of the following: [VRF: High][Time Horizon: Long-term Planning]

• Develop a common UFLS program design and schedule for implementation per Requirement R3 among the Planning Coordinators whose areas or portions of whose areas are part of the same identified island, or
• Conduct a joint UFLS design assessment per Requirement R4 among the Planning Coordinators whose areas or portions of whose areas are part of the same identified island, or
• Conduct an independent UFLS design assessment per Requirement R4 for the identified island, and in the event the UFLS design assessment fails to meet Requirement R3, identify modifications to the UFLS program(s) to meet Requirement R3 and report these modifications as recommendations to the other Planning Coordinators whose areas or portions of whose areas are also part of the same identified island and the ERO.

M5. Each Planning Coordinator, whose area or portions of whose area is part of an island identified by it or another Planning Coordinator which includes multiple Planning Coordinator areas or portions of those areas, shall have dated evidence such as joint UFLS program design documents, reports describing a joint UFLS design assessment, letters that include recommendations, or other dated documentation demonstrating that it coordinated its UFLS program design with all other Planning Coordinators whose areas or portions of whose areas are also part of the same identified island per Requirement R5.

R6. Each Planning Coordinator shall maintain a UFLS database containing data necessary to model its UFLS program for use in event analyses and assessments of the UFLS program at least once each calendar year, with no more than 15 months between maintenance activities. [VRF: Lower][Time Horizon: Long-term Planning]

M6. Each Planning Coordinator shall have dated evidence such as a UFLS database, data requests, data input forms, or other dated documentation to show that it maintained a UFLS database for use in event analyses and assessments of the UFLS program per Requirement R6 at least once each calendar year, with no more than 15 months between maintenance activities.

R7. Each Planning Coordinator shall provide its UFLS database containing data necessary to model its UFLS program to other Planning Coordinators within its Interconnection within 30 calendar days of a request. [VRF: Lower][Time Horizon: Long-term Planning]

M7. Each Planning Coordinator shall have dated evidence such as letters, memorandums, e-mails or other dated documentation that it provided their UFLS database to other Planning Coordinators within their Interconnection within 30 calendar days of a request per Requirement R7.

R8. Each UFLS entity shall provide data to its Planning Coordinator(s) according to the format and schedule specified by the Planning Coordinator(s) to support maintenance of each Planning Coordinator’s UFLS database. [VRF: Lower][Time Horizon: Long-term Planning]

M8. Each UFLS Entity shall have dated evidence such as responses to data requests, spreadsheets, letters or other dated documentation that it provided data to its Planning Coordinator according to the format and schedule specified by the Planning Coordinator to support maintenance of the UFLS database per Requirement R8.

R9. Each UFLS entity shall provide automatic tripping of Load in accordance with the UFLS program design and schedule for implementation, including any Corrective Action Plan, as determined by its Planning Coordinator(s) in each Planning Coordinator area in which it owns assets. [VRF: High][Time Horizon: Long-term Planning]

M9. Each UFLS Entity shall have dated evidence such as spreadsheets summarizing feeder load armed with UFLS relays, spreadsheets with UFLS relay settings, or other dated documentation that it provided automatic tripping of load in accordance with the UFLS program design and schedule for implementation, including any Corrective Action Plan, per Requirement R9.

R10. Each Transmission Owner shall provide automatic switching of its existing capacitor banks, Transmission Lines, and reactors to control over-voltage as a result of underfrequency load shedding if required by the UFLS program and schedule for implementation, including any Corrective Action Plan, as determined by the Planning Coordinator(s) in each Planning Coordinator area in which the Transmission Owner owns transmission. [VRF: High][Time Horizon: Long-term Planning]

M10. Each Transmission Owner shall have dated evidence such as relay settings, tripping logic or other dated documentation that it provided automatic switching of its existing capacitor banks, Transmission Lines, and reactors in order to control over-voltage as a result of underfrequency load shedding if required by the UFLS program and schedule for implementation, including any Corrective Action Plan, per Requirement R10.

R11. Each Planning Coordinator, in whose area a BES islanding event results in system frequency excursions below the initializing set points of the UFLS program, shall conduct and document an assessment of the event within one year of event actuation to evaluate: [VRF: Medium][Time Horizon: Operations Assessment]

11.1. The performance of the UFLS equipment,
11.2. The effectiveness of the UFLS program.

M11. Each Planning Coordinator shall have dated evidence such as reports, data gathered from an historical event, or other dated documentation to show that it conducted an event assessment of the performance of the UFLS equipment and the effectiveness of the UFLS program per Requirement R11.

R12. Each Planning Coordinator, in whose islanding event assessment (per R11) UFLS program deficiencies are identified, shall conduct and document a UFLS design assessment to consider the identified deficiencies within two years of event actuation. [VRF: Medium][Time Horizon: Operations Assessment]

M12. Each Planning Coordinator shall have dated evidence such as reports, data gathered from an historical event, or other dated documentation to show that it conducted a UFLS design assessment per Requirements R12 and R4 if UFLS program deficiencies are identified in R11.

R13. Each Planning Coordinator, in whose area a BES islanding event occurred that also included the area(s) or portions of area(s) of other Planning Coordinator(s) in the same islanding event and that resulted in system frequency excursions below the initializing set points of the UFLS program, shall coordinate its event assessment (in accordance with Requirement R11) with all other Planning Coordinators whose areas or portions of whose areas were also included in the same islanding event through one of the following: [VRF: Medium][Time Horizon: Operations Assessment]

• Conduct a joint event assessment per Requirement R11 among the Planning Coordinators whose areas or portions of whose areas were included in the same islanding event, or
• Conduct an independent event assessment per Requirement R11 that reaches conclusions and recommendations consistent with those of the event assessments of the other Planning Coordinators whose areas or portions of whose areas were included in the same islanding event, or
• Conduct an independent event assessment per Requirement R11 and where the assessment fails to reach conclusions and recommendations consistent with those of the event assessments of the other Planning Coordinators whose areas or portions of whose areas were included in the same islanding event, identify differences in the assessments that likely resulted in the differences in the conclusions and recommendations and report these differences to the other Planning Coordinators whose areas or portions of whose areas were included in the same islanding event and the ERO.

M13. Each Planning Coordinator, in whose area a BES islanding event occurred that also included the area(s) or portions of area(s) of other Planning Coordinator(s) in the same islanding event and that resulted in system frequency excursions below the initializing set points of the UFLS program, shall have dated evidence such as a joint assessment report, independent assessment reports and letters describing likely reasons for differences in conclusions and recommendations, or other dated documentation demonstrating it coordinated its event assessment (per Requirement R11) with all other Planning Coordinator(s) whose areas or portions of whose areas were also included in the same islanding event per Requirement R13.

R14. Each Planning Coordinator shall respond to written comments submitted by UFLS entities and Transmission Owners within its Planning Coordinator area following a comment period and before finalizing its UFLS program, indicating in the written response to comments whether changes will be made or reasons why changes will not be made to the following [VRF: Lower][Time Horizon: Long-term Planning]:

14.1. UFLS program, including a schedule for implementation
14.2. UFLS design assessment
14.3. Format and schedule of UFLS data submittal

M14. Each Planning Coordinator shall have dated evidence of responses, such as e-mails and letters, to written comments submitted by UFLS entities and Transmission Owners within its Planning Coordinator area following a comment period and before finalizing its UFLS program per Requirement R14.

R15. Each Planning Coordinator that conducts a UFLS design assessment under Requirement R4, R5, or R12 and determines that the UFLS program does not meet the performance characteristics in Requirement R3, shall develop a Corrective Action Plan and a schedule for implementation by the UFLS entities within its area. [VRF: High][Time Horizon: Long-term Planning]

15.1. For UFLS design assessments performed under Requirement R4 or R5, the Corrective Action Plan shall be developed within the five-year time frame identified in Requirement R4.
15.2. For UFLS design assessments performed under Requirement R12, the Corrective Action Plan shall be developed within the two-year time frame identified in Requirement R12.

M15. Each Planning Coordinator that conducts a UFLS design assessment under Requirement R4, R5, or R12 and determines that the UFLS program does not meet the performance characteristics in Requirement R3, shall have a dated Corrective Action Plan and a schedule for implementation by the UFLS entities within its area, that was developed within the time frame identified in Part 15.1 or 15.2.

Compliance

Compliance Monitoring Process

1.1. Compliance Enforcement Authority
As defined in the NERC Rules of Procedure, “Compliance Enforcement Authority” (CEA) means NERC or the Regional Entity in their respective roles of monitoring and enforcing compliance with the NERC Reliability Standards.

1.2. Evidence Retention
Each Planning Coordinator and UFLS entity shall keep data or evidence to show compliance as identified below unless directed by its Compliance Enforcement Authority to retain specific evidence for a longer period of time as part of an investigation:

• Each Planning Coordinator shall retain the current evidence of Requirements R1, R2, R3, R4, R5, R12, R14, and R15, Measures M1, M2, M3, M4, M5, M12, M14, and M15 as well as any evidence necessary to show compliance since the last compliance audit.
• Each Planning Coordinator shall retain the current evidence of UFLS database update in accordance with Requirement R6, Measure M6, and evidence of the prior year’s UFLS database update.
• Each Planning Coordinator shall retain evidence of any UFLS database transmittal to another Planning Coordinator since the last compliance audit in accordance with Requirement R7, Measure M7.
• Each UFLS entity shall retain evidence of UFLS data transmittal to the Planning Coordinator(s) since the last compliance audit in accordance with Requirement R8, Measure M8.
• Each UFLS entity shall retain the current evidence of adherence with the UFLS program in accordance with Requirement R9, Measure M9, and evidence of adherence since the last compliance audit.
• Transmission Owner shall retain the current evidence of adherence with the UFLS program in accordance with Requirement R10, Measure M10, and evidence of adherence since the last compliance audit.
• Each Planning Coordinator shall retain evidence of Requirements R11, and R13, and Measures M11, and M13 for 6 calendar years.

If a Planning Coordinator or UFLS entity is found non-compliant, it shall keep information related to the non-compliance until found compliant or for the retention period specified above, whichever is longer.

The Compliance Enforcement Authority shall keep the last audit records and all requested and submitted subsequent audit records

1.3. Compliance Monitoring and Assessment Processes:
Compliance Audit
Self-Certification
Spot Checking
Compliance Violation Investigation
Self-Reporting
Complaints

1.4. Additional Compliance Information
None

Rationale:
During development of this standard, text boxes were embedded within the standard to explain the rationale for various parts of the standard. Upon BOT approval, the text from the rationale text boxes was moved to this section.

Rationale for R9:
The “Corrective Action Plan” language was added in response to the FERC directive from Order No. 763, which raised concern that the standard failed to specify how soon an entity would need to implement corrections after a deficiency is identified by a Planning Coordinator (PC) assessment. The revised language adds clarity by requiring that each UFLS entity follow the UFLS program, including any Corrective Action Plan, developed by the PC.

Also, to achieve consistency of terminology throughout this standard, the word “application” was replaced with “implementation.” (See Requirements R3, R14 and R15)

Rationale for R10:
The “Corrective Action Plan” language was added in response to the FERC directive from Order No. 763, which raised concern that the standard failed to specify how soon an entity would need to implement corrections after a deficiency is identified by a PC assessment. The revised language adds clarity by requiring that each UFLS entity follow the UFLS program, including any Corrective Action Plan, developed by the PC.

Also, to achieve consistency of terminology throughout this standard, the word “application” was replaced with “implementation.” (See Requirements R3, R14 and R15)

Rationale for R15:
Requirement R15 was added in response to the directive from FERC Order No. 763, which raised concern that the standard failed to specify how soon an entity would need to implement corrections after a deficiency is identified by a PC assessment. Requirement R15 addresses the FERC directive by making explicit that if deficiencies are identified as a result of an assessment, the PC shall develop a Corrective Action Plan and schedule for implementation by the UFLS entities.

A “Corrective Action Plan” is defined in the NERC Glossary of Terms as, “a list of actions and an associated timetable for implementation to remedy a specific problem.” Thus, the Corrective Action Plan developed by the PC will identify the specific timeframe for an entity to implement corrections to remedy any deficiencies identified by the PC as a result of an assessment.

 

Related Terms:

Top