{"text_format":"3","workbook":"xlsx","n_sheets":6,"sheets":["IESOChangeHistory","NERCStandardsList","NERCRequirementsMapping","NPCCDocuments","NPCCRequirements","NPCC Paragraph Documents "],"not_rendered":{"external_links":3,"defined_names":14},"read":"whole","date_system":"1900"}

{"sheet":"IESOChangeHistory","index":0,"n_rows":3,"n_cols":4,"rows_kept":3}
["ID","Date of Change","Version","Change"]
[null,"2024-01-29",35,"Updated to remove IESO specific information "]
[null,"2024-02-20",36,"Updated EOP-011-1 and EOP-011-2 statuses "]

{"sheet":"NERCStandardsList","index":1,"n_rows":126,"n_cols":14,"rows_kept":126}
["Standard Number","Standard Group","Standard Number Without Version","Document Title","NERC BOT Adoption Date","USA Approval Status","OEB Start Date","OEB End Date","Mandatory Enforcement Date in Ontario","Inactive Date in Ontario","Status In Ontario","External Link","External Link","Functional Entities"]
[{"$nulls":10},"As Of 2022/08/16"]
["BAL-001-2","BAL","BAL-001","Real Power Balancing Control Performance","2013-08-15","Approved","2014-04-07","2014-08-15","2016-07-01",null,"Effective",{"$f":"HYPERLINK(M3,D3)","v":"Real Power Balancing Control Performance"},"http://www.nerc.com/pa/Stand/Reliability Standards/BAL-001-2.pdf","PSE, BA"]
["BAL-002-3","BAL","BAL-002","Disturbance Control Standard – Contingency Reserve for Recovery from a Balancing Contingency Event","2018-08-16","Approved","2018-08-21","2018-12-19","2019-07-01",null,"Effective","Disturbance Control Standard – Contingency Reserve for Recovery from a Balancing Contingency Event","https://www.nerc.com/pa/Stand/Reliability%20Standards/BAL-002-3.pdf","RSG, BA"]
["BAL-003-2","BAL","BAL-003","Frequency Response and Frequency Bias Setting","2019-12-19","Approved","2020-01-10","2020-04-18","2021-01-01",null,"Effective","Frequency Response and Frequency Bias Setting","https://www.nerc.com/pa/Stand/Reliability%20Standards/BAL-003-2.pdf","BA"]
["BAL-005-1","BAL","BAL-005","Balancing Authority Control","2016-02-11","Approved","2016-04-26","2016-08-24","2019-01-01",null,"Effective","Balancing Authority Control","http://www.nerc.com/pa/Stand/Reliability Standards/BAL-005-1.pdf","BA"]
["CIP-002-5.1a","CIP","CIP-002","Cyber Security — BES Cyber System Categorization","2016-12-14","Approved","1900-01-01","1900-01-02","2016-12-27",null,"Effective","Cyber Security — BES Cyber System Categorization","http://www.nerc.com/pa/Stand/Reliability%20Standards/CIP-002-5.1a.pdf","TOP, TO, RC, IA, GOP, GO, DP, BA"]
["CIP-003-8","CIP","CIP-003","Cyber Security — Security Management Controls","2019-05-08","Approved","2019-06-14","2019-09-19","2020-04-01",null,"Effective","Cyber Security — Security Management Controls","http://www.nerc.com/pa/Stand/Reliability Standards/CIP-003-8.pdf","TOP, TO, RC, GOP, GO, DP, BA"]
["CIP-004-6","CIP","CIP-004","Cyber Security — Personnel & Training","2014-11-13","Approved","2015-02-26","2015-06-26","2016-07-01",null,"Effective","Cyber Security — Personnel & Training","http://www.nerc.com/pa/Stand/Reliability Standards/CIP-004-6.pdf","TOP, TO, RC, IA, GOP, GO, DP, BA"]
["CIP-005-6","CIP","CIP-005","Cyber Security — Electronic Security Perimeter(s)","2017-08-10","Approved","2017-10-10","2018-02-07","2020-10-01","2022-09-30","Effective","Cyber Security — Electronic Security Perimeter(s)","http://www.nerc.com/pa/Stand/Reliability Standards/CIP-005-6.pdf","TOP, TO, RC, IA, GOP, GO, DP, BA"]
["CIP-005-7","CIP","CIP-005","Cyber Security – Electronic Security Perimeter(s)","2020-12-21","Approved","2021-01-19","2021-04-28","2022-10-01",null,"Future Effective","Cyber Security – Electronic Security Perimeter(s)","https://www.nerc.com/pa/Stand/Reliability%20Standards/CIP-005-7.pdf","TOP, TO, RC, GOP, GO, DP, BA"]
["CIP-006-5","CIP","CIP-006","Cyber Security — Physical Security of BES Cyber Systems","2012-11-26","Not Approved","2013-02-05","2013-06-05",null,"2022-09-30","Never Came Into Effect in Ontario","Cyber Security — Physical Security of BES Cyber Systems","http://www.nerc.com/pa/Stand/Reliability Standards/CIP-006-5.pdf","TOP, TO, RC, IA, GOP, GO, DP, BA"]
["CIP-006-6","CIP","CIP-006","Cyber Security — Physical Security of BES Cyber Systems","2014-11-13","Approved","2015-02-26","2015-06-26","2016-07-01",null,"Effective","Cyber Security — Physical Security of BES Cyber Systems","http://www.nerc.com/pa/Stand/Reliability Standards/CIP-006-6.pdf","TOP, TO, RC, IA, GOP, GO, DP, BA"]
["CIP-007-6","CIP","CIP-007","Cyber Security — Systems Security Management","2014-11-13","Approved","2015-02-26","2015-06-26","2016-07-01",null,"Effective","Cyber Security — Systems Security Management","http://www.nerc.com/pa/Stand/Reliability Standards/CIP-007-6.pdf","TOP, TO, RC, IA, GOP, GO, DP, BA"]
["CIP-008-5","CIP","CIP-008","Cyber Security — Incident Reporting and Response Planning","2012-11-26","Approved","2013-02-05","2013-06-05","2016-07-01","2021-03-31","Retired","Cyber Security — Incident Reporting and Response Planning","http://www.nerc.com/pa/Stand/Reliability Standards/CIP-008-5.pdf","TOP, TO, RC, IA, GOP, GO, DP, BA"]
["CIP-008-6","CIP","CIP-008","Cyber Security — Incident Reporting and Response Planning","2019-02-07","Approved","2019-04-01","2019-07-01","2021-04-01",null,"Effective","Cyber Security — Incident Reporting and Response Planning","https://www.nerc.com/pa/Stand/Reliability%20Standards/CIP-008-6.pdf","TO, TOP, RC, GOP, GO, DP, BA"]
["CIP-009-6","CIP","CIP-009","Cyber Security — Recovery Plans for BES Cyber Systems","2014-11-13","Approved","2015-02-26","2015-06-26","2016-07-01",null,"Effective","Cyber Security — Recovery Plans for BES Cyber Systems","http://www.nerc.com/pa/Stand/Reliability Standards/CIP-009-6.pdf","TOP, TO, RC, IA, GOP, GO, DP, BA"]
["CIP-010-3","CIP","CIP-010","Cyber Security — Configuration Change Management and Vulnerability Assessments","2017-08-10","Approved","2017-10-10","2017-10-31","2020-10-01",null,"Effective","Cyber Security — Configuration Change Management and Vulnerability Assessments","http://www.nerc.com/pa/Stand/Reliability Standards/CIP-010-3.pdf","TOP, TO, RC, IA, GOP, GO, DP, BA"]
["CIP-010-4","CIP","CIP-010","– Cyber Security — Configuration Change Management and Vulnerability Assessments","2020-06-12","Approved","2021-01-19","2021-04-28","2022-10-01",null,"Future Effective","– Cyber Security — Configuration Change Management and Vulnerability Assessments","https://www.nerc.com/pa/Stand/Reliability%20Standards/CIP-010-4.pdf","TOP, TO, RC, GOP, GO, DP, BA"]
["CIP-011-2","CIP","CIP-011","Cyber Security Information Protection","2014-11-13","Approved","2015-02-26","2015-06-26","2016-07-01",null,"Effective","Cyber Security Information Protection","http://www.nerc.com/pa/Stand/Reliability Standards/CIP-011-2.pdf","TOP, TO, RC, IA, GOP, GO, DP, BA"]
["CIP-012-1","CIP","CIP-012","Cyber Security – Control Center Communication Networks","2018-08-16","Approved","2018-09-21","2019-01-19","2022-07-01",null,"Effective","Cyber Security – Control Center Communication Networks","https://www.nerc.com/pa/Stand/Reliability%20Standards/CIP-012-1.pdf","TO, TOP, RC, GOP, GO, BA"]
["CIP-013-1","CIP","CIP-013","Cyber Security - Supply Chain Risk Management","2017-08-10","Approved","2017-10-10","2018-02-07","2020-10-01",null,"Effective","Cyber Security - Supply Chain Risk Management","http://www.nerc.com/pa/Stand/Reliability Standards/CIP-013-1.pdf","TOP, TO, RC, GOP, GO, DP, BA"]
["CIP-013-2","CIP","CIP-013","Cyber Security - Supply Chain Risk Management","2020-12-12","Approved","2021-01-19","2021-04-28","2022-10-01",null,"Future Effective","Cyber Security - Supply Chain Risk Management","https://www.nerc.com/pa/Stand/Reliability%20Standards/CIP-013-2.pdf"]
["CIP-014-2","CIP","CIP-014","Physical Security","2015-05-07","Approved","2015-05-22","2015-09-18","2015-10-02",null,"Effective","Physical Security","http://www.nerc.com/pa/Stand/Reliability Standards/CIP-014-2.pdf","TO, TOP"]
["COM-001-3","COM","COM-001","Communications","2016-08-11","Approved","2016-08-17","2016-12-15","2017-10-01",null,"Effective","Communications","http://www.nerc.com/pa/Stand/Project 201507 Internal Communications Capabilitie/COM-001-3_Clean_060116.pdf","RC, TOP, BA, GOP, DP"]
["COM-002-4","COM","COM-002","Operating Personnel Communications Protocols","2014-05-06","Approved","2014-05-21","2014-09-11","2016-07-01",null,"Effective","Operating Personnel Communications Protocols","http://www.nerc.com/pa/Stand/Reliability Standards/COM-002-4.pdf","TOP, RC, BA, GOP, DP"]
["EOP-004-4","EOP","EOP-004","Event Reporting","2017-02-09","Approved","2017-03-31","2017-07-29","2019-04-01",null,"Effective","Event Reporting","http://www.nerc.com/pa/Stand/Reliability Standards/EOP-004-4.pdf","TOP, TO, RC, GOP, GO, DP, BA"]
["EOP-005-3","EOP","EOP-005","System Restoration from Blackstart Resources","2017-02-09","Approved","2017-03-31","2017-07-29","2019-04-01",null,"Effective","System Restoration from Blackstart Resources","http://www.nerc.com/pa/Stand/Reliability Standards/EOP-005-3.pdf","TOP, GOP, TO, DP"]
["EOP-006-3","EOP","EOP-006","System Restoration Coordination","2017-02-09","Approved","2017-03-31","2017-07-29","2019-04-01",null,"Effective","System Restoration Coordination","http://www.nerc.com/pa/Stand/Reliability Standards/EOP-006-3.pdf","RC"]
["EOP-008-2","EOP","EOP-008","Loss of Control Center Functionality","2017-02-09","Approved","2017-03-31","2017-07-29","2019-04-01",null,"Effective","Loss of Control Center Functionality","http://www.nerc.com/pa/Stand/Reliability Standards/EOP-008-2.pdf","TOP, RC, BA"]
["EOP-010-1","EOP","EOP-010","Geomagnetic Disturbance Operations","2013-11-07","Approved","2013-11-15","2014-03-15","2015-04-01",null,"Effective","Geomagnetic Disturbance Operations","http://www.nerc.com/pa/Stand/Reliability Standards/EOP-010-1.pdf","RC, TOP"]
["EOP-011-1","EOP","EOP-011","Emergency Operations","2014-11-13","Approved","2015-01-07","2015-05-08","2017-04-01","2023-09-30","Retired","Emergency Operations","http://www.nerc.com/pa/Stand/Reliability Standards/EOP-011-1.pdf","TOP, BA, RC"]
["EOP-011-2","EOP","EOP-011","Emergency Preparedness and Operations","2021-06-11","Approved","2021-06-11","2021-10-09","2023-10-01",null,"Effective","Emergency Preparedness and Operations","https://www.nerc.com/pa/Stand/Project%20201906%20Cold%20Weather%20DL/2019-06_EOP-011-2_Clean_05182021.pdf","GO"]
["FAC-001-3","FAC","FAC-001","Facility Interconnection Requirements","2016-02-11","Approved","2016-04-26","2016-08-24","2019-01-01",null,"Effective","Facility Interconnection Requirements","http://www.nerc.com/pa/Stand/Project 20101421 Phase 2 DL/FAC-001-3_Draft_Standard_Clean_01272016.pdf","TO, GO"]
["FAC-002-2","FAC","FAC-002","Facility Interconnection Studies","2014-08-14","Approved","2014-08-29","2014-12-27","2016-01-01","2021-03-31","Retired",{"$f":"HYPERLINK(M35,D35)","v":"Facility Interconnection Studies"},"http://www.nerc.com/pa/Stand/Reliability Standards/FAC-002-2.pdf","TP, PC, GO, TO, LSE, DP"]
["FAC-002-3","FAC","FAC-002","Facility Interconnection Studies","2020-01-23","Approved","2020-02-26","2000-06-25","2021-04-01",null,"Effective","Facility Interconnection Studies","https://www.nerc.com/pa/Stand/Project201707StandardsAlignmentwithRegistration/FAC-002-3%20Project%202017%2007%20%20Clean_January2020.pdf","GO, DP, TP, TO, PC"]
["FAC-003-4","FAC","FAC-003","Transmission Vegetation Management",null,"Approved","2016-03-22","2016-06-18","2016-10-01",null,"Effective","Transmission Vegetation Management","http://www.nerc.com/pa/Stand/Reliability Standards/FAC-003-4.pdf","TO, GO"]
["FAC-003-5","FAC","FAC-003","Transmission Vegetation Management","2021-05-13","Approved","2021-07-07","2021-11-04","2024-04-01",null,"Future Effective","Transmission Vegetation Management","https://www.nerc.com/pa/Stand/Project%20201509%20Establish%20and%20Communicate%20System%20Op/2015-09_FAC-003-5_clean_.pdf","TO, GO"]
["FAC-008-3","FAC","FAC-008","Facility Ratings","2011-05-24","Approved","2011-07-13","2011-11-10","2013-01-01","2021-09-30","Retired","Facility Ratings","http://www.nerc.com/pa/Stand/Reliability Standards/FAC-008-3.pdf","GO, TO"]
["FAC-008-5","FAC","FAC-008","Facility Ratings","2021-02-04","Approved","2021-04-07","2011-11-10","2021-10-01",null,"Effective","Facility Ratings","https://www.nerc.com/pa/Stand/Project%20201803%20Standards%20Efficiency%20Review%20Require/2018-03_FAC-008-5_clean_01192021.pdf"]
["FAC-010-3","FAC","FAC-010","System Operating Limits Methodology for the Planning Horizon","2014-11-13","Approved","2015-02-10","2015-06-10","2017-04-01",null,"Effective","System Operating Limits Methodology for the Planning Horizon","http://www.nerc.com/pa/Stand/Reliability Standards/FAC-010-3.pdf","PA"]
["FAC-011-3","FAC","FAC-011","System Operating Limits Methodology for the Operations Horizon","2014-11-13","Approved","2015-02-10","2015-06-10","2017-04-01",null,"Effective","System Operating Limits Methodology for the Operations Horizon","http://www.nerc.com/pa/Stand/Reliability Standards/FAC-011-3.pdf","RC"]
["FAC-011-4","FAC","FAC-011","System Operating Limits Methodology for the Operations Horizon","2021-05-13","Approved","2021-07-07","2021-11-04","2024-04-01",null,"Future Effective","System Operating Limits Methodology for the Operations Horizon","https://www.nerc.com/pa/Stand/Reliability Standards/FAC-011-4.pdf","RC"]
["FAC-014-2","FAC","FAC-014","Establish and Communicate System Operating Limits","2008-06-24","Approved","2008-07-18","2008-11-15","2008-11-16",null,"Effective","Establish and Communicate System Operating Limits","http://www.nerc.com/pa/Stand/Reliability Standards/FAC-014-2.pdf","RC, TOP, PA, TP"]
["FAC-014-3","FAC","FAC-014","Establish and Communicate System Operating Limits","2021-05-13","Approved","2021-07-07","2021-11-04","2024-04-01",null,"Future Effective","Establish and Communicate System Operating Limits","http://www.nerc.com/pa/Stand/Reliability Standards/FAC-014-3.pdf","TOP, TP, RC, PC"]
["INT-006-4","INT","INT-006","Evaluation of Interchange Transactions","2014-02-06","Approved","2014-03-03","2014-07-01","2015-01-01","2021-03-31","Retired","Evaluation of Interchange Transactions","http://www.nerc.com/pa/Stand/Reliability Standards/INT-006-4.pdf","BA, TSP"]
["INT-006-5","INT","INT-006","Evaluation of Interchange Transactions","2019-05-09","Approved","2019-05-09","2019-09-06","2021-04-01",null,"Effective","Evaluation of Interchange Transactions","https://www.nerc.com/pa/Stand/Reliability%20Standards/INT-006-5.pdf","TSP, BA"]
["INT-009-2.1","INT","INT-009","Implementation of Interchange",null,"Approved","1900-01-01","1900-01-02","2015-01-01","2021-03-31","Retired","Implementation of Interchange","http://www.nerc.com/pa/Stand/Reliability Standards/INT-009-2.1.pdf","BA"]
["INT-009-3","INT","INT-009","Implementation of Interchange","2019-05-09","Approved","2019-05-09","2019-09-06","2021-04-01",null,"Effective","Implementation of Interchange","https://www.nerc.com/pa/Stand/Reliability%20Standards/INT-009-3.pdf","BA"]
["IRO-001-4","IRO","IRO-001","Reliability Coordination – Responsibilities","2014-11-13","Approved","2015-03-25","2015-07-23","2017-04-01",null,"Effective","Reliability Coordination – Responsibilities","http://www.nerc.com/pa/Stand/Reliability Standards/IRO-001-4.pdf","RC, TOP, GOP, DP, BA"]
["IRO-002-6","IRO","IRO-002","Reliability Coordination – Monitoring and Analysis","2019-05-09","Approved","2019-04-09","2019-08-15","2020-01-01","2021-03-31","Retired","Reliability Coordination – Monitoring and Analysis","http://www.nerc.com/pa/Stand/Reliability%20Standards/IRO-002-6.pdf","RC"]
["IRO-002-7","IRO","IRO-002","Reliability Coordination - Monitoring and Analysis","2019-05-09","Approved","2019-06-07","2019-10-05","2021-04-01",null,"Effective","Reliability Coordination - Monitoring and Analysis","https://www.nerc.com/pa/Stand/Project%20201803%20Standards%20Efficiency%20Review%20Require/IRO-002-7_clean_04232019.pdf","RC"]
["IRO-006-5","IRO","IRO-006","Reliability Coordination - Transmission Loading Relief (TLR)","2010-11-04","Approved","2011-03-10","2011-07-08","2011-10-01",null,"Effective","Reliability Coordination - Transmission Loading Relief (TLR)","http://www.nerc.com/pa/Stand/Reliability Standards/IRO-006-5.pdf","RC, BA"]
["IRO-006-EAST-2","IRO","IRO-006","Transmission Loading Relief Procedure for the Eastern Interconnection","2015-08-13","Approved","2015-09-22","2016-01-20","2016-07-01",null,"Effective","Transmission Loading Relief Procedure for the Eastern Interconnection","http://www.nerc.com/pa/Stand/Reliability Standards/IRO-006-EAST-2.pdf","RC"]
["IRO-008-2","IRO","IRO-008","Reliability Coordinator Operational Analyses and Real-time Assessments","2014-11-13","Approved","2015-03-25","2015-07-23","2017-04-01",null,"Effective","Reliability Coordinator Operational Analyses and Real-time Assessments","http://www.nerc.com/pa/Stand/Reliability Standards/IRO-008-2.pdf","RC"]
["IRO-008-3","IRO","IRO-008","Reliability Coordinator Operational Analyses and Real-time Assessments","2021-05-13","Approved","2021-07-07","2021-11-04","2024-04-01",null,"Future Effective","Reliability Coordinator Operational Analyses and Real-time Assessments","https://www.nerc.com/pa/Stand/Reliability%20Standards/IRO-008-3.pdf","RC"]
["IRO-009-2","IRO","IRO-009","Reliability Coordinator Actions to Operate Within IROLs","2015-08-13","Approved","2015-09-22","2016-01-20","2016-04-01",null,"Effective","Reliability Coordinator Actions to Operate Within IROLs","http://www.nerc.com/pa/Stand/Reliability Standards/IRO-009-2.pdf","RC"]
["IRO-010-2","IRO","IRO-010","Reliability Coordinator Data Specification and Collection","2014-11-13","Approved","2015-03-25","2015-07-23","2017-01-01","2021-03-31","Retired","Reliability Coordinator Data Specification and Collection","http://www.nerc.com/pa/Stand/Reliability Standards/IRO-010-2.pdf","RC, TOP, TO, LSE, GOP, GO, DP, BA"]
["IRO-010-3","IRO","IRO-010","Reliability Coordinator Data Specification and Collection","2020-01-23","Approved","2020-02-26","2020-06-25","2020-04-01","2023-09-30","Effective","Reliability Coordinator Data Specification and Collection","https://www.nerc.com/pa/Stand/Project201707StandardsAlignmentwithRegistration/IRO-010-3%20Project%202017%2007%20Clean_January2020.pdf","DP, TOP, TO, GOP, GO, BA, RC"]
["IRO-010-4","IRO","IRO-010","Reliability Coordinator Data Specification and Collection","2021-06-11","Approved","2021-10-07","2022-02-22","2023-10-01",null,"Future Effective","Reliability Coordinator Data Specification and Collection","https://www.nerc.com/pa/Stand/Project%20201906%20Cold%20Weather%20DL/2019-06_IRO-010-4_Clean_05182021.pdf"]
["IRO-014-3","IRO","IRO-014","Coordination Among Reliability Coordinators","2014-11-13","Approved","2015-03-25","2015-07-23","2017-04-01",null,"Effective","Coordination Among Reliability Coordinators","http://www.nerc.com/pa/Stand/Reliability Standards/IRO-014-3.pdf","RC"]
["IRO-017-1","IRO","IRO-017","Outage Coordination","2014-11-13","Approved","2015-03-25","2015-07-23","2017-04-01",null,"Effective","Outage Coordination","http://www.nerc.com/pa/Stand/Reliability Standards/IRO-017-1.pdf","RC, TOP, BA, TP, PC"]
["IRO-018-1(i)","IRO","IRO-018","Reliability Coordinator Real-time Reliability Monitoring and Analysis Capabilities","2016-02-11","Approved","2016-06-01","2016-09-29","2018-04-01",null,"Effective","Reliability Coordinator Real-time Reliability Monitoring and Analysis Capabilities","https://www.nerc.com/pa/Stand/Reliability%20Standards/IRO-018-1(i).pdf","RC"]
["MOD-001-0","MOD","MOD-001","Available Transmission System Capability","2005-02-08","Not Approved","1900-01-01","1900-01-02",null,null,"Never Came Into Effect in Ontario","Available Transmission System Capability","http://www.nerc.com/pa/Stand/Reliability Standards/MOD-001-0.pdf","RRO"]
["MOD-001-1a","MOD","MOD-001","Available Transmission System Capability","2009-11-05","Approved","2009-12-18","2010-04-17","2010-04-18",null,"Effective","Available Transmission System Capability","http://www.nerc.com/pa/Stand/Reliability Standards/MOD-001-1a.pdf","TOP, TSP"]
["MOD-001-2","MOD","MOD-001","Available Transmission System Capability","2014-02-06","Not Approved","2014-02-13","2014-06-12",null,null,"Never Came Into Effect in Ontario","Available Transmission System Capability","http://www.nerc.com/pa/Stand/Reliability Standards/MOD-001-2.pdf","TOP, TSP"]
["MOD-004-1","MOD","MOD-004","Capacity Benefit Margin","2008-11-13","Approved","2009-04-15","2009-08-13","2011-04-01",null,"Effective",{"$f":"HYPERLINK(M67,D67)","v":"Capacity Benefit Margin"},"http://www.nerc.com/pa/Stand/Reliability Standards/MOD-004-1.pdf","TSP, LSE, BA, RP, TP"]
["MOD-008-1","MOD","MOD-008","Transmission Reliability Margin Calculation Methodology","2008-08-26","Approved","2009-12-18","2010-04-17","2011-07-01",null,"Effective","Transmission Reliability Margin Calculation Methodology","http://www.nerc.com/pa/Stand/Reliability Standards/MOD-008-1.pdf","TOP"]
["MOD-025-2","MOD","MOD-025","Verification and Data Reporting of Generator Real and Reactive\nPower Capability and Synchronous Condenser Reactive Power Capability","2013-02-07","Approved","2013-06-03","2013-10-01","2016-07-01",null,"Effective","Verification and Data Reporting of Generator Real and Reactive\nPower Capability and Synchronous Condenser Reactive Power Capability","http://www.nerc.com/pa/Stand/Reliability Standards/MOD-025-2.pdf","TO, GO"]
["MOD-026-1","MOD","MOD-026","Verification of Models and Data for Generator Excitation Control\nSystem or Plant Volt/Var Control Functions","2013-02-07","Approved","2013-06-03","2013-10-01","2014-07-01",null,"Effective","Verification of Models and Data for Generator Excitation Control\nSystem or Plant Volt/Var Control Functions","http://www.nerc.com/pa/Stand/Reliability Standards/MOD-026-1.pdf","TP, GO"]
["MOD-027-1","MOD","MOD-027","Verification of Models and Data for Turbine/Governor and Load\nControl or Active Power/Frequency Control Functions","2013-02-07","Approved","2013-06-03","2013-10-01","2014-07-01",null,"Effective","Verification of Models and Data for Turbine/Governor and Load\nControl or Active Power/Frequency Control Functions","http://www.nerc.com/pa/Stand/Reliability Standards/MOD-027-1.pdf","TP, GO"]
["MOD-028-2","MOD","MOD-028","Area Interchange Methodology","2012-02-09","Approved","2012-09-06","2013-01-04","2013-10-01",null,"Effective","Area Interchange Methodology","http://www.nerc.com/pa/Stand/Reliability Standards/MOD-028-2.pdf","TSP, TOP"]
["MOD-029-2a","MOD","MOD-029","Rated System Path Methodology","2014-11-13","Approved","2015-02-10","2015-06-10","2017-04-01",null,"Effective","Rated System Path Methodology","http://www.nerc.com/pa/Stand/Reliability Standards/MOD-029-2a.pdf","TOP, TSP"]
["MOD-030-3","MOD","MOD-030","Flowgate Methodology","2014-11-13","Approved","2015-02-10","2015-06-10","2017-04-01",null,"Effective","Flowgate Methodology","http://www.nerc.com/pa/Stand/Reliability Standards/MOD-030-3.pdf","TSP, TOP"]
["MOD-031-2","MOD","MOD-031","Demand and Energy Data","2015-11-05","Approved","2015-11-19","2016-03-18","2016-10-01","2021-03-31","Retired","Demand and Energy Data","http://www.nerc.com/pa/Stand/Reliability Standards/MOD-031-2.pdf","PC, PA, BA, RP, LSE, DP"]
["MOD-031-3","MOD","MOD-031","Demand and Energy Data","2020-01-23","Approved","2020-02-26","2020-06-25","2021-04-01",null,"Effective","Demand and Energy Data","https://www.nerc.com/pa/Stand/Project201707StandardsAlignmentwithRegistration/MOD-031-3%20Project%202017%2007%20Clean_January2020.pdf","DP, RP, BA, TP, PC, PA"]
["MOD-032-1","MOD","MOD-032","Data for Power System Modeling and Analysis","2014-02-06","Approved","2014-02-28","2014-06-28","2015-07-01",null,"Effective","Data for Power System Modeling and Analysis","http://www.nerc.com/pa/Stand/Reliability Standards/MOD-032-1.pdf","TP, PC, TSP, TO, RP, LSE, GO, BA"]
["MOD-033-2","MOD","MOD-033","Steady-State and Dynamic System Model Validation","2020-01-23","Approved","2020-02-26","2020-06-25","2020-04-01",null,"Effective","Steady-State and Dynamic System Model Validation","https://www.nerc.com/pa/Stand/Project201707StandardsAlignmentwithRegistration/MOD-033-2%20Project%202017%2007%20Clean_January2020.pdf","TOP, RC, PC"]
["NUC-001-3","NUC","NUC-001","Nuclear Plant Interface Coordination","2014-08-14","Approved","2014-09-25","2015-01-13","2016-04-01","2021-03-31","Retired","Nuclear Plant Interface Coordination","http://www.nerc.com/pa/Stand/Reliability Standards/NUC-001-3.pdf","GOP, TSP, TP, TOP, TO, RC, PC, LSE, GO, DP, BA"]
["NUC-001-4","NUC","NUC-001","Nuclear Plant Interface Coordination","2020-01-23","Approved","2020-02-21","2020-06-25","2021-04-01",null,"Effective","Nuclear Plant Interface Coordination","https://www.nerc.com/pa/Stand/Project201707StandardsAlignmentwithRegistration/NUC-001-4%20Project%202017%2007%20Clean_January2020.pdf","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP"]
["PER-003-2","PER","PER-003","Operating Personnel Credentials","2018-05-10","Approved","2018-07-26","2018-11-24","2019-07-01",null,"Effective","Operating Personnel Credentials","https://www.nerc.com/pa/Stand/Reliability%20Standards/PER-003-2.pdf","RC, TOP, BA"]
["PER-005-2","PER","PER-005","Operations Personnel Training","2014-02-06","Approved","2014-03-12","2014-07-10","2016-10-01",null,"Effective","Operations Personnel Training","http://www.nerc.com/pa/Stand/Reliability Standards/PER-005-2.pdf","TOP, RC, BA, TO, GOP"]
["PER-006-1","PER","PER-006","Specific Training for Personnel","2016-08-11","Approved","2016-09-15","2017-01-12","2021-04-01",null,"Effective","Specific Training for Personnel","http://www.nerc.com/pa/Stand/Reliability Standards/PER-006-1.pdf","GOP"]
["PRC-002-2","PRC","PRC-002","Disturbance Monitoring and Reporting Requirements","2014-11-13","Approved","2014-12-19","2015-04-19","2016-07-01",null,"Effective","Disturbance Monitoring and Reporting Requirements","http://www.nerc.com/pa/Stand/Reliability Standards/PRC-002-2.pdf","TO, GO, RE, PC"]
["PRC-002-3","PRC","PRC-002","Disturbance Monitoring and Reporting Requirements","2021-05-13","Approved","2021-07-07","2021-11-04","2024-04-01",null,"Future Effective","Disturbance Monitoring and Reporting Requirements","https://www.nerc.com/pa/Stand/Project%20201509%20Establish%20and%20Communicate%20System%20Op/2015-09_PRC-002-3_clean.pdf","TO, RC, GO"]
["PRC-004-5(i)","PRC","PRC-004","Protection System Misoperation Identification and Correction","2015-06-22","Approved","1900-01-01","1900-01-02","2017-04-02","2021-03-31","Retired","Protection System Misoperation Identification and Correction","http://www.nerc.com/pa/Stand/Reliability Standards/PRC-004-5(i).pdf","TO, GO, DP"]
["PRC-004-6","PRC","PRC-004","Protection System Misoperation Identification and Correction","2019-05-09","Approved","2019-05-09","2020-06-25","2021-04-20",null,"Effective","Protection System Misoperation Identification and Correction","https://www.nerc.com/pa/Stand/Reliability%20Standards/PRC-004-6.pdf","DP, GO, TO"]
["PRC-005-1.1b","PRC","PRC-005","Transmission and Generation Protection System Maintenance and Testing","2012-05-09","Approved","2012-09-06","2013-01-04","2013-11-25","2027-03-31","Effective","Transmission and Generation Protection System Maintenance and Testing","http://www.nerc.com/pa/Stand/Reliability Standards/PRC-005-1.1b.pdf","TO, GO, DP"]
["PRC-005-6","PRC","PRC-005","Protection System , Automatic Reclosing and Sudden Pressure Relaying Maintenance","2015-11-05","Approved","2015-11-20","2016-03-18","2016-03-18",null,"Effective","Protection System , Automatic Reclosing and Sudden Pressure Relaying Maintenance","http://www.nerc.com/pa/Stand/Reliability Standards/PRC-005-6.pdf","TO, GO, DP"]
["PRC-006-3","PRC","PRC-006","Automatic Underfrequency Load Shedding",null,"Approved","1900-01-01","1900-01-02","2017-10-01","2021-03-31","Retired","Automatic Underfrequency Load Shedding","http://www.nerc.com/pa/Stand/Reliability Standards/PRC-006-3.pdf","PC, TO, DP"]
["PRC-006-4","PRC","PRC-006","Automatic Underfrequency Load Shedding","2020-01-23","Approved","2020-02-26","2020-06-25","2021-04-01",null,"Effective","Automatic Underfrequency Load Shedding","https://www.nerc.com/pa/Stand/Project201707StandardsAlignmentwithRegistration/PRC-006-4%20Project%202017%2007%20Clean_January2020.pdf","DP, TO, PC"]
["PRC-006-NPCC-2","PRC","PRC-006","Automatic Underfrequency Load Shedding","2019-11-05","Approved","2020-01-24","2020-05-03","2020-07-01",null,"Effective","Automatic Underfrequency Load Shedding","https://www.nerc.com/pa/Stand/Reliability%20Standards/PRC-006-NPCC-2.pdf","PC, GO, TO, DP, NERC"]
["PRC-008-0","PRC","PRC-008","Implementation and Documentation of Underfrequency Load Shedding Equipment Maintenance Program","2005-02-08","Approved","1900-01-01","1900-01-02","2005-02-08","2027-03-31","Effective","Implementation and Documentation of Underfrequency Load Shedding Equipment Maintenance Program","http://www.nerc.com/pa/Stand/Reliability Standards/PRC-008-0.pdf","TO, DP"]
["PRC-010-2","PRC","PRC-010","Undervoltage Load Shedding","2015-05-07","Approved","2015-06-16","2015-10-13","2017-04-02",null,"Effective","Undervoltage Load Shedding","http://www.nerc.com/pa/Stand/Reliability Standards/PRC-010-2.pdf","TP, PC, TO, DP"]
["PRC-011-0","PRC","PRC-011","Undervoltage Load Shedding System Maintenance and Testing","2005-02-08","Approved","1900-01-01","1900-01-02","2005-02-08","2027-03-31","Effective","Undervoltage Load Shedding System Maintenance and Testing","http://www.nerc.com/pa/Stand/Reliability Standards/PRC-011-0.pdf","TO, DP"]
["PRC-012-0","PRC","PRC-012","Special Protection System Review Procedure","2005-02-08","Not Approved","1900-01-01","1900-01-02",null,null,"Never Came Into Effect in Ontario","Special Protection System Review Procedure","http://www.nerc.com/pa/Stand/Reliability Standards/PRC-012-0.pdf","RRO"]
["PRC-012-1","PRC","PRC-012","Remedial Action Scheme Review Procedure","2014-11-13","Not Approved","2015-02-10","2015-06-10",null,null,"Never Came Into Effect in Ontario","Remedial Action Scheme Review Procedure","http://www.nerc.com/pa/Stand/Reliability Standards/PRC-012-1.pdf","RRO"]
["PRC-012-2","PRC","PRC-012","Remedial Action Schemes","2016-05-05","Approved","2016-08-15","2016-12-13","2021-01-01",null,"Effective","Remedial Action Schemes","http://www.nerc.com/pa/Stand/Prjct201005_3RmdialActnSchmsPhase3ofPrtctnSystmsDL/PRC-012-2_AHM_reviewed_04292015.pdf","PC, RC, TO, GO, DP"]
["PRC-013-1","PRC","PRC-013","Remedial Action Scheme Database","2014-11-13","Not Approved","2015-02-10","2015-06-10",null,null,"Never Came Into Effect in Ontario",{"$f":"HYPERLINK(M99,D99)","v":"Remedial Action Scheme Database"},"http://www.nerc.com/pa/Stand/Reliability Standards/PRC-013-1.pdf","RRO"]
["PRC-014-1","PRC","PRC-014","Remedial Action Scheme Assessment","2014-11-13","Not Approved","2015-02-10","2015-06-10",null,null,"Never Came Into Effect in Ontario","Remedial Action Scheme Assessment","http://www.nerc.com/pa/Stand/Reliability Standards/PRC-014-1.pdf","RRO"]
["PRC-017-1","PRC","PRC-017","Remedial Action Scheme Maintenance and Testing","2014-11-13","Approved","2015-02-10","2015-06-10","2017-04-01","2027-03-31","Effective","Remedial Action Scheme Maintenance and Testing","http://www.nerc.com/pa/Stand/Reliability Standards/PRC-017-1.pdf","TO, GO, DP"]
["PRC-018-1","PRC","PRC-018","Disturbance Monitoring Equipment Installation and Data Reporting","2006-08-02","Approved","1900-01-01","1900-01-02","2007-02-02","2022-06-30","Retired","Disturbance Monitoring Equipment Installation and Data Reporting","http://www.nerc.com/pa/Stand/Reliability Standards/PRC-018-1.pdf","TO, GO"]
["PRC-019-2","PRC","PRC-019","Coordination of Generating Unit or Plant Capabilities, Voltage\nRegulating Controls, and Protection","2015-02-12","Approved","2015-03-18","2015-07-16","2016-07-01",null,"Effective","Coordination of Generating Unit or Plant Capabilities, Voltage\nRegulating Controls, and Protection","http://www.nerc.com/pa/Stand/Reliability Standards/PRC-019-2.pdf","TO, GO"]
["PRC-023-2(i)","PRC","PRC-023","Transmission Relay Loadability","2014-11-13","Not Approved","2015-02-10","2015-06-10",null,null,"Never Came Into Effect in Ontario","Transmission Relay Loadability",null,"TO, GO, DP, PC"]
["PRC-023-4","PRC","PRC-023","Transmission Relay Loadability","2014-11-13","Approved","2015-02-10","2015-06-10","2017-04-01",null,"Effective","Transmission Relay Loadability","http://www.nerc.com/pa/Stand/Reliability Standards/PRC-023-4.pdf","TO, GO, DP, PC"]
["PRC-023-5","PRC","PRC-023","Transmission Relay Loadability","2021-05-13","Approved","2021-07-07","2021-11-04","2024-04-01",null,"Future Effective","Transmission Relay Loadability","https://www.nerc.com/pa/Stand/Reliability Standards/PRC-023-5.pdf","TO, PC, GO, DP"]
["PRC-024-2","PRC","PRC-024","Generator Frequency and Voltage Protective Relay Settings","2015-02-12","Approved","2015-03-18","2015-07-16","2016-07-01","2022-09-30","Effective","Generator Frequency and Voltage Protective Relay Settings","http://www.nerc.com/pa/Stand/Reliability Standards/PRC-024-2.pdf","GO"]
["PRC-024-3","PRC","PRC-024","Frequency and Voltage Protection Settings for Generating Resources","2020-02-06","Approved","2020-04-13","2021-07-28","2022-10-01",null,"Future Effective","Frequency and Voltage Protection Settings for Generating Resources","https://www.nerc.com/pa/Stand/Reliability%20Standards/PRC-024-3.pdf","TO, PC, GO"]
["PRC-025-2","PRC","PRC-025","Generator Relay Loadability","2018-02-08","Approved","2018-03-29","2018-07-27","2018-10-01",null,"Effective","Generator Relay Loadability","https://www.nerc.com/pa/Stand/Reliability Standards/PRC-025-2.pdf","TO, GO, DP"]
["PRC-026-1","PRC","PRC-026","Relay Performance During Stable Power Swings","2014-12-17","Approved","2015-01-09","2015-05-10","2018-01-01",null,"Effective","Relay Performance During Stable Power Swings","http://www.nerc.com/pa/Stand/Reliability Standards/PRC-026-1.pdf","TO, PC, GO"]
["PRC-026-2","PRC","PRC-026","Relay Performance During Stable Power Swings","2021-05-13","Approved","2021-07-07","2021-11-04","2024-04-01",null,"Future Effective","Relay Performance During Stable Power Swings","https://www.nerc.com/pa/Stand/Reliability Standards/PRC-026-2.pdf","TO, PC, GO"]
["PRC-027-1","PRC","PRC-027","Coordination of Protection Systems for Performance During Faults","2015-11-05","Approved","2016-09-14","2017-01-12","2021-04-01",null,"Effective","Coordination of Protection Systems for Performance During Faults","http://www.nerc.com/pa/Stand/Reliability Standards/PRC-027-1.pdf","TO, GO, DP"]
["TOP-001-4","TOP","TOP-001","Transmission Operations","2017-02-09","Approved","2017-03-20","2017-07-18","2018-10-01","2021-03-31","Retired","Transmission Operations","http://www.nerc.com/pa/Stand/Project 201601 Modifications to TOP and IRO Standa/TOP-001-4_rbs_clean_nov_27_2016.pdf","TOP, BA, GOP, DP"]
["TOP-001-5","TOP","TOP-001","Transmission Operations","2019-05-19","Approved","2019-05-26","2019-09-03","2021-04-01",null,"Effective","Transmission Operations","https://www.nerc.com/pa/Stand/Reliability%20Standards/TOP-001-5.pdf","GOP, DP, BA, TOP"]
["TOP-001-6","TOP","TOP-001","Transmission Operations","2021-05-13","Approved","2021-07-07","2021-11-04","2024-04-01",null,"Future Effective","Transmission Operations","http://www.nerc.com/pa/Stand/Reliability Standards/TOP-001-6.pdf","TOP, GOP, DP, BA"]
["TOP-002-4","TOP","TOP-002","Operations Planning","2014-11-13","Approved","2015-03-25","2015-07-23","2017-04-01",null,"Effective","Operations Planning","http://www.nerc.com/pa/Stand/Reliability Standards/TOP-002-4.pdf","TOP, BA"]
["TOP-003-3","TOP","TOP-003","Operational Reliability Data","2014-11-13","Approved","2015-03-25","2015-07-23","2017-01-01","2021-09-30","Retired","Operational Reliability Data","http://www.nerc.com/pa/Stand/Reliability Standards/TOP-003-3.pdf","TOP, BA, TO, LSE, GOP, GO, DP"]
["TOP-003-4","TOP","TOP-003","Operational Reliability Data","2020-01-23","Approved","2020-01-23","2020-05-22","2021-04-01",null,"Effective","Operational Reliability Data","https://www.nerc.com/pa/Stand/Project201707StandardsAlignmentwithRegistration/TOP-003-4%20Project%202017%2007%20Clean_January2020.pdf","DP, GOP, GO, BA, TOP, TO"]
["TOP-003-5","TOP","TOP-003","Operational Reliability Data","2021-10-06","Approved","2021-10-07","2022-02-02","2023-10-01",null,"Future Effective","Operational Reliability Data","https://www.nerc.com/pa/Stand/Project%20201906%20Cold%20Weather%20DL/2019-06_TOP-003-4_Clean_05182021.pdf"]
["TOP-010-1(i)","TOP","TOP-010","Real-time Reliability Monitoring and Analysis Capabilities","2016-02-11","Approved","2016-06-01","2016-09-29","2018-04-01",null,"Effective","Real-time Reliability Monitoring and Analysis Capabilities","https://www.nerc.com/pa/Stand/Reliability%20Standards/TOP-010-1(i).pdf","TOP, BA"]
["TPL-001-4","TPL","TPL-001","Transmission System Planning Performance Requirements",null,"Approved","2013-03-05","2013-07-03","2015-01-01",null,"Effective","Transmission System Planning Performance Requirements","http://www.nerc.com/pa/Stand/Reliability Standards/TPL-001-4.pdf","TP, PC, PA"]
["TPL-001-5","TPL","TPL-001","Transmission System Planning Performance Requirements","2018-11-07","Approved","2018-12-12","2019-04-11","2022-07-01",null,"Effective","Transmission System Planning Performance Requirements","https://www.nerc.com/pa/Stand/Project_201510%20Single%20Points%20of%20Failure_TPL001_DL/TPL-001-5_clean_10112018.pdf","PA, PC, TP"]
["TPL-007-2","TPL","TPL-007","Transmission System Planned Performance for Geomagnetic Disturbance Events","2017-11-09","Approved","2018-03-05","2018-03-26",null,null,"Never Came Into Effect in Ontario","Transmission System Planned Performance for Geomagnetic Disturbance Events","http://www.nerc.com/pa/Stand/Reliability Standards/TPL-007-2.pdf","TP, PC, TO, GO"]
["TPL-007-4","TPL","TPL-007","Transmission System Planned Performance for Geomagnetic Disturbance Events","2020-02-06","Approved","2020-03-05","2020-06-12","2020-10-01",null,"Effective","Transmission System Planned Performance for Geomagnetic Disturbance Events","https://www.nerc.com/pa/Stand/Reliability%20Standards/tpl-007-4.PDF","TP, PC, TO, GO"]
["VAR-001-5","VAR","VAR-001","Voltage and Reactive Control","2018-08-16","Approved","2018-09-11","2019-01-08","2019-04-01",null,"Effective","Voltage and Reactive Control","https://www.nerc.com/pa/Stand/Reliability%20Standards/VAR-001-5.pdf","TOP, GOP, GO"]
["VAR-002-4.1","VAR","VAR-002","Generator Operation for Maintaining Network Voltage Schedules","2017-08-10","Approved","1900-01-01","1900-01-02","2017-09-26",null,"Effective","Generator Operation for Maintaining Network Voltage Schedules","http://www.nerc.com/pa/Stand/Reliability Standards/VAR-002-4.1.pdfhttp:/www.nerc.com/pa/Stand/Reliability Standards/VAR-002-4.1.pdf","GO"]

{"sheet":"NERCRequirementsMapping","index":2,"n_rows":4116,"n_cols":20,"rows_kept":4116}
[null,"Standards",{"$nulls":3},"Status",{"$nulls":3},"Risk Assessment"]
["ID","Standard Number","Req't .","Duplicate Req't","Text of Requirement","Requirement Enforcement Date","Requirement Inactive Date","Status In Ontario","Existing Internal Control","Violation Risk Factors","Violation Likelihood (VL) Based on Inherent Risk","Risk Score Based on Inherent Risk","Violation Likelihood (VL) Based On Residual Risk","Risk Score Based on Residual Risk","Functional Entities","Applicable to MP Registered FE?","IESO","IESO Notes","HydroOne","Hydro One Notes"]
[25205,"BAL-001-2","R1.",null,"The Responsible Entity shall operate such that the Control Performance Standard 1 (CPS1), calculated in accordance with Attachment 1, is greater than or equal to 100 percent for the applicable Interconnection in which it operates for each preceding 12 consecutive calendar month period, evaluated monthly. [Violation Risk Factor: Medium] [Time Horizon: Real‐time Operations]","2016-07-01",null,"Effective","Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","PSE, BA","No",false,null,false]
[25206,"BAL-001-2","R2.",null,"Each Balancing Authority shall operate such that its clock‐minute average of Reporting ACE does not exceed its clock‐minute Balancing Authority ACE Limit (BAAL) for more than 30 consecutive clock‐minutes, calculated in accordance with Attachment 2, for the applicable Interconnection in which the Balancing Authority operates.[Violation Risk Factor: Medium] [Time Horizon: Real‐time Operations]","2016-07-01",null,"Effective","Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","BA","No",false,null,false]
[25227,"BAL-002-1a","R1.",null,"Each Balancing Authority shall have access to and/or operate Contingency Reserve to respond\nto Disturbances. Contingency Reserve may be supplied from generation, controllable load\nresources, or coordinated adjustments to Interchange Schedules.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[25228,"BAL-002-1a","R1.1.",null,"A Balancing Authority may elect to fulfill its Contingency Reserve obligations by\nparticipating as a member of a Reserve Sharing Group. In such cases, the Reserve\nSharing Group shall have the same responsibilities and obligations as each Balancing\nAuthority with respect to monitoring and meeting the requirements of Standard BAL-\n002.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[25229,"BAL-002-1a","R2.",null,"Each Regional Reliability Organization, sub-Regional Reliability Organization or Reserve\nSharing Group shall specify its Contingency Reserve policies, including:",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","RSG, RRO","No",false,null,false]
[25230,"BAL-002-1a","R2.1.",null,"The minimum reserve requirement for the group.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","RSG, RRO","No",false,null,false]
[25231,"BAL-002-1a","R2.2.",null,"Its allocation among members.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RSG, RRO","No",false,null,false]
[25232,"BAL-002-1a","R2.3.",null,"The permissible mix of Operating Reserve – Spinning and Operating Reserve – Supplemental that may be included in Contingency Reserve.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RSG, RRO","No",false,null,false]
[25233,"BAL-002-1a","R2.4.",null,"The procedure for applying Contingency Reserve in practice.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RSG, RRO","No",false,null,false]
[25234,"BAL-002-1a","R2.5.",null,"The limitations, if any, upon the amount of interruptible load that may be included.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RSG, RRO","No",false,null,false]
[25235,"BAL-002-1a","R2.6.",null,"The same portion of resource capacity (e.g. reserves from jointly owned generation) shall not be counted more than once as Contingency Reserve by multiple Balancing\nAuthorities.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","RSG, RRO","No",false,null,false]
[25236,"BAL-002-1a","R3.",null,"Each Balancing Authority or Reserve Sharing Group shall activate sufficient Contingency Reserve to comply with the DCS.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[25237,"BAL-002-1a","R3.1.",null,"As a minimum, the Balancing Authority or Reserve Sharing Group shall carry at least 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.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[25238,"BAL-002-1a","R4.",null,"A Balancing Authority or Reserve Sharing Group shall meet the Disturbance Recovery Criterion within the Disturbance Recovery Period for 100% of Reportable Disturbances. The Disturbance Recovery Criterion is:",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[25239,"BAL-002-1a","R4.1.",null,"A Balancing Authority shall return its ACE to zero if its ACE just prior to the Reportable 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-\nDisturbance value.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[25240,"BAL-002-1a","R4.2.",null,"The default Disturbance Recovery Period is 15 minutes after the start of a Reportable Disturbance.",null,null,"Retired",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[25241,"BAL-002-1a","R5.",null,"Each Reserve Sharing Group shall comply with the DCS. A Reserve Sharing Group 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\nbut 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:",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RSG","No",false,null,false]
[25242,"BAL-002-1a","R5.1.",null,"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\nsharing have been fully implemented, and within the Disturbance Recovery Period.",null,null,"Retired",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RSG","No",false,null,false]
[25243,"BAL-002-1a","R5.2.",null,"The Reserve Sharing Group reviews each member’s ACE in response to the activation of reserves. To be in compliance, a member’s 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.",null,null,"Retired",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RSG","No",false,null,false]
[25244,"BAL-002-1a","R6.",null,"A Balancing Authority or Reserve Sharing Group shall fully restore its Contingency Reserves within the Contingency Reserve Restoration Period for its Interconnection.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[25245,"BAL-002-1a","R6.1.",null,"The Contingency Reserve Restoration Period begins at the end of the Disturbance Recovery Period.",null,null,"Retired",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[25246,"BAL-002-1a","R6.2.",null,"The default Contingency Reserve Restoration Period is 90 minutes.",null,null,"Retired",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[29665,"BAL-002-2(i)","R1.",null,"The Responsible Entity experiencing a Reportable Balancing Contingency Event shall: [Violation Risk Factor: High] [Time Horizon: Real-time Operations]","2018-01-01","2019-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[29666,"BAL-002-2(i)","R1.1.",null,"within the Contingency Event Recovery Period, demonstrate recovery by returning its Reporting ACE to at least the recovery value of: \r\n\r\n• zero (if its Pre-Reporting Contingency Event ACE Value was positive or equal to zero); however, any Balancing Contingency Event that occurs during the Contingency Event Recovery Period shall reduce the required recovery: (i) beginning at the time of, and (ii) by the magnitude of, such individual Balancing Contingency Event, \r\nor, \r\n• its Pre-Reporting Contingency Event ACE Value (if its Pre-Reporting Contingency Event ACE Value was negative); however, any Balancing Contingency Event that occurs during the Contingency Event Recovery Period shall reduce the required recovery: (i) beginning at the time of, and (ii) by the magnitude of, such individual Balancing Contingency Event.","2018-01-01","2019-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[29667,"BAL-002-2(i)","R1.2.",null,"document all Reportable Balancing Contingency Events using CR Form 1.","2018-01-01","2019-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[29668,"BAL-002-2(i)","R1.3.",null,"deploy Contingency Reserve, within system constraints, to respond to all Reportable Balancing Contingency Events, however, it is not subject to compliance with Requirement R1 part 1.1 if:","2018-01-01","2019-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[29669,"BAL-002-2(i)","R1.3.1.",null,"the Responsible Entity:• is a Balancing Authority experiencing a Reliability Coordinator declared Energy Emergency Alert Level or is a Reserve Sharing Group whose member, or members, are experiencing a Reliability Coordinator declared Energy Emergency Alert level, and• is utilizing its Contingency Reserve to mitigate an operating emergency in accordance with its emergency Operating Plan, and• has depleted its Contingency Reserve to a level below its Most Severe Single Contingency\r\nor,","2018-01-01","2019-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[29670,"BAL-002-2(i)","R1.3.2.",null,"the Responsible Entity experiences:• multiple Contingencies where the combined MW loss exceeds its Most Severe Single Contingency and that are defined as a single Balancing Contingency Event, or • multiple Balancing Contingency Events within the sum of the time periods defined by the Contingency Event Recovery Period and Contingency Reserve Restoration Period whose combined magnitude exceeds the Responsible Entity's Most Severe Single Contingency.","2018-01-01","2019-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[29671,"BAL-002-2(i)","R2.",null,"Each Responsible Entity shall develop, review and maintain annually, and implement an Operating Process as part of its Operating Plan to determine its Most Severe Single Contingency and make preparations to have Contingency Reserve equal to, or greater than the Responsible Entity’s Most Severe Single Contingency available for maintaining system reliability. [Violation Risk Factor: High] [Time Horizon: Operations Planning]","2018-01-01","2019-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[29672,"BAL-002-2(i)","R3.",null,"Each Responsible Entity, following a Reportable Balancing Contingency Event, shall restore its Contingency Reserve to at least its Most Severe Single Contingency, before the end of the Contingency Reserve Restoration Period, but any Balancing Contingency Event that occurs before the end of a Contingency Reserve Restoration Period resets the beginning of the Contingency Event Recovery Period. [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]","2018-01-01","2019-06-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[29745,"BAL-002-3","R1.",null,"The Responsible Entity experiencing a Reportable Balancing Contingency Event shall: [Violation Risk Factor: High] [Time Horizon: Real-time Operations]","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[29746,"BAL-002-3","R1.1.",null,"within the Contingency Event Recovery Period, demonstrate recovery by returning its Reporting ACE to at least the recovery value of:\r\n zero (if its Pre-Reporting Contingency Event ACE Value was positive or equal to zero); however, any Balancing Contingency Event that occurs during the Contingency Event Recovery Period shall reduce the required recovery: (i) beginning at the time of, and (ii) by the magnitude of, such individual Balancing Contingency Event,\r\nor,\r\n its Pre-Reporting Contingency Event ACE Value (if its Pre-Reporting Contingency Event ACE Value was negative); however, any Balancing Contingency Event that occurs during the Contingency Event Recovery Period shall reduce the required recovery: (i) beginning at the time of, and (ii) by the magnitude of, such individual Balancing Contingency Event.","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[29747,"BAL-002-3","R1.2.",null,"document all Reportable Balancing Contingency Events using CR Form 1.","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA, RSG","No",false,null,false]
[29748,"BAL-002-3","R1.3.",null,"deploy Contingency Reserve, within system constraints, to respond to all Reportable Balancing Contingency Events, however, it is not subject to compliance with Requirement R1 part 1.1 if the Responsible Entity:","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA, RSG","No",false,null,false]
[29749,"BAL-002-3","R1.3.1.",null,"is (i) a Balancing Authority or (ii) a Reserve Sharing Group with at least one member that:\r\n is experiencing a Reliability Coordinator declared Energy Emergency Alert Level, and\r\n is utilizing its Contingency Reserve to mitigate an operating emergency in accordance with its emergency Operating Plan, and\r\n has depleted its Contingency Reserve to a level below its Most Severe Single Contingency, and\r\n has, during communications with its Reliability Coordinator in accordance with the Energy Emergency Alert procedures, (i) notified the Reliability Coordinator of the conditions described in the preceding two bullet points preventing the Responsible Entity from complying with Requirement R1 part 1.1, and (ii) provided the Reliability Coordinator with an ACE recovery plan, including target recovery time\r\nor,","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[29750,"BAL-002-3","R1.3.2.",null,"the Responsible Entity experiences:\r\n multiple Contingencies where the combined MW loss exceeds its Most Severe Single Contingency and that are defined as a single Balancing Contingency Event, or\r\n multiple Balancing Contingency Events within the sum of the time periods defined by the Contingency Event Recovery Period and Contingency Reserve Restoration Period whose combined magnitude exceeds the Responsible Entity's Most Severe Single Contingency.","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[29751,"BAL-002-3","R2.",null,"Each Responsible Entity shall develop, review and maintain annually, and implement an Operating Process as part of its Operating Plan to determine its Most Severe Single Contingency and make preparations to have Contingency Reserve equal to, or greater than the Responsible Entity’s Most Severe Single Contingency available for maintaining system reliability. [Violation Risk Factor: High] [Time Horizon: Operations Planning]","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RSG, BA","No",false,null,false]
[29752,"BAL-002-3","R3.",null,"Each Responsible Entity, following a Reportable Balancing Contingency Event, shall restore its Contingency Reserve to at least its Most Severe Single Contingency, before the end of the Contingency Reserve Restoration Period, but any Balancing Contingency Event that occurs before the end of a Contingency Reserve Restoration Period resets the beginning of the Contingency Event Recovery Period. [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA, RSG","No",false,null,false]
[25272,"BAL-003-1.1","R1.",null,"Each Frequency Response Sharing Group (FRSG) or Balancing Authority that is not a member of a FRSG shall achieve an annual Frequency Response Measure (FRM) (as calculated and reported in accordance with Attachment A) that is equal to or more negative than its Frequency Response Obligation (FRO) to ensure that sufficient Frequency Response is provided by each FRSG or BA that is not a member of a FRSG to maintain Interconnection Frequency Response equal to or more negative than the Interconnection Frequency Response Obligation. [Risk Factor: High][Time Horizon: Real-time Operations]","2016-04-01","2020-12-31","Retired",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[25273,"BAL-003-1.1","R2.",null,"Each Balancing Authority that is a member of a multiple Balancing Authority Interconnection and is not receiving Overlap Regulation Service and uses a fixed Frequency Bias Setting shall implement the Frequency Bias Setting determined in accordance with Attachment A, as validated by the ERO, into its Area Control Error (ACE) calculation during the implementation period specified by the ERO and shall use this Frequency Bias Setting until directed to change by the ERO. [Risk Factor: Medium ][Time Horizon: Operations Planning]","2015-11-13","2020-12-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[25274,"BAL-003-1.1","R3.",null,"Each Balancing Authority that is a member of a multiple Balancing Authority Interconnection and is not receiving Overlap Regulation Service and is utilizing a variable Frequency Bias Setting shall maintain a Frequency Bias Setting that is: [Risk Factor: Medium ][Time Horizon: Operations Planning]","2015-11-13","2020-12-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[25275,"BAL-003-1.1","R3.1.",null,"Less than zero at all times, and","2015-11-13","2020-12-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[25276,"BAL-003-1.1","R3.2.",null,"Equal to or more negative than its Frequency Response Obligation when Frequency varies from 60 Hz by more than +/- 0.036 Hz.","2015-11-13","2020-12-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[25277,"BAL-003-1.1","R4.",null,"Each Balancing Authority that is performing Overlap Regulation Service shall modify its Frequency Bias Setting in its ACE calculation, in order to represent the Frequency Bias Setting for the combined Balancing Authority Area, to be equivalent to either: [Risk Factor: Medium ][Time Horizon: Operations Planning]\n\n● The sum of the Frequency Bias Settings as shown on FRS Form 1 and FRS Form 2 for the participating Balancing Authorities as validated by the ERO, or\n● The Frequency Bias Setting shown on FRS Form 1 and FRS Form 2 for the entirety of the participating Balancing Authorities’ Areas.","2015-11-13","2020-12-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[30235,"BAL-003-2","R1.",null,"Each Frequency Response Sharing Group (FRSG) or Balancing Authority that is not a\r\nmember of a FRSG shall achieve an annual Frequency Response Measure (FRM) (as\r\ncalculated and reported in accordance with Attachment A) that is equal to or more\r\nnegative than its Frequency Response Obligation (FRO) to ensure that sufficient\r\nFrequency Response is provided by each FRSG or BA that is not a member of a FRSG\r\nto maintain Interconnection Frequency Response equal to or more negative than the\r\nInterconnection Frequency Response Obligation. [Risk Factor: High][Time Horizon:\r\nReal-time Operations]","2021-01-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[30236,"BAL-003-2","R2.",null,"Each Balancing Authority that is a member of a multiple Balancing Authority\r\nInterconnection and is not receiving Overlap Regulation Service and uses a fixed\r\nFrequency Bias Setting shall implement the Frequency Bias Setting determined in \r\nBAL-003-2 – Frequency Response and Frequency Bias Setting\r\nPage 2 of 13\r\naccordance with Attachment A, as validated by the ERO, into its Area Control Error\r\n(ACE) calculation during the implementation period specified by the ERO and shall use\r\nthis Frequency Bias Setting until directed to change by the ERO. [Risk Factor:\r\nMedium][Time Horizon: Operations Planning]","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30237,"BAL-003-2","R3.",null,"Each Balancing Authority that is a member of a multiple Balancing Authority\r\nInterconnection and is not receiving Overlap Regulation Service and is utilizing a\r\nvariable Frequency Bias Setting shall maintain a Frequency Bias Setting that is: [Risk\r\nFactor: Medium][Time Horizon: Operations Planning]","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30238,"BAL-003-2","R3.1.",null,"Less than zero at all times, and","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30239,"BAL-003-2","R3.2.",null,"Equal to or more negative than its Frequency Response Obligation when\r\nFrequency varies from 60 Hz by more than +/- 0.036 Hz.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30240,"BAL-003-2","R4.",null,"Each Balancing Authority that is performing Overlap Regulation Service shall modify\r\nits Frequency Bias Setting in its ACE calculation, in order to represent the Frequency\r\nBias Setting for the combined Balancing Authority Area, to be equivalent to either:\r\n[Risk Factor: Medium][Time Horizon: Operations Planning]\r\n The sum of the Frequency Bias Settings as shown on FRS Form 1 and FRS Form 2\r\nfor the participating Balancing Authorities as validated by the ERO, or\r\n The Frequency Bias Setting shown on FRS Form 1 and FRS Form 2 for the entirety\r\nof the participating Balancing Authorities’ Areas.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[25309,"BAL-005-1","R1.",null,"The Balancing Authority shall use a design scan rate of no more than six seconds in acquiring data necessary to calculate Reporting ACE.","2019-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[25310,"BAL-005-1","R2.",null,"A Balancing Authority that is unable to calculate Reporting ACE for more than 30-consecutive minutes shall notify its Reliability Coordinator within 45 minutes of the beginning of the inability to calculate Reporting ACE.","2019-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[25311,"BAL-005-1","R3.",null,"Each Balancing Authority shall use frequency metering equipment for the calculation of Reporting ACE:","2019-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[25312,"BAL-005-1","R3.1.",null,"that is available a minimum of 99.95% for each calendar year; and,","2019-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[25313,"BAL-005-1","R3.2.",null,"with a minimum accuracy of 0.001 Hz.","2019-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[25314,"BAL-005-1","R4.",null,"The Balancing Authority shall make available to the operator information associated with Reporting ACE including, but not limited to, quality flags indicating missing or invalid data.","2019-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[25315,"BAL-005-1","R5.",null,"Each Balancing Authority’s system used to calculate Reporting ACE shall be available a minimum of 99.5% of each calendar year.","2019-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[25316,"BAL-005-1","R6.",null,"Each Balancing Authority that is within a multiple Balancing Authority Interconnection shall implement an Operating Process to identify and mitigate errors affecting the accuracy of scan rate data used in the calculation of Reporting ACE for each Balancing Authority Area.","2019-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[25317,"BAL-005-1","R7.",null,"Each Balancing Authority shall ensure that each Tie-Line, Pseudo-Tie, and Dynamic Schedule with an Adjacent Balancing Authority is equipped with:","2019-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[25318,"BAL-005-1","R7.1.",null,"a common source to provide information to both Balancing Authorities for the scan rate values used in the calculation of Reporting ACE; and,","2019-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[25319,"BAL-005-1","R7.2.",null,"a time synchronized common source to determine hourly megawatt-hour values agreed-upon to aid in the identification and mitigation of errors.","2019-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[25347,"CIP-002-3(i)","R1.",null,"Critical Asset Identification Method — The Responsible Entity shall identify and document a risk-based assessment methodology to use to identify its Critical Assets.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25348,"CIP-002-3(i)","R1.1.",null,"The Responsible Entity shall maintain documentation describing its risk-based assessment methodology that includes procedures and evaluation criteria.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25349,"CIP-002-3(i)","R1.2.",null,"The risk-based assessment shall consider the following assets:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25350,"CIP-002-3(i)","R1.2.1.",null,"Control centers and backup control centers performing the functions of the entities listed in the Applicability section of this standard.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25351,"CIP-002-3(i)","R1.2.2.",null,"Transmission substations that support the reliable operation of the Bulk Electric System.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25352,"CIP-002-3(i)","R1.2.3.",null,"Generation resources that support the reliable operation of the Bulk Electric System.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25353,"CIP-002-3(i)","R1.2.4.",null,"Systems and facilities critical to system restoration, including blackstart generators and substations in the electrical path of transmission lines used for initial system restoration.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25354,"CIP-002-3(i)","R1.2.5.",null,"Systems and facilities critical to automatic load shedding under a common control system capable of shedding 300 MW or more.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25355,"CIP-002-3(i)","R1.2.6.",null,"Remedial Action Schemes that support the reliable operation of the Bulk Electric System.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25356,"CIP-002-3(i)","R1.2.7.",null,"Any additional assets that support the reliable operation of the Bulk Electric System that the Responsible Entity deems appropriate to include in its assessment.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25357,"CIP-002-3(i)","R2.",null,"Critical Asset Identification — The Responsible Entity shall develop a list of its identified Critical Assets determined through an annual application of the risk-based assessment methodology required in R1.  The Responsible Entity shall review this list at least annually, and update it as necessary.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25358,"CIP-002-3(i)","R3.",null,"Critical Cyber Asset Identification— Using the list of Critical Assets developed pursuant to Requirement R2, the Responsible Entity shall develop a list of associated Critical Cyber Assets essential to the operation of the Critical Asset. Examples at control centers and backup control centers include systems and facilities at master and remote sites that provide monitoring and control, automatic generation control, real-time power system modeling, and real-time inter-utility data exchange. The Responsible Entity shall review this list at least annually, and update it as necessary. For the purpose of Standard CIP-002-3(i), Critical Cyber Assets are further qualified to be those having at least one of the following characteristics:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25359,"CIP-002-3(i)","R3.1.",null,"The Cyber Asset uses a routable protocol to communicate outside the Electronic Security Perimeter; or,",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25360,"CIP-002-3(i)","R3.2.",null,"The Cyber Asset uses a routable protocol within a control center; or,",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25361,"CIP-002-3(i)","R3.3.",null,"The Cyber Asset is dial-up accessible.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25362,"CIP-002-3(i)","R4.",null,"Annual Approval — The senior manager or delegate(s) shall approve annually the risk-based assessment methodology, the list of Critical Assets and the list of Critical Cyber Assets. Based on Requirements R1, R2, and R3 the Responsible Entity may determine that it has no Critical Assets or Critical Cyber Assets. The Responsible Entity shall keep a signed and dated record of the senior manager or delegate(s)’s approval of the risk-based assessment methodology, the list of Critical Assets and the list of Critical Cyber Assets (even if such lists are null.)",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25395,"CIP-002-3(i)b","R1.",null,"Critical Asset Identification Method — The Responsible Entity shall identify and document a risk-based assessment methodology to use to identify its Critical Assets.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25396,"CIP-002-3(i)b","R1.1.",null,"The Responsible Entity shall maintain documentation describing its risk-based assessment methodology that includes procedures and evaluation criteria.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25397,"CIP-002-3(i)b","R1.2.",null,"The risk-based assessment shall consider the following assets:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25398,"CIP-002-3(i)b","R1.2.1.",null,"Control centers and backup control centers performing the functions of the entities listed in the Applicability section of this standard.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25399,"CIP-002-3(i)b","R1.2.2.",null,"Transmission substations that support the reliable operation of the Bulk Electric System.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25400,"CIP-002-3(i)b","R1.2.3.",null,"Generation resources that support the reliable operation of the Bulk Electric System.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25401,"CIP-002-3(i)b","R1.2.4.",null,"Systems and facilities critical to system restoration, including blackstart generators and substations in the electrical path of transmission lines used for initial system restoration.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25402,"CIP-002-3(i)b","R1.2.5.",null,"Systems and facilities critical to automatic load shedding under a common control system capable of shedding 300 MW or more.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25403,"CIP-002-3(i)b","R1.2.6.",null,"Remedial Action Schemes that support the reliable operation of the Bulk Electric System.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25404,"CIP-002-3(i)b","R1.2.7.",null,"Any additional assets that support the reliable operation of the Bulk Electric System that the Responsible Entity deems appropriate to include in its assessment.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25405,"CIP-002-3(i)b","R2.",null,"Critical Asset Identification — The Responsible Entity shall develop a list of its identified Critical Assets determined through an annual application of the risk-based assessment methodology required in R1. The Responsible Entity shall review this list at least annually, and update it as necessary.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25406,"CIP-002-3(i)b","R3.",null,"Critical Cyber Asset Identification — Using the list of Critical Assets developed pursuant to Requirement R2, the Responsible Entity shall develop a list of associated Critical Cyber Assets essential to the operation of the Critical Asset. Examples at control centers and backup control centers include systems and facilities at master and remote sites that provide monitoring and control, automatic generation control, real-time power system modeling, and real-time inter-utility data exchange. The Responsible Entity shall review this list at least annually, and update it as necessary. For the purpose of Standard CIP-002-3(i)b, Critical Cyber Assets are further qualified to be those having at least one of the following characteristics:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25407,"CIP-002-3(i)b","R3.1.",null,"The Cyber Asset uses a routable protocol to communicate outside the Electronic Security Perimeter; or,",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25408,"CIP-002-3(i)b","R3.2.",null,"The Cyber Asset uses a routable protocol within a control center; or,",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25409,"CIP-002-3(i)b","R3.3.",null,"The Cyber Asset is dial-up accessible.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",false,null,true]
[25410,"CIP-002-3(i)b","R4.",null,"Annual Approval — The senior manager or delegate(s) shall approve annually the risk-based assessment methodology, the list of Critical Assets and the list of Critical Cyber Assets. Based on Requirements R1, R2, and R3 the Responsible Entity may determine that it has no Critical Assets or Critical Cyber Assets. The Responsible Entity shall keep a signed and dated record of the senior manager or delegate(s)’s approval of the risk-based assessment methodology, the list of Critical Assets and the list of Critical Cyber Assets (even if such lists are null.)",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25363,"CIP-002-3a","R1.",null,"Critical Asset Identification Method —The Responsible Entity shall identify and document a risk-based assessment methodology to use to identify its Critical Assets.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25364,"CIP-002-3a","R1.1.",null,"The Responsible Entity shall maintain documentation describing its risk-based assessment methodology that includes procedures and evaluation criteria.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25365,"CIP-002-3a","R1.2.",null,"The risk-based assessment shall consider the following assets:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25366,"CIP-002-3a","R1.2.1.",null,"Control centers and backup control centers performing the functions of the entities listed in the Applicability section of this standard.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25367,"CIP-002-3a","R1.2.2.",null,"Transmission substations that support the reliable operation of the Bulk Electric System",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25368,"CIP-002-3a","R1.2.3.",null,"Generation resources that support the reliable operation of the Bulk Electric System",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25369,"CIP-002-3a","R1.2.4.",null,"Systems and facilities critical to system restoration, including blackstart generators and substations in the electrical path of transmission lines used for initial system restoration.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25370,"CIP-002-3a","R1.2.5.",null,"Systems and facilities critical to automatic load shedding under a common control system capable of shedding 300 MW or more.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25371,"CIP-002-3a","R1.2.6.",null,"Special Protection Systems that support the reliable operation of the Bulk Electric System.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25372,"CIP-002-3a","R1.2.7.",null,"Any additional assets that support the reliable operation of the Bulk Electric System that the Responsible Entity deems appropriate to include in its assessment.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25373,"CIP-002-3a","R2.",null,"Critical Asset Identification — The Responsible Entity shall develop a list of its identified Critical Assets determined through an annual application of the risk-based assessment methodology required in R1. The Responsible Entity shall review this list at least annually, and update it as necessary.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TSP, TOP, TO, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25374,"CIP-002-3a","R3.",null,"Critical Cyber Asset Identification — Using the list of Critical Assets developed pursuant to Requirement R2, the Responsible Entity shall develop a list of associated Critical Cyber Assets essential to the operation of the Critical Asset. Examples at control centers and backup control centers include systems and facilities at master and remote sites that provide monitoring and control, automatic generation control, real-time power system modeling, and real-time interutility data exchange. The Responsible Entity shall review this list at least annually, and update it as necessary. For the purpose of Standard CIP-002-3, Critical Cyber Assets are further qualified to be those having at least one of the following characteristics:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TSP, TOP, TO, RC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25375,"CIP-002-3a","R3.1.",null,"The Cyber Asset uses a routable protocol to communicate outside the Electronic Security Perimeter; or,",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25376,"CIP-002-3a","R3.2.",null,"The Cyber Asset uses a routable protocol within a control center; or,",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25377,"CIP-002-3a","R3.3.",null,"The Cyber Asset is dial-up accessible.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25378,"CIP-002-3a","R4.",null,"Annual Approval —The senior manager or delegate(s) shall approve annually the risk-based assessment methodology, the list of Critical Assets and the list of Critical Cyber Assets. Based on Requirements R1, R2, and R3 the Responsible Entity may determine that it has no Critical Assets or Critical Cyber Assets. The Responsible Entity shall keep a signed and dated record of the senior manager or delegate(s)’s approval of the risk-based assessment methodology, the list of Critical Assets and the list of Critical Cyber Assets (even if such lists are null.)",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25379,"CIP-002-3b","R1.",null,"Critical Asset Identification Method — The Responsible Entity shall identify and document a risk-based assessment methodology to use to identify its Critical Assets.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, TO, RE, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25380,"CIP-002-3b","R1.1.",null,"The Responsible Entity shall maintain documentation describing its risk-based assessment methodology that includes procedures and evaluation criteria.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, TO, RE, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25381,"CIP-002-3b","R1.2.",null,"The risk-based assessment shall consider the following assets:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, TO, RE, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25382,"CIP-002-3b","R1.2.1.",null,"Control centers and backup control centers performing the functions of the entities listed in the Applicability section of this standard.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, TO, RE, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25383,"CIP-002-3b","R1.2.2.",null,"Transmission substations that support the reliable operation of the Bulk Electric System.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, TO, RE, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25384,"CIP-002-3b","R1.2.3.",null,"Generation resources that support the reliable operation of the Bulk Electric System.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, TO, RE, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25385,"CIP-002-3b","R1.2.4.",null,"Systems and facilities critical to system restoration, including blackstart generators and substations in the electrical path of transmission lines used for initial system restoration.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, TO, RE, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25386,"CIP-002-3b","R1.2.5.",null,"Systems and facilities critical to automatic load shedding under a common control system capable of shedding 300 MW or more.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, TO, RE, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25387,"CIP-002-3b","R1.2.6.",null,"Special Protection Systems that support the reliable operation of the Bulk Electric System.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, TO, RE, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25388,"CIP-002-3b","R1.2.7.",null,"Any additional assets that support the reliable operation of the Bulk Electric System that the Responsible Entity deems appropriate to include in its assessment.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, TO, RE, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25389,"CIP-002-3b","R2.",null,"Critical Asset Identification — The Responsible Entity shall develop a list of its identified Critical Assets determined through an annual application of the risk-based assessment methodology required in R1. The Responsible Entity shall review this list at least annually, and update it as necessary.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, TO, RE, RC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25390,"CIP-002-3b","R3.",null,"Critical Cyber Asset Identification — Using the list of Critical Assets developed pursuant to Requirement R2, the Responsible Entity shall develop a list of associated Critical Cyber Assets essential to the operation of the Critical Asset. Examples at control centers and backup control centers include systems and facilities at master and remote sites that provide monitoring and control, automatic generation control, real-time power system modeling, and real-time inter-utility data exchange. The Responsible Entity shall review this list at least annually, and update it as necessary. For the purpose of Standard CIP-002-3, Critical Cyber Assets are further qualified to be those having at least one of the following characteristics:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, TO, RE, RC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25391,"CIP-002-3b","R3.1.",null,"The Cyber Asset uses a routable protocol to communicate outside the Electronic Security Perimeter; or,",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, TO, RE, RC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25392,"CIP-002-3b","R3.2.",null,"The Cyber Asset uses a routable protocol within a control center; or,",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, TO, RE, RC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25393,"CIP-002-3b","R3.3.",null,"The Cyber Asset is dial-up accessible.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, TO, RE, RC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25394,"CIP-002-3b","R4.",null,"Annual Approval — The senior manager or delegate(s) shall approve annually the risk-based assessment methodology, the list of Critical Assets and the list of Critical Cyber Assets. Based on Requirements R1, R2, and R3 the Responsible Entity may determine that it has no Critical Assets or Critical Cyber Assets. The Responsible Entity shall keep a signed and dated record of the senior manager or delegate(s)’s approval of the risk-based assessment methodology, the list of Critical Assets and the list of Critical Cyber Assets (even if such lists are null.)",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, TO, RE, RC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25411,"CIP-002-4","R1.",null,"Critical Asset Identification — The Responsible Entity shall develop a list of its identified Critical Assets determined through an annual application of the criteria contained in CIP-002-4 Attachment 1 – Critical Asset Criteria. The Responsible Entity shall update this list as necessary, and review it at least annually.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25412,"CIP-002-4","R2.",null,"Critical Cyber Asset Identification— Using the list of Critical Assets developed pursuant to Requirement R1, the Responsible Entity shall develop a list of associated Critical Cyber Assets essential to the operation of the Critical Asset. The Responsible Entity shall update this list as necessary, and review it at least annually.\nFor each group of generating units (including nuclear generation) at a single plant location identified in Attachment 1, criterion 1.1, the only Cyber Assets that must be considered are those shared Cyber Assets that could, within 15 minutes, adversely impact the reliable operation of any combination of units that in aggregate equal or exceed Attachment 1, criterion 1.1.\nFor the purpose of Standard CIP-002-4, Critical Cyber Assets are further qualified to be those having at least one of the following characteristics:\n• The Cyber Asset uses a routable protocol to communicate outside the Electronic Security Perimeter; or,\n• The Cyber Asset uses a routable protocol within a control center; or,\n• The Cyber Asset is dial-up accessible.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25413,"CIP-002-4","R3.",null,"Annual Approval —The senior manager or delegate(s) shall approve annually the list of Critical Assets and the list of Critical Cyber Assets. Based on Requirements R1 and R2 the Responsible Entity may determine that it has no Critical Assets or Critical Cyber Assets. The Responsible Entity shall keep a signed and dated record of the senior manager or delegate(s)’s approval of the list of Critical Assets and the list of Critical Cyber Assets (even if such lists are null.)",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25414,"CIP-002-4a","R1.",null,"Critical Asset Identification — The Responsible Entity shall develop a list of its identified Critical Assets determined through an annual application of the criteria contained in CIP-002-4 Attachment 1 – Critical Asset Criteria. The Responsible Entity shall update this list as necessary, and review it at least annually.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25415,"CIP-002-4a","R2.",null,"Critical Cyber Asset Identification— Using the list of Critical Assets developed pursuant to Requirement R1, the Responsible Entity shall develop a list of associated Critical Cyber Assets essential to the operation of the Critical Asset. The Responsible Entity shall update this list as necessary, and review it at least annually.\nFor each group of generating units (including nuclear generation) at a single plant location identified in Attachment 1, criterion 1.1, the only Cyber Assets that must be considered are those shared Cyber Assets that could, within 15 minutes, adversely impact the reliable operation of any combination of units that in aggregate equal or exceed Attachment 1, criterion 1.1.\nFor the purpose of Standard CIP-002-4, Critical Cyber Assets are further qualified to be those having at least one of the following characteristics:\n• The Cyber Asset uses a routable protocol to communicate outside the Electronic Security Perimeter; or,\n• The Cyber Asset uses a routable protocol within a control center; or,\n• The Cyber Asset is dial-up accessible.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25416,"CIP-002-4a","R3.",null,"Annual Approval —The senior manager or delegate(s) shall approve annually the list of Critical Assets and the list of Critical Cyber Assets. Based on Requirements R1 and R2 the Responsible Entity may determine that it has no Critical Assets or Critical Cyber Assets. The Responsible Entity shall keep a signed and dated record of the senior manager or delegate(s)’s approval of the list of Critical Assets and the list of Critical Cyber Assets (even if such lists are null.)",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25417,"CIP-002-5","R1.",null,"Each Responsible Entity shall implement a process that considers each of the following assets for purposes of parts 1.1 through 1.3: [Violation Risk Factor: High][Time Horizon: Operations Planning]\ni.Control Centers and backup Control Centers;\nii.Transmission stations and substations;\niii.Generation resources;\niv.Systems and facilities critical to system restoration, including Blackstart Resources and Cranking Paths and initial switching requirements;\nv.Special Protection Systems that support the reliable operation of the Bulk Electric System; and\nvi.For Distribution Providers, Protection Systems specified in Applicability section 4.2.1 above.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,false]
[25418,"CIP-002-5","R1.1.",null,"1.1. Identify each of the high impact BES Cyber Systems according to Attachment 1, Section 1, if any, at each asset;",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,false]
[25419,"CIP-002-5","R1.2.",null,"1.2. Identify each of the medium impact BES Cyber Systems according to Attachment 1, Section 2, if any, at each asset; and",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,false]
[25420,"CIP-002-5","R1.3.",null,"1.3. Identify each asset that contains a low impact BES Cyber System according to Attachment 1, Section 3, if any (a discrete list of low impact BES Cyber Systems is not required).",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,false]
[25421,"CIP-002-5","R2.",null,"The Responsible Entity shall: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,false]
[25422,"CIP-002-5","R2.1.",null,"2.1 Review the identifications in Requirement R1 and its parts (and update them if there are changes identified) at least once every 15 calendar months, even if it has no identified items in Requirement R1, and",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,false]
[25423,"CIP-002-5","R2.2.",null,"2.2 Have its CIP Senior Manager or delegate approve the identifications required by Requirement R1 at least once every 15 calendar months, even if it has no identified items in Requirement R1.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,false]
[25424,"CIP-002-5.1","R1.",null,"Each Responsible Entity shall implement a process that considers each of the following assets for purposes of parts 1.1 through 1.3: [Violation Risk Factor: High][Time Horizon: Operations Planning]\ni.Control Centers and backup Control Centers;\nii.Transmission stations and substations;\niii.Generation resources;\niv.Systems and facilities critical to system restoration, including Blackstart Resources and Cranking Paths and initial switching requirements;\nv.Special Protection Systems that support the reliable operation of the Bulk Electric System; and\nvi.For Distribution Providers, Protection Systems specified in Applicability section 4.2.1 above.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,false]
[25425,"CIP-002-5.1","R1.1.",null,"Identify each of the high impact BES Cyber Systems according to Attachment 1, Section 1, if any, at each asset;",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,false]
[25426,"CIP-002-5.1","R1.2.",null,"Identify each of the medium impact BES Cyber Systems according to Attachment 1, Section 2, if any, at each asset; and",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,false]
[25427,"CIP-002-5.1","R1.3.",null,"Identify each asset that contains a low impact BES Cyber System according to Attachment 1, Section 3, if any (a discrete list of low impact BES Cyber Systems is not required).",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,false]
[25428,"CIP-002-5.1","R2.",null,"The Responsible Entity shall: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,false]
[25429,"CIP-002-5.1","R2.1.",null,"Review the identifications in Requirement R1 and its parts (and update them if there are changes identified) at least once every 15 calendar months, even if it has no identified items in Requirement R1, and",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,false]
[25430,"CIP-002-5.1","R2.2.",null,"Have its CIP Senior Manager or delegate approve the identifications required by Requirement R1 at least once every 15 calendar months, even if it has no identified items in Requirement R1.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,false]
[25550,"CIP-002-5.1a","R1.",null,"Each Responsible Entity shall implement a process that considers each of the following assets for purposes of parts 1.1 through 1.3: [Violation Risk Factor: High][Time Horizon: Operations Planning]\ni.Control Centers and backup Control Centers;\nii.Transmission stations and substations;\niii.Generation resources;\niv.Systems and facilities critical to system restoration, including Blackstart Resources and Cranking Paths and initial switching requirements;\nv.Special Protection Systems that support the reliable operation of the Bulk Electric System; and\nvi.For Distribution Providers, Protection Systems specified in Applicability section 4.2.1 above.",null,null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25551,"CIP-002-5.1a","R1.1.",null,"Identify each of the high impact BES Cyber Systems according to Attachment 1, Section 1, if any, at each asset;",null,null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25552,"CIP-002-5.1a","R1.2.",null,"Identify each of the medium impact BES Cyber Systems according to Attachment 1, Section 2, if any, at each asset; and",null,null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25553,"CIP-002-5.1a","R1.3.",null,"Identify each asset that contains a low impact BES Cyber System according to Attachment 1, Section 3, if any (a discrete list of low impact BES Cyber Systems is not required).",null,null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25554,"CIP-002-5.1a","R2.",null,"The Responsible Entity shall: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]",null,null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25555,"CIP-002-5.1a","R2.1.",null,"Review the identifications in Requirement R1 and its parts (and update them if there are changes identified) at least once every 15 calendar months, even if it has no identified items in Requirement R1, and",null,null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25556,"CIP-002-5.1a","R2.2.",null,"Have its CIP Senior Manager or delegate approve the identifications required by Requirement R1 at least once every 15 calendar months, even if it has no identified items in Requirement R1.",null,null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25449,"CIP-003-3a","R1.",null,"Cyber Security Policy — The Responsible Entity shall document and implement a cyber security policy that represents management’s commitment and ability to secure its Critical Cyber Assets. The Responsible Entity shall, at minimum, ensure the following:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25450,"CIP-003-3a","R1.1.",null,"The cyber security policy addresses the requirements in Standards CIP-002-3 through CIP-009-3, including provision for emergency situations.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25451,"CIP-003-3a","R1.2.",null,"The cyber security policy is readily available to all personnel who have access to, or are responsible for, Critical Cyber Assets. (Retirement approved by FERC effective January 21, 2014.)",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25452,"CIP-003-3a","R1.3.",null,"Annual review and approval of the cyber security policy by the senior manager assigned pursuant to R2.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25453,"CIP-003-3a","R2.",null,"Leadership — The Responsible Entity shall assign a single senior manager with overall responsibility and authority for leading and managing the entity’s implementation of, and adherence to, Standards CIP-002-3 through CIP-009-3.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25454,"CIP-003-3a","R2.1.",null,"The senior manager shall be identified by name, title, and date of designation.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25455,"CIP-003-3a","R2.2.",null,"Changes to the senior manager must be documented within thirty calendar days of the effective date.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25456,"CIP-003-3a","R2.3.",null,"Where allowed by Standards CIP-002-3 through CIP-009-3, the senior manager may delegate authority for specific actions to a named delegate or delegates. These delegations shall be documented in the same manner as R2.1 and R2.2, and approved by the senior manager.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25457,"CIP-003-3a","R2.4.",null,"The senior manager or delegate(s), shall authorize and document any exception from the requirements of the cyber security policy.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25507,"CIP-003-3a","R3.",null,"Exceptions — Instances where the Responsible Entity cannot conform to its cyber security policy must be documented as exceptions and authorized by the senior manager or delegate(s). (Retirement approved by FERC effective January 21, 2014.)",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25508,"CIP-003-3a","R3.1.",null,"Exceptions to the Responsible Entity’s cyber security policy must be documented within thirty days of being approved by the senior manager or delegate(s). (Retirement approved by FERC effective January 21, 2014.)",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25509,"CIP-003-3a","R3.2.",null,"Documented exceptions to the cyber security policy must include an explanation as to why the exception is necessary and any compensating measures. (Retirement approved by FERC effective January 21, 2014.)",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25510,"CIP-003-3a","R3.3.",null,"Authorized exceptions to the cyber security policy must be reviewed and approved annually by the senior manager or delegate(s) to ensure the exceptions are still required and valid. Such review and approval shall be documented. (Retirement approved by FERC effective January 21, 2014.)",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25511,"CIP-003-3a","R4.",null,"Information Protection — The Responsible Entity shall implement and document a program to identify, classify, and protect information associated with Critical Cyber Assets.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25512,"CIP-003-3a","R4.1.",null,"The Critical Cyber Asset information to be protected shall include, at a minimum and regardless of media type, operational procedures, lists as required in Standard CIP- 002-3, network topology or similar diagrams, floor plans of computing centers that contain Critical Cyber Assets, equipment layouts of Critical Cyber Assets, disaster recovery plans, incident response plans, and security configuration information.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25513,"CIP-003-3a","R4.2.",null,"The Responsible Entity shall classify information to be protected under this program based on the sensitivity of the Critical Cyber Asset information. (Retirement approved by FERC effective January 21, 2014.)",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25514,"CIP-003-3a","R4.3.",null,"The Responsible Entity shall, at least annually, assess adherence to its Critical Cyber Asset information protection program, document the assessment results, and implement an action plan to remediate deficiencies identified during the assessment.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25515,"CIP-003-3a","R5.",null,"Access Control — The Responsible Entity shall document and implement a program for managing access to protected Critical Cyber Asset information.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25516,"CIP-003-3a","R5.1.",null,"The Responsible Entity shall maintain a list of designated personnel who are responsible for authorizing logical or physical access to protected information.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25517,"CIP-003-3a","R5.1.1.",null,"Personnel shall be identified by name, title, and the information for which they are responsible for authorizing access.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25518,"CIP-003-3a","R5.1.2.",null,"The list of personnel responsible for authorizing access to protected information shall be verified at least annually.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25519,"CIP-003-3a","R5.2.",null,"The Responsible Entity shall review at least annually the access privileges to protected information to confirm that access privileges are correct and that they correspond with the Responsible Entity’s needs and appropriate personnel roles and responsibilities.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25520,"CIP-003-3a","R5.3.",null,"The Responsible Entity shall assess and document at least annually the processes for controlling access privileges to protected information.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25521,"CIP-003-3a","R6.",null,"Change Control and Configuration Management — The Responsible Entity shall establish and document a process of change control and configuration management for adding, modifying, replacing, or removing Critical Cyber Asset hardware or software, and implement supporting configuration management activities to identify, control and document all entity or vendorrelated changes to hardware and software components of Critical Cyber Assets pursuant to the change control process.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25522,"CIP-003-4","R1.",null,"Cyber Security Policy —The Responsible Entity shall document and implement a cyber security policy that represents management’s commitment and ability to secure its Critical Cyber Assets. The Responsible Entity shall, at minimum, ensure the following:",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25523,"CIP-003-4","R1.1.",null,"The cyber security policy addresses the requirements in Standards CIP-002-4 through CIP-009-4, including provision for emergency situations.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25524,"CIP-003-4","R1.2.",null,"The cyber security policy is readily available to all personnel who have access to, or are responsible for, Critical Cyber Assets.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25525,"CIP-003-4","R1.3.",null,"Annual review and approval of the cyber security policy by the senior manager assigned pursuant to R2.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25526,"CIP-003-4","R2.",null,"Leadership —The Responsible Entity shall assign a single senior manager with overall responsibility and authority for leading and managing the entity’s implementation of, and adherence to, Standards CIP-002-4 through CIP-009-4.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25527,"CIP-003-4","R2.1.",null,"The senior manager shall be identified by name, title, and date of designation.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25528,"CIP-003-4","R2.2.",null,"Changes to the senior manager must be documented within thirty calendar days of the effective date.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25529,"CIP-003-4","R2.3.",null,"Where allowed by Standards CIP-002-4 through CIP-009-4, the senior manager may delegate authority for specific actions to a named delegate or delegates. These delegations shall be documented in the same manner as R2.1 and R2.2, and approved by the senior manager.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25530,"CIP-003-4","R2.4.",null,"The senior manager or delegate(s), shall authorize and document any exception from the requirements of the cyber security policy.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25531,"CIP-003-4","R3.",null,"Exceptions — Instances where the Responsible Entity cannot conform to its cyber security policy must be documented as exceptions and authorized by the senior manager or delegate(s).",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25532,"CIP-003-4","R3.1.",null,"Exceptions to the Responsible Entity’s cyber security policy must be documented within thirty days of being approved by the senior manager or delegate(s).",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25533,"CIP-003-4","R3.2.",null,"Documented exceptions to the cyber security policy must include an explanation as to why the exception is necessary and any compensating measures.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25534,"CIP-003-4","R3.3.",null,"Authorized exceptions to the cyber security policy must be reviewed and approved annually by the senior manager or delegate(s) to ensure the exceptions are still required and valid. Such review and approval shall be documented.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25535,"CIP-003-4","R4.",null,"Information Protection —The Responsible Entity shall implement and document a program to identify, classify, and protect information associated with Critical Cyber Assets.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25536,"CIP-003-4","R4.1.",null,"The Critical Cyber Asset information to be protected shall include, at a minimum and regardless of media type, operational procedures, lists as required in standard CIP-002-4, network topology or similar diagrams, floor plans of computing centers that contain Critical Cyber Assets, equipment layouts of Critical Cyber Assets, disaster recovery plans, incident response plans, and security configuration information.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25537,"CIP-003-4","R4.2.",null,"The Responsible Entity shall classify information to be protected under this program based on the sensitivity of the Critical Cyber Asset information.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25538,"CIP-003-4","R4.3.",null,"The Responsible Entity shall, at least annually, assess adherence to its Critical Cyber Asset information protection program, document the assessment results, and implement an action plan to remediate deficiencies identified during the assessment.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25539,"CIP-003-4","R5.",null,"Access Control —The Responsible Entity shall document and implement a program for managing access to protected Critical Cyber Asset information.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25540,"CIP-003-4","R5.1.",null,"The Responsible Entity shall maintain a list of designated personnel who are responsible for authorizing logical or physical access to protected information.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25541,"CIP-003-4","R5.1.1.",null,"Personnel shall be identified by name, title, and the information for which they are responsible for authorizing access.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25542,"CIP-003-4","R5.1.2.",null,"The list of personnel responsible for authorizing access to protected information shall be verified at least annually.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25543,"CIP-003-4","R5.2.",null,"The Responsible Entity shall review at least annually the access privileges to protected information to confirm that access privileges are correct and that they correspond with the Responsible Entity’s needs and appropriate personnel roles and responsibilities.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25544,"CIP-003-4","R5.3.",null,"The Responsible Entity shall assess and document at least annually the processes for controlling access privileges to protected information.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25545,"CIP-003-4","R6.",null,"Change Control and Configuration Management — The Responsible Entity shall establish and document a process of change control and configuration management for adding, modifying, replacing, or removing Critical Cyber Asset hardware or software, and implement supporting configuration management activities to identify, control and document all entity or vendor-related changes to hardware and software components of Critical Cyber Assets pursuant to the change control process.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25546,"CIP-003-5","R1.",null,"Each Responsible Entity, for its high impact and medium impact BES Cyber Systems, shall review and obtain CIP Senior Manager approval at least once every 15 calendar months for one or more documented cyber security policies that collectively address the following topics: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]\n1.1 Personnel & training (CIP-004);\n1.2 Electronic Security Perimeters (CIP-005) including Interactive Remote Access;\n1.3 Physical security of BES Cyber Systems (CIP-006);\n1.4 System security management (CIP-007);\n1.5 Incident reporting and response planning (CIP-008);\n1.6 Recovery plans for BES Cyber Systems (CIP-009);\n1.7 Configuration change management and vulnerability assessments (CIP-010);\n1.8 Information protection (CIP-011); and\n1.9 Declaring and responding to CIP Exceptional Circumstances.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25547,"CIP-003-5","R2.",null,"Each Responsible Entity for its assets identified in CIP-002-5, Requirement R1, Part R1.3, shall implement, in a manner that identifies, assesses, and corrects deficiencies, one or more documented cyber security policies that collectively address the following topics, and review and obtain CIP Senior Manager approval for those policies at least once every 15 calendar months: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]\n2.1 Cyber security awareness;\n2.2 Physical security controls;\n2.3 Electronic access controls for external routable protocol connections and Dial-up Connectivity; and\n2.4 Incident response to a Cyber Security Incident.\nAn inventory, list, or discrete identification of low impact BES Cyber Systems or their BES Cyber Assets is not required.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25548,"CIP-003-5","R3.",null,"Each Responsible Entity shall identify a CIP Senior Manager by name and document any change within 30 calendar days of the change. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25549,"CIP-003-5","R4.",null,"The Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, a documented process to delegate authority, unless no delegations are used. Where allowed by the CIP Standards, the CIP Senior Manager may delegate authority for specific actions to a delegate or delegates. These delegations shall be documented, including the name or title of the delegate, the specific actions delegated, and the date of the delegation; approved by the CIP Senior Manager; and updated within 30 days of any change to the delegation. Delegation changes do not need to be reinstated with a change to the delegator. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25557,"CIP-003-6","R1.1.",null,"1.1 For its high impact and medium impact BES Cyber Systems, if any:\n1.1.1. Personnel and training (CIP-004);\n1.1.2. Electronic Security Perimeters (CIP-005) including Interactive Remote Access;\n1.1.3. Physical security of BES Cyber Systems (CIP-006);\n1.1.4. System security management (CIP-007);\n1.1.5. Incident reporting and response planning (CIP-008);\n1.1.6. Recovery plans for BES Cyber Systems (CIP-009);\n1.1.7. Configuration change management and vulnerability assessments (CIP-010);\n1.1.8. Information protection (CIP-011); and\n1.1.9. Declaring and responding to CIP Exceptional Circumstances.","2016-07-01","2019-12-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25558,"CIP-003-6","R1.2.",null,"1.2 For its assets identified in CIP-002 containing low impact BES Cyber Systems, if any:\n1.2.1. Cyber security awareness;\n1.2.2. Physical security controls;\n1.2.3. Electronic access controls for Low Impact External Routable Connectivity (LERC) and Dial-up Connectivity; and\n1.2.4. Cyber Security Incident response","2016-07-01","2019-12-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25559,"CIP-003-6","R2.",null,"Each Responsible Entity with at least one asset identified in CIP-002 containing low impact BES Cyber Systems shall implement one or more documented cyber security plan(s) for its low impact BES Cyber Systems that include the sections in Attachment 1. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]\nNote: An inventory, list, or discrete identification of low impact BES Cyber Systems or their BES Cyber Assets is not required. Lists of authorized users are not required.","2016-07-01","2019-12-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25560,"CIP-003-6","R3.",null,"Each Responsible Entity shall identify a CIP Senior Manager by name and document any change within 30 calendar days of the change. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2016-07-01","2019-12-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25561,"CIP-003-6","R4.",null,"The Responsible Entity shall implement a documented process to delegate authority, unless no delegations are used. Where allowed by the CIP Standards, the CIP Senior Manager may delegate authority for specific actions to a delegate or delegates. These delegations shall be documented, including the name or title of the delegate, the specific actions delegated, and the date of the delegation; approved by the CIP Senior Manager; and updated within 30 days of any change to the delegation. Delegation changes do not need to be reinstated with a change to the delegator. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2016-07-01","2019-12-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25562,"CIP-003-7","R1.",null,"Each Responsible Entity shall review and obtain CIP Senior Manager approval at least once every 15 calendar months for one or more documented cyber security policies that collectively address the following topics: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2020-01-01","2020-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25563,"CIP-003-7","R1.1.",null,"For its high impact and medium impact BES Cyber Systems, if any:\n1.1.1. Personnel and training (CIP-004);\n1.1.2. Electronic Security Perimeters (CIP-005) including Interactive Remote Access;\n1.1.3. Physical security of BES Cyber Systems (CIP-006);\n1.1.4. System security management (CIP-007);\n1.1.5. Incident reporting and response planning (CIP-008);\n1.1.6. Recovery plans for BES Cyber Systems (CIP-009);\n1.1.7. Configuration change management and vulnerability assessments (CIP-010);\n1.1.8. Information protection (CIP-011); and\n1.1.9. Declaring and responding to CIP Exceptional Circumstances.","2020-01-01","2020-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25564,"CIP-003-7","R1.2.",null,"For its assets identified in CIP-002 containing low impact BES Cyber Systems, if any:\n1.2.1. Cyber security awareness;\n1.2.2. Physical security controls;\n1.2.3. Electronic access controls;\n1.2.4. Cyber Security Incident response;\n1.2.5. Transient Cyber Assets and Removable Media malicious code risk mitigation; and\n1.2.6. Declaring and responding to CIP Exceptional Circumstances.","2020-01-01","2020-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25565,"CIP-003-7","R2.",null,"Each Responsible Entity with at least one asset identified in CIP-002 containing low impact BES Cyber Systems shall implement one or more documented cyber security plan(s) for its low impact BES Cyber Systems that include the sections in Attachment 1. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2020-01-01","2020-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25566,"CIP-003-7","R3.",null,"Each Responsible Entity shall identify a CIP Senior Manager by name and document any change within 30 calendar days of the change. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2020-01-01","2020-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25567,"CIP-003-7","R4.",null,"The Responsible Entity shall implement a documented process to delegate authority, unless no delegations are used. Where allowed by the CIP Standards, the CIP Senior Manager may delegate authority for specific actions to a delegate or delegates. These delegations shall be documented, including the name or title of the delegate, the specific actions delegated, and the date of the delegation; approved by the CIP Senior Manager; and updated within 30 days of any change to the delegation. Delegation changes do not need to be reinstated with a change to the delegator. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2020-01-01","2020-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[29893,"CIP-003-8","R1.",null,"Each Responsible Entity shall review and obtain CIP Senior Manager approval at least once every 15 calendar months for one or more documented cyber security policies that collectively address the following topics: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2020-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true]
[29894,"CIP-003-8","R1.1.",null,"For its high impact and medium impact BES Cyber Systems, if any:\n1.1.1. Personnel and training (CIP-004);\n1.1.2. Electronic Security Perimeters (CIP-005) including Interactive Remote Access;\n1.1.3. Physical security of BES Cyber Systems (CIP-006);\n1.1.4. System security management (CIP-007);\n1.1.5. Incident reporting and response planning (CIP-008);\n1.1.6. Recovery plans for BES Cyber Systems (CIP-009);\n1.1.7. Configuration change management and vulnerability assessments (CIP-010);\n1.1.8. Information protection (CIP-011); and\n1.1.9. Declaring and responding to CIP Exceptional Circumstances.","2020-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true]
[29895,"CIP-003-8","R1.2.",null,"For its assets identified in CIP-002 containing low impact BES Cyber Systems, if any:\n1.2.1. Cyber security awareness;\n1.2.2. Physical security controls;\n1.2.3. Electronic access controls;\n1.2.4. Cyber Security Incident response;\n1.2.5. Transient Cyber Assets and Removable Media malicious code risk mitigation; and\n1.2.6. Declaring and responding to CIP Exceptional Circumstances.","2020-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true]
[29896,"CIP-003-8","R2.",null,"Each Responsible Entity with at least one asset identified in CIP-002 containing low impact BES Cyber Systems shall implement one or more documented cyber security plan(s) for its low impact BES Cyber Systems that include the sections in Attachment 1. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2020-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true]
[29897,"CIP-003-8","R3.",null,"Each Responsible Entity shall identify a CIP Senior Manager by name and document any change within 30 calendar days of the change. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2020-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true]
[29898,"CIP-003-8","R4.",null,"The Responsible Entity shall implement a documented process to delegate authority, unless no delegations are used. Where allowed by the CIP Standards, the CIP Senior Manager may delegate authority for specific actions to a delegate or delegates. These delegations shall be documented, including the name or title of the delegate, the specific actions delegated, and the date of the delegation; approved by the CIP Senior Manager; and updated within 30 days of any change to the delegation. Delegation changes do not need to be reinstated with a change to the delegator. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2020-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true]
[25584,"CIP-004-4","R1.",null,"Awareness —The Responsible Entity shall establish, document, implement, and maintain a security awareness program to ensure personnel having authorized cyber or authorized unescorted physical access to Critical Cyber Assets receive on-going reinforcement in sound security practices. The program shall include security awareness reinforcement on at least a quarterly basis using mechanisms such as:                                                                         \n• Direct communications (e.g., emails, memos, computer based training, etc.);                                                             \n• Indirect communications (e.g., posters, intranet, brochures, etc.);\n• Management support and reinforcement (e.g., presentations, meetings, etc.).",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25585,"CIP-004-4","R2.",null,"Training —The Responsible Entity shall establish, document, implement, and maintain an annual cyber security training program for personnel having authorized cyber or authorized unescorted physical access to Critical Cyber Assets. The cyber security training program shall be reviewed annually, at a minimum, and shall be updated whenever necessary.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25586,"CIP-004-4","R2.1.",null,"This program will ensure that all personnel having such access to Critical Cyber Assets, including contractors and service vendors, are trained prior to their being granted such access except in specified circumstances such as an emergency.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25587,"CIP-004-4","R2.2.",null,"Training shall cover the policies, access controls, and procedures as developed for the Critical Cyber Assets covered by CIP-004-4, and include, at a minimum, the following required items appropriate to personnel roles and responsibilities:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25588,"CIP-004-4","R2.2.1.",null,"The proper use of Critical Cyber Assets;",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25589,"CIP-004-4","R2.2.2.",null,"Physical and electronic access controls to Critical Cyber Assets;",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25590,"CIP-004-4","R2.2.3.",null,"The proper handling of Critical Cyber Asset information; and,",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25591,"CIP-004-4","R2.2.4.",null,"Action plans and procedures to recover or re-establish Critical Cyber Assets and access thereto following a Cyber Security Incident.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25592,"CIP-004-4","R2.3.",null,"The Responsible Entity shall maintain documentation that training is conducted at least annually, including the date the training was completed and attendance records.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25593,"CIP-004-4","R3.",null,"Personnel Risk Assessment —The Responsible Entity shall have a documented personnel risk assessment program, in accordance with federal, state, provincial, and local laws, and subject to existing collective bargaining unit agreements, for personnel having authorized cyber or authorized unescorted physical access to Critical Cyber Assets. A personnel risk assessment shall be conducted pursuant to that program prior to such personnel being granted such access except in specified circumstances such as an emergency.\nThe personnel risk assessment program shall at a minimum include:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25594,"CIP-004-4","R3.1.",null,"The Responsible Entity shall ensure that each assessment conducted include, at least, identity verification (e.g., Social Security Number verification in the U.S.) and seven-year criminal check. The Responsible Entity may conduct more detailed reviews, as permitted by law and subject to existing collective bargaining unit agreements, depending upon the criticality of the position.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25595,"CIP-004-4","R3.2.",null,"The Responsible Entity shall update each personnel risk assessment at least every seven years after the initial personnel risk assessment or for cause.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25596,"CIP-004-4","R3.3.",null,"The Responsible Entity shall document the results of personnel risk assessments of its personnel having authorized cyber or authorized unescorted physical access to Critical Cyber Assets, and that personnel risk assessments of contractor and service vendor personnel with such access are conducted pursuant to Standard CIP-004-4.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25597,"CIP-004-4","R4.",null,"Access —The Responsible Entity shall maintain list(s) of personnel with authorized cyber or authorized unescorted physical access to Critical Cyber Assets, including their specific electronic and physical access rights to Critical Cyber Assets.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25458,"CIP-004-4","R4.1.",null,"The Responsible Entity shall review the list(s) of its personnel who have such access to Critical Cyber Assets quarterly, and update the list(s) within seven calendar days of any change of personnel with such access to Critical Cyber Assets, or any change in the access rights of such personnel. The Responsible Entity shall ensure access list(s) for contractors and service vendors are properly maintained.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25459,"CIP-004-4","R4.2.",null,"The Responsible Entity shall revoke such access to Critical Cyber Assets within 24 hours for personnel terminated for cause and within seven calendar days for personnel who no longer require such access to Critical Cyber Assets.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25460,"CIP-004-4a","R1.",null,"Awareness —The Responsible Entity shall establish, document, implement, and maintain a security awareness program to ensure personnel having authorized cyber or authorized unescorted physical access to Critical Cyber Assets receive on-going reinforcement in sound security practices. The program shall include security awareness reinforcement on at least a quarterly basis using mechanisms such as:\n• Direct communications (e.g., emails, memos, computer based training, etc.);\n• Indirect communications (e.g., posters, intranet, brochures, etc.);\n• Management support and reinforcement (e.g., presentations, meetings, etc.).",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25461,"CIP-004-4a","R2.",null,"Training —The Responsible Entity shall establish, document, implement, and maintain an annual cyber security training program for personnel having authorized cyber or authorized unescorted physical access to Critical Cyber Assets. The cyber security training program shall be reviewed annually, at a minimum, and shall be updated whenever necessary.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25462,"CIP-004-4a","R2.1.",null,"This program will ensure that all personnel having such access to Critical Cyber Assets, including contractors and service vendors, are trained prior to their being granted such access except in specified circumstances such as an emergency.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25463,"CIP-004-4a","R2.2.",null,"Training shall cover the policies, access controls, and procedures as developed for the Critical Cyber Assets covered by CIP-004-4, and include, at a minimum, the following required items appropriate to personnel roles and responsibilities:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25464,"CIP-004-4a","R2.2.1.",null,"The proper use of Critical Cyber Assets;",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25598,"CIP-004-4a","R2.2.2.",null,"Physical and electronic access controls to Critical Cyber Assets;",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25599,"CIP-004-4a","R2.2.3.",null,"The proper handling of Critical Cyber Asset information; and,",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25600,"CIP-004-4a","R2.2.4.",null,"Action plans and procedures to recover or re-establish Critical Cyber Assets and access thereto following a Cyber Security Incident.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25601,"CIP-004-4a","R2.3.",null,"The Responsible Entity shall maintain documentation that training is conducted at least annually, including the date the training was completed and attendance records.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25602,"CIP-004-4a","R3.",null,"Personnel Risk Assessment —The Responsible Entity shall have a documented personnel risk assessment program, in accordance with federal, state, provincial, and local laws, and subject to existing collective bargaining unit agreements, for personnel having authorized cyber or authorized unescorted physical access to Critical Cyber Assets. A personnel risk assessment shall be conducted pursuant to that program prior to such personnel being granted such access except in specified circumstances such as an emergency.\nThe personnel risk assessment program shall at a minimum include:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25603,"CIP-004-4a","R3.1.",null,"The Responsible Entity shall ensure that each assessment conducted include, at least, identity verification (e.g., Social Security Number verification in the U.S.) and seven-year criminal check. The Responsible Entity may conduct more detailed reviews, as permitted by law and subject to existing collective bargaining unit agreements, depending upon the criticality of the position.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25604,"CIP-004-4a","R3.2.",null,"The Responsible Entity shall update each personnel risk assessment at least every seven years after the initial personnel risk assessment or for cause.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25605,"CIP-004-4a","R3.3.",null,"The Responsible Entity shall document the results of personnel risk assessments of its personnel having authorized cyber or authorized unescorted physical access to Critical Cyber Assets, and that personnel risk assessments of contractor and service vendor personnel with such access are conducted pursuant to Standard CIP-004-4.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25606,"CIP-004-4a","R4.",null,"Access —The Responsible Entity shall maintain list(s) of personnel with authorized cyber or authorized unescorted physical access to Critical Cyber Assets, including their specific electronic and physical access rights to Critical Cyber Assets.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25607,"CIP-004-4a","R4.1.",null,"The Responsible Entity shall review the list(s) of its personnel who have such access to Critical Cyber Assets quarterly, and update the list(s) within seven calendar days of any change of personnel with such access to Critical Cyber Assets, or any change in the access rights of such personnel. The Responsible Entity shall ensure access list(s) for contractors and service vendors are properly maintained.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25608,"CIP-004-4a","R4.2.",null,"The Responsible Entity shall revoke such access to Critical Cyber Assets within 24 hours for personnel terminated for cause and within seven calendar days for personnel who no longer require such access to Critical Cyber Assets.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25609,"CIP-004-5","R1.",null,"Each Responsible Entity shall implement one or more documented processes that collectively include each of the applicable requirement parts in CIP‐004‐5 Table R1 – Security Awareness Program. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25610,"CIP-004-5","R2.",null,"Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, a cyber security training program(s) appropriate to individual roles, functions, or responsibilities that collectively includes each of the applicable requirement parts in CIP‐004‐5 Table R2 – Cyber Security Training Program. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25611,"CIP-004-5","R3.",null,"Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, one or more documented personnel risk assessment programs to attain and retain authorized electronic or authorized unescorted physical access to BES Cyber Systems that collectively include each of the applicable requirement parts in CIP‐004‐5 Table R3 – Personnel Risk Assessment Program. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning].",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25612,"CIP-004-5","R4.",null,"Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, one or more documented access management programs that collectively include each of the applicable requirement parts in CIP‐004‐5 Table R4 – Access Management Program. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning and Same Day\nOperations].",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25613,"CIP-004-5","R5.",null,"Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, one or more documented access revocation programs that collectively include each of the applicable requirement parts in CIP‐004‐5 Table R5 – Access Revocation. [Violation Risk Factor: Medium] [Time Horizon: Same Day Operations and Operations Planning].",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25614,"CIP-004-5.1","R1.",null,"Each Responsible Entity shall implement one or more documented processes that collectively include each of the applicable requirement parts in CIP-004-5.1 Table R1 – Security Awareness Program. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25615,"CIP-004-5.1","R2.",null,"Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, a cyber security training program(s) appropriate to individual roles, functions, or responsibilities that collectively includes each of the applicable requirement parts in CIP-004-5.1 Table R2 – Cyber Security Training Program. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25616,"CIP-004-5.1","R3.",null,"Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, one or more documented personnel risk assessment programs to attain and retain authorized electronic or authorized unescorted physical access to BES Cyber Systems that collectively include each of the applicable requirement parts in CIP-004-5.1 Table R3 – Personnel Risk Assessment Program. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning].",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25617,"CIP-004-5.1","R4.",null,"Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, one or more documented access management programs that collectively include each of the applicable requirement parts in CIP-004-5.1 Table R4 – Access Management Program. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning and Same Day Operations].",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25618,"CIP-004-5.1","R5.",null,"Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, one or more documented access revocation programs that collectively include each of the applicable requirement parts in CIP-004-5.1 Table R5 – Access Revocation. [Violation Risk Factor: Medium] [Time Horizon: Same Day Operations and Operations Planning].",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25619,"CIP-004-6","R1.",null,"Each Responsible Entity shall implement one or more documented processes that collectively include each of the applicable requirement parts in CIP-004-6 Table R1 – Security Awareness Program. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25620,"CIP-004-6","R2.",null,"Each Responsible Entity shall implement one or more cyber security training program(s) appropriate to individual roles, functions, or responsibilities that collectively includes each of the applicable requirement parts in CIP-004-6 Table R2 – Cyber Security Training Program. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25621,"CIP-004-6","R3.",null,"Each Responsible Entity shall implement one or more documented personnel risk assessment program(s) to attain and retain authorized electronic or authorized unescorted physical access to BES Cyber Systems that collectively include each of the applicable requirement parts in CIP-004-6 Table R3 – Personnel Risk Assessment Program. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning].","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25622,"CIP-004-6","R4.",null,"Each Responsible Entity shall implement one or more documented access management program(s) that collectively include each of the applicable requirement parts in CIP-004-6 Table R4 – Access Management Program. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning and Same Day Operations].","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25623,"CIP-004-6","R5.",null,"Each Responsible Entity shall implement one or more documented access revocation program(s) that collectively include each of the applicable requirement parts in CIP-004-6 Table R5 – Access Revocation. [Violation Risk Factor: Medium] [Time Horizon: Same Day Operations and Operations Planning].","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25654,"CIP-005-4a","R1.",null,"Electronic Security Perimeter —The Responsible Entity shall ensure that every Critical Cyber Asset resides within an Electronic Security Perimeter. The Responsible Entity shall identify and document the Electronic Security Perimeter(s) and all access points to the perimeter(s).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25655,"CIP-005-4a","R1.1.",null,"Access points to the Electronic Security Perimeter(s) shall include any externally connected communication end point (for example, dial-up modems) terminating at any device within the Electronic Security Perimeter(s).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25656,"CIP-005-4a","R1.2.",null,"For a dial-up accessible Critical Cyber Asset that uses a non-routable protocol, the Responsible Entity shall define an Electronic Security Perimeter for that single access point at the dial-up device.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25657,"CIP-005-4a","R1.3.",null,"Communication links connecting discrete Electronic Security Perimeters shall not be considered part of the Electronic Security Perimeter. However, end points of these communication links within the Electronic Security Perimeter(s) shall be considered access points to the Electronic Security Perimeter(s).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25658,"CIP-005-4a","R1.4.",null,"Any non-critical Cyber Asset within a defined Electronic Security Perimeter shall be identified and protected pursuant to the requirements of Standard CIP-005-4a.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25659,"CIP-005-4a","R1.5.",null,"Cyber Assets used in the access control and/or monitoring of the Electronic Security Perimeter(s) shall be afforded the protective measures as a specified in Standard CIP-003-4; Standard CIP-004-4 Requirement R3; Standard CIP-005-4a Requirements R2 and R3; Standard CIP-006-4c Requirement R3; Standard CIP-007-4 Requirements R1 and R3 through R9; Standard CIP-008-4; and Standard CIP-009-4.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25660,"CIP-005-4a","R1.6.",null,"The Responsible Entity shall maintain documentation of Electronic Security Perimeter(s), all interconnected Critical and non-critical Cyber Assets within the Electronic Security Perimeter(s), all electronic access points to the Electronic Security Perimeter(s) and the Cyber Assets deployed for the access control and monitoring of these access points.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25661,"CIP-005-4a","R2.",null,"Electronic Access Controls — The Responsible Entity shall implement and document the organizational processes and technical and procedural mechanisms for control of electronic access at all electronic access points to the Electronic Security Perimeter(s).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25662,"CIP-005-4a","R2.1.",null,"These processes and mechanisms shall use an access control model that denies access by default, such that explicit access permissions must be specified.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25663,"CIP-005-4a","R2.2.",null,"At all access points to the Electronic Security Perimeter(s), the Responsible Entity shall enable only ports and services required for operations and for monitoring Cyber Assets within the Electronic Security Perimeter, and shall document, individually or by specified grouping, the configuration of those ports and services.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25664,"CIP-005-4a","R2.3.",null,"The Responsible Entity shall implement and maintain a procedure for securing dial-up access to the Electronic Security Perimeter(s).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25665,"CIP-005-4a","R2.4.",null,"Where external interactive access into the Electronic Security Perimeter has been enabled, the Responsible Entity shall implement strong procedural or technical controls at the access points to ensure authenticity of the accessing party, where technically feasible.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25666,"CIP-005-4a","R2.5.",null,"The required documentation shall, at least, identify and describe:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25667,"CIP-005-4a","R2.5.1.",null,"The processes for access request and authorization.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25668,"CIP-005-4a","R2.5.2.",null,"The authentication methods.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25669,"CIP-005-4a","R2.5.3.",null,"The review process for authorization rights, in accordance with Standard CIP-004-4 Requirement R4.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25670,"CIP-005-4a","R2.5.4.",null,"The controls used to secure dial-up accessible connections.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25671,"CIP-005-4a","R2.6.",null,"Appropriate Use Banner —Where technically feasible, electronic access control devices shall display an appropriate use banner on the user screen upon all interactive access attempts. The Responsible Entity shall maintain a document identifying the content of the banner.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25672,"CIP-005-4a","R3.",null,"Monitoring Electronic Access —The Responsible Entity shall implement and document an electronic or manual process(es) for monitoring and logging access at access points to the Electronic Security Perimeter(s) twenty-four hours a day, seven days a week.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25673,"CIP-005-4a","R3.1.",null,"For dial-up accessible Critical Cyber Assets that use non-routable protocols, the Responsible Entity shall implement and document monitoring process(es) at each access point to the dial-up device, where technically feasible.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25674,"CIP-005-4a","R3.2.",null,"Where technically feasible, the security monitoring process(es) shall detect and alert for attempts at or actual unauthorized accesses. These alerts shall provide for appropriate notification to designated response personnel. Where alerting is not technically feasible, the Responsible Entity shall review or otherwise assess access logs for attempts at or actual unauthorized accesses at least every ninety calendar days.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25675,"CIP-005-4a","R4.",null,"Cyber Vulnerability Assessment — The Responsible Entity shall perform a cyber vulnerability assessment of the electronic access points to the Electronic Security Perimeter(s) at least annually. The vulnerability assessment shall include, at a minimum, the following:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25676,"CIP-005-4a","R4.1.",null,"A document identifying the vulnerability assessment process;",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25677,"CIP-005-4a","R4.2.",null,"A review to verify that only ports and services required for operations at these access points are enabled;",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25678,"CIP-005-4a","R4.3.",null,"The discovery of all access points to the Electronic Security Perimeter;",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25679,"CIP-005-4a","R4.4.",null,"A review of controls for default accounts, passwords, and network management community strings;",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25680,"CIP-005-4a","R4.5.",null,"Documentation of the results of the assessment, the action plan to remediate or mitigate vulnerabilities identified in the assessment, and the execution status of that action plan.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25681,"CIP-005-4a","R5.",null,"Documentation Review and Maintenance —The Responsible Entity shall review, update, and maintain all documentation to support compliance with the requirements of Standard CIP-005-4a.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25682,"CIP-005-4a","R5.1.",null,"The Responsible Entity shall ensure that all documentation required by Standard CIP-005-4a reflect current configurations and processes and shall review the documents and procedures referenced in Standard CIP-005-4a at least annually.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25683,"CIP-005-4a","R5.2.",null,"The Responsible Entity shall update the documentation to reflect the modification of the network or controls within ninety calendar days of the change.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25684,"CIP-005-4a","R5.3.",null,"The Responsible Entity shall retain electronic access logs for at least ninety calendar days. Logs related to reportable incidents shall be kept in accordance with the requirements of Standard CIP-008-4.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25685,"CIP-005-5","R1.",null,"Each Responsible Entity shall implement one or more documented processes that collectively include each of the\napplicable requirement parts in CIP‐005‐5 Table R1 – Electronic Security Perimeter. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning and Same Day Operations].","2016-07-01","2020-06-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25686,"CIP-005-5","R2.",null,"Each Responsible Entity allowing Interactive Remote Access to BES Cyber Systems shall implement one or more\ndocumented processes that collectively include the applicable requirement parts, where technically feasible, in CIP‐005‐5 Table R2 – Interactive Remote Access Management. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning and Same Day Operations].","2016-07-01","2020-06-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25687,"CIP-005-6","R1.",null,"Each Responsible Entity shall implement one or more documented processes that collectively include each of the applicable requirement parts in CIP-005-6 Table R1 – Electronic Security Perimeter.","2020-10-01","2022-10-31","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25688,"CIP-005-6","R2.",null,"Each Responsible Entity shall implement one or more documented processes that collectively include the applicable requirement parts, where technically feasible, in CIP-005-6 Table R2 –Remote Access Management.","2020-10-01","2022-10-31","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[30241,"CIP-005-7","R1.",null,"Each Responsible Entity shall implement one or more documented processes that collectively include each of the\r\napplicable requirement parts in CIP-005-7 Table R1 – Electronic Security Perimeter. [Violation Risk Factor: Medium] [Time\r\nHorizon: Operations Planning and Same Day Operations]","2022-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",false,null,false]
[30242,"CIP-005-7","R2.",null,"Each Responsible Entity shall implement one or more documented processes that collectively include the applicable\r\nrequirement parts, where technically feasible, in CIP-005-7 Table R2 –Remote Access Management. [Violation Risk Factor:\r\nMedium] [Time Horizon: Operations Planning and Same Day Operations].","2022-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30244,"CIP-005-7","R3.",null,"Each Responsible Entity shall implement one or more documented processes that collectively include the applicable\r\nrequirement parts in CIP-005-7 Table R3 –Vendor Remote Access Management for EACMS and PACS. [Violation Risk Factor:\r\nMedium] [Time Horizon: Operations Planning and Same Day Operations].","2022-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[25712,"CIP-006-3d","R1.",null,"Physical Security Plan —The Responsible Entity shall document, implement, and maintain a physical security plan, approved by the senior manager or delegate(s) that shall address, at a minimum, the following:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25713,"CIP-006-3d","R1.1.",null,"All Cyber Assets within an Electronic Security Perimeter shall reside within an identified Physical Security Perimeter. Where a completely enclosed (“six-wall”) border cannot be established, the Responsible Entity shall deploy and document alternative measures to control physical access to such Cyber Assets.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25714,"CIP-006-3d","R1.2.",null,"Identification of all physical access points through each Physical Security Perimeter and measures to control entry at those access points.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25715,"CIP-006-3d","R1.3.",null,"Processes, tools, and procedures to monitor physical access to the perimeter(s).",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25716,"CIP-006-3d","R1.4.",null,"Appropriate use of physical access controls as described in Requirement R4 including visitor pass management, response to loss, and prohibition of inappropriate use of physical access controls.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25717,"CIP-006-3d","R1.5.",null,"Review of access authorization requests and revocation of access authorization, in accordance with CIP-004-3 Requirement R4.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25718,"CIP-006-3d","R1.6.",null,"A visitor control program for visitors (personnel without authorized unescorted access to a Physical Security Perimeter), containing at a minimum the following:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25719,"CIP-006-3d","R1.6.1.",null,"Logs (manual or automated) to document the entry and exit of visitors, including the date and time, to and from Physical Security Perimeters.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25720,"CIP-006-3d","R1.6.2.",null,"Continuous escorted access of visitors within the Physical Security Perimeter.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25721,"CIP-006-3d","R1.7.",null,"Update of the physical security plan within thirty calendar days of the completion of any physical security system redesign or reconfiguration, including, but not limited to, addition or removal of access points through the Physical Security Perimeter, physical access controls, monitoring controls, or logging controls.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25722,"CIP-006-3d","R1.8.",null,"Annual review of the physical security plan.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25723,"CIP-006-3d","R2.",null,"Protection of Physical Access Control Systems — Cyber Assets that authorize and/or log access to the Physical Security Perimeter(s), exclusive of hardware at the Physical Security Perimeter access point such as electronic lock control mechanisms and badge readers, shall:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25724,"CIP-006-3d","R2.1.",null,"Be protected from unauthorized physical access.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25725,"CIP-006-3d","R2.2.",null,"Be afforded the protective measures specified in Standard CIP-003-3; Standard CIP-004-3 Requirement R3; Standard CIP-005-3 Requirements R2 and R3; Standard CIP-006-3 Requirements R4 and R5; Standard CIP-007-3; Standard CIP-008-3; and Standard CIP-009-3.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25726,"CIP-006-3d","R3.",null,"Protection of Electronic Access Control Systems — Cyber Assets used in the access control and/or monitoring of the Electronic Security Perimeter(s) shall reside within an identified Physical Security Perimeter.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25727,"CIP-006-3d","R4.",null,"Physical Access Controls — The Responsible Entity shall document and implement the operational and procedural controls to manage physical access at all access points to the Physical Security Perimeter(s) twenty-four hours a day, seven days a week. The Responsible Entity shall implement one or more of the following physical access methods:                                                                                                                                                                    • Card Key: A means of electronic access where the access rights of the card holder are predefined in a computer database. Access rights may differ from one perimeter to another.                                                                           \n• Special Locks: These include, but are not limited to, locks with “restricted key” systems, magnetic locks that can be operated remotely, and “man-trap” systems.                                                                                                        \n• Security Personnel: Personnel responsible for controlling physical access who may reside on-site or at a monitoring station.                                                                                                                                                    • Other Authentication Devices: Biometric, keypad, token, or other equivalent devices that control physical access to the Critical Cyber Assets.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25728,"CIP-006-3d","R5.",null,"Monitoring Physical Access —The Responsible Entity shall document and implement the technical and procedural controls for monitoring physical access at all access points to the Physical Security Perimeter(s) twenty-four hours a day, seven days a week. Unauthorized access attempts shall be reviewed immediately and handled in accordance with the procedures specified in Requirement CIP-008-3. One or more of the following monitoring methods shall be used:\n• Alarm Systems: Systems that alarm to indicate a door, gate or window has been opened without authorization. These alarms must provide for immediate notification to personnel responsible for response.\n• Human Observation of Access Points: Monitoring of physical access points by authorized personnel as specified in Requirement R4.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25729,"CIP-006-3d","R6.",null,"Logging Physical Access — Logging shall record sufficient information to uniquely identify individuals and the time of access twenty-four hours a day, seven days a week. The Responsible Entity shall implement and document the technical and procedural mechanisms for logging physical entry at all access points to the Physical Security Perimeter(s) using one or more of the following logging methods or their equivalent:                                               \n• Computerized Logging: Electronic logs produced by the Responsible Entity’s selected access control and monitoring method.                                                                                                                                                    • Video Recording: Electronic capture of video images of sufficient quality to determine identity.                              \n• Manual Logging: A log book or sign-in sheet, or other record of physical access maintained by security or other personnel authorized to control and monitor physical access as specified in Requirement R4.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25730,"CIP-006-3d","R7.",null,"Access Log Retention —The Responsible Entity shall retain physical access logs for at least ninety calendar days. Logs related to reportable incidents shall be kept in accordance with the requirements of Standard CIP-008-3.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25731,"CIP-006-3d","R8.",null,"Maintenance and Testing — The Responsible Entity shall implement a maintenance and testing program to ensure that all physical security systems under Requirements R4, R5, and R6 function properly. The program must include, at a minimum, the following:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25732,"CIP-006-3d","R8.1.",null,"Testing and maintenance of all physical security mechanisms on a cycle no longer than three years.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25733,"CIP-006-3d","R8.2.",null,"Retention of testing and maintenance records for the cycle determined by the Responsible Entity in Requirement R8.1.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25734,"CIP-006-3d","R8.3.",null,"Retention of outage records regarding access controls, logging, and monitoring for a minimum of one calendar year.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25735,"CIP-006-4c","R1.",null,"Physical Security Plan —The Responsible Entity shall document, implement, and maintain a physical security plan, approved by the senior manager or delegate(s) that shall address, at a minimum, the following:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25736,"CIP-006-4c","R1.1.",null,"All Cyber Assets within an Electronic Security Perimeter shall reside within an identified Physical Security Perimeter. Where a completely enclosed (“six-wall”) border cannot be established, the Responsible Entity shall deploy and document alternative measures to control physical access to such Cyber Assets.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25737,"CIP-006-4c","R1.2.",null,"Identification of all physical access points through each Physical Security Perimeter and measures to control entry at those access points.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25738,"CIP-006-4c","R1.3.",null,"Processes, tools, and procedures to monitor physical access to the perimeter(s).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25739,"CIP-006-4c","R1.4.",null,"Appropriate use of physical access controls as described in Requirement R4 including visitor pass management, response to loss, and prohibition of inappropriate use of physical access controls.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25740,"CIP-006-4c","R1.5.",null,"Review of access authorization requests and revocation of access authorization, in accordance with CIP-004-4 Requirement R4.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25741,"CIP-006-4c","R1.6.",null,"A visitor control program for visitors (personnel without authorized unescorted access to a Physical Security Perimeter), containing at a minimum the following:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25742,"CIP-006-4c","R1.6.1.",null,"Logs (manual or automated) to document the entry and exit of visitors, including the date and time, to and from Physical Security Perimeters.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25743,"CIP-006-4c","R1.6.2.",null,"Continuous escorted access of visitors within the Physical Security Perimeter.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25744,"CIP-006-4c","R1.7.",null,"Update of the physical security plan within thirty calendar days of the completion of any physical security system redesign or reconfiguration, including, but not limited to, addition or removal of access points through the Physical Security Perimeter, physical access controls, monitoring controls, or logging controls.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25745,"CIP-006-4c","R1.8.",null,"Annual review of the physical security plan.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25746,"CIP-006-4c","R2.",null,"Protection of Physical Access Control Systems — Cyber Assets that authorize and/or log access to the Physical Security Perimeter(s), exclusive of hardware at the Physical Security Perimeter access point such as electronic lock control mechanisms and badge readers, shall:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25747,"CIP-006-4c","R2.1.",null,"Be protected from unauthorized physical access.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25748,"CIP-006-4c","R2.2.",null,"Be afforded the protective measures specified in Standard CIP-003-4; Standard CIP-004-4 Requirement R3; Standard CIP-005-4a Requirements R2 and R3; Standard CIP-006-4c Requirements R4 and R5; Standard CIP-007-4; Standard CIP-008-4; and Standard CIP-009-4.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25749,"CIP-006-4c","R3.",null,"Protection of Electronic Access Control Systems — Cyber Assets used in the access control and/or monitoring of the Electronic Security Perimeter(s) shall reside within an identified Physical Security Perimeter.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25750,"CIP-006-4c","R4.",null,"Physical Access Controls — The Responsible Entity shall document and implement the operational and procedural controls to manage physical access at all access points to the Physical Security Perimeter(s) twenty-four hours a day, seven days a week. The Responsible Entity shall implement one or more of the following physical access methods:\n• Card Key: A means of electronic access where the access rights of the card holder are predefined in a computer database. Access rights may differ from one perimeter to another.\n• Special Locks: These include, but are not limited to, locks with “restricted key” systems, magnetic locks that can be operated remotely, and “man-trap” systems.\n• Security Personnel: Personnel responsible for controlling physical access who may reside on-site or at a monitoring station.\n• Other Authentication Devices: Biometric, keypad, token, or other equivalent devices that control physical access to the Critical Cyber Assets.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25751,"CIP-006-4c","R5.",null,"Monitoring Physical Access —The Responsible Entity shall document and implement the technical and procedural controls for monitoring physical access at all access points to the Physical Security Perimeter(s) twenty-four hours a day, seven days a week. Unauthorized access attempts shall be reviewed immediately and handled in accordance with the procedures specified in Requirement CIP-008-4. One or more of the following monitoring methods shall be used:\n• Alarm Systems: Systems that alarm to indicate a door, gate or window has been opened without authorization. These alarms must provide for immediate notification to personnel responsible for response.\n• Human Observation of Access Points: Monitoring of physical access points by authorized personnel as specified in Requirement R4.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25752,"CIP-006-4c","R6.",null,"Logging Physical Access — Logging shall record sufficient information to uniquely identify individuals and the time of access twenty-four hours a day, seven days a week. The Responsible Entity shall implement and document the technical and procedural mechanisms for logging physical entry at all access points to the Physical Security Perimeter(s) using one or more of the following logging methods or their equivalent:\n• Computerized Logging: Electronic logs produced by the Responsible Entity’s selected access control and monitoring method.\n• Video Recording: Electronic capture of video images of sufficient quality to determine identity.\n• Manual Logging: A log book or sign-in sheet, or other record of physical access maintained by security or other personnel authorized to control and monitor physical access as specified in Requirement R4.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25753,"CIP-006-4c","R7.",null,"Access Log Retention —The Responsible Entity shall retain physical access logs for at least ninety calendar days. Logs related to reportable incidents shall be kept in accordance with the requirements of Standard CIP-008-4.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25754,"CIP-006-4c","R8.",null,"Maintenance and Testing — The Responsible Entity shall implement a maintenance and testing program to ensure that all physical security systems under Requirements R4, R5, and R6 function properly. The program must include, at a minimum, the following:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25755,"CIP-006-4c","R8.1.",null,"Testing and maintenance of all physical security mechanisms on a cycle no longer than three years.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25756,"CIP-006-4c","R8.2.",null,"Retention of testing and maintenance records for the cycle determined by the Responsible Entity in Requirement R8.1.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25757,"CIP-006-4c","R8.3.",null,"Retention of outage records regarding access controls, logging, and monitoring for a minimum of one calendar year.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25758,"CIP-006-4d","R1.",null,"Physical Security Plan —The Responsible Entity shall document, implement, and maintain a physical security plan, approved by the senior manager or delegate(s) that shall address, at a minimum, the following:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25759,"CIP-006-4d","R1.1.",null,"All Cyber Assets within an Electronic Security Perimeter shall reside within an identified Physical Security Perimeter. Where a completely enclosed (“six-wall”) border cannot be established, the Responsible Entity shall deploy and document alternative measures to control physical access to such Cyber Assets.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25760,"CIP-006-4d","R1.2.",null,"Identification of all physical access points through each Physical Security Perimeter and measures to control entry at those access points.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25761,"CIP-006-4d","R1.3.",null,"Processes, tools, and procedures to monitor physical access to the perimeter(s).",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25762,"CIP-006-4d","R1.4.",null,"Appropriate use of physical access controls as described in Requirement R4 including visitor pass management, response to loss, and prohibition of inappropriate use of physical access controls.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25763,"CIP-006-4d","R1.5.",null,"Review of access authorization requests and revocation of access authorization, in accordance with CIP-004-4 Requirement R4.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25764,"CIP-006-4d","R1.6.",null,"A visitor control program for visitors (personnel without authorized unescorted access to a Physical Security Perimeter), containing at a minimum the following:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25765,"CIP-006-4d","R1.6.1.",null,"Logs (manual or automated) to document the entry and exit of visitors, including the date and time, to and from Physical Security Perimeters.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25766,"CIP-006-4d","R1.6.2.",null,"Continuous escorted access of visitors within the Physical Security Perimeter.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25767,"CIP-006-4d","R1.7.",null,"Update of the physical security plan within thirty calendar days of the completion of any physical security system redesign or reconfiguration, including, but not limited to, addition or removal of access points through the Physical Security Perimeter, physical access controls, monitoring controls, or logging controls.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25768,"CIP-006-4d","R1.8.",null,"Annual review of the physical security plan.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25769,"CIP-006-4d","R2.",null,"Protection of Physical Access Control Systems — Cyber Assets that authorize and/or log access to the Physical Security Perimeter(s), exclusive of hardware at the Physical Security Perimeter access point such as electronic lock control mechanisms and badge readers, shall:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25770,"CIP-006-4d","R2.1.",null,"Be protected from unauthorized physical access.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25771,"CIP-006-4d","R2.2.",null,"Be afforded the protective measures specified in Standard CIP-003-4; Standard CIP-004-4 Requirement R3; Standard CIP-005-4 Requirements R2 and R3; Standard CIP-006-4 Requirements R4 and R5; Standard CIP-007-4; Standard CIP-008-4; and Standard CIP-009-4.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25772,"CIP-006-4d","R3.",null,"Protection of Electronic Access Control Systems — Cyber Assets used in the access control and/or monitoring of the Electronic Security Perimeter(s) shall reside within an identified Physical Security Perimeter.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25773,"CIP-006-4d","R4.",null,"Physical Access Controls — The Responsible Entity shall document and implement the operational and procedural controls to manage physical access at all access points to the Physical Security Perimeter(s) twenty-four hours a day, seven days a week. The Responsible Entity shall implement one or more of the following physical access methods:                                                                                                                                                                    • Card Key: A means of electronic access where the access rights of the card holder are predefined in a computer database. Access rights may differ from one perimeter to another.                                                                             \n• Special Locks: These include, but are not limited to, locks with “restricted key” systems, magnetic locks that can be operated remotely, and “man-trap” systems.                                                                                                         \n• Security Personnel: Personnel responsible for controlling physical access who may reside on-site or at a monitoring station.                                                                                                                                                    • Other Authentication Devices: Biometric, keypad, token, or other equivalent devices that control physical access to the Critical Cyber Assets.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25774,"CIP-006-4d","R5.",null,"Monitoring Physical Access —The Responsible Entity shall document and implement the technical and procedural controls for monitoring physical access at all access points to the Physical Security Perimeter(s) twenty-four hours a day, seven days a week. Unauthorized access attempts shall be reviewed immediately and handled in accordance with the procedures specified in Requirement CIP-008-4. One or more of the following monitoring methods shall be used:                                                                                                                                                                           • Alarm Systems: Systems that alarm to indicate a door, gate or window has been opened without authorization. These alarms must provide for immediate notification to personnel responsible for response.                                   \n• Human Observation of Access Points: Monitoring of physical access points by authorized personnel as specified in Requirement R4.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25775,"CIP-006-4d","R6.",null,"Logging Physical Access — Logging shall record sufficient information to uniquely identify individuals and the time of access twenty-four hours a day, seven days a week. The Responsible Entity shall implement and document the technical and procedural mechanisms for logging physical entry at all access points to the Physical Security Perimeter(s) using one or more of the following logging methods or their equivalent:                                              \n• Computerized Logging: Electronic logs produced by the Responsible Entity’s selected access control and monitoring method.                                                                                                                                                   • Video Recording: Electronic capture of video images of sufficient quality to determine identity.                             \n• Manual Logging: A log book or sign-in sheet, or other record of physical access maintained by security or other personnel authorized to control and monitor physical access as specified in Requirement R4.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25776,"CIP-006-4d","R7.",null,"Access Log Retention —The Responsible Entity shall retain physical access logs for at least ninety calendar days. Logs related to reportable incidents shall be kept in accordance with the requirements of Standard CIP-008-4.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25777,"CIP-006-4d","R8.",null,"Maintenance and Testing — The Responsible Entity shall implement a maintenance and testing program to ensure that all physical security systems under Requirements R4, R5, and R6 function properly. The program must include, at a minimum, the following:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25778,"CIP-006-4d","R8.1.",null,"Testing and maintenance of all physical security mechanisms on a cycle no longer than three years.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25779,"CIP-006-4d","R8.2.",null,"Retention of testing and maintenance records for the cycle determined by the Responsible Entity in Requirement R8.1.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25780,"CIP-006-4d","R8.3.",null,"Retention of outage records regarding access controls, logging, and monitoring for a minimum of one calendar year.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25781,"CIP-006-5","R1.",null,"Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, one or more documented physical security plans that collectively include all of the applicable requirement parts in CIP‐006‐5 Table R1 – Physical Security Plan. [Violation Risk Factor: Medium] [Time Horizon: Long Term Planning and Same Day Operations].",null,"2022-09-30","Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25782,"CIP-006-5","R2.",null,"Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, one or more documented visitor control programs that include each of the applicable requirement parts in CIP‐006‐5 Table R2 – Visitor Control Program. [Violation Risk Factor: Medium] [Time Horizon: Same Day Operations.]",null,"2022-09-30","Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25783,"CIP-006-5","R3.",null,"Each Responsible Entity shall implement one or more documented Physical Access Control System maintenance and testing programs that collectively include each of the applicable requirement parts in CIP‐006‐5 Table R3 – Maintenance and Testing Program. [Violation Risk Factor: Lower] [Time Horizon: Long Term Planning].",null,"2022-09-30","Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25784,"CIP-006-6","R1.",null,"Each Responsible Entity shall implement one or more documented physical security plan(s) that collectively include all of the applicable requirement parts in CIP-006-6 Table R1 – Physical Security Plan. [Violation Risk Factor: Medium] [Time Horizon: Long Term Planning and Same Day Operations].","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25785,"CIP-006-6","R2.",null,"Each Responsible Entity shall implement one or more documented visitor control program(s) that include each of the applicable requirement parts in CIP-006-6 Table R2 – Visitor Control Program. [Violation Risk Factor: Medium] [Time Horizon: Same Day Operations.]","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25786,"CIP-006-6","R3.",null,"Each Responsible Entity shall implement one or more documented Physical Access Control System maintenance and testing program(s) that collectively include each of the applicable requirement parts in CIP-006-6 Table R3 – Maintenance and Testing Program. [Violation Risk Factor: Medium] [Time Horizon: Long Term Planning].","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25815,"CIP-007-3b","R1.",null,"Test Procedures—The Responsible Entity shall ensure that new Cyber Assets and significant changes to existing Cyber Assets within the Electronic Security Perimeter do not adversely affect existing cyber security controls. For purposes of Standard CIP-007-3, a significant change shall, at a minimum, include implementation of security patches, cumulative service packs, vendor releases, and version upgrades of operating systems, applications, database platforms, or other third-party software or firmware.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25816,"CIP-007-3b","R1.1.",null,"The Responsible Entity shall create, implement, and maintain cyber security test procedures in a manner that minimizes adverse effects on the production system or its operation.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25817,"CIP-007-3b","R1.2.",null,"The Responsible Entity shall document that testing is performed in a manner that reflects the production environment.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25818,"CIP-007-3b","R1.3.",null,"The Responsible Entity shall document test results.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25819,"CIP-007-3b","R2.",null,"Ports and Services — The Responsible Entity shall establish, document and implement a process to ensure that only those ports and services required for normal and emergency operations are enabled.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25820,"CIP-007-3b","R2.1.",null,"The Responsible Entity shall enable only those ports and services required for normal and emergency operations.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25821,"CIP-007-3b","R2.2.",null,"The Responsible Entity shall disable other ports and services, including those used for testing purposes, prior to production use of all Cyber Assets inside the Electronic Security Perimeter(s).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25822,"CIP-007-3b","R2.3.",null,"In the case where unused ports and services cannot be disabled due to technical limitations, the Responsible Entity shall document compensating measure(s) applied to mitigate risk exposure.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25823,"CIP-007-3b","R3.",null,"Security Patch Management — The Responsible Entity, either separately or as a component of the documented configuration management process specified in CIP-003-3 Requirement R6,  shall establish, document and implement a security patch management program for tracking, evaluating, testing, and installing applicable cyber security software patches for all Cyber Assets within the Electronic Security Perimeter(s).",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25824,"CIP-007-3b","R3.1.",null,"The Responsible Entity shall document the assessment of security patches and security upgrades for applicability within thirty calendar days of availability of the patches or upgrades.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25825,"CIP-007-3b","R3.2.",null,"The Responsible Entity shall document the implementation of security patches.  In any case where the patch is not installed, the Responsible Entity shall document compensating measure(s) applied to mitigate risk exposure.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25826,"CIP-007-3b","R4.",null,"Malicious Software Prevention — The Responsible Entity shall use anti-virus software and other malicious software (“malware”) prevention tools, where technically feasible, to detect, prevent, deter, and mitigate the introduction, exposure, and propagation of malware on all Cyber Assets within the Electronic Security Perimeter(s).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,false]
[25827,"CIP-007-3b","R4.1.",null,"The Responsible Entity shall document and implement anti-virus and malware prevention tools.  In the case where anti-virus software and malware prevention tools are not installed, the Responsible Entity shall document compensating measure(s) applied to mitigate risk exposure.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25828,"CIP-007-3b","R4.2.",null,"The Responsible Entity shall document and implement a process for the update of anti-virus and malware prevention “signatures.”  The process must address testing and installing the signatures.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25829,"CIP-007-3b","R5.",null,"Account Management — The Responsible Entity shall establish, implement, and document technical and procedural controls that enforce access authentication of, and accountability for, all user activity, and that minimize the risk of unauthorized system access.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25830,"CIP-007-3b","R5.1.",null,"The Responsible Entity shall ensure that individual and shared system accounts and authorized access permissions are consistent with the concept of “need to know” with respect to work functions performed.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25831,"CIP-007-3b","R5.1.1.",null,"The Responsible Entity shall ensure that user accounts are implemented as approved by designated personnel. Refer to Standard CIP-003-3 Requirement R5.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25832,"CIP-007-3b","R5.1.2.",null,"The Responsible Entity shall establish methods, processes, and procedures that generate logs of sufficient detail to create historical audit trails of individual user account access activity for a minimum of ninety days.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25833,"CIP-007-3b","R5.1.3.",null,"The Responsible Entity shall review, at least annually, user accounts to verify access privileges are in accordance with Standard CIP-003-3 Requirement R5 and Standard CIP-004-3 Requirement R4.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25834,"CIP-007-3b","R5.2.",null,"The Responsible Entity shall implement a policy to minimize and manage the scope and acceptable use of administrator, shared, and other generic account privileges including factory default accounts.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25835,"CIP-007-3b","R5.2.1.",null,"The policy shall include the removal, disabling, or renaming of such accounts where possible. For such accounts that must remain enabled, passwords shall be changed prior to putting any system into service.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25836,"CIP-007-3b","R5.2.2.",null,"The Responsible Entity shall identify those individuals with access to shared accounts.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25837,"CIP-007-3b","R5.2.3.",null,"Where such accounts must be shared, the Responsible Entity shall have a policy for managing the use of such accounts that limits access to only those with authorization, an audit trail of the account use (automated or manual), and steps for securing the account in the event of personnel changes (for example, change in assignment or termination).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25838,"CIP-007-3b","R5.3.",null,"At a minimum, the Responsible Entity shall require and use passwords, subject to the following, as technically feasible:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25839,"CIP-007-3b","R5.3.1.",null,"Each password shall be a minimum of six characters.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25840,"CIP-007-3b","R5.3.2.",null,"Each password shall consist of a combination of alpha, numeric, and “special” characters.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25841,"CIP-007-3b","R5.3.3.",null,"Each password shall be changed at least annually, or more frequently based on risk.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25842,"CIP-007-3b","R6.",null,"Security Status Monitoring — The Responsible Entity shall ensure that all Cyber Assets within the Electronic Security Perimeter, as technically feasible, implement automated tools or organizational process controls to monitor system events that are related to cyber security.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25843,"CIP-007-3b","R6.1.",null,"The Responsible Entity shall implement and document the organizational processes and technical and procedural mechanisms for monitoring for security events on all Cyber Assets within the Electronic Security Perimeter.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25844,"CIP-007-3b","R6.2.",null,"The security monitoring controls shall issue automated or manual alerts for detected Cyber Security Incidents.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25845,"CIP-007-3b","R6.3.",null,"The Responsible Entity shall maintain logs of system events related to cyber security, where technically feasible, to support incident response as required in Standard CIP-008-3.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25846,"CIP-007-3b","R6.4.",null,"The Responsible Entity shall retain all logs specified in Requirement R6 for ninety calendar days.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25847,"CIP-007-3b","R6.5.",null,"The Responsible Entity shall review logs of system events related to cyber security and maintain records documenting review of logs.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25848,"CIP-007-3b","R7.",null,"Disposal or Redeployment — The Responsible Entity shall establish and implement formal methods, processes, and procedures for disposal or redeployment of Cyber Assets within the Electronic Security Perimeter(s) as identified and documented in Standard CIP-005-3.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25849,"CIP-007-3b","R7.1.",null,"Prior to the disposal of such assets, the Responsible Entity shall destroy or erase the data storage media to prevent unauthorized retrieval of sensitive cyber security or reliability data.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25850,"CIP-007-3b","R7.2.",null,"Prior to redeployment of such assets, the Responsible Entity shall, at a minimum, erase the data storage media to prevent unauthorized retrieval of sensitive cyber security or reliability data.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25851,"CIP-007-3b","R7.3.",null,"The Responsible Entity shall maintain records that such assets were disposed of or redeployed in accordance with documented procedures. (Retirement approved by FERC effective January 21, 2014.)",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25852,"CIP-007-3b","R8.",null,"Cyber Vulnerability Assessment — The Responsible Entity shall perform a cyber vulnerability assessment of all Cyber Assets within the Electronic Security Perimeter at least annually.  The vulnerability assessment shall include, at a minimum, the following:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25853,"CIP-007-3b","R8.1.",null,"A document identifying the vulnerability assessment process;",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25854,"CIP-007-3b","R8.2.",null,"A review to verify that only ports and services required for operation of the Cyber Assets within the Electronic Security Perimeter are enabled;",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25855,"CIP-007-3b","R8.3.",null,"A review of controls for default accounts; and,",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25856,"CIP-007-3b","R8.4.",null,"Documentation of the results of the assessment, the action plan to remediate or mitigate vulnerabilities identified in the assessment, and the execution status of that action plan.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25857,"CIP-007-3b","R9.",null,"Documentation Review and Maintenance — The Responsible Entity shall review and update the documentation specified in Standard CIP-007-3 at least annually.  Changes resulting from modifications to the systems or controls shall be documented within thirty calendar days of the change being completed.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25858,"CIP-007-4a","R1.",null,"Test Procedures —The Responsible Entity shall ensure that new Cyber Assets and significant changes to existing Cyber Assets within the Electronic Security Perimeter do not adversely affect existing cyber security controls. For purposes of Standard CIP-007-4, a significant change shall, at a minimum, include implementation of security patches, cumulative service packs, vendor releases, and version upgrades of operating systems, applications, database platforms, or other third-party software or firmware.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25859,"CIP-007-4a","R1.1.",null,"The Responsible Entity shall create, implement, and maintain cyber security test procedures in a manner that minimizes adverse effects on the production system or its operation.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25860,"CIP-007-4a","R1.2.",null,"The Responsible Entity shall document that testing is performed in a manner that reflects the production environment.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25861,"CIP-007-4a","R1.3.",null,"The Responsible Entity shall document test results.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25862,"CIP-007-4a","R2.",null,"Ports and Services —The Responsible Entity shall establish, document and implement a process to ensure that only those ports and services required for normal and emergency operations are enabled.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25863,"CIP-007-4a","R2.1.",null,"The Responsible Entity shall enable only those ports and services required for normal and emergency operations.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25864,"CIP-007-4a","R2.2.",null,"The Responsible Entity shall disable other ports and services, including those used for testing purposes, prior to production use of all Cyber Assets inside the Electronic Security Perimeter(s).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25865,"CIP-007-4a","R2.3.",null,"In the case where unused ports and services cannot be disabled due to technical limitations, the Responsible Entity shall document compensating measure(s) applied to mitigate risk exposure.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25866,"CIP-007-4a","R3.",null,"Security Patch Management —The Responsible Entity, either separately or as a component of the documented configuration management process specified in CIP-003-4 Requirement R6, shall establish, document and implement a security patch management program for tracking, evaluating, testing, and installing applicable cyber security software patches for all Cyber Assets within the Electronic Security Perimeter(s).",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25867,"CIP-007-4a","R3.1.",null,"The Responsible Entity shall document the assessment of security patches and security upgrades for applicability within thirty calendar days of availability of the patches or upgrades.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25868,"CIP-007-4a","R3.2.",null,"The Responsible Entity shall document the implementation of security patches. In any case where the patch is not installed, the Responsible Entity shall document compensating measure(s) applied to mitigate risk exposure.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25869,"CIP-007-4a","R4.",null,"Malicious Software Prevention —The Responsible Entity shall use anti-virus software and other malicious software (“malware”) prevention tools, where technically feasible, to detect, prevent, deter, and mitigate the introduction, exposure, and propagation of malware on all Cyber Assets within the Electronic Security Perimeter(s).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25870,"CIP-007-4a","R4.1.",null,"The Responsible Entity shall document and implement anti-virus and malware prevention tools. In the case where anti-virus software and malware prevention tools are not installed, the Responsible Entity shall document compensating measure(s) applied to mitigate risk exposure.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25871,"CIP-007-4a","R4.2.",null,"The Responsible Entity shall document and implement a process for the update of anti-virus and malware prevention “signatures.” The process must address testing and installing the signatures.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25872,"CIP-007-4a","R5.",null,"Account Management — The Responsible Entity shall establish, implement, and document technical and procedural controls that enforce access authentication of, and accountability for, all user activity, and that minimize the risk of unauthorized system access.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25873,"CIP-007-4a","R5.1.",null,"The Responsible Entity shall ensure that individual and shared system accounts and authorized access permissions are consistent with the concept of “need to know” with respect to work functions performed.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25874,"CIP-007-4a","R5.1.1.",null,"The Responsible Entity shall ensure that user accounts are implemented as approved by designated personnel. Refer to Standard CIP-003-4 Requirement R5.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25875,"CIP-007-4a","R5.1.2.",null,"The Responsible Entity shall establish methods, processes, and procedures that generate logs of sufficient detail to create historical audit trails of individual user account access activity for a minimum of ninety days.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25876,"CIP-007-4a","R5.1.3.",null,"The Responsible Entity shall review, at least annually, user accounts to verify access privileges are in accordance with Standard CIP-003-4 Requirement R5 and Standard CIP-004-4 Requirement R4.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25877,"CIP-007-4a","R5.2.",null,"The Responsible Entity shall implement a policy to minimize and manage the scope and acceptable use of administrator, shared, and other generic account privileges including factory default accounts.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25878,"CIP-007-4a","R5.2.1.",null,"The policy shall include the removal, disabling, or renaming of such accounts where possible. For such accounts that must remain enabled, passwords shall be changed prior to putting any system into service.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25879,"CIP-007-4a","R5.2.2.",null,"The Responsible Entity shall identify those individuals with access to shared accounts.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25880,"CIP-007-4a","R5.2.3.",null,"Where such accounts must be shared, the Responsible Entity shall have a policy for managing the use of such accounts that limits access to only those with authorization, an audit trail of the account use (automated or manual), and steps for securing the account in the event of personnel changes (for example, change in assignment or termination).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25881,"CIP-007-4a","R5.3.",null,"At a minimum, the Responsible Entity shall require and use passwords, subject to the following, as technically feasible:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25882,"CIP-007-4a","R5.3.1.",null,"Each password shall be a minimum of six characters.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25883,"CIP-007-4a","R5.3.2.",null,"Each password shall consist of a combination of alpha, numeric, and “special” characters.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25884,"CIP-007-4a","R5.3.3.",null,"Each password shall be changed at least annually, or more frequently based on risk.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25885,"CIP-007-4a","R6.",null,"Security Status Monitoring — The Responsible Entity shall ensure that all Cyber Assets within the Electronic Security Perimeter, as technically feasible, implement automated tools or organizational process controls to monitor system events that are related to cyber security.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25886,"CIP-007-4a","R6.1.",null,"The Responsible Entity shall implement and document the organizational processes and technical and procedural mechanisms for monitoring for security events on all Cyber Assets within the Electronic Security Perimeter.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25887,"CIP-007-4a","R6.2.",null,"The security monitoring controls shall issue automated or manual alerts for detected Cyber Security Incidents.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25888,"CIP-007-4a","R6.3.",null,"The Responsible Entity shall maintain logs of system events related to cyber security, where technically feasible, to support incident response as required in Standard CIP-008-4.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25889,"CIP-007-4a","R6.4.",null,"The Responsible Entity shall retain all logs specified in Requirement R6 for ninety calendar days.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25890,"CIP-007-4a","R6.5.",null,"The Responsible Entity shall review logs of system events related to cyber security and maintain records documenting review of logs.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25891,"CIP-007-4a","R7.",null,"Disposal or Redeployment — The Responsible Entity shall establish and implement formal methods, processes, and procedures for disposal or redeployment of Cyber Assets within the Electronic Security Perimeter(s) as identified and documented in Standard CIP-005-4.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25892,"CIP-007-4a","R7.1.",null,"Prior to the disposal of such assets, the Responsible Entity shall destroy or erase the data storage media to prevent unauthorized retrieval of sensitive cyber security or reliability data.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25893,"CIP-007-4a","R7.2.",null,"Prior to redeployment of such assets, the Responsible Entity shall, at a minimum, erase the data storage media to prevent unauthorized retrieval of sensitive cyber security or reliability data.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25894,"CIP-007-4a","R7.3.",null,"The Responsible Entity shall maintain records that such assets were disposed of or redeployed in accordance with documented procedures.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25895,"CIP-007-4a","R8.",null,"Cyber Vulnerability Assessment — The Responsible Entity shall perform a cyber vulnerability assessment of all Cyber Assets within the Electronic Security Perimeter at least annually. The vulnerability assessment shall include, at a minimum, the following:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25896,"CIP-007-4a","R8.1.",null,"A document identifying the vulnerability assessment process;",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25897,"CIP-007-4a","R8.2.",null,"A review to verify that only ports and services required for operation of the Cyber Assets within the Electronic Security Perimeter are enabled;",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25898,"CIP-007-4a","R8.3.",null,"A review of controls for default accounts; and,",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25899,"CIP-007-4a","R8.4.",null,"Documentation of the results of the assessment, the action plan to remediate or mitigate vulnerabilities identified in the assessment, and the execution status of that action plan.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25900,"CIP-007-4a","R9.",null,"Documentation Review and Maintenance —The Responsible Entity shall review and update the documentation specified in Standard CIP-007-4 at least annually. Changes resulting from modifications to the systems or controls shall be documented within thirty calendar days of the change being completed.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25479,"CIP-007-5","R1.",null,"Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, one or more documented processes that collectively include each of the applicable requirement parts in CIP‐007‐5 Table R1 – Ports and Services. [Violation Risk Factor: Medium] [Time Horizon: Same Day Operations.]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25480,"CIP-007-5","R2.",null,"Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, one or more documented processes that collectively include each of the applicable requirement parts in CIP‐007‐5 Table R2 – Security Patch Management. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25481,"CIP-007-5","R3.",null,"Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, one or more documented processes that collectively include each of the applicable requirement parts in CIP‐007‐5 Table R3 – Malicious Code Prevention. [Violation Risk Factor: Medium] [Time Horizon: Same Day Operations].",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25482,"CIP-007-5","R4.",null,"Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, one or more documented processes that collectively include each of the applicable requirement parts in CIP‐007‐5 Table R4 – Security Event Monitoring. [Violation Risk Factor: Medium] [Time Horizon: Same Day Operations and Operations Assessment.]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25483,"CIP-007-5","R5.",null,"Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, one or more documented processes that collectively include each of the applicable requirement parts in CIP‐007‐5 Table R5 – System Access Controls. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning].",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25484,"CIP-007-6","R1.",null,"Each Responsible Entity shall implement one or more documented process(es) that collectively include each of the applicable requirement parts in CIP-007-6 Table R1 – Ports and Services. [Violation Risk Factor: Medium] [Time Horizon: Same Day Operations.]","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25485,"CIP-007-6","R2.",null,"Each Responsible Entity shall implement one or more documented process(es) that collectively include each of the applicable requirement parts in CIP-007-6 Table R2 – Security Patch Management. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning].","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25901,"CIP-007-6","R3.",null,"Each Responsible Entity shall implement one or more documented process(es) that collectively include each of the applicable requirement parts in CIP-007-6 Table R3 – Malicious Code Prevention. [Violation Risk Factor: Medium] [Time Horizon: Same Day Operations].","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25902,"CIP-007-6","R4.",null,"Each Responsible Entity shall implement one or more documented process(es) that collectively include each of the applicable requirement parts in CIP-007-6 Table R4 – Security Event Monitoring. [Violation Risk Factor: Medium] [Time Horizon: Same Day Operations and Operations Assessment.]","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25903,"CIP-007-6","R5.",null,"Each Responsible Entity shall implement one or more documented process(es) that collectively include each of the applicable requirement parts in CIP-007-6 Table R5 – System Access Controls. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning].","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25912,"CIP-008-4","R1.",null,"Cyber Security Incident Response Plan —The Responsible Entity shall develop and maintain a Cyber Security Incident response plan and implement the plan in response to Cyber Security Incidents. The Cyber Security Incident response plan shall address, at a minimum, the following:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25913,"CIP-008-4","R1.1.",null,"Procedures to characterize and classify events as reportable Cyber Security Incidents.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25914,"CIP-008-4","R1.2.",null,"Response actions, including roles and responsibilities of Cyber Security Incident response teams, Cyber Security Incident handling procedures, and communication plans.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25915,"CIP-008-4","R1.3.",null,"Process for reporting Cyber Security Incidents to the Electricity Sector Information Sharing and Analysis Center (ES-ISAC). The Responsible Entity must ensure that all reportable Cyber Security Incidents are reported to the ES-ISAC either directly or through an intermediary.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25916,"CIP-008-4","R1.4.",null,"Process for updating the Cyber Security Incident response plan within thirty calendar days of any changes.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25917,"CIP-008-4","R1.5.",null,"Process for ensuring that the Cyber Security Incident response plan is reviewed at least annually.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25918,"CIP-008-4","R1.6.",null,"Process for ensuring the Cyber Security Incident response plan is tested at least annually. A test of the Cyber Security Incident response plan can range from a paper drill, to a full operational exercise, to the response to an actual incident.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25919,"CIP-008-4","R2.",null,"Cyber Security Incident Documentation —The Responsible Entity shall keep relevant documentation related to Cyber Security Incidents reportable per Requirement R1.1 for three calendar years.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25920,"CIP-008-5","R1.",null,"Each Responsible Entity shall document one or more Cyber Security Incident response plan(s) that collectively include each of the applicable requirement parts in CIP‐008‐5 Table R1 – Cyber Security Incident Response Plan Specifications. [Violation Risk Factor: Lower] [Time Horizon: Long Term Planning].","2016-07-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25921,"CIP-008-5","R2.",null,"Each Responsible Entity shall implement each of its documented Cyber Security Incident response plans to collectively include each of the applicable requirement parts in CIP‐008‐5 Table R2 – Cyber Security Incident Response Plan Implementation and Testing. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning and Real‐Time Operations].","2016-07-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25922,"CIP-008-5","R3.",null,"Each Responsible Entity shall maintain each of its Cyber Security Incident response plans according to each of the\napplicable requirement parts in CIP‐008‐5 Table R3 – Cyber Security Incident Response Plan Review, Update, and\nCommunication. [Violation Risk Factor: Lower] [Time Horizon: Operations Assessment].","2016-07-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[29900,"CIP-008-6","R1.",null,"Each Responsible Entity shall document one or more Cyber Security Incident response plan(s) that collectively include each of the applicable requirement parts in CIP-008-6 Table R1 – Cyber Security Incident Response Plan Specifications. [Violation Risk Factor: Lower] [Time Horizon: Long Term Planning].","2021-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, TOP, RC, GOP, GO, DP, BA","Yes",false,null,false]
[29901,"CIP-008-6","R2.",null,"Each Responsible Entity shall implement each of its documented Cyber Security Incident response plans to collectively include each of the applicable requirement parts in CIP-008-6 Table R2 – Cyber Security Incident Response Plan Implementation and Testing. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning and Real-Time Operations].","2021-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",false,null,false]
[29902,"CIP-008-6","R3.",null,"Each Responsible Entity shall maintain each of its Cyber Security Incident response plans according to each of the applicable requirement parts in CIP-008-6 Table R3 – Cyber Security Incident Response Plan Review, Update, and Communication. [Violation Risk Factor: Lower] [Time Horizon: Operations Assessment].","2021-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",false,null,false]
[29903,"CIP-008-6","R4.",null,"Each Responsible Entity shall notify the Electricity Information Sharing and Analysis Center (E-ISAC) and, if subject to the jurisdiction of the United States, the United States National Cybersecurity and Communications Integration Center (NCCIC),1 or their successors, of a Reportable Cyber Security Incident and a Cyber Security Incident that was an attempt to compromise, as determined by applying the criteria from Requirement R1, Part 1.2.1, a system identified in the “Applicable Systems” column, unless prohibited by law, in accordance with each of the applicable requirement parts in CIP-008-6 Table R4 – Notifications and Reporting for Cyber Security Incidents. [Violation Risk Factor: Lower] [Time Horizon: Operations Assessment].","2021-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, DP, BA, GOP, GO","Yes",false,null,false]
[25930,"CIP-009-4","R1.",null,"Recovery Plans —The Responsible Entity shall create and annually review recovery plan(s) for Critical Cyber Assets. The recovery plan(s) shall address at a minimum the following:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25931,"CIP-009-4","R1.1.",null,"Specify the required actions in response to events or conditions of varying duration and severity that would activate the recovery plan(s).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25932,"CIP-009-4","R1.2.",null,"Define the roles and responsibilities of responders.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25933,"CIP-009-4","R2.",null,"Exercises —The recovery plan(s) shall be exercised at least annually. An exercise of the recovery plan(s) can range from a paper drill, to a full operational exercise, to recovery from an actual incident.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25934,"CIP-009-4","R3.",null,"Change Control — Recovery plan(s) shall be updated to reflect any changes or lessons learned as a result of an exercise or the recovery from an actual incident. Updates shall be communicated to personnel responsible for the activation and implementation of the recovery plan(s) within thirty calendar days of the change being completed.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25935,"CIP-009-4","R4.",null,"Backup and Restore —The recovery plan(s) shall include processes and procedures for the backup and storage of information required to successfully restore Critical Cyber Assets. For example, backups may include spare electronic components or equipment, written documentation of configuration settings, tape backup, etc.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25936,"CIP-009-4","R5.",null,"Testing Backup Media — Information essential to recovery that is stored on backup media shall be tested at least annually to ensure that the information is available. Testing can be completed off site.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP, TO, RE, RC, NERC, LSE, IA, GOP, GO, BA","Yes",true,null,true]
[25937,"CIP-009-5","R1.",null,"Each Responsible Entity shall have one or more documented recovery plans that collectively include each of the applicable requirement parts in CIP‐009‐5 Table R1 – Recovery Plan Specifications. [Violation Risk Factor: Medium] [Time Horizon: Long Term Planning].",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25938,"CIP-009-5","R2.",null,"Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, its documentedrecovery plan(s) to collectively include each of the applicable requirement parts in CIP‐009‐5 Table R2 – Recovery Plan Implementation and Testing. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning and Real‐time Operations.]",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25939,"CIP-009-5","R3.",null,"Each Responsible Entity shall maintain each of its recovery plans in accordance with each of the applicable requirement parts in CIP‐009‐5 Table R3 – Recovery Plan Review, Update and Communication. [Violation Risk Factor: Lower] [Time Horizon: Operations Assessment].",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25940,"CIP-009-6","R1.",null,"Each Responsible Entity shall have one or more documented recovery plan(s) that collectively include each of the applicable requirement parts in CIP-009-6 Table R1 – Recovery Plan Specifications. [Violation Risk Factor: Medium] [Time Horizon: Long Term Planning].","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25941,"CIP-009-6","R2.",null,"Each Responsible Entity shall implement its documented recovery plan(s) to collectively include each of the applicable requirement parts in CIP-009-6 Table R2 – Recovery Plan Implementation and Testing. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning and Real-time Operations.]","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25942,"CIP-009-6","R3.",null,"Each Responsible Entity shall maintain each of its recovery plan(s) in accordance with each of the applicable requirement parts in CIP-009-6 Table R3 – Recovery Plan Review, Update and Communication. [Violation Risk Factor: Lower] [Time Horizon: Operations Assessment].","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25943,"CIP-010-1","R1.",null,"Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, one or more documented processes that collectively include each of the applicable requirement parts in CIP‐010‐1 Table R1 –\nConfiguration Change Management. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning].",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25944,"CIP-010-1","R2.",null,"Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, one or more documented processes that collectively include each of the applicable requirement parts in CIP‐010‐1 Table R2 – Configuration Monitoring. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning].",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25945,"CIP-010-1","R3.",null,"Each Responsible Entity shall implement one or more documented processes that collectively include each of the applicable requirement parts in CIP‐010‐1 Table R3– Vulnerability Assessments. [Violation Risk Factor: Medium] [Time Horizon: Long‐term Planning and Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25946,"CIP-010-2","R1.",null,"Each Responsible Entity shall implement one or more documented process(es) that collectively include each of the applicable requirement parts in CIP-010-2 Table R1 – Configuration Change Management. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning].","2016-07-01","2020-06-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25947,"CIP-010-2","R2.",null,"Each Responsible Entity shall implement one or more documented process(es) that collectively include each of the applicable requirement parts in CIP-010-2 Table R2 – Configuration Monitoring. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning].","2016-07-01","2020-06-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25948,"CIP-010-2","R3.",null,"Each Responsible Entity shall implement one or more documented process(es) that collectively include each of the applicable requirement parts in CIP-010-2 Table R3– Vulnerability Assessments. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning and Operations Planning]","2016-07-01","2020-06-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25949,"CIP-010-2","R4.",null,"Each Responsible Entity, for its high impact and medium impact BES Cyber Systems and associated Protected Cyber Assets, shall implement, except under CIP Exceptional Circumstances, one or more documented plan(s) for Transient Cyber Assets and Removable Media that include the sections in Attachment 1. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning and Operations Planning]","2017-04-01","2020-06-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25950,"CIP-010-3","R1.","YES","Each Responsible Entity shall implement one or more documented process(es) that collectively include each of the applicable requirement parts in CIP-010-3 Table R1 – Configuration Change Management.","2020-10-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25951,"CIP-010-3","R1.","YES","Each Responsible Entity shall implement one or more documented process(es) that collectively include each of the applicable requirement parts in CIP-010-3 Table R1 – Configuration Change Management.","2020-10-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25952,"CIP-010-3","R2.",null,"Each Responsible Entity shall implement one or more documented process(es) that collectively include each of the applicable requirement parts in CIP-010-3 Table R2 – Configuration Monitoring.","2020-10-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25953,"CIP-010-3","R3.",null,"Each Responsible Entity shall implement one or more documented process(es) that collectively include each of the applicable requirement parts in CIP-010-3 Table R3– Vulnerability Assessments.","2020-10-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25954,"CIP-010-3","R4.",null,"Each Responsible Entity, for its high impact and medium impact BES Cyber Systems and associated Protected Cyber Assets, shall implement, except under CIP Exceptional Circumstances, one or more documented plan(s) for Transient Cyber Assets and Removable Media that include the sections in Attachment 1.","2020-10-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[30245,"CIP-010-4","R1.",null,"Each Responsible Entity shall implement one or more documented process(es) that collectively include each of the\r\napplicable requirement parts in CIP-010-4 Table R1 – Configuration Change Management. [Violation Risk Factor: Medium]\r\n[Time Horizon: Operations Planning].","2022-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",false,null,false]
[30246,"CIP-010-4","R2.",null,"Each Responsible Entity shall implement one or more documented process(es) that collectively include each of the\r\napplicable requirement parts in CIP-010-4 Table R2 – Configuration Monitoring. [Violation Risk Factor: Medium] [Time\r\nHorizon: Operations Planning].","2022-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30247,"CIP-010-4","R3.",null,"Each Responsible Entity shall implement one or more documented process(es) that collectively include each of the\r\napplicable requirement parts in CIP-010-3 Table R3– Vulnerability Assessments. [Violation Risk Factor: Medium] [Time\r\nHorizon: Long-term Planning and Operations Planning]","2022-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30248,"CIP-010-4","R4.",null,"Each Responsible Entity, for its high impact and medium impact BES Cyber Systems and associated Protected Cyber Assets,\r\nshall implement, except under CIP Exceptional Circumstances, one or more documented plan(s) for Transient Cyber Assets\r\nand Removable Media that include the sections in Attachment 1. [Violation Risk Factor: Medium] [Time Horizon: Long-term\r\nPlanning and Operations Planning]","2022-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[25955,"CIP-011-1","R1.",null,"Each Responsible Entity shall implement, in a manner that identifies, assesses, and corrects deficiencies, one or more documented information protection program(s) that collectively includes each of the applicable requirement parts in CIP‐011‐1 Table R1 – Information Protection. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning].",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25956,"CIP-011-1","R2.",null,"Each Responsible Entity shall implement one or more documented processes that collectively include the applicable\nrequirement parts in CIP‐011‐1 Table R2 – BES Cyber Asset Reuse and Disposal. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning].",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25957,"CIP-011-2","R1.",null,"Each Responsible Entity shall implement one or more documented information protection program(s) that collectively includes each of the applicable requirement parts in CIP-011-2 Table R1 – Information Protection. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning].","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[25958,"CIP-011-2","R2.",null,"Each Responsible Entity shall implement one or more documented process(es) that collectively include the applicable requirement parts in CIP-011-2 Table R2 – BES Cyber Asset Reuse and Disposal. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning].","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, IA, GOP, GO, DP, BA","Yes",true,null,true]
[29741,"CIP-012-1","R1.",null,"The Responsible Entity shall implement, except under CIP Exceptional Circumstances, one or more documented plan(s) to mitigate the risks posed by unauthorized disclosure and unauthorized modification of Real-time Assessment and Real-time monitoring data while being transmitted between any applicable Control Centers. The Responsible Entity is not required to include oral communications in its plan. The plan shall include: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2022-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, TOP, RC, GOP, GO, BA","Yes",true,null,true]
[29742,"CIP-012-1","R1.1.",null,"Identification of security protection used to mitigate the risks posed by unauthorized disclosure and unauthorized modification of Real-time Assessment and Real-time monitoring data while being transmitted between Control Centers;","2022-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, BA","Yes",true,null,true]
[29743,"CIP-012-1","R1.2.",null,"Identification of where the Responsible Entity applied security protection for transmitting Real-time Assessment and Real-time monitoring data between Control Centers; and","2022-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, TOP, RC, GOP, GO, BA","Yes",true,null,true]
[29744,"CIP-012-1","R1.3.",null,"If the Control Centers are owned or operated by different Responsible Entities, identification of the responsibilities of each Responsible Entity for applying security protection to the transmission of Real-time Assessment and Real-time monitoring data between those Control Centers.","2022-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, BA","Yes",true,null,true]
[25959,"CIP-013-1","R1.",null,"Each Responsible Entity shall develop one or more documented supply chain cyber security risk management plan(s) for high and medium impact BES Cyber Systems. The plan(s) shall include:","2020-10-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true]
[25960,"CIP-013-1","R1.",null,"Each Responsible Entity shall develop one or more documented supply chain cyber security risk management plan(s) for high and medium impact BES Cyber Systems. The plan(s) shall include:","2020-10-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true]
[25961,"CIP-013-1","R1.1.",null,"One or more process(es) used in planning for the procurement of BES Cyber Systems to identify and assess cyber security risk(s) to the Bulk Electric System from vendor products or services resulting from: (i) procuring and installing vendor equipment and software; and (ii) transitions from one vendor(s) to another vendor(s).","2020-10-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true]
[25962,"CIP-013-1","R1.2.",null,"One or more process(es) used in procuring BES Cyber Systems that address the following, as applicable:","2020-10-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true]
[25963,"CIP-013-1","R1.2.1.",null,"Notification by the vendor of vendor-identified incidents related to the products or services provided to the Responsible Entity that pose cyber security risk to the Responsible Entity;","2020-10-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true]
[25964,"CIP-013-1","R1.2.2.",null,"Coordination of responses to vendor-identified incidents related to the products or services provided to the Responsible Entity that pose cyber security risk to the Responsible Entity;","2020-10-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true]
[25965,"CIP-013-1","R1.2.3.",null,"Notification by vendors when remote or onsite access should no longer be granted to vendor representatives;","2020-10-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true]
[25966,"CIP-013-1","R1.2.4.",null,"Disclosure by vendors of known vulnerabilities related to the products or services provided to the Responsible Entity;","2020-10-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true]
[25967,"CIP-013-1","R1.2.5.",null,"Verification of software integrity and authenticity of all software and patches provided by the vendor for use in the BES Cyber System; and","2020-10-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true]
[25968,"CIP-013-1","R1.2.6.",null,"Coordination of controls for (i) vendor-initiated Interactive Remote Access, and (ii) system-to-system remote access with a vendor(s).","2020-10-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true]
[25969,"CIP-013-1","R2.",null,"Each Responsible Entity shall implement its supply chain cyber security risk management plan(s) specified in Requirement R1.  Note: Implementation of the plan does not require the Responsible Entity to renegotiate or abrogate existing contracts (including amendments to master agreements and purchase orders). Additionally, the following issues are beyond the scope of Requirement R2: (1) the actual terms and conditions of a procurement contract; and (2) vendor performance and adherence to a contract.","2020-10-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true]
[25970,"CIP-013-1","R3.",null,"Each Responsible Entity shall review and obtain CIP Senior Manager or delegate approval of its supply chain cyber security risk management plan(s) specified in Requirement R1 at least once every 15 calendar months.","2020-10-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true]
[30249,"CIP-013-2","R1.",null,"Each Responsible Entity shall develop one or more documented supply chain cyber\r\nsecurity risk management plan(s) for high and medium impact BES Cyber Systems and\r\ntheir associated Electronic Access Control or Monitoring Systems (EACMS) and Physical\r\nAccess Control Systems (PACS). The plan(s) shall include: [Violation Risk Factor:\r\nMedium] [Time Horizon: Operations Planning]","2022-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",true,null,true]
[30250,"CIP-013-2","R1.1.",null,"One or more process(es) used in planning for the procurement of BES Cyber\r\nSystems and their associated EACMS and PACS to identify and assess cyber\r\nsecurity risk(s) to the Bulk Electric System from vendor products or services\r\nresulting from: (i) procuring and installing vendor equipment and software; and\r\n(ii) transitions from one vendor(s) to another vendor(s).","2022-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",true,null,true]
[30251,"CIP-013-2","R1.2.",null,"One or more process(es) used in procuring BES Cyber Systems, and their\r\nassociated EACMS and PACS, that address the following, as applicable:","2022-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",true,null,true]
[30252,"CIP-013-2","R1.2.1.",null,"Notification by the vendor of vendor-identified incidents related to the products or services provided to the Responsible Entity that pose cyber security risk to the Responsible Entity;","2022-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",true,null,true]
[30253,"CIP-013-2","R1.2.2.",null,"Coordination of responses to vendor-identified incidents related to the products or services provided to the Responsible Entity that pose cyber security risk to the Responsible Entity;","2022-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",true,null,true]
[30254,"CIP-013-2","R1.2.3.",null,"Notification by vendors when remote or onsite access should no longer be granted to vendor representatives;","2022-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",true,null,true]
[30255,"CIP-013-2","R1.2.4.",null,"Disclosure by vendors of known vulnerabilities related to the products or services provided to the Responsible Entity;","2022-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",true,null,true]
[30256,"CIP-013-2","R1.2.5.",null,"Verification of software integrity and authenticity of all software and\r\npatches provided by the vendor for use in the BES Cyber System and their\r\nassociated EACMS and PACS; and","2022-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",true,null,true]
[30257,"CIP-013-2","R1.2.6.",null,"Coordination of controls for vendor-initiated remote access","2022-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",true,null,true]
[30258,"CIP-013-2","R2.",null,"Each Responsible Entity shall implement its supply chain cyber security risk management plan(s) specified in Requirement R1.  Note: Implementation of the plan does not require the Responsible Entity to renegotiate or abrogate existing contracts (including amendments to master agreements and purchase orders). Additionally, the following issues are beyond the scope of Requirement R2: (1) the actual terms and conditions of a procurement contract; and (2) vendor performance and adherence to a contract.","2022-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",true,null,true]
[30259,"CIP-013-2","R3.",null,"Each Responsible Entity shall review and obtain CIP Senior Manager or delegate approval of its supply chain cyber security risk management plan(s) specified in Requirement R1 at least once every 15 calendar months.","2022-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",true,null,true]
[25995,"CIP-014-2","R1.",null,"Each Transmission Owner shall perform an initial risk assessment and subsequent risk assessments of its Transmission stations and Transmission substations (existing and planned to be in service within 24 months) that meet the criteria specified in Applicability Section 4.1.1. The initial and subsequent risk assessments shall consist of a transmission analysis or transmission analyses designed to identify the Transmission station(s) and Transmission substation(s) that if rendered inoperable or damaged could result in instability, uncontrolled separation, or Cascading within an Interconnection. [VRF: High; Time-Horizon: Long-term Planning]","2015-10-02",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[25996,"CIP-014-2","R1.1.",null,"Subsequent risk assessments shall be performed:\n At least once every 30 calendar months for a Transmission Owner that has identified in its previous risk assessment (as verified according to Requirement R2) one or more Transmission stations or Transmission substations that if rendered inoperable or damaged could result in instability, uncontrolled separation, or Cascading within an Interconnection; or                                                                                                                                                                                                                                                                                                                                                                   At least once every 60 calendar months for a Transmission Owner that has not identified in its previous risk assessment (as verified according to Requirement R2) any Transmission stations or Transmission substations that if rendered inoperable or damaged could result in instability, uncontrolled separation, or Cascading within an Interconnection.","2015-10-02",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[25997,"CIP-014-2","R1.2.",null,"The Transmission Owner shall identify the primary control center that operationally controls each Transmission station or Transmission substation identified in the Requirement R1 risk assessment.","2015-10-02",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[25998,"CIP-014-2","R2.",null,"Each Transmission Owner shall have an unaffiliated third party verify the risk assessment performed under Requirement R1. The verification may occur concurrent with or after the risk assessment performed under Requirement R1. [VRF: Medium; Time-Horizon: Long-term Planning]","2015-10-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[25999,"CIP-014-2","R2.1.",null,"Each Transmission Owner shall select an unaffiliated verifying entity that is either:                                                                                                                                                                                                                                                                                                                                                                                            A registered Planning Coordinator, Transmission Planner, or Reliability Coordinator; or                                                                                                                                                                                                                                                                                                                                                                        An entity that has transmission planning or analysis experience.","2015-10-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26000,"CIP-014-2","R2.2.",null,"The unaffiliated third party verification shall verify the Transmission Owner’s risk assessment performed under Requirement R1, which may include recommendations for the addition or deletion of a Transmission station(s) or Transmission substation(s). The Transmission Owner shall ensure the verification is completed within 90 calendar days following the completion of the Requirement R1 risk assessment.","2015-10-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26001,"CIP-014-2","R2.3.",null,"If the unaffiliated verifying entity recommends that the Transmission Owner add a Transmission station(s) or Transmission substation(s) to, or remove a Transmission station(s) or Transmission substation(s) from, its identification under Requirement R1, the Transmission Owner shall either, within 60 calendar days of completion of the verification, for each recommended addition or removal of a Transmission station or Transmission substation:                                                                                                                                                                         Modify its identification under Requirement R1 consistent with the recommendation; or                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        Document the technical basis for not modifying the identification in accordance with the recommendation.","2015-10-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26002,"CIP-014-2","R2.4.",null,"Each Transmission Owner shall implement procedures, such as the use of non-disclosure agreements, for protecting sensitive or confidential information made available to the unaffiliated third party verifier and to protect or exempt sensitive or confidential information developed pursuant to this Reliability Standard from public disclosure.","2015-10-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26003,"CIP-014-2","R3.",null,"For a primary control center(s) identified by the Transmission Owner according to Requirement R1, Part 1.2 that a) operationally controls an identified Transmission station or Transmission substation verified according to Requirement R2, and b) is not under the operational control of the Transmission Owner: the Transmission Owner shall, within seven calendar days following completion of Requirement R2, notify the Transmission Operator that has operational control of the primary control center of such identification and the date of completion of Requirement R2. [VRF: Lower; Time-Horizon: Long-term Planning]","2015-10-02",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26004,"CIP-014-2","R3.1.",null,"If a Transmission station or Transmission substation previously identified under Requirement R1 and verified according to Requirement R2 is removed from the identification during a subsequent risk assessment performed according to Requirement R1 or a verification according to Requirement R2, then the Transmission Owner shall, within seven calendar days following the verification or the subsequent risk assessment, notify the Transmission Operator that has operational control of the primary control center of the removal.","2015-10-02",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26005,"CIP-014-2","R4.",null,"Each Transmission Owner that identified a Transmission station, Transmission substation, or a primary control center in Requirement R1 and verified according to Requirement R2, and each Transmission Operator notified by a Transmission Owner according to Requirement R3, shall conduct an evaluation of the potential threats and vulnerabilities of a physical attack to each of their respective Transmission station(s), Transmission substation(s), and primary control center(s) identified in Requirement R1 and verified according to Requirement R2. The evaluation shall consider the following: [VRF: Medium; Time-Horizon: Operations Planning, Long-term Planning]","2015-10-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO","Yes",false,null,true]
[26006,"CIP-014-2","R4.1.",null,"Unique characteristics of the identified and verified Transmission station(s), Transmission substation(s), and primary control center(s);","2015-10-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO","Yes",false,null,true]
[26007,"CIP-014-2","R4.2.",null,"Prior history of attack on similar facilities taking into account the frequency, geographic proximity, and severity of past physical security related events; and","2015-10-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO","Yes",false,null,true]
[26008,"CIP-014-2","R4.3.",null,"Intelligence or threat warnings received from sources such as law enforcement, the Electric Reliability Organization (ERO), the Electricity Sector Information Sharing and Analysis Center (ES-ISAC), U.S. federal and/or Canadian governmental agencies, or their successors.","2015-10-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO","Yes",false,null,true]
[26009,"CIP-014-2","R5.",null,"Each Transmission Owner that identified a Transmission station, Transmission substation, or primary control center in Requirement R1 and verified according to Requirement R2, and each Transmission Operator notified by a Transmission Owner according to Requirement R3, shall develop and implement a documented physical security plan(s) that covers their respective Transmission station(s), Transmission substation(s), and primary control center(s). The physical security plan(s) shall be developed within 120 calendar days following the completion of Requirement R2 and executed according to the timeline specified in the physical security plan(s). The physical security plan(s) shall include the following attributes: [VRF: High; Time-Horizon: Long-term Planning]","2015-10-02",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, TO","Yes",false,null,true]
[26010,"CIP-014-2","R5.1.",null,"Resiliency or security measures designed collectively to deter, detect, delay, assess, communicate, and respond to potential physical threats and vulnerabilities identified during the evaluation conducted in Requirement R4.","2015-10-02",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, TO","Yes",false,null,true]
[26011,"CIP-014-2","R5.2.",null,"Law enforcement contact and coordination information.","2015-10-02",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, TO","Yes",false,null,true]
[26012,"CIP-014-2","R5.3.",null,"A timeline for executing the physical security enhancements and modifications specified in the physical security plan.","2015-10-02",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, TO","Yes",false,null,true]
[26013,"CIP-014-2","R5.4.",null,"Provisions to evaluate evolving physical threats, and their corresponding security measures, to the Transmission station(s), Transmission substation(s), or primary control center(s).","2015-10-02",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, TO","Yes",false,null,true]
[26014,"CIP-014-2","R6.",null,"Each Transmission Owner that identified a Transmission station, Transmission substation, or primary control center in Requirement R1 and verified according to Requirement R2, and each Transmission Operator notified by a Transmission Owner according to Requirement R3, shall have an unaffiliated third party review the evaluation performed under Requirement R4 and the security plan(s) developed under Requirement R5. The review may occur concurrently with or after completion of the evaluation performed under Requirement R4 and the security plan development under Requirement R5. [VRF: Medium; Time-Horizon: Long-term Planning]","2015-10-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO","Yes",false,null,true]
[26015,"CIP-014-2","R6.1.",null,"Each Transmission Owner and Transmission Operator shall select an unaffiliated third party reviewer from the following:                                                                                                                                                                                                                                                                                                                                                                             An entity or organization with electric industry physical security experience and whose review staff has at least one member who holds either a Certified Protection Professional (CPP) or Physical Security Professional (PSP) certification.                                                                                                                                                                                                                                          An entity or organization approved by the ERO.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             A governmental agency with physical security expertise.                                                                                                                                                                                                                                                                                                                                                                                                                                                                  An entity or organization with demonstrated law enforcement, government, or military physical security expertise.","2015-10-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO","Yes",false,null,true]
[26016,"CIP-014-2","R6.2.",null,"The Transmission Owner or Transmission Operator, respectively, shall ensure that the unaffiliated third party review is completed within 90 calendar days of completing the security plan(s) developed in Requirement R5. The unaffiliated third party review may, but is not required to, include recommended changes to the evaluation performed under Requirement R4 or the security plan(s) developed under Requirement R5.","2015-10-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO","Yes",false,null,true]
[26017,"CIP-014-2","R6.3.",null,"If the unaffiliated third party reviewer recommends changes to the evaluation performed under Requirement R4 or security plan(s) developed under Requirement R5, the Transmission Owner or Transmission Operator shall, within 60 calendar days of the completion of the unaffiliated third party review, for each recommendation:\n Modify its evaluation or security plan(s) consistent with the recommendation; or\n Document the reason(s) for not modifying the evaluation or security plan(s) consistent with the recommendation.","2015-10-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO","Yes",false,null,true]
[26018,"CIP-014-2","R6.4.",null,"Each Transmission Owner and Transmission Operator shall implement procedures, such as the use of non-disclosure agreements, for protecting sensitive or confidential information made available to the unaffiliated third party reviewer and to protect or exempt sensitive or confidential information developed pursuant to this Reliability Standard from public disclosure.","2015-10-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO","Yes",false,null,true]
[26103,"COM-001-3","R1.",null,"Each Reliability Coordinator shall have Interpersonal Communication capability with the following entities (unless the Reliability Coordinator detects a failure of its Interpersonal Communication capability in which case Requirement R10 shall apply):","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26104,"COM-001-3","R1.1.",null,"All Transmission Operators and Balancing Authorities within its Reliability Coordinator Area.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26105,"COM-001-3","R1.2.",null,"Each adjacent Reliability Coordinator within the same Interconnection.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26138,"COM-001-3","R10.",null,"Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall notify entities as identified in Requirements R1, R3, and R5, respectively within 60 minutes of the detection of a failure of its Interpersonal Communication capability that lasts 30 minutes or longer.","2017-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26139,"COM-001-3","R11.",null,"Each Distribution Provider and Generator Operator that detects a failure of its Interpersonal Communication capability shall consult each entity affected by the failure, as identified in Requirement R7 for a Distribution Provider or Requirement R8 for a Generator Operator, to determine a mutually agreeable action for the restoration of its Interpersonal Communication capability.","2017-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP, DP","Yes",false,null,false]
[26140,"COM-001-3","R12.",null,"Each Reliability Coordinator, Transmission Operator, Generator Operator, and Balancing Authority shall have internal Interpersonal Communication capabilities for the exchange of information necessary for the Reliable Operation of the BES. This includes communication capabilities between Control Centers within the same functional entity, and/or between a Control Center and field personnel.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, RC, GOP, BA","Yes",true,null,true]
[26141,"COM-001-3","R13.",null,"Each Distribution Provider shall have internal Interpersonal Communication capabilities for the exchange of information necessary for the Reliable Operation of the BES. This includes communication capabilities between control centers within the same functional entity, and/or between a control center and field personnel.","2017-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP","Yes",false,null,false]
[26106,"COM-001-3","R2.",null,"Each Reliability Coordinator shall designate an Alternative Interpersonal Communication capability with the following entities:","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26107,"COM-001-3","R2.1.",null,"All Transmission Operators and Balancing Authorities within its Reliability Coordinator Area.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26108,"COM-001-3","R2.2.",null,"Each adjacent Reliability Coordinator within the same Interconnection.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26109,"COM-001-3","R3.",null,"Each Transmission Operator shall have Interpersonal Communication capability with the following entities (unless the Transmission Operator detects a failure of its Interpersonal Communication capability in which case Requirement R10 shall apply): [Violation Risk Factor: High] [Time Horizon: Real-time Operations]","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26110,"COM-001-3","R3.1.",null,"Its Reliability Coordinator.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26111,"COM-001-3","R3.2.",null,"Each Balancing Authority within its Transmission Operator Area.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26112,"COM-001-3","R3.3.",null,"Each Distribution Provider within its Transmission Operator Area.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26113,"COM-001-3","R3.4.",null,"Each Generator Operator within its Transmission Operator Area.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26114,"COM-001-3","R3.5.",null,"Each adjacent Transmission Operator synchronously connected.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26115,"COM-001-3","R3.6.",null,"Each adjacent Transmission Operator asynchronously connected.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26116,"COM-001-3","R4.",null,"Each Transmission Operator shall designate an Alternative Interpersonal Communication capability with the following entities:","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26117,"COM-001-3","R4.1.",null,"Its Reliability Coordinator.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26118,"COM-001-3","R4.2.",null,"Each Balancing Authority within its Transmission Operator Area.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26119,"COM-001-3","R4.3.",null,"Each adjacent Transmission Operator synchronously connected.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26120,"COM-001-3","R4.4.",null,"Each adjacent Transmission Operator asynchronously connected.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26121,"COM-001-3","R5.",null,"Each Balancing Authority shall have Interpersonal Communication capability with the following entities (unless the Balancing Authority detects a failure of its Interpersonal Communication capability in which case Requirement R10 shall apply):","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26122,"COM-001-3","R5.1.",null,"Its Reliability Coordinator.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26123,"COM-001-3","R5.2.",null,"Each Transmission Operator that operates Facilities within its Balancing Authority Area.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26124,"COM-001-3","R5.3.",null,"Each Distribution Provider within its Balancing Authority Area.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26125,"COM-001-3","R5.4.",null,"Each Generator Operator that operates Facilities within its Balancing Authority Area.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26126,"COM-001-3","R5.5.",null,"Each Adjacent Balancing Authority.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26127,"COM-001-3","R6.",null,"Each Balancing Authority shall designate an Alternative Interpersonal Communication capability with the following entities:","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26128,"COM-001-3","R6.1.",null,"Its Reliability Coordinator.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26129,"COM-001-3","R6.2.",null,"Each Transmission Operator that operates Facilities within its Balancing Authority Area.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26130,"COM-001-3","R6.3.",null,"Each Adjacent Balancing Authority.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26131,"COM-001-3","R7.",null,"Each Distribution Provider shall have Interpersonal Communication capability with the following entities (unless the Distribution Provider detects a failure of its Interpersonal Communication capability in which case Requirement R11 shall apply):","2017-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP","Yes",false,null,false]
[26132,"COM-001-3","R7.1.",null,"Its Balancing Authority.","2017-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP","Yes",false,null,false]
[26133,"COM-001-3","R7.2.",null,"Its Transmission Operator.","2017-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP","Yes",false,null,false]
[26134,"COM-001-3","R8.",null,"Each Generator Operator shall have Interpersonal Communication capability with the following entities (unless the Generator Operator detects a failure of its Interpersonal Communication capability in which case Requirement R11 shall apply):","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26135,"COM-001-3","R8.1.",null,"Its Balancing Authority.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26136,"COM-001-3","R8.2.",null,"Its Transmission Operator.","2017-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26137,"COM-001-3","R9.",null,"Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall test its Alternative Interpersonal Communication capability at least once each calendar month. If the test is unsuccessful, the responsible entity shall initiate action to repair or designate a replacement Alternative Interpersonal Communication capability within 2 hours.","2017-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26145,"COM-002-2a","R1.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, BA","Yes",true,null,false]
[26146,"COM-002-2a","R1.1.",null,"Each Balancing Authority 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.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26147,"COM-002-2a","R2.",null,"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 acknowledge the response as correct or repeat the original statement to resolve any misunderstandings.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,false]
[26148,"COM-002-3","R1.",null,"When a Reliability Coordinator, Transmission Operator, or Balancing Authority requires actions to be executed as a Reliability Directive, the Reliability Coordinator, Transmission Operator, or Balancing Authority shall identify the action as a Reliability Directive to the recipient. [Violation Risk Factor: High][Time Horizon: Real-Time]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,false]
[26149,"COM-002-3","R2.",null,"Each Balancing Authority, Transmission Operator, Generator Operator, and Distribution Provider that is the recipient of a Reliability Directive shall repeat, restate, rephrase, or recapitulate the Reliability Directive. [Violation Risk Factor: High][Time Horizon: Real-Time]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",true,null,false]
[26150,"COM-002-3","R3.",null,"Each Reliability Coordinator, Transmission Operator, and Balancing Authority that issues a Reliability Directive shall either: [Violation Risk Factor: High][Time Horizon: Real-Time]\n Confirm that the response from the recipient of the Reliability Directive (in accordance with Requirement R2) was accurate, or\n Reissue the Reliability Directive to resolve a misunderstanding.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,false]
[26151,"COM-002-4","R1.",null,"Each Balancing Authority, Reliability Coordinator, and Transmission Operator shall develop documented communications protocols for its operating personnel that issue and receive Operating Instructions. The protocols shall, at a minimum: [Violation Risk Factor: Low][Time Horizon: Long-term Planning]","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true,"Hydro One will comply with this requirement when communicating with the IESO and other (neighboring) TOPs. The IESO will be responsible for any communication with all other NERC entities."]
[26153,"COM-002-4","R1.1.",null,"Require its operating personnel that issue and receive an oral or written Operating Instruction to use the English language, unless agreed to otherwise. An alternate language may be used for internal operations.","2016-07-01",null,"Effective",null,"LOWER","UNLIKELY","LOW (Limited Controls Required)",null,"N/A","TOP, RC, BA","No",true,null,true]
[26155,"COM-002-4","R1.2.",null,"Require its operating personnel that issue an oral two-party, person-to-person Operating Instruction to take one of the following actions:\n Confirm the receiver’s response if the repeated information is correct.\n Reissue the Operating Instruction if the repeated information is incorrect or if requested by the receiver.\n Take an alternative action if a response is not received or if the Operating Instruction was not understood by the receiver.","2016-07-01",null,"Effective",null,"LOWER","UNLIKELY","LOW (Limited Controls Required)",null,"N/A","TOP, RC, BA","No",true,null,true,"Hydro One would not issue an Operating Instruction without the IESO's involvement, unless taking independent action as per IESO/Hydro One Operating Agreement"]
[26157,"COM-002-4","R1.3.",null,"Require its operating personnel that receive an oral two-party, person-to-person Operating Instruction to take one of the following actions:\n Repeat, not necessarily verbatim, the Operating Instruction and receive confirmation from the issuer that the response was correct.\n Request that the issuer reissue the Operating Instruction.","2016-07-01",null,"Effective",null,"LOWER","SOMEWHAT LIKELY","LOW (Limited Controls Required)",null,"N/A","TOP, RC, BA","No",true,null,true]
[26159,"COM-002-4","R1.4.",null,"Require its operating personnel that issue a written or oral single-party to multiple-party burst Operating Instruction to confirm or verify that the Operating Instruction was received by at least one receiver of the Operating Instruction.","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true,"Hydro One would not issue an Operating Instruction without the IESO's involvement, unless taking independent action as per IESO/Hydro One Operating Agreement"]
[26161,"COM-002-4","R1.5.",null,"Specify the instances that require time identification when issuing an oral or written Operating Instruction and the format for that time identification.","2016-07-01",null,"Effective",null,"LOWER","SOMEWHAT LIKELY","LOW (Limited Controls Required)",null,"N/A","TOP, RC, BA","No",true,null,true,"Hydro One would not issue an Operating Instruction without the IESO's involvement, unless taking independent action as per IESO/Hydro One Operating Agreement"]
[26163,"COM-002-4","R1.6.",null,"Specify the nomenclature for Transmission interface Elements and Transmission interface Facilities when issuing an oral or written Operating Instruction.","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,false]
[26165,"COM-002-4","R2.",null,"Each Balancing Authority, Reliability Coordinator, and Transmission Operator shall conduct initial training for each of its operating personnel responsible for the Real-time operation of the interconnected Bulk Electric System on the documented communications protocols developed in Requirement R1 prior to that individual operator issuing an Operating Instruction. [Violation Risk Factor: Low][Time Horizon: Long-term Planning]","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26166,"COM-002-4","R3.",null,"Each Distribution Provider and Generator Operator shall conduct initial training for each of its operating personnel who can receive an oral two-party, person-to-person Operating Instruction prior to that individual operator receiving an oral two-party, person-to-person Operating Instruction to either: [Violation Risk Factor: Low][Time Horizon: Long-term Planning]\n Repeat, not necessarily verbatim, the Operating Instruction and receive confirmation from the issuer that the response was correct, or\n Request that the issuer reissue the Operating Instruction.","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GOP, DP","Yes",false,null,false]
[26167,"COM-002-4","R4.",null,"Each Balancing Authority, Reliability Coordinator, and Transmission Operator shall at least once every twelve (12) calendar months: [Violation Risk Factor: Medium][Time Horizon: Operations Planning]","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26168,"COM-002-4","R4.1.",null,"Assess adherence to the documented communications protocols in Requirement R1 by its operating personnel that issue and receive Operating Instructions, provide feedback to those operating personnel and take corrective action, as deemed appropriate by the entity, to address deviations from the documented protocols.","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26169,"COM-002-4","R4.2.",null,"Assess the effectiveness of its documented communications protocols in Requirement R1 for its operating personnel that issue and receive Operating Instructions and modify its documented communication protocols, as necessary.","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26170,"COM-002-4","R5.",null,"Each Balancing Authority, Reliability Coordinator, and Transmission Operator that issues an oral two-party, person-to-person Operating Instruction during an Emergency, excluding written or oral single-party to multiple-party burst Operating Instructions, shall either: [Violation Risk Factor: High][Time Horizon: Real-time Operations]\n Confirm the receiver’s response if the repeated information is correct (in accordance with Requirement R6).\n Reissue the Operating Instruction if the repeated information is incorrect or if requested by the receiver, or\n Take an alternative action if a response is not received or if the Operating Instruction was not understood by the receiver.","2016-07-01",null,"Effective","Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, RC, BA","No",true,null,true,"Hydro One would not issue an Operating Instruction without the IESO's involvement, unless taking independent action as per IESO/Hydro One Operating Agreement"]
[26171,"COM-002-4","R6.",null,"Each Balancing Authority, Distribution Provider, Generator Operator, and Transmission Operator that receives an oral two-party, person-to-person Operating Instruction during an Emergency, excluding written or oral single-party to multiple-party burst Operating Instructions, shall either: [Violation Risk Factor: High][Time Horizon: Real-time Operations]\n Repeat, not necessarily verbatim, the Operating Instruction and receive confirmation from the issuer that the response was correct, or\n Request that the issuer reissue the Operating Instruction.","2016-07-01",null,"Effective","Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, GOP, DP, BA","Yes",true,null,true]
[26172,"COM-002-4","R7.",null,"Each Balancing Authority, Reliability Coordinator, and Transmission Operator that issues a written or oral single-party to multiple-party burst Operating Instruction during an Emergency shall confirm or verify that the Operating Instruction was received by at least one receiver of the Operating Instruction. [Violation Risk Factor: High][Time Horizon: Real-time Operations]","2016-07-01",null,"Effective","Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, RC, BA","No",true,null,true,"Hydro One would not issue an Operating Instruction without the IESO's involvement, unless taking independent action as per IESO/Hydro One Operating Agreement"]
[26173,"EOP-001-1","R1.",null,"Balancing Authorities shall have operating agreements with adjacent Balancing Authorities that shall, at a minimum, contain provisions for emergency assistance, including provisions to obtain emergency assistance from remote Balancing Authorities.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","BA","No",false,null,false]
[26175,"EOP-001-1","R2.","YES","Each Transmission Operator and Balancing Authority shall:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26174,"EOP-001-1","R2.","YES","Each Transmission Operator and Balancing Authority shall:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26176,"EOP-001-1","R2.1.",null,"Develop, maintain, and implement a set of plans to mitigate operating emergencies for insufficient generating capacity.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26177,"EOP-001-1","R2.2.",null,"Develop, maintain, and implement a set of plans to mitigate operating emergencies on the transmission system.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26178,"EOP-001-1","R2.3.",null,"Develop, maintain, and implement a set of plans for load shedding.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26179,"EOP-001-1","R2.4.",null,"Develop, maintain, and implement a set of plans for system restoration.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26180,"EOP-001-1","R3.",null,"Each Transmission Operator and Balancing Authority shall have emergency plans that will enable it to mitigate operating emergencies.  At a minimum, Transmission Operator and Balancing Authority emergency plans shall include:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26181,"EOP-001-1","R3.1.",null,"Communications protocols to be used during emergencies.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26182,"EOP-001-1","R3.2.",null,"A list of controlling actions to resolve the emergency.  Load reduction, in sufficient quantity to resolve the emergency within NERC-established timelines, shall be one of the controlling actions.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26183,"EOP-001-1","R3.3.",null,"The tasks to be coordinated with and among adjacent Transmission Operators and Balancing Authorities.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26184,"EOP-001-1","R3.4.",null,"Staffing levels for the emergency.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26185,"EOP-001-1","R4.",null,"Each Transmission Operator and Balancing Authority shall include the applicable elements in Attachment 1-EOP-001-0 when developing an emergency plan.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26186,"EOP-001-1","R5.",null,"The Transmission Operator and Balancing Authority shall annually review and update 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.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26188,"EOP-001-1","R6.","YES","The Transmission Operator and Balancing Authority shall coordinate its emergency plans with other Transmission Operators and Balancing Authorities as appropriate.  This coordination includes the following steps, as applicable:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26189,"EOP-001-1","R6.","YES","The Transmission Operator and Balancing Authority shall coordinate its emergency plans with other Transmission Operators and Balancing Authorities as appropriate.  This coordination includes the following steps, as applicable:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26187,"EOP-001-1","R6.","YES","The Transmission Operator and Balancing Authority shall coordinate its emergency plans with other Transmission Operators and Balancing Authorities as appropriate.  This coordination includes the following steps, as applicable:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26190,"EOP-001-1","R6.1.",null,"The Transmission Operator and Balancing Authority shall establish and maintain reliable communications between interconnected systems.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26191,"EOP-001-1","R6.2.",null,"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.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26192,"EOP-001-1","R6.3.",null,"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.)",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26193,"EOP-001-1","R6.4.",null,"The Transmission Operator and Balancing Authority shall arrange deliveries of electrical energy or fuel from remote systems through normal operating channels.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26194,"EOP-001-2","R1.",null,"Balancing Authorities shall have operating agreements with adjacent Balancing Authorities that shall, at a minimum, contain provisions for emergency assistance, including provisions to obtain emergency assistance from remote Balancing Authorities.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26195,"EOP-001-2","R2.","YES","Each Transmission Operator and Balancing Authority shall:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26196,"EOP-001-2","R2.","YES","Each Transmission Operator and Balancing Authority shall:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26197,"EOP-001-2","R2.1.",null,"Develop, maintain, and implement a set of plans to mitigate operating emergencies for insufficient generating capacity.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26198,"EOP-001-2","R2.2.",null,"Develop, maintain, and implement a set of plans to mitigate operating emergencies on the transmission system.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26199,"EOP-001-2","R2.3.",null,"Develop, maintain, and implement a set of plans for load shedding.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26200,"EOP-001-2","R3.",null,"Each Transmission Operator and Balancing Authority shall have emergency plans that will enable it to mitigate operating emergencies.  At a minimum, Transmission Operator and Balancing Authority emergency plans shall include:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26201,"EOP-001-2","R3.1.",null,"Communications protocols to be used during emergencies.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26202,"EOP-001-2","R3.2.",null,"A list of controlling actions to resolve the emergency.  Load reduction, in sufficient quantity to resolve the emergency within NERC-established timelines, shall be one of the controlling actions.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26203,"EOP-001-2","R3.3.",null,"The tasks to be coordinated with and among adjacent Transmission Operators and Balancing Authorities.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26204,"EOP-001-2","R3.4.",null,"Staffing levels for the emergency.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26205,"EOP-001-2","R4.",null,"Each Transmission Operator and Balancing Authority shall include the applicable elements in Attachment 1-EOP-001-0 when developing an emergency plan.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26206,"EOP-001-2","R5.",null,"The Transmission Operator and Balancing Authority shall annually review and update 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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26209,"EOP-001-2","R6.","YES","The Transmission Operator and Balancing Authority shall coordinate its emergency plans with other Transmission Operators and Balancing Authorities as appropriate.  This coordination includes the following steps, as applicable:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26208,"EOP-001-2","R6.","YES","The Transmission Operator and Balancing Authority shall coordinate its emergency plans with other Transmission Operators and Balancing Authorities as appropriate.  This coordination includes the following steps, as applicable:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26207,"EOP-001-2","R6.","YES","The Transmission Operator and Balancing Authority shall coordinate its emergency plans with other Transmission Operators and Balancing Authorities as appropriate.  This coordination includes the following steps, as applicable:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26210,"EOP-001-2","R6.1.",null,"The Transmission Operator and Balancing Authority shall establish and maintain reliable communications between interconnected systems.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26211,"EOP-001-2","R6.2.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26212,"EOP-001-2","R6.3.",null,"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.)",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26213,"EOP-001-2","R6.4.",null,"The Transmission Operator and Balancing Authority shall arrange deliveries of electrical energy or fuel from remote systems through normal operating channels.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26214,"EOP-001-2b","R1.",null,"Balancing Authorities shall have operating agreements with adjacent Balancing Authorities that shall, at a minimum, contain provisions for emergency assistance, including provisions to obtain emergency assistance from remote Balancing Authorities.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26216,"EOP-001-2b","R2.","YES","Each Transmission Operator and Balancing Authority shall:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26215,"EOP-001-2b","R2.","YES","Each Transmission Operator and Balancing Authority shall:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26217,"EOP-001-2b","R2.1.",null,"Develop, maintain, and implement a set of plans to mitigate operating emergencies for insufficient generating capacity.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26218,"EOP-001-2b","R2.2.",null,"Develop, maintain, and implement a set of plans to mitigate operating emergencies on the transmission system.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26219,"EOP-001-2b","R2.3.",null,"Develop, maintain, and implement a set of plans for load shedding.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26220,"EOP-001-2b","R3.",null,"Each Transmission Operator and Balancing Authority shall have emergency plans that will enable it to mitigate operating emergencies.  At a minimum, Transmission Operator and Balancing Authority emergency plans shall include:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26221,"EOP-001-2b","R3.1.",null,"Communications protocols to be used during emergencies.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26222,"EOP-001-2b","R3.2.",null,"A list of controlling actions to resolve the emergency.  Load reduction, in sufficient quantity to resolve the emergency within NERC-established timelines, shall be one of the controlling actions.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26223,"EOP-001-2b","R3.3.",null,"The tasks to be coordinated with and among adjacent Transmission Operators and Balancing Authorities.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26224,"EOP-001-2b","R3.4.",null,"Staffing levels for the emergency.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26225,"EOP-001-2b","R4.",null,"Each Transmission Operator and Balancing Authority shall include the applicable elements in Attachment 1-EOP-001-0 when developing an emergency plan.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26226,"EOP-001-2b","R5.",null,"The Transmission Operator and Balancing Authority shall annually review and update 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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26229,"EOP-001-2b","R6.","YES","The Transmission Operator and Balancing Authority shall coordinate its emergency plans with other Transmission Operators and Balancing Authorities as appropriate.  This coordination includes the following steps, as applicable:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26228,"EOP-001-2b","R6.","YES","The Transmission Operator and Balancing Authority shall coordinate its emergency plans with other Transmission Operators and Balancing Authorities as appropriate.  This coordination includes the following steps, as applicable:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26227,"EOP-001-2b","R6.","YES","The Transmission Operator and Balancing Authority shall coordinate its emergency plans with other Transmission Operators and Balancing Authorities as appropriate.  This coordination includes the following steps, as applicable:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26230,"EOP-001-2b","R6.1.",null,"The Transmission Operator and Balancing Authority shall establish and maintain reliable communications between interconnected systems.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26231,"EOP-001-2b","R6.2.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26232,"EOP-001-2b","R6.3.",null,"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.)",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26233,"EOP-001-2b","R6.4.",null,"The Transmission Operator and Balancing Authority shall arrange deliveries of electrical energy or fuel from remote systems through normal operating channels.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[26279,"EOP-004-3","R1.",null,"Each Responsible Entity shall have an event reporting Operating Plan in accordance with EOP-004-2-3 Attachment 1 that includes the protocol(s) for reporting to the Electric Reliability Organization and other organizations (e.g., the Regional Entity, company\npersonnel, the Responsible Entity’s Reliability Coordinator, law enforcement, or governmental authority). [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2017-04-01","2019-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",false,null,false]
[26281,"EOP-004-3","R2.",null,"Each Responsible Entity shall report events per their Operating Plan within 24 hours of recognition of meeting an event type threshold for reporting or by the end of the next business day if the event occurs on a weekend (which is recognized to be 4 PM local time on Friday to 8 AM Monday local time). [Violation Risk Factor: Medium] [Time Horizon: Operations Assessment]","2017-04-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true]
[26283,"EOP-004-3","R3.",null,"Each Responsible Entity shall validate all contact information contained in the Operating Plan pursuant to Requirement R1 each calendar year. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,false]
[26284,"EOP-004-4","R1.",null,"Each Responsible Entity shall have an event reporting Operating Plan in accordance with EOP-004-4 Attachment 1 that includes the protocol(s) for reporting to the Electric Reliability Organization and other organizations (e.g., the Regional Entity, company personnel, the Responsible Entity’s Reliability Coordinator, law enforcement, or governmental authority). [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2019-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true,"\"The IESO is the only entity that reports \"\"events\"\" to NERC (ERO).  However, for R1 Hydro One is still required to have an Operating Plan that includes the protocol(s) for reporting to other organizations.\n\nAccording to the MOU between the IESO, NERC and NPCC, the IESO is accountable to report to NERC (ERO) and NPCC (RE) on behalf of Ontario.  Hydro One will report to the IESO, internally and to law enforcement.  \""]
[26287,"EOP-004-4","R2.",null,"Each Responsible Entity shall report events specified in EOP-004-4 Attachment 1 to the entities specified per their event reporting Operating Plan by the later of 24 hours of recognition of meeting an event type threshold for reporting or by the end of the Responsible Entity’s next business day (4 p.m. local time will be considered the end of the business day). [Violation Risk Factor: Medium] [Time Horizon: Operations Assessment]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, GOP, GO, DP, BA","Yes",true,null,true,"The current acceptable practice is that Hydro One reports all events to the IESO verbally. Written reports/forms only need to be filled out if explicity requested by the IESO on a case by case basis."]
[26288,"EOP-005-2","R1.",null,"Each Transmission Operator shall have a restoration plan approved by its Reliability Coordinator. The restoration plan shall allow for restoring the Transmission Operator’s System following a Disturbance in which one or more areas of the Bulk Electric System (BES) shuts down and the use of Blackstart Resources is required to restore the shut down area to service, to a state whereby the choice of the next Load to be restored is not driven by the need to control frequency or voltage regardless of whether the Blackstart Resource is located within the Transmission Operator’s System. The restoration plan shall include:","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Segregation of Duties; Tools and Applications; Training","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26289,"EOP-005-2","R1.1.",null,"Strategies for system restoration that are coordinated with the Reliability Coordinator’s high level strategy for restoring the Interconnection.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Segregation of Duties; Tools and Applications; Training","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26290,"EOP-005-2","R1.2.",null,"A description of how all Agreements or mutually agreed upon procedures or protocols for off-site power requirements of nuclear power plants, including priority of restoration, will be fulfilled during System restoration.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Segregation of Duties; Tools and Applications; Training","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26291,"EOP-005-2","R1.3.",null,"Procedures for restoring interconnections with other Transmission Operators under the direction of the Reliability Coordinator.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Segregation of Duties; Tools and Applications; Training","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26292,"EOP-005-2","R1.4.",null,"Identification of each Blackstart Resource and its characteristics including but not limited to the following: the name of the Blackstart Resource, location, megawatt and megavar capacity, and type of unit.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Segregation of Duties; Tools and Applications; Training","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26293,"EOP-005-2","R1.5.",null,"Identification of Cranking Paths and initial switching requirements between each Blackstart Resource and the unit(s) to be started.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Segregation of Duties; Tools and Applications; Training","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26294,"EOP-005-2","R1.6.",null,"Identification of acceptable operating voltage and frequency limits during restoration.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Segregation of Duties; Tools and Applications; Training","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26295,"EOP-005-2","R1.7.",null,"Operating Processes to reestablish connections within the Transmission Operator’s System for areas that have been restored and are prepared for reconnection.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Segregation of Duties; Tools and Applications; Training","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,true]
[26296,"EOP-005-2","R1.8.",null,"Operating Processes to restore Loads required to restore the System, such as station service for substations, units to be restarted or stabilized, the Load needed to stabilize generation and frequency, and provide voltage control.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Segregation of Duties; Tools and Applications; Training","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,true]
[26297,"EOP-005-2","R1.9.",null,"Operating Processes for transferring authority back to the Balancing Authority in accordance with the Reliability Coordinator’s criteria.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Segregation of Duties; Tools and Applications; Training","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26316,"EOP-005-2","R10.",null,"Each Transmission Operator shall include within its operations training program, annual System restoration training for its System Operators to assure the proper execution of its restoration plan. This training program shall include training on the following:","2013-07-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26317,"EOP-005-2","R10.1.",null,"System restoration plan including coordination with the Reliability Coordinator and Generator Operators included in the restoration plan.","2013-07-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26318,"EOP-005-2","R10.2.",null,"Restoration priorities.","2013-07-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26319,"EOP-005-2","R10.3.",null,"Building of cranking paths.","2013-07-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26320,"EOP-005-2","R10.4.",null,"Synchronizing (re-energized sections of the System).","2013-07-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26321,"EOP-005-2","R11.",null,"Each Transmission Operator, each applicable Transmission Owner, and each applicable Distribution Provider shall provide a minimum of two hours of System restoration training every two calendar years to their field switching personnel identified as performing unique tasks associated with the Transmission Operator’s restoration plan that are outside of their normal tasks.","2013-07-01","2019-03-31","Retired","Communications; Documentations, Policies and Procedures","MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, TO, DP","Yes",false,null,true]
[26322,"EOP-005-2","R12.",null,"Each Transmission Operator shall participate in its Reliability Coordinator’s restoration drills, exercises, or simulations as requested by its Reliability Coordinator.","2013-07-01","2019-03-31","Retired","Communications; Documentations, Policies and Procedures","MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,true]
[26323,"EOP-005-2","R13.",null,"Each Transmission Operator and each Generator Operator with a Blackstart Resource shall have written Blackstart Resource Agreements or mutually agreed upon procedures or protocols, specifying the terms and conditions of their arrangement. Such Agreements shall include references to the Blackstart Resource testing requirements.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, GOP","Yes",true,null,false]
[26324,"EOP-005-2","R14.",null,"Each Generator Operator with a Blackstart Resource shall have documented procedures for starting each Blackstart Resource and energizing a bus.","2013-07-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26325,"EOP-005-2","R15.",null,"Each Generator Operator with a Blackstart Resource shall notify its Transmission Operator of any known changes to the capabilities of that Blackstart Resource affecting the ability to meet the Transmission Operator’s restoration plan within 24 hours following such change.","2013-07-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26326,"EOP-005-2","R16.",null,"Each Generator Operator with a Blackstart Resource shall perform Blackstart Resource tests, and maintain records of such testing, in accordance with the testing requirements set by the Transmission Operator to verify that the Blackstart Resource can perform as specified in the restoration plan.","2013-07-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26327,"EOP-005-2","R16.1.",null,"Testing records shall include at a minimum: name of the Blackstart Resource, unit tested, date of the test, duration of the test, time required to start the unit, an indication of any testing requirements not met under Requirement R9.","2013-07-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26328,"EOP-005-2","R16.2.",null,"Each Generator Operator shall provide the blackstart test results within 30 calendar days following a request from its Reliability Coordinator or Transmission Operator.","2013-07-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26329,"EOP-005-2","R17.",null,"Each Generator Operator with a Blackstart Resource shall provide a minimum of two hours of training every two calendar years to each of its operating personnel responsible for the startup of its Blackstart Resource generation units and energizing a bus. The training program shall include training on the following:","2013-07-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26330,"EOP-005-2","R17.1.",null,"System restoration plan including coordination with the Transmission Operator.","2013-07-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26331,"EOP-005-2","R17.2.",null,"The procedures documented in Requirement R14.","2013-07-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26332,"EOP-005-2","R18.",null,"Each Generator Operator shall participate in the Reliability Coordinator’s restoration drills, exercises, or simulations as requested by the Reliability Coordinator.","2013-07-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26298,"EOP-005-2","R2.",null,"Each Transmission Operator shall provide the entities identified in its approved restoration plan with a description of any changes to their roles and specific tasks prior to the implementation date of the plan.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring","MEDIUM","SOMEWHAT LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26299,"EOP-005-2","R3.",null,"Each Transmission Operator shall review its restoration plan and submit it to its Reliability Coordinator annually on a mutually agreed predetermined schedule.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring","MEDIUM","SOMEWHAT LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26300,"EOP-005-2","R4.",null,"Each Transmission Operator shall update its restoration plan within 90 calendar days after identifying any unplanned permanent System modifications, or prior to implementing a planned BES modification, that would change the implementation of its restoration plan.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Segregation of Duties; Training","MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26301,"EOP-005-2","R4.1.",null,"Each Transmission Operator shall submit its revised restoration plan to itsReliability Coordinator for approval within the same 90 calendar day period.","2013-07-01","2019-03-31","Retired","Communications; Documentations, Policies and Procedures","MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26302,"EOP-005-2","R5.",null,"Each Transmission Operator shall have a copy of its latest Reliability Coordinator approved restoration plan within its primary and backup control rooms so that it is available to all of its System Operators prior to its implementation date.","2013-07-01","2019-03-31","Retired","Communications; Documentations, Policies and Procedures","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,true]
[26303,"EOP-005-2","R6.","YES","Each Transmission Operator shall verify through analysis of actual events, steady state and dynamic simulations, or testing that its restoration plan accomplishes its intended function. This shall be completed every five years at a minimum. Such analysis, simulations or testing shall verify:","2013-07-01","2019-03-31","Retired","Authorization/Approval; Documentations, Policies and Procedures; Quality Check/Verification; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26304,"EOP-005-2","R6.","YES","Each Transmission Operator shall verify through analysis of actual events, steady state and dynamic simulations, or testing that its restoration plan accomplishes its intended function. This shall be completed every five years at a minimum. Such analysis, simulations or testing shall verify:","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26305,"EOP-005-2","R6.1.",null,"The capability of Blackstart Resources to meet the Real and Reactive Power requirements of the Cranking Paths and the dynamic capability to supply initial Loads.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Documentations, Policies and Procedures; Quality Check/Verification; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26306,"EOP-005-2","R6.2.",null,"The location and magnitude of Loads required to control voltages and frequency within acceptable operating limits.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Documentations, Policies and Procedures; Quality Check/Verification; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26307,"EOP-005-2","R6.3.",null,"The capability of generating resources required to control voltages and frequency within acceptable operating limits.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Documentations, Policies and Procedures; Quality Check/Verification; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26308,"EOP-005-2","R7.",null,"Following a Disturbance in which one or more areas of the BES shuts down and the use of Blackstart Resources is required to restore the shut down area to service, each affected Transmission Operator shall implement its restoration plan. If the restoration plan cannot be executed as expected the Transmission Operator shall utilize its restoration strategies to facilitate restoration.","2013-07-01","2019-03-31","Retired","Documentations, Policies and Procedures","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,true]
[26309,"EOP-005-2","R8.",null,"Following a Disturbance in which one or more areas of the BES shuts down and the use of Blackstart Resources is required to restore the shut down area to service, the Transmission Operator shall resynchronize area(s) with neighboring Transmission Operator area(s) only with the authorization of the Reliability Coordinator or in accordance with the established procedures of the Reliability Coordinator.","2013-07-01","2019-03-31","Retired","Documentations, Policies and Procedures","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,true]
[26310,"EOP-005-2","R9.",null,"Each Transmission Operator shall have Blackstart Resource testing requirements to verify that each Blackstart Resource is capable of meeting the requirements of its restoration plan. These Blackstart Resource testing requirements shall include:","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Segregation of Duties","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26311,"EOP-005-2","R9.1.",null,"The frequency of testing such that each Blackstart Resource is tested at least once every three calendar years.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Segregation of Duties","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26312,"EOP-005-2","R9.2.",null,"A list of required tests including:","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Segregation of Duties","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26313,"EOP-005-2","R9.2.1.",null,"The ability to start the unit when isolated with no support from the BES or when designed to remain energized without connection to the remainder of the System.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Segregation of Duties","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26314,"EOP-005-2","R9.2.2.",null,"The ability to energize a bus. If it is not possible to energize a bus during the test, the testing entity must affirm that the unit has the capability to energize a bus such as verifying that the breaker close coil relay can be energized with the voltage and frequency monitor controls disconnected from the synchronizing circuits.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Segregation of Duties","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26315,"EOP-005-2","R9.3.",null,"The minimum duration of each of the required tests.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Segregation of Duties","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26333,"EOP-005-3","R1.",null,"Each Transmission Operator shall develop and implement a restoration plan approved by its Reliability Coordinator. The restoration plan shall be implemented to restore the Transmission Operator’s System following a Disturbance in which one or more areas of the Bulk Electric System (BES) shuts down and the use of Blackstart Resources is required to restore the shutdown area to a state whereby the choice of the next Load to be restored is not driven by the need to control frequency or voltage regardless of whether the Blackstart Resource is located within the Transmission Operator’s System. The restoration plan shall include: [Violation Risk Factor = High] [Time Horizon = Operations Planning, Real-time Operations]","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,"\"The IESO has the Ontario Power System Restoration Plan (OPSRP) to re-establish its electric system in a stable and orderly manner. This obligation is laid out in the market rules, Section 11, Ch. 5 of market rules                                                                                           The IESO also has an Emergency Preparedness Task Force (EPTF) which helps in preparing and providing the long-term maintenance of an integrated emergency preparedness plan. This plan, the Ontario Electricity Emergency Plan (OEEP), provides the framework for developing the emergency planning and response process in the event of a major electricity emergency. The EPTF plays an advisory role to the IESO.  The IESO also has a Crisis Management Support Team (CMST). The purpose of the CMST  is to provide a forum for Ontario’s electricity industry participants and stakeholders to co-ordinate emergency management initiatives, information and response during a major electricity emergency.\nCh 5, S11.2 specifies the obligation of the IESO with respect to these plans and S11.3 describes the role of MP.\nMM7.8 - OPSRP & Section 10, which specifies MP attachments requirements.                 Market Rules, Ontario Power System Restoration Plan (OPSRP)\"",true,"See Requirement 1.8.  Hydro One is an integral transmission participant of  the Ontario Power System Restoration Plan (OPSRP) and participates in all aspects of its development including:                                                                                                  • Determination of equipment operating and synchronization capability      • Energization parameters (e.g. charging current)                                               • Testing criteria and frequency based on industry accepted standards and practices (e.g. IEEE)                                                                                     Hydro One also has an internal Emergency Preparedness program that includes participation on the Emergency Preparedness Task Force, Crisis Management Support Team and the Ontario Electricity Emergency Plan."]
[26334,"EOP-005-3","R1.1.",null,"Strategies for System restoration that are coordinated with its Reliability Coordinator’s high level strategy for restoring the Interconnection.","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26335,"EOP-005-3","R1.2.",null,"1.2. A description of how all Agreements or mutually-agreed upon procedures or protocols for off-site power requirements of nuclear power plants, including priority of restoration, will be fulfilled during System restoration.","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26336,"EOP-005-3","R1.3.",null,"1.3. Procedures for restoring interconnections with other Transmission Operators under the direction of its Reliability Coordinator.","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26337,"EOP-005-3","R1.4.",null,"1.4. Identification of each Blackstart Resource and its characteristics including but not limited to the following: the name of the Blackstart Resource, location, megawatt and megavar capacity, and type of unit.","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26338,"EOP-005-3","R1.5.",null,"Identification of Cranking Paths and initial switching requirements between each Blackstart Resource and the unit(s) to be started.","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26339,"EOP-005-3","R1.6.",null,"1.6. Identification of acceptable operating voltage and frequency limits during restoration.","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26340,"EOP-005-3","R1.7.",null,"1.7. Operating Processes to reestablish connections within the Transmission Operator’s System for areas that have been restored and are prepared for reconnection.","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26341,"EOP-005-3","R1.8.",null,"1.8. Operating Processes to restore Loads required to restore the System, such as station service for substations, units to be restarted or stabilized, the Load needed to stabilize generation and frequency, and provide voltage control.","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true,"Hydro One is responsible for station service availability requirements as outlined in the OPSRP."]
[26342,"EOP-005-3","R1.9.",null,"1.9. Operating Processes for transferring operations back to the Balancing Authority in accordance with its Reliability Coordinator’s criteria.","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26367,"EOP-005-3","R10.",null,"Each Transmission Operator shall participate in its Reliability Coordinator’s restoration drills, exercises, or simulations as requested by its Reliability Coordinator. [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26368,"EOP-005-3","R11.",null,"Each Transmission Operator and each Generator Operator with a Blackstart Resource shall have written Blackstart Resource Agreements or mutually agreed upon procedures or protocols, specifying the terms and conditions of their arrangement. Such Agreements shall include references to the Blackstart Resource testing requirements. [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, GOP","Yes",true,null,false]
[26369,"EOP-005-3","R12.",null,"Each Generator Operator with a Blackstart Resource shall have documented procedures for starting each Blackstart Resource and energizing a bus. [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26370,"EOP-005-3","R13.",null,"Each Generator Operator with a Blackstart Resource shall notify its Transmission Operator of any known changes to the capabilities of that Blackstart Resource affecting the ability to meet the Transmission Operator’s restoration plan within 24 hours following such change. [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26371,"EOP-005-3","R14.",null,"Each Generator Operator with a Blackstart Resource shall perform Blackstart Resource tests, and maintain records of such testing, in accordance with the testing requirements set by the Transmission Operator to verify that the Blackstart Resource can perform as specified in the restoration plan. [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26372,"EOP-005-3","R14.1.",null,"Testing records shall include at a minimum: name of the Blackstart Resource, unit tested, date of the test, duration of the test, time required to start the unit, an indication of any testing requirements not met under Requirement R7.","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26373,"EOP-005-3","R14.2.",null,"Each Generator Operator shall provide the blackstart test results within 30 calendar days following a request from its Reliability Coordinator or Transmission Operator.","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26374,"EOP-005-3","R15.",null,"Each Generator Operator with a Blackstart Resource shall provide a minimum of two hours of training every two calendar years to each of its operating personnel responsible for the startup of its Blackstart Resource generation units and energizing a bus. The training program shall include training on the following: [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26375,"EOP-005-3","R15.1.",null,"System restoration plan including coordination with the Transmission Operator","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26376,"EOP-005-3","R15.2.",null,"The procedures documented in Requirement R12","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26377,"EOP-005-3","R16.",null,"Each Generator Operator shall participate in its Reliability Coordinator’s restoration drills, exercises, or simulations as requested by its Reliability Coordinator. [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[26343,"EOP-005-3","R2.",null,"Each Transmission Operator shall provide the entities identified in its approved restoration plan with a description of any changes to their roles and specific tasks prior to the effective date of the plan. [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26344,"EOP-005-3","R3.",null,"Each Transmission Operator shall review its restoration plan and submit it to its Reliability Coordinator annually on a mutually-agreed, predetermined schedule. [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false,"Hydro One reviews its restoration plan annually and certifies to the IESO that a review has been performed."]
[26345,"EOP-005-3","R4.",null,"Each Transmission Operator shall submit its revised restoration plan to its Reliability Coordinator for approval, when the revision would change its ability to implement its restoration plan, as follows: [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true,"Hydro One shall review and update its Restoration Participant Attachment as per the requirement."]
[26346,"EOP-005-3","R4.1.",null,"Within 90 calendar days after identifying any unplanned permanent BES modifications.","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true,"Hydro One shall review and update its Restoration Participant Attachment as per the requirement."]
[26347,"EOP-005-3","R4.2.",null,"4.2. Prior to implementing a planned permanent BES modification subject to its Reliability Coordinator approval requirements per EOP-006.","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true,"Hydro One shall review and update its Restoration Participant Attachment as per the requirement."]
[26348,"EOP-005-3","R5.",null,"Each Transmission Operator shall have a copy of its latest Reliability Coordinator approved restoration plan within its primary and backup control rooms so that it is available to all of its System Operators prior to its effective date. [Violation Risk Factor = Lower] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26349,"EOP-005-3","R6.","YES","Each Transmission Operator shall verify through analysis of actual events, a combination of steady state and dynamic simulations, or testing that its restoration plan accomplishes its intended function. This shall be completed at least once every five years. Such analysis, simulations or testing shall verify: [Violation Risk Factor = Medium] [Time Horizon = Long-term Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26350,"EOP-005-3","R6.","YES","Each Transmission Operator shall verify through analysis of actual events, a combination of steady state and dynamic simulations, or testing that its restoration plan accomplishes its intended function. This shall be completed at least once every five years. Such analysis, simulations or testing shall verify: [Violation Risk Factor = Medium] [Time Horizon = Long-term Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26351,"EOP-005-3","R6.1.",null,"The capability of Blackstart Resources to meet the Real and Reactive Power requirements of the Cranking Paths and the dynamic capability to supply initial Loads.","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26352,"EOP-005-3","R6.2.",null,"The location and magnitude of Loads required to control voltages and frequency within acceptable operating limits.","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26353,"EOP-005-3","R6.3.",null,"The capability of generating resources required to control voltages and frequency within acceptable operating limits.","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26354,"EOP-005-3","R7.",null,"Each Transmission Operator shall have Blackstart Resource testing requirements to verify that each Blackstart Resource is capable of meeting the requirements of its restoration plan. These Blackstart Resource testing requirements shall include: [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26355,"EOP-005-3","R7.1.",null,"The frequency of testing such that each Blackstart Resource is tested at least once every three calendar years.","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26356,"EOP-005-3","R7.2.",null,"A list of required tests including:","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26357,"EOP-005-3","R7.2.1.",null,"The ability to start the unit when isolated with no support from the BES or when designed to remain energized without connection to the remainder of the System.","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26358,"EOP-005-3","R7.2.2.",null,"The ability to energize a bus. If it is not possible to energize a bus during the test, the testing entity must affirm that the unit has the capability to energize a bus such as verifying that the breaker close coil relay can be energized with the voltage and frequency monitor controls disconnected from the synchronizing circuits.","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26359,"EOP-005-3","R7.3.",null,"The minimum duration of each of the required tests.","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26360,"EOP-005-3","R8.",null,"Each Transmission Operator shall include within its operations training program, annual System restoration training for its System Operators. This training program shall include training on the following: [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26361,"EOP-005-3","R8.1.",null,"System restoration plan including coordination with its Reliability Coordinator and Generator Operators included in the restoration plan.","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26362,"EOP-005-3","R8.2.",null,"Restoration priorities.","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26363,"EOP-005-3","R8.3.",null,"Building of cranking paths.","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26364,"EOP-005-3","R8.4.",null,"Synchronizing (re-energized sections of the System).","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true]
[26365,"EOP-005-3","R8.5.",null,"Transition of Demand and resource balance within its area to the Balancing Authority","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26366,"EOP-005-3","R9.",null,"Each Transmission Operator, each applicable Transmission Owner, and each applicable Distribution Provider shall provide a minimum of two hours of System restoration training every two calendar years to their field switching personnel identified as performing unique tasks associated with the Transmission Operator’s restoration plan that are outside of their normal tasks. [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, DP","Yes",true,null,false]
[26378,"EOP-006-2","R1.",null,"Each Reliability Coordinator shall have a Reliability Coordinator Area restoration plan. The scope of the Reliability Coordinator’s restoration plan starts when Blackstart Resources are utilized to re-energize a shut down area of the Bulk Electric System\n(BES), or separation has occurred between neighboring Reliability Coordinators, or an energized island has been formed on the BES within the Reliability Coordinator Area. The scope of the Reliability Coordinator’s restoration plan ends when all of its Transmission Operators are interconnected and it its Reliability Coordinator Area is connected to all of its neighboring Reliability Coordinator Areas. The restoration plan shall include:","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[26379,"EOP-006-2","R1.1.",null,"A description of the high level strategy to be employed during restoration events for restoring the Interconnection including minimum criteria for meeting the objectives of the Reliability Coordinator’s restoration plan.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring","No Individual VRF Assigned","LIKELY","N/A","UNLIKELY","N/A","RC","No",false,null,false]
[26380,"EOP-006-2","R1.2.",null,"Operating Processes for restoring the Interconnection.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring","No Individual VRF Assigned","LIKELY","N/A","UNLIKELY","N/A","RC","No",false,null,false]
[26381,"EOP-006-2","R1.3.",null,"Descriptions of the elements of coordination between individual Transmission Operator restoration plans.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring","No Individual VRF Assigned","LIKELY","N/A","UNLIKELY","N/A","RC","No",false,null,false]
[26382,"EOP-006-2","R1.4.",null,"Descriptions of the elements of coordination of restoration plans with neighboring Reliability Coordinators.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring","No Individual VRF Assigned","LIKELY","N/A","UNLIKELY","N/A","RC","No",false,null,false]
[26383,"EOP-006-2","R1.5.",null,"Criteria and conditions for reestablishing interconnections with other Transmission Operators within its Reliability Coordinator Area, with Transmission Operators in other Reliability Coordinator Areas, and with other Reliability Coordinators.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring","No Individual VRF Assigned","LIKELY","N/A","UNLIKELY","N/A","RC","No",false,null,false]
[26384,"EOP-006-2","R1.6.",null,"Reporting requirements for the entities within the Reliability Coordinator Area during a restoration event.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring","No Individual VRF Assigned","LIKELY","N/A","UNLIKELY","N/A","RC","No",false,null,false]
[26385,"EOP-006-2","R1.7.",null,"Criteria for sharing information regarding restoration with neighboring Reliability Coordinators and with Transmission Operators and Balancing Authorities within its Reliability Coordinator Area.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring","No Individual VRF Assigned","LIKELY","N/A","UNLIKELY","N/A","RC","No",false,null,false]
[26386,"EOP-006-2","R1.8.",null,"Identification of the Reliability Coordinator as the primary contact for disseminating information regarding restoration to neighboring Reliability Coordinators, and to Transmission Operators, and Balancing Authorities within its Reliability Coordinator Area.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring","No Individual VRF Assigned","LIKELY","N/A","UNLIKELY","N/A","RC","No",false,null,false]
[26387,"EOP-006-2","R1.9.",null,"Criteria for transferring operations and authority back to the Balancing Authority.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring","No Individual VRF Assigned","LIKELY","N/A","UNLIKELY","N/A","RC","No",false,null,false]
[26400,"EOP-006-2","R10.",null,"Each Reliability Coordinator shall conduct two System restoration drills, exercises, or simulations per calendar year, which shall include the Transmission Operators and Generator Operators as dictated by the particular scope of the drill, exercise, or simulation that is being conducted.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Tools and Applications; Training","MEDIUM","SOMEWHAT LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[26401,"EOP-006-2","R10.1.",null,"Each Reliability Coordinator shall request each Transmission Operator identified in its restoration plan and each Generator Operator identified in the Transmission Operators’ restoration plans to participate in a drill, exercise, or simulation at least every two calendar years.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Tools and Applications; Training","No Individual VRF Assigned","SOMEWHAT LIKELY","N/A","UNLIKELY","N/A","RC","No",false,null,false]
[26388,"EOP-006-2","R2.",null,"The Reliability Coordinator shall distribute its most recent Reliability Coordinator Area restoration plan to each of its Transmission Operators and neighboring Reliability Coordinators within 30 calendar days of creation or revision.","2013-07-01","2019-03-31","Retired","Communications; Documentations, Policies and Procedures","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[26389,"EOP-006-2","R3.",null,"Each Reliability Coordinator shall review its restoration plan within 13 calendar months of the last review.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring","MEDIUM","SOMEWHAT LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[26390,"EOP-006-2","R4.",null,"Each Reliability Coordinator shall review their neighboring Reliability Coordinator’s restoration plans.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring","MEDIUM","SOMEWHAT LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[26391,"EOP-006-2","R4.1.",null,"If the Reliability Coordinator finds conflicts between its restoration plans and any of its neighbors, the conflicts shall be resolved in 30 calendar days.","2013-07-01","2019-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring","No Individual VRF Assigned","SOMEWHAT LIKELY","N/A","UNLIKELY","N/A","RC","No",false,null,false]
[26392,"EOP-006-2","R5.",null,"Each Reliability Coordinator shall review the restoration plans required by EOP-005 of the Transmission Operators within its Reliability Coordinator Area.","2013-07-01","2019-03-31","Retired","Communications; Documentations, Policies and Procedures","MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[26393,"EOP-006-2","R5.1.",null,"The Reliability Coordinator shall determine whether the Transmission Operator’s restoration plan is coordinated and compatible with the Reliability Coordinator’s restoration plan and other Transmission Operators’ restoration plans within its Reliability Coordinator Area. The Reliability Coordinator shall approve or disapprove, with stated reasons, the Transmission Operator’s submitted restoration plan within 30 calendar days following the receipt of the restoration plan from the Transmission Operator.","2013-07-01","2019-03-31","Retired","Communications; Documentations, Policies and Procedures","No Individual VRF Assigned","UNLIKELY","N/A","UNLIKELY","N/A","RC","No",false,null,false]
[26394,"EOP-006-2","R6.",null,"Each Reliability Coordinator shall have a copy of its latest restoration plan and copies of the latest approved restoration plan of each Transmission Operator in its Reliability Coordinator Area within its primary and backup control rooms so that it is available to all of its System Operators prior to the implementation date.","2013-07-01","2019-03-31","Retired","Communications; Documentations, Policies and Procedures","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[26395,"EOP-006-2","R7.",null,"Each Reliability Coordinator shall work with its affected Generator Operators, and Transmission Operators as well as neighboring Reliability Coordinators to monitor restoration progress, coordinate restoration, and take actions to restore the BES frequency within acceptable operating limits. If the restoration plan cannot be completed as expected the Reliability Coordinator shall utilize its restoration plan strategies to facilitate System restoration.","2013-07-01","2019-03-31","Retired","Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[26396,"EOP-006-2","R8.",null,"The Reliability Coordinator shall coordinate or authorize resynchronizing islanded areas that bridge boundaries between Transmission Operators or Reliability Coordinators. If the resynchronization cannot be completed as expected the Reliability Coordinator shall utilize its restoration plan strategies to facilitate resynchronization.","2013-07-01","2019-03-31","Retired","Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[26397,"EOP-006-2","R9.",null,"Each Reliability Coordinator shall include within its operations training program, annual System restoration training for its System Operators to assure the proper execution of its restoration plan. This training program shall address the following:","2013-07-01","2019-03-31","Retired","Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","SOMEWHAT LIKELY","MEDIUM (Moderate Controls)","RC","No",false,null,false]
[26398,"EOP-006-2","R9.1.",null,"The coordination role of the Reliability Coordinator.","2013-07-01","2019-03-31","Retired","Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Training","No Individual VRF Assigned","VERY LIKELY","N/A","SOMEWHAT LIKELY","N/A","RC","No",false,null,false]
[26399,"EOP-006-2","R9.2.",null,"Reestablishing the Interconnection.","2013-07-01","2019-03-31","Retired",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[26402,"EOP-006-3","R1.",null,"Each Reliability Coordinator shall develop and implement a Reliability Coordinator Area restoration plan. The scope of the Reliability Coordinator’s restoration plan starts when Blackstart Resources are utilized to re-energize a shutdown area of the Bulk Electric System (BES), or separation has occurred between neighboring Reliability Coordinators, or an energized island has been formed on the BES within the Reliability Coordinator Area. The scope of the Reliability Coordinator’s restoration plan ends when all of its Transmission Operators are interconnected and its Reliability Coordinator Area is connected to all of its neighboring Reliability Coordinator Areas. The restoration plan shall include: [Violation Risk Factor = High] [Time Horizon = Operations Planning, Real-time Operations]","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26403,"EOP-006-3","R1.1.",null,"A description of the high-level strategy to be employed during restoration events for restoring the Interconnection, including minimum criteria for meeting the objectives of the Reliability Coordinator’s restoration plan.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[26404,"EOP-006-3","R1.2.",null,"Criteria and conditions for re-establishing interconnections with other Transmission Operators within its Reliability Coordinator Area, with Transmission Operators in other Reliability Coordinator Areas, and with other Reliability Coordinators.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[26405,"EOP-006-3","R1.3.",null,"Reporting requirements for the entities within the Reliability Coordinator Area during a restoration event.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[26406,"EOP-006-3","R1.4.",null,"Criteria for sharing information regarding restoration with neighboring Reliability Coordinators and with Transmission Operators and Balancing Authorities within its Reliability Coordinator Area.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[26407,"EOP-006-3","R1.5.",null,"Identification of the Reliability Coordinator as the primary contact for disseminating information regarding restoration to neighboring Reliability Coordinators, and to Transmission Operators, and Balancing Authorities within its Reliability Coordinator Area.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[26408,"EOP-006-3","R1.6.",null,"Criteria for transferring operations and authority back to the Balancing Authority.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[26409,"EOP-006-3","R2.",null,"The Reliability Coordinator shall distribute its most recent Reliability Coordinator Area restoration plan to each of its Transmission Operators and neighboring Reliability Coordinators within 30 calendar days of creation or revision. [Violation Risk Factor = Lower] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[26410,"EOP-006-3","R3.",null,"Each Reliability Coordinator shall review its restoration plan within 13 calendar months of the last review. [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26411,"EOP-006-3","R4.",null,"Each Reliability Coordinator shall review its neighboring Reliability Coordinator’s restoration plans and provide written notification of any conflicts discovered during that review within 60 calendar days of receipt. [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26412,"EOP-006-3","R4.1.",null,"If a Reliability Coordinator finds conflicts between its restoration plans and any of its neighbors, the conflicts shall be resolved within 30 calendar days of receipt of written notification.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[26413,"EOP-006-3","R5.",null,"Each Reliability Coordinator shall review the restoration plans required by EOP-005 of the Transmission Operators within its Reliability Coordinator Area. [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26414,"EOP-006-3","R5.1.",null,"The Reliability Coordinator shall determine whether the Transmission Operator’s restoration plan is coordinated and compatible with the Reliability Coordinator’s restoration plan and other Transmission Operators’ restoration plans within its Reliability Coordinator Area. The Reliability Coordinator shall provide notification to the Transmission Operator of approval or disapproval, with stated reasons, of the Transmission Operator’s submitted restoration plan within 30 calendar days following the receipt of the restoration plan from the Transmission Operator.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[26415,"EOP-006-3","R6.",null,"Each Reliability Coordinator shall have a copy of its latest restoration plan and copies of the latest approved restoration plan of each Transmission Operator in its Reliability Coordinator Area within its primary and backup control rooms so that it is available to all of its System Operators prior to the effective date. [Violation Risk Factor = Lower] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[26416,"EOP-006-3","R7.",null,"Each Reliability Coordinator shall include within its operations training program, annual System restoration training for its System Operators. This training program shall address the following: [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26417,"EOP-006-3","R7.1.",null,"The coordination role of the Reliability Coordinator; and","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[26418,"EOP-006-3","R7.2.",null,"Re-establishing the Interconnection.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[26419,"EOP-006-3","R8.",null,"Each Reliability Coordinator shall conduct two System restoration drills, exercises, or simulations per calendar year, which shall include the Transmission Operators and Generator Operators as dictated by the particular scope of the drill, exercise, or simulation that is being conducted. [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26420,"EOP-006-3","R8.1.",null,"Each Reliability Coordinator shall request each Transmission Operator identified in its restoration plan and each Generator Operator identified in the Transmission Operators’ restoration plans to participate in a drill, exercise, or simulation at least once every two calendar years.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[26422,"EOP-008-1","R1.","YES","Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall have a current Operating Plan describing the manner in which it continues to meet its functional obligations with regard to the reliable operations of the BES in the event that its primary control center functionality is lost. This Operating Plan for backup functionality shall include the following, at a minimum:","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26421,"EOP-008-1","R1.","YES","Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall have a current Operating Plan describing the manner in which it continues to meet its functional obligations with regard to the reliable operations of the BES in the event that its primary control center functionality is lost. This Operating Plan for backup functionality shall include the following, at a minimum:","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26423,"EOP-008-1","R1.1.",null,"The location and method of implementation for providing backup functionality for the time it takes to restore the primary control center functionality.","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26424,"EOP-008-1","R1.2.",null,"A summary description of the elements required to support the backup functionality. These elements shall include, at a minimum:","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26425,"EOP-008-1","R1.2.1.",null,"Tools and applications to ensure that System Operators have situational awareness of the BES.","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26426,"EOP-008-1","R1.2.2.",null,"Data communications.","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26427,"EOP-008-1","R1.2.3.",null,"Voice communications.","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26428,"EOP-008-1","R1.2.4.",null,"Power source(s).","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26429,"EOP-008-1","R1.2.5.",null,"Physical and cyber security.","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26430,"EOP-008-1","R1.3.",null,"An Operating Process for keeping the backup functionality consistent with the primary control center.","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26431,"EOP-008-1","R1.4.",null,"Operating Procedures, including decision authority, for use in determining when to implement the Operating Plan for backup functionality.","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26432,"EOP-008-1","R1.5.",null,"A transition period between the loss of primary control center functionality and the time to fully implement the backup functionality that is less than or equal to two hours.","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26433,"EOP-008-1","R1.6.",null,"An Operating Process describing the actions to be taken during the transition period between the loss of primary control center functionality and the time to fully implement backup functionality elements identified in Requirement R1, Part 1.2. The Operating Process shall include at a minimum:","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26434,"EOP-008-1","R1.6.1.",null,"A list of all entities to notify when there is a change in operating locations.","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26435,"EOP-008-1","R1.6.2.",null,"Actions to manage the risk to the BES during the transition from primary to backup functionality as well as during outages of the primary or backup functionality.","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26436,"EOP-008-1","R1.6.3.",null,"Identification of the roles for personnel involved during the initiation and implementation of the Operating Plan for backup functionality.","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26437,"EOP-008-1","R2.",null,"Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall have a copy of its current Operating Plan for backup functionality available at its primary control center and at the location providing backup functionality.","2013-10-01","2019-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26438,"EOP-008-1","R3.",null,"Each Reliability Coordinator shall have a backup control center facility (provided through its own dedicated backup facility or at another entity’s control center staffed with certified Reliability Coordinator operators when control has been transferred to the backup facility) that provides the functionality required for maintaining compliance with all Reliability Standards that depend on primary control center functionality. To avoid requiring a tertiary facility, a backup facility is not required during:\n\n• Planned outages of the primary or backup facilities of two weeks or less\n• Unplanned outages of the primary or backup facilities","2013-10-01","2019-03-31","Retired","Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[26439,"EOP-008-1","R4.",null,"Each Balancing Authority and Transmission Operator shall have backup functionality (provided either through a facility or contracted services staffed by applicable certified operators when control has been transferred to the backup functionality location) that includes monitoring, control, logging, and alarming sufficient for maintaining compliance with all Reliability Standards that depend on a Balancing Authority and Transmission Operator’s primary control center functionality respectively. To avoid requiring tertiary functionality, backup functionality is not required during:\n\n• Planned outages of the primary or backup functionality of two weeks or less\n• Unplanned outages of the primary or backup functionality","2013-10-01","2019-03-31","Retired","Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, BA","No",true,null,true]
[26440,"EOP-008-1","R5.",null,"Each Reliability Coordinator, Balancing Authority, and Transmission Operator, shall annually review and approve its Operating Plan for backup functionality.","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26441,"EOP-008-1","R5.1.",null,"An update and approval of the Operating Plan for backup functionality shall take place within sixty calendar days of any changes to any part of the Operating Plan described in Requirement R1.","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26442,"EOP-008-1","R6.",null,"Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall have primary and backup functionality that do not depend on each other for the control center functionality required to maintain compliance with Reliability Standards.","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26443,"EOP-008-1","R7.",null,"Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall conduct and document results of an annual test of its Operating Plan that demonstrates:","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26444,"EOP-008-1","R7.1.",null,"The transition time between the simulated loss of primary control center functionality and the time to fully implement the backup functionality.","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26445,"EOP-008-1","R7.2.",null,"The backup functionality for a minimum of two continuous hours.","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26446,"EOP-008-1","R8.",null,"Each Reliability Coordinator, Balancing Authority, and Transmission Operator that has experienced a loss of its primary or backup functionality and that anticipates that the loss of primary or backup functionality will last for more than six calendar months shall provide a plan to its Regional Entity within six calendar months of the date when the functionality is lost, showing how it will re-establish primary or backup functionality.","2013-10-01","2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26448,"EOP-008-2","R1.","YES","Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall have a current Operating Plan describing the manner in which it continues to meet its functional obligations with regard to the reliable operations of the BES in the event that its primary control center functionality is lost. This Operating Plan for backup functionality shall include: [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26447,"EOP-008-2","R1.","YES","Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall have a current Operating Plan describing the manner in which it continues to meet its functional obligations with regard to the reliable operations of the BES in the event that its primary control center functionality is lost. This Operating Plan for backup functionality shall include: [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26449,"EOP-008-2","R1.1.",null,"The location and method of implementation for providing backup functionality.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26450,"EOP-008-2","R1.2.",null,"A summary description of the elements required to support the backup functionality. These elements shall include:","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26451,"EOP-008-2","R1.2.1.",null,"Tools and applications to ensure that System Operators have situational awareness of the BES.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26452,"EOP-008-2","R1.2.2.",null,"Data exchange capabilities.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26453,"EOP-008-2","R1.2.3.",null,"Interpersonal Communications.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26454,"EOP-008-2","R1.2.4.",null,"Power source(s).","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26455,"EOP-008-2","R1.2.5.",null,"Physical and cyber security.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26456,"EOP-008-2","R1.3.",null,"An Operating Process for keeping the backup functionality consistent with the primary control center.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26457,"EOP-008-2","R1.4.",null,"Operating Procedures, including decision authority, for use in determining when to implement the Operating Plan for backup functionality.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26458,"EOP-008-2","R1.5.",null,"A transition period between the loss of primary control center functionality and the time to fully implement the backup functionality that is less than or equal to two hours.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26459,"EOP-008-2","R1.6.",null,"An Operating Process describing the actions to be taken during the transition period between the loss of primary control center functionality and the time to fully implement backup functionality elements identified in Requirement R1, Part 1.2. The Operating Process shall include:","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26460,"EOP-008-2","R1.6.1.",null,"A list of all entities to notify when there is a change in operating locations.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26461,"EOP-008-2","R1.6.2.",null,"Actions to manage the risk to the BES during the transition from primary to backup functionality, as well as during outages of the primary or backup functionality.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26462,"EOP-008-2","R1.6.3.",null,"Identification of the roles for personnel involved during the initiation and implementation of the Operating Plan for backup functionality.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26463,"EOP-008-2","R2.",null,"Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall have a copy of its current Operating Plan for backup functionality available at its primary control center and at the location providing backup functionality. [Violation Risk Factor = Lower] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26464,"EOP-008-2","R3.",null,"Each Reliability Coordinator shall have a backup control center facility (provided through its own dedicated backup facility or at another entity’s control center staffed with certified Reliability Coordinator operators when control has been transferred to the backup facility) that provides the functionality required for maintaining compliance with all Reliability Standards are applicable to the primary control center functionality. To avoid requiring a tertiary facility, a backup facility is not required during: [Violation Risk Factor = High] [Time Horizon = Operations Planning]\n• Planned outages of the primary or backup facilities of two weeks or less\n• Unplanned outages of the primary or backup facilities","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26465,"EOP-008-2","R4.",null,"Each Balancing Authority and Transmission Operator shall have backup functionality (provided either through a facility or contracted services staffed by applicable certified operators when control has been transferred to the backup functionality location) that includes monitoring, control, logging, and alarming sufficient for maintaining compliance with all Reliability Standards that are applicable to a Balancing Authority’s and Transmission Operator’s primary control center functionality. To avoid requiring tertiary functionality, backup functionality is not required during: [Violation Risk Factor = High] [Time Horizon = Operations Planning]\n• Planned outages of the primary or backup functionality of two weeks or less\n• Unplanned outages of the primary or backup functionality","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[26466,"EOP-008-2","R5.",null,"Each Reliability Coordinator, Balancing Authority, and Transmission Operator, shall annually review and approve its Operating Plan for backup functionality. [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26467,"EOP-008-2","R5.1.",null,"An update and approval of the Operating Plan for backup functionality shall take place within sixty calendar days of any changes to any part of the Operating Plan described in Requirement R1.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26468,"EOP-008-2","R6.",null,"Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall have primary and backup functionality that do not depend on each other for the control center functionality required to maintain compliance with Reliability Standards. [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26469,"EOP-008-2","R7.",null,"Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall conduct and document results of an annual test of its Operating Plan that demonstrates: [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26470,"EOP-008-2","R7.1.",null,"The transition time between the simulated loss of primary control center functionality and the time to fully implement the backup functionality.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26471,"EOP-008-2","R7.2.",null,"The backup functionality for a minimum of two continuous hours.","2019-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26472,"EOP-008-2","R8.",null,"Each Reliability Coordinator, Balancing Authority, and Transmission Operator that has experienced a loss of its primary or backup functionality and that anticipates that the loss of primary or backup functionality will last for more than six calendar months shall provide a plan to its Regional Entity within six calendar months of the date when the functionality is lost, showing how it will re-establish primary or backup functionality. [Violation Risk Factor = Medium] [Time Horizon = Operations Planning]","2019-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[26473,"EOP-010-1","R1.",null,"Each Reliability Coordinator shall develop, maintain, and implement a GMD Operating Plan that coordinates GMD Operating Procedures or Operating Processes within its Reliability Coordinator Area. At a minimum, the GMD Operating Plan shall include:\n[Violation Risk Factor: Medium] [Time Horizon: Long-term Planning, Operations Planning, Same-day Operations, Real-time Operations]","2015-04-01",null,"Effective",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","LIKELY","MEDIUM (Moderate Controls)","RC","No",false,null,false]
[26474,"EOP-010-1","R1.1.",null,"A description of activities designed to mitigate the effects of GMD events on the reliable operation of the interconnected transmission system within the Reliability Coordinator Area.","2015-04-01",null,"Effective",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","LIKELY","MEDIUM (Moderate Controls)","RC","No",false,null,false]
[26475,"EOP-010-1","R1.2.",null,"A process for the Reliability Coordinator to review the GMD Operating Procedures or Operating Processes of Transmission Operators within its Reliability Coordinator Area.","2015-04-01",null,"Effective",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","LIKELY","MEDIUM (Moderate Controls)","RC","No",false,null,false]
[26476,"EOP-010-1","R2.",null,"Each Reliability Coordinator shall disseminate forecasted and current space weather information to functional entities identified as recipients in the Reliability Coordinator's GMD Operating Plan. [Violation Risk Factor: Medium] [Time Horizon: Same-day Operations, Real-time Operations]","2017-04-01",null,"Effective",null,"MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[26477,"EOP-010-1","R3.",null,"Each Transmission Operator shall develop, maintain, and implement a GMD Operating Procedure or Operating Process to mitigate the effects of GMD events on the reliable operation of its respective system. At a minimum, the Operating Procedure or Operating Process shall include: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning, Operations Planning, Same-day  operations, Real-Time Operations]","2015-04-01",null,"Effective",null,"MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,true]
[26478,"EOP-010-1","R3.1.",null,"Steps or tasks to receive space weather information.","2015-04-01",null,"Effective",null,"MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,true]
[26479,"EOP-010-1","R3.2.",null,"System Operator actions to be initiated based on predetermined conditions.","2015-04-01",null,"Effective",null,"MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,true]
[26480,"EOP-010-1","R3.3.",null,"The conditions for terminating the Operating Procedure or Operating Process.","2015-04-01",null,"Effective",null,"MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,true]
[26482,"EOP-011-1","R1.","YES","Each Transmission Operator shall develop, maintain, and implement one or more Reliability Coordinator-reviewed Operating Plan(s) to mitigate operating Emergencies in its Transmission Operator Area. The Operating Plan(s) shall include the following, as applicable: [Violation Risk Factor: High] [Time Horizon: Real-Time Operations, Operations Planning, Long-term Planning]","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true,"See note in R1.2.5"]
[26481,"EOP-011-1","R1.","YES","Each Transmission Operator shall develop, maintain, and implement one or more Reliability Coordinator-reviewed Operating Plan(s) to mitigate operating Emergencies in its Transmission Operator Area. The Operating Plan(s) shall include the following, as applicable: [Violation Risk Factor: High] [Time Horizon: Real-Time Operations, Operations Planning, Long-term Planning]","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true,"See note in R1.2.5"]
[26483,"EOP-011-1","R1.","YES","Each Transmission Operator shall develop, maintain, and implement one or more Reliability Coordinator-reviewed Operating Plan(s) to mitigate operating Emergencies in its Transmission Operator Area. The Operating Plan(s) shall include the following, as applicable: [Violation Risk Factor: High] [Time Horizon: Real-Time Operations, Operations Planning, Long-term Planning]","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true,"See note in R1.2.5"]
[26484,"EOP-011-1","R1.1.",null,"Roles and responsibilities for activating the Operating Plan(s);","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26485,"EOP-011-1","R1.2.","YES","Processes to prepare for and mitigate Emergencies including:","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true,"See note in R1.2.5"]
[26487,"EOP-011-1","R1.2.","YES","Processes to prepare for and mitigate Emergencies including:","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true,"See note in R1.2.5"]
[26486,"EOP-011-1","R1.2.","YES","Processes to prepare for and mitigate Emergencies including:","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true,"See note in R1.2.5"]
[26489,"EOP-011-1","R1.2.1.","YES","Notification to its Reliability Coordinator, to include current and projected conditions, when experiencing an operating Emergency;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26488,"EOP-011-1","R1.2.1.","YES","Notification to its Reliability Coordinator, to include current and projected conditions, when experiencing an operating Emergency;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26490,"EOP-011-1","R1.2.2.","YES","Cancellation or recall of Transmission and generation outages;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26491,"EOP-011-1","R1.2.2.","YES","Cancellation or recall of Transmission and generation outages;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26492,"EOP-011-1","R1.2.3.",null,"Transmission system reconfiguration;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26493,"EOP-011-1","R1.2.4.",null,"Redispatch of generation request;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26494,"EOP-011-1","R1.2.5.",null,"Provisions for operator-controlled manual Load shedding that minimizes the overlap with automatic Load shedding and are capable of being implemented in a timeframe adequate for mitigating the Emergency; and","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true,"Hydro One shall have provisions for operator-controlled manual load shedding that minimizes overlap with automatic load shedding and are capable of being implemented in a timeframe adequate for mitigating the emergency."]
[26496,"EOP-011-1","R1.2.6.","YES","Reliability impacts of extreme weather conditions.","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26495,"EOP-011-1","R1.2.6.","YES","Reliability impacts of extreme weather conditions.","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[26498,"EOP-011-1","R2.","YES","Each Balancing Authority shall develop, maintain, and implement one or more Reliability Coordinator-reviewed Operating Plan(s) to mitigate Capacity Emergencies and Energy Emergencies within its Balancing Authority Area. The Operating Plan(s) shall include the following, as applicable: [Violation Risk Factor: High] [Time Horizon: Real-Time Operations, Operations Planning, Long-term Planning]","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26497,"EOP-011-1","R2.","YES","Each Balancing Authority shall develop, maintain, and implement one or more Reliability Coordinator-reviewed Operating Plan(s) to mitigate Capacity Emergencies and Energy Emergencies within its Balancing Authority Area. The Operating Plan(s) shall include the following, as applicable: [Violation Risk Factor: High] [Time Horizon: Real-Time Operations, Operations Planning, Long-term Planning]","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26499,"EOP-011-1","R2.1.","YES","Roles and responsibilities for activating the Operating Plan(s);","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26500,"EOP-011-1","R2.1.","YES","Roles and responsibilities for activating the Operating Plan(s);","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26501,"EOP-011-1","R2.2.","YES","Processes to prepare for and mitigate Emergencies including:","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26502,"EOP-011-1","R2.2.","YES","Processes to prepare for and mitigate Emergencies including:","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26503,"EOP-011-1","R2.2.1.","YES","Notification to its Reliability Coordinator, to include current and projected conditions when experiencing a Capacity Emergency or Energy Emergency;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26504,"EOP-011-1","R2.2.1.","YES","Notification to its Reliability Coordinator, to include current and projected conditions when experiencing a Capacity Emergency or Energy Emergency;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26505,"EOP-011-1","R2.2.2.","YES","Requesting an Energy Emergency Alert, per Attachment 1;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26506,"EOP-011-1","R2.2.2.","YES","Requesting an Energy Emergency Alert, per Attachment 1;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26508,"EOP-011-1","R2.2.3.","YES","Managing generating resources in its Balancing Authority Area to address:","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26507,"EOP-011-1","R2.2.3.","YES","Managing generating resources in its Balancing Authority Area to address:","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26509,"EOP-011-1","R2.2.3.1.","YES","capability and availability;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26510,"EOP-011-1","R2.2.3.1.","YES","capability and availability;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26511,"EOP-011-1","R2.2.3.2.","YES","fuel supply and inventory concerns;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26512,"EOP-011-1","R2.2.3.2.","YES","fuel supply and inventory concerns;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26513,"EOP-011-1","R2.2.3.3.","YES","fuel switching capabilities; and","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26514,"EOP-011-1","R2.2.3.3.","YES","fuel switching capabilities; and","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26516,"EOP-011-1","R2.2.3.4.","YES","environmental constraints.","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26515,"EOP-011-1","R2.2.3.4.","YES","environmental constraints.","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26518,"EOP-011-1","R2.2.4.","YES","Public appeals for voluntary Load reductions;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26517,"EOP-011-1","R2.2.4.","YES","Public appeals for voluntary Load reductions;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26520,"EOP-011-1","R2.2.5.","YES","Requests to government agencies to implement their programs to achieve necessary energy reductions;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26519,"EOP-011-1","R2.2.5.","YES","Requests to government agencies to implement their programs to achieve necessary energy reductions;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26522,"EOP-011-1","R2.2.6.","YES","Reduction of internal utility energy use;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26521,"EOP-011-1","R2.2.6.","YES","Reduction of internal utility energy use;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26523,"EOP-011-1","R2.2.7.","YES","Use of Interruptible Load, curtailable Load and demand response;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26524,"EOP-011-1","R2.2.7.","YES","Use of Interruptible Load, curtailable Load and demand response;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26525,"EOP-011-1","R2.2.8.","YES","Provisions for operator-controlled manual Load shedding that minimizes the overlap with automatic Load shedding and are capable of being implemented in a timeframe adequate for mitigating the Emergency; and","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26526,"EOP-011-1","R2.2.8.","YES","Provisions for operator-controlled manual Load shedding that minimizes the overlap with automatic Load shedding and are capable of being implemented in a timeframe adequate for mitigating the Emergency; and","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26527,"EOP-011-1","R2.2.9.","YES","Reliability impacts of extreme weather conditions.","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26528,"EOP-011-1","R2.2.9.","YES","Reliability impacts of extreme weather conditions.","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[26529,"EOP-011-1","R3.",null,"The Reliability Coordinator shall review the Operating Plan(s) to mitigate operating Emergencies submitted by a Transmission Operator or a Balancing Authority regarding any reliability risks that are identified between Operating Plans. [ViolationRisk Factor: High] [Time Horizon: Operations Planning]","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26530,"EOP-011-1","R3.1.",null,"Within 30 calendar days of receipt, the Reliability Coordinator shall:","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26531,"EOP-011-1","R3.1.1.",null,"Review each submitted Operating Plan(s) on the basis of compatibility and inter-dependency with other Balancing Authorities’ and Transmission Operators’ Operating Plans;","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26532,"EOP-011-1","R3.1.2.",null,"Review each submitted Operating Plan(s) for coordination to avoid risk to Wide Area reliability; and","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26533,"EOP-011-1","R3.1.3.",null,"Notify each Balancing Authority and Transmission Operator of the results of its review, specifying any time frame for resubmittal of its Operating Plan(s) if revisions are identified.","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26534,"EOP-011-1","R4.",null,"Each Transmission Operator and Balancing Authority shall address any reliability risks identified by its Reliability Coordinator pursuant to Requirement R3 and resubmit its Operating Plan(s) to its Reliability Coordinator within a time period specified by its Reliability Coordinator. [Violation Risk Factor: High] [Time Horizon: Operation Planning]","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, BA","No",true,null,true,"See note in R1.2.5"]
[26535,"EOP-011-1","R5.",null,"Each Reliability Coordinator that receives an Emergency notification from a Transmission Operator or Balancing Authority within its Reliability Coordinator Area shall notify, within 30 minutes from the time of receiving notification, other Balancing Authorities and Transmission Operators in its Reliability Coordinator Area, and neighboring Reliability Coordinators. [Violation Risk Factor: High] [Time Horizon: Real-Time Operations]","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26536,"EOP-011-1","R6.",null,"Each Reliability Coordinator that has a Balancing Authority experiencing a potential or actual Energy Emergency within its Reliability Coordinator Area shall declare an Energy Emergency Alert, as detailed in Attachment 1. [Violation Risk Factor: High] [Time Horizon: Real-Time Operations]","2017-04-01","2023-09-30","Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30263,"EOP-011-2","R1.","YES","Each Transmission Operator shall develop, maintain, and implement one or more Reliability Coordinator-reviewed Operating Plan(s) to mitigate operating Emergencies in its Transmission Operator Area. The Operating Plan(s) shall include the following, as applicable: [Violation Risk Factor: High] [Time Horizon: Real-Time Operations, Operations Planning, Long-term Planning]","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,true,"See note in R1.2.5"]
[30262,"EOP-011-2","R1.","YES","Each Transmission Operator shall develop, maintain, and implement one or more Reliability Coordinator-reviewed Operating Plan(s) to mitigate operating Emergencies in its Transmission Operator Area. The Operating Plan(s) shall include the following, as applicable: [Violation Risk Factor: High] [Time Horizon: Real-Time Operations, Operations Planning, Long-term Planning]","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,true,"See note in R1.2.5"]
[30261,"EOP-011-2","R1.","YES","Each Transmission Operator shall develop, maintain, and implement one or more Reliability Coordinator-reviewed Operating Plan(s) to mitigate operating Emergencies in its Transmission Operator Area. The Operating Plan(s) shall include the following, as applicable: [Violation Risk Factor: High] [Time Horizon: Real-Time Operations, Operations Planning, Long-term Planning]","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,true,"See note in R1.2.5"]
[30264,"EOP-011-2","R1.1.",null,"Roles and responsibilities for activating the Operating Plan(s);","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,false]
[30265,"EOP-011-2","R1.2.","YES","Processes to prepare for and mitigate Emergencies including:","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,true,"See note in R1.2.5"]
[30266,"EOP-011-2","R1.2.","YES","Processes to prepare for and mitigate Emergencies including:","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,true,"See note in R1.2.5"]
[30267,"EOP-011-2","R1.2.","YES","Processes to prepare for and mitigate Emergencies including:","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,true,"See note in R1.2.5"]
[30269,"EOP-011-2","R1.2.1.","YES","Notification to its Reliability Coordinator, to include current and projected conditions, when experiencing an operating Emergency;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,false]
[30268,"EOP-011-2","R1.2.1.","YES","Notification to its Reliability Coordinator, to include current and projected conditions, when experiencing an operating Emergency;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,false]
[30271,"EOP-011-2","R1.2.2.","YES","Cancellation or recall of Transmission and generation outages;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,false]
[30270,"EOP-011-2","R1.2.2.","YES","Cancellation or recall of Transmission and generation outages;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,false]
[30272,"EOP-011-2","R1.2.3.",null,"Transmission system reconfiguration;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,false]
[30273,"EOP-011-2","R1.2.4.",null,"Redispatch of generation request;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,false]
[30274,"EOP-011-2","R1.2.5.",null,"Provisions for operator-controlled manual Load shedding that minimizes the overlap with automatic Load shedding and are capable of being implemented in a timeframe adequate for mitigating the Emergency; and","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,true,"Hydro One shall have provisions for operator-controlled manual load shedding that minimizes overlap with automatic load shedding and are capable of being implemented in a timeframe adequate for mitigating the emergency."]
[30276,"EOP-011-2","R1.2.6.","YES","Provisions to determine reliability impacts of","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,false]
[30275,"EOP-011-2","R1.2.6.","YES","Provisions to determine reliability impacts of:","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,false]
[30317,"EOP-011-2","R1.2.6.1.","YES","cold weather conditions; and","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,false]
[30318,"EOP-011-2","R1.2.6.1.","YES","cold weather conditions; and","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,false]
[30319,"EOP-011-2","R1.2.6.2.","YES","extreme weather conditions","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,false]
[30320,"EOP-011-2","R1.2.6.2.","YES","extreme weather conditions","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,false]
[30277,"EOP-011-2","R2.","YES","Each Balancing Authority shall develop, maintain, and implement one or more Reliability Coordinator-reviewed Operating Plan(s) to mitigate Capacity Emergencies and Energy Emergencies within its Balancing Authority Area. The Operating Plan(s) shall include the following, as applicable: [Violation Risk Factor: High] [Time Horizon: Real-Time Operations, Operations Planning, Long-term Planning]","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30278,"EOP-011-2","R2.","YES","Each Balancing Authority shall develop, maintain, and implement one or more Reliability Coordinator-reviewed Operating Plan(s) to mitigate Capacity Emergencies and Energy Emergencies within its Balancing Authority Area. The Operating Plan(s) shall include the following, as applicable: [Violation Risk Factor: High] [Time Horizon: Real-Time Operations, Operations Planning, Long-term Planning]","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30279,"EOP-011-2","R2.1.","YES","Roles and responsibilities for activating the Operating Plan(s);","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30280,"EOP-011-2","R2.1.","YES","Roles and responsibilities for activating the Operating Plan(s);","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30281,"EOP-011-2","R2.2.","YES","Processes to prepare for and mitigate Emergencies including:","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30282,"EOP-011-2","R2.2.","YES","Processes to prepare for and mitigate Emergencies including:","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30284,"EOP-011-2","R2.2.1.","YES","Notification to its Reliability Coordinator, to include current and projected conditions when experiencing a Capacity Emergency or Energy Emergency;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30283,"EOP-011-2","R2.2.1.","YES","Notification to its Reliability Coordinator, to include current and projected conditions when experiencing a Capacity Emergency or Energy Emergency;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30285,"EOP-011-2","R2.2.2.","YES","Requesting an Energy Emergency Alert, per Attachment 1;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30286,"EOP-011-2","R2.2.2.","YES","Requesting an Energy Emergency Alert, per Attachment 1;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30288,"EOP-011-2","R2.2.3.","YES","Managing generating resources in its Balancing Authority Area to address:","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30287,"EOP-011-2","R2.2.3.","YES","Managing generating resources in its Balancing Authority Area to address:","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30290,"EOP-011-2","R2.2.3.1.","YES","capability and availability;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30289,"EOP-011-2","R2.2.3.1.","YES","capability and availability;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30291,"EOP-011-2","R2.2.3.2.","YES","fuel supply and inventory concerns;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30292,"EOP-011-2","R2.2.3.2.","YES","fuel supply and inventory concerns;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30294,"EOP-011-2","R2.2.3.3.","YES","fuel switching capabilities; and","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30293,"EOP-011-2","R2.2.3.3.","YES","fuel switching capabilities; and","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30296,"EOP-011-2","R2.2.3.4.","YES","environmental constraints.","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30295,"EOP-011-2","R2.2.3.4.","YES","environmental constraints.","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30297,"EOP-011-2","R2.2.4.","YES","Public appeals for voluntary Load reductions;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30298,"EOP-011-2","R2.2.4.","YES","Public appeals for voluntary Load reductions;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30299,"EOP-011-2","R2.2.5.","YES","Requests to government agencies to implement their programs to achieve necessary energy reductions;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30300,"EOP-011-2","R2.2.5.","YES","Requests to government agencies to implement their programs to achieve necessary energy reductions;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30301,"EOP-011-2","R2.2.6.","YES","Reduction of internal utility energy use;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30302,"EOP-011-2","R2.2.6.","YES","Reduction of internal utility energy use;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30304,"EOP-011-2","R2.2.7.","YES","Use of Interruptible Load, curtailable Load and demand response;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30303,"EOP-011-2","R2.2.7.","YES","Use of Interruptible Load, curtailable Load and demand response;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30305,"EOP-011-2","R2.2.8.","YES","Provisions for operator-controlled manual Load shedding that minimizes the overlap with automatic Load shedding and are capable of being implemented in a timeframe adequate for mitigating the Emergency; and","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30306,"EOP-011-2","R2.2.8.","YES","Provisions for operator-controlled manual Load shedding that minimizes the overlap with automatic Load shedding and are capable of being implemented in a timeframe adequate for mitigating the Emergency; and","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30307,"EOP-011-2","R2.2.9.","YES","Provisions to determine reliability impacts of","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30308,"EOP-011-2","R2.2.9.","YES","Provisions to determine reliability impacts of","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30322,"EOP-011-2","R2.2.9.1.","YES","cold weather conditions; and","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30321,"EOP-011-2","R2.2.9.1.","YES","cold weather conditions; and","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30324,"EOP-011-2","R2.2.9.2.","YES","extreme weather conditions","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30323,"EOP-011-2","R2.2.9.2.","YES","extreme weather conditions","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30309,"EOP-011-2","R3.",null,"The Reliability Coordinator shall review the Operating Plan(s) to mitigate operating Emergencies submitted by a Transmission Operator or a Balancing Authority regarding any reliability risks that are identified between Operating Plans. [Violation\nRisk Factor: High] [Time Horizon: Operations Planning]","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30310,"EOP-011-2","R3.1.",null,"Within 30 calendar days of receipt, the Reliability Coordinator shall:","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30311,"EOP-011-2","R3.1.1.",null,"Review each submitted Operating Plan(s) on the basis of compatibility and inter-dependency with other Balancing Authorities’ and Transmission Operators’ Operating Plans;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30312,"EOP-011-2","R3.1.2.",null,"Review each submitted Operating Plan(s) for coordination to avoid risk to Wide Area reliability; and","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30313,"EOP-011-2","R3.1.3.",null,"Notify each Balancing Authority and Transmission Operator of the results of its review, specifying any time frame for resubmittal of its Operating Plan(s) if revisions are identified.","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30314,"EOP-011-2","R4.",null,"Each Transmission Operator and Balancing Authority shall address any reliability risks identified by its Reliability Coordinator pursuant to Requirement R3 and resubmit its Operating Plan(s) to its Reliability Coordinator within a time period specified by its Reliability Coordinator. [Violation Risk Factor: High] [Time Horizon: Operation Planning]","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,true,"See note in R1.2.5"]
[30315,"EOP-011-2","R5.",null,"Each Reliability Coordinator that receives an Emergency notification from a Transmission Operator or Balancing Authority within its Reliability Coordinator Area shall notify, within 30 minutes from the time of receiving notification, other Balancing Authorities and Transmission Operators in its Reliability Coordinator Area, and neighboring Reliability Coordinators. [Violation Risk Factor: High] [Time Horizon: Real-Time Operations]","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30316,"EOP-011-2","R6.",null,"Each Reliability Coordinator that has a Balancing Authority experiencing a potential or actual Energy Emergency within its Reliability Coordinator Area shall declare an Energy Emergency Alert, as detailed in Attachment 1. [Violation Risk Factor: High] [Time Horizon: Real-Time Operations]","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30325,"EOP-011-2","R7.",null,"Each Generator Owner shall implement and maintain one or more cold weather \r\npreparedness plan(s) for its generating units. The cold weather preparedness plan(s)\r\nshall include the following, at a minimum:","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[30326,"EOP-011-2","R7.1.",null,"Generating unit(s) freeze protection measures based on geographical location \r\nand plant configuration;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30327,"EOP-011-2","R7.2.",null,"Annual inspection and maintenance of generating unit(s) freeze protection \r\nmeasures;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30328,"EOP-011-2","R7.3.",null,"Generating unit(s) cold weather data, to include:","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30329,"EOP-011-2","R7.3.1.",null,"Generating unit(s) operating limitations in cold weather to include:","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30330,"EOP-011-2","R7.3.1.1.",null,"capability and availability;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30331,"EOP-011-2","R7.3.1.2.",null,"fuel supply and inventory concerns;","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30332,"EOP-011-2","R7.3.1.3.",null,"fuel switching capabilities; and","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30333,"EOP-011-2","R7.3.1.4.",null,"environmental constraints.","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30334,"EOP-011-2","R7.3.2.",null,"Generating unit(s) minimum:","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30335,"EOP-011-2","R7.3.2.1.",null,"design temperature; or","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30336,"EOP-011-2","R7.3.2.2.",null,"historical operating temperature; or","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30337,"EOP-011-2","R7.3.2.3.",null,"current cold weather performance temperature determined by an \r\nengineering analysis.","2023-10-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30338,"EOP-011-2","R8.",null,"Each Generator Owner in conjunction with its Generator Operator shall identify the \r\nentity responsible for providing the generating unit-specific training, and that \r\nidentified entity shall provide the training to its maintenance or operations personnel \r\nresponsible for implementing cold weather preparedness plan(s) developed pursuant \r\nto Requirement R7. [Violation Risk Factor: Medium] [Time Horizon: Long-term \r\nPlanning, Operations Planning]","2023-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[26572,"FAC-001-3","R1.",null,"Each Transmission Owner shall document Facility interconnection requirements, update them as needed, and make them available upon request. Each Transmission Owner’s Facility interconnection requirements shall address interconnection requirements for:","2019-01-01",null,"Effective",null,"Lower",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26573,"FAC-001-3","R1.1.",null,"generation Facilities;","2019-01-01",null,"Effective",null,"Lower",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26574,"FAC-001-3","R1.2.",null,"transmission Facilities; and","2019-01-01",null,"Effective",null,"Lower",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26575,"FAC-001-3","R1.3.",null,"end-user Facilities.","2019-01-01",null,"Effective",null,"Lower",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26576,"FAC-001-3","R2.",null,"Each applicable Generator Owner shall document Facility interconnection requirements and make them available upon request within 45 calendar days of full execution of an Agreement to conduct a study on the reliability impact of interconnecting a third party Facility to the Generator Owner’s existing Facility that is used to interconnect to the Transmission system.","2019-01-01",null,"Effective",null,"Lower",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26577,"FAC-001-3","R3.",null,"Each Transmission Owner shall address the following items in its Facility interconnection requirements:","2019-01-01",null,"Effective",null,"Lower",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26578,"FAC-001-3","R3.1.",null,"Procedures for coordinated studies of new or materially modified existing interconnections and their impacts on affected system(s).","2019-01-01",null,"Effective",null,"Lower",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26579,"FAC-001-3","R3.2.",null,"Procedures for notifying those responsible for the reliability of affected system(s) of new or materially modified existing interconnections.","2019-01-01",null,"Effective",null,"Lower",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26580,"FAC-001-3","R3.3.",null,"Procedures for confirming with those responsible for the reliability of affected systems that new or materially modified Facilities are within a Balancing Authority Area’s metered boundaries.","2019-01-01",null,"Effective",null,"Lower",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26581,"FAC-001-3","R4.",null,"Each applicable Generator Owner shall address the following items in its Facility interconnection requirements:","2019-01-01",null,"Effective",null,"Lower",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26582,"FAC-001-3","R4.1.",null,"Procedures for coordinated studies of new interconnections and their impacts on affected system(s).","2019-01-01",null,"Effective",null,"Lower",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26583,"FAC-001-3","R4.2.",null,"Procedures for notifying those responsible for the reliability of affected system(s) of new interconnections.","2019-01-01",null,"Effective",null,"Lower",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26584,"FAC-001-3","R4.3.",null,"Procedures for confirming with those responsible for the reliability of affected systems that new or materially modified Facilities are within a Balancing Authority Area’s metered boundaries.","2019-01-01",null,"Effective",null,"Lower",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26591,"FAC-002-2","R1.",null,"Each Transmission Planner and each Planning Coordinator shall study the reliability impact of: (i) interconnecting new generation, transmission, or electricity end-user Facilities and (ii) materially modifying existing interconnections of generation, transmission, or electricity end-user Facilities. The following shall be studied: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2016-01-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC","No",false,null,false]
[26592,"FAC-002-2","R1.1.",null,"The reliability impact of the new interconnection, or materially modified existing interconnection, on affected system(s);","2016-01-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC","No",false,null,false]
[26593,"FAC-002-2","R1.2.",null,"Adherence to applicable NERC Reliability Standards; regional and Transmission Owner planning criteria; and Facility interconnection requirements;","2016-01-01","2021-03-31","Retired","Authorization/Approval; Documentations, Policies and Procedures; Quality Check/Verification; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC","No",false,null,false]
[26594,"FAC-002-2","R1.3.",null,"Steady-state, short-circuit, and dynamics studies, as necessary, to evaluate system performance under both normal and contingency conditions; and","2016-01-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC","No",false,null,false]
[26595,"FAC-002-2","R1.4.",null,"Study assumptions, system performance, alternatives considered, and coordinated recommendations. While these studies may be performed independently, the results shall be evaluated and coordinated by the entities involved.","2016-01-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC","No",false,null,false]
[26596,"FAC-002-2","R2.",null,"Each Generator Owner seeking to interconnect new generation Facilities, or to materially modify existing interconnections of generation Facilities, shall coordinate and cooperate on studies with its Transmission Planner or Planning Coordinator, including but not limited to the provision of data as described in R1, Parts 1.1-1.4. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2016-01-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26597,"FAC-002-2","R3.",null,"Each Transmission Owner, each Distribution Provider, and each Load-Serving Entity seeking to interconnect new transmission Facilities or electricity end-user Facilities, or to materially modify existing interconnections of transmission Facilities or electricity end-user Facilities, shall coordinate and cooperate on studies with its Transmission Planner or Planning Coordinator, including but not limited to the provision of data as described in R1, Parts 1.1-1.4. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2016-01-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, LSE, DP","Yes",false,null,false]
[26598,"FAC-002-2","R4.",null,"Each Transmission Owner shall coordinate and cooperate with its Transmission Planner or Planning Coordinator on studies regarding requested new or materially modified interconnections to its Facilities, including but not limited to the provision of data as described in R1, Parts 1.1-1.4. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2016-01-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26599,"FAC-002-2","R5.",null,"Each applicable Generator Owner shall coordinate and cooperate with its Transmission Planner or Planning Coordinator on studies regarding requested interconnections to its Facilities, including but not limited to the provision of data as described in R1, Parts 1.1-1.4. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2016-01-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29918,"FAC-002-3","R1.",null,"Each Transmission Planner and each Planning Coordinator shall study the reliability impact of: (i) interconnecting new generation, transmission, or electricity end-user Facilities and (ii) materially modifying existing interconnections of generation, transmission, or electricity end-user Facilities. The following shall be studied: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GO, DP, TP, TO, PC","Yes",false,null,false]
[29919,"FAC-002-3","R1.1.",null,"The reliability impact of the new interconnection, or materially modified existing interconnection, on affected system(s);","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GO, DP, TO, TP, PC","Yes",false,null,false]
[29920,"FAC-002-3","R1.2.",null,"Adherence to applicable NERC Reliability Standards; regional and Transmission Owner planning criteria; and Facility interconnection requirements;","2021-04-01",null,"Effective","Authorization/Approval; Documentations, Policies and Procedures; Communications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GO, DP, TO, TP, PC","Yes",false,null,false]
[29921,"FAC-002-3","R1.3.",null,"Steady-state, short-circuit, and dynamics studies, as necessary, to evaluate system performance under both normal and contingency conditions; and","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GO, DP, TO, TP, PC","Yes",false,null,false]
[29922,"FAC-002-3","R1.4.",null,"Study assumptions, system performance, alternatives considered, and coordinated recommendations. While these studies may be performed independently, the results shall be evaluated and coordinated by the entities involved.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GO, DP, TO, TP, PC","Yes",false,null,false]
[29923,"FAC-002-3","R2.",null,"Each Generator Owner seeking to interconnect new generation Facilities, or to materially modify existing interconnections of generation Facilities, shall coordinate and cooperate on studies with its Transmission Planner or Planning Coordinator, including but not limited to the provision of data as described in R1, Parts 1.1-1.4. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective",null,"MEDIUM","N/A","N/A","N/A","N/A","GO, DP, TO, TP, PC","Yes",false,null,false]
[29924,"FAC-002-3","R3.",null,"Each Transmission Owner and each Distribution Provider seeking to interconnect new transmission Facilities or electricity end-user Facilities, or to materially modify existing interconnections of transmission Facilities or electricity end-user Facilities, shall coordinate and cooperate on studies with its Transmission Planner or Planning Coordinator, including but not limited to the provision of data as described in R1, Parts 1.1-1.4. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective",null,"MEDIUM","N/A","N/A","N/A","N/A","GO, DP, TO, TP, PC","Yes",false,null,false]
[29925,"FAC-002-3","R4.",null,"Each Transmission Owner shall coordinate and cooperate with its Transmission Planner or Planning Coordinator on studies regarding requested new or materially modified interconnections to its Facilities, including but not limited to the provision of data as described in R1, Parts 1.1-1.4. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective",null,"MEDIUM","N/A","N/A","N/A","N/A","GO, DP, TO, TP, PC","Yes",false,null,false]
[29926,"FAC-002-3","R5.",null,"Each applicable Generator Owner shall coordinate and cooperate with its Transmission Planner or Planning Coordinator on studies regarding requested interconnections to its Facilities, including but not limited to the provision of data as described in R1, Parts 1.1-1.4. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective",null,"MEDIUM","N/A","N/A","N/A","N/A","GO, DP, TO, TP, PC","Yes",false,null,false]
[26600,"FAC-003-2","R1.",null,"Each Transmission Owner shall manage vegetation to prevent encroachments into the MVCD of its applicable line(s) which are either an element of an IROL, or an element of a Major WECC Transfer Path; operating within their Rating and all Rated Electrical Operating Conditions of the types shown below2.                                                 \n1. An encroachment into the MVCD as shown in FAC-003-Table 2, observed in Real-time, absent a Sustained Outage, [Violation Risk Factor: High] [Time Horizon: Real-time]:                                                                                \n2. An encroachment due to a fall-in from inside the ROW that caused a vegetation-related Sustained Outage,               \n3. An encroachment due to the blowing together of applicable lines and vegetation located inside the ROW that caused a vegetation-related Sustained Outage,4                                                                                                  \n4. An encroachment due to vegetation growth into the MVCD that caused a vegetation-related Sustained Outage.4",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26601,"FAC-003-2","R2.",null,"Each Transmission Owner shall manage vegetation to prevent encroachments into the MVCD of its applicable line(s) which are not either an element of an IROL, or an element of a Major WECC Transfer Path; operating within its Rating and all Rated Electrical Operating Conditions of the types shown below2 [Violation Risk Factor: Medium] [Time Horizon: Real-time]:                                                                                                                             1. An encroachment into the MVCD, observed in Real-time, absent a Sustained Outage,3        \n2. An encroachment due to a fall-in from inside the ROW that caused a vegetation-related Sustained Outage,4         \n3. An encroachment due to blowing together of applicable lines and vegetation located inside the ROW that caused a vegetation-related Sustained Outage,4                                                                                                                           \n4. An encroachment due to vegetation growth into the line MVCD that caused a vegetation-related Sustained Outage4",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26602,"FAC-003-2","R3.",null,"Each Transmission Owner shall have documented maintenance strategies or procedures or processes or specifications it uses to prevent the encroachment of vegetation into the MVCD of its applicable lines that accounts for the following:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26603,"FAC-003-2","R3.1.",null,"Movement of applicable line conductors under their Rating and all Rated Electrical Operating Conditions;",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26604,"FAC-003-2","R3.2.",null,"Inter-relationships between vegetation growth rates, vegetation control methods, and inspection frequency. [Violation Risk Factor: Lower] [Time Horizon: Long Term Planning]:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26605,"FAC-003-2","R4.",null,"Each Transmission Owner, without any intentional time delay, shall notify the control center holding switching authority for the associated applicable line when the Transmission Owner has confirmed the existence of a vegetation condition that is likely to cause a Fault at any moment [Violation Risk Factor: Medium] [Time Horizon: Real-time].",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26606,"FAC-003-2","R5.",null,"When a Transmission Owner is constrained from performing vegetation work on an applicable line operating within its Rating and all Rated Electrical Operating Conditions, and the constraint may lead to a vegetation encroachment into the MVCD prior to the implementation of the next annual work plan, then the Transmission Owner shall take corrective action to ensure continued vegetation management to prevent encroachments [Violation Risk Factor: Medium] [Time Horizon: Operations Planning].",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26607,"FAC-003-2","R6.",null,"Each Transmission Owner shall perform a Vegetation Inspection of 100% of its applicable transmission lines (measured in units of choice - circuit, pole line, line miles or kilometers, etc.) at least once per calendar year and with no more than 18 calendar months between inspections on the same ROW5.   [Violation Risk Factor: Medium] [Time Horizon: Operations Planning].",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26608,"FAC-003-2","R7.",null,"Each Transmission Owner shall complete 100% of its annual vegetation work plan of applicable lines to ensure no vegetation encroachments occur within the MVCD. Modifications to the work plan in response to changing conditions or to findings from vegetation inspections may be made (provided they do not allow encroachment of vegetation into the MVCD) and must be documented. The percent completed calculation is based on the number of units actually completed divided by the number of units in the final amended plan (measured in units of choice - circuit, pole line, line miles or kilometers, etc.) Examples of reasons for modification to annual plan may include [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]:                                                                       • Change in expected growth rate/ environmental factors                                                                                            \n• Circumstances that are beyond the control of a Transmission Owner6                                                                      \n• Rescheduling work between growing seasons                                                                                                                 \n• Crew or contractor availability/ Mutual assistance agreements                                                                                    \n• Identified unanticipated high priority work                                                                                                                \n• Weather conditions/Accessibility                                                                                                                                 \n• Permitting delays                                                                                                                                                        \n• Land ownership changes/Change in land use by the landowner                                                                                      \n• Emerging technologies",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[25506,"FAC-003-4","R1.",null,"Each applicable Transmission Owner and applicable Generator Owner shall manage vegetation to prevent encroachments into the Minimum Vegetation Clearance Distance (MVCD) of its applicable line(s) which are either an element of an IROL, or an element of a Major WECC Transfer Path; operating within their Rating and all Rated Electrical Operating Conditions of the types shown below4 :","2016-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26610,"FAC-003-4","R1.1.",null,"An encroachment into the MVCD as shown in FAC-003-Table 2, observed in Real-time, absent a Sustained Outage,","2016-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26611,"FAC-003-4","R1.2.",null,"An encroachment due to a fall-in from inside the ROW that caused a vegetation-related Sustained Outage,","2016-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26612,"FAC-003-4","R1.3.",null,"An encroachment due to the blowing together of applicable lines and vegetation located inside the ROW that caused a vegetation-related Sustained Outage","2016-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26613,"FAC-003-4","R1.4.",null,"An encroachment due to vegetation growth into the MVCD that caused a vegetation-related Sustained Outage.","2016-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26614,"FAC-003-4","R2.",null,"Each applicable Transmission Owner and applicable Generator Owner shall manage vegetation to prevent encroachments into the MVCD of its applicable line(s) which are not either an element of an IROL, or an element of a Major WECC Transfer Path; operating within its Rating and all Rated Electrical Operating Conditions of the types shown below","2016-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26615,"FAC-003-4","R2.1.",null,"An encroachment into the MVCD, observed in Real-time, absent a Sustained Outage","2016-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26616,"FAC-003-4","R2.2.",null,"An encroachment due to a fall-in from inside the ROW that caused a vegetation-related Sustained Outage,","2016-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26617,"FAC-003-4","R2.3.",null,"An encroachment due to the blowing together of applicable lines and vegetation located inside the ROW that caused a vegetation-related Sustained Outage,","2016-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26618,"FAC-003-4","R2.4.",null,"An encroachment due to vegetation growth into the line MVCD that caused a vegetation-related Sustained Outage.","2016-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26619,"FAC-003-4","R3.",null,"Each applicable Transmission Owner and applicable Generator Owner shall have documented maintenance strategies or procedures or processes or specifications it uses to prevent the encroachment of vegetation into the MVCD of its applicable lines that accounts for the following:","2016-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26620,"FAC-003-4","R3.1.",null,"Movement of applicable line conductors under their Rating and all Rated Electrical Operating Conditions;","2016-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26621,"FAC-003-4","R3.2.",null,"Inter-relationships between vegetation growth rates, vegetation control methods, and inspection frequency.","2016-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26622,"FAC-003-4","R4.",null,"Each applicable Transmission Owner and applicable Generator Owner, without any intentional time delay, shall notify the control center holding switching authority for the associated applicable line when the applicable Transmission Owner and applicable Generator Owner has confirmed the existence of a vegetation condition that is likely to cause a Fault at any moment","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26623,"FAC-003-4","R5.",null,"When an applicable Transmission Owner and an applicable Generator Owner are constrained from performing vegetation work on an applicable line operating within its Rating and all Rated Electrical Operating Conditions, and the constraint may lead to a vegetation encroachment into the MVCD prior to the implementation of the next annual work plan, then the applicable Transmission Owner or applicable Generator Owner shall take corrective action to ensure continued vegetation management to prevent encroachments","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26624,"FAC-003-4","R6.",null,"Each applicable Transmission Owner and applicable Generator Owner shall perform a Vegetation Inspection of 100% of its applicable transmission lines (measured in units of choice - circuit, pole line, line miles or kilometers, etc.) at least once per calendar year and with no more than 18 calendar months between inspections on the same ROW14","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26625,"FAC-003-4","R7.",null,"Each applicable Transmission Owner and applicable Generator Owner shall complete 100% of its annual vegetation work plan of applicable lines to ensure no vegetation encroachments occur within the MVCD. Modifications to the work plan in response to changing conditions or to findings from vegetation inspections may be made (provided they do not allow encroachment of vegetation into the MVCD) and must be documented. The percent completed calculation is based on the number of units actually completed divided by the number of units in the final amended plan (measured in units of choice - circuit, pole line, line miles or kilometers, etc.). Examples of reasons for modification to annual plan may include","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26626,"FAC-003-4","R7.1.",null,"Change in expected growth rate/environmental factors","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26635,"FAC-003-4","R7.10.",null,"Each applicable Transmission Owner and applicable Generator Owner has evidence that it completed its annual vegetation work plan for its applicable lines. Examples of acceptable forms of evidence may include a copy of the completed annual work plan (as finally modified), dated work orders, dated invoices, or dated inspection records.","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26627,"FAC-003-4","R7.2.",null,"Circumstances that are beyond the control of an applicable Transmission Owner or applicable Generator Owner15","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26628,"FAC-003-4","R7.3.",null,"Rescheduling work between growing seasons","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26629,"FAC-003-4","R7.4.",null,"Crew or contractor availability/Mutual assistance agreements","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26630,"FAC-003-4","R7.5.",null,"Identified unanticipated high priority work","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26631,"FAC-003-4","R7.6.",null,"Weather conditions/Accessibility","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26632,"FAC-003-4","R7.7.",null,"Permitting delays","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26633,"FAC-003-4","R7.8.",null,"Land ownership changes/Change in land use by the landowner","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26634,"FAC-003-4","R7.9.",null,"Emerging technologies","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30493,"FAC-003-5","R1.",null,"Each applicable Transmission Owner and applicable Generator Owner shall manage vegetation to prevent encroachments into the Minimum Vegetation Clearance Distance (MVCD) of its applicable line(s); operating within their Rating and all Rated Electrical Operating Conditions of the types shown below4 :","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30494,"FAC-003-5","R1.1.",null,"An encroachment into the MVCD as shown in FAC-003-Table 2, observed in Real-time, absent a Sustained Outage,","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30495,"FAC-003-5","R1.2.",null,"An encroachment due to a fall-in from inside the ROW that caused a vegetation-related Sustained Outage,","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30496,"FAC-003-5","R1.3.",null,"An encroachment due to the blowing together of applicable lines and vegetation located inside the ROW that caused a vegetation-related Sustained Outage","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30497,"FAC-003-5","R1.4.",null,"An encroachment due to vegetation growth into the MVCD that caused a vegetation-related Sustained Outage.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30498,"FAC-003-5","R2.",null,"Reserved for future use","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30503,"FAC-003-5","R3.",null,"Each applicable Transmission Owner and applicable Generator Owner shall have documented maintenance strategies or procedures or processes or specifications it uses to prevent the encroachment of vegetation into the MVCD of its applicable lines that accounts for the following:","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30504,"FAC-003-5","R3.1.",null,"Movement of applicable line conductors under their Rating and all Rated Electrical Operating Conditions;","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30505,"FAC-003-5","R3.2.",null,"Inter-relationships between vegetation growth rates, vegetation control methods, and inspection frequency.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30506,"FAC-003-5","R4.",null,"Each applicable Transmission Owner and applicable Generator Owner, without any intentional time delay, shall notify the control center holding switching authority for the associated applicable line when the applicable Transmission Owner and applicable Generator Owner has confirmed the existence of a vegetation condition that is likely to cause a Fault at any moment","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30507,"FAC-003-5","R5.",null,"When an applicable Transmission Owner and an applicable Generator Owner are constrained from performing vegetation work on an applicable line operating within its Rating and all Rated Electrical Operating Conditions, and the constraint may lead to a vegetation encroachment into the MVCD prior to the implementation of the next annual work plan, then the applicable Transmission Owner or applicable Generator Owner shall take corrective action to ensure continued vegetation management to prevent encroachments","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30508,"FAC-003-5","R6.",null,"Each applicable Transmission Owner and applicable Generator Owner shall perform a Vegetation Inspection of 100% of its applicable transmission lines (measured in units of choice - circuit, pole line, line miles or kilometers, etc.) at least once per calendar year and with no more than 18 calendar months between inspections on the same ROW14","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30509,"FAC-003-5","R7.",null,"Each applicable Transmission Owner and applicable Generator Owner shall complete 100% of its annual vegetation work plan of applicable lines to ensure no vegetation encroachments occur within the MVCD. Modifications to the work plan in response to changing conditions or to findings from vegetation inspections may be made (provided they do not allow encroachment of vegetation into the MVCD) and must be documented. The percent completed calculation is based on the number of units actually completed divided by the number of units in the final amended plan (measured in units of choice - circuit, pole line, line miles or kilometers, etc.). Examples of reasons for modification to annual plan may include","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30510,"FAC-003-5","R7.1.",null,"Change in expected growth rate/environmental factors","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30519,"FAC-003-5","R7.10.",null,"Each applicable Transmission Owner and applicable Generator Owner has evidence that it completed its annual vegetation work plan for its applicable lines. Examples of acceptable forms of evidence may include a copy of the completed annual work plan (as finally modified), dated work orders, dated invoices, or dated inspection records.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30511,"FAC-003-5","R7.2.",null,"Circumstances that are beyond the control of an applicable Transmission Owner or applicable Generator Owner15","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30512,"FAC-003-5","R7.3.",null,"Rescheduling work between growing seasons","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30513,"FAC-003-5","R7.4.",null,"Crew or contractor availability/Mutual assistance agreements","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30514,"FAC-003-5","R7.5.",null,"Identified unanticipated high priority work","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30515,"FAC-003-5","R7.6.",null,"Weather conditions/Accessibility","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30516,"FAC-003-5","R7.7.",null,"Permitting delays","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30517,"FAC-003-5","R7.8.",null,"Land ownership changes/Change in land use by the landowner","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30518,"FAC-003-5","R7.9.",null,"Emerging technologies","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26636,"FAC-008-2","R1.",null,"Each Generator Owner shall have documentation for determining the Facility Ratings of its solely and jointly owned generator Facility(ies) up to the low side terminals of the main step up transformer if the Generator Owner does not own the main step up transformer and the high side terminals of the main step up transformer if the Generator Owner owns the main step up transformer.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","GO","Yes",false,null,false]
[26637,"FAC-008-2","R1.1.",null,"The documentation shall contain assumptions used to rate the generator and at least one of the following:\n• Design or construction information such as design criteria, ratings provided by equipment manufacturers, equipment drawings and/or specifications, engineering analyses, method(s) consistent with industry standards (e.g. ANSI and IEEE), or an established engineering practice that has been verified by testing or engineering analysis.\n• Operational information such as commissioning test results, performance testing or historical performance records, any of which may be supplemented by engineering analyses.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","GO","Yes",false,null,false]
[26638,"FAC-008-2","R1.2.",null,"The documentation shall be consistent with the principle that the Facility Ratings do not exceed the most limiting applicable Equipment Rating of the individual equipment that comprises that Facility.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","GO","Yes",false,null,false]
[26639,"FAC-008-2","R2.",null,"Each Generator Owner shall have a documented methodology for determining Facility Ratings (Facility Ratings methodology) of its solely and jointly owned equipment connected between the location specified in R1 and the point of interconnection with the Transmission Owner that contains all of the following.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","GO","Yes",false,null,false]
[26640,"FAC-008-2","R2.1.",null,"The methodology used to establish the Ratings of the equipment that comprises the Facility(ies) shall be consistent with at least one of the following:  • Ratings provided by equipment manufacturers or obtained from equipment manufacturer specifications such as nameplate rating. • One or more industry standards developed through an open process such as Institute of Electrical and Electronic Engineers (IEEE) or International Council on Large Electric Systems (CIGRE).\n• A practice that has been verified by testing, performance history or engineering analysis.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","GO","Yes",false,null,false]
[26641,"FAC-008-2","R2.2.",null,"The underlying assumptions, design criteria, and methods used to determine the Equipment Ratings identified in Requirement R2, Part 2.1 including identification of how each of the following were considered:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","GO","Yes",false,null,false]
[26642,"FAC-008-2","R2.2.1.",null,"Equipment Rating standard(s) used in development of this methodology.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","GO","Yes",false,null,false]
[26643,"FAC-008-2","R2.2.2.",null,"Ratings provided by equipment manufacturers or obtained from equipment manufacturer specifications.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","GO","Yes",false,null,false]
[26644,"FAC-008-2","R2.2.3.",null,"Ambient conditions (for particular or average conditions or as they vary in real-time).",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","GO","Yes",false,null,false]
[26645,"FAC-008-2","R2.2.4.",null,"Operating limitations.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","GO","Yes",false,null,false]
[26646,"FAC-008-2","R2.3.",null,"A statement that a Facility Rating shall respect the most limiting applicable Equipment Rating of the individual equipment that comprises that Facility.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","GO","Yes",false,null,false]
[26647,"FAC-008-2","R2.4.",null,"The process by which the Rating of equipment that comprises a Facility is determined.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","GO","Yes",false,null,false]
[26648,"FAC-008-2","R2.4.1.",null,"The scope of equipment addressed shall include, but not be limited to, conductors, transformers, relay protective devices, terminal equipment, and series and shunt compensation devices.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","GO","Yes",false,null,false]
[26649,"FAC-008-2","R2.4.2.",null,"The scope of Ratings addressed shall include, as a minimum, both Normal and Emergency Ratings.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","GO","Yes",false,null,false]
[26650,"FAC-008-2","R3.",null,"Each Transmission Owner shall have a documented methodology for determining Facility Ratings (Facility Ratings methodology) of its solely and jointly owned Facilities (except for those generating unit Facilities addressed in R1 and R2) that contains all of the following:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TO","Yes",false,null,false]
[26651,"FAC-008-2","R3.1.",null,"The methodology used to establish the Ratings of the equipment that comprises the Facility shall be consistent with at least one of the following:\n• Ratings provided by equipment manufacturers or obtained from equipment manufacturer specifications such as nameplate rating.\n• One or more industry standards developed through an open process such as Institute of Electrical and Electronics Engineers (IEEE) or International Council on Large Electric Systems (CIGRE).\n• A practice that has been verified by testing, performance history or engineering analysis.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TO","Yes",false,null,false]
[26652,"FAC-008-2","R3.2.",null,"The underlying assumptions, design criteria, and methods used to determine the Equipment Ratings identified in Requirement R3, Part 3.1 including identification of how each of the following were considered:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TO","Yes",false,null,false]
[26653,"FAC-008-2","R3.2.1.",null,"Equipment Rating standard(s) used in development of this methodology.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TO","Yes",false,null,false]
[26654,"FAC-008-2","R3.2.2.",null,"Ratings provided by equipment manufacturers or obtained from equipment manufacturer specifications.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TO","Yes",false,null,false]
[26655,"FAC-008-2","R3.2.3.",null,"Ambient conditions (for particular or average conditions or as they vary in real-time).",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TO","Yes",false,null,false]
[26656,"FAC-008-2","R3.2.4.",null,"Operating limitations.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TO","Yes",false,null,false]
[26657,"FAC-008-2","R3.3.",null,"A statement that a Facility Rating shall respect the most limiting applicable Equipment Rating of the individual equipment that comprises that Facility.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TO","Yes",false,null,false]
[26658,"FAC-008-2","R3.4.",null,"The process by which the Rating of equipment that comprises a Facility is determined.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TO","Yes",false,null,false]
[26659,"FAC-008-2","R3.4.1.",null,"The scope of equipment addressed shall include, but not be limited to, transmission conductors, transformers, relay protective devices, terminal equipment, and series and shunt compensation devices.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TO","Yes",false,null,false]
[26660,"FAC-008-2","R3.4.2.",null,"The scope of Ratings addressed shall include, as a minimum, both Normal and Emergency Ratings.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TO","Yes",false,null,false]
[26661,"FAC-008-2","R4.",null,"Each Transmission Owner shall make its Facility Ratings methodology and each Generator Owner shall each make its documentation for determining its Facility Ratings and its Facility Ratings methodology available for inspection and technical review by those Reliability Coordinators, Transmission Operators, Transmission Planners and Planning Coordinators that have responsibility for the area in which the associated Facilities are located, within 21 calendar days of receipt of a request.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26662,"FAC-008-2","R5.",null,"If a Reliability Coordinator, Transmission Operator, Transmission Planner or Planning Coordinator provides documented comments on its technical review of a Transmission Owner’s Facility Ratings methodology or Generator Owner’s documentation for determining its Facility Ratings and its Facility Rating methodology, the Transmission Owner or Generator Owner shall provide a response to that commenting entity within 45 calendar days of receipt of those comments. The response shall indicate whether a change will be made to the Facility Ratings methodology and, if no change will be made to that Facility Ratings methodology, the reason why.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26663,"FAC-008-2","R6.",null,"Each Transmission Owner and Generator Owner shall have Facility Ratings for its solely and jointly owned Facilities that are consistent with the associated Facility Ratings methodology or documentation for determining its Facility Ratings.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26664,"FAC-008-2","R7.",null,"Each Transmission Owner and Generator Owner shall 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 Coordinator(s), Transmission Planner(s), Transmission Owner(s) and Transmission Operator(s) as scheduled by such requesting entities.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26665,"FAC-008-3","R1.",null,"Each Generator Owner shall have documentation for determining the Facility Ratings of its solely and jointly owned generator Facility(ies) up to the low side terminals of the main step up transformer if the Generator Owner does not own the main step up transformer and the high side terminals of the main step up transformer if the Generator Owner owns the main step up transformer.","2013-01-01","2021-09-30","Retired",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26666,"FAC-008-3","R1.1.",null,"The documentation shall contain assumptions used to rate the generator and at least one of the following:• Design or construction information such as design criteria, ratings provided by equipment manufacturers, equipment drawings and/or specifications, engineering analyses, method(s) consistent with industry standards (e.g. ANSI and IEEE), or an established engineering practice that has been verified by testing or engineering analysis.• Operational information such as commissioning test results, performance testing or historical performance records, any of which may be supplemented by engineering analyses.","2013-01-01","2021-09-30","Retired",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26667,"FAC-008-3","R1.2.",null,"The documentation shall be consistent with the principle that the Facility Ratings do not exceed the most limiting applicable Equipment Rating of the individual equipment that comprises that Facility.","2013-01-01","2021-09-30","Retired",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26668,"FAC-008-3","R2.",null,"Each Generator Owner shall have a documented methodology for determining Facility Ratings (Facility Ratings methodology) of its solely and jointly owned equipment connected between the location specified in R1 and the point of interconnection with the Transmission Owner that contains all of the following.","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26669,"FAC-008-3","R2.1.",null,"The methodology used to establish the Ratings of the equipment that comprises the Facility(ies) shall be consistent with at least one of the following:• Ratings provided by equipment manufacturers or obtained from equipment manufacturer specifications such as nameplate rating. • One or more industry standards developed through an open process such as Institute of Electrical and Electronic Engineers (IEEE) or International Council on Large Electric Systems (CIGRE).• A practice that has been verified by testing, performance history or engineering analysis.","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26670,"FAC-008-3","R2.2.",null,"The underlying assumptions, design criteria, and methods used to determine the Equipment Ratings identified in Requirement R2, Part 2.1 including identification of how each of the following were considered:","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26671,"FAC-008-3","R2.2.1.",null,"Equipment Rating standard(s) used in development of this methodology.","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26672,"FAC-008-3","R2.2.2.",null,"Ratings provided by equipment manufacturers or obtained from equipment manufacturer specifications.","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26673,"FAC-008-3","R2.2.3.",null,"Ambient conditions (for particular or average conditions or as they vary in real-time).","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26674,"FAC-008-3","R2.2.4.",null,"Operating limitations.1","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26675,"FAC-008-3","R2.3.",null,"A statement that a Facility Rating shall respect the most limiting applicable Equipment Rating of the individual equipment that comprises that Facility.","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26676,"FAC-008-3","R2.4.",null,"The process by which the Rating of equipment that comprises a Facility is determined.","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26677,"FAC-008-3","R2.4.1.",null,"The scope of equipment addressed shall include, but not be limited to, conductors, transformers, relay protective devices, terminal equipment, and series and shunt compensation devices.","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26678,"FAC-008-3","R2.4.2.",null,"The scope of Ratings addressed shall include, as a minimum, both Normal and Emergency Ratings.","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26679,"FAC-008-3","R3.",null,"Each Transmission Owner shall have a documented methodology for determining Facility Ratings (Facility Ratings methodology) of its solely and jointly owned Facilities (except for those generating unit Facilities addressed in R1 and R2) that contains all of the following:","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26680,"FAC-008-3","R3.1.",null,"The methodology used to establish the Ratings of the equipment that comprises the Facility shall be consistent with at least one of the following:• Ratings provided by equipment manufacturers or obtained from equipment manufacturer specifications such as nameplate rating.• One or more industry standards developed through an open process such as Institute of Electrical and Electronics Engineers (IEEE) or International Council on Large Electric Systems (CIGRE).• A practice that has been verified by testing, performance history or engineering analysis.","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26681,"FAC-008-3","R3.2.",null,"The underlying assumptions, design criteria, and methods used to determine the Equipment Ratings identified in Requirement R3, Part 3.1 including identification of how each of the following were considered:","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26682,"FAC-008-3","R3.2.1.",null,"Equipment Rating standard(s) used in development of this methodology.","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26683,"FAC-008-3","R3.2.2.",null,"Ratings provided by equipment manufacturers or obtained from equipment manufacturer specifications.","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26684,"FAC-008-3","R3.2.3.",null,"Ambient conditions (for particular or average conditions or as they vary in real-time).","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26685,"FAC-008-3","R3.2.4.",null,"Operating limitations.2","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26686,"FAC-008-3","R3.3.",null,"A statement that a Facility Rating shall respect the most limiting applicable Equipment Rating of the individual equipment that comprises that Facility.","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26687,"FAC-008-3","R3.4.",null,"The process by which the Rating of equipment that comprises a Facility is determined.","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26688,"FAC-008-3","R3.4.1.",null,"The scope of equipment addressed shall include, but not be limited to, transmission conductors, transformers, relay protective devices, terminal equipment, and series and shunt compensation devices.","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26689,"FAC-008-3","R3.4.2.",null,"The scope of Ratings addressed shall include, as a minimum, both Normal and Emergency Ratings.","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[26690,"FAC-008-3","R6.",null,"Each Transmission Owner and Generator Owner shall have Facility Ratings for its solely and jointly owned Facilities that are consistent with the associated Facility Ratings methodology or documentation for determining its Facility Ratings.","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26691,"FAC-008-3","R7.",null,"Each Generator Owner shall 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 Coordinator(s), Transmission Planner(s), Transmission Owner(s) and Transmission Operator(s) as scheduled by such requesting entities.","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26692,"FAC-008-3","R8.",null,"Each Transmission Owner (and each Generator Owner subject to Requirement R2) shall provide requested information as specified below (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 Coordinator(s), Transmission Planner(s), Transmission Owner(s) and Transmission Operator(s):","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26693,"FAC-008-3","R8.1.",null,"As scheduled by the requesting entities:","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26694,"FAC-008-3","R8.1.1.",null,"Facility Ratings","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26695,"FAC-008-3","R8.1.2.",null,"Identity of the most limiting equipment of the Facilities","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26696,"FAC-008-3","R8.2.",null,"Within 30 calendar days (or a later date if specified by the requester), for any requested Facility with a Thermal Rating that limits the use of Facilities under the requester’s authority by causing any of the following: 1) An Interconnection Reliability Operating Limit, 2) A limitation of Total Transfer Capability, 3) An impediment to generator deliverability, or 4) An impediment to service to a major load center:","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26697,"FAC-008-3","R8.2.1.",null,"Identity of the existing next most limiting equipment of the Facility","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26698,"FAC-008-3","R8.2.2.",null,"The Thermal Rating for the next most limiting equipment identified in Requirement R8, Part 8.2.1.","2013-01-01","2021-09-30","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30373,"FAC-008-5","R1.",null,"Each Generator Owner shall have documentation for determining the Facility Ratings of its solely and jointly owned generator Facility(ies) up to the low side terminals of the main step up transformer if the Generator Owner does not own the main step up transformer and the high side terminals of the main step up transformer if the Generator Owner owns the main step up transformer.","2021-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30374,"FAC-008-5","R1.1.",null,"The documentation shall contain assumptions used to rate the generator and at least one of the following:• Design or construction information such as design criteria, ratings provided by equipment manufacturers, equipment drawings and/or specifications, engineering analyses, method(s) consistent with industry standards (e.g. ANSI and IEEE), or an established engineering practice that has been verified by testing or engineering analysis.• Operational information such as commissioning test results, performance testing or historical performance records, any of which may be supplemented by engineering analyses.","2021-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30375,"FAC-008-5","R1.2.",null,"The documentation shall be consistent with the principle that the Facility Ratings do not exceed the most limiting applicable Equipment Rating of the individual equipment that comprises that Facility.","2021-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30376,"FAC-008-5","R2.",null,"Each Generator Owner shall have a documented methodology for determining Facility Ratings (Facility Ratings methodology) of its solely and jointly owned equipment connected between the location specified in R1 and the point of interconnection with the Transmission Owner that contains all of the following.","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30377,"FAC-008-5","R2.1.",null,"The methodology used to establish the Ratings of the equipment that comprises the Facility(ies) shall be consistent with at least one of the following:• Ratings provided by equipment manufacturers or obtained from equipment manufacturer specifications such as nameplate rating. • One or more industry standards developed through an open process such as Institute of Electrical and Electronic Engineers (IEEE) or International Council on Large Electric Systems (CIGRE).• A practice that has been verified by testing, performance history or engineering analysis.","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30378,"FAC-008-5","R2.2.",null,"The underlying assumptions, design criteria, and methods used to determine the Equipment Ratings identified in Requirement R2, Part 2.1 including identification of how each of the following were considered:","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30379,"FAC-008-5","R2.2.1.",null,"Equipment Rating standard(s) used in development of this methodology.","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30380,"FAC-008-5","R2.2.2.",null,"Ratings provided by equipment manufacturers or obtained from equipment manufacturer specifications.","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30381,"FAC-008-5","R2.2.3.",null,"Ambient conditions (for particular or average conditions or as they vary in real-time).","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30382,"FAC-008-5","R2.2.4.",null,"Operating limitations.1","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30383,"FAC-008-5","R2.3.",null,"A statement that a Facility Rating shall respect the most limiting applicable Equipment Rating of the individual equipment that comprises that Facility.","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30384,"FAC-008-5","R2.4.",null,"The process by which the Rating of equipment that comprises a Facility is determined.","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30385,"FAC-008-5","R2.4.1.",null,"The scope of equipment addressed shall include, but not be limited to, conductors, transformers, relay protective devices, terminal equipment, and series and shunt compensation devices.","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30386,"FAC-008-5","R2.4.2.",null,"The scope of Ratings addressed shall include, as a minimum, both Normal and Emergency Ratings.","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30387,"FAC-008-5","R3.",null,"Each Transmission Owner shall have a documented methodology for determining Facility Ratings (Facility Ratings methodology) of its solely and jointly owned Facilities (except for those generating unit Facilities addressed in R1 and R2) that contains all of the following:","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30388,"FAC-008-5","R3.1.",null,"The methodology used to establish the Ratings of the equipment that comprises the Facility shall be consistent with at least one of the following:• Ratings provided by equipment manufacturers or obtained from equipment manufacturer specifications such as nameplate rating.• One or more industry standards developed through an open process such as Institute of Electrical and Electronics Engineers (IEEE) or International Council on Large Electric Systems (CIGRE).• A practice that has been verified by testing, performance history or engineering analysis.","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30389,"FAC-008-5","R3.2.",null,"The underlying assumptions, design criteria, and methods used to determine the Equipment Ratings identified in Requirement R3, Part 3.1 including identification of how each of the following were considered:","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30390,"FAC-008-5","R3.2.1.",null,"Equipment Rating standard(s) used in development of this methodology.","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30391,"FAC-008-5","R3.2.2.",null,"Ratings provided by equipment manufacturers or obtained from equipment manufacturer specifications.","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30392,"FAC-008-5","R3.2.3.",null,"Ambient conditions (for particular or average conditions or as they vary in real-time).","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30393,"FAC-008-5","R3.2.4.",null,"Operating limitations.2","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30394,"FAC-008-5","R3.3.",null,"A statement that a Facility Rating shall respect the most limiting applicable Equipment Rating of the individual equipment that comprises that Facility.","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30395,"FAC-008-5","R3.4.",null,"The process by which the Rating of equipment that comprises a Facility is determined.","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30396,"FAC-008-5","R3.4.1.",null,"The scope of equipment addressed shall include, but not be limited to, transmission conductors, transformers, relay protective devices, terminal equipment, and series and shunt compensation devices.","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30397,"FAC-008-5","R3.4.2.",null,"The scope of Ratings addressed shall include, as a minimum, both Normal and Emergency Ratings.","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30398,"FAC-008-5","R6.",null,"Each Transmission Owner and Generator Owner shall have Facility Ratings for its solely and jointly owned Facilities that are consistent with the associated Facility Ratings methodology or documentation for determining its Facility Ratings.","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30399,"FAC-008-5","R8.",null,"Each Transmission Owner (and each Generator Owner subject to Requirement R2) shall provide requested information as specified below (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 Coordinator(s), Transmission Planner(s), Transmission Owner(s) and Transmission Operator(s):","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30400,"FAC-008-5","R8.1.",null,"As scheduled by the requesting entities:","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30401,"FAC-008-5","R8.1.1.",null,"Facility Ratings","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30402,"FAC-008-5","R8.1.2.",null,"Identity of the most limiting equipment of the Facilities","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30403,"FAC-008-5","R8.2.",null,"Within 30 calendar days (or a later date if specified by the requester), for any requested Facility with a Thermal Rating that limits the use of Facilities under the requester’s authority by causing any of the following: 1) An Interconnection Reliability Operating Limit, 2) A limitation of Total Transfer Capability, 3) An impediment to generator deliverability, or 4) An impediment to service to a major load center:","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30404,"FAC-008-5","R8.2.1.",null,"Identity of the existing next most limiting equipment of the Facility","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30405,"FAC-008-5","R8.2.2.",null,"The Thermal Rating for the next most limiting equipment identified in Requirement R8, Part 8.2.1.","2021-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[26727,"FAC-010-3","R1.",null,"The Planning Authority shall have a documented SOL Methodology for use in developing SOLs within its Planning Authority Area.  This SOL Methodology shall:","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PA","No",false,null,false]
[26728,"FAC-010-3","R1.1.",null,"Be applicable for developing SOLs used in the planning horizon.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PA","No",false,null,false]
[26729,"FAC-010-3","R1.2.",null,"State that SOLs shall not exceed associated Facility Ratings.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PA","No",false,null,false]
[26730,"FAC-010-3","R1.3.",null,"Include a description of how to identify the subset of SOLs that qualify as IROLs.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PA","No",false,null,false]
[26731,"FAC-010-3","R2.",null,"The Planning Authority’s SOL Methodology shall include a requirement that SOLs provide BES performance consistent with the following:","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","PA","No",false,null,false]
[26732,"FAC-010-3","R2.1.",null,"In the pre-contingency state and with all Facilities in service, the BES shall demonstrate transient, dynamic and voltage stability; all Facilities shall be within their Facility Ratings and within their thermal, voltage and stability limits. In the determination of SOLs, the BES condition used shall reflect expected system conditions and shall reflect changes to system topology such as Facility outages.","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","PA","No",false,null,false]
[26733,"FAC-010-3","R2.2.",null,"Following the single Contingencies1 identified in Requirement 2.2.1 through Requirement 2.2.3, the system shall demonstrate transient, dynamic and voltage stability; all Facilities shall be operating within their Facility Ratings and within their thermal, voltage and stability limits; and Cascading or uncontrolled separation shall not occur.","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","PA","No",false,null,false]
[26734,"FAC-010-3","R2.2.1.",null,"Single line to ground or three-phase Fault (whichever is more severe), with Normal Clearing, on any Faulted generator, line, transformer, or shunt device.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PA","No",false,null,false]
[26735,"FAC-010-3","R2.2.2.",null,"Loss of any generator, line, transformer, or shunt device without a Fault.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PA","No",false,null,false]
[26736,"FAC-010-3","R2.2.3.",null,"Single pole block, with Normal Clearing, in a monopolar or bipolar high voltage direct current system.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PA","No",false,null,false]
[26737,"FAC-010-3","R2.3.",null,"Starting with all Facilities in service, the system’s response to a single Contingency, may include any of the following:","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PA","No",false,null,false]
[26738,"FAC-010-3","R2.3.1.",null,"Planned or controlled interruption of electric supply to radial customers or some local network customers connected to or supplied by the Faulted Facility or by the affected area.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PA","No",false,null,false]
[26739,"FAC-010-3","R2.3.2.",null,"System reconfiguration through manual or automatic control or protection actions.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PA","No",false,null,false]
[26740,"FAC-010-3","R2.4.",null,"To prepare for the next Contingency, system adjustments may be made, including changes to generation, uses of the transmission system, and the transmission system topology.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PA","No",false,null,false]
[26741,"FAC-010-3","R2.5.",null,"Starting with all Facilities in service and following any of the multiple Contingencies identified in Reliability Standard TPL-003 the system shall demonstrate transient, dynamic and voltage stability; all Facilities shall be operating within their Facility Ratings and within their thermal, voltage and stability limits; and Cascading or uncontrolled separation shall not occur.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PA","No",false,null,false]
[26742,"FAC-010-3","R2.6.",null,"In determining the system’s response to any of the multiple Contingencies, identified in Reliability Standard TPL-003, in addition to the actions identified in R2.3.1 and R2.3.2, the following shall be acceptable:","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PA","No",false,null,false]
[26743,"FAC-010-3","R2.6.1.",null,"Planned or controlled interruption of electric supply to customers (load shedding), the planned removal from service of certain generators, and/or the curtailment of contracted Firm (non-recallable reserved) electric power Transfers.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PA","No",false,null,false]
[26744,"FAC-010-3","R3.",null,"The Planning Authority’s methodology for determining SOLs, shall include, as a minimum, a description of the following, along with any reliability margins applied for each:","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PA","No",false,null,false]
[26745,"FAC-010-3","R3.1.",null,"Study model (must include at least the entire Planning Authority Area as well as the critical Real-Time Applications details from other Planning Authority Areas that would impact the Facility or Facilities under study).","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PA","No",false,null,false]
[26746,"FAC-010-3","R3.2.",null,"Selection of applicable Contingencies.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PA","No",false,null,false]
[26747,"FAC-010-3","R3.3.",null,"Level of detail of system models used to determine SOLs.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PA","No",false,null,false]
[26748,"FAC-010-3","R3.4.",null,"Allowed uses of Remedial Action Schemes.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PA","No",false,null,false]
[26749,"FAC-010-3","R3.5.",null,"Anticipated transmission system configuration, generation dispatch and Load level.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PA","No",false,null,false]
[26750,"FAC-010-3","R3.6.",null,"Criteria for determining when violating a SOL qualifies as an Interconnection Reliability Operating Limit (IROL) and criteria for developing any associated IROL Tv.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PA","No",false,null,false]
[26751,"FAC-010-3","R4.",null,"The Planning Authority shall issue its SOL Methodology, and any change to that methodology, to all of the following prior to the effectiveness of the change:","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PA","No",false,null,false]
[26752,"FAC-010-3","R4.1.",null,"Each adjacent Planning Authority and each Planning Authority that indicated it has a reliability-related need for the methodology.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PA","No",false,null,false]
[26753,"FAC-010-3","R4.2.",null,"Each Reliability Coordinator and Transmission Operator that operates any portion of the Planning Authority’s Planning Authority Area.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PA","No",false,null,false]
[26754,"FAC-010-3","R4.3.",null,"Each Transmission Planner that works in the Planning Authority’s Planning Authority Area.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PA","No",false,null,false]
[26783,"FAC-011-3","R1.",null,"The Reliability Coordinator shall have a documented methodology for use in developing SOLs (SOL Methodology) within its Reliability Coordinator Area.  This SOL Methodology shall:","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[26784,"FAC-011-3","R1.1.",null,"Be applicable for developing SOLs used in the operations horizon.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[26785,"FAC-011-3","R1.2.",null,"State that SOLs shall not exceed associated Facility Ratings.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[26786,"FAC-011-3","R1.3.",null,"Include a description of how to identify the subset of SOLs that qualify as IROLs.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[26787,"FAC-011-3","R2.",null,"The Reliability Coordinator’s SOL Methodology shall include a requirement that SOLs provide BES performance consistent with the following:","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[26788,"FAC-011-3","R2.1.",null,"In the pre-contingency state, the BES shall demonstrate transient, dynamic and voltage stability; all Facilities shall be within their Facility Ratings and within their thermal, voltage and stability limits. In the determination of SOLs, the BES condition used shall reflect current or expected system conditions and shall reflect changes to system topology such as Facility outages.","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26789,"FAC-011-3","R2.2.",null,"Following the single Contingencies  identified in Requirement 2.2.1 through Requirement 2.2.3, the system shall demonstrate transient, dynamic and voltage stability; all Facilities shall be operating within their Facility Ratings and within their thermal, voltage and stability limits; and Cascading or uncontrolled separation shall not occur.","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26790,"FAC-011-3","R2.2.1.",null,"Single line to ground or 3-phase Fault (whichever is more severe), with Normal Clearing, on any Faulted generator, line, transformer, or shunt device.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26791,"FAC-011-3","R2.2.2.",null,"Loss of any generator, line, transformer, or shunt device without a Fault.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26792,"FAC-011-3","R2.2.3.",null,"Single pole block, with Normal Clearing, in a monopolar or bipolar high voltage direct current system.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26793,"FAC-011-3","R2.3.",null,"In determining the system’s response to a single Contingency, the following shall be acceptable:","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26794,"FAC-011-3","R2.3.1.",null,"Planned or controlled interruption of electric supply to radial customers or some local network customers connected to or supplied by the Faulted Facility or by the affected area.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26795,"FAC-011-3","R2.3.2.",null,"Interruption of other network customers, (a) only if the system has already been adjusted, or is being adjusted, following at least one prior outage, or (b) if the real-time operating conditions are more adverse than anticipated in the corresponding studies","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26796,"FAC-011-3","R2.3.3.",null,"System reconfiguration through manual or automatic control or protection actions.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26797,"FAC-011-3","R2.4.",null,"To prepare for the next Contingency, system adjustments may be made, including changes to generation, uses of the transmission system, and the transmission system topology.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26798,"FAC-011-3","R3.",null,"The Reliability Coordinator’s methodology for determining SOLs, shall include, as a minimum, a description of the following, along with any reliability margins applied for each:","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26799,"FAC-011-3","R3.1.",null,"Study model (must include at least the entire Reliability Coordinator Area as well as the critical Real-Time Applications details from other Reliability Coordinator Areas that would impact the Facility or Facilities under study.)","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26800,"FAC-011-3","R3.2.",null,"Selection of applicable Contingencies","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26801,"FAC-011-3","R3.3.",null,"A process for determining which of the stability limits associated with the list of multiple contingencies (provided by the Planning Authority in accordance with FAC-014 Requirement 6) are applicable for use in the operating horizon given the actual or expected system conditions.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26802,"FAC-011-3","R3.3.1.",null,"This process shall address the need to modify these limits, to modify the list of limits, and to modify the list of associated multiple contingencies.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[26803,"FAC-011-3","R3.4.",null,"Level of detail of system models used to determine SOLs.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[26804,"FAC-011-3","R3.5.",null,"Allowed uses of Remedial Action Plans.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26805,"FAC-011-3","R3.6.",null,"Anticipated transmission system configuration, generation dispatch and Load level","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26806,"FAC-011-3","R3.7.",null,"Criteria for determining when violating a SOL qualifies as an Interconnection Reliability Operating Limit (IROL) and criteria for developing any associated IROL Tv.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26807,"FAC-011-3","R4.",null,"The Reliability Coordinator shall issue its SOL Methodology and any changes to that methodology, prior to the effectiveness of the Methodology or of a change to the Methodology, to all of the following:","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[26808,"FAC-011-3","R4.1.",null,"Each adjacent Reliability Coordinator and each Reliability Coordinator that indicated it has a reliability-related need for the methodology.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[26809,"FAC-011-3","R4.2.",null,"Each Planning Authority and Transmission Planner that models any portion of the Reliability Coordinator’s Reliability Coordinator Area.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[26810,"FAC-011-3","R4.3.",null,"Each Transmission Operator that operates in the Reliability Coordinator Area.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[30612,"FAC-011-4","R1.","YES","Each Reliability Coordinator shall have a documented methodology for establishing SOLs (i.e., SOL methodology) within its Reliability Coordinator Area.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30619,"FAC-011-4","R1.",null,"Each Reliability Coordinator shall have a documented methodology for establishing SOLs (i.e., SOL methodology) within its Reliability Coordinator Area.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30620,"FAC-011-4","R2.",null,"Each Reliability Coordinator shall include in its SOL methodology the method for Transmission Operators to determine which owner-provided Facility Ratings are to be used in operations such that the Transmission Operator and its Reliability Coordinator use common Facility Ratings","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30621,"FAC-011-4","R3.",null,"Each Reliability Coordinator shall include in its SOL methodology the method for Transmission Operators to determine the System Voltage Limits to be used in operations. The method shall:","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30622,"FAC-011-4","R3.1.",null,"Require that each BES bus/station have an associated System Voltage Limits, unless its SOL methodology specifically allows the exclusion of BES buses/stations from the requirement to have an associated System Voltage Limit;","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30623,"FAC-011-4","R3.2.",null,"Require that System Voltage Limits respect voltage-based Facility Ratings;","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30624,"FAC-011-4","R3.3.",null,"Require that System Voltage Limits are greater than or equal to in-service BES relay settings for undervoltage load shedding systems and Undervoltage Load Shedding Programs;","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30625,"FAC-011-4","R3.4.",null,"Identify the minimum allowable System Voltage Limit;","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30626,"FAC-011-4","R3.5.",null,"Define the method for determining common System Voltage Limits between the Reliability Coordinator and its Transmission Operators, between adjacent Transmission Operators, and between adjacent Reliability Coordinators within an Interconnection","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30627,"FAC-011-4","R4.",null,"Each Reliability Coordinator shall include in its SOL methodology the method for determining the stability limits to be used in operations. The method shall:","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30628,"FAC-011-4","R4.1.",null,"Specify stability performance criteria, including any margins applied. The criteria shall, at a minimum, include the following:","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30629,"FAC-011-4","R4.1.1.",null,"steady-state voltage stability;","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30630,"FAC-011-4","R4.1.2.",null,"transient voltage response;","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30631,"FAC-011-4","R4.1.3.",null,"angular stability; and","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30632,"FAC-011-4","R4.1.4.",null,"System damping.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30633,"FAC-011-4","R4.2.",null,"Require that stability limits are established to meet the criteria specified in Part 4.1 for the Contingencies identified in Requirement R5 applicable to the establishment of stability limits that are expected to produce more severe System impacts on its portion of the BES.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30634,"FAC-011-4","R4.3.",null,"Describe how the Reliability Coordinator establishes stability limits when there is an impact to more than one Transmission Operator in its Reliability Coordinator Area or other Reliability Coordinator Areas.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30635,"FAC-011-4","R4.4.",null,"Describe how stability limits are determined, considering levels of transfers, Load and generation dispatch, and System conditions including any changes to System topology such as Facility outages.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30636,"FAC-011-4","R4.5.",null,"Describe the level of detail that is required for the study model(s), including the portion modeled of the Reliability Coordinator Area, and the critical modeling details from other Reliability Coordinator Areas, necessary to determine different types of stability limits.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30637,"FAC-011-4","R4.6.",null,"Describe the allowed uses of Remedial Action Schemes and other automatic post-Contingency mitigation actions in establishing stability limits used in operations.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30638,"FAC-011-4","R4.7.",null,"State that the use of underfrequency load shedding (UFLS) programs and Undervoltage Load Shedding (UVLS) Programs are not allowed in the establishment of stability limits.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30639,"FAC-011-4","R5.",null,"Each Reliability Coordinator shall identify in its SOL methodology the set of Contingency events for use in determining stability limits and the set of Contingency events for use in performing Operational Planning Analysis (OPAs) and Real-time Assessments (RTAs). The SOL methodology for each set shall:","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30640,"FAC-011-4","R5.1.",null,"Specify the following single Contingency events","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30641,"FAC-011-4","R5.1.1.",null,"Loss of any of the following either by single phase to ground or three phase Fault (whichever is more severe) with Normal Clearing, or without a Fault: • generator; • transmission circuit; • transformer; • shunt device; or • single pole block in a monopolar or bipolar high voltage direct current system.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30642,"FAC-011-4","R5.2.",null,"Specify additional single or multiple Contingency events or types of Contingency events, if any.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30643,"FAC-011-4","R5.3.",null,"Describe the method(s) for identifying which, if any, of the Contingency events provided by the Planning Coordinator or Transmission Planner in accordance with FAC-014-3, Requirement R7, to use in determining stability limits.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30644,"FAC-011-4","R6.",null,"Each Reliability Coordinator shall include the following performance framework in its SOL methodology to determine SOL exceedances when performing Real-time monitoring, Real-time Assessments, and Operational Planning Analyses:","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30645,"FAC-011-4","R6.1.",null,"System performance for no Contingencies demonstrates the following:","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30646,"FAC-011-4","R6.1.1.",null,"Steady state flow through Facilities are within Normal Ratings; however, Emergency Ratings may be used when System adjustments to return the flow within its Normal Rating could be executed and completed within the specified time duration of those Emergency Ratings.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30647,"FAC-011-4","R6.1.2.",null,"Steady state voltages are within normal System Voltage Limits; however, emergency System Voltage Limits may be used when System adjustments to return the voltage within its normal System Voltage Limits could be executed and completed within the specified time duration of those emergency System Voltage Limits.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30648,"FAC-011-4","R6.1.3.",null,"Predetermined stability limits are not exceeded.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30649,"FAC-011-4","R6.1.4.",null,"Instability, Cascading or uncontrolled separation that adversely impact the reliability of the Bulk Electric System does not occur. 1","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30650,"FAC-011-4","R6.2.",null,"System performance for the single Contingencies listed in Part 5.1 demonstrates the following:","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30651,"FAC-011-4","R6.2.1.",null,"Steady state post-Contingency flow through Facilities within applicable Emergency Ratings. Steady state post-Contingency flow through a Facility must not be above the Facility’s highest Emergency Rating.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30652,"FAC-011-4","R6.2.2.",null,"Steady state post-Contingency voltages are within emergency System Voltage Limits.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30653,"FAC-011-4","R6.2.3.",null,"The stability performance criteria defined in the Reliability Coordinator’s SOL methodology are met1 .","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30654,"FAC-011-4","R6.2.4.",null,"Instability, Cascading or uncontrolled separation that adversely impact the reliability of the Bulk Electric System does not occur1 .","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30655,"FAC-011-4","R6.3.",null,"System performance for applicable Contingencies identified in Part 5.2 demonstrates that: instability, Cascading, or uncontrolled separation that adversely impact the reliability of the Bulk Electric System does not occur.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30656,"FAC-011-4","R6.4.",null,"In determining the System’s response to any Contingency identified in Requirement R5, planned manual load shedding is acceptable only after all other available System adjustments have been made.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30657,"FAC-011-4","R7.",null,"Each Reliability Coordinator shall include in its SOL methodology a risk-based approach for determining how SOL exceedances identified as part of Real-time monitoring and Real-time Assessments must be communicated and if so, the timeframe that communication must occur. The approach shall include:","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30658,"FAC-011-4","R7.1.",null,"A requirement that the following SOL exceedances will always be communicated, within a timeframe identified by the Reliability Coordinator.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30659,"FAC-011-4","R7.1.1.",null,"IROL exceedances;","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30660,"FAC-011-4","R7.1.2.",null,"SOL exceedances of stability limits;","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30661,"FAC-011-4","R7.1.3.",null,"Post Contingency SOL exceedances that are identified to have a validated risk of instability, Cascading, and uncontrolled separation;","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30662,"FAC-011-4","R7.1.4.",null,"Pre-Contingency SOL exceedances of Facility Ratings; and","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30663,"FAC-011-4","R7.1.5.",null,"Pre-Contingency SOL exceedances of normal minimum System Voltage Limits.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30664,"FAC-011-4","R7.2.",null,"A requirement that the following SOL exceedances must be communicated, if not resolved within 30 minutes, within a timeframe identified by the Reliability Coordinator.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30665,"FAC-011-4","R7.2.1.",null,"Post-Contingency SOL exceedances of Facility Ratings and emergency System Voltage Limits, and","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30666,"FAC-011-4","R7.2.2.",null,"Pre-Contingency SOL exceedances of normal maximum System Voltage Limits.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30667,"FAC-011-4","R8.",null,"Each Reliability Coordinator shall include in its SOL methodology:","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30668,"FAC-011-4","R8.1.",null,"A description of how to identify the subset of SOLs that qualify as Interconnection Reliability Operating Limits (IROLs).","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30669,"FAC-011-4","R8.2.",null,"Criteria for determining when exceeding a SOL qualifies as exceeding an IROL and criteria for developing any associated IROL Tv.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30670,"FAC-011-4","R9.",null,"Each Reliability Coordinator shall provide its SOL methodology to:","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[30671,"FAC-011-4","R9.1.",null,"Each Reliability Coordinator that requests and indicates it has a reliability-related need within 30 days of a request.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[30672,"FAC-011-4","R9.2.",null,"Each of the following entities prior to the effective date of the SOL methodology:","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[30673,"FAC-011-4","R9.2.1.",null,"Each adjacent Reliability Coordinator within the same; Interconnection;","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[30674,"FAC-011-4","R9.2.2.",null,"Each Planning Coordinator and Transmission Planner that is responsible for planning any portion of the Reliability Coordinator Area;","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[30675,"FAC-011-4","R9.2.3.",null,"Each Transmission Operator within its Reliability Coordinator Area; and","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[30676,"FAC-011-4","R9.2.4.",null,"Each Reliability Coordinator that has requested to receive updates and indicated it had a reliability-related need.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[26811,"FAC-013-2","R1.",null,"Each Planning Coordinator shall have a documented methodology it uses to perform an annual assessment of Transfer Capability in the Near-Term Transmission Planning Horizon (Transfer Capability methodology). The Transfer Capability methodology shall include, at a minimum, the following information:","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[26812,"FAC-013-2","R1.1.",null,"Criteria for the selection of the transfers to be assessed.","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","PC","No",false,null,false]
[26813,"FAC-013-2","R1.2.",null,"A statement that the assessment shall respect known System Operating Limits (SOLs).","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","PC","No",false,null,false]
[26814,"FAC-013-2","R1.3.",null,"A statement that the assumptions and criteria used to perform the assessment are consistent with the Planning Coordinator’s planning practices.","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","PC","No",false,null,false]
[26815,"FAC-013-2","R1.4.",null,"A description of how each of the following assumptions and criteria used in performing the assessment are addressed:","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","PC","No",false,null,false]
[26816,"FAC-013-2","R1.4.1.",null,"Generation dispatch, including but not limited to long term planned outages, additions and retirements.","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","PC","No",false,null,false]
[26817,"FAC-013-2","R1.4.2.",null,"Transmission system topology, including but not limited to long term planned Transmission outages, additions, and retirements.","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","PC","No",false,null,false]
[26818,"FAC-013-2","R1.4.3.",null,"System demand.","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","PC","No",false,null,false]
[26819,"FAC-013-2","R1.4.4.",null,"Current approved and projected Transmission uses.","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","PC","No",false,null,false]
[26820,"FAC-013-2","R1.4.5.",null,"Parallel path (loop flow) adjustments.","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","PC","No",false,null,false]
[26821,"FAC-013-2","R1.4.6.",null,"Contingencies","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","PC","No",false,null,false]
[26822,"FAC-013-2","R1.4.7.",null,"Monitored Facilities.","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","PC","No",false,null,false]
[26823,"FAC-013-2","R1.5.",null,"A description of how simulations of transfers are performed through the adjustment of generation, Load or both.","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","PC","No",false,null,false]
[26824,"FAC-013-2","R2.",null,"Each Planning Coordinator shall issue its Transfer Capability methodology, and any revisions to the Transfer Capability methodology, to the following entities subject to the following:","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[26825,"FAC-013-2","R2.1.",null,"Distribute to the following prior to the effectiveness of such revisions:","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","PC","No",false,null,false]
[26826,"FAC-013-2","R2.1.1.",null,"Each Planning Coordinator adjacent to the Planning Coordinator’s Planning Coordinator area or overlapping the Planning Coordinator’s area.","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","PC","No",false,null,false]
[26827,"FAC-013-2","R2.1.2.",null,"Each Transmission Planner within the Planning Coordinator’s Planning Coordinator area.","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","PC","No",false,null,false]
[26828,"FAC-013-2","R2.2.",null,"Distribute to each functional entity that has a reliability-related need for the Transfer Capability methodology and submits a request for that methodology within 30 calendar days of receiving that written request.","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","PC","No",false,null,false]
[26829,"FAC-013-2","R4.",null,"During each calendar year, each Planning Coordinator shall conduct simulations and document an assessment based on those simulations in accordance with its Transfer Capability methodology for at least one year in the Near-Term Transmission Planning Horizon.","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[26830,"FAC-013-2","R5.",null,"Each Planning Coordinator shall make the documented Transfer Capability assessment results available within 45 calendar days of the completion of the assessment to the recipients of its Transfer Capability methodology pursuant to Requirement R2, Parts 2.1 and Part 2.2. However, if a functional entity that has a reliability related need for the results of the annual assessment of the Transfer Capabilities makes a written request for such an assessment after the completion of the assessment, the Planning Coordinator shall make the documented Transfer Capability assessment results available to that entity within 45 calendar days of receipt of the request","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[26831,"FAC-013-2","R6.",null,"If a recipient of a documented Transfer Capability assessment requests data to support the assessment results, the Planning Coordinator shall provide such data to that entity within 45 calendar days of receipt of the request. The provision of such data shall be subject to the legal and regulatory obligations of the Planning Coordinator’s area regarding the disclosure of confidential and/or sensitive information.","2013-04-01","2020-12-24","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Tools and Applications","LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[26832,"FAC-014-2","R1.","YES","The Reliability Coordinator shall ensure that SOLs, including Interconnection Reliability Operating Limits (IROLs), for its Reliability Coordinator Area are established and that the SOLs (including Interconnection Reliability Operating Limits) are consistent with its SOL Methodology.","2008-11-16",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26833,"FAC-014-2","R1.","YES","The Reliability Coordinator shall ensure that SOLs, including Interconnection Reliability Operating Limits (IROLs), for its Reliability Coordinator Area are established and that the SOLs (including Interconnection Reliability Operating Limits) are consistent with its SOL Methodology.","2008-11-16",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26835,"FAC-014-2","R2.","YES","The Transmission Operator shall establish SOLs (as directed by its Reliability Coordinator) for its portion of the Reliability Coordinator Area that are consistent with its Reliability Coordinator’s SOL Methodology.","2008-11-16",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC","No",true,null,false]
[26834,"FAC-014-2","R2.","YES","The Transmission Operator shall establish SOLs (as directed by its Reliability Coordinator) for its portion of the Reliability Coordinator Area that are consistent with its Reliability Coordinator’s SOL Methodology.","2008-11-16",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC","No",true,null,false]
[26836,"FAC-014-2","R3.","YES","The Planning Authority shall establish SOLs, including IROLs, for its Planning\nAuthority Area that are consistent with its SOL Methodology.","2008-11-16",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PA","No",false,null,false]
[26837,"FAC-014-2","R3.","YES","The Planning Authority shall establish SOLs, including IROLs, for its Planning\nAuthority Area that are consistent with its SOL Methodology.","2008-11-16",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PA","No",false,null,false]
[26838,"FAC-014-2","R4.","YES","The Transmission Planner shall establish SOLs, including IROLs, for its Transmission Planning Area that are consistent with its Planning Authority’s SOL Methodology.","2008-11-16",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP","No",false,null,false]
[26839,"FAC-014-2","R4.","YES","The Transmission Planner shall establish SOLs, including IROLs, for its Transmission Planning Area that are consistent with its Planning Authority’s SOL Methodology.","2008-11-16",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP","No",false,null,false]
[26840,"FAC-014-2","R5.",null,"The Reliability Coordinator, Planning Authority and Transmission Planner shall each provide its SOLs and IROLs to those entities that have a reliability-related need for those limits and provide a written request that includes a schedule for delivery of those limits as follows:","2008-11-16",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, RC, PA","No",false,null,false]
[26841,"FAC-014-2","R5.1.",null,"The Reliability Coordinator shall provide its SOLs (including the subset of SOLs that are IROLs) to adjacent Reliability Coordinators and Reliability Coordinators who indicate a reliability-related need for those limits, and to the Transmission Operators, Transmission Planners, Transmission Service Providers and Planning Authorities within its Reliability Coordinator Area. For each IROL, the Reliability Coordinator shall provide the following\nsupporting information:","2008-11-16",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26843,"FAC-014-2","R5.1.1.","YES","Identification and status of the associated Facility (or group of Facilities) that is (are) critical to the derivation of the IROL.","2008-11-16",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26842,"FAC-014-2","R5.1.1.","YES","Identification and status of the associated Facility (or group of Facilities) that is (are) critical to the derivation of the IROL.","2008-11-16",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[26844,"FAC-014-2","R5.1.2.",null,"The value of the IROL and its associated Tv.","2008-11-16",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[26893,"FAC-014-2","R5.1.3.",null,"The associated Contingency(ies).","2008-11-16",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[26894,"FAC-014-2","R5.1.4.",null,"The type of limitation represented by the IROL (e.g., voltage collapse, angular stability).","2008-11-16",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[26895,"FAC-014-2","R5.2.",null,"The Transmission Operator shall provide any SOLs it developed to its Reliability Coordinator and to the Transmission Service Providers that share its portion of the Reliability Coordinator Area.","2008-11-16",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26896,"FAC-014-2","R5.3.",null,"The Planning Authority shall provide its SOLs (including the subset of SOLs that are IROLs) to adjacent Planning Authorities, and to Transmission Planners, Transmission Service Providers, Transmission Operators and Reliability Coordinators that work within its Planning Authority Area.","2008-11-16",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","PA","No",false,null,false]
[26897,"FAC-014-2","R5.4.",null,"The Transmission Planner shall provide its SOLs (including the subset of SOLs that are IROLs) to its Planning Authority, Reliability Coordinators, Transmission Operators, and Transmission Service Providers that work within its Transmission Planning Area and to adjacent Transmission Planners.","2008-11-16",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP","No",false,null,false]
[26898,"FAC-014-2","R6.",null,"The Planning Authority shall identify the subset of multiple contingencies (if any), from Reliability Standard TPL-003 which result in stability limits.","2008-11-16",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","PA","No",false,null,false]
[26899,"FAC-014-2","R6.1.",null,"The Planning Authority shall provide this list of multiple contingencies and the associated stability limits to the Reliability Coordinators that monitor the facilities associated with these contingencies and limits.","2008-11-16",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","PA","No",false,null,false]
[26900,"FAC-014-2","R6.2.",null,"If the Planning Authority does not identify any stability-related multiple contingencies, the Planning Authority shall so notify the Reliability Coordinator.","2008-11-16",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PA","No",false,null,false]
[30730,"FAC-014-3","R1.","YES","Each Reliability Coordinator shall establish Interconnection Reliability Operating Limits (IROLs) for its Reliability Coordinator Area in accordance with its System Operating Limit methodology (SOL methodology).","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[30731,"FAC-014-3","R1.","YES","Each Reliability Coordinator shall establish Interconnection Reliability Operating Limits (IROLs) for its Reliability Coordinator Area in accordance with its System Operating Limit methodology (SOL methodology).","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[30733,"FAC-014-3","R2.","YES","Each Transmission Operator shall establish System Operating Limits SOLs for its portion of the Reliability Coordinator Area in accordance with its Reliability Coordinator's SOL methodology.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",true,null,false]
[30732,"FAC-014-3","R2.","YES","Each Transmission Operator shall establish System Operating Limits SOLs for its portion of the Reliability Coordinator Area in accordance with its Reliability Coordinator's SOL methodology.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",true,null,false]
[30734,"FAC-014-3","R3.","YES","Each Transmission Operator shall provide its SOLs to its Reliability Coordinator.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[30735,"FAC-014-3","R3.","YES","Each Transmission Operator shall provide its SOLs to its Reliability Coordinator.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[30736,"FAC-014-3","R4.","YES","Each Reliability Coordinator shall establish stability limits when an identified instability impacts adjacent Reliability Coordinator Areas or more than one Transmission Operator in its Reliability Coordinator Area in accordance with its SOL methodology.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[30737,"FAC-014-3","R4.","YES","Each Reliability Coordinator shall establish stability limits when an identified instability impacts adjacent Reliability Coordinator Areas or more than one Transmission Operator in its Reliability Coordinator Area in accordance with its SOL methodology.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[30738,"FAC-014-3","R5.",null,"Each Reliability Coordinator shall provide:","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[30739,"FAC-014-3","R5.1.",null,"Each Planning Coordinator and each Transmission Planner within its Reliability Coordinator Area, the SOLs for its Reliability Coordinator Area (including the subset of SOLs that are IROLs) at least once every twelve calendar months. [Time Horizon: Operati","2024-04-01",null,"Future Effective",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, TP, RC, PC","No",true,null,false]
[30740,"FAC-014-3","R5.2.",null,"Each impacted Planning Coordinator and each impacted Transmission Planner within its Reliability Coordinator Area, the following information for each established stability limit and each established IROL at least once every twelve calendar months: [Time H","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[30741,"FAC-014-3","R5.2.1.",null,"The value of the stability limit or IROL;","2024-04-01",null,"Future Effective",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, TP, RC, PC","No",false,null,false]
[30742,"FAC-014-3","R5.2.2.","YES","Identification of the Facilities that are critical to the derivation of the stability limit or the IROL;","2024-04-01",null,"Future Effective",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, TP, RC, PC","No",false,null,false]
[30743,"FAC-014-3","R5.2.2.","YES","Identification of the Facilities that are critical to the derivation of the stability limit or the IROL;","2024-04-01",null,"Future Effective",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, TP, RC, PC","No",false,null,false]
[30744,"FAC-014-3","R5.2.3.",null,"The associated IROL Tv for any IROL;","2024-04-01",null,"Future Effective",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, TP, RC, PC","No",false,null,false]
[30745,"FAC-014-3","R5.2.4.",null,"The associated critical Contingency(ies);","2024-04-01",null,"Future Effective",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, TP, RC, PC","No",false,null,false]
[30746,"FAC-014-3","R5.2.5.",null,"A description of system conditions associated with the stability limit or IROL; and","2024-04-01",null,"Future Effective",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, TP, RC, PC","No",false,null,false]
[30747,"FAC-014-3","R5.2.6.",null,"The type of limitation represented by the stability limit or IROL (e.g., voltage collapse, angular stability).","2024-04-01",null,"Future Effective",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, TP, RC, PC","No",false,null,false]
[30748,"FAC-014-3","R5.3.",null,"Each impacted Transmission Operator within its Reliability Coordinator Area, the value of the stability limits established pursuant to Requirement R4 and each IROL established pursuant to Requirement R1, in an agreed upon time frame necessary for inclusio","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[30749,"FAC-014-3","R5.4.",null,"Each impacted Transmission Operator within its Reliability Coordinator Area, the information identified in Requirement R5 Parts 5.2.2 – 5.2.6 for each established stability limit and each established IROL, and any updates to that information within an agr","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[30750,"FAC-014-3","R5.5.",null,"Each requesting Transmission Operator within its Reliability Coordinator Area, requested SOL information for its Reliability Coordinator Area, on a mutually agreed upon schedule. [Time Horizon: Operations Planning]","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[30751,"FAC-014-3","R5.6.",null,"Each impacted Generator Owner or Transmission Owner, within its Reliability Coordinator Area, with a list of their Facilities that have been identified as critical to the derivation of an IROL and its associated critical contingencies at least once every","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[30752,"FAC-014-3","R6.",null,"Each Planning Coordinator and each Transmission Planner shall implement a documented process to use Facility Ratings, System steady-state voltage limits and stability criteria in its Planning Assessment of Near-Term Transmission Planning Horizon that are","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[30753,"FAC-014-3","R7.",null,"Each Planning Coordinator and each Transmission Planner shall annually communicate the following information for Corrective Action Plans developed to address any instability identified in its Planning Assessment of the Near-Term Transmission Planning Hori","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[30754,"FAC-014-3","R7.1.",null,"The Corrective Action Plan developed to mitigate the identified instability, including any automatic control or operator-assisted actions (such as Remedial Action Schemes, under voltage load shedding, or any Operating Procedures);","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[30755,"FAC-014-3","R7.2.",null,"The type of instability addressed by the Corrective Action Plan (e.g. steady-state and/or transient voltage instability, angular instability including generating unit loss of synchronism and/or unacceptable damping);","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[30756,"FAC-014-3","R7.3.",null,"The associated stability criteria violation requiring the Corrective Action Plan (e.g. violation of transient voltage response criteria or damping rate criteria);","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[30757,"FAC-014-3","R7.4.",null,"The planning event Contingency(ies) associated with the identified instability requiring the Corrective Action Plan;","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[30758,"FAC-014-3","R7.5.",null,"The System conditions and Facilities associated with the identified instability requiring the Corrective Action Plan.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[30759,"FAC-014-3","R8.",null,"Each Planning Coordinator and each Transmission Planner shall annually communicate to each impacted Transmission Owner and Generation Owner a list of their Facilities that comprise the planning event Contingency(ies) that would cause instability, Cascadin","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TP, RC, PC","No",false,null,false]
[26901,"INT-004-3.1","R1.","12/14/2020","Each Purchasing-Selling Entity that secures energy to serve Load via a Dynamic Schedule or Pseudo-Tie shall ensure that a Request for Interchange is submitted as an on-time1 Arranged Interchange to the Sink Balancing Authority for that Dynamic\nSchedule or Pseudo-Tie, unless the information about the Pseudo-Tie is included in congestion management procedure(s) via an alternate method. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning, Same-day Operations]","2015-01-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PSE","No",false,null,false]
[26902,"INT-004-3.1","R2.","12/14/2020","The Purchasing-Selling Entity that submits a Request for Interchange in accordance with Requirement R1 shall ensure the Confirmed Interchange associated with that Dynamic Schedule or Pseudo-Tie is updated for future hours in order to support\ncongestion management procedures if any one of the following occurs: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning, Same Day Operations, Real Time Operations]","2015-01-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PSE","No",false,null,false]
[26903,"INT-004-3.1","R2.1.","12/14/2020","For Confirmed Interchange greater than 250 MW for the last hour, the actual hourly integrated energy deviates from the Confirmed Interchange by more than 10% for that hour and that deviation is expected to persist.","2015-01-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PSE","No",false,null,false]
[26904,"INT-004-3.1","R2.2.","12/14/2020","For Confirmed Interchange less than or equal to 250 MW for the last hour, the actual hourly integrated energy deviates from the Confirmed Interchange by more than 25 MW for that hour and that deviation is expected to persist.","2015-01-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PSE","No",false,null,false]
[26905,"INT-004-3.1","R2.3.","12/14/2020","The Purchasing-Selling Entity receives notification from a Reliability Coordinator or Transmission Operator to update the Confirmed Interchange.","2015-01-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PSE","No",false,null,false]
[26906,"INT-004-3.1","R3.","12/14/2020","Each Balancing Authority shall only implement or operate a Pseudo-Tie that is included in the NAESB Electric Industry Registry publication in order to support congestion management procedures. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2015-01-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[26907,"INT-006-4","R1.",null,"Each Balancing Authority shall approve or deny each on-time Arranged Interchange or emergency Arranged Interchange that it receives and shall do so prior to the expiration of the time period defined in Attachment 1, Column B. [Violation Risk Factor: Lower]\n[Time Horizon: Operations Planning, Same-day Operations, Real-time Operations]","2015-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[26908,"INT-006-4","R1.1.",null,"Each Source and Sink Balancing Authority shall deny the Arranged Interchange or curtail Confirmed Interchange if it does not expect to be capable of supporting the magnitude of the Interchange, including ramping, throughout the duration of the Arranged Interchange.","2015-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[26909,"INT-006-4","R1.2.",null,"Each Balancing Authority shall deny the Arranged Interchange or curtail Confirmed Interchange if the Scheduling Path (proper connectivity of Adjacent Balancing Authorities) between it and its Adjacent Balancing Authorities is invalid.","2015-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[26910,"INT-006-4","R2.",null,"Each Transmission Service Provider shall approve or deny each on-time Arranged Interchange or emergency Arranged Interchange that it receives and shall do so prior to the expiration of the time period defined in Attachment 1, Column B. [Violation\nRisk Factor: Lower] [Time Horizon: Operations Planning, Same-day Operations, Real-time Operations]","2015-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[26911,"INT-006-4","R2.1.",null,"Each Transmission Service Provider shall deny the Arranged Interchange or curtail Confirmed Interchange if the transmission path (proper connectivity of adjacent Transmission Service Providers) between it and its adjacent Transmission Service Providers is invalid.","2015-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[26912,"INT-006-4","R3.",null,"The Source Balancing Authority and the Sink Balancing Authority receiving a Reliability Adjustment Arranged Interchange shall approve or deny it prior to the expiration of the time period defined in Attachment 1, Column B. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning, Same-day Operations, Real-time Operations]","2015-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[26913,"INT-006-4","R3.1.",null,"If a Balancing Authority denies a Reliability Adjustment Arranged Interchange, the Balancing Authority must communicate that fact to its Reliability Coordinator no more than 10 minutes after the denial.","2015-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[26914,"INT-006-4","R4.",null,"Each Sink Balancing Authority shall confirm that none of the following conditions exist prior to transitioning an Arranged Interchange to Confirmed Interchange: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning, Same-day\nOperations, Real-time Operations]\n It is a Reliability Adjustment Arranged Interchange, the time period specified in Attachment 1, Column B has elapsed, and the Source Balancing Authority or the Sink Balancing Authority associated with the Arranged Interchange has not communicated its approval of the transition.\n It is not a Reliability Adjustment Arranged Interchange, the time period specified in Attachment 1, Column B, has elapsed, and not all Balancing Authorities and Transmission Service Providers associated with the Arranged Interchange have communicated their approval of the transition.\n It is not a Reliability Adjustment Arranged Interchange, the time period specified in Attachment 1, Column B, has elapsed, and any entity associated with the Arranged Interchange has communicated its denial of the transition.","2015-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[26915,"INT-006-4","R5.",null,"For each Arranged Interchange that is transitioned to Confirmed Interchange, the Sink Balancing Authority shall notify the following entities of the on-time Confirmed Interchange such that the notification is delivered in time to be incorporated into scheduling systems prior to ramp start as specified in Attachment 1, Column D: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning, Same-day Operations, Real-time Operations]","2015-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[26916,"INT-006-4","R5.1.",null,"The Source Balancing Authority,","2015-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[26917,"INT-006-4","R5.2.",null,"Each Intermediate Balancing Authority,","2015-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[26918,"INT-006-4","R5.3.",null,"Each Reliability Coordinator associated with each Balancing Authority included in the Arranged Interchange,","2015-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[26919,"INT-006-4","R5.4.",null,"Each Transmission Service Provider included in the Arranged Interchange, and","2015-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[26920,"INT-006-4","R5.5.",null,"Each Purchasing Selling Entity included in the Arranged Interchange.","2015-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[30215,"INT-006-5","R1.",null,"Each Balancing Authority shall approve or deny each on-time Arranged Interchange or\r\nemergency Arranged Interchange that it receives and shall do so prior to the\r\nexpiration of the time period defined in Attachment 1, Column B. [Violation Risk\r\nFactor: Lower] [Time Horizon: Operations Planning, Same-day Operations, Real-time\r\nOperations]","2021-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP, BA","No",false,null,false]
[30216,"INT-006-5","R1.1.",null,"Each Source and Sink Balancing Authority shall deny the Arranged Interchange or curtail Confirmed Interchange if it does not expect to be capable of supporting the magnitude of the Interchange, including ramping, throughout the duration of the Arranged Interchange.","2021-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP, BA","No",false,null,false]
[30217,"INT-006-5","R1.2.",null,"Each Balancing Authority shall deny the Arranged Interchange or curtail Confirmed Interchange if the Scheduling Path (proper connectivity of Adjacent Balancing Authorities) between it and its Adjacent Balancing Authorities is invalid.","2021-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP, BA","No",false,null,false]
[30218,"INT-006-5","R2.",null,"Each Transmission Service Provider shall approve or deny each on-time Arranged Interchange or emergency Arranged Interchange that it receives and shall do so prior to the expiration of the time period defined in Attachment 1, Column B. [Violation\nRisk Factor: Lower] [Time Horizon: Operations Planning, Same-day Operations, Real-time Operations]","2021-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP, BA","No",false,null,false]
[30219,"INT-006-5","R2.1.",null,"Each Transmission Service Provider shall deny the Arranged Interchange or curtail Confirmed Interchange if the transmission path (proper connectivity of adjacent Transmission Service Providers) between it and its adjacent Transmission Service Providers is invalid.","2021-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP, BA","No",false,null,false]
[30220,"INT-006-5","R3.",null,"The Source Balancing Authority and the Sink Balancing Authority receiving a Reliability Adjustment Arranged Interchange shall approve or deny it prior to the expiration of the time period defined in Attachment 1, Column B. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning, Same-day Operations, Real-time Operations]","2021-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP, BA","No",false,null,false]
[30221,"INT-006-5","R3.1.",null,"Reserved","2021-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP, BA","No",false,null,false]
[30222,"INT-006-5","R4.",null,"Reserved","2021-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP, BA","No",false,null,false]
[30223,"INT-006-5","R5.",null,"Reserved","2021-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP, BA","No",false,null,false]
[30224,"INT-006-5","R5.1.",null,"The Source Balancing Authority,","2021-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP, BA","No",false,null,false]
[30225,"INT-006-5","R5.2.",null,"Each Intermediate Balancing Authority,","2021-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP, BA","No",false,null,false]
[30226,"INT-006-5","R5.3.",null,"Each Reliability Coordinator associated with each Balancing Authority included in the Arranged Interchange,","2021-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP, BA","No",false,null,false]
[30227,"INT-006-5","R5.4.",null,"Each Transmission Service Provider included in the Arranged Interchange, and","2021-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP, BA","No",false,null,false]
[30228,"INT-006-5","R5.5.",null,"Each Purchasing Selling Entity included in the Arranged Interchange.","2021-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP, BA","No",false,null,false]
[26845,"INT-009-2.1","R1.",null,"Each Balancing Authority shall agree with each of its Adjacent Balancing Authorities that its Composite Confirmed Interchange with that Adjacent Balancing Authority, at mutually agreed upon time intervals, excluding Dynamic Schedules and Pseudo-Ties\nand including any Interchange per INT-010-2 not yet captured in the Composite Confirmed Interchange, is: [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]","2015-01-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[26846,"INT-009-2.1","R1.1.",null,"Identical in magnitude to that of the Adjacent Balancing Authority, and","2015-01-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[26847,"INT-009-2.1","R1.2.",null,"Opposite in sign or direction to that of the Adjacent Balancing Authority.","2015-01-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[26848,"INT-009-2.1","R2.",null,"The Attaining Balancing Authority and the Native Balancing Authority shall use a dynamic value emanating from an agreed upon common source to account for the Pseudo-Tie in the Actual Net Interchange (NIA) term of their respective control ACE\n(or alternate control process). [Violation Risk Factor: Medium] [Time Horizon: Realtime Operations]","2015-01-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[26849,"INT-009-2.1","R3.",null,"Each Balancing Authority in whose area the high-voltage direct current tie is controlled shall coordinate the Confirmed Interchange prior to its implementation with the Transmission Operator of the high-voltage direct current tie. [Violation Risk Factor:\nMedium] [Time Horizon: Real-time Operations, Operations Planning]","2015-01-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[30229,"INT-009-3","R1.",null,"Each Balancing Authority shall agree with each of its Adjacent Balancing Authorities\r\nthat its Composite Confirmed Interchange with that Adjacent Balancing Authority, at\r\nmutually agreed upon time intervals, excluding Dynamic Schedules and Pseudo‐Ties\r\nand including any Interchange not yet captured in the Composite Confirmed\r\nInterchange, is: [Violation Risk Factor: Medium] [Time Horizon: Real‐time Operations]","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[30230,"INT-009-3","R1.1.",null,"Identical in magnitude to that of the Adjacent Balancing Authority, and","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[30231,"INT-009-3","R1.2.",null,"Opposite in sign or direction to that of the Adjacent Balancing Authority.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[30232,"INT-009-3","R2.",null,"Reserved","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[30233,"INT-009-3","R3.",null,"Each Balancing Authority in whose area the high-voltage direct current tie is controlled shall coordinate the Confirmed Interchange prior to its implementation with the Transmission Operator of the high-voltage direct current tie. [Violation Risk Factor:\nMedium] [Time Horizon: Real-time Operations, Operations Planning]","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[26850,"INT-010-2.1","R1.",null,"The Balancing Authority that experiences a loss of resources covered by an energy sharing agreement or other reliability needs covered by an energy sharing agreement shall ensure that a Request for Interchange (RFI) is submitted with a start time no more\nthan 60 minutes beyond the resource loss. If the use of the energy sharing agreement does not exceed 60 minutes from the time of the resource loss, no RFI is required. [Violation Risk Factor: Lower] [Time Horizon: Real Time Operations]","2015-01-01","2020-12-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[26851,"INT-010-2.1","R2.",null,"Each Sink Balancing Authority shall ensure that a Reliability Adjustment Arranged Interchange reflecting a modification is submitted within 60 minutes of the start of the modification if a Reliability Coordinator directs the modification of a Confirmed Interchange or Implemented Interchange for actual or anticipated reliability-related reasons. [Violation Risk Factor: Lower] [Time Horizon: Real Time Operations]","2015-01-01","2020-12-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[26852,"INT-010-2.1","R3.",null,"Each Sink Balancing Authority shall ensure that a Request for Interchange is submitted reflecting that Interchange Schedule within 60 minutes of the start of the scheduled Interchange if a Reliability Coordinator directs the scheduling of Interchange for actual\nor anticipated reliability-related reasons. [Violation Risk Factor: Lower] [Time Horizon: Real Time Operations]","2015-01-01","2020-12-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[26921,"INT-011-1.1","R1.",null,"Each Load-Serving Entity that uses Point to Point Transmission Service for intra-Balancing Authority Area transfers shall submit a Request for Interchange unless the information about intra-Balancing Authority transfers is included in congestion management procedure(s) via an alternate method. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning, Same-day Operations]","2015-01-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","LSE","Yes",false,null,false]
[26931,"IRO-001-2","R1.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","RRO","No",false,null,false]
[26932,"IRO-001-2","R2.",null,"The Reliability Coordinator shall comply with a regional reliability plan approved by the NERC Operating Committee.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26933,"IRO-001-2","R3.",null,"The Reliability Coordinator shall have clear decision-making authority to act and to direct actions to be taken by Transmission Operators, Balancing Authorities, Generator Operators, Transmission Service Providers, Load-Serving Entities, and Purchasing-Selling 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.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26934,"IRO-001-2","R4.",null,"Reliability Coordinators that delegate tasks to other entities shall have formal operating 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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26935,"IRO-001-2","R5.",null,"The Reliability Coordinator shall list within its reliability plan all entities to which the Reliability Coordinator has delegated required tasks.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[26936,"IRO-001-2","R6.",null,"The Reliability Coordinator shall verify that all delegated tasks are carried out by NERC-certified Reliability Coordinator operating personnel.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26937,"IRO-001-2","R7.",null,"Transmission Operators, Balancing Authorities, Generator Operators, Transmission 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.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TSP, TOP, PSE, LSE, GOP, BA","Yes",true,null,true]
[26938,"IRO-001-2","R8.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26939,"IRO-001-3","R1.",null,"Each Reliability Coordinator shall have the authority to act or direct others to act (which could include issuing Reliability Directives) to prevent identified events or mitigate the magnitude or duration of actual events that result in an Emergency or Adverse Reliability Impact. [Violation Risk Factor: High][Time Horizon: Real-time Operations, Same Day Operations and Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26940,"IRO-001-3","R2.",null,"Each Transmission Operator, Balancing Authority, Generator Operator, and Distribution Provider shall comply with its Reliability Coordinator’s direction unless compliance with the direction cannot be physically implemented or unless such actions would violate safety, equipment, regulatory, or statutory requirements. [Violation Risk Factor: High] [Time Horizon: Real-time Operations, Same Day Operations and Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[26941,"IRO-001-3","R3.",null,"Each Transmission Operator, Balancing Authority, Generator Operator, and Distribution Provider shall inform its Reliability Coordinator upon recognition of its inability to perform as directed in accordance with Requirement R2. [Violation Risk Factor:\nHigh] [Time Horizon: Real-time Operations, Same Day Operations and Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[26942,"IRO-001-4","R1.",null,"Each Reliability Coordinator shall act to address the reliability of its Reliability Coordinator Area via direct actions or by issuing Operating Instructions. [Violation Risk Factor: High][Time Horizon: Same-Day Operations, Real-time Operations]","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26943,"IRO-001-4","R2.",null,"Each Transmission Operator, Balancing Authority, Generator Operator, and Distribution Provider shall comply with its Reliability Coordinator’s Operating Instructions unless compliance with the Operating Instructions cannot be physically implemented or unless such actions would violate safety, equipment, regulatory, or statutory requirements. [Violation Risk Factor: High] [Time Horizon: Same-Day Operations, Real-time Operations]","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",true,"Market Manual (MM) 7.1 System Operating Procedures specifies the communications protocol between market participants and the IESO.                                                                   The IESO-Hydro One Operating Agreement authorizes the IESO to direct the operation of the IESO-controlled grid. The Operating Agreement requires Hydro one to promptly execute the IESO’s direction.                                                                                                          Section 3.2.1, Chap 5 of the Market Rules: The IESO shall direct the operations of the IESO-controlled grid pursuant to the provisions of all applicable operating agreements and shall maintain the reliability of the IESO-controlled grid. The IESO's responsibilities in this regard shall include, but are not limited to, the monitoring of, and the issuing of orders, directions or instructions to dispatch generation, dispatchable loads, distribution facilities and transmission facilities on the IESO-controlled grid.                                                           Sections 3.5 through 3.7 of Chap 5 of the Market Rules provides for the obligations of the market participants, the obligation to inform the IESO if they are not able to follow the directives of the IESO, and the conditions under which they are allowed to do.",true]
[26944,"IRO-001-4","R3.",null,"Each Transmission Operator, Balancing Authority, Generator Operator, and Distribution Provider shall inform its Reliability Coordinator of its inability to perform the Operating Instruction issued by its Reliability Coordinator in Requirement R1.\n[Violation Risk Factor: High] [Time Horizon: Same-Day Operations, Real-time Operations]","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",true,null,true]
[26953,"IRO-002-3","R1.",null,"Each Reliability Coordinator shall provide its System Operators with the authority to approve, deny or cancel planned outages of its own analysis tools.",null,null,"Never Came Into Effect in Ontario","Documentations, Policies and Procedures; Monitoring; Tools and Applications","MEDIUM",null,"N/A","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[26954,"IRO-002-3","R2.",null,"Each Reliability Coordinator shall have procedures in place to mitigate the effects of analysis tool outages.",null,null,"Never Came Into Effect in Ontario","Documentations, Policies and Procedures; Monitoring; Tools and Applications","MEDIUM",null,"N/A","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[26959,"IRO-002-5","R1.",null,"Each Reliability Coordinator shall have data exchange capabilities with its Balancing Authorities and Transmission Operators, and with other entities it deems necessary, for it to perform its Operational Planning Analyses. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2018-01-01","2019-12-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26960,"IRO-002-5","R2.",null,"Each Reliability Coordinator shall have data exchange capabilities, with redundant and diversely routed data exchange infrastructure within the Reliability Coordinator's primary Control Center, for the exchange of Real-time data with its Balancing Authorities and Transmission Operators, and with other entities it deems necessary, for performing its Real-time monitoring and Real-time Assessments. [Violation Risk Factor: High] [Time Horizon: Same-Day Operations, Real-time Operations]","2018-01-01","2019-12-31","Retired",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26961,"IRO-002-5","R3.",null,"Each Reliability Coordinator shall test its primary Control Center data exchange capabilities specified in Requirement R2 for redundant functionality at least once every 90 calendar days. If the test is unsuccessful, the Reliability Coordinator shall initiate action within two hours to restore redundant functionality. [Violation Risk Factor: Medium ] [Time Horizon: Operations Planning]","2018-01-01","2019-12-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26962,"IRO-002-5","R4.",null,"Each Reliability Coordinator shall provide its System Operators with the authority to approve planned outages and maintenance of its telecommunication, monitoring and analysis capabilities. [Violation Risk Factor: High] [Time Horizon: Operations Planning, Same-Day Operations, Real-time Operations]","2018-01-01","2019-12-31","Retired",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26963,"IRO-002-5","R5.",null,"Each Reliability Coordinator shall monitor Facilities, the status of Remedial Action Schemes, and non-BES facilities identified as necessary by the Reliability Coordinator, within its Reliability Coordinator Area and neighboring Reliability Coordinator Areas to identify any System Operating Limit exceedances and to determine any Interconnection Reliability Operating Limit exceedances within its Reliability Coordinator Area. [Violation Risk Factor: High] [Time Horizon: Real-Time Operations]","2018-01-01","2019-12-31","Retired",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26964,"IRO-002-5","R6.",null,"Each Reliability Coordinator shall have monitoring systems that provide information utilized by the Reliability Coordinator’s operating personnel, giving particular emphasis to alarm management and awareness systems, automated data transfers, and synchronized information systems, over a redundant infrastructure. [Violation Risk Factor: High] [Time Horizon: Real-time Operations]","2018-01-01","2019-12-31","Retired",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[29887,"IRO-002-6","R1.",null,"Each Reliability Coordinator shall have data exchange capabilities with its Balancing Authorities and Transmission Operators, and with other entities it deems necessary, for it to perform its Operational Planning Analyses. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2020-01-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[29888,"IRO-002-6","R2.",null,"Each Reliability Coordinator shall have data exchange capabilities, with redundant and diversely routed data exchange infrastructure within the Reliability Coordinator's primary Control Center, for the exchange of Real-time data with its Balancing Authorities and Transmission Operators, and with other entities it deems necessary, for performing its Real-time monitoring and Real-time Assessments. [Violation Risk Factor: High] [Time Horizon: Same-Day Operations, Real-time Operations]","2020-01-01","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[29889,"IRO-002-6","R3.",null,"Each Reliability Coordinator shall test its primary Control Center data exchange capabilities specified in Requirement R2 for redundant functionality at least once every 90 calendar days. If the test is unsuccessful, the Reliability Coordinator shall initiate action within two hours to restore redundant functionality. [Violation Risk Factor: Medium ] [Time Horizon: Operations Planning]","2020-01-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[29890,"IRO-002-6","R4.",null,"Each Reliability Coordinator shall provide its System Operators with the authority to approve planned outages and maintenance of its telecommunication, monitoring and analysis capabilities. [Violation Risk Factor: High] [Time Horizon: Operations Planning, Same-Day Operations, Real-time Operations]","2020-01-01","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[29891,"IRO-002-6","R5.",null,"Each Reliability Coordinator shall monitor Facilities, the status of Remedial Action Schemes, and non-BES facilities identified as necessary by the Reliability Coordinator, within its Reliability Coordinator Area and neighboring Reliability Coordinator Areas to identify any System Operating Limit exceedances and to determine any Interconnection Reliability Operating Limit exceedances within its Reliability Coordinator Area. [Violation Risk Factor: High] [Time Horizon: Real-Time Operations]","2020-01-01","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[29892,"IRO-002-6","R6.",null,"Each Reliability Coordinator shall have monitoring systems that provide information utilized by the Reliability Coordinator’s operating personnel, giving particular emphasis to alarm management and awareness systems, automated data transfers, and synchronized information systems, over a redundant infrastructure. [Violation Risk Factor: High] [Time Horizon: Real-time Operations]","2020-01-01","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30209,"IRO-002-7","R1.",null,"Reserved. (retired in SAR)","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30210,"IRO-002-7","R2.",null,"Each Reliability Coordinator shall have data exchange capabilities, with redundant and diversely routed data exchange infrastructure within the Reliability Coordinator's primary Control Center, for the exchange of Real-time data with its Balancing Authorities and Transmission Operators, and with other entities it deems necessary, for performing its Real-time monitoring and Real-time Assessments. [Violation Risk Factor: High] [Time Horizon: Same-Day Operations, Real-time Operations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30211,"IRO-002-7","R3.",null,"Each Reliability Coordinator shall test its primary Control Center data exchange capabilities specified in Requirement R2 for redundant functionality at least once every 90 calendar days. If the test is unsuccessful, the Reliability Coordinator shall initiate action within two hours to restore redundant functionality. [Violation Risk Factor: Medium ] [Time Horizon: Operations Planning]","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30212,"IRO-002-7","R4.",null,"Each Reliability Coordinator shall provide its System Operators with the authority to approve planned outages and maintenance of its telecommunication, monitoring and analysis capabilities. [Violation Risk Factor: High] [Time Horizon: Operations Planning, Same-Day Operations, Real-time Operations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30213,"IRO-002-7","R5.",null,"Each Reliability Coordinator shall monitor Facilities, the status of Remedial Action Schemes, and non-BES facilities identified as necessary by the Reliability Coordinator, within its Reliability Coordinator Area and neighboring Reliability Coordinator Areas to identify any System Operating Limit exceedances and to determine any Interconnection Reliability Operating Limit exceedances within its Reliability Coordinator Area. [Violation Risk Factor: High] [Time Horizon: Real-Time Operations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30214,"IRO-002-7","R6.",null,"Each Reliability Coordinator shall have monitoring systems that provide information utilized by the Reliability Coordinator’s operating personnel, giving particular emphasis to alarm management and awareness systems, automated data transfers, and synchronized information systems, over a redundant infrastructure. [Violation Risk Factor: High] [Time Horizon: Real-time Operations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26990,"IRO-005-3.1(i)a","R1.",null,"Each Reliability Coordinator shall monitor its Reliability Coordinator Area parameters, including but not limited to the following:",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RC","No",false,null,false]
[26991,"IRO-005-3.1(i)a","R1.1.",null,"Current status of Bulk Electric System elements (transmission or generation including critical auxiliaries such as Automatic Voltage Regulators and Remedial Action Schemes) and system loading.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RC","No",false,null,false]
[27000,"IRO-005-3.1(i)a","R1.10.",null,"Contingency events.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RC","No",false,null,false]
[26992,"IRO-005-3.1(i)a","R1.2.",null,"Current pre-contingency element conditions (voltage, thermal, or stability), including any applicable mitigation plans to alleviate SOL or IROL violations, including the plan’s viability and scope.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RC","No",false,null,false]
[26993,"IRO-005-3.1(i)a","R1.3.",null,"Current post-contingency element conditions (voltage, thermal, or stability), including any applicable mitigation plans to alleviate SOL or IROL violations, including the plan’s viability and scope.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RC","No",false,null,false]
[26994,"IRO-005-3.1(i)a","R1.4.",null,"System real and reactive reserves (actual versus required).",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RC","No",false,null,false]
[26995,"IRO-005-3.1(i)a","R1.5.",null,"Capacity and energy adequacy conditions.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RC","No",false,null,false]
[26996,"IRO-005-3.1(i)a","R1.6.",null,"Current ACE for all its Balancing Authorities.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RC","No",false,null,false]
[26997,"IRO-005-3.1(i)a","R1.7.",null,"Current local or Transmission Loading Relief procedures in effect.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RC","No",false,null,false]
[26998,"IRO-005-3.1(i)a","R1.8.",null,"Planned generation dispatches.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RC","No",false,null,false]
[26999,"IRO-005-3.1(i)a","R1.9.",null,"Planned transmission or generation outages.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RC","No",false,null,false]
[27009,"IRO-005-3.1(i)a","R10.",null,"In instances where there is a difference in derived limits, the Transmission Operators, Balancing Authorities, Generator Operators, Transmission Service Providers, Load-Serving Entities, and Purchasing-Selling Entities shall always operate the Bulk Electric System to the most limiting parameter.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","TSP, TOP, PSE, LSE, GOP, BA","Yes",true,null,false]
[27010,"IRO-005-3.1(i)a","R11.",null,"The Transmission Service Provider shall respect SOLs and IROLs in accordance with filed tariffs and regional Total Transfer Calculation and Available Transfer Calculation processes.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27011,"IRO-005-3.1(i)a","R12.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RC","No",false,null,false]
[27001,"IRO-005-3.1(i)a","R2.",null,"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 Load-Serving Entities.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RC","No",false,null,false]
[27002,"IRO-005-3.1(i)a","R3.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RC","No",false,null,false]
[27003,"IRO-005-3.1(i)a","R4.",null,"The Reliability Coordinator shall disseminate information within its Reliability Coordinator Area, as required.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RC","No",false,null,false]
[27004,"IRO-005-3.1(i)a","R5.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[27005,"IRO-005-3.1(i)a","R6.",null,"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, 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.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RC","No",false,null,false]
[27006,"IRO-005-3.1(i)a","R7.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RC","No",false,null,false]
[27007,"IRO-005-3.1(i)a","R8.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RC","No",false,null,false]
[27008,"IRO-005-3.1(i)a","R9.",null,"Whenever a Remedial Action Scheme 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 Remedial Action Scheme on inter-area flows. The Transmission Operator shall immediately inform the Reliability Coordinator of the status of the Remedial Action Scheme including any degradation or potential failure to operate as expected.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","TOP, RC","No",true,null,true]
[26854,"IRO-005-4","R1.","YES","When the results of an Operational Planning Analysis or Real-time Assessment indicate an anticipated or actual condition with Adverse Reliability Impacts within its Reliability Coordinator Area, each Reliability Coordinator shall notify all impacted Transmission Operators and Balancing Authorities in its Reliability Coordinator Area.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26853,"IRO-005-4","R1.","YES","When the results of an Operational Planning Analysis or Real-time Assessment indicate an anticipated or actual condition with Adverse Reliability Impacts within its Reliability Coordinator Area, each Reliability Coordinator shall notify all impacted Transmission Operators and Balancing Authorities in its Reliability Coordinator Area.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[26856,"IRO-005-4","R2.","YES","Each Reliability Coordinator that identifies an anticipated or actual condition with Adverse Reliability Impacts within its Reliability Coordinator Area shall notify all impacted Transmission Operators and Balancing Authorities in its Reliability Coordinator Area when the problem has been mitigated.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26855,"IRO-005-4","R2.","YES","Each Reliability Coordinator that identifies an anticipated or actual condition with Adverse Reliability Impacts within its Reliability Coordinator Area shall notify all impacted Transmission Operators and Balancing Authorities in its Reliability Coordinator Area when the problem has been mitigated.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[26857,"IRO-006-5","R1.",null,"Each Reliability Coordinator and Balancing Authority that receives a request pursuant to an Interconnection-wide transmission loading relief procedure (such as Eastern Interconnection TLR, WECC Unscheduled Flow Mitigation, or congestion management procedures from the ERCOT Protocols) from any Reliability Coordinator, Balancing Authority, or Transmission Operator in another Interconnection to curtail an Interchange Transaction that crosses an Interconnection boundary shall comply with the request, unless it provides a reliability reason to the requestor why it cannot comply with the request.","2011-10-01",null,"Effective","Communications; Documentations, Policies and Procedures; Monitoring; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC, BA","No",false,null,false]
[27020,"IRO-006-EAST-2","R1.",null,"Each Reliability Coordinator that initiates the Eastern Interconnection TLR procedure to prevent or mitigate an SOL or IROL exceedance shall identify the TLR level and the congestion management actions to be implemented, and shall update this information at least every clock hour (except TLR-1) after initiation up to and including the hour when the TLR level has been identified as TLR Level 0.1 [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27021,"IRO-006-EAST-2","R2.",null,"Each Reliability Coordinator with a Sink Balancing Authority that must implement congestion management actions pursuant to the Eastern Interconnection TLR procedure shall, within 15 minutes of receiving the request from the issuing Reliability Coordinator, instruct the Sink Balancing Authority to implement the congestion management actions, subject to the following exception: [Violation Risk Factor: High] [Time Horizon: Real-time Operations ]\n\n● Should an assessment determine that one or more of the congestion management actions communicated will result in a reliability concern or will be ineffective, the Reliability Coordinator with a Sink Balancing Authority shall coordinate alternate congestion management actions with the issuing Reliability Coordinator.","2016-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[27027,"IRO-008-2","R1.",null,"Each Reliability Coordinator shall perform an Operational Planning Analysis that will allow it to assess whether the planned operations for the next-day will exceed System Operating Limits (SOLs) and Interconnection Operating Reliability Limits (IROLs) within its Wide Area. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27029,"IRO-008-2","R2.",null,"Each Reliability Coordinator shall have a coordinated Operating Plan(s) for next-day operations to address potential System Operating Limit (SOL) and Interconnection Reliability Operating Limit (IROL) exceedances identified as a result of its Operational Planning Analysis as performed in Requirement R1 while considering the Operating Plans for the next-day provided by its Transmission Operators and Balancing Authorities. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27031,"IRO-008-2","R3.",null,"Each Reliability Coordinator shall notify impacted entities identified in its Operating Plan(s) cited in Requirement R2 as to their role in such plan(s). [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27032,"IRO-008-2","R4.",null,"Each Reliability Coordinator shall ensure that a Real-time Assessment is performed at least once every 30 minutes. [Violation Risk Factor: High] [Time Horizon: Sameday Operations, Real-time Operations]","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[27033,"IRO-008-2","R5.",null,"Each Reliability Coordinator shall notify impacted Transmission Operators and Balancing Authorities within its Reliability Coordinator Area, and other impacted Reliability Coordinators as indicated in its Operating Plan, when the results of a Realtime Assessment indicate an actual or expected condition that results in, or could result in, a System Operating Limit (SOL) or Interconnection Reliability Operating Limit (IROL) exceedance within its Wide Area. [Violation Risk Factor: High] [Time Horizon: Same-Day Operations, Real-time Operations]","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[27034,"IRO-008-2","R6.",null,"Each Reliability Coordinator shall notify impacted Transmission Operators and Balancing Authorities within its Reliability Coordinator Area, and other impacted Reliability Coordinators as indicated in its Operating Plan, when the System Operating Limit (SOL) or Interconnection Reliability Operating Limit (IROL) exceedance identified in Requirement R5 has been prevented or mitigated.\n[Violation Risk Factor: Medium] [Time Horizon: Same-Day Operations, Real-time Operations]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30677,"IRO-008-3","R1.",null,"Each Reliability Coordinator shall perform an Operational Planning Analysis that will allow it to assess whether the planned operations for the next-day will exceed System Operating Limits (SOLs) and Interconnection Reliability Operating Limits (IROLs) within its Wide Area. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30678,"IRO-008-3","R2.",null,"Each Reliability Coordinator shall have a coordinated Operating Plan(s) for next-day operations to address potential System Operating Limit (SOL) and Interconnection Reliability Operating Limit (IROL) exceedances identified as a result of its Operational Planning Analysis as performed in Requirement R1 while considering the Operating Plans for the next-day provided by its Transmission Operators and Balancing Authorities. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30679,"IRO-008-3","R3.",null,"Each Reliability Coordinator shall notify impacted entities identified in its Operating Plan(s) cited in Requirement R2 as to their role in such plan(s). [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30680,"IRO-008-3","R4.",null,"Each Reliability Coordinator shall ensure that a Real-time Assessment is performed at least once every 30 minutes. [Violation Risk Factor: High] [Time Horizon: Sameday Operations, Real-time Operations]","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30681,"IRO-008-3","R5.",null,"Each Reliability Coordinator shall notify, in accordance with its SOL methodology, impacted Transmission Operators and Balancing Authorities within its Reliability Coordinator Area, and other impacted Reliability Coordinators as indicated in its Operating Plan, when the results of a Realtime Assessment indicate an actual or expected condition that results in, or could result in, a System Operating Limit (SOL) exceedance or an Interconnection Reliability Operating Limit (IROL) exceedance within its Wide Area. [Violation Risk Factor: High] [Time Horizon: Same-Day Operations, Real-time Operations]","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[30682,"IRO-008-3","R6.",null,"Each Reliability Coordinator shall notifyy, in accordance with SOL methodology, impacted Transmission Operators and Balancing Authorities within its Reliability Coordinator Area, and other impacted Reliability Coordinators as indicated in its Operating Plan, when the System Operating Limit (SOL) exceedance or an Interconnection Reliability Operating Limit (IROL) exceedance identified in Requirement R5 has been prevented or mitigated.[Violation Risk Factor: Medium] [Time Horizon: Same-Day Operations, Real-time Operations]","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[30683,"IRO-008-3","R7.",null,"Each Reliability Coordinator shall use its SOL methodology when determining SOL exceedances for Real-time Assessments, Real-time monitoring, and Operational Planning Analysis. [Violation Risk Factor: Medium ] [Time Horizon: Same-Day Operations, Real-time Operations, Operations Planning]","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27035,"IRO-009-2","R1.",null,"For each IROL (in its Reliability Coordinator Area) that the Reliability Coordinator identifies one or more days prior to the current day, the Reliability Coordinator shall have one or more Operating Processes, Procedures, or Plans that identify actions the Reliability Coordinator shall take or actions the Reliability Coordinator shall direct others to take (up to and including load shedding): [Violation Risk Factor: Medium] [Time Horizon: Operations Planning or Same Day Operations]","2016-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27036,"IRO-009-2","R1.1.",null,"That can be implemented in time to prevent the identified IROL exceedance.","2016-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27037,"IRO-009-2","R1.2.",null,"To mitigate the magnitude and duration of an IROL exceedance such that the IROL exceedance is relieved within the IROL’s Tv.","2016-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27038,"IRO-009-2","R2.",null,"Each Reliability Coordinator shall initiate one or more Operating Processes, Procedures, or Plans (not limited to the Operating Processes, Procedures, or Plans developed for Requirement R1) that are intended to prevent an IROL exceedance, as identified in the Reliability Coordinator’s Real-time monitoring or Real-time Assessment. [Violation Risk Factor: High] [Time Horizon: Real-time Operations]","2016-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[27039,"IRO-009-2","R3.",null,"Each Reliability Coordinator shall act or direct others to act so that the magnitude and duration of an IROL exceedance is mitigated within the IROL’s Tv, as identified in the Reliability Coordinator’s Real-time monitoring or Real-time Assessment. [Violation Risk Factor: High] [Time Horizon: Real-time Operations]","2016-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[27040,"IRO-009-2","R4.",null,"Each Reliability Coordinator shall operate to the most limiting IROL and Tv in instances where there is a difference in an IROL or its Tv between Reliability Coordinators that are responsible for that Facility (or group of Facilities). [Violation Risk Factor: High] [Time Horizon: Real-time Operations]","2016-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[27048,"IRO-010-2","R1.",null,"The Reliability Coordinator shall maintain a documented specification for the data necessary for it to perform its Operational Planning Analyses, Real-time monitoring, and Real-time Assessments. The data specification shall include but not be limited to:\n(Violation Risk Factor: Low) (Time Horizon: Operations Planning)","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[27049,"IRO-010-2","R1.1.",null,"A list of data and information needed by the Reliability Coordinator to support its Operational Planning Analyses, Real-time monitoring, and Realtime Assessments including non-BES data and external network data, as deemed necessary by the Reliability Coordinator.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[27050,"IRO-010-2","R1.2.",null,"Provisions for notification of current Protection System and Special Protection System status or degradation that impacts System reliability.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[27051,"IRO-010-2","R1.3.",null,"A periodicity for providing data.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[27052,"IRO-010-2","R1.4.",null,"The deadline by which the respondent is to provide the indicated data.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[27053,"IRO-010-2","R2.",null,"The Reliability Coordinator shall distribute its data specification to entities that have data required by the Reliability Coordinator’s Operational Planning Analyses, Realtime monitoring, and Real-time Assessments. (Violation Risk Factor: Low) (Time Horizon: Operations Planning)","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[27054,"IRO-010-2","R3.",null,"Each Reliability Coordinator, Balancing Authority, Generator Owner, Generator Operator, Load-Serving Entity, Transmission Operator, Transmission Owner, and Distribution Provider receiving a data specification in Requirement R2 shall satisfy the obligations of the documented specifications using: (Violation Risk Factor: Medium) (Time Horizon: Operations Planning, Same-Day Operations, Real-time Operations)","2017-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27055,"IRO-010-2","R3.1.",null,"A mutually agreeable format","2017-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27056,"IRO-010-2","R3.2.",null,"A mutually agreeable process for resolving data conflicts","2017-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27057,"IRO-010-2","R3.3.",null,"A mutually agreeable security protocol","2017-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[29927,"IRO-010-3","R1.",null,"The Reliability Coordinator shall maintain a documented specification for the data necessary for it to perform its Operational Planning Analyses, Real-time monitoring, and Real-time Assessments. The data specification shall include but not be limited to: (Violation Risk Factor: Low) (Time Horizon: Operations Planning)","2021-04-01","2023-09-30","Effective",null,"LOWER","N/A","N/A",null,"N/A","DP, TOP, TO, GOP, GO, BA, RC","Yes",false,null,false]
[29928,"IRO-010-3","R1.",null,"The Reliability Coordinator shall maintain a documented specification for the data necessary for it to perform its Operational Planning Analyses, Real-time monitoring, and Real-time Assessments. The data specification shall include but not be limited to: (Violation Risk Factor: Low) (Time Horizon: Operations Planning)","2021-04-01","2023-09-30","Effective",null,"LOWER","N/A","N/A",null,"N/A","DP, TOP, TO, GOP, GO, BA, RC","Yes",false,null,false]
[29929,"IRO-010-3","R1.1.",null,"A list of data and information needed by the Reliability Coordinator to support its Operational Planning Analyses, Real-time monitoring, and Real-time Assessments including non-BES data and external network data, as deemed necessary by the Reliability Coordinator.","2021-04-01","2023-09-30","Effective",null,"LOWER","N/A","N/A",null,"N/A","DP, TOP, TO, GOP, GO, BA, RC","Yes",true,null,false]
[29930,"IRO-010-3","R1.2.",null,"Provisions for notification of current Protection System and Special Protection System status or degradation that impacts System reliability.","2021-04-01","2023-09-30","Effective",null,"LOWER","N/A","N/A",null,"N/A","DP, TOP, TO, GOP, GO, BA, RC","Yes",true,null,false]
[29931,"IRO-010-3","R1.3.",null,"A periodicity for providing data.","2021-04-01","2023-09-30","Effective",null,"LOWER","N/A","N/A",null,"N/A","DP, TOP, TO, GOP, GO, BA, RC","Yes",true,null,false]
[29932,"IRO-010-3","R1.4.",null,"The deadline by which the respondent is to provide the indicated data.","2021-04-01","2023-09-30","Effective",null,"LOWER","N/A","N/A",null,"N/A","DP, TOP, TO, GOP, GO, BA, RC","Yes",true,null,false]
[29933,"IRO-010-3","R2.",null,"The Reliability Coordinator shall distribute its data specification to entities that have data required by the Reliability Coordinator’s Operational Planning Analyses, Real-time monitoring, and Real-time Assessments. (Violation Risk Factor: Low) (Time Horizon: Operations Planning)","2021-04-01","2023-09-30","Effective",null,"LOWER","N/A","N/A",null,"N/A","DP, TOP, TO, GOP, GO, BA, RC","Yes",true,null,false]
[29934,"IRO-010-3","R3.",null,"Each Reliability Coordinator, Balancing Authority, Generator Owner, Generator Operator, Transmission Operator, Transmission Owner, and Distribution Provider receiving a data specification in Requirement R2 shall satisfy the obligations of the documented specifications using: (Violation Risk Factor: Medium) (Time Horizon: Operations Planning, Same-Day Operations, Real-time Operations)","2021-04-01","2023-09-30","Effective",null,"MEDIUM","N/A","N/A",null,"N/A","DP, TOP, TO, GOP, GO, BA, RC","Yes",true,null,false]
[29935,"IRO-010-3","R3.1.",null,"A mutually agreeable format","2021-04-01","2023-09-30","Effective",null,"MEDIUM","N/A","N/A",null,"N/A","DP, GOP, GO, TOP, TO, BA, RC","Yes",true,null,false]
[29936,"IRO-010-3","R3.2.",null,"A mutually agreeable process for resolving data conflicts","2021-04-01","2023-09-30","Effective",null,"MEDIUM","N/A","N/A",null,"N/A","DP, TOP, TO, GOP, GO, BA, RC","Yes",true,null,false]
[30406,"IRO-010-4","R1.",null,"The Reliability Coordinator shall maintain a documented specification for the data necessary for it to perform its Operational Planning Analyses, Real-time monitoring, and Real-time Assessments. The data specification shall include but not be limited to: (Violation Risk Factor: Low) (Time Horizon: Operations Planning)","2023-10-01",null,"Future Effective",null,"LOWER","N/A","N/A",null,"N/A",null,"No",false,null,false]
[30407,"IRO-010-4","R1.1.",null,"A list of data and information needed by the Reliability Coordinator to support its Operational Planning Analyses, Real-time monitoring, and Real-time Assessments including non-BES data and external network data, as deemed necessary by the Reliability Coordinator.","2023-10-01",null,"Future Effective",null,"LOWER","N/A","N/A",null,"N/A",null,"No",true,null,false]
[30408,"IRO-010-4","R1.2.",null,"Provisions for notification of current Protection System and Remedial Action Scheme (RAS) status or degradation that impacts System reliability.","2023-10-01",null,"Future Effective",null,"LOWER","N/A","N/A",null,"N/A",null,"No",true,null,false]
[30409,"IRO-010-4","R1.3.",null,"Provisions for notification of BES generating unit(s) during local forecasted cold weather to include:","2023-10-01",null,"Future Effective",null,"LOWER","N/A","N/A",null,"N/A",null,"No",true,null,false]
[30410,"IRO-010-4","R1.3.1.",null,"Operating limitations based on:","2023-10-01",null,"Future Effective",null,"LOWER","N/A","N/A",null,"N/A",null,"No",true,null,false]
[30411,"IRO-010-4","R1.3.1.1.",null,"capability and availability;","2023-10-01",null,"Future Effective",null,"LOWER","N/A","N/A",null,"N/A",null,"No",true,null,false]
[30412,"IRO-010-4","R1.3.1.2.",null,"fuel supply and inventory concerns;","2023-10-01",null,"Future Effective",null,"LOWER","N/A","N/A",null,"N/A",null,"No",true,null,false]
[30413,"IRO-010-4","R1.3.1.3.",null,"fuel switching capabilities; and","2023-10-01",null,"Future Effective",null,"LOWER","N/A","N/A",null,"N/A",null,"No",true,null,false]
[30414,"IRO-010-4","R1.3.1.4.",null,"environmental constraints","2023-10-01",null,"Future Effective",null,"LOWER","N/A","N/A",null,"N/A",null,"No",true,null,false]
[30415,"IRO-010-4","R1.3.2.",null,"Generating unit(s) minimum","2023-10-01",null,"Future Effective",null,"LOWER","N/A","N/A",null,"N/A",null,"No",true,null,false]
[30419,"IRO-010-4","R1.4.",null,"A periodicity for providing data","2023-10-01",null,"Future Effective",null,"LOWER","N/A","N/A",null,"N/A",null,"No",true,null,false]
[30420,"IRO-010-4","R1.5.",null,"The deadline by which the respondent is to provide the indicated data.","2023-10-01",null,"Future Effective",null,"LOWER","N/A","N/A",null,"N/A",null,"No",true,null,false]
[30421,"IRO-010-4","R2.",null,"The Reliability Coordinator shall distribute its data specification to entities that have data required by the Reliability Coordinator’s Operational Planning Analyses, Real-time monitoring, and Real-time Assessments. (Violation Risk Factor: Low) (Time Horizon: Operations Planning)","2023-10-01",null,"Future Effective",null,"LOWER","N/A","N/A",null,"N/A",null,"No",true,null,false]
[30422,"IRO-010-4","R3.",null,"Each Reliability Coordinator, Balancing Authority, Generator Owner, Generator Operator, Transmission Operator, Transmission Owner, and Distribution Provider receiving a data specification in Requirement R2 shall satisfy the obligations of the documented specifications using: (Violation Risk Factor: Medium) (Time Horizon: Operations Planning, Same-Day Operations, Real-time Operations)","2023-10-01",null,"Future Effective",null,"MEDIUM","N/A","N/A",null,"N/A",null,"No",true,null,false]
[30423,"IRO-010-4","R3.1.",null,"A mutually agreeable format","2023-10-01",null,"Future Effective",null,"MEDIUM","N/A","N/A",null,"N/A",null,"No",true,null,false]
[30424,"IRO-010-4","R3.2.",null,"A mutually agreeable process for resolving data conflicts","2023-10-01",null,"Future Effective",null,"MEDIUM","N/A","N/A",null,"N/A",null,"No",true,null,false]
[30425,"IRO-010-4","R3.3.",null,"A mutually agreeable security protocol","2023-10-01",null,"Future Effective",null,"MEDIUM","N/A","N/A",null,"N/A",null,"No",true,null,false]
[27076,"IRO-014-2","R1.",null,"Each Reliability Coordinator shall have Operating Procedures, Operating Processes, or Operating Plans for activities that require notification, exchange of information or coordination of actions that may impact other Reliability Coordinator Areas to support Interconnection reliability. These Operating Procedures, Processes, or Plans shall collectively address the following:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27077,"IRO-014-2","R1.1.",null,"Communications and notifications, including the mutually agreed to conditions 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.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[27078,"IRO-014-2","R1.2.",null,"Energy and capacity shortages.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[27079,"IRO-014-2","R1.3.",null,"Planned or unplanned outage information.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[27080,"IRO-014-2","R1.4.",null,"Control of voltage, including the coordination of reactive resources.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[27081,"IRO-014-2","R1.5.",null,"Coordination of information exchange to support reliability assessments.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[27082,"IRO-014-2","R1.6.",null,"Authority to act to prevent and mitigate system conditions which could cause Adverse Reliability Impacts to other Reliability Coordinator Areas.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[27083,"IRO-014-2","R1.7.",null,"Weekly conference calls",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[27084,"IRO-014-2","R2.",null,"Each Reliability Coordinator shall maintain its Operating Procedures, Operating Processes, or Operating Plans identified in Requirement R1 as follows:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[27085,"IRO-014-2","R2.1.",null,"Review and update annually with no more that 15 months between reviews.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[27086,"IRO-014-2","R2.2.",null,"Obtain written agreement from all of the Reliability Coordinators required to take the indicated action(s) for each update.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[27087,"IRO-014-2","R2.3.",null,"Distribute to all Reliability Coordinators that are required to take the indicated action(s) within 30 days of an update.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RC","No",false,null,false]
[27088,"IRO-014-2","R3.",null,"Each Reliability Coordinator shall make notifications and exchange reliability–related information with other Reliability Coordinators in accordance with the Operating Procedures, Operating Processes, or Operating Plans identified in Requirement R1.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27089,"IRO-014-2","R4.",null,"Each Reliability Coordinator shall participate in agreed upon conference calls, at least weekly (per Requirement 1, Part 1.7) with other Reliability Coordinators within the same Interconnection.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[27090,"IRO-014-2","R5.",null,"Each Reliability Coordinator, upon identification of an Adverse Reliability Impact, shall notify all other Reliability Coordinators.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27091,"IRO-014-2","R6.",null,"During each instance where Reliability Coordinators disagree on the existence of an Adverse Reliability Impact each impacted Reliability Coordinator shall operate as though the problem exists.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[27092,"IRO-014-2","R7.",null,"During those instances where Reliability Coordinators disagree on the existence of an Adverse Reliability Impact, the Reliability Coordinator that identified the Adverse Reliability Impact shall develop an action plan to resolve the Adverse Reliability Impact. [Violation Risk Factor:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[27093,"IRO-014-2","R8.",null,"During those instances where Reliability Coordinators disagree on the existence of an Adverse Reliability Impact, each Reliability Coordinator shall implement the action plan developed by the Reliability Coordinator that identified the Adverse Reliability Impact unless such actions would violate safety, equipment, regulatory or statutory requirements.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[27094,"IRO-014-3","R1.",null,"Each Reliability Coordinator shall have and implement Operating Procedures, Operating Processes, or Operating Plans, for activities that require notification or coordination of actions that may impact adjacent Reliability Coordinator Areas, to support Interconnection reliability. These Operating Procedures, Operating Processes, or Operating Plans shall include, but are not limited to, the following:\n[Violation Risk Factor: Medium] [Time Horizon: Operations Planning, Same-Day Operations]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27095,"IRO-014-3","R1.1.",null,"Criteria and processes for notifications.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27096,"IRO-014-3","R1.2.",null,"Energy and capacity shortages.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27097,"IRO-014-3","R1.3.",null,"Control of voltage, including the coordination of reactive resources.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27098,"IRO-014-3","R1.4.",null,"Exchange of information including planned and unplanned outage information to support its Operational Planning Analyses and Real-time Assessments.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27099,"IRO-014-3","R1.5.",null,"Provisions for periodic communications to support reliable operations.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27100,"IRO-014-3","R2.",null,"Each Reliability Coordinator shall maintain its Operating Procedures, Operating Processes, or Operating Plans identified in Requirement R1 as follows: [Violation Risk Factor: Low] [Time Horizon: Operations Planning, Same-Day Operations]","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[27101,"IRO-014-3","R2.1.",null,"Review and update annually with no more than 15 months between reviews.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[27102,"IRO-014-3","R2.2.",null,"Obtain written agreement from all of the Reliability Coordinators required to take the indicated action(s) for each update.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[27103,"IRO-014-3","R2.3.",null,"Distribute to all Reliability Coordinators that are required to take the indicated action(s) within 30 days of an update.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RC","No",false,null,false]
[27104,"IRO-014-3","R3.",null,"Each Reliability Coordinator, upon identification of an expected or actual Emergency in its Reliability Coordinator Area, shall notify other impacted Reliability Coordinators. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning, Same Day Operations, Real-time Operations]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27105,"IRO-014-3","R4.",null,"Each impacted Reliability Coordinator shall operate as though the Emergency exists during each instance where Reliability Coordinators disagree on the existence of an Emergency. [Violation Risk Factor: High] [Time Horizon: Operations Planning, Same-\nDay Operations, Real-time Operations]","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[27106,"IRO-014-3","R5.",null,"Each Reliability Coordinator that Identifies an Emergency in its Reliability Coordinator Area shall develop an action plan to resolve the Emergency during those instances where impacted Reliability Coordinators disagree on the existence of an Emergency.\n[Violation Risk Factor: High][Time Horizon: Operations Planning, Same-Day Operations, Real-time Operations]","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[27107,"IRO-014-3","R6.",null,"Each impacted Reliability Coordinator shall implement the action plan developed by the Reliability Coordinator that identifies the Emergency during those instances where Reliability Coordinators disagree on the existence of an Emergency, unless such\nactions would violate safety, equipment, regulatory, or statutory requirements. [Violation Risk Factor: High][Time Horizon: Operations Planning, Same-Day Operations, Real-time Operations]","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[27108,"IRO-014-3","R7.",null,"Each Reliability Coordinator shall assist Reliability Coordinators, if requested and able, provided that the requesting Reliability Coordinator has implemented its emergency procedures, unless such actions cannot be physically implemented or would violate\nsafety, equipment, regulatory, or statutory requirements. [Violation Risk Factor: High] [Time Horizon: Real-time Operations]","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[27114,"IRO-017-1","R1.",null,"Each Reliability Coordinator shall develop, implement, and maintain an outage coordination process for generation and Transmission outages within its Reliability Coordinator Area. The outage coordination process shall: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27115,"IRO-017-1","R1.1.",null,"Identify applicable roles and reporting responsibilities including:","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27116,"IRO-017-1","R1.1.1.",null,"Development and communication of outage schedules.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27117,"IRO-017-1","R1.1.2.",null,"Assignment of coordination responsibilities for outage schedules between Transmission Operator(s) and Balancing Authority(s).","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27118,"IRO-017-1","R1.2.",null,"Specify outage submission timing requirements.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27119,"IRO-017-1","R1.3.",null,"Define the process to evaluate the impact of Transmission and generation outages within its Wide Area.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27120,"IRO-017-1","R1.4.",null,"Define the process to coordinate the resolution of identified outage conflicts with its Transmission Operators and Balancing Authorities, and other Reliability Coordinators.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27121,"IRO-017-1","R2.","YES","Each Transmission Operator and Balancing Authority shall perform the functions specified in its Reliability Coordinator’s outage coordination process. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[27122,"IRO-017-1","R2.","YES","Each Transmission Operator and Balancing Authority shall perform the functions specified in its Reliability Coordinator’s outage coordination process. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[27126,"IRO-017-1","R3.","YES","Each Planning Coordinator and Transmission Planner shall provide its Planning Assessment to impacted Reliability Coordinators. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[27125,"IRO-017-1","R3.","YES","Each Planning Coordinator and Transmission Planner shall provide its Planning Assessment to impacted Reliability Coordinators. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[27124,"IRO-017-1","R3.","YES","Each Planning Coordinator and Transmission Planner shall provide its Planning Assessment to impacted Reliability Coordinators. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[27123,"IRO-017-1","R3.","YES","Each Planning Coordinator and Transmission Planner shall provide its Planning Assessment to impacted Reliability Coordinators. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[27129,"IRO-017-1","R4.","YES","Each Planning Coordinator and Transmission Planner shall jointly develop solutions with its respective Reliability Coordinator(s) for identified issues or conflicts with planned outages in its Planning Assessment for the Near-Term Transmission Planning Horizon. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[27128,"IRO-017-1","R4.","YES","Each Planning Coordinator and Transmission Planner shall jointly develop solutions with its respective Reliability Coordinator(s) for identified issues or conflicts with planned outages in its Planning Assessment for the Near-Term Transmission Planning Horizon. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[27127,"IRO-017-1","R4.","YES","Each Planning Coordinator and Transmission Planner shall jointly develop solutions with its respective Reliability Coordinator(s) for identified issues or conflicts with planned outages in its Planning Assessment for the Near-Term Transmission Planning Horizon. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29673,"IRO-018-1(i)","R1.",null,"Each Reliability Coordinator shall implement an Operating Process or Operating Procedure to address the quality of the Real-time data necessary to perform its Real-time monitoring and Real-time Assessments. The Operating Process or Operating Procedure shall include: [Violation Risk Factor: High ] [Time Horizon: Real-time Operations]","2018-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[29674,"IRO-018-1(i)","R1.1.",null,"Criteria for evaluating the quality of Real-time data;","2018-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[29675,"IRO-018-1(i)","R1.2.",null,"Provisions to indicate the quality of Real-time data to the System Operator; and","2018-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[29676,"IRO-018-1(i)","R1.3.",null,"Actions to address Real-time data quality issues with the entity(ies) responsible for providing the data when data quality affects Real-time Assessments.","2018-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[29677,"IRO-018-1(i)","R2.",null,"Each Reliability Coordinator shall implement an Operating Process or Operating Procedure to address the quality of analysis used in its Real-time Assessments. The Operating Process or Operating Procedure shall include: [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]","2018-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[29678,"IRO-018-1(i)","R2.1.",null,"Criteria for evaluating the quality of analysis used in its Real-time Assessments;","2018-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[29679,"IRO-018-1(i)","R2.2.",null,"Provisions to indicate the quality of analysis used in its Real-time Assessments; and","2018-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[29680,"IRO-018-1(i)","R2.3.",null,"Actions to address analysis quality issues affecting its Real-time Assessments.","2018-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[29681,"IRO-018-1(i)","R3.",null,"Each Reliability Coordinator shall have an alarm process monitor that provides notification(s) to its System Operators when a failure of its Real-time monitoring alarm processor has occurred. [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]","2018-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RC","No",false,null,false]
[27143,"MOD-001-0","R1.",null,"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 Organization’s TTC and ATC methodology shall include each of the following nine items, and shall explain its use in determining TTC and ATC values:",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27144,"MOD-001-0","R1.1.",null,"A narrative explaining how TTC and ATC values are determined.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27145,"MOD-001-0","R1.2.",null,"An accounting for how the reservations and schedules for firm (non-recallable) and non-firm (recallable) transfers, both within and outside the Transmission Service Provider’s system, are included.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27146,"MOD-001-0","R1.3.",null,"An accounting for the ultimate points of power injection (sources) and power extraction (sinks) in TTC and ATC calculations.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27147,"MOD-001-0","R1.4.",null,"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.)",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27148,"MOD-001-0","R1.5.",null,"A requirement that TTC and ATC values shall be determined and posted as follows:",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27149,"MOD-001-0","R1.5.1.",null,"Daily values for current week at least once per day.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27150,"MOD-001-0","R1.5.2.",null,"Daily values for day 8 through the first month at least once per week.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27151,"MOD-001-0","R1.5.3.",null,"Monthly values for months 2 through 13 at least once per month.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27152,"MOD-001-0","R1.6.",null,"Indication of the treatment and level of customer demands, including interruptible demands.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27153,"MOD-001-0","R1.7.",null,"A specification of how system conditions, limiting facilities, contingencies, transmission reservations, energy schedules, and other data needed by Transmission Service Providers for the calculation of TTC and ATC values are shared and used within the Regional 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.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27154,"MOD-001-0","R1.8.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27155,"MOD-001-0","R1.9.",null,"A description of the Regional Reliability Organization’s practice on the netting of transmission reservations for purposes of TTC and ATC determination.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27156,"MOD-001-0","R2.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27157,"MOD-001-1a","R1.",null,"Each Transmission Operator shall select one of the methodologies  listed below for calculating Available Transfer Capability (ATC) or Available Flowgate Capability (AFC) for each ATC Path per time period identified in R2 for those Facilities within its Transmission operating area:  [Time Horizon: Operations Planning]\n The Area Interchange Methodology, as described in MOD-028\n The Rated System Path Methodology, as described in MOD-029\n The Flowgate Methodology, as described in MOD-030","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures","MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[27159,"MOD-001-1a","R2.","YES","Each Transmission Service Provider shall calculate ATC or AFC values as listed below using the methodology or methodologies selected by its Transmission Operator(s):  [Time Horizon: Operations Planning]","2010-04-18",null,"Effective","Documentations, Policies and Procedures; Quality Check/Verification; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP","No",false,null,false]
[27160,"MOD-001-1a","R2.","YES","Each Transmission Service Provider shall calculate ATC or AFC values as listed below using the methodology or methodologies selected by its Transmission Operator(s):  [Time Horizon: Operations Planning]","2010-04-18",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27162,"MOD-001-1a","R2.1.","YES","Hourly values for at least the next 48 hours.","2010-04-18",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27161,"MOD-001-1a","R2.1.","YES","Hourly values for at least the next 48 hours.","2010-04-18",null,"Effective","Documentations, Policies and Procedures; Quality Check/Verification; Tools and Applications","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27163,"MOD-001-1a","R2.2.","YES","Daily values for at least the next 31 calendar days.","2010-04-18",null,"Effective","Documentations, Policies and Procedures; Quality Check/Verification; Tools and Applications","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27164,"MOD-001-1a","R2.2.","YES","Daily values for at least the next 31 calendar days.","2010-04-18",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27166,"MOD-001-1a","R2.3.","YES","Monthly values for at least the next 12 months (months 2-13).","2010-04-18",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27167,"MOD-001-1a","R3.",null,"Each Transmission Service Provider shall prepare and keep current an Available Transfer Capability Implementation Document (ATCID) that includes, at a minimum, the following information: [Time Horizon: Operations Planning]","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP","No",false,null,false]
[27168,"MOD-001-1a","R3.1.",null,"Information describing how the selected methodology (or methodologies) has been implemented, in such detail that, given the same information used by the Transmission Service Provider, the results of the ATC or AFC calculations can be validated.","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27169,"MOD-001-1a","R3.2.",null,"A description of the manner in which the Transmission Service Provider will account for counterflows including:","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27170,"MOD-001-1a","R3.2.1.",null,"How confirmed Transmission reservations, expected Interchange and internal counterflow are addressed in firm and non-firm ATC or AFC calculations.","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27171,"MOD-001-1a","R3.2.2.",null,"A rationale for that accounting specified in R3.2.","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27172,"MOD-001-1a","R3.3.",null,"The identity of the Transmission Operators  and Transmission Service Providers from which the Transmission Service Provider receives data for use in calculating ATC or AFC.","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27173,"MOD-001-1a","R3.4.",null,"The identity of the Transmission Service Providers and Transmission Operators to which it provides data for use in calculating transfer or Flowgate capability.","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27174,"MOD-001-1a","R3.5.",null,"A description of the allocation processes listed below that are applicable to the Transmission Service Provider:\n• Processes used to allocate transfer or Flowgate capability among multiple lines or sub-paths within a larger ATC Path or Flowgate.\n• Processes used to allocate transfer or Flowgate capabilities among multiple owners or users of an ATC Path or Flowgate.\n• Processes used to allocate transfer or Flowgate capabilities between Transmission Service Providers to address issues such as forward looking congestion management and seams coordination.","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27175,"MOD-001-1a","R3.6.",null,"A description of how generation and transmission outages are considered in transfer or Flowgate capability calculations, including:","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27176,"MOD-001-1a","R3.6.1.",null,"The criteria used to determine when an outage that is in effect part of a day impacts a daily calculation.","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27177,"MOD-001-1a","R3.6.2.",null,"The criteria used to determine when an outage that is in effect part of a month impacts a monthly calculation.","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27178,"MOD-001-1a","R3.6.3.",null,"How outages from other Transmission Service Providers that can not be mapped to the Transmission model used to calculate transfer or Flowgate capability are addressed.","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27179,"MOD-001-1a","R4.",null,"The Transmission Service Provider shall notify the following entities before implementing a new or revised ATCID: [Time Horizon: Operations Planning]","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP","No",false,null,false]
[27180,"MOD-001-1a","R4.1.",null,"Each Planning Coordinator associated with the Transmission Service Provider’s area.","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27181,"MOD-001-1a","R4.2.",null,"Each Reliability Coordinator associated with the Transmission Service Provider’s area.","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27182,"MOD-001-1a","R4.3.",null,"Each Transmission Operator associated with the Transmission Service Provider’s area.","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27183,"MOD-001-1a","R4.4.",null,"Each Planning Coordinator adjacent to the Transmission Service Provider’s area.","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27184,"MOD-001-1a","R4.5.",null,"Each Reliability Coordinator adjacent to the Transmission Service Provider’s area.","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27185,"MOD-001-1a","R4.6.",null,"Each Transmission Service Provider whose area is adjacent to the Transmission Service Provider’s area.","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27186,"MOD-001-1a","R5.",null,"The Transmission Service Provider shall make available the current ATCID to all of the entities specified in R4. [Time Horizon: Operations Planning]","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification","LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP","No",false,null,false]
[27187,"MOD-001-1a","R6.",null,"When calculating Total Transfer Capability (TTC) or Total Flowgate Capability (TFC) the Transmission Operator shall use assumptions no more limiting than those used in the planning of operations for the corresponding time period studied, providing such planning of operations has been performed for that time period.  [Time Horizon: Operations Planning]","2010-04-18",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures","MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[27190,"MOD-001-1a","R7.","YES","When calculating ATC or AFC the Transmission Service Provider shall use assumptions no more limiting than those used in the planning of operations for the corresponding time period studied, providing such planning of operations has been performed for that time period. [Time Horizon: Operations Planning]","2010-04-18",null,"Effective","Documentations, Policies and Procedures; Training","MEDIUM","SOMEWHAT LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP","No",false,null,false]
[27191,"MOD-001-1a","R7.","YES","When calculating ATC or AFC the Transmission Service Provider shall use assumptions no more limiting than those used in the planning of operations for the corresponding time period studied, providing such planning of operations has been performed for that time period. [Time Horizon: Operations Planning]","2010-04-18",null,"Effective","Documentations, Policies and Procedures; Monitoring; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP","No",false,null,false]
[27193,"MOD-001-1a","R8.","YES","Each Transmission Service Provider that calculates ATC shall recalculate ATC at a minimum on the following frequency, unless none of the calculated values identified in the ATC equation have changed:  [Time Horizon: Operations Planning]","2010-04-18",null,"Effective","Documentations, Policies and Procedures; Monitoring; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP","No",false,null,false]
[27194,"MOD-001-1a","R8.","YES","Each Transmission Service Provider that calculates ATC shall recalculate ATC at a minimum on the following frequency, unless none of the calculated values identified in the ATC equation have changed:  [Time Horizon: Operations Planning]","2010-04-18",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27196,"MOD-001-1a","R8.1.","YES","Hourly values, once per hour.  Transmission Service Providers are allowed up to 175 hours per calendar year during which calculations are not required to be performed, despite a change in a calculated value identified in the ATC equation.","2010-04-18",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27195,"MOD-001-1a","R8.1.","YES","Hourly values, once per hour.  Transmission Service Providers are allowed up to 175 hours per calendar year during which calculations are not required to be performed, despite a change in a calculated value identified in the ATC equation.","2010-04-18",null,"Effective","Documentations, Policies and Procedures; Monitoring; Training","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27197,"MOD-001-1a","R8.2.","YES","Daily values, once per day.","2010-04-18",null,"Effective","Documentations, Policies and Procedures; Monitoring; Training","No Individual VRF Assigned","VERY LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27198,"MOD-001-1a","R8.2.","YES","Daily values, once per day.","2010-04-18",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27200,"MOD-001-1a","R8.3.","YES","Monthly values, once per week.","2010-04-18",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27202,"MOD-001-1a","R9.","YES","Within thirty calendar days of receiving a request by any Transmission Service Provider, Planning Coordinator, Reliability Coordinator, or Transmission Operator for data from the list below solely for use in the requestor’s ATC or AFC calculations, each Transmission Service Provider receiving said request shall begin to make the requested data available to the requestor, subject to the conditions specified in R9.1 and R9.2:  [Time Horizon: Operations Planning]  • Expected generation and Transmission outages, additions, and retirements. • Load forecasts.  • Unit commitments and order of dispatch, to include all designated network resources and other resources that are committed or have the legal obligation to run, as they are expected to run, in one of the following formats chosen by the data provider:  Dispatch Order  Participation Factors\n Block Dispatch  • Aggregated firm capacity set-aside for Network Integration Transmission Service and aggregated non-firm capacity set aside for Network Integration Transmission Service (i.e. Secondary Service).  • Firm and non-firm Transmission reservations.  • Aggregated capacity set-aside for Grandfathered obligations   • Firm roll-over rights.  • Any firm and non-firm adjustments applied by the Transmission Service Provider to reflect parallel path impacts.  • Power flow models and underlying assumptions.  • Contingencies, provided in one or more of the following formats: A list of Elements   A list of Flowgates   A set of selection criteria that can be applied to the Transmission model used by the Transmission Operator and/or Transmission Service Provider  • Facility Ratings.  • Any other services that impact Existing Transmission Commitments (ETCs).\n• Values of Capacity Benefit Margin (CBM) and Transmission Reliability Margin (TRM) for all ATC Paths or Flowgates.  • Values of Total Flowgate Capability (TFC) and AFC for any Flowgates considered by the Transmission Service Provider receiving the request when selling Transmission service.   • Values of TTC and ATC for all ATC Paths for those Transmission Service Providers receiving the request that do not consider Flowgates when selling Transmission Service.  • Source and sink identification and mapping to the model.","2010-04-18",null,"Effective","Documentations, Policies and Procedures; Tools and Applications","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP","No",false,null,false]
[27203,"MOD-001-1a","R9.","YES","Within thirty calendar days of receiving a request by any Transmission Service Provider, Planning Coordinator, Reliability Coordinator, or Transmission Operator for data from the list below solely for use in the requestor’s ATC or AFC calculations, each Transmission Service Provider receiving said request shall begin to make the requested data available to the requestor, subject to the conditions specified in R9.1 and R9.2:  [Time Horizon: Operations Planning]  • Expected generation and Transmission outages, additions, and retirements. • Load forecasts.  • Unit commitments and order of dispatch, to include all designated network resources and other resources that are committed or have the legal obligation to run, as they are expected to run, in one of the following formats chosen by the data provider:  Dispatch Order  Participation Factors\n Block Dispatch  • Aggregated firm capacity set-aside for Network Integration Transmission Service and aggregated non-firm capacity set aside for Network Integration Transmission Service (i.e. Secondary Service).  • Firm and non-firm Transmission reservations.  • Aggregated capacity set-aside for Grandfathered obligations   • Firm roll-over rights.  • Any firm and non-firm adjustments applied by the Transmission Service Provider to reflect parallel path impacts.  • Power flow models and underlying assumptions.  • Contingencies, provided in one or more of the following formats: A list of Elements   A list of Flowgates   A set of selection criteria that can be applied to the Transmission model used by the Transmission Operator and/or Transmission Service Provider  • Facility Ratings.  • Any other services that impact Existing Transmission Commitments (ETCs).\n• Values of Capacity Benefit Margin (CBM) and Transmission Reliability Margin (TRM) for all ATC Paths or Flowgates.  • Values of Total Flowgate Capability (TFC) and AFC for any Flowgates considered by the Transmission Service Provider receiving the request when selling Transmission service.   • Values of TTC and ATC for all ATC Paths for those Transmission Service Providers receiving the request that do not consider Flowgates when selling Transmission Service.  • Source and sink identification and mapping to the model.","2010-04-18",null,"Effective",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)",null,"N/A","TSP","No",false,null,false]
[27205,"MOD-001-1a","R9.1.","YES","The Transmission Service Provider shall make its own current data available, in the format maintained by the Transmission Service Provider, for up to 13 months into the future (subject to confidentiality and security requirements).","2010-04-18",null,"Effective","Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27206,"MOD-001-1a","R9.1.","YES","The Transmission Service Provider shall make its own current data available, in the format maintained by the Transmission Service Provider, for up to 13 months into the future (subject to confidentiality and security requirements).","2010-04-18",null,"Effective",null,"No Individual VRF Assigned","LIKELY","N/A",null,"N/A","TSP","No",false,null,false]
[27208,"MOD-001-1a","R9.1.1.","YES","If the Transmission Service Provider uses the data requested in its transfer or Flowgate capability calculations, it shall make the data used available","2010-04-18",null,"Effective","Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27209,"MOD-001-1a","R9.1.1.","YES","If the Transmission Service Provider uses the data requested in its transfer or Flowgate capability calculations, it shall make the data used available","2010-04-18",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27211,"MOD-001-1a","R9.1.2.","YES","If the Transmission Service Provider does not use the data requested in its transfer or Flowgate capability calculations, but maintains that data, it shall make that data available","2010-04-18",null,"Effective","Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27212,"MOD-001-1a","R9.1.2.","YES","If the Transmission Service Provider does not use the data requested in its transfer or Flowgate capability calculations, but maintains that data, it shall make that data available","2010-04-18",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27214,"MOD-001-1a","R9.1.3.","YES","If the Transmission Service Provider does not use the data requested in its transfer or Flowgate capability calculations, and does not maintain that data, it shall not be required to make that data available","2010-04-18",null,"Effective","Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27215,"MOD-001-1a","R9.1.3.","YES","If the Transmission Service Provider does not use the data requested in its transfer or Flowgate capability calculations, and does not maintain that data, it shall not be required to make that data available","2010-04-18",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27217,"MOD-001-1a","R9.2.","YES","This data shall be made available by the Transmission Provider on the schedule specified by the requestor (but no more frequently than once per hour, unless mutually agreed to by the requester and the provider).","2010-04-18",null,"Effective","Documentations, Policies and Procedures; Tools and Applications","No Individual VRF Assigned","LIKELY","N/A","UNLIKELY","N/A","TSP","No",false,null,false]
[27218,"MOD-001-1a","R9.2.","YES","This data shall be made available by the Transmission Provider on the schedule specified by the requestor (but no more frequently than once per hour, unless mutually agreed to by the requester and the provider).","2010-04-18",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27219,"MOD-001-2","R1.",null,"Each Transmission Operator that determines Total Flowgate Capability (TFC) or Total Transfer Capability (TTC) shall develop a written methodology (or methodologies) for determining TFC or TTC values. The methodology (or methodologies) shall reflect the Transmission Operator’s current practices for determining TFC or TTC values. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27220,"MOD-001-2","R1.1.",null,"Each methodology shall describe the method used to account for the following limitations in both the pre‐ and post‐contingency state:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27221,"MOD-001-2","R1.1.1.",null,"Facility ratings;",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27222,"MOD-001-2","R1.1.2.",null,"System voltage limits;",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27223,"MOD-001-2","R1.1.3.",null,"Transient stability limits;",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27224,"MOD-001-2","R1.1.4.",null,"Voltage stability limits; and",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27225,"MOD-001-2","R1.1.5.",null,"Other System Operating Limits (SOLs).",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27226,"MOD-001-2","R1.2.",null,"Each methodology shall describe the method used to account for each of the following elements, provided such elements impact the determination of TFC or TTC:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27227,"MOD-001-2","R1.2.1.",null,"The simulation of transfers performed through the adjustment of generation, Load, or both;",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27228,"MOD-001-2","R1.2.2.",null,"Transmission topology, including, but not limited to, additions and retirements;",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27229,"MOD-001-2","R1.2.3.",null,"Expected transmission uses;",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27230,"MOD-001-2","R1.2.4.",null,"Planned outages;",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27231,"MOD-001-2","R1.2.5.",null,"Parallel path (loop flow) adjustments;",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27232,"MOD-001-2","R1.2.6.",null,"Load forecast; and",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27233,"MOD-001-2","R1.2.7.",null,"Generator dispatch, including, but not limited to, additions and retirements.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27234,"MOD-001-2","R1.3.",null,"Each methodology shall describe the process for including any reliability‐related constraints that are requested to be included by another Transmission Operator, provided that (1) the request references this specific requirement, and (2) the requesting Transmission Operator includes those constraints in its TFC or TTC determination.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27235,"MOD-001-2","R1.3.1.",null,"Each Transmission Operator that uses the Flowgate Methodology shall include in its methodology an impact test process for including requested constraints. If a generator to Load transfer in a registered entity’s area or a transfer to a neighboring registered entity impacts the requested constraint by five percent or greater, the requested constraint shall be included in the TFC determination, otherwise the requested constraint is not required to be included.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27236,"MOD-001-2","R1.3.2.",null,"Each Transmission Operator that uses the Area Interchange or Rated System Path Methodology shall describe in its methodology the process it uses to account for requested constraints that have a five percent or greater distribution factor for a transfer between areas in the TTC determination; otherwise the requested constraint is not required to be included. When testing transfers involving the requesting Transmission Operator’s area, the requested constraint may be excluded.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27237,"MOD-001-2","R1.3.3.",null,"A different method for determining whether requested constraints need to be included in the TFC or TTC determination may be used if agreed to by the Transmission Operators.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27238,"MOD-001-2","R2.","YES","Each Transmission Service Provider that determines Available Flowgate Capability (AFC) or Available Transfer Capability (ATC) shall develop an Available Transfer Capability Implementation Document (ATCID) that describes the methodology (or methodologies) for determining AFC or ATC values. The methodology (or methodologies) shall reflect the Transmission Service Provider’s current practices for determining AFC or ATC values. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27239,"MOD-001-2","R2.","YES","Each Transmission Service Provider that determines Available Flowgate Capability (AFC) or Available Transfer Capability (ATC) shall develop an Available Transfer Capability Implementation Document (ATCID) that describes the methodology (or methodologies) for determining AFC or ATC values. The methodology (or methodologies) shall reflect the Transmission Service Provider’s current practices for determining AFC or ATC values. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27240,"MOD-001-2","R2.1.",null,"Each methodology shall describe the method used to account for the following elements, provided such elements impact the determination of AFC or ATC:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27241,"MOD-001-2","R2.1.1.",null,"The simulation of transfers performed through the adjustment of generation, Load, or both;",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27242,"MOD-001-2","R2.1.2.",null,"Transmission topology, including, but not limited to, additions and retirements;",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27243,"MOD-001-2","R2.1.3.",null,"Expected transmission uses;",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27244,"MOD-001-2","R2.1.4.",null,"Planned outages;",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27245,"MOD-001-2","R2.1.5.",null,"Parallel path (loop flow) adjustments;",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27246,"MOD-001-2","R2.1.6.",null,"Load forecast; and",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27247,"MOD-001-2","R2.1.7.",null,"Generator dispatch, including, but not limited to, additions and retirements.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27248,"MOD-001-2","R2.2.",null,"Each Transmission Service Provider that uses the Flowgate Methodology shall, for reliabilityrelated constraints identified in part 1.3, use the AFC determined by the Transmission Service Provider for that constraint.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27249,"MOD-001-2","R3.",null,"Each Transmission Service Provider that determines Capacity Benefit Margin (CBM) values shall develop a Capacity Benefit Margin Implementation Document (CBMID) that describes its method for determining CBM values. The method described in the CBMID shall reflect the Transmission Service Provider’s current practices for determining CBM values. [Violation Risk Factor: Lower] [Time\nHorizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27250,"MOD-001-2","R4.",null,"Each Transmission Operator that determines Transmission Reliability Margin (TRM) values shall develop a Transmission Reliability Margin Implementation Document (TRMID) that describes its method for determining TRM values. The method described in the TRMID shall reflect the Transmission Operator’s current practices for determining TRM values. [Violation Risk Factor: Lower][Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27251,"MOD-001-2","R5.",null,"Within 45 calendar days of receiving a written request that references this specific requirement from a Planning Coordinator, Reliability Coordinator, Transmission Operator, Transmission Planner, Transmission Service Provider, or any other registered entity that demonstrates a reliability need, each Transmission Operator or Transmission Service Provider shall provide:\n[Violation Risk Factor: Lower] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP","No",true,null,false]
[27252,"MOD-001-2","R5.1.",null,"A written response to any request for clarification of its TFC or TTC methodology, ATCID, CBMID, or TRMID. If the request for clarification is contrary to the Transmission Operator’s or Transmission Service Provider’s confidentiality, regulatory, or security requirements then a written response shall be provided explaining the clarifications not provided, on what basis and whether there are any options for resolving any of the confidentiality, regulatory, or security concerns.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP","No",true,null,false]
[27253,"MOD-001-2","R5.2.",null,"If not publicly posted on OASIS or its company website, the Transmission Operator’s\neffective:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP","No",true,null,false]
[27254,"MOD-001-2","R5.2.1.",null,"TRMID; and",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP","No",true,null,false]
[27255,"MOD-001-2","R5.2.2.",null,"TFC or TTC methodology.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP","No",true,null,false]
[27256,"MOD-001-2","R5.3.",null,"If not publicly posted on OASIS or its company website, the Transmission Service Provider’s\neffective:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP","No",true,null,false]
[27257,"MOD-001-2","R5.3.1.",null,"ATCID; and",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP","No",true,null,false]
[27258,"MOD-001-2","R5.3.2.",null,"CBMID.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP","No",true,null,false]
[27259,"MOD-001-2","R6.",null,"Each Transmission Operator or Transmission Service Provider that receives a written request from another Transmission Operator or Transmission Service Provider for data related to AFC, ATC, TFC, or TTC determinations that (1) references this specific requirement, and (2) specifies that the requested data is for use in the requesting party’s AFC, ATC, TFC, or TTC determination shall take one of the actions below. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP","No",true,null,false]
[27260,"MOD-001-2","R6.1.",null,"In responding to a written request for data on an ongoing basis, the Transmission Service Provider or Transmission Operator shall make available its data on an ongoing basis no later than 45 calendar days from receipt of the written request. Unless otherwise agreed upon, the Transmission Operator or Transmission Service Provider is not required to:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP","No",true,null,false]
[27261,"MOD-001-2","R6.1.1.",null,"Alter the format in which it maintains or uses the data; or",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP","No",true,null,false]
[27262,"MOD-001-2","R6.1.2.",null,"Make available the requested data on a more frequent basis than it produces the data and in no event shall it be required to provide the data more frequently than once an hour.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP","No",true,null,false]
[27263,"MOD-001-2","R6.2.",null,"In responding to all other data requests, each Transmission Operator or Transmission Service Provider shall make available the requested data within 45 calendar days of receipt of the written request. Unless otherwise agreed upon, the Transmission Operator or Transmission Service Provider is not required to alter the format in which it maintains or uses the data.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP","No",true,null,false]
[27264,"MOD-001-2","R6.3.",null,"If making available any requested data under parts 6.1 or 6.2 of this requirement is contrary to the Transmission Operator’s or Transmission Service Provider’s confidentiality, regulatory, or security requirements, the Transmission Operator or Transmission Service Provider shall not be required to make available that data; provided that, within 45 calendar days of the written request, it responds to the requesting registered entity specifying the data that is not being provided, on what basis and whether there are any options for resolving any of the confidentiality, regulatory or security concerns.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TSP, TOP","No",true,null,false]
[27265,"MOD-004-0","R1.",null,"Each Regional Reliability Organization, in conjunction with its members, shall develop and document a Regional CBM methodology. The Regional Reliability Organization’s 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.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27266,"MOD-004-0","R1.1.",null,"Specify that the method used by each Regional Reliability Organization member to determine its generation reliability requirements as the basis for CBM shall be consistent with its generation planning criteria.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27267,"MOD-004-0","R1.10.",null,"Describe the inclusion or exclusion rationale for generation reserve sharing arrangements in the CBM values.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27268,"MOD-004-0","R1.2.",null,"Specify the frequency of calculation of the generation reliability requirement and associated CBM values.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27269,"MOD-004-0","R1.3.",null,"Require that generation unit outages considered in a Transmission Service Provider’s CBM calculation be restricted to those units within the Transmission Service Provider’s system.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27270,"MOD-004-0","R1.4.",null,"Require that CBM be preserved only on the Transmission Service Provider’s System where the Load-Serving Entity’s Load is located (i.e., CBM is an import quantity only).",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27271,"MOD-004-0","R1.5.",null,"Describe the inclusion or exclusion rationale for generation resources of each Load-Serving Entity including those generation resources not directly connected to the Transmission Service Provider’s system but serving Load-Serving Entity loads connected to the Transmission Service Provider’s system.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27272,"MOD-004-0","R1.6.",null,"Describe the inclusion or exclusion rationale for generation connected to the Transmission Service Provider’s system but not obligated to serve Native/Network Load connected to the Transmission Service Provider’s system.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27273,"MOD-004-0","R1.7.",null,"Describe the formal process and rationale for the Regional Reliability Organization to grant any variances to individual Transmission Service Providers from the Regional Reliability Organization’s CBM methodology.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27274,"MOD-004-0","R1.8.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27275,"MOD-004-0","R1.9.",null,"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).",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27276,"MOD-004-0","R2.",null,"The Regional Reliability Organization shall make the most recent version of the documentation of its CBM methodology available on a website accessible by NERC, the Regional Reliability Organizations, and transmission users.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27277,"MOD-004-1","R1.",null,"The Transmission Service Provider that maintains CBM shall prepare and keep current a “Capacity Benefit Margin Implementation Document” (CBMID) that includes, at a minimum, the following information: [Time Horizon: Operations Planning, Long-term Planning]","2011-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27278,"MOD-004-1","R1.1.",null,"The process through which a Load-Serving Entity within a Balancing Authority Area associated with the Transmission Service Provider, or the Resource Planner associated with that Balancing Authority Area, may ensure that its need for Transmission capacity to be set aside as CBM will be reviewed and accommodated by the Transmission Service Provider to the extent Transmission capacity is available.","2011-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27279,"MOD-004-1","R1.2.",null,"The procedure and assumptions for establishing CBM for each Available Transfer Capability (ATC) Path or Flowgate.","2011-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27280,"MOD-004-1","R1.3.",null,"The procedure for a Load-Serving Entity or Balancing Authority to use Transmission capacity set aside as CBM, including the manner in which the Transmission Service Provider will manage situations where the requested use of CBM exceeds the amount of CBM available.","2011-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27281,"MOD-004-1","R10.",null,"The Load-Serving Entity or Balancing Authority shall  request to import energy over firm Transfer Capability set aside as CBM only when experiencing a declared NERC Energy Emergency Alert (EEA) 2 or higher.  [Time Horizon: Same-day Operations]","2011-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","LSE, BA","Yes",false,null,false]
[27282,"MOD-004-1","R11.",null,"When reviewing an Arranged Interchange using CBM, all Balancing Authorities and Transmission Service Providers shall waive, within the bounds of reliable operation, any Real-time timing and ramping requirements. [Time Horizon: Same-day Operations]","2011-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TSP, BA","No",false,null,false]
[27283,"MOD-004-1","R12.",null,"The Transmission Service Provider that maintains CBM shall approve, within the bounds of reliable operation, any Arranged Interchange using CBM that is submitted by an “energy deficient entity ” under an EEA 2 if: [Time Horizon: Same-day Operations]","2011-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27284,"MOD-004-1","R12.1.",null,"The CBM is available","2011-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27285,"MOD-004-1","R12.2.",null,"The EEA 2 is declared within the Balancing Authority Area of the “energy deficient entity,” and","2011-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27286,"MOD-004-1","R12.3.",null,"The Load of the “energy deficient entity” is located within the Transmission Service Provider’s area.","2011-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27287,"MOD-004-1","R2.",null,"The Transmission Service Provider that maintains CBM shall make available its current CBMID to the Transmission Operators, Transmission Service Providers, Reliability Coordinators, Transmission Planners, Resource Planners, and Planning Coordinators that are within or adjacent to the Transmission Service Provider’s area, and to the Load Serving Entities and Balancing Authorities within the Transmission Service Provider’s area, and notify those entities of any changes to the CBMID prior to the effective date of the change.  [Time Horizon: Operations Planning]","2011-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27288,"MOD-004-1","R3.",null,"Each Load-Serving Entity determining the need for Transmission capacity to be set aside as CBM for imports into a Balancing Authority Area shall determine that need by: [Time Horizon: Operations Planning]","2011-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","LSE","Yes",false,null,false]
[27289,"MOD-004-1","R3.1.",null,"Using one or more of the following to determine the GCIR:\nLoss of Load Expectation (LOLE) studies\nLoss of Load Probability (LOLP) studies\nDeterministic risk-analysis studies \nReserve margin or resource adequacy requirements established by other entities, such as municipalities, state commissions, regional transmission organizations, independent system operators, Regional Reliability Organizations, or regional entities","2011-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","LSE","Yes",false,null,false]
[27290,"MOD-004-1","R3.2.",null,"Identifying expected import path(s) or source region(s).","2011-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","LSE","Yes",false,null,false]
[27291,"MOD-004-1","R4.",null,"Each Resource Planner determining the need for Transmission capacity to be set aside as CBM for imports into a Balancing Authority Area shall determine that need by: [Time Horizon: Operations Planning]","2011-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","RP","No",false,null,false]
[27292,"MOD-004-1","R4.1.",null,"Using one or more of the following to determine the GCIR:\nLoss of Load Expectation (LOLE) studies\nLoss of Load Probability (LOLP) studies\nDeterministic risk-analysis studies\nReserve margin or resource adequacy requirements established by other entities, such as municipalities, state commissions, regional transmission organizations, independent system operators, Regional Reliability Organizations, or regional entities","2011-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RP","No",false,null,false]
[27293,"MOD-004-1","R4.2.",null,"Identifying expected import path(s) or source region(s).","2011-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","RP","No",false,null,false]
[27294,"MOD-004-1","R5.",null,"At least every 13 months, the Transmission Service Provider that maintains CBM shall establish a CBM value for each ATC Path or Flowgate to be used for ATC or Available Flowgate Capability (AFC) calculations during the 13 full calendar months (months 2-14) following the current month (the month in which the Transmission Service Provider is establishing the CBM values).  This value shall: [Time Horizon: Operations Planning]","2011-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27295,"MOD-004-1","R5.1.",null,"Reflect consideration of each of the following if available:\nAny studies (as described in R3.1) performed by Load-Serving Entities for loads within the Transmission Service Provider’s area \nAny studies (as described in R4.1) performed by Resource Planners for loads within the Transmission Service Provider’s area  \nAny reserve margin or resource adequacy requirements for loads within the Transmission Service Provider’s area established by other entities, such as municipalities, state commissions, regional transmission organizations, independent system operators, Regional Reliability Organizations, or regional entities","2011-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27296,"MOD-004-1","R5.2.",null,"Be allocated as follows:\nFor ATC Paths, based on the expected import paths or source regions provided by Load-Serving Entities or Resource Planners\nFor Flowgates, based on the expected import paths or source regions provided by Load-Serving Entities or Resource Planners and the distribution factors associated with those paths or regions, as determined by the Transmission Service Provider","2011-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27297,"MOD-004-1","R6.",null,"At least every 13 months, the Transmission Planner shall establish a CBM value for each ATC Path or Flowgate to be used in planning during each of the full calendar years two through ten following the current year (the year in which the Transmission Planner is establishing the CBM values).  This value shall:  [Time Horizon: Long-term Planning]","2011-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP","No",false,null,false]
[27298,"MOD-004-1","R6.1.",null,"Reflect consideration of each of the following if available:\nAny studies (as described in R3.1) performed by Load-Serving Entities for loads within the Transmission Planner’s area \nAny studies (as described in R4.1) performed by Resource Planners for loads within the Transmission Planner’s area\nAny reserve margin or resource adequacy requirements for loads within the Transmission Planner’s area established by other entities, such as municipalities, state commissions, regional transmission organizations, independent system operators, Regional Reliability Organizations, or regional entities","2011-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP","No",false,null,false]
[27299,"MOD-004-1","R6.2.",null,"Be allocated as follows:\nFor ATC Paths, based on the expected import paths or source regions provided by Load-Serving Entities or Resource Planners\n For Flowgates, based on the expected import paths or source regions provided by Load-Serving Entities or Resource Planners and the distribution factors associated with those paths or regions, as determined by the Transmission Planner.","2011-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP","No",false,null,false]
[27300,"MOD-004-1","R7.",null,"Less than 31 calendar days after the establishment of CBM, the Transmission Service Provider that maintains CBM shall notify all the Load-Serving Entities and Resource Planners that determined they had a need for CBM on the Transmission Service Provider’s system of the amount of CBM set aside. [Time Horizon: Operations Planning]","2011-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27301,"MOD-004-1","R8.",null,"Less than 31 calendar days after the establishment of CBM, the Transmission Planner shall notify all the Load-Serving Entities and Resource Planners that determined they had a need for CBM on the system being planned by the Transmission Planner of the amount of CBM set aside. [Time Horizon: Operations Planning]","2011-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP","No",false,null,false]
[27302,"MOD-004-1","R9.",null,"The Transmission Service Provider that maintains CBM and the Transmission Planner shall each provide (subject to confidentiality and security requirements) copies of the applicable supporting data, including any models, used for determining CBM or allocating CBM over each ATC Path or Flowgate to the following: [Time Horizon: Operations Planning, Long-term Planning]","2011-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP, TP","No",false,null,false]
[27303,"MOD-004-1","R9.1.",null,"Each of its associated Transmission Operators within 30 calendar days of their making a request for the data.","2011-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP","No",false,null,false]
[27304,"MOD-004-1","R9.2.",null,"To any Transmission Service Provider, Reliability Coordinator, Transmission Planner, Resource Planner, or Planning Coordinator within 30 calendar days of their making a request for the data.","2011-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP","No",false,null,false]
[27305,"MOD-008-0","R1.",null,"Each Regional Reliability Organization, in conjunction with its members, shall develop and document a Regional TRM methodology. The Region’s 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.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27306,"MOD-008-0","R1.1.",null,"Specify the update frequency of TRM calculations.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27307,"MOD-008-0","R1.2.",null,"Specify how TRM values are incorporated into Available Transfer Capability calculations.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27308,"MOD-008-0","R1.3.",null,"Specify the uncertainties accounted for in TRM and the methods used to determine their 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.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27309,"MOD-008-0","R1.3.1.",null,"Aggregate Load forecast error (not included in determining generation\nreliability requirements).",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27310,"MOD-008-0","R1.3.2.",null,"Load distribution error.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27311,"MOD-008-0","R1.3.3.",null,"Variations in facility Loadings due to balancing of generation within a\nBalancing Authority Area.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27312,"MOD-008-0","R1.3.4.",null,"Forecast uncertainty in transmission system topology.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27313,"MOD-008-0","R1.3.5.",null,"Allowances for parallel path (loop flow) impacts.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27314,"MOD-008-0","R1.3.6.",null,"Allowances for simultaneous path interactions.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27315,"MOD-008-0","R1.3.7.",null,"Variations in generation dispatch.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27316,"MOD-008-0","R1.3.8.",null,"Short-term System Operator response (Operating Reserve actions not\nexceeding a 59-minute window).",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27317,"MOD-008-0","R1.4.",null,"Describe the conditions, if any, under which TRM may be available to the market as Non-Firm Transmission Service.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27318,"MOD-008-0","R1.5.",null,"Describe the formal process for the Regional Reliability Organization to grant any variances to individual Transmission Service Providers from the Regional TRM methodology.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27319,"MOD-008-0","R2.",null,"The Regional Reliability Organization shall make its most recent version of the documentation of its TRM methodology available on a web site accessible by NERC, the Regional Reliability Organizations, and transmission users.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27320,"MOD-008-1","R1.",null,"Each Transmission Operator shall prepare and keep current a TRM Implementation Document (TRMID) that includes, as a minimum, the following information:  [Time Horizon: Operations Planning]","2011-07-01",null,"Effective","Authorization/Approval; Documentations, Policies and Procedures; Quality Check/Verification","MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[27321,"MOD-008-1","R1.1.",null,"Identification of (on each of its respective ATC Paths or Flowgates) each of the following components of uncertainty if used in establishing TRM, and a description of how that component is used to establish a TRM value:\n- Aggregate Load forecast.\n- Load distribution uncertainty.\n- Forecast uncertainty in Transmission system topology (including, but not limited to, forced or unplanned outages and maintenance outages).\n- Allowances for parallel path (loop flow) impacts.\n- Allowances for simultaneous path interactions.\n- Variations in generation dispatch (including, but not limited to, forced or unplanned outages, maintenance outages and location of future generation).\n- Short-term System Operator response (Operating Reserve actions ).\n- Reserve sharing requirements.\n- Inertial response and frequency bias.","2011-07-01",null,"Effective","Authorization/Approval; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","UNLIKELY","N/A","UNLIKELY","N/A","TOP","No",true,null,false]
[27322,"MOD-008-1","R1.2.",null,"The description of the method used to allocate TRM across ATC Paths or Flowgates.","2011-07-01",null,"Effective","Authorization/Approval; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","UNLIKELY","N/A","UNLIKELY","N/A","TOP","No",true,null,false]
[27323,"MOD-008-1","R1.3.",null,"The identification of the TRM calculation used for the following time periods:","2011-07-01",null,"Effective","Authorization/Approval; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","UNLIKELY","N/A","UNLIKELY","N/A","TOP","No",true,null,false]
[27324,"MOD-008-1","R1.3.1.",null,"Same day and real-time.","2011-07-01",null,"Effective","Authorization/Approval; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","UNLIKELY","N/A","UNLIKELY","N/A","TOP","No",true,null,false]
[27325,"MOD-008-1","R1.3.2.",null,"Day-ahead and pre-schedule.","2011-07-01",null,"Effective","Authorization/Approval; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","UNLIKELY","N/A","UNLIKELY","N/A","TOP","No",true,null,false]
[27326,"MOD-008-1","R1.3.3.",null,"Beyond day-ahead and pre-schedule, up to thirteen months ahead.","2011-07-01",null,"Effective","Authorization/Approval; Documentations, Policies and Procedures; Quality Check/Verification","No Individual VRF Assigned","UNLIKELY","N/A","UNLIKELY","N/A","TOP","No",true,null,false]
[27327,"MOD-008-1","R2.","YES","Each Transmission Operator shall only use the components of uncertainty from R1.1 to establish TRM, and shall not include any of the components of Capacity Benefit Margin (CBM). Transmission capacity set aside for reserve sharing agreements can be included in TRM. [Time Horizon: Operations Planning]","2011-07-01",null,"Effective","Authorization/Approval; Documentations, Policies and Procedures; Quality Check/Verification","MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[27328,"MOD-008-1","R2.","YES","Each Transmission Operator shall only use the components of uncertainty from R1.1 to establish TRM, and shall not include any of the components of Capacity Benefit Margin (CBM). Transmission capacity set aside for reserve sharing agreements can be included in TRM. [Time Horizon: Operations Planning]","2011-07-01",null,"Effective","Documentations, Policies and Procedures","MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[27329,"MOD-008-1","R3.",null,"Each Transmission Operator shall make available its TRMID, and if requested, underlying documentation (if any) used to determine TRM, in the format used by the Transmission Operator, to any of the following who make a written request no more than 30 calendar days after receiving the request.  [Time Horizon: Operations Planning] \n• Transmission Service Providers\n• Reliability Coordinators\n• Planning Coordinators\n• Transmission Planner\n• Transmission Operators","2011-07-01",null,"Effective","Authorization/Approval; Documentations, Policies and Procedures; Quality Check/Verification","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[27330,"MOD-008-1","R4.",null,"Each Transmission Operator that maintains TRM shall establish TRM values in accordance with the TRMID at least once every 13 months. [Time Horizon: Operations Planning]","2011-07-01",null,"Effective","Documentations, Policies and Procedures","MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[27331,"MOD-008-1","R5.","YES","The Transmission Operator that maintains TRM shall provide the TRM values to its Transmission Service Provider(s) and Transmission Planner(s) no more than seven calendar days after a TRM value is initially established or subsequently changed. [Time Horizon: Operations Planning]","2011-07-01",null,"Effective","Authorization/Approval; Documentations, Policies and Procedures","MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[27332,"MOD-008-1","R5.","YES","The Transmission Operator that maintains TRM shall provide the TRM values to its Transmission Service Provider(s) and Transmission Planner(s) no more than seven calendar days after a TRM value is initially established or subsequently changed. [Time Horizon: Operations Planning]","2011-07-01",null,"Effective","Authorization/Approval; Communications","MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[26867,"MOD-015-0","R1.",null,"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\nsystem models, as appropriate, of Reliability Standard MOD-014-0_R1.",null,null,"Retired",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[26868,"MOD-015-0","R1.1.",null,"The Regional Reliability Organization(s) shall develop Interconnectionspecific dynamics system models for at least two timeframes (present or nearterm 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.",null,null,"Retired",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[26869,"MOD-015-0","R2.",null,"The Regional Reliability Organization(s) within each Interconnection shall develop 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 Interconnection’s schedule for submission.",null,null,"Retired",null,"N/A",null,"N/A",null,"N/A","RRO","No",false,null,false]
[26870,"MOD-015-0.1","R1.",null,"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.",null,null,"Retired",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[26871,"MOD-015-0.1","R1.1.",null,"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.",null,null,"Retired",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[26872,"MOD-015-0.1","R2.",null,"The Regional Reliability Organization(s) within each Interconnection shall develop 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 Interconnection’s schedule for submission.",null,null,"Retired",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[27352,"MOD-020-0","R1.",null,"The Load-Serving Entity, Transmission Planner, and Resource Planner shall each make 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.","2005-02-08","2020-12-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TP, RP, LSE","Yes",false,null,false]
[27356,"MOD-024-1","R1.",null,"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:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27357,"MOD-024-1","R1.1.",null,"Generating unit exemption criteria including documentation of those units that are exempt from a portion or all of these procedures.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27358,"MOD-024-1","R1.2.",null,"Criteria for reporting generating unit auxiliary loads.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27359,"MOD-024-1","R1.3.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27360,"MOD-024-1","R1.4.",null,"Periodicity and schedule of model and data verification and reporting.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27361,"MOD-024-1","R1.5.",null,"Information to be verified and reported:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27362,"MOD-024-1","R1.5.1.",null,"Seasonal gross and net Real Power generating capabilities.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27363,"MOD-024-1","R1.5.2.",null,"Real power requirements of auxiliary loads.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27364,"MOD-024-1","R1.5.3.",null,"Method of verification, including date and conditions.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[26873,"MOD-024-1","R2.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO, GOP, GO","Yes",false,null,false]
[26874,"MOD-024-1","R3.",null,"The Generator Owner shall follow its Regional Reliability Organization’s procedures for verifying and reporting its gross and net Real Power generating capability per R1.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO, GO","Yes",false,null,false]
[26875,"MOD-025-1","R1.",null,"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:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[26876,"MOD-025-1","R1.1.",null,"Generating unit exemption criteria including documentation of those units that are exempt from a portion or all of these procedures.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[26877,"MOD-025-1","R1.2.",null,"Criteria for reporting generating unit auxiliary loads.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[26878,"MOD-025-1","R1.3.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[26879,"MOD-025-1","R1.4.",null,"Periodicity and schedule of model and data verification and reporting.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[26880,"MOD-025-1","R1.5.",null,"Information to be reported:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27365,"MOD-025-1","R1.5.1.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27366,"MOD-025-1","R1.5.2.",null,"Verified Reactive Power limitations, such as generator terminal voltage limitations, shorted rotor turns, etc.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27367,"MOD-025-1","R1.5.3.",null,"Verified Reactive Power of auxiliary loads.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27368,"MOD-025-1","R1.5.4.",null,"Method of verification, including date and conditions.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[27369,"MOD-025-1","R2.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO, GOP, GO","Yes",false,null,false]
[27370,"MOD-025-1","R3.",null,"The Generator Owner shall follow its Regional Reliability Organization’s procedures for verifying and reporting its gross and net Reactive Power generating capability per R1.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO, GO","Yes",false,null,false]
[27371,"MOD-025-2","R1.",null,"Each Generator Owner shall provide its Transmission Planner with verification of the Real Power capability of its applicable Facilities as follows: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[27372,"MOD-025-2","R1.1.",null,"Verify the Real Power capability of its generating units in accordance with Attachment 1.","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[27373,"MOD-025-2","R1.2.",null,"Submit a completed Attachment 2 (or a form containing the same information as identified in Attachment 2) to its Transmission Planner within 90 calendar days of either (i) the date the data is recorded for a staged test; or (ii) the date the data is\nselected for verification using historical operational data.","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[27374,"MOD-025-2","R2.",null,"Each Generator Owner shall provide its Transmission Planner with verification of the Reactive Power capability of its applicable Facilities as follows: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[27375,"MOD-025-2","R2.1.",null,"Verify, in accordance with Attachment 1, (i) the Reactive Power capability of its generating units and (ii) the Reactive Power capability of its synchronous condenser units.","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[27376,"MOD-025-2","R2.2.",null,"Submit a completed Attachment 2 (or a form containing the same information as identified in Attachment 2) to its Transmission Planner within 90 calendar days of either (i) the date the data is recorded for a staged test; or (ii) the date the data is selected for verification using historical operational data.","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[27377,"MOD-025-2","R3.",null,"Each Transmission Owner shall provide its Transmission Planner with verification of the Reactive Power capability of its applicable Facilities as follows: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[27378,"MOD-025-2","R3.1.",null,"Verify, in accordance with Attachment 1, the Reactive Power capability of its synchronous condenser units.","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26881,"MOD-025-2","R3.2.",null,"Submit a completed Attachment 2 (or a form containing the same information as identified in Attachment 2) to its Transmission Planner within 90 calendar days of either (i) the date the data is recorded for a staged test; or (ii) the date the data is selected for verification using historical operational data.","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[26884,"MOD-026-1","R1.",null,"Each Transmission Planner shall provide the following requested information to the Generator Owner within 90 calendar days of receiving a written request : [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]\n Instructions on how to obtain the list of excitation control system or plant volt/var control function models that are acceptable to the Transmission Planner for use in dynamic simulation,\n Instructions on how to obtain the dynamic excitation control system or plant volt/var control function model library block diagrams and/or data sheets for models that are acceptable to the Transmission Planner, or\n Model data for any of the Generator Owner’s existing applicable unit specific excitation control system or plant volt/var control function contained in the Transmission Planner’s dynamic database from the current (in-use) models, including generator MVA base.","2014-07-01",null,"Effective",null,"LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP","No",false,null,false]
[26885,"MOD-026-1","R2.",null,"Each Generator Owner shall provide for each applicable unit, a verified generator excitation control system or plant volt/var control function model, including documentation and data (as specified in Part 2.1) to its Transmission Planner in accordance with the periodicity specified in MOD-026 Attachment 1. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2018-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[26886,"MOD-026-1","R2.1.",null,"Each applicable unit’s model shall be verified by the Generator Owner using one or more models acceptable to the Transmission Planner. Verification for individual units less than 20 MVA (gross nameplate rating) in a generating plant (per Section 4.2.1.2, 4.2.2.2, or 4.2.3.2) may be performed using either individual unit or aggregate unit model(s), or both. Each verification shall include the following","2018-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27379,"MOD-026-1","R2.1.1.",null,"Documentation demonstrating the applicable unit’s model response matches the recorded response for a voltage excursion from either a staged test or a measured system disturbance,","2018-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27380,"MOD-026-1","R2.1.2.",null,"Manufacturer, model number (if available), and type of the excitation control system including, but not limited to static, AC brushless, DC rotating, and/or the plant volt/var control function (if installed),","2018-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27381,"MOD-026-1","R2.1.3.",null,"Model structure and data including, but not limited to reactance, time constants, saturation factors, total rotational inertia, or equivalent data for the generator,","2018-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27382,"MOD-026-1","R2.1.4.",null,"Model structure and data for the excitation control system, including the closed loop voltage regulator if a closed loop voltage regulator is installed or the model structure and data for the plant volt/var control function system,","2018-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27383,"MOD-026-1","R2.1.5.",null,"Compensation settings (such as droop, line drop, differential compensation), if used, and","2018-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27384,"MOD-026-1","R2.1.6.",null,"Model structure and data for power system stabilizer, if so equipped.","2018-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27385,"MOD-026-1","R3.",null,"Each Generator Owner shall provide a written response to its Transmission Planner within 90 calendar days of receiving one of the following items for an applicable unit:\n Written notification from its Transmission Planner (in accordance with Requirement R6) that the excitation control system or plant volt/var control function model is not usable,\n Written comments from its Transmission Planner identifying technical concerns with the verification documentation related to the excitation control system or plant volt/var control function model, or\n Written comments and supporting evidence from its Transmission Planner indicating that the simulated excitation control system or plant volt/var control function model response did not match the recorded response to a transmission system event.\nThe written response shall contain either the technical basis for maintaining the current model, the model changes, or a plan to perform model verification3 (in accordance with Requirement R2). [Violation Risk Factor: Lower] [Time Horizon: Operations\nPlanning]","2014-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27386,"MOD-026-1","R4.",null,"Each Generator Owner shall provide revised model data or plans to perform model verification4 (in accordance with Requirement R2) for an applicable unit to its Transmission Planner within 180 calendar days of making changes to the excitation control system or plant volt/var control function that alter the equipment response characteristic.5 [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2014-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27387,"MOD-026-1","R5.",null,"Each Generator Owner shall provide a written response to its Transmission Planner, within 90 calendar days following receipt of a technically justified6 unit request from the Transmission Planner to perform a model review of a unit or plant that includes one\nof the following: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]\n Details of plans to verify the model (in accordance with Requirement R2), or\n Corrected model data including the source of revised model data such as discovery of manufacturer test values to replace generic model data or updating of data parameters based on an on-site review of the equipment.","2014-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27389,"MOD-026-1","R6.",null,"Each Transmission Planner shall provide a written response to the Generator Owner within 90 calendar days of receiving the verified excitation control system or plant volt/var control function model information in accordance with Requirement R2 that\nthe model is usable (meets the criteria specified in Parts 6.1 through 6.3) or is not usable.","2014-07-01",null,"Effective",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","LIKELY","MEDIUM (Moderate Controls)","TP","No",false,null,false]
[27390,"MOD-026-1","R6.1.","YES","The excitation control system or plant volt/var control function model initializes to compute Real-Time Applications data without error,","2014-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP","No",false,null,false]
[27391,"MOD-026-1","R6.1.","YES","The excitation control system or plant volt/var control function model initializes to compute Real-Time Applications data without error,","2014-07-01",null,"Effective",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","LIKELY","MEDIUM (Moderate Controls)","TP","No",false,null,false]
[27393,"MOD-026-1","R6.2.","YES","A no-disturbance simulation results in negligible transients, and","2014-07-01",null,"Effective",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","LIKELY","MEDIUM (Moderate Controls)","TP","No",false,null,false]
[27392,"MOD-026-1","R6.2.","YES","A no-disturbance simulation results in negligible transients, and","2014-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP","No",false,null,false]
[27395,"MOD-026-1","R6.3.","YES","For an otherwise stable simulation, a disturbance simulation results in the excitation control and plant volt/var control function model exhibiting positive damping. If the model is not usable, the Transmission Planner shall provide a technical description of why the model is not usable. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2014-07-01",null,"Effective",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","LIKELY","MEDIUM (Moderate Controls)","TP","No",false,null,false]
[27394,"MOD-026-1","R6.3.","YES","For an otherwise stable simulation, a disturbance simulation results in the excitation control and plant volt/var control function model exhibiting positive damping. If the model is not usable, the Transmission Planner shall provide a technical\ndescription of why the model is not usable. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2014-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP","No",false,null,false]
[27397,"MOD-027-1","R1.",null,"Each Transmission Planner shall provide the following requested information to the Generator Owner within 90 calendar days of receiving a written request: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]\n Instructions on how to obtain the list of turbine/governor and load control or active power/frequency control system models that are acceptable to the Transmission Planner for use in dynamic simulation,\n Instructions on how to obtain the dynamic turbine/governor and load control or active power/frequency control function model library block diagrams and/or data sheets for models that are acceptable to the Transmission Planner, or\n Model data for any of the Generator Owner’s existing applicable unit specific turbine/governor and load control or active power/frequency control system contained in the Transmission Planner’s dynamic database from the current (in-use) models.","2014-07-01",null,"Effective",null,"LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP","No",false,null,false]
[27398,"MOD-027-1","R2.",null,"Each Generator Owner shall provide, for each applicable unit, a verified turbine/governor and load control or active power/frequency control model, including documentation and data (as specified in Part 2.1) to its Transmission Planner in\naccordance with the periodicity specified in MOD-027 Attachment 1. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2018-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27399,"MOD-027-1","R2.1.",null,"Each applicable unit’s model shall be verified by the Generator Owner using one or more models acceptable to the Transmission Planner. Verification for individual units rated less than 20 MVA (gross nameplate rating) in a generating plant (per Section 4.2.1.2, 4.2.2.2, or 4.2.3.2) may be performed using either individual unit or aggregate unit model(s) or both. Each verification shall include\nthe following:","2018-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27400,"MOD-027-1","R2.1.1.",null,"Documentation comparing the applicable unit’s MW model response to the recorded MW response for either:\n A frequency excursion from a system disturbance that meets MOD-027 Attachment 1 Note 1 with the applicable unit on-line,\n A speed governor reference change with the applicable unit online,\nor\n A partial load rejection test,2","2018-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27401,"MOD-027-1","R2.1.2.",null,"Type of governor and load control or active power control/frequency control1 equipment,","2018-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27402,"MOD-027-1","R2.1.3.",null,"A description of the turbine (e.g. for hydro turbine - Kaplan, Francis, or Pelton; for steam turbine - boiler type, normal fuel type, and turbine type; for gas turbine - the type and manufacturer; for variable energy plant - type and manufacturer),","2018-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27403,"MOD-027-1","R2.1.4.",null,"Model structure and data for turbine/governor and load control or active power/frequency control, and","2018-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27404,"MOD-027-1","R2.1.5.",null,"Representation of the real power response effects of outer loop controls (such as operator set point controls, and load control but excluding AGC control) that would override the governor response (including blocked or nonfunctioning governors or modes of operation that limit Frequency Response), if applicable.","2018-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27405,"MOD-027-1","R3.",null,"Each Generator Owner shall provide a written response to its Transmission Planner within 90 calendar days of receiving one of the following items for an applicable unit.\n Written notification, from its Transmission Planner (in accordance with Requirement R5) that the turbine/governor and load control or active power/frequency control model is not “usable,”\n Written comments from its Transmission Planner identifying technical concerns with the verification documentation related to the turbine/governor and load control or active power/frequency control model, or\n Written comments and supporting evidence from its Transmission Planner indicating that the simulated turbine/governor and load control or active power/frequency control response did not approximate the recorded response for three or more transmission system events. The written response shall contain either the technical basis for maintaining the current model, the model changes, or a plan to perform model verification3 (in accordance with Requirement R2). [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2014-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27406,"MOD-027-1","R4.",null,"Each Generator Owner shall provide revised model data or plans to perform model verification4 (in accordance with Requirement R2) for an applicable unit to its Transmission Planner within 180 calendar days of making changes to the turbine/governor and load control or active power/frequency control system that alter the equipment response characteristic5. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2014-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27408,"MOD-027-1","R5.",null,"Each Transmission Planner shall provide a written response to the Generator Owner within 90 calendar days of receiving the turbine/governor and load control or active power/frequency control system verified model information in accordance with Requirement R2 that the model is usable (meets the criteria specified in Parts 5.1 through 5.3) or is not usable.","2014-07-01",null,"Effective",null,"MEDIUM","UNLIKELY","LOW (Limited Controls Required)","LIKELY","MEDIUM (Moderate Controls)","TP","No",false,null,false]
[27409,"MOD-027-1","R5.1.",null,"The turbine/governor and load control or active power/frequency control function model initializes to compute Real-Time Applications data without error,","2014-07-01",null,"Effective",null,"MEDIUM","UNLIKELY","LOW (Limited Controls Required)","LIKELY","MEDIUM (Moderate Controls)","TP","No",false,null,false]
[27410,"MOD-027-1","R5.2.",null,"A no-disturbance simulation results in negligible transients, and","2014-07-01",null,"Effective",null,"MEDIUM","UNLIKELY","LOW (Limited Controls Required)","LIKELY","MEDIUM (Moderate Controls)","TP","No",false,null,false]
[27411,"MOD-027-1","R5.3.",null,"For an otherwise stable simulation, a disturbance simulation results in the turbine/governor and load control or active power/frequency control model exhibiting positive damping. If the model is not usable, the Transmission Planner shall provide a technical description of why the model is not usable. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2014-07-01",null,"Effective",null,"MEDIUM","UNLIKELY","LOW (Limited Controls Required)","LIKELY","MEDIUM (Moderate Controls)","TP","No",false,null,false]
[27412,"MOD-028-2","R1.","YES","Each Transmission Service Provider shall include in its Available Transfer Capability Implementation Document (ATCID), at a minimum, the following information relative to its methodology for determining Total Transfer Capability (TTC): [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2013-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27413,"MOD-028-2","R1.1.","YES","Information describing how the selected methodology has been implemented, in such detail that, given the same information used by the Transmission Operator, the results of the TTC calculations can be validated.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27414,"MOD-028-2","R1.2.","YES","A description of the manner in which the Transmission Operator will account for Interchange Schedules in the calculation of TTC.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27415,"MOD-028-2","R1.3.","YES","Any contractual obligations for allocation of TTC.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27416,"MOD-028-2","R1.4.","YES","A description of the manner in which Contingencies are identified for use in the TTC process.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27417,"MOD-028-2","R1.5.","YES","The following information on how source and sink for transmission service is accounted for in ATC calculations including:","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27418,"MOD-028-2","R1.5.1.","YES","Define if the source used for Available Transfer Capability (ATC) calculations is obtained from the source field or the Point of Receipt (POR) field of the transmission reservation","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27419,"MOD-028-2","R1.5.2.","YES","Define if the sink used for ATC calculations is obtained from the sink field or the Point of Delivery (POD) field of the transmission reservation","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27420,"MOD-028-2","R1.5.3.","YES","The source/sink or POR/POD identification and mapping to the model.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27421,"MOD-028-2","R1.5.4.","YES","If the Transmission Service Provider’s ATC calculation process involves a grouping of generation, the ATCID must identify how these generators participate in the group.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27451,"MOD-028-2","R10.","YES","When calculating firm ATC for an ATC Path for a specified period, the Transmission Service Provider shall utilize the following algorithm: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning] See Standard for Formula","2013-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27452,"MOD-028-2","R11.","YES","When calculating non-firm ATC for a ATC Path for a specified period, the Transmission Service Provider shall use the following algorithm: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning] See Standard for Formula","2013-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27422,"MOD-028-2","R2.","YES","When calculating TTC for ATC Paths, the Transmission Operator shall use a Transmission model that contains all of the following: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2013-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27423,"MOD-028-2","R2.1.","YES","Modeling data and topology of its Reliability Coordinator’s area of responsibility. Equivalent representation of radial lines and facilities 161 kV or below is allowed.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27424,"MOD-028-2","R2.2.","YES","Modeling data and topology (or equivalent representation) for immediately adjacent and beyond Reliability Coordination areas.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27425,"MOD-028-2","R2.3.","YES","Facility Ratings specified by the Generator Owners and Transmission Owners.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27426,"MOD-028-2","R3.","YES","When calculating TTCs for ATC Paths, the Transmission Operator shall include the following data for the Transmission Service Provider’s area. The Transmission Operator shall also include the following data associated with Facilities that are explicitly represented in the Transmission model, as provided by adjacent Transmission Service Providers and any other Transmission Service Providers with which coordination agreements have been executed: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2013-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27427,"MOD-028-2","R3.1.","YES","For TTCs, use the following (as well as any other values and additional parameters as specified in the ATCID):","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27428,"MOD-028-2","R3.1.1.","YES","Expected generation and Transmission outages, additions, and retirements, included as specified in the ATCID.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27429,"MOD-028-2","R3.1.2.","YES","A daily or hourly load forecast for TTCs used in current-day and next-day ATC calculations.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27430,"MOD-028-2","R3.1.3.","YES","A daily load forecast for TTCs used in ATC calculations for days two through 31.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27431,"MOD-028-2","R3.1.4.","YES","A monthly load forecast for TTCs used in ATC calculations for months two through 13 months TTCs.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27432,"MOD-028-2","R3.1.5.","YES","Unit commitment and dispatch order, to include all designated network resources and other resources that are committed or have the legal obligation to run, (within or out of economic dispatch) as they are expected to run.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27433,"MOD-028-2","R4.","YES","When calculating TTCs for ATC Paths, the Transmission Operator shall meet all of the following conditions: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2013-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27434,"MOD-028-2","R4.1.","YES","Use all Contingencies meeting the criteria described in the ATCID.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27435,"MOD-028-2","R4.2.","YES","Respect any contractual allocations of TTC.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27436,"MOD-028-2","R4.3.","YES","Include, for each time period, the Firm Transmission Service expected to be scheduled as specified in the ATCID (filtered to reduce or eliminate duplicate impacts from transactions using Transmission service from multiple Transmission Service Providers) for the Transmission Service Provider, all adjacent Transmission Service Providers, and any Transmission Service Providers with which coordination agreements have been executed modeling the source and sink as follows:                                                                                                                                           - If the source, as specified in the ATCID, has been identified in the reservation and it is discretely modeled in the Transmission Service Provider’s Transmission model, use the discretely modeled point as the source.                                                                                        - If the source, as specified in the ATCID, has been identified in the reservation and the point can be mapped to an “equivalence” or “aggregate representation” in the Transmission Service Provider’s Transmission model, use the modeled equivalence or aggregate as the source.                                                                                                                                                                                                                         - If the source, as specified in the ATCID, has been identified in the reservation and the point cannot be mapped to a discretely modeled point, an “equivalence,” or an “aggregate representation” in the Transmission Service Provider’s Transmission model, use the immediately adjacent Balancing Authority associated with the Transmission Service Provider from which the power is to be received as the source.                                                                                                                                                                                                                             - If the source, as specified in the ATCID, has not been identified in the reservation, use the immediately adjacent Balancing Authority associated with the Transmission Service Provider from which the power is to be received as the source.                                                                                                                                                                   - If the sink, as specified in the ATCID, has been identified in the reservation and it is discretely modeled in the Transmission Service Provider’s Transmission model, use the discretely modeled point shall as the sink.                                                                                                     - If the sink, as specified in the ATCID, has been identified in the reservation and the point can be mapped to an “equivalence” or “aggregate representation” in the Transmission Service Provider’s Transmission model, use the modeled equivalence or aggregate as the sink.                                                                                                                                                                                                                                 - If the sink, as specified in the ATCID, has been identified in the reservation and the point can not be mapped to a discretely modeled point, an “equivalence,” or an “aggregate representation” in the Transmission Service Provider’s Transmission model, use the immediately adjacent Balancing Authority associated with the Transmission Service Provider to which the power is to be delivered as the sink.                                                                                                                                                                                                                                                     - If the sink, as specified in the ATCID, has not been identified in the reservation, use the immediately adjacent Balancing Authority associated with the Transmission Service Provider to which the power is being delivered as the sink.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27437,"MOD-028-2","R5.","YES","Each Transmission Operator shall establish TTC for each ATC Path as defined below: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2013-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27438,"MOD-028-2","R5.1.","YES","At least once within the seven calendar days prior to the specified period for TTCs used in hourly and daily ATC calculations.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27439,"MOD-028-2","R5.2.","YES","At least once per calendar month for TTCs used in monthly ATC calculations.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27440,"MOD-028-2","R5.3.","YES","Within 24 hours of the unexpected outage of a 500 kV or higher transmission Facility or a transformer with a low-side voltage of 200 kV or higher for TTCs in effect during the anticipated duration of the outage, provided such outage is expected to last 24 hours or longer.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27441,"MOD-028-2","R6.","YES","Each Transmission Operator shall establish TTC for each ATC Path using the following process: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2013-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27442,"MOD-028-2","R6.1.","YES","Determine the incremental Transfer Capability for each ATC Path by increasing generation and/or decreasing load within the source Balancing Authority area and decreasing generation and/or increasing load within the sink Balancing Authority area until either:                                                                                                                          - A System Operating Limit is reached on the Transmission Service Provider’s system, or                                          - A SOL is reached on any other adjacent system in the Transmission model that is not on the study path and the distribution factor is 5% or greater1.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27443,"MOD-028-2","R6.2.","YES","If the limit in step R6.1 can not be reached by adjusting any combination of load or generation, then set the incremental Transfer Capability by the results of the case where the maximum adjustments were applied.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27444,"MOD-028-2","R6.3.","YES","Use (as the TTC) the lesser of:                                                                                                                                   − The sum of the incremental Transfer Capability and the impacts of Firm Transmission Services, as specified in the Transmission Service Provider’s ATCID, that were included in the study model, or                                             − The sum of Facility Ratings of all ties comprising the ATC Path.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27445,"MOD-028-2","R6.4.","YES","For ATC Paths whose capacity uses jointly-owned or allocated Facilities, limit TTC for each Transmission Service Provider so the TTC does not exceed each Transmission Service Provider’s contractual rights.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27446,"MOD-028-2","R7.","YES","The Transmission Operator shall provide the Transmission Service Provider of that ATC Path with the most current value for TTC for that ATC Path no more than: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2013-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27447,"MOD-028-2","R7.1.","YES","One calendar day after its determination for TTCs used in hourly and daily ATC calculations.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27448,"MOD-028-2","R7.2.","YES","Seven calendar days after its determination for TTCs used in monthly ATC calculations.","2013-10-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27449,"MOD-028-2","R8.","YES","When calculating Existing Transmission Commitments (ETCs) for firm commitments (ETCF) for all time periods for an ATC Path the Transmission Service Provider shall use the following algorithm: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning] See Standard for Formula","2013-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27450,"MOD-028-2","R9.","YES","When calculating ETC for non-firm commitments (ETCNF) for all time periods for an ATC Path the Transmission Service Provider shall use the following algorithm: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning] See Standard for Formula","2013-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27540,"MOD-029-2a","R1.","YES","When calculating TTCs for ATC Paths, the Transmission Operator shall use a Transmission model which satisfies the following requirements: [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27541,"MOD-029-2a","R1.","YES","When calculating TTCs for ATC Paths, the Transmission Operator shall use a Transmission model which satisfies the following requirements: [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27542,"MOD-029-2a","R1.1.","YES","The model  utilizes data and assumptions consistent with the time period being studied and that meets the following criteria:","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27543,"MOD-029-2a","R1.1.","YES","The model  utilizes data and assumptions consistent with the time period being studied and that meets the following criteria:","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27544,"MOD-029-2a","R1.1.1.","YES","Includes at least:","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27545,"MOD-029-2a","R1.1.1.","YES","Includes at least:","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27546,"MOD-029-2a","R1.1.1.1.","YES","The Transmission Operator area. Equivalent representation of radial lines and facilities 161kV or below is allowed.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27547,"MOD-029-2a","R1.1.1.1.","YES","The Transmission Operator area. Equivalent representation of radial lines and facilities 161kV or below is allowed.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27548,"MOD-029-2a","R1.1.1.2.","YES","All Transmission Operator areas contiguous with its own Transmission Operator area. (Equivalent representation is allowed.)","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27549,"MOD-029-2a","R1.1.1.2.","YES","All Transmission Operator areas contiguous with its own Transmission Operator area. (Equivalent representation is allowed.)","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27550,"MOD-029-2a","R1.1.1.3.","YES","Any other Transmission Operator area linked to the Transmission Operator’s area by joint operating agreement.  (Equivalent representation is allowed.)","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27551,"MOD-029-2a","R1.1.1.3.","YES","Any other Transmission Operator area linked to the Transmission Operator’s area by joint operating agreement.  (Equivalent representation is allowed.)","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27569,"MOD-029-2a","R1.1.10.","YES","Includes any other modeling requirements or criteria specified in the ATCID.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27568,"MOD-029-2a","R1.1.10.","YES","Includes any other modeling requirements or criteria specified in the ATCID.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27552,"MOD-029-2a","R1.1.2.","YES","Models all system Elements as in-service for the assumed initial conditions.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27553,"MOD-029-2a","R1.1.2.","YES","Models all system Elements as in-service for the assumed initial conditions.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27555,"MOD-029-2a","R1.1.3.","YES","Models all generation (may be either a single generator or multiple generators) that is greater than 20 MVA at the point of interconnection in the studied area.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27554,"MOD-029-2a","R1.1.3.","YES","Models all generation (may be either a single generator or multiple generators) that is greater than 20 MVA at the point of interconnection in the studied area.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27557,"MOD-029-2a","R1.1.4.","YES","Models phase shifters in non-regulating mode, unless otherwise specified in the Available Transfer Capability Implementation Document (ATCID).","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27556,"MOD-029-2a","R1.1.4.","YES","Models phase shifters in non-regulating mode, unless otherwise specified in the Available Transfer Capability Implementation Document (ATCID).","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27559,"MOD-029-2a","R1.1.5.","YES","Uses Load forecast by Balancing Authority.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27558,"MOD-029-2a","R1.1.5.","YES","Uses Load forecast by Balancing Authority.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27560,"MOD-029-2a","R1.1.6.","YES","Uses Transmission Facility additions and retirements.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27561,"MOD-029-2a","R1.1.6.","YES","Uses Transmission Facility additions and retirements.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27563,"MOD-029-2a","R1.1.7.","YES","Uses Generation Facility additions and retirements.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27562,"MOD-029-2a","R1.1.7.","YES","Uses Generation Facility additions and retirements.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27564,"MOD-029-2a","R1.1.8.","YES","Uses Remedial Action Scheme (RAS) models where currently existing or projected for implementation within the studied time horizon.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27565,"MOD-029-2a","R1.1.8.","YES","Uses Remedial Action Scheme (RAS) models where currently existing or projected for implementation within the studied time horizon.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27566,"MOD-029-2a","R1.1.9.","YES","Models series compensation for each line at the expected operating level unless specified otherwise in the ATCID.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27567,"MOD-029-2a","R1.1.9.","YES","Models series compensation for each line at the expected operating level unless specified otherwise in the ATCID.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27570,"MOD-029-2a","R1.2.","YES","Uses Facility Ratings as provided by the Transmission Owner and Generator Owner","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27571,"MOD-029-2a","R1.2.","YES","Uses Facility Ratings as provided by the Transmission Owner and Generator Owner","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27573,"MOD-029-2a","R2.","YES","The Transmission Operator shall use the following process to determine TTC: [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27575,"MOD-029-2a","R2.1.","YES","Except where otherwise specified within MOD-029-2a, adjust base case generation and Load levels within the updated power flow model to determine the TTC (maximum flow or reliability limit) that can be simulated on the ATC Path while at the same time satisfying all planning criteria contingencies as follows:","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27577,"MOD-029-2a","R2.1.1.","YES","When modeling normal conditions, all Transmission Elements will be modeled at or below 100% of their continuous rating.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27579,"MOD-029-2a","R2.1.2.","YES","When modeling contingencies the system shall demonstrate transient, dynamic and voltage stability, with no Transmission Element modeled above its Emergency Rating.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27581,"MOD-029-2a","R2.1.3.","YES","Uncontrolled separation shall not occur.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27583,"MOD-029-2a","R2.2.","YES","Where it is impossible to actually simulate a reliability-limited flow in a direction counter to prevailing flows (on an alternating current Transmission line), set the TTC for the non-prevailing direction equal to the TTC in the prevailing direction. If the TTC in the prevailing flow direction is dependent on a Remedial Action Scheme (RAS), set the TTC for the non-prevailing flow direction equal to the greater of the maximum flow that can be simulated in the non-prevailing flow direction or the maximum TTC that can be achieved in the prevailing flow direction without use of a RAS.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27585,"MOD-029-2a","R2.3.","YES","For an ATC Path whose capacity is limited by contract, set TTC on the ATC Path at the lesser of the maximum allowable contract capacity or the reliability limit as determined by R2.1.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27587,"MOD-029-2a","R2.4.","YES","For an ATC Path whose TTC varies due to simultaneous interaction with one or more other paths, develop a nomogram describing the interaction of the paths and the resulting TTC under specified conditions.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27589,"MOD-029-2a","R2.5.","YES","The Transmission Operator shall identify when the TTC for the ATC Path being studied has an adverse impact on the TTC value of any existing path.  Do this by modeling the flow on the path being studied at its proposed new TTC level simultaneous with the flow on the existing path at its TTC level while at the same time honoring the reliability criteria outlined in R2.1.   The Transmission Operator shall include the resolution of this adverse impact in its study report for the ATC Path.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27591,"MOD-029-2a","R2.6.","YES","Where multiple ownership of Transmission rights exists on an ATC Path, allocate TTC of that ATC Path in accordance with the contractual agreement made by the multiple owners of that ATC Path.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27593,"MOD-029-2a","R2.7.","YES","For ATC Paths whose path rating, adjusted for seasonal variance, was established, known and used in operation since January 1, 1994, and no action has been taken to have the path rated using a different method, set the TTC at that previously established amount.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27595,"MOD-029-2a","R2.8.","YES","Create a study report that describes the steps above that were undertaken (R2.1 - R2.7), including the contingencies and assumptions used, when determining the TTC and the results of the study. Where three phase fault damping is used to determine stability limits, that report shall also identify the percent used and include justification for use unless specified otherwise in the ATCID.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27597,"MOD-029-2a","R3.","YES","Each Transmission Operator shall establish the TTC at the lesser of the value calculated in R2 or any System Operating Limit (SOL) for that ATC Path.  [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27599,"MOD-029-2a","R4.","YES","Within seven calendar days of the finalization of the study report, the Transmission Operator shall make available to the Transmission Service Provider of the ATC Path, the most current value for TTC and the TTC study report documenting the assumptions used and steps taken in determining the current value for TTC for that ATC Path.  [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27600,"MOD-029-2a","R5.",null,"When calculating ETC for firm Existing Transmission Commitments (ETCF) for a specified period for an ATC Path, the Transmission Service Provider shall use the algorithm below:  [Time Horizon: Operations Planning] \nETCF = NLF + NITSF + GFF + PTPF + RORF + OSF\nWhere:\nNLF is the firm capacity set aside to serve peak Native Load forecast commitments for the time period being calculated, to include losses, and Native Load growth, not otherwise included in Transmission Reliability Margin or Capacity Benefit Margin.\nNITSF is the firm capacity reserved for Network Integration Transmission Service serving Load, to include losses, and Load growth, not otherwise included in Transmission Reliability Margin or Capacity Benefit Margin.\nGFF is the firm capacity set aside for grandfathered Transmission Service and contracts for energy and/or Transmission Service, where executed prior to theeffective date of a Transmission Service Provider’s Open Access Transmission Tariff or “safe harbor tariff.”\nPTPF is the firm capacity reserved for confirmed Point-to-Point Transmission Service.\nRORF is the firm capacity reserved for Roll-over rights for contracts granting Transmission Customers the right of first refusal to take or continue to take Transmission Service when the Transmission Customer’s Transmission Service contract expires or is eligible for renewal.\nOSF is the firm capacity reserved for any other service(s), contract(s), or agreement(s) not specified above using Firm Transmission Service as specified in the ATCID.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27601,"MOD-029-2a","R6.",null,"When calculating ETC for non-firm Existing Transmission Commitments (ETCNF) for all time horizons for an ATC Path the Transmission Service Provider shall use the following algorithm: [Time Horizon: Operations Planning] \n    ETCNF = NITSNF + GFNF + PTPNF + OSNF\nWhere:\nNITSNF is the non-firm capacity set aside for Network Integration Transmission Service serving Load (i.e., secondary service), to include losses, and load growth not otherwise included in Transmission Reliability Margin or Capacity Benefit Margin.\nGFNF is the non-firm capacity set aside for grandfathered Transmission Service and contracts for energy and/or Transmission Service, where executed prior to the effective date of a Transmission Service Provider’s Open Access Transmission Tariff or “safe harbor tariff.”\nPTPNF is non-firm capacity reserved for confirmed Point-to-Point Transmission Service.\nOSNF is the non-firm capacity reserved for any other service(s), contract(s), or agreement(s) not specified above using non-firm transmission service as specified in the ATCID.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27602,"MOD-029-2a","R7.",null,"When calculating firm ATC for an ATC Path  for a specified period, the Transmission Service Provider shall use the following algorithm:  [Time Horizon: Operations Planning] \nATCF = TTC – ETCF – CBM – TRM + PostbacksF + counterflowsF\nWhere\nATCF is the firm Available Transfer Capability for the ATC Path for that period.\nTTC is the Total Transfer Capability of the ATC Path for that period.\nETCF is the sum of existing firm commitments for the ATC Path during that period.\nCBM is the Capacity Benefit Margin for the ATC Path during that period.\nTRM is the Transmission Reliability Margin for the ATC Path during that period.\nPostbacksF are changes to firm Available Transfer Capability due to a change in the use of Transmission Service for that period, as defined in Business Practices.\ncounterflowsF are adjustments to firm Available Transfer Capability as determined by the Transmission Service Provider and specified in their ATCID.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27603,"MOD-029-2a","R8.",null,"When calculating non-firm ATC for an ATC Path for a specified period, the Transmission Service Provider shall use the following algorithm:[Time Horizon: Operations Planning] See Standard for Formula\nATCNF = TTC – ETCF – ETCNF – CBMS – TRMU + PostbacksNF + counterflowsNF\nWhere:\nATCNF is the non-firm Available Transfer Capability for the ATC Path for that period.\nTTC is the Total Transfer Capability of the ATC Path for that period.\nETCF is the sum of existing firm commitments for the ATC Path during that period.\nETCNF is the sum of existing non-firm commitments for the ATC Path during that period.\nCBMS is the Capacity Benefit Margin for the ATC Path that has been scheduled during that period.\nTRMU is the Transmission Reliability Margin for the ATC Path that has not been released for sale (unreleased) as non-firm capacity by the Transmission Service Provider during that period.\nPostbacksNF are changes to non-firm Available Transfer Capability due to a change in the use of Transmission Service for that period, as defined in Business Practices.\ncounterflowsNF are adjustments to non-firm Available Transfer Capability as determined by the Transmission Service Provider and specified in its ATCID.","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27669,"MOD-030-3","R1.","YES","The Transmission Service Provider shall include in its “Available Transfer Capability Implementation Document” (ATCID):  [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"N/A",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27670,"MOD-030-3","R1.1.","YES","The criteria used by the Transmission Operator to identify sets of Transmission Facilities as Flowgates that are to be considered in Available Flowgate Capability (AFC) calculations.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27671,"MOD-030-3","R1.2.","YES","The following information on how source and sink for transmission service is accounted for in AFC calculations including:","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27672,"MOD-030-3","R1.2.1.","YES","Define if the source used for AFC calculations is obtained from the source field or the Point of Receipt (POR) field of the transmission reservation.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27673,"MOD-030-3","R1.2.2.","YES","Define if the sink used for AFC calculations is obtained from the sink field or the Point of Delivery (POD) field of the transmission reservation.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27674,"MOD-030-3","R1.2.3.","YES","The source/sink or POR/POD identification and mapping to the model.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27675,"MOD-030-3","R1.2.4.","YES","If the Transmission Service Provider’s AFC calculation process involves a grouping of generators, the ATCID must identify how these generators participate in the group.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27722,"MOD-030-3","R10.","YES","Each Transmission Service Provider shall recalculate AFC, utilizing the updated models described in R3.2, R3.3, and R5, at a minimum on the following frequency, unless none of the calculated values identified in the AFC equation have changed: [Violation Risk Factor: To Be Determined] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"N/A",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27723,"MOD-030-3","R10.1.","YES","For hourly AFC, once per hour. Transmission Service Providers are allowed up to 175 hours per calendar year during which calculations are not required to be performed, despite a change in a calculated value identified in the AFC equation.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27724,"MOD-030-3","R10.2.","YES","For daily AFC, once per day.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27725,"MOD-030-3","R10.3.","YES","For monthly AFC, once per week.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27726,"MOD-030-3","R11.","YES","When converting Flowgate AFCs to ATCs for ATC Paths, the Transmission Service Provider shall convert those values based on the following algorithm: [Time Horizon: Operations Planning] See Standard for Formula","2017-04-01",null,"Effective",null,"N/A",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27676,"MOD-030-3","R2.","YES","The Transmission Operator shall perform the following: [Violation Risk Factor: To Be Determined] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"N/A",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27677,"MOD-030-3","R2.1.","YES","Include Flowgates used in the AFC process based, at a minimum, on the following criteria:","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27678,"MOD-030-3","R2.1.1.","YES","Results of a first Contingency transfer analysis for ATC Paths internal to a Transmission Operator’s system up to the path capability such that at a minimum the first three limiting Elements and their worst associated Contingency combinations with an OTDF of at least 5% and within the Transmission Operator’s system are included as Flowgates.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27679,"MOD-030-3","R2.1.1.1.","YES","Use first Contingency criteria consistent with those first Contingency criteria used in planning of operations for the applicable time periods, including use of Remedial Action Schemes.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27680,"MOD-030-3","R2.1.1.2.","YES","Only the most limiting element in a series configuration needs to be included as a Flowgate.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27681,"MOD-030-3","R2.1.1.3.","YES","If any limiting element is kept within its limit for its associated worst Contingency by operating within the limits of another Flowgate, then no new Flowgate needs to be established for such limiting elements or Contingencies.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27682,"MOD-030-3","R2.1.2.","YES","Results of a first Contingency transfer analysis from all adjacent Balancing Authority source and sink (as defined in the ATCID) combinations up to the path capability such that at a minimum the first three limiting Elements and their worst associated Contingency combinations with an Outage Transfer Distribution Factor (OTDF) of at least 5% and within the Transmission Operator’s system are included as Flowgates unless the interface between such adjacent Balancing Authorities is accounted for using another ATC methodology.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27683,"MOD-030-3","R2.1.2.1.","YES","Use first Contingency criteria consistent with those first Contingency criteria used in planning of operations for the applicable time periods, including use of Remedial Action Schemes.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27684,"MOD-030-3","R2.1.2.2.","YES","Only the most limiting element in a series configuration needs to be included as a Flowgate.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27685,"MOD-030-3","R2.1.2.3.","YES","If any limiting element is kept within its limit for its associated worst Contingency by operating within the limits of another Flowgate, then no new Flowgate needs to be established for such limiting elements or Contingencies.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27686,"MOD-030-3","R2.1.3.","YES","Any limiting Element/Contingency combination at least within its Reliability Coordinator’s Area that has been subjected to an Interconnection-wide congestion management procedure within the last 12 months, unless the limiting Element/Contingency combination is accounted for using another ATC methodology or was created to address temporary operating conditions.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27687,"MOD-030-3","R2.1.4.","YES","Any limiting Element/Contingency combination within the Transmission model that has been requested to be included by any other Transmission Service Provider using the Flowgate Methodology or Area Interchange Methodology, where:","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27688,"MOD-030-3","R2.1.4.1.","YES","The coordination of the limiting Element/Contingency combination is not already addressed through a different methodology, and \n- Any generator within the Transmission Service Provider’s area has at least a 5% Power Transfer Distribution Factor (PTDF) or Outage Transfer Distribution Factor (OTDF) impact on the Flowgate when delivered to the aggregate load of its own area, or\n- A transfer from any Balancing Area within the Transmission Service Provider’s area to a Balancing Area adjacent has at least a 5% PTDF or OTDF impact on the Flowgate. \n- The Transmission Operator may utilize distribution factors less than 5% if desired.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27689,"MOD-030-3","R2.1.4.2.","YES","The limiting Element/Contingency combination is included in the requesting Transmission Service Provider’s methodology.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27690,"MOD-030-3","R2.2.","YES","At a minimum, establish a list of Flowgates by creating, modifying, or deleting Flowgate definitions at least once per calendar year.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27691,"MOD-030-3","R2.3.","YES","At a minimum, establish a list of Flowgates by creating, modifying, or deleting Flowgates that have been requested as part of R2.1.4 within thirty calendar days from the request.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27692,"MOD-030-3","R2.4.","YES","Establish the TFC of each of the defined Flowgates as equal to: \n- For thermal limits, the System Operating Limit (SOL) of the Flowgate. \n- For voltage or stability limits, the flow that will respect the SOL of the Flowgate.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27693,"MOD-030-3","R2.5.","YES","At a minimum, establish the TFC once per calendar year.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27694,"MOD-030-3","R2.5.1.","YES","If notified of a change in the Rating by the Transmission Owner that would affect the TFC of a flowgate used in the AFC process, the TFC should be updated within seven calendar days of the notification.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27695,"MOD-030-3","R2.6.","YES","Provide the Transmission Service Provider with the TFCs within seven calendar days of their establishment.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27696,"MOD-030-3","R3.","YES","The Transmission Operator shall make available to the Transmission Service Provider a Transmission model to determine Available Flowgate Capability (AFC) that meets the following criteria: [Violation Risk Factor: To Be Determined] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"N/A",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27697,"MOD-030-3","R3.1.","YES","Contains generation Facility Ratings, such as generation maximum and minimum output levels, specified by the Generator Owners of the Facilities within the model.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27698,"MOD-030-3","R3.2.","YES","Updated at least once per day for AFC calculations for intra-day, next day, and days two through 30.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27699,"MOD-030-3","R3.3.","YES","Updated at least once per month for AFC calculations for months two through 13.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27700,"MOD-030-3","R3.4.","YES","Contains modeling data and system topology for the Facilities within its Reliability Coordinator’s Area. Equivalent representation of radial lines and Facilities161kV or below is allowed.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27701,"MOD-030-3","R3.5.","YES","Contains modeling data and system topology (or equivalent representation) for immediately adjacent and beyond Reliability Coordination Areas.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP","No",true,null,false]
[27702,"MOD-030-3","R4.","YES","When calculating AFCs, the Transmission Service Provider shall represent the impact of Transmission Service as follows: [Time Horizon: Operations Planning]\n- If the source, as specified in the ATCID, has been identified in the reservation and it is discretely modeled in the Transmission Service Provider’s Transmission model, use the discretely modeled point as the source.\n- If the source, as specified in the ATCID, has been identified in the reservation and the point can be mapped to an “equivalence” or “aggregate” representation in the Transmission Service Provider’s Transmission model, use the modeled equivalence or aggregate as the source.\n- If the source, as specified in the ATCID, has been identified in the reservation and the point cannot be mapped to a discretely modeled point or an “equivalence” representation in the Transmission Service Provider’s Transmission model, use the immediately adjacent Balancing Authority associated with the Transmission Service Provider from which the power is to be received as the source.\n- If the source, as specified in the ATCID, has not been identified in the reservation use the immediately adjacent Balancing Authority associated with the Transmission Service Provider from which the power is to be received as the source.\n- If the sink, as specified in the ATCID, has been identified in the reservation and it is discretely modeled in the Transmission Service Provider’s Transmission model, use the discretely modeled point as the sink.\n- If the sink, as specified in the ATCID, has been identified in the reservation and the point can be mapped to an “equivalence” or “aggregate” representation in the Transmission Service Provider’s Transmission model, use the modeled equivalence or aggregate as the sink.\n- If the sink, as specified in the ATCID, has been identified in the reservation and the point cannot be mapped to a discretely modeled point or an “equivalence” representation in the Transmission Service Provider’s Transmission model, use the immediately adjacent Balancing Authority associated with the Transmission Service Provider receiving the power as the sink.\n- If the sink, as specified in the ATCID, has not been identified in the reservation use the immediately adjacent Balancing Authority associated with the Transmission Service Provider receiving the power as the sink.","2017-04-01",null,"Effective",null,"N/A",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27703,"MOD-030-3","R5.","YES","When calculating AFCs, the Transmission Service Provider shall: [Violation Risk Factor: To Be Determined] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"N/A",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27704,"MOD-030-3","R5.1.","YES","Use the models provided by the Transmission Operator.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27705,"MOD-030-3","R5.2.","YES","Include in the transmission model expected generation and Transmission outages, additions, and retirements within the scope of the model as specified in the ATCID and in effect during the applicable period of the AFC calculation for the Transmission Service Provider’s area, all adjacent Transmission Service Providers, and any Transmission Service Providers with which coordination agreements have been executed.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27706,"MOD-030-3","R5.3.","YES","For external Flowgates, identified in R2.1.4, use the AFC provided by the Transmission Service Provider that calculates AFC for that Flowgate.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27707,"MOD-030-3","R6.","YES","When calculating the impact of ETC for firm commitments (ETCFi) for all time periods for a Flowgate, the Transmission Service Provider shall sum the following: [Violation Risk Factor: To Be Determined] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"N/A",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27708,"MOD-030-3","R6.1.","YES","The impact of firm Network Integration Transmission Service, including the impacts of generation to load, in the model referenced in R5.2 for the Transmission Service Provider’s area, based on:","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27709,"MOD-030-3","R6.1.1.","YES","Load forecast for the time period being calculated, including Native Load and Network Service load","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27710,"MOD-030-3","R6.1.2.","YES","Unit commitment and Dispatch Order, to include all designated network resources and other resources that are committed or have the legal obligation to run as specified in the Transmission Service Provider's ATCID.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27473,"MOD-030-3","R6.2.","YES","The impact of any firm Network Integration Transmission Service, including the impacts of generation to load in the model referenced in R5.2 and has a distribution factor equal to or greater than the percentage  used to curtail in the Interconnection-wide congestion management procedure used by the Transmission Service Provider, for all adjacent Transmission Service Providers and any other Transmission Service Providers with which coordination agreements have been executed based on:","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27474,"MOD-030-3","R6.2.1.","YES","Load forecast for the time period being calculated, including Native Load and Network Service load","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27475,"MOD-030-3","R6.2.2.","YES","Unit commitment and Dispatch Order, to include all designated network resources and other resources that are committed or have the legal obligation to run as specified in the Transmission Service Provider's ATCID.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27476,"MOD-030-3","R6.3.","YES","The impact of all confirmed firm Point-to-Point Transmission Service expected to be scheduled, including roll-over rights for Firm Transmission Service contracts, for the Transmission Service Provider’s area.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27477,"MOD-030-3","R6.4.","YES","The impact of any confirmed firm Point-to-Point Transmission Service expected to be scheduled, filtered to reduce or eliminate duplicate impacts from transactions using Transmission service from multiple Transmission Service Providers, including roll-over rights for Firm Transmission Service contracts having a distribution factor equal to or greater than the percentage  used to curtail in the Interconnection-wide congestion management procedure used by the Transmission Service Provider, for all adjacent Transmission Service Providers and any other Transmission Service Providers with which coordination agreements have been executed.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27478,"MOD-030-3","R6.5.","YES","The impact of any Grandfathered firm obligations expected to be scheduled or expected to flow for the Transmission Service Provider’s area.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27479,"MOD-030-3","R6.6.","YES","The impact of any Grandfathered firm obligations expected to be scheduled or expected to flow that have a distribution factor equal to or greater than the percentage  used to curtail in the Interconnection-wide congestion management procedure used by the Transmission Service Provider, for all adjacent Transmission Service Providers and any other Transmission Service Providers with which coordination agreements have been executed.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27711,"MOD-030-3","R6.7.","YES","The impact of other firm services determined by the Transmission Service Provider.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27712,"MOD-030-3","R7.","YES","When calculating the impact of ETC for non-firm commitments (ETCNFi) for all time periods for a Flowgate the Transmission Service Provider shall sum: [Violation Risk Factor: To Be Determined] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"N/A",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27713,"MOD-030-3","R7.1.","YES","The impact of all confirmed non-firm Point-to-Point Transmission Service expected to be scheduled for the Transmission Service Provider’s area.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27714,"MOD-030-3","R7.2.","YES","The impact of any confirmed non-firm Point-to-Point Transmission Service expected to be scheduled, filtered to reduce or eliminate duplicate impacts from transactions using Transmission service from multiple Transmission Service Providers, that have a distribution factor equal to or greater than the percentage  used to curtail in the Interconnection-wide congestion management procedure used by the Transmission Service Provider, for all adjacent Transmission Service Providers and any other Transmission Service Providers with which coordination agreements have been executed.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27715,"MOD-030-3","R7.3.","YES","The impact of any Grandfathered non-firm obligations expected to be scheduled or expected to flow for the Transmission Service Provider’s area.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27716,"MOD-030-3","R7.4.","YES","The impact of any Grandfathered non-firm obligations expected to be scheduled or expected to flow that have a distribution factor equal to or greater than the percentage  used to curtail in the Interconnection-wide congestion management procedure used by the Transmission Service Provider, for all adjacent Transmission Service Providers and any other Transmission Service Providers with which coordination agreements have been executed.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27717,"MOD-030-3","R7.5.","YES","The impact of non-firm Network Integration Transmission Service serving Load within the Transmission Service Provider’s area (i.e., secondary service), to include load growth, and losses not otherwise included in Transmission Reliability Margin or Capacity Benefit Margin.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27718,"MOD-030-3","R7.6.","YES","The impact of any non-firm Network Integration Transmission Service (secondary service) with a distribution factor equal to or greater than the percentage  used to curtail in the Interconnection-wide congestion management procedure used by the Transmission Service Provider, filtered to reduce or eliminate duplicate impacts from transactions using Transmission service from multiple Transmission Service Providers, for all adjacent Transmission Service Providers and any other Transmission Service Providers with which coordination agreements have been executed.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27719,"MOD-030-3","R7.7.","YES","The impact of other non-firm services determined by the Transmission Service Provider.","2017-04-01",null,"Effective",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27720,"MOD-030-3","R8.","YES","When calculating firm AFC for a Flowgate for a specified period, the Transmission Service Provider shall use the following algorithm (subject to allocation processes described in the ATCID):  [Time Horizon: Operations Planning] See Standard for Formula","2017-04-01",null,"Effective",null,"N/A",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27721,"MOD-030-3","R9.","YES","When calculating non-firm AFC for a Flowgate for a specified period, the Transmission Service Provider shall use the following algorithm (subject to allocation processes described in the ATCID):  [Time Horizon: Operations Planning] See Standard for Formula","2017-04-01",null,"Effective",null,"N/A",null,"N/A",null,"N/A","TSP","No",false,null,false]
[27752,"MOD-031-2","R1.",null,"Each Planning Coordinator or Balancing Authority that identifies a need for the collection of Total Internal Demand, Net Energy for Load, and Demand Side Management data shall develop and issue a data request to the applicable entities in its area. The data request shall include: [Violation Risk Factor: Medium] [Time Horizon: Long‐term Planning]","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27753,"MOD-031-2","R1.1.",null,"A list of Transmission Planners, Balancing Authorities, Load Serving Entities, and Distribution Providers that are required to provide the data (“Applicable Entities”).","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27754,"MOD-031-2","R1.2.",null,"A timetable for providing the data. (A minimum of 30 calendar days must be allowed for responding to the request).","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27755,"MOD-031-2","R1.3.",null,"A request to provide any or all of the following actual data, as necessary:","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27756,"MOD-031-2","R1.3.1.",null,"Integrated hourly Demands in megawatts for the prior calendar year.","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27757,"MOD-031-2","R1.3.2.",null,"Monthly and annual integrated peak hour Demands in megawatts for the prior calendar year.","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27758,"MOD-031-2","R1.3.2.1.",null,"If the annual peak hour actual Demand varies due to weatherrelated conditions (e.g., temperature, humidity or wind speed), the Applicable Entity shall also provide the weather normalized annual peak hour actual Demand for the prior calendar year.","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27759,"MOD-031-2","R1.3.3.",null,"Monthly and annual Net Energy for Load in gigawatthours for the prior calendar year.","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27760,"MOD-031-2","R1.3.4.",null,"Monthly and annual peak hour controllable and dispatchable Demand Side Management under the control or supervision of the System Operator in megawatts for the prior calendar year. Three values shall be reported for each hour: 1) the committed megawatts (the amount under control or supervision), 2) the  dispatched megawatts (the amount, if any, activated for use by the System Operator), and 3) the realized megawatts (the amount of actual demand reduction).","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27761,"MOD-031-2","R1.4.",null,"A request to provide any or all of the following forecast data, as necessary:","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27762,"MOD-031-2","R1.4.1.",null,"Monthly peak hour forecast Total Internal Demands in megawatts for the next two calendar years.","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27763,"MOD-031-2","R1.4.2.",null,"Monthly forecast Net Energy for Load in gigawatthours for the next two calendar years.","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27764,"MOD-031-2","R1.4.3.",null,"Peak hour forecast Total Internal Demands (summer and winter) in megawatts for ten calendar years into the future.","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27765,"MOD-031-2","R1.4.4.",null,"Annual forecast Net Energy for Load in gigawatthours for ten calendar years into the future.","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27766,"MOD-031-2","R1.4.5.",null,"Total and available peak hour forecast of controllable and dispatchable Demand Side Management (summer and winter), in megawatts, under the control or supervision of the System Operator for ten calendar years into the future.","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27767,"MOD-031-2","R1.5.",null,"A request to provide any or all of the following summary explanations, as necessary,:","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27768,"MOD-031-2","R1.5.1.",null,"The assumptions and methods used in the development of aggregated Peak Demand and Net Energy for Load forecasts.","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27769,"MOD-031-2","R1.5.2.",null,"The Demand and energy effects of controllable and dispatchable Demand Side Management under the control or supervision of the System Operator.","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27770,"MOD-031-2","R1.5.3.",null,"How Demand Side Management is addressed in the forecasts of its Peak Demand and annual Net Energy for Load.","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27771,"MOD-031-2","R1.5.4.",null,"How the controllable and dispatchable Demand Side Management forecast compares to actual controllable and dispatchable Demand Side Management for the prior calendar year and, if applicable, how the assumptions and methods for future forecasts were adjusted.","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27772,"MOD-031-2","R1.5.5.",null,"How the peak Demand forecast compares to actual Demand for the prior calendar year with due regard to any relevant weather‐related variations (e.g., temperature, humidity, or wind speed) and, if applicable, how the assumptions and methods for future forecasts were adjusted.","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27773,"MOD-031-2","R2.",null,"Each Applicable Entity identified in a data request shall provide the data requested by its Planning Coordinator or Balancing Authority in accordance with the data request issued pursuant to Requirement R1. [Violation Risk Factor: Medium] [Time Horizon: Long‐term Planning]","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","RP, PC, PA, LSE, DP, BA","Yes",false,null,false]
[27774,"MOD-031-2","R3.",null,"The Planning Coordinator or the Balancing Authority shall provide the data listed under Requirement R1 Parts 1.3 through 1.5 for their area to the applicable Regional Entity within 75 calendar days of receiving a request for such data, unless otherwise agreed upon by the parties. [Violation Risk Factor: Medium] [Time Horizon: Long‐term Planning]","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, PA, BA","No",false,null,false]
[27775,"MOD-031-2","R4.",null,"Any Applicable Entity shall, in response to a written request for the data included in parts 1.3‐1.5 of Requirement R1 from a Planning Coordinator, Balancing Authority, Transmission Planner or Resource Planner with a demonstrated need for such data in order to conduct reliability assessments of the Bulk Electric System, provide or otherwise make available that data to the requesting entity. This requirement does not modify an entity’s obligation pursuant to Requirement R2 to respond to data requests issued by its Planning Coordinator or Balancing Authority pursuant to Requirement R1. Unless otherwise agreed upon, the Applicable Entity: [Violation Risk Factor: Medium] [Time Horizon: Long‐term Planning]\n\n● shall not be required to alter the format in which it maintains or uses the data;\n● shall provide the requested data within 45 calendar days of the written request, subject to part 4.1 of this requirement; unless providing the requested data would conflict with the Applicable Entity’s confidentialit , regulatory, or security requirements","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","RP, PC, PA, LSE, DP, BA","Yes",false,null,false]
[27776,"MOD-031-2","R4.1.",null,"If the Applicable Entity does not provide data requested because (1) the requesting entity did not demonstrate a reliability need for the data; or (2) providing the data would conflict with the Applicable Entity’s confidentiality, regulatory, or security requirements, the Applicable Entity shall, within 30 calendar days of the written request, provide a written response to the requesting entity specifying the data that is not being provided and on what basis.","2016-10-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","RP, PC, PA, LSE, DP, BA","Yes",false,null,false]
[29943,"MOD-031-3","R1.",null,"Each Planning Coordinator or Balancing Authority that identifies a need for the collection of Total Internal Demand, Net Energy for Load, and Demand Side Management data shall develop and issue a data request to the applicable entities in its area. The data request shall include: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29944,"MOD-031-3","R1.1.",null,"A list of Transmission Planners, Balancing Authorities, and Distribution Providers that are required to provide the data (“Applicable Entities”).","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PA","Yes",false,null,false]
[29945,"MOD-031-3","R1.2.",null,"A timetable for providing the data. (A minimum of 30 calendar days must be allowed for responding to the request).","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29946,"MOD-031-3","R1.3.",null,"A request to provide any or all of the following actual data, as necessary:","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29947,"MOD-031-3","R1.3.1.",null,"Integrated hourly Demands in megawatts for the prior calendar year.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29948,"MOD-031-3","R1.3.2.",null,"Monthly and annual integrated peak hour Demands in megawatts for the prior calendar year.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA, TP, PC, DP, RP","Yes",false,null,false]
[29949,"MOD-031-3","R1.3.2.1.",null,"If the annual peak hour actual Demand varies due to weather-related conditions (e.g., temperature, humidity or wind speed), the Applicable Entity shall also provide the weather normalized annual peak hour actual Demand for the prior calendar year.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29950,"MOD-031-3","R1.3.3.",null,"Monthly and annual Net Energy for Load in gigawatt hours for the prior calendar year.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29951,"MOD-031-3","R1.3.4.",null,"Monthly and annual peak hour controllable and dispatchable Demand Side Management under the control or supervision of the System Operator in megawatts for the prior calendar year. Three values shall be reported for each hour: 1) the committed megawatts (the amount under control or supervision), 2) the dispatched megawatts (the amount, if any, activated for use by the System Operator),","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29952,"MOD-031-3","R1.4.",null,"A request to provide any or all of the following forecast data, as necessary:","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29953,"MOD-031-3","R1.4.1.",null,"Monthly peak hour forecast Total Internal Demands in megawatts for the next two calendar years.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29954,"MOD-031-3","R1.4.2.",null,"Monthly forecast Net Energy for Load in gigawatthours for the next two calendar years.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29955,"MOD-031-3","R1.4.3.",null,"Peak hour forecast Total Internal Demands (summer and winter) in megawatts for ten calendar years into the future.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29956,"MOD-031-3","R1.4.4.",null,"Annual forecast Net Energy for Load in gigawatthours for ten calendar years into the future.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29957,"MOD-031-3","R1.4.5.",null,"Total and available peak hour forecast of controllable and dispatchable Demand Side Management (summer and winter), in megawatts, under the control or supervision of the System Operator for ten calendar years into the future.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29958,"MOD-031-3","R1.5.",null,"A request to provide any or all of the following summary explanations, as necessary,:","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29959,"MOD-031-3","R1.5.1.",null,"The assumptions and methods used in the development of aggregated Peak Demand and Net Energy for Load forecasts.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29960,"MOD-031-3","R1.5.2.",null,"The Demand and energy effects of controllable and dispatchable Demand Side Management under the control or supervision of the System Operator.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29961,"MOD-031-3","R1.5.3.",null,"How Demand Side Management is addressed in the forecasts of its Peak Demand and annual Net Energy for Load.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29962,"MOD-031-3","R1.5.4.",null,"How the controllable and dispatchable Demand Side Management forecast compares to actual controllable and dispatchable Demand Side Management for the prior calendar year and, if applicable, how the assumptions and methods for future forecasts were adjusted.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29963,"MOD-031-3","R1.5.5.",null,"How the peak Demand forecast compares to actual Demand for the prior calendar year with due regard to any relevant weather-related variations (e.g., temperature, humidity, or wind speed) and, if applicable, how the assumptions and methods for future forecasts were adjusted.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29964,"MOD-031-3","R2.",null,"Each Applicable Entity identified in a data request shall provide the data requested by its Planning Coordinator or Balancing Authority in accordance with the data request issued pursuant to Requirement R1. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29965,"MOD-031-3","R3.",null,"The Planning Coordinator or the Balancing Authority shall provide the data listed under Requirement R1 Parts 1.3 through 1.5 for their area to the applicable Regional Entity within 75 calendar days of receiving a request for such data, unless otherwise agreed upon by the parties. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29966,"MOD-031-3","R4.",null,"Any Applicable Entity shall, in response to a written request for the data included in parts 1.3-1.5 of Requirement R1 from a Planning Coordinator, Balancing Authority, Transmission Planner or Resource Planner with a demonstrated need for such data in order to conduct reliability assessments of the Bulk Electric System, provide or otherwise make available that data to the requesting entity. This requirement does not modify an entity’s obligation pursuant to Requirement R2 to respond to data requests issued by its Planning Coordinator or Balancing Authority pursuant to Requirement R1. Unless otherwise agreed upon, the Applicable Entity: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]\r\n• shall not be required to alter the format in which it maintains or uses the data;\r\n• shall provide the requested data within 45 calendar days of the written request, subject to part 4.1 of this requirement; unless providing the requested data would conflict with the Applicable Entity’s confidentiality, regulatory, or security requirements","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[29967,"MOD-031-3","R4.1.",null,"If the Applicable Entity does not provide data requested because (1) the requesting entity did not demonstrate a reliability need for the data; or (2) providing the data would conflict with the Applicable Entity’s confidentiality, regulatory, or security requirements, the Applicable Entity shall, within 30 calendar days of the written request, provide a written response to the requesting entity specifying the data that is not being provided and on what basis.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, RP, BA, TP, PC","Yes",false,null,false]
[27777,"MOD-032-1","R1.",null,"Each Planning Coordinator and each of its Transmission Planners shall jointly develop\nsteady‐state, dynamics, and short circuit Real-Time Applications data requirements and reporting\nprocedures for the Planning Coordinator’s planning area that include: [Violation Risk\nFactor: Lower] [Time Horizon: Long‐term Planning]","2015-07-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC","No",false,null,false]
[27778,"MOD-032-1","R1.1.",null,"The data listed in Attachment 1.","2015-07-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC","No",false,null,false]
[27779,"MOD-032-1","R1.2.",null,"Specifications of the following items consistent with procedures for building the\nInterconnection‐wide case(s):","2015-07-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC","No",false,null,false]
[27780,"MOD-032-1","R1.2.1.",null,"Data format;","2015-07-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC","No",false,null,false]
[27781,"MOD-032-1","R1.2.2.",null,"Level of detail to which equipment shall be modeled;","2015-07-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC","No",false,null,false]
[27782,"MOD-032-1","R1.2.3.",null,"Case types or scenarios to be modeled; and","2015-07-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC","No",false,null,false]
[27783,"MOD-032-1","R1.2.4.",null,"A schedule for submission of data at least once every 13 calendar\nmonths.","2015-07-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","LIKELY","LOW (Adequate Controls)","TP, PC","No",false,null,false]
[27784,"MOD-032-1","R1.3.",null,"Specifications for distribution or posting of the data requirements and reporting procedures so that they are available to those entities responsible for providing the data.","2015-07-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC","No",false,null,false]
[27785,"MOD-032-1","R2.",null,"Each Balancing Authority, Generator Owner, Load Serving Entity, Resource Planner, Transmission Owner, and Transmission Service Provider shall provide steady‐state, dynamics, and short circuit Real-Time Applications data to its Transmission Planner(s) and Planning\nCoordinator(s) according to the data requirements and reporting procedures developed by its Planning Coordinator and Transmission Planner in Requirement R1. For data that has not changed since the last submission, a written confirmation that\nthe data has not changed is sufficient. [Violation Risk Factor: Medium] [Time Horizon: Long‐term Planning]","2015-07-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","LIKELY","LOW (Adequate Controls)","TSP, TO, RP, LSE, GO, BA","Yes",false,null,false]
[27786,"MOD-032-1","R3.",null,"Upon receipt of written notification from its Planning Coordinator or Transmission Planner regarding technical concerns with the data submitted under Requirement R2, including the technical basis or reason for the technical concerns, each notified\nBalancing Authority, Generator Owner, Load Serving Entity, Resource Planner, Transmission Owner, or Transmission Service Provider shall respond to the notifying Planning Coordinator or Transmission Planner as follows: [Violation Risk Factor:\nLower] [Time Horizon: Long‐term Planning]","2015-07-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TO, RP, LSE, GO, BA","Yes",false,null,false]
[27787,"MOD-032-1","R3.1.",null,"Provide either updated data or an explanation with a technical basis for maintaining the current data;","2015-07-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TO, RP, LSE, GO, BA","Yes",false,null,false]
[27788,"MOD-032-1","R3.2.",null,"Provide the response within 90 calendar days of receipt, unless a longer time period is agreed upon by the notifying Planning Coordinator or Transmission Planner.","2015-07-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TO, RP, LSE, GO, BA","Yes",false,null,false]
[27789,"MOD-032-1","R4.",null,"Each Planning Coordinator shall make available models for its planning area reflecting data provided to it under Requirement R2 to the Electric Reliability Organization (ERO) or its designee to support creation of the Interconnection‐wide case(s) that includes\nthe Planning Coordinator’s planning area. [Violation Risk Factor: Medium] [Time Horizon: Long‐term Planning]","2015-07-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[27790,"MOD-033-1","R1.",null,"Each Planning Coordinator shall implement a documented data validation process that includes the following attributes: [Violation Risk Factor: Medium] [Time Horizon: Long‐term Planning]","2017-07-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[27791,"MOD-033-1","R1.1.",null,"Comparison of the performance of the Planning Coordinator’s portion of the existing system in a planning power flow model to actual system behavior, represented by a state estimator case or other Real‐time data sources, at least once every 24 calendar months through simulation;","2017-07-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","LIKELY","MEDIUM (Moderate Controls)","PC","No",false,null,false]
[27792,"MOD-033-1","R1.2.",null,"Comparison of the performance of the Planning Coordinator’s portion of the existing system in a planning dynamic model to actual system response, through simulation of a dynamic local event, at least once every 24 calendar months (use a dynamic local event that occurs within 24 calendar months of the last dynamic local event used in comparison, and complete each comparison within 24 calendar months of the dynamic local event). If no dynamic local event occurs within the 24 calendar months, use the next dynamic local event that occurs;","2017-07-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","VERY LIKELY","HIGH (Inadequate Controls)","PC","No",false,null,false]
[27793,"MOD-033-1","R1.3.",null,"Guidelines the Planning Coordinator will use to determine unacceptable\ndifferences in performance under Part 1.1 or 1.2; and","2017-07-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[27794,"MOD-033-1","R1.4.",null,"Guidelines to resolve the unacceptable differences in performance identified\nunder Part 1.3.","2017-07-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","VERY LIKELY","HIGH (Inadequate Controls)","PC","No",false,null,false]
[27795,"MOD-033-1","R2.",null,"Each Reliability Coordinator and Transmission Operator shall provide actual system\nbehavior data (or a written response that it does not have the requested data) to any\nPlanning Coordinator performing validation under Requirement R1 within 30 calendar\ndays of a written request, such as, but not limited to, state estimator case or other\nReal‐time data (including disturbance data recordings) necessary for actual system\nresponse validation. [Violation Risk Factor: Lower] [Time Horizon: Long‐term Planning]","2017-07-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, RC","No",true,null,false]
[29937,"MOD-033-2","R1.",null,"Each Planning Coordinator shall implement a documented data validation process that includes the following attributes: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, RC, PC","No",false,null,false]
[29938,"MOD-033-2","R1.1.",null,"Comparison of the performance of the Planning Coordinator’s portion of the existing system in a planning power flow model to actual system behavior, represented by a state estimator case or other Real-time data sources, at least once every 24 calendar months through simulation;","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","LIKELY","MEDIUM (Moderate Controls)","TOP, RC, PC","No",false,null,false]
[29939,"MOD-033-2","R1.2.",null,"Comparison of the performance of the Planning Coordinator’s portion of the existing system in a planning dynamic model to actual system response, through simulation of a dynamic local event, at least once every 24 calendar months (use a dynamic local event that occurs within 24 calendar months of the last dynamic local event used in comparison, and complete each comparison within 24 calendar months of the dynamic local event). If no dynamic local event occurs within the 24 calendar months, use the next dynamic local event that occurs;","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","VERY LIKELY","HIGH (Inadequate Controls)","TOP, RC, PC","No",false,null,false]
[29940,"MOD-033-2","R1.3.",null,"Guidelines the Planning Coordinator will use to determine unacceptable differences in performance under Part 1.1 or 1.2; and","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, RC, PC","No",false,null,false]
[29941,"MOD-033-2","R1.4.",null,"Guidelines to resolve the unacceptable differences in performance identified under Part 1.3.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","VERY LIKELY","HIGH (Inadequate Controls)","TOP, RC, PC","No",false,null,false]
[29942,"MOD-033-2","R2.",null,"Each Reliability Coordinator and Transmission Operator shall provide actual system behavior data (or a written response that it does not have the requested data) to any Planning Coordinator performing validation under Requirement R1 within 30 calendar days of a written request, such as, but not limited to, state estimator case or other Real-time data (including disturbance data recordings) necessary for actual system response validation. [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, RC, PC","No",false,null,false]
[27822,"NUC-001-2.1(i)","R1.",null,"The Nuclear Plant Generator Operator shall provide the proposed NPIRs in writing to the applicable Transmission Entities and shall verify receipt [Risk Factor: Lower]",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[27823,"NUC-001-2.1(i)","R2.",null,"The Nuclear Plant Generator Operator and the applicable Transmission Entities shall have in effect one or more Agreements1 that include mutually agreed to NPIRs and document how the Nuclear Plant Generator Operator and the applicable Transmission Entities shall address and implement these NPIRs. [Risk Factor: Medium]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27824,"NUC-001-2.1(i)","R3.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall incorporate the NPIRs into their planning analyses of the electric system and shall communicate the results of these analyses to the Nuclear Plant Generator Operator. [Risk Factor: Medium]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27825,"NUC-001-2.1(i)","R3.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall incorporate the NPIRs into their planning analyses of the electric system and shall communicate the results of these analyses to the Nuclear Plant Generator Operator. [Risk Factor: Medium]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27828,"NUC-001-2.1(i)","R4.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall: [Risk Factor: High]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27826,"NUC-001-2.1(i)","R4.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall: [Risk Factor: High]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27827,"NUC-001-2.1(i)","R4.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall: [Risk Factor: High]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27831,"NUC-001-2.1(i)","R4.1.","YES","Incorporate the NPIRs into their operating analyses of the electric system.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27829,"NUC-001-2.1(i)","R4.1.","YES","Incorporate the NPIRs into their operating analyses of the electric system.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27830,"NUC-001-2.1(i)","R4.1.","YES","Incorporate the NPIRs into their operating analyses of the electric system.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27832,"NUC-001-2.1(i)","R4.2.",null,"Operate the electric system to meet the NPIRs.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27833,"NUC-001-2.1(i)","R4.3.",null,"Inform the Nuclear Plant Generator Operator when the ability to assess the operation of the electric system affecting NPIRs is lost.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, PA, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27834,"NUC-001-2.1(i)","R5.",null,"The Nuclear Plant Generator Operator shall operate per the Agreements developed in accordance with this standard. [Risk Factor: High]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[27835,"NUC-001-2.1(i)","R6.",null,"Per the Agreements developed in accordance with this standard, the applicable Transmission Entities and the Nuclear Plant Generator Operator shall coordinate outages and maintenance activities which affect the NPIRs. [Risk Factor: Medium]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27836,"NUC-001-2.1(i)","R7.",null,"Per the Agreements developed in accordance with this standard, the Nuclear Plant Generator Operator shall inform the applicable Transmission Entities of actual or proposed changes to nuclear plant design, configuration, operations, limits, Protection Systems, or capabilities that may impact the ability of the electric system to meet the NPIRs. [Risk Factor: High]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[27839,"NUC-001-2.1(i)","R8.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall inform the Nuclear Plant Generator Operator of actual or proposed changes to electric system design, configuration, operations, limits, Protection Systems, or capabilities that may impact the ability of the electric system to meet the NPIRs. [Risk Factor: High]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27840,"NUC-001-2.1(i)","R8.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall inform the Nuclear Plant Generator Operator of actual or proposed changes to electric system design, configuration, operations, limits, Protection Systems, or capabilities that may impact the ability of the electric system to meet the NPIRs. [Risk Factor: High]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27838,"NUC-001-2.1(i)","R8.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall inform the Nuclear Plant Generator Operator of actual or proposed changes to electric system design, configuration, operations, limits, Protection Systems, or capabilities that may impact the ability of the electric system to meet the NPIRs. [Risk Factor: High]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27837,"NUC-001-2.1(i)","R8.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall inform the Nuclear Plant Generator Operator of actual or proposed changes to electric system design, configuration, operations, limits, Protection Systems, or capabilities that may impact the ability of the electric system to meet the NPIRs. [Risk Factor: High]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27842,"NUC-001-2.1(i)","R9.","YES","The Nuclear Plant Generator Operator and the applicable Transmission Entities shall include, as a minimum, the following elements within the agreement(s) identified in R2: [Risk Factor: Medium]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27843,"NUC-001-2.1(i)","R9.","YES","The Nuclear Plant Generator Operator and the applicable Transmission Entities shall include, as a minimum, the following elements within the agreement(s) identified in R2: [Risk Factor: Medium]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27841,"NUC-001-2.1(i)","R9.","YES","The Nuclear Plant Generator Operator and the applicable Transmission Entities shall include, as a minimum, the following elements within the agreement(s) identified in R2: [Risk Factor: Medium]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27844,"NUC-001-2.1(i)","R9.1.","YES","Administrative elements:",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27845,"NUC-001-2.1(i)","R9.1.","YES","Administrative elements:",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27846,"NUC-001-2.1(i)","R9.1.1.",null,"Definitions of key terms used in the agreement.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27847,"NUC-001-2.1(i)","R9.1.2.",null,"Names of the responsible entities, organizational relationships, and responsibilities related to the NPIRs.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27848,"NUC-001-2.1(i)","R9.1.3.",null,"A requirement to review the agreement(s) at least every three years.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27849,"NUC-001-2.1(i)","R9.1.4.",null,"A dispute resolution mechanism.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27850,"NUC-001-2.1(i)","R9.2.",null,"Technical requirements and analysis:",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27851,"NUC-001-2.1(i)","R9.2.1.",null,"Identification of parameters, limits, configurations, and operating scenarios included in the NPIRs and, as applicable, procedures for providing any specific data not provided within the agreement.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27852,"NUC-001-2.1(i)","R9.2.2.",null,"Identification of facilities, components, and configuration restrictions that are essential for meeting the NPIRs.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27853,"NUC-001-2.1(i)","R9.2.3.",null,"Types of planning and operational analyses performed specifically to support the NPIRs, including the frequency of studies and types of Contingencies and scenarios required.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27854,"NUC-001-2.1(i)","R9.3.","YES","Operations and maintenance coordination:",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27855,"NUC-001-2.1(i)","R9.3.","YES","Operations and maintenance coordination:",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27856,"NUC-001-2.1(i)","R9.3.","YES","Operations and maintenance coordination:",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27857,"NUC-001-2.1(i)","R9.3.1.",null,"Designation of ownership of electrical facilities at the interface between the electric system and the nuclear plant and responsibilities for operational control coordination and maintenance of these facilities.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27858,"NUC-001-2.1(i)","R9.3.2.",null,"Identification of any maintenance requirements for equipment not owned or controlled by the Nuclear Plant Generator Operator that are necessary to meet the NPIRs.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27859,"NUC-001-2.1(i)","R9.3.3.",null,"Coordination of testing, calibration and maintenance of on-site and off-site power supply systems and related components.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27860,"NUC-001-2.1(i)","R9.3.4.",null,"Provisions to address mitigating actions needed to avoid violating NPIRs and to address periods when responsible Transmission Entity loses the ability to assess the capability of the electric system to meet the NPIRs. These provisions shall include responsibility to notify the Nuclear Plant Generator Operator within a specified time frame.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27861,"NUC-001-2.1(i)","R9.3.5.",null,"Provision for considering, within the restoration process, the requirements and urgency of a nuclear plant that has lost all off-site and on-site AC power.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27862,"NUC-001-2.1(i)","R9.3.6.",null,"Coordination of physical and cyber security protection of the Bulk Electric System at the nuclear plant interface to ensure each asset is covered under at least one entity’s plan.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27863,"NUC-001-2.1(i)","R9.3.7.",null,"Coordination of the NPIRs with transmission system Remedial Action Schemes and underfrequency and undervoltage load shedding programs.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27864,"NUC-001-2.1(i)","R9.4.","YES","Communications and training:",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27865,"NUC-001-2.1(i)","R9.4.","YES","Communications and training:",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27866,"NUC-001-2.1(i)","R9.4.1.",null,"Provisions for communications between the Nuclear Plant Generator Operator and Transmission Entities, including communications protocols, notification time requirements, and definitions of terms.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27867,"NUC-001-2.1(i)","R9.4.2.",null,"Provisions for coordination during an off-normal or emergency event affecting the NPIRs, including the need to provide timely information explaining the event, an estimate of when the system will be returned to a normal state, and the actual time the system is returned to normal.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27868,"NUC-001-2.1(i)","R9.4.3.",null,"Provisions for coordinating investigations of causes of unplanned events affecting the NPIRs and developing solutions to minimize future risk of such events.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27869,"NUC-001-2.1(i)","R9.4.4.",null,"Provisions for supplying information necessary to report to government agencies, as related to NPIRs.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27870,"NUC-001-2.1(i)","R9.4.5.",null,"Provisions for personnel training, as related to NPIRs.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27871,"NUC-001-3","R1.",null,"The Nuclear Plant Generator Operator shall provide the proposed NPIRs in writing to the applicable Transmission Entities and shall verify receipt.","2016-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[27872,"NUC-001-3","R2.",null,"The Nuclear Plant Generator Operator and the applicable Transmission Entities shall have in effect one or more Agreements that include mutually agreed to NPIRs and document how the Nuclear Plant Generator Operator and the applicable Transmission Entities shall address and implement these NPIRs.","2016-04-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27873,"NUC-001-3","R3.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall incorporate the NPIRs into their planning analyses of the electric system and shall communicate the results of these analyses to the Nuclear Plant Generator Operator.:","2016-04-01","2021-03-31","Retired",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27874,"NUC-001-3","R3.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall incorporate the NPIRs into their planning analyses of the electric system and shall communicate the results of these analyses to the Nuclear Plant Generator Operator.:","2016-04-01","2021-03-31","Retired","Authorization/Approval; Communications; Quality Check/Verification; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27877,"NUC-001-3","R4.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall","2016-04-01","2021-03-31","Retired","Communications; Documentations, Policies and Procedures; Monitoring; Tools and Applications; Training","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27876,"NUC-001-3","R4.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall","2016-04-01","2021-03-31","Retired","Communications; Documentations, Policies and Procedures; Quality Check/Verification; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27875,"NUC-001-3","R4.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall","2016-04-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27879,"NUC-001-3","R4.1.","YES","Incorporate the NPIRs into their operating analyses of the electric system.","2016-04-01","2021-03-31","Retired","Communications; Documentations, Policies and Procedures; Quality Check/Verification; Training","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27880,"NUC-001-3","R4.1.","YES","Incorporate the NPIRs into their operating analyses of the electric system.","2016-04-01","2021-03-31","Retired","Communications; Documentations, Policies and Procedures; Monitoring; Tools and Applications; Training","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27878,"NUC-001-3","R4.1.","YES","Incorporate the NPIRs into their operating analyses of the electric system.","2016-04-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27881,"NUC-001-3","R4.2.",null,"Operate the electric system to meet the NPIRs.","2016-04-01","2021-03-31","Retired","Communications; Documentations, Policies and Procedures; Monitoring; Tools and Applications; Training","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27882,"NUC-001-3","R4.3.",null,"Inform the Nuclear Plant Generator Operator when the ability to assess the operation of the electric system affecting NPIRs is lost.","2016-04-01","2021-03-31","Retired","Communications; Documentations, Policies and Procedures; Monitoring; Tools and Applications; Training","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27883,"NUC-001-3","R5.",null,"Per the Agreements developed in accordance with this standard, the Nuclear Plant Generator Operator shall operate the nuclear plant to meet the NPIRs.","2016-04-01","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[27884,"NUC-001-3","R6.",null,"Per the Agreements developed in accordance with this standard, the applicable Transmission Entities and the Nuclear Plant Generator Operator shall coordinate outages and maintenance activities which affect the NPIRs.","2016-04-01","2021-03-31","Retired","Communications; Documentations, Policies and Procedures; Quality Check/Verification; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27885,"NUC-001-3","R7.",null,"Per the Agreements developed in accordance with this standard, the Nuclear Plant Generator Operator shall inform the applicable Transmission Entities of actual or proposed changes to nuclear plant design (e.g., protective relay setpoints), configuration, operations, limits, or capabilities that may impact the ability of the electric system to meet the NPIRs.","2016-04-01","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[27889,"NUC-001-3","R8.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall inform the Nuclear Plant Generator Operator of actual or proposed changes to electric system design (e.g., protective relay setpoints), configuration, operations, limits, or capabilities that may impact the ability of the electric system to meet the NPIRs.","2016-04-01","2021-03-31","Retired","Communications; Documentations, Policies and Procedures; Quality Check/Verification; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27888,"NUC-001-3","R8.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall inform the Nuclear Plant Generator Operator of actual or proposed changes to electric system design (e.g., protective relay setpoints), configuration, operations, limits, or capabilities that may impact the ability of the electric system to meet the NPIRs.","2016-04-01","2021-03-31","Retired",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27886,"NUC-001-3","R8.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall inform the Nuclear Plant Generator Operator of actual or proposed changes to electric system design (e.g., protective relay setpoints), configuration, operations, limits, or capabilities that may impact the ability of the electric system to meet the NPIRs.","2016-04-01","2021-03-31","Retired","Communications; Documentations, Policies and Procedures; Monitoring; Training","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27887,"NUC-001-3","R8.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall inform the Nuclear Plant Generator Operator of actual or proposed changes to electric system design (e.g., protective relay setpoints), configuration, operations, limits, or capabilities that may impact the ability of the electric system to meet the NPIRs.","2016-04-01","2021-03-31","Retired","Authorization/Approval; Communications; Quality Check/Verification; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27890,"NUC-001-3","R9.","YES","The Nuclear Plant Generator Operator and the applicable Transmission Entities shall include the following elements in aggregate within the Agreement(s) identified in R2.\n--Where multiple Agreements with a single Transmission Entity are put into effect, the R9 elements must be addressed in aggregate within the Agreements; however, each Agreement does not have to contain each element. The Nuclear Plant Generator Operator and the Transmission Entity are responsible for ensuring all the R9 elements are addressed in aggregate within the Agreements.\n-- Where Agreements with multiple Transmission Entities are required, the Nuclear Plant Generator Operator is responsible for ensuring all the R9 elements are addressed in aggregate within the Agreements with the Transmission Entities. The Agreements with each Transmission Entity do not have to contain each element; however, the Agreements with the multiple Transmission Entities, in the aggregate, must address all R9 elements. For each Agreement(s), the Nuclear Plant Generator Operator and the Transmission Entity are responsible to ensure the Agreement(s) contain(s) the elements of R9 applicable to that Transmission Entity.","2016-04-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27891,"NUC-001-3","R9.","YES","The Nuclear Plant Generator Operator and the applicable Transmission Entities shall include the following elements in aggregate within the Agreement(s) identified in R2.\n--Where multiple Agreements with a single Transmission Entity are put into effect, the R9 elements must be addressed in aggregate within the Agreements; however, each Agreement does not have to contain each element. The Nuclear Plant Generator Operator and the Transmission Entity are responsible for ensuring all the R9 elements are addressed in aggregate within the Agreements.\n-- Where Agreements with multiple Transmission Entities are required, the Nuclear Plant Generator Operator is responsible for ensuring all the R9 elements are addressed in aggregate within the Agreements with the Transmission Entities. The Agreements with each Transmission Entity do not have to contain each element; however, the Agreements with the multiple Transmission Entities, in the aggregate, must address all R9 elements. For each Agreement(s), the Nuclear Plant Generator Operator and the Transmission Entity are responsible to ensure the Agreement(s) contain(s) the elements of R9 applicable to that Transmission Entity.","2016-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27892,"NUC-001-3","R9.","YES","The Nuclear Plant Generator Operator and the applicable Transmission Entities shall include the following elements in aggregate within the Agreement(s) identified in R2.\n--Where multiple Agreements with a single Transmission Entity are put into effect, the R9 elements must be addressed in aggregate within the Agreements; however, each Agreement does not have to contain each element. The Nuclear Plant Generator Operator and the Transmission Entity are responsible for ensuring all the R9 elements are addressed in aggregate within the Agreements.\n-- Where Agreements with multiple Transmission Entities are required, the Nuclear Plant Generator Operator is responsible for ensuring all the R9 elements are addressed in aggregate within the Agreements with the Transmission Entities. The Agreements with each Transmission Entity do not have to contain each element; however, the Agreements with the multiple Transmission Entities, in the aggregate, must address all R9 elements. For each Agreement(s), the Nuclear Plant Generator Operator and the Transmission Entity are responsible to ensure the Agreement(s) contain(s) the elements of R9 applicable to that Transmission Entity.","2016-04-01","2021-03-31","Retired","Communications; Documentations, Policies and Procedures; Quality Check/Verification; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27893,"NUC-001-3","R9.2.",null,"Technical requirements and analysis:","2016-04-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27894,"NUC-001-3","R9.2.1.",null,"Identification of parameters, limits, configurations, and operating scenarios included in the NPIRs and, as applicable, procedures for providing any specific data not provided within the Agreement.","2016-04-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27895,"NUC-001-3","R9.2.2.",null,"Identification of facilities, components, and configuration restrictions that are essential for meeting the NPIRs.","2016-04-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27896,"NUC-001-3","R9.2.3.",null,"Types of planning and operational analyses performed specifically to support the NPIRs, including the frequency of studies and types of Contingencies and scenarios required.","2016-04-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27897,"NUC-001-3","R9.3.","YES","Operations and maintenance coordination","2016-04-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27898,"NUC-001-3","R9.3.","YES","Operations and maintenance coordination","2016-04-01","2021-03-31","Retired","Communications; Documentations, Policies and Procedures; Quality Check/Verification; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27899,"NUC-001-3","R9.3.","YES","Operations and maintenance coordination","2016-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27900,"NUC-001-3","R9.3.1.",null,"Designation of ownership of electrical facilities at the interface between the electric system and the nuclear plant and responsibilities for operational control coordination and maintenance of these facilities.","2016-04-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27901,"NUC-001-3","R9.3.2.",null,"Identification of any maintenance requirements for equipment not owned or controlled by the Nuclear Plant Generator Operator that are necessary to meet the NPIRs.","2016-04-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27902,"NUC-001-3","R9.3.3.",null,"Coordination of testing, calibration and maintenance of on-site and off-site power supply systems and related components.","2016-04-01","2021-03-31","Retired","Authorization/Approval; Documentations, Policies and Procedures","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27903,"NUC-001-3","R9.3.4.",null,"Provisions to address mitigating actions needed to avoid violating NPIRs and to address periods when responsible Transmission Entity loses the ability to assess the capability of the electric system to meet the NPIRs. These provisions shall include responsibility to notify the Nuclear Plant Generator Operator within a specified time frame.","2016-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27904,"NUC-001-3","R9.3.5.",null,"Provision for considering, within the restoration process, the requirements and urgency of a nuclear plant that has lost all off-site and on-site AC power.","2016-04-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27905,"NUC-001-3","R9.3.6.",null,"Coordination of physical and cyber security protection at the nuclear plant interface to ensure each asset is covered under at least one entity’s plan.","2016-04-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27906,"NUC-001-3","R9.3.7.",null,"Coordination of the NPIRs with transmission system Remedial Action Schemes and any programs that reduce or shed load based on underfrequency or undervoltage.","2016-04-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27907,"NUC-001-3","R9.4.","YES","Communications and training Administrative elements:","2016-04-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27908,"NUC-001-3","R9.4.","YES","Communications and training Administrative elements:","2016-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27909,"NUC-001-3","R9.4.1.",null,"Provisions for communications affecting the NPIRs between the Nuclear Plant Generator Operator and Transmission Entities, including communications protocols, notification time requirements, and definitions of applicable unique terms.","2016-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27910,"NUC-001-3","R9.4.2.",null,"Provisions for coordination during an off-normal or emergency event affecting the NPIRs, including the need to provide timely information explaining the event, an estimate of when the system will be returned to a normal state, and the actual time the system is returned to normal.","2016-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27911,"NUC-001-3","R9.4.3.",null,"Provisions for coordinating investigations of causes of unplanned events affecting the NPIRs and developing solutions to minimize future risk of such events.","2016-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27497,"NUC-001-3","R9.4.4.",null,"Provisions for supplying information necessary to report to government agencies, as related to NPIRs.","2016-04-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[27498,"NUC-001-3","R9.4.5.",null,"Provisions for personnel training, as related to NPIRs.","2016-04-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TSP, TP, TOP, TO, RC, PC, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[29968,"NUC-001-4","R1.",null,"The Nuclear Plant Generator Operator shall provide the proposed NPIRs in writing to the applicable Transmission Entities and shall verify receipt. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning ]","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29969,"NUC-001-4","R2.",null,"The Nuclear Plant Generator Operator and the applicable Transmission Entities shall have in effect one or more Agreements1 that include mutually agreed to NPIRs and document how the Nuclear Plant Generator Operator and the applicable Transmission Entities shall address and implement these NPIRs. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning ]","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29971,"NUC-001-4","R3.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall incorporate the NPIRs into their planning analyses of the electric system and shall communicate the results of these analyses to the Nuclear Plant Generator Operator.: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning ]","2021-04-01",null,"Effective","Authorization/Approval; Communications; Quality Check/Verification; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29972,"NUC-001-4","R3.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall incorporate the NPIRs into their planning analyses of the electric system and shall communicate the results of these analyses to the Nuclear Plant Generator Operator.: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning ]","2021-04-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29974,"NUC-001-4","R4.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall [Violation Risk Factor: High] [Time Horizon: Operations Planning and Real-time Operations]","2021-04-01",null,"Effective","Communications; Documentations, Policies and Procedures; Quality Check/Verification; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29973,"NUC-001-4","R4.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall [Violation Risk Factor: High] [Time Horizon: Operations Planning and Real-time Operations]","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29975,"NUC-001-4","R4.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall [Violation Risk Factor: High] [Time Horizon: Operations Planning and Real-time Operations]","2021-04-01",null,"Effective","Communications; Documentations, Policies and Procedures; Tools and Applications; Training; Monitoring","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29977,"NUC-001-4","R4.1.","YES","Incorporate the NPIRs into their operating analyses of the electric system.","2021-04-01",null,"Effective","Documentations, Policies and Procedures; Quality Check/Verification; Training; Communications","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29978,"NUC-001-4","R4.1.","YES","Incorporate the NPIRs into their operating analyses of the electric system.","2021-04-01",null,"Effective","Communications; Documentations, Policies and Procedures; Monitoring; Tools and Applications; Training","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29976,"NUC-001-4","R4.1.","YES","Incorporate the NPIRs into their operating analyses of the electric system.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29979,"NUC-001-4","R4.2.",null,"Operate the electric system to meet the NPIRs.","2021-04-01",null,"Effective","Communications; Documentations, Policies and Procedures; Monitoring; Tools and Applications; Training","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29980,"NUC-001-4","R4.3.",null,"Inform the Nuclear Plant Generator Operator when the ability to assess the operation of the electric system affecting NPIRs is lost.","2021-04-01",null,"Effective","Communications; Documentations, Policies and Procedures; Monitoring; Tools and Applications; Training; Segregation of Duties","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29981,"NUC-001-4","R5.",null,"Per the Agreements developed in accordance with this standard, the Nuclear Plant Generator Operator shall operate the nuclear plant to meet the NPIRs. [Violation Risk Factor: High] [Time Horizon: Operations Planning and Real-time Operations ]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29982,"NUC-001-4","R6.",null,"Per the Agreements developed in accordance with this standard, the applicable Transmission Entities and the Nuclear Plant Generator Operator shall coordinate outages and maintenance activities which affect the NPIRs. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2021-04-01",null,"Effective","Communications; Documentations, Policies and Procedures; Quality Check/Verification; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29983,"NUC-001-4","R7.",null,"Per the Agreements developed in accordance with this standard, the Nuclear Plant Generator Operator shall inform the applicable Transmission Entities of actual or proposed changes to nuclear plant design (e.g., protective relay setpoints), configuration, operations, limits, or capabilities that may impact the ability of the electric system to meet the NPIRs. [Violation Risk Factor: High] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29985,"NUC-001-4","R8.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall inform the Nuclear Plant Generator Operator of actual or proposed changes to electric system design (e.g., protective relay setpoints), configuration, operations, limits, or capabilities that may impact the ability of the electric system to meet the NPIRs. [Violation Risk Factor: High] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective","Communications; Documentations, Policies and Procedures; Training; Monitoring","HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29986,"NUC-001-4","R8.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall inform the Nuclear Plant Generator Operator of actual or proposed changes to electric system design (e.g., protective relay setpoints), configuration, operations, limits, or capabilities that may impact the ability of the electric system to meet the NPIRs. [Violation Risk Factor: High] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)",null,"N/A","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29987,"NUC-001-4","R8.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall inform the Nuclear Plant Generator Operator of actual or proposed changes to electric system design (e.g., protective relay setpoints), configuration, operations, limits, or capabilities that may impact the ability of the electric system to meet the NPIRs. [Violation Risk Factor: High] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective","Communications; Quality Check/Verification; Training; Authorization/Approval","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29984,"NUC-001-4","R8.","YES","Per the Agreements developed in accordance with this standard, the applicable Transmission Entities shall inform the Nuclear Plant Generator Operator of actual or proposed changes to electric system design (e.g., protective relay setpoints), configuration, operations, limits, or capabilities that may impact the ability of the electric system to meet the NPIRs. [Violation Risk Factor: High] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective","Communications; Documentations, Policies and Procedures; Quality Check/Verification; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29988,"NUC-001-4","R9.","YES","The Nuclear Plant Generator Operator and the applicable Transmission Entities shall include the following elements in aggregate within the Agreement(s) identified in R2.\r\n• Where multiple Agreements with a single Transmission Entity are put into effect, the R9 elements must be addressed in aggregate within the Agreements; however, each Agreement does not have to contain each element. The Nuclear Plant Generator Operator and the Transmission Entity are responsible for ensuring all the R9 elements are addressed in aggregate within the Agreements.\r\n• Where Agreements with multiple Transmission Entities are required, the Nuclear Plant Generator Operator is responsible for ensuring all the R9 elements are addressed in aggregate within the Agreements with the Transmission Entities. The Agreements with each Transmission Entity do not have to contain each element; however, the Agreements with the multiple Transmission Entities, in the aggregate, must address all R9 elements. For each Agreement(s), the Nuclear Plant Generator Operator and the Transmission Entity are responsible to ensure the Agreement(s) contain(s) the elements of R9 applicable to that Transmission Entity. : [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective","Communications; Documentations, Policies and Procedures; Quality Check/Verification; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29990,"NUC-001-4","R9.","YES","The Nuclear Plant Generator Operator and the applicable Transmission Entities shall include the following elements in aggregate within the Agreement(s) identified in R2.\r\n• Where multiple Agreements with a single Transmission Entity are put into effect, the R9 elements must be addressed in aggregate within the Agreements; however, each Agreement does not have to contain each element. The Nuclear Plant Generator Operator and the Transmission Entity are responsible for ensuring all the R9 elements are addressed in aggregate within the Agreements.\r\n• Where Agreements with multiple Transmission Entities are required, the Nuclear Plant Generator Operator is responsible for ensuring all the R9 elements are addressed in aggregate within the Agreements with the Transmission Entities. The Agreements with each Transmission Entity do not have to contain each element; however, the Agreements with the multiple Transmission Entities, in the aggregate, must address all R9 elements. For each Agreement(s), the Nuclear Plant Generator Operator and the Transmission Entity are responsible to ensure the Agreement(s) contain(s) the elements of R9 applicable to that Transmission Entity. : [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29989,"NUC-001-4","R9.","YES","The Nuclear Plant Generator Operator and the applicable Transmission Entities shall include the following elements in aggregate within the Agreement(s) identified in R2.\r\n• Where multiple Agreements with a single Transmission Entity are put into effect, the R9 elements must be addressed in aggregate within the Agreements; however, each Agreement does not have to contain each element. The Nuclear Plant Generator Operator and the Transmission Entity are responsible for ensuring all the R9 elements are addressed in aggregate within the Agreements.\r\n• Where Agreements with multiple Transmission Entities are required, the Nuclear Plant Generator Operator is responsible for ensuring all the R9 elements are addressed in aggregate within the Agreements with the Transmission Entities. The Agreements with each Transmission Entity do not have to contain each element; however, the Agreements with the multiple Transmission Entities, in the aggregate, must address all R9 elements. For each Agreement(s), the Nuclear Plant Generator Operator and the Transmission Entity are responsible to ensure the Agreement(s) contain(s) the elements of R9 applicable to that Transmission Entity. : [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[30234,"NUC-001-4","R9.1.",null,"Retired. [Note: Part 9.1 was retired under the Paragraph 81 project. The NUC SDT\r\nproposes to leave this Part blank to avoid renumbering Requirement parts that\r\nwould impact existing agreements throughout the industry.]","2021-04-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)",null,"No",false,null,false]
[29991,"NUC-001-4","R9.2.",null,"Technical requirements and analysis:","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29992,"NUC-001-4","R9.2.1.",null,"Identification of parameters, limits, configurations, and operating scenarios included in the NPIRs and, as applicable, procedures for providing any specific data not provided within the Agreement.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29993,"NUC-001-4","R9.2.2.",null,"Identification of facilities, components, and configuration restrictions that are essential for meeting the NPIRs.","2021-04-01",null,"Effective","Authorization/Approval; Communications; dos; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","LIKELY","MEDIUM (Moderate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29994,"NUC-001-4","R9.2.3.",null,"Types of planning and operational analyses performed specifically to support the NPIRs, including the frequency of studies and types of Contingencies and scenarios required.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29996,"NUC-001-4","R9.3.","YES","Operations and maintenance coordination","2021-04-01",null,"Effective","Communications; Documentations, Policies and Procedures; Quality Check/Verification; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29997,"NUC-001-4","R9.3.","YES","Operations and maintenance coordination","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29995,"NUC-001-4","R9.3.","YES","Operations and maintenance coordination","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29998,"NUC-001-4","R9.3.1.",null,"Designation of ownership of electrical facilities at the interface between the electric system and the nuclear plant and responsibilities for operational control coordination and maintenance of these facilities.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[29999,"NUC-001-4","R9.3.2.",null,"Identification of any maintenance requirements for equipment not owned or controlled by the Nuclear Plant Generator Operator that are necessary to meet the NPIRs.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[30000,"NUC-001-4","R9.3.3.",null,"Coordination of testing, calibration and maintenance of on-site and off-site power supply systems and related components.","2021-04-01",null,"Effective","Authorization/Approval; Documentations, Policies and Procedures","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[30001,"NUC-001-4","R9.3.4.",null,"Provisions to address mitigating actions needed to avoid violating NPIRs and to address periods when responsible Transmission Entity loses the ability to assess the capability of the electric system to meet the NPIRs. These provisions shall include responsibility to notify the Nuclear Plant Generator Operator within a specified time frame.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[30002,"NUC-001-4","R9.3.5.",null,"Provision for considering, within the restoration process, the requirements and urgency of a nuclear plant that has lost all off-site and on-site AC power.","2021-04-01",null,"Effective","Authorization/Approval; dom; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[30003,"NUC-001-4","R9.3.6.",null,"Coordination of physical and cyber security protection at the nuclear plant interface to ensure each asset is covered under at least one entity’s plan.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[30004,"NUC-001-4","R9.3.7.",null,"Coordination of the NPIRs with transmission system Remedial Action Schemes and any programs that reduce or shed load based on underfrequency or undervoltage.","2021-04-01",null,"Effective","Authorization/Approval; Communications; docs; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[30006,"NUC-001-4","R9.4.","YES","Communications and training Administrative elements:","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[30005,"NUC-001-4","R9.4.","YES","Communications and training Administrative elements:","2021-04-01",null,"Effective","Authorization/Approval; Communications; docs; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","LIKELY","MEDIUM (Moderate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[30007,"NUC-001-4","R9.4.1.",null,"Provisions for communications affecting the NPIRs between the Nuclear Plant Generator Operator and Transmission Entities, including communications protocols, notification time requirements, and definitions of applicable unique terms.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[30008,"NUC-001-4","R9.4.2.",null,"Provisions for coordination during an off-normal or emergency event affecting the NPIRs, including the need to provide timely information explaining the event, an estimate of when the system will be returned to a normal state, and the actual time the system is returned to normal.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[30009,"NUC-001-4","R9.4.3.",null,"Provisions for coordinating investigations of causes of unplanned events affecting the NPIRs and developing solutions to minimize future risk of such events.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[30010,"NUC-001-4","R9.4.4.",null,"Provisions for supplying information necessary to report to government agencies, as related to NPIRs.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, TO, TOP, GOP, GO, DP, PC, RC, BA, TSP","Yes",false,null,false]
[30011,"NUC-001-4","R9.4.5.",null,"Provisions for supplying information necessary to report to government agencies, as related to NPIRs.","2021-04-01",null,"Effective","Authorization/Approval; Communications; docs; Monitoring; Quality Check/Verification; Segregation of Duties; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","GOP, GO, DP, PC, RC, BA, TSP, TP, TO, TOP","Yes",false,null,false]
[27500,"PER-003-1","R1.",null,"Each Reliability Coordinator shall staff its Real-time operating positions performing Reliability Coordinator reliability-related tasks with System Operators who have demonstrated minimum competency in the areas listed by obtaining and maintaining a valid NERC Reliability Operator certificate","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[27501,"PER-003-1","R1.1.",null,"Areas of Competency","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[27912,"PER-003-1","R1.1.1.",null,"Resource and demand balancing","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[27913,"PER-003-1","R1.1.2.",null,"Transmission operations","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[27914,"PER-003-1","R1.1.3.",null,"Emergency preparedness and operations","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[27915,"PER-003-1","R1.1.4.",null,"System operations","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[27916,"PER-003-1","R1.1.5.",null,"Protection and control","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[27917,"PER-003-1","R1.1.6.",null,"Voltage and reactive","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[27918,"PER-003-1","R1.1.7.",null,"Interchange scheduling and coordination","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[27919,"PER-003-1","R1.1.8.",null,"Interconnection reliability operations and coordination","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[27920,"PER-003-1","R2.",null,"Each Transmission Operator shall staff its Real-time operating positions performing Transmission Operator reliability-related tasks with System Operators who have demonstrated minimum competency in the areas listed by obtaining and maintaining one of the following valid NERC certificates (1","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,"",true]
[27921,"PER-003-1","R2.1.",null,"Areas of Competency","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,true]
[27959,"PER-003-1","R2.1.1.",null,"Transmission operations","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,true]
[27960,"PER-003-1","R2.1.2.",null,"Emergency preparedness and operations","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,true]
[27961,"PER-003-1","R2.1.3.",null,"System operations","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,true]
[27962,"PER-003-1","R2.1.4.",null,"Protection and control","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,true]
[27963,"PER-003-1","R2.1.5.",null,"Voltage and reactive","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,true]
[27964,"PER-003-1","R2.2.",null,"Certificates\n• Reliability Operator\n• Balancing, Interchange and Transmission Operator\n• Transmission Operator","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,true]
[27965,"PER-003-1","R3.",null,"Each Balancing Authority shall staff its Real-time operating positions performing Balancing Authority reliability-related tasks with System Operators who have demonstrated minimum competency in the areas listed by obtaining and maintaining one of the following valid NERC certificates (1)","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","BA","No",false,null,false]
[27966,"PER-003-1","R3.1.",null,"Areas of Competency","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","BA","No",false,null,false]
[27967,"PER-003-1","R3.1.1.",null,"Resources and demand balancing","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","BA","No",false,null,false]
[27968,"PER-003-1","R3.1.2.",null,"Emergency preparedness and operations","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","BA","No",false,null,false]
[27969,"PER-003-1","R3.1.3.",null,"System operations","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","BA","No",false,null,false]
[27970,"PER-003-1","R3.1.4.",null,"Interchange scheduling and coordination","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","BA","No",false,null,false]
[27971,"PER-003-1","R3.2.",null,"Certificates\n• Reliability Operator\n• Balancing, Interchange and Transmission Operator\n• Balancing and Interchange Operator","2012-10-01","2019-06-30","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","BA","No",false,null,false]
[29714,"PER-003-2","R1.",null,"Each Reliability Coordinator shall staff its Real-time operating positions performing Reliability Coordinator reliability-related tasks with System Operators who have demonstrated minimum competency in the areas listed by obtaining and maintaining a valid NERC Reliability Operator certificate (1)(2): [Risk Factor: High][Time Horizon: Real-time Operations]","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[29715,"PER-003-2","R1.1.",null,"Areas of Competency","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[29716,"PER-003-2","R1.1.1.",null,"Resource and demand balancing","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[29717,"PER-003-2","R1.1.2.",null,"Transmission operations","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[29718,"PER-003-2","R1.1.3.",null,"Emergency preparedness and operations","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[29719,"PER-003-2","R1.1.4.",null,"System operations","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[29720,"PER-003-2","R1.1.5.",null,"Protection and control","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[29721,"PER-003-2","R1.1.6.",null,"Voltage and reactive","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[29723,"PER-003-2","R1.1.7.",null,"Interchange scheduling and coordination","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[29725,"PER-003-2","R1.1.8.",null,"Interconnection reliability operations and coordination","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","RC","No",false,null,false]
[29726,"PER-003-2","R2.",null,"Each Transmission Operator shall staff its Real-time operating positions performing Transmission Operator reliability-related tasks with System Operators who have demonstrated minimum competency in the areas listed by obtaining and maintaining one of the following valid NERC certificates (1)(2): [Risk Factor: High][Time Horizon: Real-time Operations]:","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[29727,"PER-003-2","R2.1.",null,"Areas of Competency","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[29728,"PER-003-2","R2.1.1.",null,"Transmission operations","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[29729,"PER-003-2","R2.1.2.",null,"Emergency preparedness and operations","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[29730,"PER-003-2","R2.1.3.",null,"System operations","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[29731,"PER-003-2","R2.1.4.",null,"Protection and control","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[29732,"PER-003-2","R2.1.5.",null,"Voltage and reactive","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[29733,"PER-003-2","R2.2.",null,"Certificates\r\n Reliability Operator\r\n Balancing, Interchange and Transmission Operator\r\n Transmission Operator","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[29734,"PER-003-2","R3.",null,"Each Balancing Authority shall staff its Real-time operating positions performing Balancing Authority reliability-related tasks with System Operators who have demonstrated minimum competency in the areas listed by obtaining and maintaining one of the following valid NERC certificates (1)(2): [Risk Factor: High][Time Horizon: Real-time Operations]:","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[29735,"PER-003-2","R3.1.",null,"Areas of Competency","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[29736,"PER-003-2","R3.1.1.",null,"Resources and demand balancing","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[29737,"PER-003-2","R3.1.2.",null,"Emergency preparedness and operations","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[29738,"PER-003-2","R3.1.3.",null,"System operations","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[29739,"PER-003-2","R3.1.4.",null,"Interchange scheduling and coordination","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[29740,"PER-003-2","R3.2.",null,"Certificates\r\n Reliability Operator\r\n Balancing, Interchange and Transmission Operator\r\n Balancing and Interchange Operator","2019-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[27972,"PER-004-2","R1.",null,"Each Reliability Coordinator shall be staffed with adequately trained and NERC-certified Reliability Coordinator operators, 24 hours per day, seven days per week.","2011-04-01","2019-06-23","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[27973,"PER-004-2","R2.",null,"Reliability Coordinator operating personnel shall place particular attention on SOLs and 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.","2011-04-01","2019-06-23","Retired","Authorization/Approval; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","RC","No",false,null,false]
[27984,"PER-005-2","R1.",null,"Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall use a systematic approach to develop and implement a training program for its System Operators as follows:","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[27985,"PER-005-2","R1.1.",null,"Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall create a list of Bulk Electric System (BES) company-specific Real-time reliability-related tasks based on a defined and documented methodology.","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[27986,"PER-005-2","R1.1.1.",null,"Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall review, and update if necessary, its list of BES company-specific Real-time reliability-related tasks identified in part 1.1 each calendar year.","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[27987,"PER-005-2","R1.2.",null,"Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall design and develop training materials according to its training program, based on the BES company-specific Real-time reliability-related task list created in part 1.1.","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[27988,"PER-005-2","R1.3.",null,"Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall deliver training to its System Operators according to its training program.","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[27989,"PER-005-2","R1.4.",null,"Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall conduct an evaluation each calendar year of the training program established in Requirement R1 to identify any needed changes to the training program and shall implement the changes identified.","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[27990,"PER-005-2","R2.",null,"Each Transmission Owner shall use a systematic approach to develop and implement a training program for its personnel identified in Applicability Section 4.1.4.1 of this standard as follows:","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[27991,"PER-005-2","R2.1.",null,"Each Transmission Owner shall create a list of BES company-specific Real-time reliability-related tasks based on a defined and documented methodology.","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[27992,"PER-005-2","R2.1.1.",null,"Each Transmission Owner shall review, and update if necessary, its list of BES company-specific Real-time reliability-related tasks identified in part 2.1 each calendar year.","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[27993,"PER-005-2","R2.2.",null,"Each Transmission Owner shall design and develop training materials according to its training program, based on the BES company-specific Real-time reliability-related task list created in part 2.1.","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[27994,"PER-005-2","R2.3.",null,"Each Transmission Owner shall deliver training to its personnel identified in Applicability Section 4.1.4.1 of this standard according to its training program.","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[27995,"PER-005-2","R2.4.",null,"Each Transmission Owner shall conduct an evaluation each calendar year of the training program established in Requirement R2 to identify any needed changes to the training program and shall implement the changes identified.","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[27996,"PER-005-2","R3.",null,"Each Reliability Coordinator, Balancing Authority, Transmission Operator, and Transmission Owner shall verify, at least once, the capabilities of its personnel, identified in Requirement R1 or Requirement R2, assigned to perform each of the BES company-specific Real-time reliability-related tasks identified under Requirement R1 part 1.1 or Requirement R2 part 2.1.","2016-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, TO, RC, BA","Yes",true,null,true]
[27997,"PER-005-2","R3.1.",null,"Within six months of a modification or addition of a BES company-specific Real-time reliability-related task, each Reliability Coordinator, Balancing Authority, Transmission Operator, and Transmission Owner shall verify the capabilities of each of its personnel identified in Requirement R1 or Requirement R2 to perform the new or modified BES company-specific Real-time reliability-related tasks identified in Requirement R1 part 1.1 or Requirement R2 part 2.1.","2016-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, TO, RC, BA","Yes",true,null,true]
[27998,"PER-005-2","R4.",null,"Each Reliability Coordinator, Balancing Authority, Transmission Operator, and Transmission Owner that (1) has operational authority or control over Facilities with established Interconnection Reliability Operating Limits (IROLs), or (2) has established protection systems or operating guides to mitigate IROL violations, shall provide its personnel identified in Requirement R1 or Requirement R2 with emergency operations training using simulation technology such as a simulator, virtual technology, or other technology that replicates the operational behavior of the BES.","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, BA","Yes",true,null,true]
[27999,"PER-005-2","R4.1.",null,"A Reliability Coordinator, Balancing Authority, Transmission Operator, or Transmission Owner that did not previously meet the criteria of Requirement R4, shall comply with Requirement R4 within 12 months of meeting the criteria.","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, RC, BA","Yes",true,null,true]
[28001,"PER-005-2","R5.","YES","Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall use a systematic approach to develop and implement training for its identified Operations Support Personnel on how their job function(s) impact those BES company-specific Real-time reliability-related tasks identified by the entity pursuant to Requirement R1 part 1.1.","2016-10-01",null,"Effective","Communications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","LIKELY","MEDIUM (Moderate Controls)","TOP, RC, BA","No",true,null,true]
[28000,"PER-005-2","R5.","YES","Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall use a systematic approach to develop and implement training for its identified Operations Support Personnel on how their job function(s) impact those BES company-specific Real-time reliability-related tasks identified by the entity pursuant to Requirement R1 part 1.1.","2016-10-01",null,"Effective","Communications; Documentations, Policies and Procedures","MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, RC, BA","No",true,null,true]
[30082,"PER-005-2","R5.","YES","Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall have available for inspection evidence that Operations Support Personnel completed training in accordance with its systematic approach. This evidence may be documents such as training records showing successful completion of training. Documentation of training shall include employee name and date of training.","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA, RC, TOP","No",false,null,false]
[28002,"PER-005-2","R5.1.","YES","Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall conduct an evaluation each calendar year of the training established in Requirement R5 to identify and implement changes to the training.","2016-10-01",null,"Effective","Communications; Documentations, Policies and Procedures","MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP, RC, BA","No",true,null,true]
[28003,"PER-005-2","R5.1.","YES","Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall conduct an evaluation each calendar year of the training established in Requirement R5 to identify and implement changes to the training.","2016-10-01",null,"Effective","Communications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","LIKELY","MEDIUM (Moderate Controls)","TOP, RC, BA","No",true,null,true]
[30083,"PER-005-2","R5.1.","YES","Each Reliability Coordinator, Balancing Authority, and Transmission Operator shall have available for inspection evidence (such as instructor observations, trainee feedback, supervisor feedback, course evaluations, learning assessments, or internal audit results) that it performed an evaluation each calendar year, as specified in Requirement R5 part 5.1.","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA, RC, TOP","No",false,null,false]
[28004,"PER-005-2","R6.",null,"Each Generator Operator shall use a systematic approach to develop and implement training to its personnel identified in Applicability Section 4.1.5.1 of this standard, on how their job function(s) impact the reliable operations of the BES during normal and emergency operations.","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[28005,"PER-005-2","R6.1.",null,"Each Generator Operator shall conduct an evaluation each calendar year of the training established in Requirement R6 to identify and implement changes to the training.","2016-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[28006,"PER-006-1","R1.",null,"Each Generator Operator shall provide training to personnel identified in Applicability section 4.1.1.1. on the operational functionality of Protection Systems and Remedial Action Schemes (RAS) that affect the output of the generating Facility(ies) it operates.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[28023,"PRC-001-1.1(i)","R1.",null,"Each Transmission Operator, Balancing Authority, and Generator Operator shall be familiar with the purpose and limitations of Protection System schemes applied in its area.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, BA","Yes",true,null,true]
[28024,"PRC-001-1.1(i)","R2.",null,"Each Generator Operator and Transmission Operator shall notify reliability entities of relay or equipment failures as follows:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP","Yes",true,null,true]
[28025,"PRC-001-1.1(i)","R2.1.",null,"If a protective relay or equipment failure reduces system reliability, the Generator Operator shall notify its Transmission Operator and Host Balancing Authority. The Generator Operator shall take corrective action as soon as possible.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[28026,"PRC-001-1.1(i)","R2.2.",null,"If a protective relay or equipment failure reduces system reliability, the Transmission Operator shall notify its Reliability Coordinator and affected Transmission Operators and Balancing Authorities. The Transmission Operator shall take corrective action as soon as possible.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[28027,"PRC-001-1.1(i)","R3.",null,"A Generator Operator or Transmission Operator shall coordinate new protective systems and changes as follows.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP, GOP","Yes",true,null,true]
[28028,"PRC-001-1.1(i)","R3.1.",null,"Each Generator Operator shall coordinate all new protective systems and all protective system changes with its Transmission Operator and Host Balancing Authority.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[28029,"PRC-001-1.1(i)","R3.2.",null,"Each Transmission Operator shall coordinate all new protective systems and all protective system changes with neighboring Transmission Operators and Balancing Authorities.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[28030,"PRC-001-1.1(i)","R4.",null,"Each Transmission Operator shall coordinate Protection Systems on major transmission lines and interconnections with neighboring Generator Operators, Transmission Operators, and Balancing Authorities.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[28031,"PRC-001-1.1(i)","R5.","YES","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:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP","Yes",true,null,true]
[28032,"PRC-001-1.1(i)","R5.","YES","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:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP","Yes",true,null,true]
[28033,"PRC-001-1.1(i)","R5.","YES","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:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP","Yes",true,null,true]
[28034,"PRC-001-1.1(i)","R5.1.",null,"Each Generator Operator shall notify its Transmission Operator in advance of changes in generation or operating conditions that could require changes in the Transmission Operator’s Protection Systems.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[28036,"PRC-001-1.1(i)","R5.2.","YES","Each Transmission Operator shall notify neighboring Transmission Operators in advance of changes in generation, transmission, load, or operating conditions that could require changes in the other Transmission Operators’ Protection Systems.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[28037,"PRC-001-1.1(i)","R5.2.","YES","Each Transmission Operator shall notify neighboring Transmission Operators in advance of changes in generation, transmission, load, or operating conditions that could require changes in the other Transmission Operators’ Protection Systems.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[28035,"PRC-001-1.1(i)","R5.2.","YES","Each Transmission Operator shall notify neighboring Transmission Operators in advance of changes in generation, transmission, load, or operating conditions that could require changes in the other Transmission Operators’ Protection Systems.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[28038,"PRC-001-1.1(i)","R6.",null,"Each Transmission Operator and Balancing Authority shall monitor the status of each Remedial Action Scheme in their area, and shall notify affected Transmission Operators and Balancing Authorities of each change in status.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[28039,"PRC-001-1.1(ii)","R1.",null,"Each Transmission Operator, Balancing Authority, and Generator Operator shall be familiar with the purpose and limitations of Protection System schemes applied in its area.","2015-07-16","2020-09-30","Retired",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, BA","Yes",true,"System Control Order (SCO)                                                                                                               Protection and Aux. Outages                                                                                                              MR Chap 5, S6(6.1.3), S14 (14.1.2, 14.1.3),  S8",true]
[28043,"PRC-001-1.1(ii)","R3.",null,"A Generator Operator or Transmission Operator shall coordinate new protective systems and changes as follows.","2015-07-16","2020-09-30","Retired",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP","Yes",true,null,true]
[28044,"PRC-001-1.1(ii)","R3.1.",null,"Each Generator Operator shall coordinate all new protective systems and all protective system changes with its Transmission Operator and Host Balancing Authority.\n• Requirement R3.1 is not applicable to the individual generating units of dispersed power producing resources identified through Inclusion I4 of the Bulk Electric System definition.","2015-07-16","2020-09-30","Retired",null,"HIGH",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[28045,"PRC-001-1.1(ii)","R3.2.",null,"Each Transmission Operator shall coordinate all new protective systems and all protective system changes with neighboring Transmission Operators and Balancing Authorities.","2015-07-16","2020-09-30","Retired",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,"Assess and approve new or modifications to existing facilities through its CAA process to ensure appropriate coordination and assessment of any changes to the ICG.   Ch 4 s2 , Chap 5 s5(5.1.2.7, 5.1.2.8)",true,"Interconnection Agreements and Hydro One Change Control (NMI 0525)  procedures outline requirements"]
[28046,"PRC-001-1.1(ii)","R4.",null,"Each Transmission Operator shall coordinate Protection Systems on major transmission lines and interconnections with neighboring Generator Operators, Transmission Operators, and Balancing Authorities.","2015-07-16","2020-09-30","Retired",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,"Assess and approve new or modifications to existing facilities through its CAA process to ensure appropriate coordination and assessment of any changes to the ICG                        Ch 4 s2, Chap 5 s5(5.1.2.7, 5.1.2.8)",true,"Interconnection Agreements and Hydro One Change Control (NMI 0525)  procedures outline requirements"]
[28053,"PRC-001-2","R1.",null,"Each Transmission Operator, Balancing Authority, and Generator Operator shall be familiar with the purpose and limitations of Protection System schemes applied in its area.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, BA","Yes",true,null,true]
[28054,"PRC-001-2","R2.",null,"A Generator Operator or Transmission Operator shall coordinate new protective systems and changes as follows.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TOP, GOP","Yes",false,null,false]
[28055,"PRC-001-2","R2.1.",null,"Each Generator Operator shall coordinate all new protective systems and all protective system changes with its Transmission Operator and Host Balancing Authority.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[28056,"PRC-001-2","R2.2.",null,"Each Transmission Operator shall coordinate all new protective systems and all protective system changes with neighboring Transmission Operators and Balancing Authorities.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[28057,"PRC-001-2","R3.",null,"Each Transmission Operator shall coordinate Protection Systems on major transmission lines and interconnections with neighboring Generator Operators, Transmission Operators, and Balancing Authorities.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP","Yes",false,null,false]
[28058,"PRC-002-1","R1.",null,"The Regional Reliability Organization shall establish the following installation requirements for sequence of event recording:",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28059,"PRC-002-1","R1.1.",null,"Location, monitoring and recording requirements, including the following:",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28060,"PRC-002-1","R1.1.1.",null,"Criteria for equipment location (e.g., by voltage, geographic area, station size, etc.).",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28061,"PRC-002-1","R1.1.2.",null,"Devices to be monitored.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28062,"PRC-002-1","R2.",null,"The Regional Reliability Organization shall establish the following installation requirements for fault recording:",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28063,"PRC-002-1","R2.1.",null,"Location, monitoring and recording requirements, including the following:",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28064,"PRC-002-1","R2.1.1.",null,"Criteria for equipment location (e.g., by voltage, geographic area, station size, etc.).",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28065,"PRC-002-1","R2.1.2.",null,"Elements to be monitored at each location.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28066,"PRC-002-1","R2.1.3.",null,"Electrical quantities to be recorded for each monitored element shall be sufficient to determine the following:",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28067,"PRC-002-1","R2.1.3.1.",null,"Three phase to neutral voltages.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28068,"PRC-002-1","R2.1.3.2.",null,"Three phase currents and neutral currents.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28069,"PRC-002-1","R2.1.3.3.",null,"Polarizing currents and voltages, if used.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28070,"PRC-002-1","R2.1.3.4.",null,"Frequency.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28071,"PRC-002-1","R2.1.3.5.",null,"Megawatts and megavars.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28072,"PRC-002-1","R2.2.",null,"Technical requirements, including the following:",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28073,"PRC-002-1","R2.2.1.",null,"Recording duration requirements.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28074,"PRC-002-1","R2.2.2.",null,"Minimum sampling rate of 16 samples per cycle.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28075,"PRC-002-1","R2.2.3.",null,"Event triggering requirements.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28076,"PRC-002-1","R3.",null,"The Regional Reliability Organization shall establish the following installation requirements for dynamic Disturbance recording:",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28077,"PRC-002-1","R3.1.",null,"Location, monitoring and recording requirements including the following:",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28078,"PRC-002-1","R3.1.1.",null,"Criteria for equipment location giving consideration to the following:\n- Site(s) in or near major load centers\n- Site(s) in or near major generation clusters\n- Site(s) in or near major voltage sensitive areas\n- Site(s) on both sides of major transmission interfaces\n- A major transmission junction\n- Elements associated with Interconnection Reliability Operating Limits\n- Major EHV interconnections between control areas\n- Coordination with neighboring regions within the interconnection",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28079,"PRC-002-1","R3.1.2.",null,"Elements and number of phases to be monitored at each location.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28080,"PRC-002-1","R3.1.3.",null,"Electrical quantities to be recorded for each monitored element shall be sufficient to determine the following:",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28081,"PRC-002-1","R3.1.3.1.",null,"Voltage, current and frequency.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28082,"PRC-002-1","R3.1.3.2.",null,"Megawatts and megavars.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28083,"PRC-002-1","R3.2.",null,"Technical requirements, including the following:",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28084,"PRC-002-1","R3.2.1.",null,"Capability for continuous recording for devices installed after January 1, 2009.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28085,"PRC-002-1","R3.2.2.",null,"Each device shall sample data at a rate of at least 960 samples per second and shall record the RMS value of electrical quantities at a rate of at least 6 records per second.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28086,"PRC-002-1","R4.",null,"The Regional Reliability Organization shall establish requirements for facility owners to report Disturbance data recorded by their DME installations. The Disturbance data reporting requirements shall include the following:",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28087,"PRC-002-1","R4.1.",null,"Criteria for events that require the collection of data from DMEs.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28088,"PRC-002-1","R4.2.",null,"List of entities that must be provided with recorded Disturbance data.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28089,"PRC-002-1","R4.3.",null,"Timetable for response to data request.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28090,"PRC-002-1","R4.4.",null,"Provision for reporting Disturbance data in a format which is capable of being viewed, read and analyzed with a generic COMTRADE1 analysis tool,",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28091,"PRC-002-1","R4.5.",null,"Naming of data files in conformance with the IEEE C37.232 Recommended Practice for Naming Time Sequence Data Files2.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28092,"PRC-002-1","R4.6.",null,"Data content requirements and guidelines.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28093,"PRC-002-1","R5.",null,"The Regional Reliability Organization shall provide its requirements (and any revisions to those requirements) including those for DME installation and Disturbance data reporting to the affected Transmission Owners and Generator Owners within 30 calendar days of approval of those requirements.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28094,"PRC-002-1","R6.",null,"The Regional Reliability Organization shall periodically (at least every five years) review, update and approve its Regional requirements for Disturbance monitoring and reporting.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28095,"PRC-002-2","R1.",null,"Each Transmission Owner shall: [Violation Risk Factor: Lower ] [Time Horizon: Longterm Planning]","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[28096,"PRC-002-2","R1.1.",null,"Identify BES buses for which sequence of events recording (SER) and fault recording (FR) data is required by using the methodology in PRC-002-2, Attachment 1.","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[28097,"PRC-002-2","R1.2.",null,"Notify other owners of BES Elements connected to those BES buses, if any, within 90-calendar days of completion of Part 1.1, that those BES Elements require SER data and/or FR data.","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[28098,"PRC-002-2","R1.3.",null,"Re-evaluate all BES buses at least once every five calendar years in accordance with Part 1.1 and notify other owners, if any, in accordance with Part 1.2, and implement the re-evaluated list of BES buses as per the Implementation Plan.","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[28148,"PRC-002-2","R10.",null,"Each Transmission Owner and Generator Owner shall time synchronize all SER and FR data for the BES buses identified in Requirement R1 and DDR data for the BES Elements identified in Requirement R5 to meet the following: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28149,"PRC-002-2","R10.1.",null,"Synchronization to Coordinated Universal Time (UTC) with or without a local time offset.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28150,"PRC-002-2","R10.2.",null,"Synchronized device clock accuracy within ± 2 milliseconds of UTC.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28151,"PRC-002-2","R11.",null,"Each Transmission Owner and Generator Owner shall provide, upon request, all SER and FR data for the BES buses identified in Requirement R1 and DDR data for the BES Elements identified in Requirement R5 to the Responsible Entity, Regional Entity, or NERC in accordance with the following: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28152,"PRC-002-2","R11.1.",null,"Data will be retrievable for the period of 10-calendar days, inclusive of the day the data was recorded.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28153,"PRC-002-2","R11.2.",null,"Data subject to Part 11.1 will be provided within 30-calendar days of a request unless an extension is granted by the requestor.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28154,"PRC-002-2","R11.3.",null,"SER data will be provided in ASCII Comma Separated Value (CSV) format following Attachment 2.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28155,"PRC-002-2","R11.4.",null,"FR and DDR data will be provided in electronic files that are formatted in conformance with C37.111, (IEEE Standard for Common Format for Transient Data Exchange (COMTRADE), revision C37.111-1999 or later.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28156,"PRC-002-2","R11.5.",null,"Data files will be named in conformance with C37.232, IEEE Standard for Common Format for Naming Time Sequence Data Files (COMNAME), revision C37.232-2011 or later.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28157,"PRC-002-2","R12.",null,"Each Transmission Owner and Generator Owner shall, within 90-calendar days of the discovery of a failure of the recording capability for the SER, FR or DDR data, either: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]\n Restore the recording capability, or\n Submit a Corrective Action Plan (CAP) to the Regional Entity and implement it.","2016-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28099,"PRC-002-2","R2.",null,"Each Transmission Owner and Generator Owner shall have SER data for circuit breaker position (open/close) for each circuit breaker it owns connected directly to the BES buses identified in Requirement R1 and associated with the BES Elements at those BES buses. [Violation Risk Factor: Lower ] [Time Horizon: Long-term Planning]","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28100,"PRC-002-2","R3.",null,"Each Transmission Owner and Generator Owner shall have FR data to determine the following electrical quantities for each triggered FR for the BES Elements it owns connected to the BES buses identified in Requirement R1: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28101,"PRC-002-2","R3.1.",null,"Phase-to-neutral voltage for each phase of each specified BES bus.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28102,"PRC-002-2","R3.2.",null,"Each phase current and the residual or neutral current for the following BES Elements:","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28103,"PRC-002-2","R3.2.1.",null,"Transformers that have a low-side operating voltage of 100kV or above.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28104,"PRC-002-2","R3.2.2.",null,"Transmission Lines.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28105,"PRC-002-2","R4.",null,"Each Transmission Owner and Generator Owner shall have FR data as specified in Requirement R3 that meets the following: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28106,"PRC-002-2","R4.1.",null,"A single record or multiple records that include:\n• A pre-trigger record length of at least two cycles and a total record length of at\nleast 30-cycles for the same trigger point, or\n• At least two cycles of the pre-trigger data, the first three cycles of the posttrigger\ndata, and the final cycle of the fault as seen by the fault recorder.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28107,"PRC-002-2","R4.2.",null,"A minimum recording rate of 16 samples per cycle.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28108,"PRC-002-2","R4.3.",null,"Trigger settings for at least the following:","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28109,"PRC-002-2","R4.3.1.",null,"Neutral (residual) overcurrent.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28110,"PRC-002-2","R4.3.2.",null,"Phase undervoltage or overcurrent.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28112,"PRC-002-2","R5.","YES","Each Responsible Entity shall: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RE, PC","No",false,null,false]
[28111,"PRC-002-2","R5.","YES","Each Responsible Entity shall: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RE, PC","No",false,null,false]
[28113,"PRC-002-2","R5.","YES","Each Responsible Entity shall: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RE, PC","No",false,null,false]
[28115,"PRC-002-2","R5.1.","YES","Identify BES Elements for which dynamic Disturbance recording (DDR) data is required, including the following:","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RE, PC","No",false,null,false]
[28116,"PRC-002-2","R5.1.","YES","Identify BES Elements for which dynamic Disturbance recording (DDR) data is required, including the following:","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RE, PC","No",false,null,false]
[28117,"PRC-002-2","R5.1.1.",null,"Generating resource(s) with:","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RE, PC","No",false,null,false]
[28118,"PRC-002-2","R5.1.1.1.",null,"Gross individual nameplate rating greater than or equal to 500 MVA.","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RE, PC","No",false,null,false]
[28119,"PRC-002-2","R5.1.1.2.",null,"Gross individual nameplate rating greater than or equal to 300 MVA where the gross plant/facility aggregate nameplate rating is greater than or equal to 1,000 MVA.","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RE, PC","No",false,null,false]
[28120,"PRC-002-2","R5.1.2.",null,"Any one BES Element that is part of a stability (angular or voltage) related System Operating Limit (SOL).","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RE, PC","No",false,null,false]
[28121,"PRC-002-2","R5.1.3.",null,"Each terminal of a high voltage direct current (HVDC) circuit with a nameplate rating greater than or equal to 300 MVA, on the alternating current (AC) portion of the converter.","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RE, PC","No",false,null,false]
[28122,"PRC-002-2","R5.1.4.",null,"One or more BES Elements that are part of an Interconnection Reliability Operating Limit (IROL).","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RE, PC","No",false,null,false]
[28123,"PRC-002-2","R5.1.5.",null,"Any one BES Element within a major voltage sensitive area as defined by an area with an in-service undervoltage load shedding (UVLS) program.","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RE, PC","No",false,null,false]
[28124,"PRC-002-2","R5.2.",null,"Identify a minimum DDR coverage, inclusive of those BES Elements identified in Part 5.1, of at least:","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RE, PC","No",false,null,false]
[28125,"PRC-002-2","R5.2.1.",null,"One BES Element; and","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RE, PC","No",false,null,false]
[28126,"PRC-002-2","R5.2.2.",null,"One BES Element per 3,000 MW of the Responsible Entity’s historical simultaneous peak System Demand.","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RE, PC","No",false,null,false]
[28127,"PRC-002-2","R5.3.",null,"Notify all owners of identified BES Elements, within 90-calendar days of completion of Part 5.1, that their respective BES Elements require DDR data when requested.","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RE, PC","No",false,null,false]
[28130,"PRC-002-2","R5.4.","YES","Re-evaluate all BES Elements at least once every five calendar years in accordance with Parts 5.1 and 5.2, and notify owners in accordance with Part 5.3 to implement the re-evaluated list of BES Elements as per the Implementation Plan.","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RE, PC","No",false,null,false]
[28129,"PRC-002-2","R5.4.","YES","Re-evaluate all BES Elements at least once every five calendar years in accordance with Parts 5.1 and 5.2, and notify owners in accordance with Part 5.3 to implement the re-evaluated list of BES Elements as per the Implementation Plan.","2016-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","RE, PC","No",false,null,false]
[28132,"PRC-002-2","R6.",null,"Each Transmission Owner shall have DDR data to determine the following electrical quantities for each BES Element it owns for which it received notification as identified in Requirement R5: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning ]","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[28133,"PRC-002-2","R6.1.",null,"One phase-to-neutral or positive sequence voltage.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[28134,"PRC-002-2","R6.2.",null,"The phase current for the same phase at the same voltage corresponding to the voltage in Requirement R6, Part 6.1, or the positive sequence current.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[28135,"PRC-002-2","R6.3.",null,"Real Power and Reactive Power flows expressed on a three phase basis corresponding to all circuits where current measurements are required.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[28136,"PRC-002-2","R6.4.",null,"Frequency of any one of the voltage(s) in Requirement R6, Part 6.1.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[28137,"PRC-002-2","R7.",null,"Each Generator Owner shall have DDR data to determine the following electrical quantities for each BES Element it owns for which it received notification as identified in Requirement R5: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2021-07-11",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28138,"PRC-002-2","R7.1.",null,"One phase-to-neutral, phase-to-phase, or positive sequence voltage at either the generator step-up transformer (GSU) high-side or low-side voltage level.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28139,"PRC-002-2","R7.2.",null,"The phase current for the same phase at the same voltage corresponding to the voltage in Requirement R7, Part 7.1, phase current(s) for any phase-to-phase voltages, or positive sequence current.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28140,"PRC-002-2","R7.3.",null,"Real Power and Reactive Power flows expressed on a three phase basis corresponding to all circuits where current measurements are required.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28141,"PRC-002-2","R7.4.",null,"Frequency of at least one of the voltages in Requirement R7, Part 7.1.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28142,"PRC-002-2","R8.",null,"Each Transmission Owner and Generator Owner responsible for DDR data for the BES Elements identified in Requirement R5 shall have continuous data recording and storage. If the equipment was installed prior to the effective date of this standard and is not capable of continuous recording, triggered records must meet the following: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28143,"PRC-002-2","R8.1.",null,"Triggered record lengths of at least three minutes.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28144,"PRC-002-2","R8.2.",null,"At least one of the following three triggers:\n Off nominal frequency trigger set at:\n                                                                            Low                High\no Eastern Interconnection                 <59.75 Hz      >61.0 Hz\no Western Interconnection               <59.55 Hz      >61.0 Hz\no ERCOT Interconnection                <59.35 Hz      >61.0 Hz\no Hydro-Quebec Interconnection   <58.55 Hz      >61.5 Hz                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 \n Rate of change of frequency trigger set at:\no Eastern Interconnection                < -0.03125 Hz/sec               > 0.125 Hz/sec\no Western Interconnection              < -0.05625 Hz/sec              > 0.125 Hz/sec\no ERCOT Interconnection               < -0.08125 Hz/sec              > 0.125 Hz/sec\no Hydro-Quebec Interconnection  < -0.18125 Hz/sec               > 0.1875 Hz/sec\n Undervoltage trigger set no lower than 85 percent of normal operating voltage\nfor a duration of 5 seconds.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28145,"PRC-002-2","R9.",null,"Each Transmission Owner and Generator Owner responsible for DDR data for the BES Elements identified in Requirement R5 shall have DDR data that meet the following: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28146,"PRC-002-2","R9.1.",null,"Input sampling rate of at least 960 samples per second.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28147,"PRC-002-2","R9.2.",null,"Output recording rate of electrical quantities of at least 30 times per second.","2021-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30520,"PRC-002-3","R1.",null,"Each Transmission Owner shall: [Violation Risk Factor: Lower ] [Time Horizon: Longterm Planning]","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30521,"PRC-002-3","R1.1.",null,"Identify BES buses for which sequence of events recording (SER) and fault recording (FR) data is required by using the methodology in PRC-002-3, Attachment 1.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30522,"PRC-002-3","R1.2.",null,"Notify other owners of BES Elements connected to those BES buses, if any, within 90-calendar days of completion of Part 1.1, that those BES Elements require SER data and/or FR data.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30523,"PRC-002-3","R1.3.",null,"Re-evaluate all BES buses at least once every five calendar years in accordance with Part 1.1 and notify other owners, if any, in accordance with Part 1.2, and implement the re-evaluated list of BES buses as per the Implementation Plan.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30566,"PRC-002-3","R10.",null,"Each Transmission Owner and Generator Owner shall time synchronize all SER and FR data for the BES buses identified in Requirement R1 and DDR data for the BES Elements identified in Requirement R5 to meet the following: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30567,"PRC-002-3","R10.1.",null,"Synchronization to Coordinated Universal Time (UTC) with or without a local time offset.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30568,"PRC-002-3","R10.2.",null,"Synchronized device clock accuracy within ± 2 milliseconds of UTC.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30569,"PRC-002-3","R11.",null,"Each Transmission Owner and Generator Owner shall provide, upon request, all SER and FR data for the BES buses identified in Requirement R1 and DDR data for the BES Elements identified in Requirement R5 to the Reliability Coordinator, Regional Entity, or NERC in accordance with the following: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30570,"PRC-002-3","R11.1.",null,"Data will be retrievable for the period of 10-calendar days, inclusive of the day the data was recorded.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30571,"PRC-002-3","R11.2.",null,"Data subject to Part 11.1 will be provided within 30-calendar days of a request unless an extension is granted by the requestor.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30572,"PRC-002-3","R11.3.",null,"SER data will be provided in ASCII Comma Separated Value (CSV) format following Attachment 2.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30573,"PRC-002-3","R11.4.",null,"FR and DDR data will be provided in electronic files that are formatted in conformance with C37.111, (IEEE Standard for Common Format for Transient Data Exchange (COMTRADE), revision C37.111-1999 or later.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30574,"PRC-002-3","R11.5.",null,"Data files will be named in conformance with C37.232, IEEE Standard for Common Format for Naming Time Sequence Data Files (COMNAME), revision C37.232-2011 or later.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30575,"PRC-002-3","R12.",null,"Each Transmission Owner and Generator Owner shall, within 90-calendar days of the discovery of a failure of the recording capability for the SER, FR or DDR data, either: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]\n Restore the recording capability, or\n Submit a Corrective Action Plan (CAP) to the Regional Entity and implement it.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30524,"PRC-002-3","R2.",null,"Each Transmission Owner and Generator Owner shall have SER data for circuit breaker position (open/close) for each circuit breaker it owns connected directly to the BES buses identified in Requirement R1 and associated with the BES Elements at those BES buses. [Violation Risk Factor: Lower ] [Time Horizon: Long-term Planning]","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30525,"PRC-002-3","R3.",null,"Each Transmission Owner and Generator Owner shall have FR data to determine the following electrical quantities for each triggered FR for the BES Elements it owns connected to the BES buses identified in Requirement R1: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30526,"PRC-002-3","R3.1.",null,"Phase-to-neutral voltage for each phase of each specified BES bus.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30527,"PRC-002-3","R3.2.",null,"Each phase current and the residual or neutral current for the following BES Elements:","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30528,"PRC-002-3","R3.2.1.",null,"Transformers that have a low-side operating voltage of 100kV or above.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30529,"PRC-002-3","R3.2.2.",null,"Transmission Lines.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30530,"PRC-002-3","R4.",null,"Each Transmission Owner and Generator Owner shall have FR data as specified in Requirement R3 that meets the following: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30531,"PRC-002-3","R4.1.",null,"A single record or multiple records that include:\n• A pre-trigger record length of at least two cycles and a total record length of at\nleast 30-cycles for the same trigger point, or\n• At least two cycles of the pre-trigger data, the first three cycles of the posttrigger\ndata, and the final cycle of the fault as seen by the fault recorder.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30532,"PRC-002-3","R4.2.",null,"A minimum recording rate of 16 samples per cycle.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30533,"PRC-002-3","R4.3.",null,"Trigger settings for at least the following:","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30534,"PRC-002-3","R4.3.1.",null,"Neutral (residual) overcurrent.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30535,"PRC-002-3","R4.3.2.",null,"Phase undervoltage or overcurrent.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30536,"PRC-002-3","R5.",null,"Each Reliability Coordinator shall: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30537,"PRC-002-3","R5.1.",null,"Identify BES Elements for which dynamic Disturbance recording (DDR) data is required, including the following:","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30538,"PRC-002-3","R5.1.1.",null,"Generating resource(s) with:","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30539,"PRC-002-3","R5.1.1.1.",null,"Gross individual nameplate rating greater than or equal to 500 MVA.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30540,"PRC-002-3","R5.1.1.2.",null,"Gross individual nameplate rating greater than or equal to 300 MVA where the gross plant/facility aggregate nameplate rating is greater than or equal to 1,000 MVA.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30541,"PRC-002-3","R5.1.2.",null,"Any one BES Element that is part of a stability (angular or voltage) related System Operating Limit (SOL).","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30542,"PRC-002-3","R5.1.3.",null,"Each terminal of a high voltage direct current (HVDC) circuit with a nameplate rating greater than or equal to 300 MVA, on the alternating current (AC) portion of the converter.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30543,"PRC-002-3","R5.1.4.",null,"One or more BES Elements that are part of an Interconnection Reliability Operating Limit (IROL).","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30544,"PRC-002-3","R5.1.5.",null,"Any one BES Element within a major voltage sensitive area as defined by an area with an in-service undervoltage load shedding (UVLS) program.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30545,"PRC-002-3","R5.2.",null,"Identify a minimum DDR coverage, inclusive of those BES Elements identified in Part 5.1, of at least:","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30546,"PRC-002-3","R5.2.1.",null,"One BES Element; and","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30547,"PRC-002-3","R5.2.2.",null,"One BES Element per 3,000 MW of the Reliability Coordinator’s historical simultaneous peak System Demand.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30548,"PRC-002-3","R5.3.",null,"Notify all owners of identified BES Elements, within 90-calendar days of completion of Part 5.1, that their respective BES Elements require DDR data when requested.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30549,"PRC-002-3","R5.4.",null,"Re-evaluate all BES Elements at least once every five calendar years in accordance with Parts 5.1 and 5.2, and notify owners in accordance with Part 5.3 to implement the re-evaluated list of BES Elements as per the Implementation Plan.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30550,"PRC-002-3","R6.",null,"Each Transmission Owner shall have DDR data to determine the following electrical quantities for each BES Element it owns for which it received notification as identified in Requirement R5: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning ]","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30551,"PRC-002-3","R6.1.",null,"One phase-to-neutral or positive sequence voltage.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30552,"PRC-002-3","R6.2.",null,"The phase current for the same phase at the same voltage corresponding to the voltage in Requirement R6, Part 6.1, or the positive sequence current.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30553,"PRC-002-3","R6.3.",null,"Real Power and Reactive Power flows expressed on a three phase basis corresponding to all circuits where current measurements are required.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30554,"PRC-002-3","R6.4.",null,"Frequency of any one of the voltage(s) in Requirement R6, Part 6.1.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30555,"PRC-002-3","R7.",null,"Each Generator Owner shall have DDR data to determine the following electrical quantities for each BES Element it owns for which it received notification as identified in Requirement R5: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30556,"PRC-002-3","R7.1.",null,"One phase-to-neutral, phase-to-phase, or positive sequence voltage at either the generator step-up transformer (GSU) high-side or low-side voltage level.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30557,"PRC-002-3","R7.2.",null,"The phase current for the same phase at the same voltage corresponding to the voltage in Requirement R7, Part 7.1, phase current(s) for any phase-to-phase voltages, or positive sequence current.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30558,"PRC-002-3","R7.3.",null,"Real Power and Reactive Power flows expressed on a three phase basis corresponding to all circuits where current measurements are required.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30559,"PRC-002-3","R7.4.",null,"Frequency of at least one of the voltages in Requirement R7, Part 7.1.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30560,"PRC-002-3","R8.",null,"Each Transmission Owner and Generator Owner responsible for DDR data for the BES Elements identified in Requirement R5 shall have continuous data recording and storage. If the equipment was installed prior to the effective date of this standard and is not capable of continuous recording, triggered records must meet the following: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30561,"PRC-002-3","R8.1.",null,"Triggered record lengths of at least three minutes.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30562,"PRC-002-3","R8.2.",null,"At least one of the following three triggers:\n Off nominal frequency trigger set at:\n                                                                            Low                High\no Eastern Interconnection                 <59.75 Hz      >61.0 Hz\no Western Interconnection               <59.55 Hz      >61.0 Hz\no ERCOT Interconnection                <59.35 Hz      >61.0 Hz\no Hydro-Quebec Interconnection   <58.55 Hz      >61.5 Hz                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 \n Rate of change of frequency trigger set at:\no Eastern Interconnection                < -0.03125 Hz/sec               > 0.125 Hz/sec\no Western Interconnection              < -0.05625 Hz/sec              > 0.125 Hz/sec\no ERCOT Interconnection               < -0.08125 Hz/sec              > 0.125 Hz/sec\no Hydro-Quebec Interconnection  < -0.18125 Hz/sec               > 0.1875 Hz/sec\n Undervoltage trigger set no lower than 85 percent of normal operating voltage\nfor a duration of 5 seconds.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30563,"PRC-002-3","R9.",null,"Each Transmission Owner and Generator Owner responsible for DDR data for the BES Elements identified in Requirement R5 shall have DDR data that meet the following: [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30564,"PRC-002-3","R9.1.",null,"Input sampling rate of at least 960 samples per second.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[30565,"PRC-002-3","R9.2.",null,"Output recording rate of electrical quantities of at least 30 times per second.","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, RC, GO","Yes",false,null,false]
[28242,"PRC-003-1","R1.",null,"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:",null,null,"Retired",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28243,"PRC-003-1","R1.1.",null,"The Protection Systems to be reviewed and analyzed for Misoperations (due to theirpotential impact on BES reliability).",null,null,"Retired",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28244,"PRC-003-1","R1.2.",null,"Data reporting requirements (periodicity and format) for Misoperations.",null,null,"Retired",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28245,"PRC-003-1","R1.3.",null,"Process for review, analysis follow up, and documentation of Corrective Action Plans for Misoperations.",null,null,"Retired",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28246,"PRC-003-1","R1.4.",null,"Identification of the Regional Reliability Organization group responsible for the procedures and the process for approval of the procedures.",null,null,"Retired",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28247,"PRC-003-1","R2.",null,"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.",null,null,"Retired",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28248,"PRC-003-1","R3.",null,"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\napproval of those procedures.",null,null,"Retired",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28249,"PRC-004-2","R1.",null,"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 Entity’s procedures.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28250,"PRC-004-2","R2.",null,"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 Entity’s procedures.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28251,"PRC-004-2","R3.",null,"The Transmission Owner, any Distribution Provider that owns a transmission Protection System, and the Generator Owner shall each provide to its Regional Entity, documentation of its Misoperations analyses and Corrective Action Plans according to the Regional Entity’s procedures.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28258,"PRC-004-3","R1.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that owns a BES interrupting device that operated under the circumstances in Parts 1.1 through 1.3 shall, within 120 calendar days of the BES interrupting device operation, identify whether its Protection System component(s) caused a Misoperation: [Violation Risk Factor: Medium][Time Horizon: Operations Assessment, Operations Planning]",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28259,"PRC-004-3","R1.1.",null,"The BES interrupting device operation was caused by a Protection System or by manual intervention in response to a Protection System failure to operate; and",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28260,"PRC-004-3","R1.2.",null,"The BES interrupting device owner owns all or part of the Composite Protection System; and",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28261,"PRC-004-3","R1.3.",null,"The BES interrupting device owner identified that its Protection System component(s) caused the BES interrupting device(s) operation or was caused by manual intervention in response to its Protection System failure to operate.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28262,"PRC-004-3","R2.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that owns a BES interrupting device that operated shall, within 120 calendar days of the BES interrupting device operation, provide notification as described in Parts 2.1 and 2.2. [Violation Risk Factor: Medium][Time Horizon: Operations Assessment, Operations Planning]",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28263,"PRC-004-3","R2.1.",null,"For a BES interrupting device operation by a Composite Protection System or by manual intervention in response to a Protection System failure to operate, notification of the operation shall be provided to the other owner(s) that share Misoperation identification responsibility for the Composite Protection System under the following circumstances:",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28264,"PRC-004-3","R2.1.1.",null,"The BES interrupting device owner shares the Composite Protection System ownership with any other owner; and",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28265,"PRC-004-3","R2.1.2.",null,"The BES interrupting device owner has determined that a Misoperation occurred or cannot rule out a Misoperation; and",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28266,"PRC-004-3","R2.1.3.",null,"The BES interrupting device owner has determined that its Protection System component(s) did not cause the BES interrupting device(s) operation or cannot determine whether its Protection System components caused the BES interrupting device(s) operation.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28267,"PRC-004-3","R2.2.",null,"For a BES interrupting device operation by a Protection System component intended to operate as backup protection for a condition on another entity’s BES Element, notification of the operation shall be provided to the other Protection System owner(s) for which that backup protection was provided.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28268,"PRC-004-3","R3.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that receives notification, pursuant to Requirement R2 shall, within the later of 60 calendar days of notification or 120 calendar days of the BES interrupting device(s) operation, identify whether its Protection System component(s) caused a Misoperation. [Violation Risk Factor: Medium][Time Horizon: Operations Assessment, Operations Planning]",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28269,"PRC-004-3","R4.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that receives notification, pursuant to Requirement R2 shall, within the later of 60 calendar days of notification or 120 calendar days of the BES interrupting device(s) operation, identify whether its Protection System component(s) caused a Misoperation. [Violation Risk Factor: Medium][Time Horizon: Operations Assessment, Operations Planning]",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28270,"PRC-004-3","R5.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that owns the Protection System component(s) that caused the Misoperation shall, within 60 calendar days of first identifying a cause of the Misoperation: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning, Long-Term Planning]\n Develop a Corrective Action Plan (CAP) for the identified Protection System component(s), and an evaluation of the CAP’s applicability to the entity’s other Protection Systems including other locations; or\n Explain in a declaration why corrective actions are beyond the entity’s control or would not improve BES reliability, and that no further corrective actions will be taken.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28271,"PRC-004-3","R6.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall implement each CAP developed in Requirement R5, and update each CAP if actions or timetables change, until completed. [Violation Risk Factor: Medium][Time Horizon: Operations Planning, Long-Term Planning]",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28272,"PRC-004-3(i)","R1.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that owns a BES interrupting device that operated under the circumstances in Parts 1.1 through 1.3 shall, within 120 calendar days of the BES interrupting device operation, identify whether its Protection System component(s) caused a Misoperation: [Violation Risk Factor: High][Time Horizon: Operations Assessment, Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28273,"PRC-004-3(i)","R1.1.",null,"The BES interrupting device operation was caused by a Protection System or by manual intervention in response to a Protection System failure to operate; and",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28274,"PRC-004-3(i)","R1.2.",null,"The BES interrupting device owner owns all or part of the Composite Protection System; and",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28275,"PRC-004-3(i)","R1.3.",null,"The BES interrupting device owner identified that its Protection System component(s) caused the BES interrupting device(s) operation or was caused by manual intervention in response to its Protection System failure to operate.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28276,"PRC-004-3(i)","R2.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that owns a BES interrupting device that operated shall, within 120 calendar days of the BES interrupting device operation, provide notification as described in Parts 2.1 and 2.2. [Violation Risk Factor: High][Time Horizon: Operations Assessment, Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28277,"PRC-004-3(i)","R2.1.",null,"For a BES interrupting device operation by a Composite Protection System or by manual intervention in response to a Protection System failure to operate, notification of the operation shall be provided to the other owner(s) that share Misoperation identification responsibility for the Composite Protection System\nunder the following circumstances:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28278,"PRC-004-3(i)","R2.1.1.",null,"The BES interrupting device owner shares the Composite Protection System ownership with any other owner; and",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28279,"PRC-004-3(i)","R2.1.2.",null,"The BES interrupting device owner has determined that a Misoperation occurred or cannot rule out a Misoperation; and",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28280,"PRC-004-3(i)","R2.1.3.",null,"The BES interrupting device owner has determined that its Protection System component(s) did not cause the BES interrupting device(s) operation or cannot determine whether its Protection System components caused the BES interrupting device(s) operation.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28281,"PRC-004-3(i)","R2.2.",null,"For a BES interrupting device operation by a Protection System component intended to operate as backup protection for a condition on another entity’s BES Element, notification of the operation shall be provided to the other Protection System owner(s) for which that backup protection was provided.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28282,"PRC-004-3(i)","R3.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that receives notification, pursuant to Requirement R2 shall, within the later of 60 calendar days of notification or 120 calendar days of the BES interrupting device(s) operation, identify whether its Protection System component(s) caused a Misoperation. [Violation Risk Factor: High][Time Horizon: Operations Assessment, Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28283,"PRC-004-3(i)","R4.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that has not determined the cause(s) of a Misoperation, for a Misoperation identified in accordance with Requirement R1 or R3, shall perform investigative action(s) to determine the cause(s) of the Misoperation at least once every two full calendar quarters after the Misoperation was first identified, until one of the following completes the investigation: [Violation Risk Factor: High] [Time Horizon:  Operations Assessment, Operations Planning]\n\n● The identification of the cause(s) of the Misoperation; or\n\n● A declaration that no cause was identified.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28284,"PRC-004-3(i)","R5.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that owns the Protection System component(s) that caused the Misoperation shall, within 60 calendar days of first identifying a cause of the Misoperation: [Violation Risk Factor: High] [Time Horizon: Operations Planning, Long-Term Planning]\n\n● Develop a Corrective Action Plan (CAP) for the identified Protection System component(s), and an evaluation of the CAP’s applicability to the entity’s other Protection Systems including other locations; or \n\n● Explain in a declaration why corrective actions are beyond the entity’s control or would not improve BES reliability, and that no further corrective actions will be taken.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28285,"PRC-004-3(i)","R6.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall implement each CAP developed in Requirement R5, and update each CAP if actions or timetables change, until completed. [Violation Risk Factor: High][Time Horizon: Operations Planning, Long-Term Planning]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28286,"PRC-004-4","R1.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that owns a BES interrupting device that operated under the circumstances in Parts 1.1 through 1.3 shall, within 120 calendar days of the BES interrupting device operation, identify whether its Protection System component(s) caused a Misoperation: [Violation Risk Factor: Medium][Time Horizon: Operations Assessment, Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28287,"PRC-004-4","R1.1.",null,"The BES interrupting device operation was caused by a Protection System or by manual intervention in response to a Protection System failure to operate; and",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28288,"PRC-004-4","R1.2.",null,"The BES interrupting device owner owns all or part of the Composite Protection System; and",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28289,"PRC-004-4","R1.3.",null,"The BES interrupting device owner identified that its Protection System component(s) caused the BES interrupting device(s) operation or was caused by manual intervention in response to its Protection System failure to operate.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28290,"PRC-004-4","R2.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that owns a BES interrupting device that operated shall, within 120 calendar days of the BES interrupting device operation, provide notification as described in Parts 2.1 and 2.2. [Violation Risk Factor: Medium][Time Horizon: Operations Assessment, Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28291,"PRC-004-4","R2.1.",null,"For a BES interrupting device operation by a Composite Protection System or by manual intervention in response to a Protection System failure to operate, notification of the operation shall be provided to the other owner(s) that share Misoperation identification responsibility for the Composite Protection System under the following circumstances:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28292,"PRC-004-4","R2.1.1.",null,"The BES interrupting device owner shares the Composite Protection System ownership with any other owner; and",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28293,"PRC-004-4","R2.1.2.",null,"The BES interrupting device owner has determined that a Misoperation occurred or cannot rule out a Misoperation; and",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28294,"PRC-004-4","R2.1.3.",null,"The BES interrupting device owner has determined that its Protection System component(s) did not cause the BES interrupting device(s) operation or cannot determine whether its Protection System components caused the BES interrupting device(s) operation.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28295,"PRC-004-4","R2.2.",null,"For a BES interrupting device operation by a Protection System component intended to operate as backup protection for a condition on another entity’s BES Element, notification of the operation shall be provided to the other Protection System owner(s) for which that backup protection was provided.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28296,"PRC-004-4","R3.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that receives notification, pursuant to Requirement R2 shall, within the later of 60 calendar days of notification or 120 calendar days of the BES interrupting device(s) operation, identify whether its Protection System component(s) caused a Misoperation. [Violation Risk Factor: Medium][Time Horizon: Operations Assessment, Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28297,"PRC-004-4","R4.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that has not determined the cause(s) of a Misoperation, for a Misoperation identified in accordance with Requirement R1 or R3, shall perform investigative action(s) to determine the cause(s) of the Misoperation at least once every two full calendar quarters after the Misoperation was first identified, until one of the following completes the investigation: [Violation Risk Factor: Medium] [Time Horizon: Operations Assessment, Operations Planning]\n The identification of the cause(s) of the Misoperation; or\n A declaration that no cause was identified.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28298,"PRC-004-4","R5.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that owns the Protection System component(s) that caused the Misoperation shall, within 60 calendar days of first identifying a cause of the Misoperation: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning, Long-Term Planning]\n Develop a Corrective Action Plan (CAP) for the identified Protection System component(s), and an evaluation of the CAP’s applicability to the entity’s other Protection Systems including other locations; or\n Explain in a declaration why corrective actions are beyond the entity’s control or would not improve BES reliability, and that no further corrective actions will be taken.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28299,"PRC-004-4","R6.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall implement each CAP developed in Requirement R5, and update each CAP if actions or timetables change, until completed. [Violation Risk Factor: Medium][Time Horizon: Operations Planning, Long-Term Planning]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28314,"PRC-004-5","R1.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that owns a BES interrupting device that operated under the circumstances in Parts 1.1 through 1.3 shall, within 120 calendar days of the BES interrupting device operation, identify whether its Protection System component(s) caused a Misoperation: [Violation Risk Factor: Medium][Time Horizon: Operations Assessment, Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28315,"PRC-004-5","R1.1.",null,"The BES interrupting device operation was caused by a Protection System or by manual intervention in response to a Protection System failure to operate; and",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28316,"PRC-004-5","R1.2.",null,"The BES interrupting device owner owns all or part of the Composite Protection System; and",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28317,"PRC-004-5","R1.3.",null,"The BES interrupting device owner identified that its Protection System component(s) caused the BES interrupting device(s) operation or was caused by manual intervention in response to its Protection System failure to operate.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28318,"PRC-004-5","R2.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that owns a BES interrupting device that operated shall, within 120 calendar days of the BES interrupting device operation, provide notification as described in Parts 2.1 and 2.2. [Violation Risk Factor: Medium][Time Horizon: Operations Assessment, Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28319,"PRC-004-5","R2.1.",null,"For a BES interrupting device operation by a Composite Protection System or by manual intervention in response to a Protection System failure to operate, notification of the operation shall be provided to the other owner(s) that share Misoperation identification responsibility for the Composite Protection System under the following circumstances:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28320,"PRC-004-5","R2.1.1.",null,"The BES interrupting device owner shares the Composite Protection System ownership with any other owner; and",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28321,"PRC-004-5","R2.1.2.",null,"The BES interrupting device owner has determined that a Misoperation occurred or cannot rule out a Misoperation; and",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28322,"PRC-004-5","R2.1.3.",null,"The BES interrupting device owner has determined that its Protection System component(s) did not cause the BES interrupting device(s) operation or cannot determine whether its Protection System components caused the BES interrupting device(s) operation.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28323,"PRC-004-5","R2.2.",null,"For a BES interrupting device operation by a Protection System component intended to operate as backup protection for a condition on another entity’s BES Element, notification of the operation shall be provided to the other Protection System owner(s) for which that backup protection was provided.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28324,"PRC-004-5","R3.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that receives notification, pursuant to Requirement R2 shall, within the later of 60 calendar days of notification or 120 calendar days of the BES interrupting device(s) operation, identify whether its Protection System component(s) caused a Misoperation. [Violation RisK Factor: Medium][Time Horizon: Operations Assessment, Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28325,"PRC-004-5","R4.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that has not determined the cause(s) of a Misoperation, for a Misoperation identified in accordance with Requirement R1 or R3, shall perform investigative action(s) to determine the cause(s) of the Misoperation at least once every two full calendar quarters after the Misoperation was first identified, until one of the following completes the investigation: [Violation Risk Factor: Medium] [Time Horizon: Operations Assessment, Operations Planning]\n The identification of the cause(s) of the Misoperation; or\n A declaration that no cause was identified.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28326,"PRC-004-5","R5.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that owns the Protection System component(s) that caused the Misoperation shall, within 60 calendar days of first identifying a cause of the Misoperation: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning, Long‐Term Planning]\n Develop a Corrective Action Plan (CAP) for the identified Protection System component(s), and an evaluation of the CAP’s applicability to the entity’s other Protection Systems including other locations; or\n Explain in a declaration why corrective actions are beyond the entity’s control or would not improve BES reliability, and that no further corrective actions will be taken.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28327,"PRC-004-5","R6.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall implement each CAP developed in Requirement R5, and update each CAP if actions or timetables change, until completed. [Violation Risk Factor: Medium][Time Horizon: Operations Planning, Long‐Term Planning]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28328,"PRC-004-5(i)","R1.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that owns a BES interrupting device that operated under the circumstances in Parts 1.1 through 1.3 shall, within 120 calendar days of the BES interrupting device operation, identify whether its Protection System component(s) caused a Misoperation: [Violation Risk Factor: High][Time Horizon: Operations Assessment, Operations Planning]","2017-04-02","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28329,"PRC-004-5(I)","R1.1.",null,"The BES interrupting device operation was caused by a Protection System or by manual intervention in response to a Protection System failure to operate; and","2017-04-02","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28330,"PRC-004-5(I)","R1.2.",null,"The BES interrupting device owner owns all or part of the Composite Protection System; and","2017-04-02","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28331,"PRC-004-5(I)","R1.3.",null,"The BES interrupting device owner identified that its Protection System component(s) caused the BES interrupting device(s) operation or was caused by manual intervention in response to its Protection System failure to operate.","2017-04-02","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28332,"PRC-004-5(I)","R2.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that owns a BES interrupting device that operated shall, within 120 calendar days of the BES interrupting device operation, provide notification as described in Parts 2.1 and 2.2. [Violation Risk Factor: High][Time Horizon: Operations Assessment, Operations Planning]","2017-04-02","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28333,"PRC-004-5(I)","R2.1.",null,"For a BES interrupting device operation by a Composite Protection System or by manual intervention in response to a Protection System failure to operate, notification of the operation shall be provided to the other owner(s) that share Misoperation identification responsibility for the Composite Protection System under the following circumstances:","2017-04-02","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28334,"PRC-004-5(I)","R2.1.1.",null,"The BES interrupting device owner shares the Composite Protection System ownership with any other owner; and","2017-04-02","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28335,"PRC-004-5(I)","R2.1.2.",null,"The BES interrupting device owner has determined that a Misoperation occurred or cannot rule out a Misoperation; and","2017-04-02","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28336,"PRC-004-5(I)","R2.1.3.",null,"The BES interrupting device owner has determined that its Protection System component(s) did not cause the BES interrupting device(s) operation or cannot determine whether its Protection System components caused the BES interrupting device(s) operation.","2017-04-02","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28337,"PRC-004-5(I)","R2.2.",null,"For a BES interrupting device operation by a Protection System component intended to operate as backup protection for a condition on another entity’s BES Element, notification of the operation shall be provided to the other Protection System owner(s) for which that backup protection was provided.","2017-04-02","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28338,"PRC-004-5(I)","R3.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that receives notification, pursuant to Requirement R2 shall, within the later of 60 calendar days of notification or 120 calendar days of the BES interrupting device(s) operation, identify whether its Protection System component(s) caused a Misoperation. [Violation Risk Factor: High][Time Horizon: Operations Assessment, Operations Planning]","2017-04-02","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28339,"PRC-004-5(I)","R4.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that has not determined the cause(s) of a Misoperation, for a Misoperation identified in accordance with Requirement R1 or R3, shall perform investigative action(s) to determine the cause(s) of the Misoperation at least once every two full calendar quarters after the Misoperation was first identified, until one of the following completes the investigation: [Violation Risk Factor: High] [Time Horizon: Operations Assessment, Operations Planning]\n\n● The identification of the cause(s) of the Misoperation; or\n\n● A declaration that no cause was identified.","2017-04-02","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28340,"PRC-004-5(I)","R5.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that owns the Protection System component(s) that caused the Misoperation shall, within 60 calendar days of first identifying a cause of the Misoperation: [Violation Risk Factor: High] [Time Horizon: Operations Planning, Long‐Term Planning] \n\n● Develop a Corrective Action Plan (CAP) for the identified Protection System component(s), and an evaluation of the CAP’s applicability to the entity’s other Protection Systems including other locations; or \n\n● Explain in a declaration why corrective actions are beyond the entity’s control or would not improve BES reliability, and that no further corrective actions will be taken.","2017-04-02","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28341,"PRC-004-5(I)","R6.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall implement each CAP developed in Requirement R5, and update each CAP if actions or timetables change, until completed. [Violation Risk Factor: High][Time Horizon: Operations Planning, Long‐Term Planning]","2017-04-02","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[30195,"PRC-004-6","R.1.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that owns a\r\nBES interrupting device that operated under the circumstances in Parts 1.1 through\r\n1.3 shall, within 120 calendar days of the BES interrupting device operation, identify\r\nwhether its Protection System component(s) caused a Misoperation: [Violation Risk\r\nFactor: High][Time Horizon: Operations Assessment, Operations Planning]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","DP, GO, TO","Yes",false,null,false]
[30196,"PRC-004-6","R1.1.",null,"The BES interrupting device operation was caused by a Protection System or by manual intervention in response to a Protection System failure to operate; and","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","DP, GO, TO","Yes",false,null,false]
[30197,"PRC-004-6","R1.2.",null,"The BES interrupting device owner owns all or part of the Composite Protection System; and","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","DP, TO, GO","Yes",false,null,false]
[30198,"PRC-004-6","R1.3.",null,"The BES interrupting device owner identified that its Protection System component(s) caused the BES interrupting device(s) operation or was caused by manual intervention in response to its Protection System failure to operate.","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","DP, TO, GO","Yes",false,null,false]
[30199,"PRC-004-6","R2.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that owns a BES interrupting device that operated shall, within 120 calendar days of the BES interrupting device operation, provide notification as described in Parts 2.1 and 2.2. [Violation Risk Factor: High][Time Horizon: Operations Assessment, Operations Planning]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","DP, TO, GO","Yes",false,null,false]
[30200,"PRC-004-6","R2.1.",null,"For a BES interrupting device operation by a Composite Protection System or by manual intervention in response to a Protection System failure to operate, notification of the operation shall be provided to the other owner(s) that share Misoperation identification responsibility for the Composite Protection System under the following circumstances:","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","DP, TO, GO","Yes",false,null,false]
[30201,"PRC-004-6","R2.1.1.",null,"The BES interrupting device owner shares the Composite Protection System ownership with any other owner; and","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","DP, TO, GO","Yes",false,null,false]
[30202,"PRC-004-6","R2.1.2.",null,"The BES interrupting device owner has determined that a Misoperation occurred or cannot rule out a Misoperation; and","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","DP, TO, GO","Yes",false,null,false]
[30203,"PRC-004-6","R2.1.3.",null,"The BES interrupting device owner has determined that its Protection System component(s) did not cause the BES interrupting device(s) operation or cannot determine whether its Protection System components caused the BES interrupting device(s) operation.","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","DP, TO, GO","Yes",false,null,false]
[30204,"PRC-004-6","R2.2.",null,"For a BES interrupting device operation by a Protection System component intended to operate as backup protection for a condition on another entity’s BES Element, notification of the operation shall be provided to the other Protection System owner(s) for which that backup protection was provided.","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","DP, TO, GO","Yes",false,null,false]
[30205,"PRC-004-6","R3.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that receives notification, pursuant to Requirement R2 shall, within the later of 60 calendar days of notification or 120 calendar days of the BES interrupting device(s) operation, identify whether its Protection System component(s) caused a Misoperation. [Violation Risk Factor: High][Time Horizon: Operations Assessment, Operations Planning]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","DP, TO, GO","Yes",false,null,false]
[30206,"PRC-004-6","R4.",null,"Reserved","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","DP, TO, GO","Yes",false,null,false]
[30207,"PRC-004-6","R5.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that owns the Protection System component(s) that caused the Misoperation shall, within 60 calendar days of first identifying a cause of the Misoperation: [Violation Risk Factor: High] [Time Horizon: Operations Planning, Long‐Term Planning] \n\n● Develop a Corrective Action Plan (CAP) for the identified Protection System component(s), and an evaluation of the CAP’s applicability to the entity’s other Protection Systems including other locations; or \n\n● Explain in a declaration why corrective actions are beyond the entity’s control or would not improve BES reliability, and that no further corrective actions will be taken.","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","DP, TO, GO","Yes",false,null,false]
[30208,"PRC-004-6","R6.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall implement each CAP developed in Requirement R5, and update each CAP if actions or timetables change, until completed. [Violation Risk Factor: High][Time Horizon: Operations Planning, Long‐Term Planning]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","DP, TO, GO","Yes",false,null,false]
[28342,"PRC-005-1.1b","R1.",null,"Each Transmission Owner and any Distribution Provider that owns a transmission Protection System and each Generator Owner that owns a generation or generator interconnection Facility 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:","2013-11-25","2027-03-31","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28343,"PRC-005-1.1b","R1.1.",null,"Maintenance and testing intervals and their basis.","2013-11-25","2027-03-31","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28344,"PRC-005-1.1b","R1.2.",null,"Summary of maintenance and testing procedures.","2013-11-25","2027-03-31","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28345,"PRC-005-1.1b","R2.",null,"Each Transmission Owner and any Distribution Provider that owns a transmission Protection System and each Generator Owner that owns a generation or generator interconnection Facility Protection System shall provide documentation of its Protection System maintenance and testing program and the implementation of that program to its Regional Entity on request (within 30 calendar days). The documentation of the program implementation shall include:","2013-11-25","2027-03-31","Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28346,"PRC-005-1.1b","R2.1.",null,"Evidence Protection System devices were maintained and tested within the defined intervals","2013-11-25","2027-03-31","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28347,"PRC-005-1.1b","R2.2.",null,"Date each Protection System device was last tested/maintained.","2013-11-25","2027-03-31","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28362,"PRC-005-2(ii)","R1.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall establish a Protection System Maintenance Program (PSMP) for its Protection Systems identified in Section 4.2. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]\nThe PSMP shall:",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28363,"PRC-005-2(ii)","R1.1.",null,"Identify which maintenance method (time-based, performance-based per PRC-005 Attachment A, or a combination) is used to address each Protection System Component Type. All batteries associated with the station dc supply Component Type of a Protection System shall be included in a time-based program as described in Table 1-4 and Table 3.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28364,"PRC-005-2(ii)","R1.2.",null,"Include the applicable monitored Component attributes applied to each Protection System Component Type consistent with the maintenance intervals specified in Tables 1-1 through 1-5, Table 2, and Table 3 where monitoring is used to extend the maintenance intervals beyond those specified for unmonitored Protection System Components",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28365,"PRC-005-2(ii)","R2.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that uses performance-based maintenance intervals in its\nPSMP shall follow the procedure established in PRC-005 Attachment A to establish and maintain its performance-based intervals.\n[Violation Risk Factor: Medium] [Time Horizon: Operations Planning]",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28366,"PRC-005-2(ii)","R3.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that utilizes timebased maintenance program(s) shall maintain its Protection System Components that are included within the time-based maintenance program in accordance with the minimum maintenance activities and maximum maintenance intervals prescribed within Tables 1-1 through 1-5, Table 2, and Table 3. [Violation Risk Factor: High] [Time Horizon: Operations Planning]",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28367,"PRC-005-2(ii)","R4.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that utilizes performance-based maintenance program(s) in accordance with Requirement R2 shall implement and follow its PSMP for its Protection System Components that are included within the performance-based program(s). [Violation Risk Factor: High] [Time Horizon: Operations Planning]",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28368,"PRC-005-2(ii)","R5.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall demonstrate efforts to correct identified Unresolved Maintenance Issues. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28369,"PRC-005-3","R1.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall establish a\nProtection System Maintenance Program (PSMP) for its Protection Systems and Automatic\nReclosing identified in Facilities Section 4.2. [Violation Risk Factor: Medium] [Time\nHorizon: Operations Planning]","2024-04-01",null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28370,"PRC-005-3","R1.1.",null,"The PSMP shall:\nIdentify which maintenance method (time-based, performance-based per PRC-005 Attachment A, or a combination) is used to address each Protection System and Automatic Reclosing Component Type. All batteries associated with the station dc\nsupply Component Type of a Protection System shall be included in a time-based program as described in Table 1-4 and Table 3.","2024-04-01",null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28371,"PRC-005-3","R1.2.",null,"Include the applicable monitored Component attributes applied to each Protection System and Automatic Reclosing Component Type consistent with the maintenance intervals specified in Tables 1-1 through 1-5, Table 2, Table 3, and Table 4-1 through 4-2 where\nmonitoring is used to extend the maintenance intervals beyond those specified for unmonitored Protection System and Automatic Reclosing Components.","2024-04-01",null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28372,"PRC-005-3","R2.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that uses performancebased maintenance intervals in its PSMP shall follow the procedure established in PRC-005 Attachment A to establish and maintain its performance-based intervals. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2024-04-01",null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28373,"PRC-005-3","R3.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that utilizes timebased maintenance program(s) shall maintain its Protection System and Automatic Reclosing Components that are included within the time-based maintenance program in accordance with the minimum maintenance activities and maximum maintenance intervals prescribed within Tables 1-1 through 1-5, Table 2, Table 3, and Table 4-1 through 4-2. [Violation Risk Factor: High] [Time Horizon: Operations Planning]","2024-04-01",null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28374,"PRC-005-3","R4.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that utilizes performance-based maintenance program(s) in accordance with Requirement R2 shall implement and follow its PSMP for its Protection System and Automatic Reclosing\nComponents that are included within the performance-based program(s). [Violation Risk Factor: High] [Time Horizon: Operations Planning]","2024-04-01",null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28375,"PRC-005-3","R5.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall demonstrate efforts to correct identified Unresolved Maintenance Issues. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2024-04-01",null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28376,"PRC-005-3(i)","R1.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall establish a Protection System Maintenance Program (PSMP) for its Protection Systems and Automatic Reclosing identified in Facilities Section 4.2. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]\nThe PSMP shall:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28377,"PRC-005-3(i)","R1.1.",null,"Identify which maintenance method (time-based, performance-based per PRC-005 Attachment A, or a combination) is used to address each Protection System and Automatic Reclosing Component Type. All batteries associated with the station dc supply Component Type of a Protection System shall be included in a time-based program as described in Table 1-4 and Table 3.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28378,"PRC-005-3(i)","R1.2.",null,"Include the applicable monitored Component attributes applied to each Protection System and Automatic Reclosing Component Type consistent with the maintenance intervals specified in Tables 1-1 through 1-5, Table 2, Table 3, and Table 4-1 through 4-2 where monitoring is used to extend the maintenance intervals beyond those specified for unmonitored Protection System and Automatic Reclosing Components.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28379,"PRC-005-3(i)","R2.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that uses performance-based maintenance intervals in its PSMP shall follow the procedure established in PRC-005 Attachment A to establish and maintain its performance-based intervals. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28380,"PRC-005-3(i)","R3.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that utilizes time-based maintenance program(s) shall maintain its Protection System and Automatic Reclosing Components that are included within the time-based maintenance program in accordance with the minimum maintenance activities and maximum maintenance intervals prescribed within Tables 1-1 through 1-5, Table 2, Table 3, and Table 4-1 through 4-2. [Violation Risk Factor: High] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28381,"PRC-005-3(i)","R4.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that utilizes performance-based maintenance program(s) in accordance with Requirement R2 shall implement and follow its PSMP for its Protection System and Automatic Reclosing Components that are included within the performance-based program(s). [Violation Risk Factor: High] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28382,"PRC-005-3(i)","R5.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall demonstrate efforts to correct identified Unresolved Maintenance Issues. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28383,"PRC-005-3(ii)","R1.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall establish a\nProtection System Maintenance Program (PSMP) for its Protection Systems and Automatic\nReclosing identified in Facilities Section 4.2. [Violation Risk Factor: Medium] [Time\nHorizon: Operations Planning]",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28384,"PRC-005-3(ii)","R1.1.",null,"The PSMP shall:\nIdentify which maintenance method (time-based, performance-based per PRC-005 Attachment A, or a combination) is used to address each Protection System and Automatic Reclosing Component Type. All batteries associated with the station dc\nsupply Component Type of a Protection System shall be included in a time-based program as described in Table 1-4 and Table 3.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28385,"PRC-005-3(ii)","R1.2.",null,"Include the applicable monitored Component attributes applied to each Protection System and Automatic Reclosing Component Type consistent with the maintenance intervals specified in Tables 1-1 through 1-5, Table 2, Table 3, and Table 4-1 through 4-2 where monitoring is used to extend the maintenance intervals beyond those specified for unmonitored Protection System and Automatic Reclosing Components.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28386,"PRC-005-3(ii)","R2.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that uses performancebased maintenance intervals in its PSMP shall follow the procedure established in PRC-005 Attachment A to establish and maintain its performance-based intervals. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28387,"PRC-005-3(ii)","R3.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that utilizes timebased maintenance program(s) shall maintain its Protection System and Automatic Reclosing Components that are included within the time-based maintenance program in accordance with the minimum maintenance activities and maximum maintenance intervals prescribed within Tables 1-1 through 1-5, Table 2, Table 3, and Table 4-1 through 4-2. [Violation Risk Factor: High] [Time Horizon: Operations Planning]",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28388,"PRC-005-3(ii)","R4.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that utilizes performance-based maintenance program(s) in accordance with Requirement R2 shall implement and follow its PSMP for its Protection System and Automatic Reclosing\nComponents that are included within the performance-based program(s). [Violation Risk Factor: High] [Time Horizon: Operations Planning]",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28389,"PRC-005-3(ii)","R5.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall demonstrate efforts to correct identified Unresolved Maintenance Issues. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28390,"PRC-005-4","R1.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall establish a Protection System Maintenance Program (PSMP) for its Protection Systems, Automatic Reclosing, and Sudden Pressure Relaying identified in Section 4.2, Facilities. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]\nThe PSMP shall:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28391,"PRC-005-4","R1.1.",null,"Identify which maintenance method (time-based, performance-based per PRC-005 Attachment A, or a combination) is used to address each Protection System, Automatic Reclosing, and Sudden Pressure Relaying Component Type. All batteries associated with the station dc supply Component Type of a Protection System shall be included in a time-based program as described in Table 1-4 and Table 3.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28392,"PRC-005-4","R1.2.",null,"Include the applicable monitored Component attributes applied to each Protection System, Automatic Reclosing, and Sudden Pressure Relaying Component Type consistent with the maintenance intervals specified in Tables 1-1 through 1-5, Table 2, Table 3, Table 4-1 through 4-2, and Table 5 where monitoring is used to extend the maintenance intervals beyond those specified for unmonitored Protection System, Automatic Reclosing, and Sudden Pressure Relaying Components.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28393,"PRC-005-4","R2.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that uses performance-based maintenance intervals in its PSMP shall follow the procedure established in PRC-005 Attachment A to establish and maintain its performance-based intervals. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28394,"PRC-005-4","R3.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that utilizes time-based maintenance program(s) shall maintain its Protection System, Automatic Reclosing, and Sudden Pressure Relaying Components that are included within the time-based maintenance program in accordance with the minimum maintenance activities and maximum maintenance intervals prescribed within Tables 1-1 through 1-5, Table 2, Table 3, Table 4-1 through 4-2, and Table 5. [Violation Risk Factor: High] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28395,"PRC-005-4","R4.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that utilizes performance-based maintenance program(s) in accordance with Requirement R2 shall implement and follow its PSMP for its Protection System, Automatic Reclosing, and Sudden Pressure Relaying Components that are included within the performance-based program(s). [Violation Risk Factor: High] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28396,"PRC-005-4","R5.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall demonstrate efforts to correct identified Unresolved Maintenance Issues. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28397,"PRC-005-5","R1.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall establish a Protection System Maintenance Program (PSMP) for its Protection Systems, Automatic Reclosing, and Sudden Pressure Relaying identified in Section 4.2, Facilities. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]\n\nThe PSMP shall:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28398,"PRC-005-5","R1.1.",null,"Identify which maintenance method (time‐based, performance‐based per PRC‐005 Attachment A, or a combination) is used to address each Protection System, Automatic Reclosing, and Sudden Pressure Relaying Component Type. All batteries associated with the station dc supply Component Type of a Protection System shall be included in a time‐based program as described in Table 1‐4 and Table 3.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28399,"PRC-005-5","R1.2.",null,"Include the applicable monitored Component attributes applied to each Protection System, Automatic Reclosing, and Sudden Pressure Relaying Component Type consistent with the maintenance intervals specified in Tables 1‐1 through 1‐5, Table 2, Table 3, Table 4‐1 through 4‐2, and Table 5 where monitoring is used to extend the maintenance intervals beyond those specified for unmonitored Protection System, Automatic Reclosing, and Sudden Pressure Relaying Components.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28400,"PRC-005-5","R2.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that uses performance‐based maintenance intervals in its PSMP shall follow the procedure established in PRC‐005 Attachment A to establish and maintain its performance‐based intervals. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28401,"PRC-005-5","R3.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that utilizes time‐based maintenance program(s) shall maintain its Protection System, Automatic Reclosing, and Sudden Pressure Relaying Components that are included within the time‐based maintenance program in accordance with the minimum maintenance activities and maximum maintenance intervals prescribed within Tables 1‐1 through 1‐5, Table 2, Table 3, Table 4‐1 through 4‐2, and Table 5. [Violation Risk Factor: High] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28402,"PRC-005-5","R4.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that utilizes performance‐based maintenance program(s) in accordance with Requirement R2 shall implement and follow its PSMP for its Protection System, Automatic Reclosing, and Sudden Pressure Relaying Components that are included within the performancebased program(s). [Violation Risk Factor: High] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28403,"PRC-005-5","R5.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall demonstrate efforts to correct identified Unresolved Maintenance Issues. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28404,"PRC-005-6","R1.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall establish a Protection System Maintenance Program (PSMP) for its Protection Systems, Automatic Reclosing, and Sudden Pressure Relaying identified in Section 4.2, Facilities. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]\n\nThe PSMP shall:","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28405,"PRC-005-6","R1.1.",null,"Identify which maintenance method (time‐based, performance‐based per PRC‐005 Attachment A, or a combination) is used to address each Protection System, Automatic Reclosing, and Sudden Pressure Relaying Component Type. All batteries associated with the station dc supply Component Type of a Protection System shall be included in a time‐based program as described in Table 1‐4 and Table 3.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28406,"PRC-005-6","R1.2.",null,"Include the applicable monitored Component attributes applied to each Protection System, Automatic Reclosing, and Sudden Pressure Relaying Component Type consistent with the maintenance intervals specified in Tables 1‐1 through 1‐5, Table 2, Table 3, Table 4‐1 through 4‐3, and Table 5 where monitoring is used to extend the maintenance intervals beyond those specified for unmonitored Protection System, Automatic Reclosing, and Sudden Pressure Relaying Components.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28407,"PRC-005-6","R2.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that uses performance‐based maintenance intervals in its PSMP shall follow the procedure established in PRC‐005 Attachment A to establish and maintain its performance‐based intervals. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28408,"PRC-005-6","R3.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that utilizes time‐based maintenance program(s) shall maintain its Protection System, Automatic Reclosing, and Sudden Pressure Relaying Components that are included within the time‐based maintenance program in accordance with the minimum maintenance activities and maximum maintenance intervals prescribed within Tables 1‐1 through 1‐5, Table 2, Table 3, Table 4‐1 through 4‐3, and Table 5. [Violation Risk Factor: High] [Time Horizon: Operations Planning]","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28409,"PRC-005-6","R4.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that utilizes performance‐based maintenance program(s) in accordance with Requirement R2 shall implement and follow its PSMP for its Protection System, Automatic Reclosing, and Sudden Pressure Relaying Components that are included within the performancebased program(s). [Violation Risk Factor: High] [Time Horizon: Operations Planning]","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28410,"PRC-005-6","R5.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall demonstrate efforts to correct identified Unresolved Maintenance Issues. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28447,"PRC-006-1(i)","R1.",null,"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.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[28473,"PRC-006-1(i)","R10.",null,"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 application determined by the Planning Coordinator(s) in each Planning Coordinator area in which the Transmission Owner owns transmission.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[28474,"PRC-006-1(i)","R11.",null,"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:",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC","No",false,null,false]
[28475,"PRC-006-1(i)","R11.1.",null,"The performance of the UFLS equipment,",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC","No",false,null,false]
[28476,"PRC-006-1(i)","R11.2.",null,"The effectiveness of the UFLS program.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC","No",false,null,false]
[28477,"PRC-006-1(i)","R12.",null,"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.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC","No",false,null,false]
[28478,"PRC-006-1(i)","R13.",null,"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]\n• 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\n• 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\n• 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.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC","No",false,null,false]
[28479,"PRC-006-1(i)","R14.",null,"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",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","PC","No",false,null,false]
[28480,"PRC-006-1(i)","R14.1.",null,"UFLS program, including a schedule for implementation",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","PC","No",false,null,false]
[28481,"PRC-006-1(i)","R14.2.",null,"UFLS design assessment",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","PC","No",false,null,false]
[28482,"PRC-006-1(i)","R14.3.",null,"Format and schedule of UFLS data submittal",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","PC","No",false,null,false]
[28448,"PRC-006-1(i)","R2.",null,"Each Planning Coordinator shall identify one or more islands to serve as a basis for designing its UFLS program including:",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[28449,"PRC-006-1(i)","R2.1.",null,"Those islands selected by applying the criteria in Requirement R1, and",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[28450,"PRC-006-1(i)","R2.2.",null,"Any portions of the BES designed to detach from the Interconnection (planned islands) as a result of the operation of a relay scheme or Remedial Action Scheme, and",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[28451,"PRC-006-1(i)","R2.3.",null,"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.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[28453,"PRC-006-1(i)","R3.","YES","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).",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC","No",false,null,false]
[28452,"PRC-006-1(i)","R3.","YES","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).",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[28454,"PRC-006-1(i)","R3.1.",null,"Frequency shall remain above the Underfrequency Performance Characteristic curve in PRC-006-1(i) - Attachment 1, either for 60 seconds or until a steady-state condition between 59.3 Hz and 60.7 Hz is reached, and",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC","No",false,null,false]
[28455,"PRC-006-1(i)","R3.2.",null,"Frequency shall remain below the Overfrequency Performance Characteristic curve in PRC-006-1(i) - Attachment 1, either for 60 seconds or until a steady-state condition between 59.3 Hz and 60.7 Hz is reached, and",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC","No",false,null,false]
[28456,"PRC-006-1(i)","R3.3.",null,"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:",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC","No",false,null,false]
[28457,"PRC-006-1(i)","R3.3.1.",null,"Individual generating units greater than 20 MVA (gross nameplate rating) directly connected to the BES",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC","No",false,null,false]
[28458,"PRC-006-1(i)","R3.3.2.",null,"Generating plants/facilities greater than 75 MVA (gross aggregate nameplate rating) directly connected to the BES",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC","No",false,null,false]
[28459,"PRC-006-1(i)","R3.3.3.",null,"Facilities consisting of one or more units connected to the BES at a common bus with total generation above 75 MVA gross nameplate rating.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC","No",false,null,false]
[28460,"PRC-006-1(i)","R4.",null,"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:",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[28461,"PRC-006-1(i)","R4.1.",null,"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-1(i) - Attachment 1.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[28462,"PRC-006-1(i)","R4.2.",null,"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-1(i) - Attachment 1.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[28463,"PRC-006-1(i)","R4.3.",null,"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-1(i) - Attachment 1.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[28464,"PRC-006-1(i)","R4.4.",null,"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-1(i) — Attachment 1.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[28465,"PRC-006-1(i)","R4.5.",null,"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-1(i) — Attachment 1.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[28466,"PRC-006-1(i)","R4.6.",null,"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-1(i) — Attachment 1.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[28467,"PRC-006-1(i)","R4.7.",null,"Any automatic Load restoration that impacts frequency stabilization and operates within the duration of the simulations run for the assessment.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[28468,"PRC-006-1(i)","R5.",null,"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:\n• 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\n• 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\n• 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.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[28469,"PRC-006-1(i)","R6.",null,"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.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","PC","No",false,null,false]
[28470,"PRC-006-1(i)","R7.",null,"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.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","PC","No",false,null,false]
[28471,"PRC-006-1(i)","R8.",null,"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.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28472,"PRC-006-1(i)","R9.",null,"Each UFLS entity shall provide automatic tripping of Load in accordance with the UFLS program design and schedule for application determined by its Planning Coordinator(s) in each Planning Coordinator area in which it owns assets.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28519,"PRC-006-3","R1.",null,"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.","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28542,"PRC-006-3","R10.",null,"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.","2017-10-01","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TO","Yes",false,null,false]
[28543,"PRC-006-3","R11.",null,"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:","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28544,"PRC-006-3","R11.1.",null,"The performance of the UFLS equipment,","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28545,"PRC-006-3","R11.2.",null,"The effectiveness of the UFLS program.","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28546,"PRC-006-3","R12.",null,"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.","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28547,"PRC-006-3","R13.",null,"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:\n• 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\n• 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\n• 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.","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28548,"PRC-006-3","R14.",null,"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","2017-10-01","2021-03-31","Retired","Communications; Documentations, Policies and Procedures","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28549,"PRC-006-3","R14.1.",null,"UFLS program, including a schedule for implementation","2017-10-01","2021-04-30","Retired","Communications; Documentations, Policies and Procedures","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28550,"PRC-006-3","R14.2.",null,"UFLS design assessment","2017-10-01","2021-04-30","Retired","Communications; Documentations, Policies and Procedures","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28551,"PRC-006-3","R14.3.",null,"Format and schedule of UFLS data submittal","2017-10-01","2021-04-30","Retired","Communications; Documentations, Policies and Procedures","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28552,"PRC-006-3","R15.",null,"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.","2017-10-01","2021-04-30","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28553,"PRC-006-3","R15.1.",null,"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.","2017-10-01","2021-04-30","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28554,"PRC-006-3","R15.2.",null,"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.","2017-10-01","2021-04-30","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28520,"PRC-006-3","R2.",null,"Each Planning Coordinator shall identify one or more islands to serve as a basis for designing its UFLS program including:","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28521,"PRC-006-3","R2.1.",null,"Those islands selected by applying the criteria in Requirement R1, and","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28522,"PRC-006-3","R2.2.",null,"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","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28523,"PRC-006-3","R2.3.",null,"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.","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28525,"PRC-006-3","R3.","YES","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)","2017-10-01","2021-03-31","Retired",null,"HIGH",null,"N/A","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28524,"PRC-006-3","R3.","YES","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)","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28526,"PRC-006-3","R3.1.",null,"Frequency shall remain above the Underfrequency Performance Characteristic curve in PRC-006-2 - Attachment 1, either for 60 seconds or until a steady-state condition between 59.3 Hz and 60.7 Hz is reached, and","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28527,"PRC-006-3","R3.2.",null,"Frequency shall remain below the Overfrequency Performance Characteristic curve in PRC-006-2 - Attachment 1, either for 60 seconds or until a steady-state condition between 59.3 Hz and 60.7 Hz is reached, and","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28528,"PRC-006-3","R3.3.",null,"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:\n• Individual generating units greater than 20 MVA (gross nameplate rating) directly connected to the BES \n• Generating plants/facilities greater than 75 MVA (gross aggregate nameplate rating) directly connected to the BES\n• Facilities consisting of one or more units connected to the BES at a common bus with total generation above 75 MVA gross nameplate rating.","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28529,"PRC-006-3","R4.",null,"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:","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28530,"PRC-006-3","R4.1.",null,"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-2 - Attachment 1.","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28531,"PRC-006-3","R4.2.",null,"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-2 - Attachment 1.","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28532,"PRC-006-3","R4.3.",null,"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-2 - Attachment 1.","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28533,"PRC-006-3","R4.4.",null,"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-2 — Attachment 1.","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28534,"PRC-006-3","R4.5.",null,"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-2 — Attachment 1.","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28535,"PRC-006-3","R4.6.",null,"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-2 — Attachment 1.","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28536,"PRC-006-3","R4.7.",null,"Any automatic Load restoration that impacts frequency stabilization and operates within the duration of the simulations run for the assessment","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28537,"PRC-006-3","R5.",null,"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:\n• 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\n• 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\n• 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.","2017-10-01","2021-03-31","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28538,"PRC-006-3","R6.","YES","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.","2017-10-01","2021-03-31","Retired","Communications; Documentations, Policies and Procedures","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[29822,"PRC-006-3","R6.","YES","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.","2017-10-01","2021-03-31","Retired","Communications; Documentations, Policies and Procedures","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28539,"PRC-006-3","R7.",null,"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.","2017-10-01","2021-03-31","Retired","Communications; Documentations, Policies and Procedures","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28540,"PRC-006-3","R8.",null,"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.","2017-10-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28541,"PRC-006-3","R9.",null,"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.","2017-10-01","2021-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[30013,"PRC-006-4","R1.",null,"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]","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30037,"PRC-006-4","R10.",null,"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]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","DP, TO, PC","Yes",false,null,false]
[30038,"PRC-006-4","R11.",null,"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]","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30039,"PRC-006-4","R11.1.",null,"The performance of the UFLS equipment,","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30040,"PRC-006-4","R11.2.",null,"The effectiveness of the UFLS program.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30041,"PRC-006-4","R12.",null,"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]","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30042,"PRC-006-4","R13.",null,"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]\r\n• 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\r\n• 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\r\n• 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.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30043,"PRC-006-4","R14.",null,"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]:","2021-04-01",null,"Effective","Communications; Documentations, Policies and Procedures","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30044,"PRC-006-4","R14.1.",null,"UFLS program, including a schedule for implementation","2021-04-01",null,"Effective","Communications; Documentations, Policies and Procedures","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30045,"PRC-006-4","R14.2.",null,"UFLS design assessment","2021-04-01",null,"Effective","Communications; Documentations, Policies and Procedures","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30046,"PRC-006-4","R14.3.",null,"Format and schedule of UFLS data submittal","2021-04-01",null,"Effective","Communications; Documentations, Policies and Procedures","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30047,"PRC-006-4","R15.",null,"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]","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30048,"PRC-006-4","R15.1.",null,"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.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30049,"PRC-006-4","R15.2.",null,"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.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30014,"PRC-006-4","R2.",null,"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]","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30015,"PRC-006-4","R2.1.",null,"Those islands selected by applying the criteria in Requirement R1, and","2021-04-01",null,"Effective","Authorization/Approval; Communications; DOCS; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30016,"PRC-006-4","R2.2.",null,"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","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30017,"PRC-006-4","R2.3.",null,"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.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30018,"PRC-006-4","R3.","YES","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]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30019,"PRC-006-4","R3.","YES","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]","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30020,"PRC-006-4","R3.1.",null,"Frequency shall remain above the Underfrequency Performance Characteristic curve in PRC-006-4 - Attachment 1, either for 60 seconds or until a steady-state condition between 59.3 Hz and 60.7 Hz is reached, and","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30021,"PRC-006-4","R3.2.",null,"Frequency shall remain below the Overfrequency Performance Characteristic curve in PRC-006-4 - Attachment 1, either for 60 seconds or until a steady-state condition between 59.3 Hz and 60.7 Hz is reached, and","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30022,"PRC-006-4","R3.3.",null,"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:\r\n• Individual generating units greater than 20 MVA (gross nameplate rating) directly connected to the BES\r\n• Generating plants/facilities greater than 75 MVA (gross aggregate nameplate rating) directly connected to the BES\r\n• Facilities consisting of one or more units connected to the BES at a common bus with total generation above 75 MVA gross nameplate rating.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30023,"PRC-006-4","R4.",null,"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]","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30024,"PRC-006-4","R4.1.",null,"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-4 - Attachment 1.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30025,"PRC-006-4","R4.2.",null,"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-4 - Attachment 1.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30026,"PRC-006-4","R4.3.",null,"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-4 - Attachment 1.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30027,"PRC-006-4","R4.4.",null,"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-4 — Attachment 1.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30028,"PRC-006-4","R4.5.",null,"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-4 — Attachment 1.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30029,"PRC-006-4","R4.6.",null,"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-4 — Attachment 1.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30030,"PRC-006-4","R4.7.",null,"Any automatic Load restoration that impacts frequency stabilization and operates within the duration of the simulations run for the assessment.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30031,"PRC-006-4","R5.",null,"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]\r\n• 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\r\n• 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\r\n• 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.","2021-04-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30033,"PRC-006-4","R6.","YES","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]","2021-04-01",null,"Effective","Communications; Documentations, Policies and Procedures","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30032,"PRC-006-4","R6.","YES","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]","2021-04-01",null,"Effective","Communications; Documentations, Policies and Procedures","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30034,"PRC-006-4","R7.",null,"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]","2021-04-01",null,"Effective","Communications; Documentations, Policies and Procedures","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","DP, TO, PC","Yes",false,null,false]
[30035,"PRC-006-4","R8.",null,"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]","2021-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","DP, TO, PC","Yes",false,null,false]
[30036,"PRC-006-4","R9.",null,"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]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","DP, TO, PC","Yes",false,null,false]
[28555,"PRC-006-NPCC-1","R1.",null,"Each Planning Coordinator shall establish requirements for entities aggregating their UFLS programs for each anticipated island and requirements for compensatory load shedding based on islanding criteria (required by the NERC PRC Standard on UFLS). [Violation Risk Factor: Medium] [Time Horizon: Long Term Planning]","2017-04-01","2020-06-30","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28571,"PRC-006-NPCC-1","R10.",null,"Each Distribution Provider and Transmission Owner shall implement the inhibit threshold settings based on the notification provided by the Planning Coordinator in accordance with Requirement R9. [Violation Risk Factor: High] [Time Horizon: Operations Planning]","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28572,"PRC-006-NPCC-1","R11.",null,"Each Distribution Provider and Transmission Owner shall develop and submit an implementation plan within 90 days of the request from the Planning Coordinator for approval by the Planning Coordinator in accordance with R9. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2017-04-01","2020-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","DP","Yes",false,null,false]
[28573,"PRC-006-NPCC-1","R12.",null,"Each Transmission Owner and Distribution Provider shall annually provide documentation, with no more than 15 months between updates, to its Planning Coordinator of the actual net Load that would have been shed by the UFLS relays at each UFLS stage coincident with their integrated hourly peak net Load during the previous year, as determined by measuring actual metered Load through the switches that would be opened by the UFLS relays. [Violation Risk Factor: Lower] [Time Horizon: Long Term Planning]","2017-04-01","2020-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28574,"PRC-006-NPCC-1","R13.",null,"Each Generator Owner shall set each generator underfrequency trip relay, if so equipped, below the appropriate generator underfrequency trip protection settings threshold curve in Figure 1, except as otherwise exempted in Requirements R16 and R19. [Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28575,"PRC-006-NPCC-1","R14.",null,"Each Generator Owner shall transmit the generator underfrequency trip setting and time delay to its Planning Coordinator within 45 days of the Planning Coordinator’s request. [Violation Risk Factor: High] [Time Horizon: Operations Planning]","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28576,"PRC-006-NPCC-1","R15.",null,"Each Generator Owner with a new generating unit, scheduled to be in service on or after the effective date of this Standard, or an existing generator increasing its net capability by greater than 10% shall: [Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28577,"PRC-006-NPCC-1","R15.1.",null,"Design measures to prevent the generating unit from tripping directly or indirectly for underfrequency conditions above the appropriate generator tripping threshold curve in Figure 1.","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28578,"PRC-006-NPCC-1","R15.2.",null,"Design auxiliary system(s) or devices used for the control and protection of auxiliary system(s), necessary for the generating unit operation such that they will not trip the generating unit during underfrequency conditions above the appropriate generator underfrequency trip protection settings threshold curve in Figure 1.","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28579,"PRC-006-NPCC-1","R16.",null,"Each Generator Owner of existing non-nuclear units in service prior to the effective date of this standard that have underfrequency protections set to trip above the appropriate curve in Figure 1 shall: [Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28580,"PRC-006-NPCC-1","R16.1.",null,"Set the underfrequency protection to operate at the lowest frequency allowed by the plant design and licensing limitations.","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28581,"PRC-006-NPCC-1","R16.2.",null,"Transmit the existing underfrequency settings and any changes to the underfrequency settings along with the technical basis for the settings to the Planning Coordinator.","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28582,"PRC-006-NPCC-1","R16.3.",null,"Have compensatory load shedding, as provided by a Distribution Provider or Transmission Owner that is adequate to compensate for the loss of their generator due to early tripping.","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28583,"PRC-006-NPCC-1","R17.",null,"Each Planning Coordinator in Ontario, Quebec and the Maritime provinces shall apply the criteria described in Attachment A to determine the compensatory load shedding that is required in Requirement R16.3 for generating units in its respective NPCC area. [Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2017-04-01","2020-06-30","Retired","Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification","HIGH","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[27922,"PRC-006-NPCC-1","R18.",null,"Each Generator Owner, Distribution Provider or Transmission Owner within the Planning Coordinator area of ISO-NE or the New York ISO shall apply the criteria described in Attachment B to determine the compensatory load shedding that is required in Requirement R16.3 for generating units in its respective NPCC area. [Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[27923,"PRC-006-NPCC-1","R19.",null,"Each Generator Owner of existing nuclear generating plants with units that have underfrequency relay threshold settings above the Eastern Interconnection generator tripping curve in Figure 1, based on their licensing design basis, shall: [Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27924,"PRC-006-NPCC-1","R19.1.",null,"Set the underfrequency protection to operate at as low a frequency as possible in accordance with the plant design and licensing limitations but not greater than 57.8Hz.","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27925,"PRC-006-NPCC-1","R19.2.",null,"Set the frequency trip setting upper tolerance to no greater than + 0.1 Hz.","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[27926,"PRC-006-NPCC-1","R19.3.",null,"Transmit the initial frequency trip setting and any changes to the setting and the technical basis for the settings to the Planning Coordinator.","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28556,"PRC-006-NPCC-1","R2.",null,"Each Planning Coordinator shall, within 30 days of completion of its system studies required by the NERC PRC Standard on UFLS, identify to the Regional Entity the generation facilities within its Planning Coordinator Area necessary to support the UFLS program performance characteristics. [Violation Risk Factor: Medium] [Time Horizon: Long Term Planning]","2017-04-01","2020-06-30","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[27927,"PRC-006-NPCC-1","R20.","YES","The Planning Coordinator shall update its UFLS program database as specified by the NERC PRC Standard on UFLS. This database shall include the following information: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective","Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[29823,"PRC-006-NPCC-1","R20.","YES","The Planning Coordinator shall update its UFLS program database as specified by the NERC PRC Standard on UFLS. This database shall include the following information: [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[27928,"PRC-006-NPCC-1","R20.1.","YES","For each UFLS relay, including those used for compensatory load shedding, the amount and location of load shed at peak, the corresponding frequency threshold and time delay settings.","2017-04-01",null,"Effective","Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[29824,"PRC-006-NPCC-1","R20.1.","YES","For each UFLS relay, including those used for compensatory load shedding, the amount and location of load shed at peak, the corresponding frequency threshold and time delay settings.","2017-04-01",null,"Effective",null,"LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[27929,"PRC-006-NPCC-1","R20.2.","YES","The buses at which the Load is modeled in the NPCC library power flow case.","2017-04-01",null,"Effective","Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[29825,"PRC-006-NPCC-1","R20.2.","YES","The buses at which the Load is modeled in the NPCC library power flow case.","2017-04-01",null,"Effective",null,"LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[27930,"PRC-006-NPCC-1","R20.3.","YES","A list of all generating units that may be tripped for underfrequency conditions above the appropriate generator underfrequency trip protection settings threshold curve in Figure 1, including the frequency trip threshold and time delay for each protection system.","2017-04-01",null,"Effective","Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[29826,"PRC-006-NPCC-1","R20.3.","YES","A list of all generating units that may be tripped for underfrequency conditions above the appropriate generator underfrequency trip protection settings threshold curve in Figure 1, including the frequency trip threshold and time delay for each protection system.","2017-04-01",null,"Effective",null,"LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[27931,"PRC-006-NPCC-1","R20.4.","YES","The location and amount of additional elements to be switched for voltage control that are coordinated with UFLS program tripping.","2017-04-01",null,"Effective","Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[29827,"PRC-006-NPCC-1","R20.4.","YES","The location and amount of additional elements to be switched for voltage control that are coordinated with UFLS program tripping.","2017-04-01",null,"Effective",null,"LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[27932,"PRC-006-NPCC-1","R20.5.","YES","A list of all UFLS relay inhibit functions along with the corresponding settings and locations of these relays.","2017-04-01",null,"Effective","Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification","LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[29828,"PRC-006-NPCC-1","R20.5.","YES","A list of all UFLS relay inhibit functions along with the corresponding settings and locations of these relays.","2017-04-01",null,"Effective",null,"LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28584,"PRC-006-NPCC-1","R21.",null,"Each Planning Coordinator shall notify each Distribution Provider, Transmission Owner, and Generator Owner within its Planning Coordinator area of changes to load distribution needed to satisfy UFLS program performance characteristics as specified by the NERC PRC Standard on UFLS.[Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2017-04-01","2020-06-30","Retired","Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification","HIGH","SOMEWHAT LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28585,"PRC-006-NPCC-1","R22.",null,"Each Distribution Provider, Transmission Owner and Generator Owner shall implement the load distribution changes based on the notification provided by the Planning Coordinator in accordance with Requirement R21. [Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28586,"PRC-006-NPCC-1","R23.",null,"Each Distribution Provider, Transmission Owner and Generator Owner shall develop and submit an implementation plan within 90 days of the request from the Planning Coordinator for approval by the Planning Coordinator in accordance with Requirement R21. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2017-04-01","2020-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28557,"PRC-006-NPCC-1","R3.",null,"Each Planning Coordinator shall provide to the Transmission Owner, Distribution Provider, and Generator Owner within 30 days upon written request the requirements for entities aggregating the UFLS programs and requirements for compensatory load shedding program derived from each Planning Coordinator’s system studies as determined by Requirement R1. [Violation Risk Factor: Low] [Time Horizon: Long Term Planning]","2017-04-01","2020-06-30","Retired","Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification","LOWER","SOMEWHAT LIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28558,"PRC-006-NPCC-1","R4.",null,"Each Distribution Provider and Transmission Owner in the Eastern Interconnection portion of NPCC shall implement an automatic UFLS program reflecting normal operating conditions excluding outages for its Facilities based on frequency thresholds, total nominal operating time and amounts specified in Attachment C, Tables 1 through 3, or shall collectively implement by mutual agreement with one or more Distribution Providers and Transmission Owners within the same island identified in Requirement R1 and acting as a single entity, provide an aggregated automatic UFLS program that sheds their coincident peak aggregated net Load, based on frequency thresholds, total nominal operating time and amounts specified in Attachment C, Tables 1 through 3. [Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28559,"PRC-006-NPCC-1","R5.",null,"Each Distribution Provider or Transmission Owner that must arm its load to trip on underfrequency in order to meet its requirements as specified and by doing so exceeds the tolerances and/or deviates from the number of stages and frequency set points of the UFLS program as specified in the tables contained in Requirement R4 above, as applicable depending on its total peak net Load shall: [Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28560,"PRC-006-NPCC-1","R5.1.",null,"Inform its Planning Coordinator of the need to exceed the stated tolerances or the number of stages as shown in UFLS Attachment C, Table 1 if applicable and","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28561,"PRC-006-NPCC-1","R5.2.",null,"Provide its Planning Coordinator with a technical study that demonstrates that the Distribution Providers or Transmission Owners specific deviations from the requirements of UFLS Attachment C, Table 1 will not have a significant adverse impact on the bulk power system.","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28562,"PRC-006-NPCC-1","R5.3.",null,"Inform its Planning Coordinator of the need to exceed the stated tolerances of UFLS Attachment C, Table 2 or Table 3, and in the case of Attachment C, Table 2 only, the need to deviate from providing two stages of UFLS, if applicable, and","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28563,"PRC-006-NPCC-1","R5.4.",null,"Provide its Planning Coordinator with an analysis demonstrating that no alternative load shedding solution is available that would allow the Distribution Provider or Transmission Owner to comply with UFLS Attachment C Table 2 or Attachment C Table 3.","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28564,"PRC-006-NPCC-1","R6.",null,"Each Distribution Provider and Transmission Owner in the Québec Interconnection portion of NPCC shall implement an automatic UFLS program for its Facilities based on the frequency thresholds, slopes, total nominal operating time and amounts specified in Attachment C, Table 4 or shall collectively implement by mutual agreement with one or more Distribution Providers and Transmission Owners within the same island, identified in Requirement R1, an aggregated automatic UFLS program that sheds Load based on the frequency thresholds, slopes, total nominal operating time and amounts specified in Attachment C, Table 4. [Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28565,"PRC-006-NPCC-1","R7.",null,"Each Distribution Provider and Transmission Owner shall set each underfrequency relay that is part of its region’s UFLS program with the following minimum time delay:","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28566,"PRC-006-NPCC-1","R7.1.",null,"Eastern Interconnection – 100 ms","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28567,"PRC-006-NPCC-1","R7.2.",null,"Québec Interconnection – 200 ms           [Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2017-04-01","2020-06-30","Retired",null,"HIGH",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28568,"PRC-006-NPCC-1","R8.",null,"Each Planning Coordinator shall develop and review once per calendar year settings for inhibit thresholds (such as but not limited to voltage, current and time) to be utilized within its region's UFLS program. [Violation Risk Factor: Medium] [Time Horizon: Long Term Planning]","2017-04-01","2020-06-30","Retired","Authorization/Approval; Communications; Documentations, Policies and Procedures; Segregation of Duties; Tools and Applications; Training","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[28570,"PRC-006-NPCC-1","R9.",null,"Each Planning Coordinator shall provide each Transmission Owner and Distribution Provider within its Planning Coordinator area the applicable inhibit thresholds within 30 days of the initial determination of those inhibit thresholds and within 30 days of any changes to those thresholds. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01","2020-06-30","Retired","Communications; Documentations, Policies and Procedures; Monitoring; Physical and Data Security; Quality Check/Verification","MEDIUM","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC","No",false,null,false]
[30138,"PRC-006-NPCC-2","R1.",null,"Each Planning Coordinator in the Eastern Interconnection portion of NPCC shall design\r\nan UFLS program, pertaining to islands wholly within the NPCC Region, having\r\nperformance characteristics that prevents the frequency from remaining below 59.5\r\nHz for more than 30 seconds in accordance with Figure 1 [Violation Risk Factor: High]\r\n[Time Horizon: Long Term Planning","2020-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[30147,"PRC-006-NPCC-2","R10.",null,"Each Generator Owner shall set each generator underfrequency trip relay, if so\r\nequipped, on or below the appropriate generator underfrequency trip protection\r\nsetting threshold curve in Figure 2, except as otherwise exempted in Requirements\r\nR13 and R16. [Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2020-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[30148,"PRC-006-NPCC-2","R11.",null,"Each Generator Owner shall transmit the generator underfrequency trip setting and\r\ntime delay within 45 calendar days of the Planning Coordinator’s request. [Violation\r\nRisk Factor: Lower] [Time Horizon: Operations Planning]","2020-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[30149,"PRC-006-NPCC-2","R12.",null,"Each Generator Owner with a new generating unit, or an existing generator increasing\r\nits net capability by greater than 10% shall: [Violation Risk Factor: Medium] [Time\r\nHorizon: Long Term Planning]","2020-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[30150,"PRC-006-NPCC-2","R12.1.",null,"Design measures to prevent the generating unit from tripping directly or\r\nindirectly for underfrequency conditions above the appropriate\r\ngenerator tripping threshold curve in Figure 2.","2020-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[30151,"PRC-006-NPCC-2","R12.2.",null,"Design auxiliary system(s) or devices used for the control and protection\r\nof auxiliary system(s), necessary for the generating unit operation such\r\nthat they will not trip the generating unit during underfrequency\r\nconditions above the appropriate generator underfrequency trip\r\nprotection setting threshold curve in Figure 2.","2020-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[30152,"PRC-006-NPCC-2","R13.",null,"For existing non-nuclear units in service prior to July 1, 2015, that have\r\nunderfrequency protections set to trip above the appropriate curve in Figure 2:\r\n[Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2020-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[30153,"PRC-006-NPCC-2","R13.1.",null,"Each Generator Owner shall set the underfrequency protection to\r\noperate at the lowest frequency allowed by the plant design and licensing\r\nlimitations","2020-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[30154,"PRC-006-NPCC-2","R13.2.",null,"Each Generator Owner shall transmit the existing underfrequency\r\nsettings and any changes to the underfrequency settings along with the\r\ntechnical basis for the settings to the Planning Coordinator","2020-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[30155,"PRC-006-NPCC-2","R13.3.",null,"Each Planning Coordinator in Ontario, Québec and the Maritime\r\nProvinces shall arrange for compensatory load shedding, in accordance\r\nwith Attachment A and as provided by a Distribution Provider or\r\nTransmission Owner, that is adequate to compensate for the loss of\r\ngenerator(s) due to early tripping that is within the UFLS island identified\r\nby the Planning Coordinator in Requirement R2","2020-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, PC, DP, GO","Yes",false,null,false]
[30156,"PRC-006-NPCC-2","R13.4.",null,"Each Generator Owner in the ISO-NE Planning Coordinator area and in\r\nNYISO Planning Coordinator area shall arrange for compensatory load\r\nshedding, in accordance with Attachment B and as provided by a\r\nDistribution Provider or Transmission Owner, that is adequate to\r\ncompensate for the loss of generator(s) due to early tripping that is\r\nwithin the UFLS island identified by the Planning Coordinator in\r\nRequirement R2.","2020-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, PC, DP, GO","Yes",false,null,false]
[30157,"PRC-006-NPCC-2","R14.",null,"Each Planning Coordinator in Ontario, Quebec and the Maritime provinces shall apply\r\nthe criteria described in Attachment A to determine the compensatory load shedding\r\nthat is required in Requirement R13.3 for generating units in its respective NPCC area.\r\n[Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2020-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[30158,"PRC-006-NPCC-2","R15.",null,"Each Generator Owner, Distribution Provider or Transmission Owner within the ISONE Planning Coordinator area and in NYISO Planning Coordinator Area shall apply the\r\ncriteria described in Attachment B to determine the compensatory load shedding that is required in Requirement R13.4 for generating units in its respective NPCC area.\r\n[Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2020-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[30159,"PRC-006-NPCC-2","R16.",null,"Each Generator Owner of existing nuclear generating plants with units that have\r\nunderfrequency relay threshold settings above the Eastern Interconnection generator\r\ntripping curve in Figure 2 based on their licensing design shall: [Violation Risk Factor:\r\nHigh] [Time Horizon: Long Term Planning]","2020-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[30160,"PRC-006-NPCC-2","R16.1.",null,"Set the underfrequency protection to operate at a frequency setting that\r\nis as low as possible in accordance with the plant design and licensing\r\nlimitations but not greater than 57.8 Hz.","2020-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[30161,"PRC-006-NPCC-2","R16.2.",null,"Set the frequency trip setting upper tolerance to no greater than + 0.1 Hz.","2020-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[30162,"PRC-006-NPCC-2","R16.3.",null,"Transmit the initial frequency trip setting and any changes to the setting\r\nand the technical basis for the settings to the Planning Coordinator.","2020-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[30139,"PRC-006-NPCC-2","R2.",null,"Each Planning Coordinator shall provide UFLS island boundaries, as identified per the\r\nNERC continent-wide PRC-006 Standard on UFLS, to Distribution Providers, Generator\r\nOwners, and Transmission Owners within 30 calendar days of receipt of a request.\r\n[Violation Risk Factor: Lower] [Time Horizon: Long Term Planning]","2020-07-01",null,"Effective",null,"Lower",null,"N/A",null,"N/A","DP, TO, GO, PC","Yes",false,null,false]
[30140,"PRC-006-NPCC-2","R3.",null,"Each Distribution Provider and Transmission Owner in the Eastern Interconnection\r\nportion of NPCC shall implement an automatic UFLS program, reflecting normal\r\noperating conditions, excluding outages. The automatic UFLS program shall be\r\nimplemented on an island basis for each identified island per the NERC continent-wide\r\nPRC-006 Standard on UFLS as follows: [Violation Risk Factor: High] [Time Horizon: Long\r\nTerm Planning]\r\n The UFLS program shall be implemented by each Distribution Provider and\r\nTransmission Owner according to the frequency thresholds, nominal operating\r\ntimes, and load shedding amounts specified in Attachment C, Tables 1-3; or\r\n The UFLS program shall be implemented collectively by multiple Distribution\r\nProviders or Transmission Owners, as long as they reside in the same UFLS\r\nisland identified by the Planning Coordinator per Requirement R2. These\r\nmultiple Distribution Providers or Transmission Owners, via mutual agreement,\r\nshall act as a single entity to provide an aggregated automatic UFLS program\r\nthat sheds their coincident peak aggregated net Load according to the\r\nfrequency thresholds, total nominal operating time, and load shedding\r\namounts specified in Attachment C, Tables 1-3.","2021-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","PC, TO, DP","Yes",false,null,false]
[30141,"PRC-006-NPCC-2","R4.",null,"Each Distribution Provider or Transmission Owner in the Eastern Interconnection\r\nportion of NPCC that does not meet the UFLS program parameters specified in\r\nAttachment C, Table 1-3, and each Distribution Provider or Transmission Owner in the\r\nQuebec Interconnection that does not meet the UFLS program parameters specified\r\nby its Planning Coordinator shall: [Violation Risk Factor: High] [Time Horizon: Long\r\nTerm Planning]\r\n Within 30 calendar days of determining that it does not meet the\r\nspecified parameters, notify its Planning Coordinator that it does not\r\nmeet the UFLS program parameters; and\r\n Within the following 180 calendar days from notification of the Planning\r\nCoordinator,\r\n(1) develop a Corrective Action Plan and a schedule for implementation that is\r\nmutually agreed upon with its Planning Coordinator or\r\n(2) provide its Planning Coordinator with a technical study that demonstrates\r\nthat the deviations from the program parameters will not result in failure of\r\nUFLS performance criteria being met for any island. The technical study must be\r\nacceptable to the Planning Coordinator prior to implementing deviations from\r\nprogram parameters and shall demonstrate coordination with UFLS programs of\r\nall entities residing within the same island(s) identified by the Planning Coordinator in Requirement R2. The technical study shall also demonstrate\r\ncoordination with other UFLS programs of adjoining Planning Coordinators, or\r\n(3) provide its Planning Coordinator with an analysis demonstrating that no\r\nalternative load shedding solution is available that would allow the Distribution\r\nProvider or Transmission Owner to comply with UFLS Attachment C Table 2 or\r\nAttachment C Table 3.","2020-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","PC, TO, DP","Yes",false,null,false]
[30142,"PRC-006-NPCC-2","R5.",null,"Each Planning Coordinator shall develop and review settings for inhibit thresholds at\r\nleast once per five calendar years (such as, but not limited to, voltage, current and\r\ntime) to be utilized within its region’s UFLS program. [Violation Risk Factor: Medium]\r\n[Time Horizon: Long Term Planning]","2020-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PC","No",false,null,false]
[30143,"PRC-006-NPCC-2","R6.",null,"Each Planning Coordinator shall provide each Transmission Owner and Distribution\r\nProvider within its Planning Coordinator area the applicable inhibit thresholds within\r\n30 calendar days of any changes. [Violation Risk Factor: Lower] [Time Horizon:\r\nOperations Planning]","2020-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","DP, TO, PC","Yes",false,null,false]
[30144,"PRC-006-NPCC-2","R7.",null,"Each Distribution Provider and Transmission Owner that receives a notification\r\npursuant to Requirement R6 shall develop and submit an implementation plan with\r\nrespect to inhibit thresholds for approval by the Planning Coordinator within 90\r\ncalendar days of the request from the Planning Coordinator. [Violation Risk Factor:\r\nLower] [Time Horizon: Operations Planning]","2020-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PC, TO, DP","Yes",false,null,false]
[30145,"PRC-006-NPCC-2","R8.",null,"Each Distribution Provider and Transmission Owner shall implement the inhibit\r\nthresholds provided by the Planning Coordinator in accordance with Requirement R6\r\nand based on the Planning Coordinator approved implementation plan in accordance\r\nwith R7. [Violation Risk Factor: High] [Time Horizon: Operation Planning]","2020-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","PC, NERC, DP","Yes",false,null,false]
[30146,"PRC-006-NPCC-2","R9.",null,"Each Transmission Owner and Distribution Provider shall annually provide\r\ndocumentation, with no more than 15 calendar months between updates, to its\r\nPlanning Coordinator of the actual net Load that would have been shed by the UFLS\r\nrelays at each UFLS stage. The actual net Load shall be coincident with the entity’s\r\nintegrated hourly peak net Load during the previous year, as determined by\r\nmeasuring or calculating Load through the switches that would disconnect load if\r\ntriggered by the UFLS relays. If measured data is unavailable then calculated data may\r\nbe used. [Violation Risk Factor: Lower] [Time Horizon: Long Term Planning]","2020-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, PC, DP","Yes",false,null,false]
[28587,"PRC-008-0","R1.",null,"The Transmission Owner and Distribution Provider with a UFLS program (as required 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.","2005-02-08","2027-03-31","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28588,"PRC-008-0","R2.",null,"The Transmission Owner and Distribution Provider with a UFLS program (as required 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).","2005-02-08","2027-03-31","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28606,"PRC-010-2","R1.",null,"Each Planning Coordinator or Transmission Planner that is developing a UVLS Program shall evaluate its effectiveness and subsequently provide the UVLS Program’s specifications and implementation schedule to the UVLS entities responsible for implementing the UVLS Program. The evaluation shall include, but is not limited to, studies and analyses that show: [Violation Risk Factor: High] [Time Horizon: Long‐term Planning]","2017-04-02",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[28607,"PRC-010-2","R1.1.",null,"The implementation of the UVLS Program resolves the identified undervoltage issues that led to its development and design.","2017-04-02",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[28608,"PRC-010-2","R1.2.",null,"The UVLS Program is integrated through coordination with generator voltage ride‐through capabilities and other protection and control systems, including, but not limited to, transmission line protection, autoreclosing, Remedial Action Schemes, and other undervoltage‐based load shedding programs.","2017-04-02",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[28609,"PRC-010-2","R2.",null,"Each UVLS entity shall adhere to the UVLS Program specifications and implementation schedule determined by its Planning Coordinator or Transmission Planner associated with UVLS Program development per Requirement R1 or with any Corrective Action Plans per Requirement R5. [Violation Risk Factor: High] [Time Horizon: Long‐term Planning]","2017-04-02",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28610,"PRC-010-2","R3.",null,"Each Planning Coordinator or Transmission Planner shall perform a comprehensive assessment to evaluate the effectiveness of each of its UVLS Programs at least once every 60 calendar months. Each assessment shall include, but is not limited to, studies and analyses that evaluate whether: [Violation Risk Factor: Medium] [Time Horizon: Long‐term Planning]","2017-04-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[28611,"PRC-010-2","R3.1.",null,"The UVLS Program resolves the identified undervoltage issues for which the UVLS Program is designed.","2017-04-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[28612,"PRC-010-2","R3.2.",null,"The UVLS Program is integrated through coordination with generator voltage ride‐through capabilities and other protection and control systems, including, but not limited to, transmission line protection, autoreclosing, Remedial Action Schemes, and other undervoltage‐based load shedding programs.","2017-04-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[28613,"PRC-010-2","R4.",null,"Each Planning Coordinator or Transmission Planner shall, within 12 calendar months of an event that resulted in a voltage excursion for which its UVLS Program was designed to operate, perform an assessment to evaluate: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[28614,"PRC-010-2","R4.1.",null,"Whether its UVLS Program resolved the undervoltage issues associated with the event, and","2017-04-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[28615,"PRC-010-2","R4.2.",null,"The performance (i.e., operation and non‐operation) of the UVLS Program equipment.","2017-04-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[28616,"PRC-010-2","R5.",null,"Each Planning Coordinator or Transmission Planner that identifies deficiencies during an assessment performed in either Requirement R3 or R4 shall develop a Corrective Action Plan to address the deficiencies and subsequently provide the Corrective Action Plan, including an implementation schedule, to UVLS entities within three calendar months of completing the assessment. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-02",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[28617,"PRC-010-2","R6.",null,"Each Planning Coordinator that has a UVLS Program in its area shall update a database containing data necessary to model the UVLS Program(s) in its area for use in event analyses and assessments of the UVLS Program at least once each calendar year. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2017-04-02",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PC","No",false,null,false]
[28618,"PRC-010-2","R7.",null,"Each UVLS entity shall provide data to its Planning Coordinator according to the format and schedule specified by the Planning Coordinator to support maintenance of a UVLS Program database. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2017-04-02",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28619,"PRC-010-2","R8.",null,"Each Planning Coordinator that has a UVLS Program in its area shall provide its UVLS Program database to other Planning Coordinators and Transmission Planners within its Interconnection, and other functional entities with a reliability need, within 30 calendar days of a written request. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2017-04-02",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","PC","No",false,null,false]
[28620,"PRC-011-0","R1.",null,"The Transmission Owner and Distribution Provider that owns a UVLS system shall have a UVLS equipment maintenance and testing program in place. This program shall include:","2005-02-08","2027-03-31","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28621,"PRC-011-0","R1.1.",null,"The UVLS system identification which shall include but is not limited to:","2005-02-08","2027-03-31","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28622,"PRC-011-0","R1.1.1.",null,"Relays.","2005-02-08","2027-03-31","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28623,"PRC-011-0","R1.1.2.",null,"Instrument transformers.","2005-02-08","2027-03-31","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28624,"PRC-011-0","R1.1.3.",null,"Communications systems, where appropriate.","2005-02-08","2027-03-31","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28625,"PRC-011-0","R1.1.4.",null,"Batteries.","2005-02-08","2027-03-31","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28626,"PRC-011-0","R1.2.",null,"Documentation of maintenance and testing intervals and their basis.","2005-02-08","2027-03-31","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28627,"PRC-011-0","R1.3.",null,"Summary of testing procedure.","2005-02-08","2027-03-31","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28628,"PRC-011-0","R1.4.",null,"Schedule for system testing.","2005-02-08","2027-03-31","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28629,"PRC-011-0","R1.5.",null,"Schedule for system maintenance.","2005-02-08","2027-03-31","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28630,"PRC-011-0","R1.6.",null,"Date last tested/maintained.","2005-02-08","2027-03-31","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28631,"PRC-011-0","R2.",null,"The Transmission Owner and Distribution Provider that owns a UVLS system shall provide documentation of its UVLS equipment maintenance and testing program and the implementation of that UVLS equipment maintenance and testing program to its Regional Reliability Organization and NERC on request (within 30 calendar days).","2005-02-08","2027-03-31","Effective",null,"LOWER",null,"N/A",null,"N/A","TO, DP","Yes",false,null,false]
[28632,"PRC-012-0","R1.",null,"Each Regional Reliability Organization with a Transmission Owner, Generator Owner, 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:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28633,"PRC-012-0","R1.1.",null,"Description of the process for submitting a proposed SPS for Regional Reliability Organization review.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28634,"PRC-012-0","R1.2.",null,"Requirements to provide data that describes design, operation, and modeling of an SPS.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28635,"PRC-012-0","R1.3.",null,"Requirements to demonstrate that the SPS shall be designed so that a single SPS 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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28636,"PRC-012-0","R1.4.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28637,"PRC-012-0","R1.5.",null,"Requirements to demonstrate the proposed SPS will coordinate with other protection and control systems and applicable Regional Reliability Organization Emergency procedures.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28638,"PRC-012-0","R1.6.",null,"Regional Reliability Organization definition of misoperation.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28639,"PRC-012-0","R1.7.",null,"Requirements for analysis and documentation of corrective action plans for all SPS misoperations.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28640,"PRC-012-0","R1.8.",null,"Identification of the Regional Reliability Organization group responsible for the Regional Reliability Organization’s review procedure and the process for Regional Reliability Organization approval of the procedure.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28641,"PRC-012-0","R1.9.",null,"Determination, as appropriate, of maintenance and testing requirements.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28642,"PRC-012-0","R2.",null,"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).",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28643,"PRC-012-1","R1.",null,"Each Regional Reliability Organization with a Transmission Owner, Generator Owner, or Distribution Providers that uses or is planning to use a RAS shall have a documented Regional Reliability Organization RAS review procedure to ensure that RAS comply with Regional criteria and NERC Reliability Standards. The Regional RAS review procedure shall include:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28644,"PRC-012-1","R1.1.",null,"Description of the process for submitting a proposed RAS for Regional Reliability Organization review.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28645,"PRC-012-1","R1.2.",null,"Requirements to provide data that describes design, operation, and modeling of a RAS.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28646,"PRC-012-1","R1.3.",null,"Requirements to demonstrate that the RAS shall be designed so that a single RAS component failure, when the RAS 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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28647,"PRC-012-1","R1.4.",null,"Requirements to demonstrate that the inadvertent operation of a RAS 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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28648,"PRC-012-1","R1.5.",null,"Requirements to demonstrate the proposed RAS will coordinate with other protection and control systems and applicable Regional Reliability Organization Emergency procedures.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28649,"PRC-012-1","R1.6.",null,"Regional Reliability Organization definition of misoperation.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28650,"PRC-012-1","R1.7.",null,"Requirements for analysis and documentation of corrective action plans for all RAS misoperations",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28651,"PRC-012-1","R1.8.",null,"Identification of the Regional Reliability Organization group responsible for the Regional Reliability Organization’s review procedure and the process for Regional Reliability Organization approval of the procedure.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28652,"PRC-012-1","R1.9.",null,"Determination, as appropriate, of maintenance and testing requirements.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28653,"PRC-012-1","R2.",null,"The Regional Reliability Organization shall provide affected Regional Reliability Organizations and NERC with documentation of its RAS review procedure on request (within 30 calendar days).",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28654,"PRC-012-2","R1.",null,"Prior to placing a new or functionally modified RAS in service or retiring an existing RAS, each RAS-entity shall provide the information identified in Attachment 1 for review to the Reliability Coordinator(s) where the RAS is located. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PC, RC, TO, GO, DP","Yes",false,null,false]
[28655,"PRC-012-2","R2.",null,"Each Reliability Coordinator that receives Attachment 1 information pursuant to Requirement R1 shall, within four full calendar months of receipt or on a mutually agreed upon schedule, perform a review of the RAS in accordance with Attachment 2, and provide written feedback to each RAS-entity. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO, TO, DP, PC, RC","Yes",false,null,false]
[28656,"PRC-012-2","R3.",null,"Prior to placing a new or functionally modified RAS in service or retiring an existing RAS, each RAS‐entity that receives feedback from the reviewing Reliability Coordinator(s) identifying reliability issue(s) shall resolve each issue to obtain approval of the RAS from each reviewing Reliability Coordinator. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PC, RC, TO, GO, DP","Yes",false,null,false]
[28657,"PRC-012-2","R4.",null,"Each Planning Coordinator, at least once every five full calendar years, shall: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO, TO, DP, PC, RC","Yes",false,null,false]
[28658,"PRC-012-2","R4.1.",null,"Perform an evaluation of each RAS within its planning area to determine whether:","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO, TO, DP, PC, RC","Yes",false,null,false]
[29904,"PRC-012-2","R4.1.1.",null,"The RAS mitigates the System condition(s) or Contingency(ies) for which it was designed.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO, TO, DP, PC, RC","Yes",false,null,false]
[29905,"PRC-012-2","R4.1.2.",null,"The RAS avoids adverse interactions with other RAS, and protection and control systems.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO, TO, DP, PC, RC","Yes",false,null,false]
[29906,"PRC-012-2","R4.1.3.",null,"For limited impact1 RAS, the inadvertent operation of the RAS or the failure of the RAS to operate does not cause or contribute to BES Cascading, uncontrolled separation, angular instability, voltage instability, voltage collapse, or unacceptably damped oscillations.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO, TO, DP, PC, RC","Yes",false,null,false]
[29907,"PRC-012-2","R4.1.4.",null,"Except for limited impact RAS, the possible inadvertent operation of the RAS, resulting from any single RAS component malfunction satisfies all of the following:","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO, TO, DP, PC, RC","Yes",false,null,false]
[29908,"PRC-012-2","R4.1.4.1.",null,"The BES shall remain stable.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO, TO, DP, PC, RC","Yes",false,null,false]
[29909,"PRC-012-2","R4.1.4.2.",null,"Cascading shall not occur.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO, TO, DP, PC, RC","Yes",false,null,false]
[29910,"PRC-012-2","R4.1.4.3.",null,"Applicable Facility Ratings shall not be exceeded.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO, TO, DP, PC, RC","Yes",false,null,false]
[29911,"PRC-012-2","R4.1.4.4.",null,"BES voltages shall be within post-Contingency voltage limits and post-Contingency voltage deviation limits as established","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO, TO, DP, PC, RC","Yes",false,null,false]
[29912,"PRC-012-2","R4.1.4.5.",null,"Transient voltage responses shall be within acceptable limits as established by the Transmission Planner and the Planning Coordinator.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO, TO, DP, PC, RC","Yes",false,null,false]
[29913,"PRC-012-2","R4.1.5.",null,"Except for limited impact RAS, a single component failure in the RAS, when the RAS is intended to operate does not prevent the BES from meeting the same performance requirements (defined in Reliability Standard TPL-001-4 or its successor) as those required for the events and conditions for which the RAS is designed.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO, TO, DP, PC, RC","Yes",false,null,false]
[28659,"PRC-012-2","R4.2.",null,"Provide the results of the RAS evaluation including any identified deficiencies to each reviewing Reliability Coordinator and RAS-entity, and each impacted Transmission Planner and Planning Coordinator.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO, TO, DP, PC, RC","Yes",false,null,false]
[28667,"PRC-012-2","R5.",null,"Each RAS-entity, within 120 full calendar days of a RAS operation or a failure of its RAS to operate when expected, or on a mutually agreed upon schedule with its reviewing Reliability Coordinator(s), shall: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PC, RC, TO, GO, DP","Yes",false,null,false]
[28668,"PRC-012-2","R5.1.",null,"Participate in analyzing the RAS operational performance to determine whether:","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PC, RC, TO, GO, DP","Yes",false,null,false]
[29914,"PRC-012-2","R5.1.1.",null,"The System events and/or conditions appropriately triggered the RAS.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PC, RC, DP, GO, TO","Yes",false,null,false]
[29915,"PRC-012-2","R5.1.2.",null,"The RAS responded as designed.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PC, RC, DP, GO, TO","Yes",false,null,false]
[29916,"PRC-012-2","R5.1.3.",null,"The RAS was effective in mitigating BES performance issues it was designed to address.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PC, RC, DP, GO, TO","Yes",false,null,false]
[29917,"PRC-012-2","R5.1.4.",null,"The RAS operation resulted in any unintended or adverse BES response.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PC, RC, DP, GO, TO","Yes",false,null,false]
[28669,"PRC-012-2","R5.2.",null,"Provide the results of RAS operational performance analysis that identified any deficiencies to its reviewing Reliability Coordinator(s).","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PC, RC, TO, GO, DP","Yes",false,null,false]
[28672,"PRC-012-2","R6.",null,"Each RAS-entity shall participate in developing a Corrective Action Plan (CAP) and submit the CAP to its reviewing Reliability Coordinator(s) within six full calendar months of: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning, Long-term Planning]\r\n• Being notified of a deficiency in its RAS pursuant to Requirement R4, or\r\n• Notifying the Reliability Coordinator of a deficiency pursuant to Requirement R5, Part 5.2, or\r\n• Identifying a deficiency in its RAS pursuant to Requirement R8.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PC, RC, TO, GO, DP","Yes",false,null,false]
[28673,"PRC-012-2","R7.",null,"Each RAS-entity shall, for each of its CAPs developed pursuant to Requirement R6: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning, Long-term Planning]","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PC, RC, TO, GO, DP","Yes",false,null,false]
[28674,"PRC-012-2","R7.1.",null,"Implement the CAP.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PC, RC, TO, GO, DP","Yes",false,null,false]
[28675,"PRC-012-2","R7.2.",null,"Update the CAP if actions or timetables change.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PC, RC, TO, GO, DP","Yes",false,null,false]
[28676,"PRC-012-2","R7.3.",null,"Notify each reviewing Reliability Coordinator if CAP actions or timetables change and when the CAP is completed.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","PC, RC, TO, GO, DP","Yes",false,null,false]
[28677,"PRC-012-2","R8.",null,"Each RAS-entity shall participate in performing a functional test of each of its RAS to verify the overall RAS performance and the proper operation of non-Protection System components: [Violation Risk Factor: High] [Time Horizon: Long-term Planning]\r\n• At least once every six full calendar years for all RAS not designated as limited impact, or\r\n• At least once every twelve full calendar years for all RAS designated as limited impact","2021-01-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","PC, RC, TO, GO, DP","Yes",false,null,false]
[28678,"PRC-012-2","R9.",null,"Each Reliability Coordinator shall update a RAS database containing, at a minimum, the information in Attachment 3 at least once every twelve full calendar months. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2021-01-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GO, TO, DP, PC, RC","Yes",false,null,false]
[28679,"PRC-013-0","R1.",null,"The Regional Reliability Organization that has a Transmission Owner, Generator Owner, or Distribution Provider with an SPS installed shall maintain an SPS database. The database shall include the following types of information:",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28680,"PRC-013-0","R1.1.",null,"Design Objectives — Contingencies and system conditions for which the SPS was designed,",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28681,"PRC-013-0","R1.2.",null,"Operation — The actions taken by the SPS in response to Disturbance conditions, and",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28682,"PRC-013-0","R1.3.",null,"Modeling — Information on detection logic or relay settings that control operation of the SPS.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28683,"PRC-013-0","R2.",null,"The Regional Reliability Organization shall provide to affected Regional Reliability Organization(s) and NERC documentation of its database or the information therein on request (within 30 calendar days).",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28684,"PRC-013-1","R1.",null,"The Regional Reliability Organization that has a Transmission Owner, Generator Owner, or Distribution Provider with a RAS installed shall maintain a RAS database. The database shall include the following types of information:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28685,"PRC-013-1","R1.1.",null,"Design Objectives — Contingencies and system conditions for which the RAS was designed,",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28686,"PRC-013-1","R1.2.",null,"Operation —The actions taken by the RAS in response to Disturbance conditions, and",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28687,"PRC-013-1","R1.3.",null,"Modeling — Information on detection logic or relay settings that control operation of the RAS.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28688,"PRC-013-1","R2.",null,"The Regional Reliability Organization shall provide to affected Regional Reliability Organization(s) and NERC documentation of its database or the information therein on request (within 30 calendar days).",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28689,"PRC-014-0","R1.",null,"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.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28690,"PRC-014-0","R2.",null,"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).",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28691,"PRC-014-0","R3.",null,"The documentation of the Regional Reliability Organization’s SPS assessment shall include the following elements:",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28692,"PRC-014-0","R3.1.",null,"Identification of group conducting the assessment and the date the assessment was performed.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28693,"PRC-014-0","R3.2.",null,"Study years, system conditions, and contingencies analyzed in the technical studies on which the assessment is based and when those technical studies were performed.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28694,"PRC-014-0","R3.3.",null,"Identification of SPSs that were found not to comply with NERC standards and Regional Reliability Organization criteria.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28695,"PRC-014-0","R3.4.",null,"Discussion of any coordination problems found between a SPS and other protection and control systems.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28696,"PRC-014-0","R3.5.",null,"Provide corrective action plans for non-compliant SPSs.",null,null,"Retired",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28697,"PRC-014-1","R1.",null,"The Regional Reliability Organization shall assess the operation, coordination, and effectiveness of all RAS installed in its Region at least once every five years for compliance with NERC Reliability Standards and Regional criteria.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28698,"PRC-014-1","R2.",null,"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 RAS installed in its Region to affected Regional Reliability Organizations or NERC on request (within 30 calendar days).",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28699,"PRC-014-1","R3.",null,"The documentation of the Regional Reliability Organization’s RAS assessment shall include the following elements:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28700,"PRC-014-1","R3.1.",null,"Identification of group conducting the assessment and the date the assessment was performed.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28701,"PRC-014-1","R3.2.",null,"Study years, system conditions, and contingencies analyzed in the technical studies on which the assessment is based and when those technical studies were performed.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28702,"PRC-014-1","R3.3.",null,"Identification of RAS that were found not to comply with NERC standards and Regional Reliability Organization criteria.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28703,"PRC-014-1","R3.4.",null,"Discussion of any coordination problems found between a RAS and other protection and control systems.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","RRO","No",false,null,false]
[28704,"PRC-014-1","R3.5.",null,"Provide corrective action plans for non-compliant RAS.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28708,"PRC-015-1","R1.",null,"The Transmission Owner, Generator Owner, and Distribution Provider that owns a RAS shall maintain a list of and provide data for existing and proposed RAS as specified in Reliability Standard PRC-013-1 R1.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28709,"PRC-015-1","R2.",null,"The Transmission Owner, Generator Owner, and Distribution Provider that owns a RAS shall have evidence it reviewed new or functionally modified RAS in accordance with the Regional Reliability Organization’s procedures as defined in Reliability Standard PRC-012-1_R1 prior to being placed in service.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28710,"PRC-015-1","R3.",null,"The Transmission Owner, Generator Owner, and Distribution Provider that owns a RAS shall provide documentation of RAS data and the results of Studies that show compliance of new or functionally modified RAS with NERC Reliability Standards and Regional Reliability Organization criteria to affected Regional Reliability Organizations and NERC on request (within 30 calendar days).","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28714,"PRC-016-1","R1.",null,"The Transmission Owner, Generator Owner, and Distribution Provider that owns a RAS shall analyze its RAS operations and maintain a record of all misoperations in accordance with the Regional RAS review procedure specified in Reliability Standard PRC-012-1_R1.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28715,"PRC-016-1","R2.",null,"The Transmission Owner, Generator Owner, and Distribution Provider that owns a RAS shall take corrective actions to avoid future misoperations.","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28716,"PRC-016-1","R3.",null,"The Transmission Owner, Generator Owner, and Distribution Provider that owns a RAS 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).","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28717,"PRC-017-0","R1.",null,"The Transmission Owner, Generator Owner, and Distribution Provider that owns an SPS shall have a system maintenance and testing program(s) in place. The program(s) shall include:","2005-02-08","2028-06-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28718,"PRC-017-0","R1.1.",null,"SPS identification shall include but is not limited to:","2005-02-08","2028-06-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28719,"PRC-017-0","R1.1.1.",null,"Relays.","2005-02-08","2028-06-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28720,"PRC-017-0","R1.1.2.",null,"Instrument transformers.","2005-02-08","2028-06-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28721,"PRC-017-0","R1.1.3.",null,"Communications systems, where appropriate.","2005-02-08","2028-06-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28722,"PRC-017-0","R1.1.4.",null,"Batteries.","2005-02-08","2028-06-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28723,"PRC-017-0","R1.2.",null,"Documentation of maintenance and testing intervals and their basis.","2005-02-08","2028-06-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28724,"PRC-017-0","R1.3.",null,"Summary of testing procedure.","2005-02-08","2028-06-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28725,"PRC-017-0","R1.4.",null,"Schedule for system testing.","2005-02-08","2028-06-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28726,"PRC-017-0","R1.5.",null,"Schedule for system maintenance.","2005-02-08","2028-06-30","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28727,"PRC-017-0","R1.6.",null,"Date last tested/maintained.","2005-02-08","2028-06-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28728,"PRC-017-0","R2.",null,"The Transmission Owner, Generator Owner, and Distribution Provider that owns an SPS shall provide documentation of the program and its implementation to the appropriate Regional Reliability Organizations and NERC on request (within 30 calendar days).","2005-02-08","2028-06-30","Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28729,"PRC-017-1","R1.",null,"The Transmission Owner, Generator Owner, and Distribution Provider that owns a RAS shall\nhave a system maintenance and testing program(s) in place. The program(s) shall include:","2017-04-01","2027-03-31","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28730,"PRC-017-1","R1.1.",null,"RAS identification shall include but is not limited to:","2017-04-01","2027-03-31","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28731,"PRC-017-1","R1.1.1.",null,"Relays.","2017-04-01","2027-03-31","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28732,"PRC-017-1","R1.1.2.",null,"Instrument transformers.","2017-04-01","2027-03-31","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28733,"PRC-017-1","R1.1.3.",null,"Communications systems, where appropriate.","2017-04-01","2027-03-31","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28734,"PRC-017-1","R1.1.4.",null,"Batteries.","2017-04-01","2027-03-31","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28735,"PRC-017-1","R1.2.",null,"Documentation of maintenance and testing intervals and their basis.","2017-04-01","2027-03-31","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28736,"PRC-017-1","R1.3.",null,"Summary of testing procedure.","2017-04-01","2027-03-31","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28737,"PRC-017-1","R1.4.",null,"Schedule for system testing.","2017-04-01","2027-03-31","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28738,"PRC-017-1","R1.5.",null,"Schedule for system maintenance.","2017-04-01","2027-03-31","Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28739,"PRC-017-1","R1.6.",null,"Date last tested/maintained.","2017-04-01","2027-03-31","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28740,"PRC-017-1","R2.",null,"The Transmission Owner, Generator Owner, and Distribution Provider that owns a RAS shall\nprovide documentation of the program and its implementation to the appropriate Regional\nReliability Organizations and NERC on request (within 30 calendar days).","2017-04-01","2027-03-31","Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28741,"PRC-018-1","R1.",null,"Each Transmission Owner and Generator Owner required to install DMEs by its Regional Reliability Organization (reliability standard PRC-002 Requirements 1-3) shall have DMEs installed that meet the following requirements:","2007-02-02","2022-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28742,"PRC-018-1","R1.1.",null,"Internal Clocks in DME devices shall be synchronized to within 2 milliseconds or less of Universal Coordinated Time scale (UTC)","2007-02-02","2022-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28743,"PRC-018-1","R1.2.",null,"Recorded data from each Disturbance shall be retrievable for ten calendar days..","2007-02-02","2022-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28744,"PRC-018-1","R2.",null,"The Transmission Owner and Generator Owner shall each install DMEs in accordance with its Regional Reliability Organization’s installation requirements (reliability standard PRC-002 Requirements 1 through 3).","2007-02-02","2022-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28745,"PRC-018-1","R3.",null,"The Transmission Owner and Generator Owner shall each maintain, and report to its Regional Reliability Organization on request, the following data on the DMEs installed to meet that region’s installation requirements (reliability standard PRC-002 Requirements1.1, 2.1 and 3.1):","2007-02-02","2022-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28746,"PRC-018-1","R3.1.",null,"Type of DME (sequence of event recorder, fault recorder, or dynamic disturbance recorder).","2007-02-02","2022-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28747,"PRC-018-1","R3.2.",null,"Make and model of equipment.","2007-02-02","2022-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28748,"PRC-018-1","R3.3.",null,"Installation location.","2007-02-02","2022-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28749,"PRC-018-1","R3.4.",null,"Operational status.","2007-02-02","2022-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28750,"PRC-018-1","R3.5.",null,"Date last tested.","2007-02-02","2022-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28751,"PRC-018-1","R3.6.",null,"Monitored elements, such as transmission circuit, bus section, etc.","2007-02-02","2022-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28752,"PRC-018-1","R3.7.",null,"Monitored devices, such as circuit breaker, disconnect status, alarms, etc.","2007-02-02","2022-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28753,"PRC-018-1","R3.8.",null,"Monitored electrical quantities, such as voltage, current, etc.","2007-02-02","2022-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28754,"PRC-018-1","R4.",null,"The Transmission Owner and Generator Owner shall each provide Disturbance data (recorded by DMEs) in accordance with its Regional Reliability Organization’s requirements (reliability standard PRC-002 Requirement 4).","2007-02-02","2022-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28755,"PRC-018-1","R5.",null,"The Transmission Owner and Generator Owner shall each archive all data recorded by DMEs for Regional Reliability Organization-identified events for at least three years.","2007-02-02","2022-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28756,"PRC-018-1","R6.",null,"Each Transmission Owner and Generator Owner that is required by its Regional Reliability Organization to have DMEs shall have a maintenance and testing program for those DMEs that includes:","2007-02-02","2022-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28757,"PRC-018-1","R6.1.",null,"Maintenance and testing intervals and their basis.","2007-02-02","2022-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28758,"PRC-018-1","R6.2.",null,"Summary of maintenance and testing procedures.","2007-02-02","2022-06-30","Retired",null,"LOWER",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28759,"PRC-019-1","R1.",null,"At a maximum of every five calendar years, each Generator Owner and Transmission Owner with applicable Facilities shall coordinate the voltage regulating system controls, (including in-service1 limiters and protection functions) with the applicable\nequipment capabilities and settings of the applicable Protection System devices and functions. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28760,"PRC-019-1","R1.1.",null,"Assuming the normal automatic voltage regulator control loop and steady-state system operating conditions, verify the following coordination items for each applicable Facility:",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28761,"PRC-019-1","R1.1.1.",null,"The in-service limiters are set to operate before the Protection System of the applicable Facility in order to avoid disconnecting the generator unnecessarily.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28762,"PRC-019-1","R1.1.2.",null,"The applicable in-service Protection System devices are set to operate to isolate or de-energize equipment in order to limit the extent of damage when operating conditions exceed equipment capabilities or stability limits.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28763,"PRC-019-1","R2.",null,"Within 90 calendar days following the identification or implementation of systems, equipment or setting changes that will affect the coordination described in Requirement R1, each Generator Owner and Transmission Owner with applicable Facilities shall\nperform the coordination as described in Requirement R1. These possible systems, equipment or settings changes include, but are not limited to the following [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]:\n Voltage regulating settings or equipment changes;\n Protection System settings or component changes;\n Generating or synchronous condenser equipment capability changes; or\n Generator or synchronous condenser step-up transformer changes.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28764,"PRC-019-2","R1.",null,"At a maximum of every five calendar years, each Generator Owner and Transmission Owner with applicable Facilities shall coordinate the voltage regulating system controls, (including in-service1 limiters and protection functions) with the applicable equipment capabilities and settings of the applicable Protection System devices and functions. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28765,"PRC-019-2","R1.1.",null,"Assuming the normal automatic voltage regulator control loop and steady-state system operating conditions, verify the following coordination items for each applicable Facility:","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28766,"PRC-019-2","R1.1.1.",null,"The in-service limiters are set to operate before the Protection System of the applicable Facility in order to avoid disconnecting the generator unnecessarily.","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28767,"PRC-019-2","R1.1.2.",null,"The applicable in-service Protection System devices are set to operate to isolate or de-energize equipment in order to limit the extent of damage when operating conditions exceed equipment capabilities or stability limits.","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28768,"PRC-019-2","R2.",null,"Within 90 calendar days following the identification or implementation of systems, equipment or setting changes that will affect the coordination described in Requirement R1, each Generator Owner and Transmission Owner with applicable Facilities shall\nperform the coordination as described in Requirement R1. These possible systems, equipment or settings changes include, but are not limited to the following [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]:\n• Voltage regulating settings or equipment changes;\n• Protection System settings or component changes;\n• Generating or synchronous condenser equipment capability changes; or\n• Generator or synchronous condenser step-up transformer changes.","2016-07-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28769,"PRC-020-1","R1.",null,"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:",null,null,"Retired",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28770,"PRC-020-1","R1.1.",null,"Owner and operator of the UVLS program.",null,null,"Retired",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28771,"PRC-020-1","R1.2.",null,"Size and location of customer load, or percent of connected load, to be interrupted.",null,null,"Retired",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28772,"PRC-020-1","R1.3.",null,"Corresponding voltage set points and overall scheme clearing times.",null,null,"Retired",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28773,"PRC-020-1","R1.4.",null,"Time delay from initiation to trip signal.",null,null,"Retired",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28774,"PRC-020-1","R1.5.",null,"Breaker operating times.",null,null,"Retired",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28775,"PRC-020-1","R1.6.",null,"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.",null,null,"Retired",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28776,"PRC-020-1","R2.",null,"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.",null,null,"Retired",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28777,"PRC-020-2","R1.",null,"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:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28778,"PRC-020-2","R1.1.",null,"Owner and operator of the UVLS program.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28779,"PRC-020-2","R1.2.",null,"Size and location of customer load, or percent of connected load, to be interrupted.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28780,"PRC-020-2","R1.3.",null,"Corresponding voltage set points and overall scheme clearing times.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28781,"PRC-020-2","R1.4.",null,"Time delay from initiation to trip signal.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28782,"PRC-020-2","R1.5.",null,"Breaker operating times.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28783,"PRC-020-2","R1.6.",null,"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 Remedial Action Schemes.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28784,"PRC-020-2","R2.",null,"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.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","RRO","No",false,null,false]
[28805,"PRC-023-2(i)","R1.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall use any one of the following criteria (Requirement R1, criteria 1 through 13) for any specific circuit terminal to prevent its phase protective relay settings from limiting transmission system loadability while maintaining reliable protection of the BES for all fault conditions. Each Transmission Owner, Generator Owner, and Distribution Provider shall evaluate relay loadability at 0.85 per unit voltage and a power factor angle of 30 degrees. (see standard for list of criteria.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28806,"PRC-023-2(i)","R2.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall set its out-of-step blocking elements to allow tripping of phase protective relays for faults that occur during the loading conditions used to verify transmission line relay loadability per Requirement R1.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28807,"PRC-023-2(i)","R3.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that uses a circuit capability with the practical limitations described in Requirement R1, criterion 6, 7, 8, 9, 12, or 13 shall use the calculated circuit capability as the Facility Rating of the circuit and shall obtain the agreement of the Planning Coordinator, Transmission Operator, and Reliability Coordinator with the calculated circuit capability.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28808,"PRC-023-2(i)","R4.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that chooses to use Requirement R1 criterion 2 as the basis for verifying transmission line relay loadability shall provide its Planning Coordinator, Transmission Operator, and Reliability Coordinator with an updated list of circuits associated with those transmission line relays at least once each calendar year, with no more than 15 months between reports.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28809,"PRC-023-2(i)","R5.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that sets transmission line relays according to Requirement R1 criterion 12 shall provide an updated list of the circuits associated with those relays to its Regional Entity at least once each calendar year, with no more than 15 months between reports, to allow the ERO to compile a list of all circuits that have protective relay settings that limit circuit capability.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28810,"PRC-023-2(i)","R6.",null,"Each Planning Coordinator shall conduct an assessment at least once each calendar year, with no more than 15 months between assessments, by applying the criteria in Attachment B to determine the circuits in its Planning Coordinator area for which Transmission Owners, Generator Owners, and Distribution Providers must comply with Requirements R1 through R5. The Planning Coordinator shall:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[28811,"PRC-023-2(i)","R6.1.",null,"Maintain a list of circuits subject to PRC-023-2(i) per application of Attachment B, including identification of the first calendar year in which any criterion in Attachment B applies.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","PC","No",false,null,false]
[28812,"PRC-023-2(i)","R6.2.",null,"Provide the list of circuits to all Regional Entities, Reliability Coordinators, Transmission Owners, Generator Owners, and Distribution Providers within its Planning Coordinator area within 30 calendar days of the establishment of the initial list and within 30 calendar days of any changes to that list.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","PC","No",false,null,false]
[28821,"PRC-023-4","R1.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall use any one of the following criteria (Requirement R1, criteria 1 through 13) for any specific circuit terminal to prevent its phase protective relay settings from limiting transmission system loadability while maintaining reliable protection of the BES for all fault conditions. Each Transmission Owner,\nGenerator Owner, and Distribution Provider shall evaluate relay loadability at 0.85 per unit voltage and a power factor angle of 30 degrees. [Violation Risk Factor: High] [Time Horizon: Long Term Planning]. See detailed Criteria in the standard.","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28822,"PRC-023-4","R2.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall set its out-of-step blocking elements to allow tripping of phase protective relays for faults that occur during the loading conditions used to verify transmission line relay loadability per Requirement R1. [Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28823,"PRC-023-4","R3.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that uses a circuit capability with the practical limitations described in Requirement R1, criterion 7, 8, 9, 12, or 13 shall use the calculated circuit capability as the Facility Rating of the circuit and shall obtain the agreement of the Planning Coordinator, Transmission Operator, and Reliability Coordinator with\nthe calculated circuit capability. [Violation Risk Factor: Medium] [Time Horizon: Long Term Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28824,"PRC-023-4","R4.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that chooses to use Requirement R1 criterion 2 as the basis for verifying transmission line relay loadability shall provide its Planning Coordinator, Transmission Operator, and Reliability Coordinator with an updated list of circuits associated with those transmission line relays at least once each calendar\nyear, with no more than 15 months between reports. [Violation Risk Factor: Lower] [Time Horizon: Long Term Planning]","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28825,"PRC-023-4","R5.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that sets transmission line relays according to Requirement R1 criterion 12 shall provide an updated list of the circuits associated with those relays to its Regional Entity at least once each calendar year, with no more than 15 months between reports, to allow the ERO to compile a list of all circuits that have\nprotective relay settings that limit circuit capability. [Violation Risk Factor: Lower] [Time Horizon: Long Term Planning]","2017-04-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28826,"PRC-023-4","R6.","YES","Each Planning Coordinator shall conduct an assessment at least once each calendar year, with no more than 15 months between assessments, by applying the criteria in PRC-023-4, Attachment B to determine the circuits in its Planning Coordinator area for which Transmission Owners, Generator Owners, and Distribution Providers must comply with Requirements R1 through R5.\nThe Planning Coordinator shall: [Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[30012,"PRC-023-4","R6.","YES","Each Planning Coordinator shall conduct an assessment at least once each calendar year, with no more than 15 months between assessments, by applying the criteria in PRC-023-4, Attachment B to determine the circuits in its Planning Coordinator area for which Transmission Owners, Generator Owners, and Distribution Providers must comply with Requirements R1 through R5. The Planning Coordinator shall: [Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[28827,"PRC-023-4","R6.1.",null,"Maintain a list of circuits subject to PRC-023-4 per application of Attachment B, including identification of the first calendar year in which any criterion in PRC-023-4, Attachment B applies.","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[28828,"PRC-023-4","R6.2.",null,"Provide the list of circuits to all Regional Entities, Reliability Coordinators, Transmission Owners, Generator Owners, and Distribution Providers within its Planning Coordinator area within 30 calendar days of the establishment of the initial list and within 30 calendar days of any changes to that list.","2017-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","PC","No",false,null,false]
[30684,"PRC-023-5","R1.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall use any one of the following criteria (Requirement R1, criteria 1 through 13) for any specific circuit terminal to prevent its phase protective relay settings from limiting transmission system loadability while maintaining reliable protection of the BES for all fault conditions. Each Transmission Owner,Generator Owner, and Distribution Provider shall evaluate relay loadability at 0.85 per unit voltage and a power factor angle of 30 degrees. [Violation Risk Factor: High] [Time Horizon: Long Term Planning]. See detailed Criteria in the standard.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TO, PC, GO, DP","Yes",false,null,false]
[30685,"PRC-023-5","R2.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall set its out-of-step blocking elements to allow tripping of phase protective relays for faults that occur during the loading conditions used to verify transmission line relay loadability per Requirement R1. [Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TO, PC, GO, DP","Yes",false,null,false]
[30686,"PRC-023-5","R3.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that uses a circuit capability with the practical limitations described in Requirement R1, criterion 7, 8, 9, 12, or 13 shall use the calculated circuit capability as the Facility Rating of the circuit and shall obtain the agreement of the Planning Coordinator, Transmission Operator, and Reliability Coordinator withthe calculated circuit capability. [Violation Risk Factor: Medium] [Time Horizon: Long Term Planning]","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO, DP, TO, PC","Yes",false,null,false]
[30687,"PRC-023-5","R4.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that chooses to use Requirement R1 criterion 2 as the basis for verifying transmission line relay loadability shall provide its Planning Coordinator, Transmission Operator, and Reliability Coordinator with an updated list of circuits associated with those transmission line relays at least once each calendaryear, with no more than 15 months between reports. [Violation Risk Factor: Lower] [Time Horizon: Long Term Planning]","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, PC, GO, DP","Yes",false,null,false]
[30688,"PRC-023-5","R5.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider that sets transmission line relays according to Requirement R1 criterion 12 shall provide an updated list of the circuits associated with those relays to its Regional Entity at least once each calendar year, with no more than 15 months between reports, to allow the ERO to compile a list of all circuits that haveprotective relay settings that limit circuit capability. [Violation Risk Factor: Lower] [Time Horizon: Long Term Planning]","2024-04-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A","TO, PC, GO, DP","Yes",false,null,false]
[30689,"PRC-023-5","R6.","YES","Each Planning Coordinator shall conduct an assessment at least once each calendar year, with no more than 15 months between assessments, by applying the criteria in PRC-023-4, Attachment B to determine the circuits in its Planning Coordinator area for which Transmission Owners, Generator Owners, and Distribution Providers must comply with Requirements R1 through R5.The Planning Coordinator shall: [Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TO, PC, GO, DP","Yes",false,null,false]
[30690,"PRC-023-5","R6.","YES","Each Planning Coordinator shall conduct an assessment at least once each calendar year, with no more than 15 months between assessments, by applying the criteria in PRC-023-4, Attachment B to determine the circuits in its Planning Coordinator area for which Transmission Owners, Generator Owners, and Distribution Providers must comply with Requirements R1 through R5. The Planning Coordinator shall: [Violation Risk Factor: High] [Time Horizon: Long Term Planning]","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TO, PC, GO, DP","Yes",false,null,false]
[30691,"PRC-023-5","R6.1.",null,"Maintain a list of circuits subject to PRC-023-5 per application of Attachment B, including identification of the first calendar year in which any criterion in PRC-023-5, Attachment B applies.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TO, PC, GO, DP","Yes",false,null,false]
[30692,"PRC-023-5","R6.2.",null,"Provide the list of circuits to all Regional Entities, Reliability Coordinators, Transmission Owners, Generator Owners, and Distribution Providers within its Planning Coordinator area within 30 calendar days of the establishment of the initial list and within 30 calendar days of any changes to that list.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TO, PC, GO, DP","Yes",false,null,false]
[28834,"PRC-024-2","R1.",null,"Each Generator Owner that has generator frequency protective relaying1 activated to trip its applicable generating unit(s) shall set its protective relaying such that the generator frequency protective relaying does not trip the applicable generating unit(s) within the “no trip zone” of PRC-024 Attachment 1, subject to the following exceptions:2 [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]\n• Generating unit(s) may trip if the protective functions (such as out-of-step functions or loss-of-field functions) operate due to an impending or actual loss of synchronism or, for asynchronous generating units, due to instability in power conversion control\nequipment.\n• Generating unit(s) may trip if clearing a system fault necessitates disconnecting (a) generating unit(s).\n• Generating unit(s) may trip within a portion of the “no trip zone” of PRC-024 Attachment 1 for documented and communicated regulatory or equipment limitations in accordance with Requirement R3.","2016-07-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28835,"PRC-024-2","R2.",null,"Each Generator Owner that has generator voltage protective relaying1 activated to trip its applicable generating unit(s) shall set its protective relaying such that the generator voltage protective relaying does not trip the applicable generating unit(s) as a result of a voltage excursion (at the point of interconnection3) caused by an event on the transmission system external to the generating plant that remains within the “no trip zone” of PRC-024 Attachment 2.4 If the Transmission Planner allows less stringent voltage relay settings than those required to meet PRC-024 Attachment 2, then the Generator Owner shall set its protective relaying within the voltage recovery characteristics of a location-specific Transmission Planner’s study. Requirement R2 is subject to the following exceptions: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]\n• Generating unit(s) may trip in accordance with a Special Protection System (SPS) or Remedial Action Scheme (RAS).\n• Generating unit(s) may trip if clearing a system fault necessitates disconnecting (a) generating unit(s).\n• Generating unit(s) may trip by action of protective functions (such as out-of-step functions or loss-of-field functions) that operate due to an impending or actual loss of synchronism or, for asynchronous generating units, due to instability in power\nconversion control equipment.\n• Generating unit(s) may trip within a portion of the “no trip zone” of PRC-024 Attachment 2 for documented and communicated regulatory or equipment limitations in accordance with Requirement R3.","2016-07-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28836,"PRC-024-2","R3.",null,"Each Generator Owner shall document each known regulatory or equipment limitation, that prevents an applicable generating unit with generator frequency or voltage protective relays from meeting the relay setting criteria in Requirements R1 or R2 including (but not limited to) study results, experience from an actual event, or manufacturer’s advice. [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2016-07-01","2022-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28837,"PRC-024-2","R3.1.",null,"The Generator Owner shall communicate the documented regulatory or equipment limitation, or the removal of a previously documented regulatory or equipment limitation, to its Planning Coordinator and Transmission Planner within 30 calendar\ndays of any of the following:\n• Identification of a regulatory or equipment limitation.\n• Repair of the equipment causing the limitation that removes the limitation.\n• Replacement of the equipment causing the limitation with equipment that removes the limitation.\n• Creation or adjustment of an equipment limitation caused by consumption of the\ncumulative turbine life-time frequency excursion allowance.","2016-07-01","2022-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[28838,"PRC-024-2","R4.",null,"Each Generator Owner shall provide its applicable generator protection trip settings associated with Requirements R1 and R2 to the Planning Coordinator or Transmission Planner that models the associated unit within 60 calendar days of receipt of a written\nrequest for the data and within 60 calendar days of any change to those previously requested trip settings unless directed by the requesting Planning Coordinator or Transmission Planner that the reporting of relay setting changes is not required. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2016-07-01","2022-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[30576,"PRC-024-3","R1.",null,"Each Generator Owner shall set its applicable frequency protection5 in accordance with \r\nPRC-024 Attachment 1 such that the applicable protection does not cause the \r\ngenerating resource to trip or cease injecting current within the “no trip zone” during a \r\nfrequency excursion with the following exceptions: [Violation Risk Factor: Medium] \r\n[Time Horizon: Long-term Planning]\r\n• Applicable frequency protection may be set to trip or cease injecting current within \r\na portion of the “no trip zone” for documented and communicated regulatory or \r\nequipment limitations in accordance with Requirement R3.","2016-07-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, PC, GO","Yes",false,null,false]
[30577,"PRC-024-3","R2.",null,"Each Generator Owner shall set its applicable voltage protection5 in accordance with \r\nPRC-024 Attachment 2, such that the applicable protection does not cause the \r\ngenerating resource to trip or cease injecting current within the “no trip zone” during a \r\nvoltage excursion at the high side of the GSU or MPT, subject to the following \r\nexceptions: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]\r\n• If the Transmission Planner allows less stringent voltage protection settings than \r\nthose required to meet PRC-024 Attachment 2, then the Generator Owner may set \r\nits protection within the voltage recovery characteristics of a location-specific \r\nTransmission Planner’s study.\r\n• Applicable voltage protection may be set to trip or cease injecting current during a \r\nvoltage excursion within a portion of the “no trip zone” for documented and \r\ncommunicated regulatory or equipment limitations in accordance with \r\nRequirement R3","2016-07-01","2022-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, PC, GO","Yes",false,null,false]
[30578,"PRC-024-3","R3.",null,"Each Generator Owner shall document each known regulatory or equipment limitation6\r\nthat prevents an applicable generating resource(s) with frequency or voltage protection\r\nfrom meeting the protection setting criteria in Requirements R1 or R2, including (but not \r\nlimited to) study results, experience from an actual event, or manufacturer’s advice.\r\n[Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2016-07-01","2022-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","TO, PC, GO","Yes",false,null,false]
[30579,"PRC-024-3","R3.1.",null,"The Generator Owner shall communicate the documented regulatory or equipment \r\nlimitation, or the removal of a previously documented regulatory or equipment \r\nlimitation, to its Planning Coordinator and Transmission Planner within 30 calendar \r\ndays of any of the following:\r\n• Identification of a regulatory or equipment limitation.\r\n• Repair of the equipment causing the limitation that removes the limitation.\r\n• Replacement of the equipment causing the limitation with equipment that \r\nremoves the limitation.\r\n• Creation or adjustment of an equipment limitation caused by consumption of \r\nthe cumulative turbine life-time frequency excursion allowance.","2016-07-01","2022-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","TO, PC, GO","Yes",false,null,false]
[30580,"PRC-024-3","R4.",null,"Each Generator Owner shall provide its applicable protection settings associated with \r\nRequirements R1 and R2 to the Planning Coordinator or Transmission Planner that \r\nmodels the associated generating resource(s) within 60 calendar days of receipt of a \r\nwritten request for the data and within 60 calendar days of any change to those \r\npreviously requested settings unless directed by the requesting Planning Coordinator or \r\nTransmission Planner that the reporting of protection setting changes is not required. \r\n[Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2016-07-01","2022-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","TO, PC, GO","Yes",false,null,false]
[28840,"PRC-025-2","R1.",null,"Each Generator Owner, Transmission Owner, and Distribution Provider shall apply\nsettings that are in accordance with PRC-025-2 – Attachment 1: Relay Settings, on each\nload-responsive protective relay while maintaining reliable fault protection. [Violation\nRisk Factor: High] [Time Horizon: Long-Term Planning]","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28841,"PRC-026-1","R1.",null,"Each Planning Coordinator shall, at least once each calendar year, provide notification of each generator, transformer, and transmission line BES Element in its area that meets one or more of the following criteria, if any, to the respective Generator Owner and Transmission Owner: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]\nCriteria:\n1. Generator(s) where an angular stability constraint exists that is addressed by a System Operating Limit (SOL) or a Remedial Action Scheme (RAS) and those Elements terminating at the Transmission station associated with the generator(s).\n2. An Element that is monitored as part of an SOL identified by the Planning Coordinator’s methodology1 based on an angular stability constraint.\n3. An Element that forms the boundary of an island in the most recent underfrequency load shedding (UFLS) design assessment based on application of the Planning Coordinator’s criteria for identifying islands, only if the island is formed by tripping the Element due to angular instability.\n4. An Element identified in the most recent annual Planning Assessment where relay tripping occurs due to a stable or unstable2 power swing during a simulated disturbance.","2018-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, PC, GO","Yes",false,null,false]
[28842,"PRC-026-1","R2.",null,"Each Generator Owner and Transmission Owner shall: [Violation Risk Factor: High] [Time Horizon: Operations Planning]","2020-01-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28843,"PRC-026-1","R2.1.",null,"Within 12 full calendar months of notification of a BES Element pursuant to Requirement R1, determine whether its load-responsive protective relay(s) applied to that BES Element meets the criteria in PRC-026-1 – Attachment B where an evaluation of that Element’s load-responsive protective relay(s) based on PRC-026-1 – Attachment B criteria has not been performed in the last five calendar years.","2020-01-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28844,"PRC-026-1","R2.2.",null,"Within 12 full calendar months of becoming aware4 of a generator, transformer, or transmission line BES Element that tripped in response to a stable or unstable5 power swing due to the operation of its protective relay(s), determine whether its load-responsive protective relay(s) applied to that BES Element meets the criteria in PRC-026-1 – Attachment B.","2020-01-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28845,"PRC-026-1","R3.",null,"Each Generator Owner and Transmission Owner shall, within six full calendar months of determining a load-responsive protective relay does not meet the PRC-026-1 – Attachment B criteria pursuant to Requirement R2, develop a Corrective Action Plan (CAP) to meet one of the following: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]\n• The Protection System meets the PRC-026-1 – Attachment B criteria, while maintaining dependable fault detection and dependable out-of-step tripping (if out-of-step tripping is applied at the terminal of the BES Element); or\n• The Protection System is excluded under the PRC-026-1 – Attachment A criteria (e.g., modifying the Protection System so that relay functions are supervised by power swing blocking or using relay systems that are immune to power swings), while maintaining dependable fault detection and dependable out-of-step tripping (if out-of-step tripping is applied at the terminal of the BES Element).","2020-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[28846,"PRC-026-1","R4.",null,"Each Generator Owner and Transmission Owner shall implement each CAP developed pursuant to Requirement R3 and update each CAP if actions or timetables change until all actions are complete. [Violation Risk Factor: Medium][Time Horizon: Long-Term Planning]","2020-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30693,"PRC-026-2","R1.",null,"Each Planning Coordinator shall, at least once each calendar year, provide notification of each generator, transformer, and transmission line BES Element in its area that meets one or more of the following criteria, if any, to the respective Generator Owner and Transmission Owner: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]Criteria:1. Generator(s) where an angular stability constraint, identified in Planning Assessments of the Near-Term Transmission Planning Horizon for a planning  event, that is addressed by limiting the output of a generator or a Remedial Action Scheme (RAS), and those Elements terminating at the Transmission station associated with the generator(s).2. Elements associated with angular instability identified in Planning Assessments of the Near-Term Transmission Planning Horizon for a planning event.3. An Element that forms the boundary of an island in the most recent underfrequency load shedding (UFLS) design assessment based on application of the Planning Coordinator’s criteria for identifying islands, only if the island is formed by tripping the Element due to angular instability.4. An Element identified in the most recent annual Planning Assessment of the Near-Term Transmission Planning Horizon where relay tripping occurs due to a stable or unstable2 power swing during a simulated disturbance for a planning event.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, PC, GO","Yes",false,null,false]
[30694,"PRC-026-2","R2.",null,"Each Generator Owner and Transmission Owner shall: [Violation Risk Factor: High] [Time Horizon: Operations Planning]","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TO, PC, GO","Yes",false,null,false]
[30695,"PRC-026-2","R2.1.",null,"Within 12 full calendar months of notification of a BES Element pursuant to Requirement R1, determine whether its load-responsive protective relay(s) applied to that BES Element meets the criteria in PRC-026-2 – Attachment B where an evaluation of that Element’s load-responsive protective relay(s) based on PRC-026-2 – Attachment B criteria has not been performed in the last five calendar years.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TO, PC, GO","Yes",false,null,false]
[30696,"PRC-026-2","R2.2.",null,"Within 12 full calendar months of becoming aware4 of a generator, transformer, or transmission line BES Element that tripped in response to a stable or unstable5 power swing due to the operation of its protective relay(s), determine whether its load-responsive protective relay(s) applied to that BES Element meets the criteria in PRC-026-2 – Attachment B.","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TO, PC, GO","Yes",false,null,false]
[30697,"PRC-026-2","R3.",null,"Each Generator Owner and Transmission Owner shall, within six full calendar months of determining a load-responsive protective relay does not meet the PRC-026-2 – Attachment B criteria pursuant to Requirement R2, develop a Corrective Action Plan (CAP) to meet one of the following: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]• The Protection System meets the PRC-026-2 – Attachment B criteria, while maintaining dependable fault detection and dependable out-of-step tripping (if out-of-step tripping is applied at the terminal of the BES Element); or• The Protection System is excluded under the PRC-026-2 – Attachment A criteria (e.g., modifying the Protection System so that relay functions are supervised by power swing blocking or using relay systems that are immune to power swings), while maintaining dependable fault detection and dependable out-of-step tripping (if out-of-step tripping is applied at the terminal of the BES Element).","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, PC, GO","Yes",false,null,false]
[30698,"PRC-026-2","R4.",null,"Each Generator Owner and Transmission Owner shall implement each CAP developed pursuant to Requirement R3 and update each CAP if actions or timetables change until all actions are complete. [Violation Risk Factor: Medium][Time Horizon: Long-Term Planning]","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, PC, GO","Yes",false,null,false]
[28847,"PRC-027-1","R1.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall establish a process for developing new and revised Protection System settings for BES Elements, such that the Protection Systems operate in the intended sequence during Faults. The process shall include: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28848,"PRC-027-1","R1.1.",null,"A review and update of short-circuit model data for the BES Elements under study.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28849,"PRC-027-1","R1.2.",null,"A review of the developed Protection System settings.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28850,"PRC-027-1","R1.3.",null,"For Protection System settings applied on BES Elements that electrically join Facilities owned by separate functional entities (Transmission Owners, Generator Owners, and Distribution Providers), provisions to:","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28851,"PRC-027-1","R1.3.1.",null,"Provide the proposed Protection System settings to the owner(s) of the electrically joined Facilities.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28852,"PRC-027-1","R1.3.2.",null,"Respond to any owner(s) that provided its proposed Protection System settings pursuant to Requirement R1, Part 1.3.1 by identifying any coordination issue(s) or affirming that no coordination issue(s) were identified.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28853,"PRC-027-1","R1.3.3.",null,"Verify that identified coordination issue(s) associated with the proposed Protection System settings for the associated BES Elements are addressed prior to implementation.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28854,"PRC-027-1","R1.3.4.",null,"Communicate with the other owner(s) of the electrically joined Facilities regarding revised Protection System settings resulting from unforeseen circumstances that arise during implementation or commissioning, Misoperation investigations, maintenance activities, or emergency replacements required as a result of Protection System component failure.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28855,"PRC-027-1","R2.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall, for each BES Element with Protection System functions identified in Attachment A: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]\n\n● Option 1: Perform a Protection System Coordination Study in a time interval not to exceed six-calendar years; or\n\n● Option 2: Compare present Fault current values to an established Fault current baseline and perform a Protection System Coordination Study when the comparison identifies a 15 percent or greater deviation in Fault current values (either three phase or phase to ground) at a bus to which the BES Element is connected, all in a time interval not to exceed six-calendar years;1 or,\n\n● Option 3: Use a combination of the above.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28856,"PRC-027-1","R3.",null,"Each Transmission Owner, Generator Owner, and Distribution Provider shall utilize its process established in Requirement R1 to develop new and revised Protection System settings for BES Elements. [Violation Risk Factor: High] [Time Horizon: Operations Planning]","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO, DP","Yes",false,null,false]
[28868,"TOP-001-2","R1.",null,"Each Balancing Authority, Generator Operator, Distribution Provider, and Load-Serving Entity shall comply with each Reliability Directive issued and identified as such by its Transmission Operator(s), unless such action would violate safety, equipment, regulatory, or statutory requirements.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, LSE, GOP, DP, BA","Yes",false,null,false]
[28878,"TOP-001-2","R10.",null,"Each Transmission Operator shall inform its Reliability Coordinator of its actions to return the system to within limits when an IROL, or an SOL identified in Requirement R8, has been exceeded.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC","No",false,null,false]
[28879,"TOP-001-2","R11.",null,"Each Transmission Operator shall act or direct others to act, to mitigate both the magnitude and duration of exceeding an IROL within the IROL’s Tv, or of an SOL identified in Requirement R8.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP","No",false,null,false]
[28869,"TOP-001-2","R2.",null,"Each Balancing Authority, Generator Operator, Distribution Provider, and Load-Serving Entity shall inform its Transmission Operator of its inability to perform an identified Reliability Directive issued by that Transmission Operator.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, LSE, GOP, DP, BA","Yes",false,null,false]
[28870,"TOP-001-2","R3.",null,"Each Transmission Operator shall inform its Reliability Coordinator and Transmission Operator(s) that are known or expected to be affected by each actual and anticipated Emergency based on its assessment of its Operational Planning Analysis.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, RC","No",false,null,false]
[28871,"TOP-001-2","R4.",null,"Each Transmission Operator shall render emergency assistance to other Transmission Operators, as requested and available, provided that the requesting entity has implemented its comparable emergency procedures, unless such actions would violate safety, equipment, regulatory, or statutory requirements.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A",null,"No",false,null,false]
[28872,"TOP-001-2","R5.",null,"Each Transmission Operator shall inform its Reliability Coordinator and other Transmission Operators of its operations known or expected to result in an Adverse Reliability Impact on those respective Transmission Operator Areas unless conditions do not permit such communications. Examples of such operations are relay or equipment failures, and changes in generation, Transmission, or Load.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, RC","No",false,null,false]
[28873,"TOP-001-2","R6.",null,"Each Balancing Authority and Transmission Operator shall notify its Reliability Coordinator and negatively impacted interconnected NERC registered entities of planned outages of telemetering equipment, control equipment and associated communication channels between\nthe affected entities.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",false,null,false]
[28874,"TOP-001-2","R7.",null,"Each Transmission Operator shall not operate outside any identified Interconnection Reliability\nOperating Limit (IROL) for a continuous duration exceeding its associated IROL Tv.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP","No",false,null,false]
[28875,"TOP-001-2","R7.1.",null,"For a generator outage, the Generator Operator shall notify and coordinate with the Transmission Operator.  The Transmission Operator shall notify the Reliability Coordinator and other affected Transmission Operators, and coordinate the impact of removing the Bulk Electric System facility.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, RC, GOP","Yes",false,null,false]
[28876,"TOP-001-2","R8.",null,"Each Transmission Operator shall inform its Reliability Coordinator of each SOL which, while not an IROL, has been identified by the Transmission Operator as supporting reliability internal to its Transmission Operator Area based on its assessment of its Operational Planning\nAnalysis.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC","No",false,null,false]
[28877,"TOP-001-2","R9.",null,"Each Transmission Operator shall not operate outside any System Operating Limit (SOL) identified in Requirement R8 for a continuous duration that would cause a violation of the Facility Rating or Stability criteria upon which it is based.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",false,null,false]
[28902,"TOP-001-4","R1.",null,"Each Transmission Operator shall act to maintain the reliability of its Transmission Operator Area via its own actions or by issuing Operating Instructions. [Violation Risk Factor: High][Time Horizon: Same-Day Operations, Real-time Operations]","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true,"Hydro One may perform Independent Action as per the IESO/Hydro One Operating Agreement"]
[28911,"TOP-001-4","R10.",null,"Each Transmission Operator shall perform the following for determining System Operating Limit (SOL) exceedances within its Transmission Operator Area: [Violation Risk Factor: High] [Time Horizon: Real-Time Operations]","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28912,"TOP-001-4","R10.1.",null,"Monitor Facilities within its Transmission Operator Area;","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28913,"TOP-001-4","R10.2.",null,"Monitor the status of Remedial Action Schemes within its Transmission Operator Area;","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28914,"TOP-001-4","R10.3.",null,"Monitor non-BES facilities within its Transmission Operator Area identified as necessary by the Transmission Operator;","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28915,"TOP-001-4","R10.4.",null,"Obtain and utilize status, voltages, and flow data for Facilities outside its Transmission Operator Area identified as necessary by the Transmission Operator;","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28916,"TOP-001-4","R10.5.",null,"Obtain and utilize the status of Remedial Action Schemes outside its Transmission Operator Area identified as necessary by the Transmission Operator; and","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28917,"TOP-001-4","R10.6.",null,"Obtain and utilize status, voltages, and flow data for non-BES facilities outside its Transmission Operator Area identified as necessary by the Transmission Operator.","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28918,"TOP-001-4","R11.",null,"Each Balancing Authority shall monitor its Balancing Authority Area, including the status of Remedial Action Schemes that impact generation or Load, in order to maintain generation-Load-interchange balance within its Balancing Authority Area and support Interconnection frequency. [Violation Risk Factor: High] [Time Horizon: Real-Time Operations]","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[28919,"TOP-001-4","R12.",null,"Each Transmission Operator shall not operate outside any identified Interconnection Reliability Operating Limit (IROL) for a continuous duration exceeding its associated IROL Tv. [Violation Risk Factor: High] [Time Horizon: Real-time Operations]","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28920,"TOP-001-4","R13.",null,"Each Transmission Operator shall ensure that a Real-time Assessment is performed at least once every 30 minutes. [Violation Risk Factor: High] [Time Horizon: Real-time Operations]","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28921,"TOP-001-4","R14.",null,"Each Transmission Operator shall initiate its Operating Plan to mitigate a SOL exceedance identified as part of its Real-time monitoring or Real-time Assessment. [Violation Risk Factor: High] [Time Horizon: Real-time Operations]","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28922,"TOP-001-4","R15.",null,"Each Transmission Operator shall inform its Reliability Coordinator of actions taken to return the System to within limits when a SOL has been exceeded. [Violation Risk Factor: Medium] [Time Horizon: Real-Time Operations]","2018-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true,"Hydro One may perform Independent Action as per the IESO/Hydro One Operating Agreement"]
[28923,"TOP-001-4","R16.",null,"Each Transmission Operator shall provide its System Operators with the authority to approve planned outages and maintenance of its telemetering and control equipment, monitoring and assessment capabilities, and associated communication channels between affected entities. [Violation Risk Factor: High] [Time Horizon: Operations Planning, Same-Day Operations, Real-time Operations]","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28924,"TOP-001-4","R17.",null,"Each Balancing Authority shall provide its System Operators with the authority to approve planned outages and maintenance of its telemetering and control equipment, monitoring and assessment capabilities, and associated communication channels between affected entities. [Violation Risk Factor: High] [Time Horizon: Operations Planning, Same-Day Operations, Real-time Operations]","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[28925,"TOP-001-4","R18.",null,"Each Transmission Operator shall operate to the most limiting parameter in instances where there is a difference in SOLs. [Violation Risk Factor: High] [Time Horizon: Operations Planning, Same-Day Operations, Real-time Operations]","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28926,"TOP-001-4","R19.",null,"Each Transmission Operator shall have data exchange capabilities with the entities it has identified it needs data from in order to perform its Operational Planning Analyses. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2018-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true]
[28903,"TOP-001-4","R2.",null,"Each Balancing Authority shall act to maintain the reliability of its Balancing Authority Area via its own actions or by issuing Operating Instructions. [Violation Risk Factor: High][Time Horizon: Same-Day Operations, Real-time Operations]","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[28927,"TOP-001-4","R20.",null,"Each Transmission Operator shall have data exchange capabilities, with redundant and diversely routed data exchange infrastructure within the Transmission Operator's primary Control Center, for the exchange of Real-time data with its Reliability Coordinator, Balancing Authority, and the entities it has identified it needs data from in order for it to perform its Real-time monitoring and Real-time Assessments. [Violation Risk Factor: High] [Time Horizon: Same-Day Operations, Real-time Operations]","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[28928,"TOP-001-4","R21.",null,"Each Transmission Operator shall test its primary Control Center data exchange capabilities specified in Requirement R20 for redundant functionality at least once every 90 calendar days. If the test is unsuccessful, the Transmission Operator shall initiate action within two hours to restore redundant functionality. [Violation Risk Factor: Medium ] [Time Horizon: Operations Planning]","2018-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true]
[28929,"TOP-001-4","R22.",null,"Each Balancing Authority shall have data exchange capabilities with the entities it has identified it needs data from in order to develop its Operating Plan for next-day operations. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2018-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[28930,"TOP-001-4","R23.",null,"Each Balancing Authority shall have data exchange capabilities, with redundant and diversely routed data exchange infrastructure within the Balancing Authority's primary Control Center, for the exchange of Real-time data with its Reliability Coordinator, Transmission Operator, and the entities it has identified it needs data from in order for it to perform its Real-time monitoring and analysis functions. [Violation Risk Factor: High] [Time Horizon: Same-Day Operations, Real-time Operations]","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[28931,"TOP-001-4","R24.",null,"Each Balancing Authority shall test its primary Control Center data exchange capabilities specified in Requirement R23 for redundant functionality at least once every 90 calendar days. If the test is unsuccessful, the Balancing Authority shall initiate action within two hours to restore redundant functionality. [Violation Risk Factor: Medium ] [Time Horizon: Operations Planning]","2018-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[28904,"TOP-001-4","R3.",null,"Each Balancing Authority, Generator Operator, and Distribution Provider shall comply with each Operating Instruction issued by its Transmission Operator(s), unless such action cannot be physically implemented or it would violate safety, equipment, regulatory, or statutory requirements. [Violation Risk Factor: High] [Time Horizon: Same-Day Operations, Real-Time Operations]","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GOP, DP, BA","Yes",false,null,false]
[28905,"TOP-001-4","R4.",null,"Each Balancing Authority, Generator Operator, and Distribution Provider shall inform its Transmission Operator of its inability to comply with an Operating Instruction issued by its Transmission Operator. [Violation Risk Factor: High] [Time Horizon: Same-Day Operations, Real-Time Operations]","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GOP, DP, BA","Yes",false,null,false]
[28906,"TOP-001-4","R5.",null,"Each Transmission Operator, Generator Operator, and Distribution Provider shall comply with each Operating Instruction issued by its Balancing Authority, unless such action cannot be physically implemented or it would violate safety, equipment, regulatory, or statutory requirements. [Violation Risk Factor: High] [Time Horizon: Same-Day Operations, Real-Time Operations]","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP","Yes",true,null,true]
[28907,"TOP-001-4","R6.",null,"Each Transmission Operator, Generator Operator, and Distribution Provider shall inform its Balancing Authority of its inability to comply with an Operating Instruction issued by its Balancing Authority. [Violation Risk Factor: High] [Time Horizon: Same-Day Operations, Real-Time Operations]","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP","Yes",true,null,true]
[28908,"TOP-001-4","R7.",null,"Each Transmission Operator shall assist other Transmission Operators within its Reliability Coordinator Area, if requested and able, provided that the requesting Transmission Operator has implemented its comparable Emergency procedures, unless such assistance cannot be physically implemented or would violate safety, equipment, regulatory, or statutory requirements. [Violation Risk Factor: High] [Time Horizon: Real-Time Operations]","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true,"\"H1 takes action under the direction of the IESO (MR. Ch. 5, S.3.4.1.5).              \nH1 will take independent action for safety, equipment, and environment (focus on H1's equipment) but must notify IESO ASAP (MR. Ch.5, S.1.2.3.)                                                    \n\""]
[28909,"TOP-001-4","R8.",null,"Each Transmission Operator shall inform its Reliability Coordinator, known impacted Balancing Authorities, and known impacted Transmission Operators of its actual or expected operations that result in, or could result in, an Emergency. [Violation Risk Factor: High] [Time Horizon: Operations Planning, Same-Day Operations, Real-Time Operations]","2018-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true,"Hydro One shall inform IESO only in its capacity as BA/RC"]
[28910,"TOP-001-4","R9.",null,"Each Balancing Authority and Transmission Operator shall notify its Reliability Coordinator and known impacted interconnected entities of all planned outages, and unplanned outages of 30 minutes or more, for telemetering and control equipment, monitoring and assessment capabilities, and associated communication channels between the affected entities. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning, Same-Day Operations, Real-Time Operations]","2018-10-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[30164,"TOP-001-5","R1.",null,"Each Transmission Operator shall act to maintain the reliability of its Transmission\r\nOperator Area via its own actions or by issuing Operating Instructions.  [Violation Risk\r\nFactor:  High][Time Horizon:  Same‐Day Operations, Real‐time Operations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GOP, DP, BA, TOP","Yes",false,null,false]
[30174,"TOP-001-5","R10.",null,"Each Transmission Operator shall perform the following for determining System\r\nOperating Limit (SOL) exceedances within its Transmission Operator Area: [Violation\r\nRisk Factor: High] [Time Horizon: Real‐Time Operations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30175,"TOP-001-5","R10.1.",null,"Monitor Facilities within its Transmission Operator Area;","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30176,"TOP-001-5","R10.2.",null,"Monitor the status of  Remedial Action Schemes within its Transmission\r\nOperator Area;","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30177,"TOP-001-5","R10.3.",null,"Monitor non‐BES facilities within its Transmission Operator Area identified as\r\nnecessary by the Transmission Operator;","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30178,"TOP-001-5","R10.4.",null,"Obtain and utilize status, voltages, and flow data for Facilities outside its\r\nTransmission Operator Area identified as necessary by the Transmission\r\nOperator;","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30179,"TOP-001-5","R10.5.",null,"Obtain and utilize the status of Remedial Action Schemes outside its\r\nTransmission Operator Area identified as necessary by the Transmission\r\nOperator; and","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30180,"TOP-001-5","R10.6.",null,"Obtain and utilize status, voltages, and flow data for non‐BES facilities outside\r\nits Transmission Operator Area identified as necessary by the Transmission\r\nOperator","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30181,"TOP-001-5","R11.",null,"Each Balancing Authority shall monitor its Balancing Authority Area, including the\r\nstatus of Remedial Action Schemes that impact generation or Load, in order to\r\nmaintain generation‐Load‐interchange balance within its Balancing Authority Area\r\nand support Interconnection frequency. [Violation Risk Factor: High] [Time Horizon:\r\nReal‐Time Operations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30182,"TOP-001-5","R12.",null,"Each Transmission Operator shall not operate outside any identified Interconnection\r\nReliability Operating Limit (IROL) for a continuous duration exceeding its associated\r\nIROL Tv.  [Violation Risk Factor: High] [Time Horizon: Real‐time Operations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30183,"TOP-001-5","R13.",null,". Each Transmission Operator shall ensure that a Real‐time Assessment is performed at\r\nleast once every 30 minutes. [Violation Risk Factor: High] [Time Horizon: Real‐time\r\nOperations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30184,"TOP-001-5","R14.",null,"Each Transmission Operator shall initiate its Operating Plan to mitigate a SOL\r\nexceedance identified as part of its Real‐time monitoring or Real‐time Assessment.\r\n[Violation Risk Factor: High] [Time Horizon: Real‐time Operations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30185,"TOP-001-5","R15.",null,"Each Transmission Operator shall inform its Reliability Coordinator of actions taken to\r\nreturn the System to within limits when a SOL has been exceeded.  [Violation Risk\r\nFactor: Medium] [Time Horizon: Real‐Time Operations]","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30186,"TOP-001-5","R16.",null,"Each Transmission Operator shall provide its System Operators with the authority to\r\napprove planned outages and maintenance of its telemetering and control\r\nequipment, monitoring and assessment capabilities, and associated communication\r\nchannels between affected entities. [Violation Risk Factor: High] [Time Horizon:\r\nOperations Planning, Same‐Day Operations, Real‐time Operations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30187,"TOP-001-5","R17.",null,"Each Balancing Authority shall provide its System Operators with the authority to\r\napprove planned outages and maintenance of its telemetering and control\r\nequipment, monitoring and assessment capabilities, and associated communication channels between affected entities. [Violation Risk Factor: High] [Time Horizon:\r\nOperations Planning, Same‐Day Operations, Real‐time Operations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30188,"TOP-001-5","R18.",null,"Each Transmission Operator shall operate to the most limiting parameter in instances\r\nwhere there is a difference in SOLs.  [Violation Risk Factor: High] [Time Horizon:\r\nOperations Planning, Same‐Day Operations, Real‐time Operations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30189,"TOP-001-5","R19.",null,"Reserved.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30165,"TOP-001-5","R2.",null,"Each Balancing Authority shall act to maintain the reliability of its Balancing Authority\r\nArea via its own actions or by issuing Operating Instructions.  [Violation Risk Factor:  \r\nHigh][Time Horizon:  Same‐Day Operations, Real‐time Operations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30190,"TOP-001-5","R20.",null,"Each Transmission Operator shall have data exchange capabilities, with redundant\r\nand diversely routed data exchange infrastructure within the Transmission Operator's\r\nprimary Control Center, for the exchange of Real‐time data with its Reliability\r\nCoordinator, Balancing Authority, and the entities it has identified it needs data from\r\nin order for it to perform its Real‐time monitoring and Real‐time Assessments.   \r\n[Violation Risk Factor: High] [Time Horizon: Same‐Day Operations, Real‐time\r\nOperations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30191,"TOP-001-5","R21.",null,"Each Transmission Operator shall test its primary Control Center data exchange\r\ncapabilities specified in Requirement R20 for redundant functionality at least once\r\nevery 90 calendar days. If the test is unsuccessful, the Transmission Operator shall\r\ninitiate action within two hours to restore redundant functionality. [Violation Risk\r\nFactor: Medium ] [Time Horizon: Operations Planning]","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30192,"TOP-001-5","R22.",null,"Reserved.","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30193,"TOP-001-5","R23.",null,"Each Balancing Authority shall have data exchange capabilities, with redundant and\r\ndiversely routed data exchange infrastructure within the Balancing Authority's\r\nprimary Control Center, for the exchange of Real‐time data with its Reliability\r\nCoordinator, Transmission Operator, and the entities it has identified it needs data\r\nfrom in order for it to perform its Real‐time monitoring and analysis functions.   \r\n[Violation Risk Factor: High] [Time Horizon: Same‐Day Operations, Real‐time\r\nOperations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30194,"TOP-001-5","R24.",null,"Each Balancing Authority shall test its primary Control Center data exchange\r\ncapabilities specified in Requirement R23 for redundant functionality at least once\r\nevery 90 calendar days. If the test is unsuccessful, the Balancing Authority shall\r\ninitiate action within two hours to restore redundant functionality. [Violation Risk\r\nFactor: Medium ] [Time Horizon: Operations Planning]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30166,"TOP-001-5","R3.",null,"Each Balancing Authority, Generator Operator, and Distribution Provider shall comply\r\nwith each Operating Instruction issued by its Transmission Operator(s), unless such\r\naction cannot be physically implemented or it would violate safety, equipment,\r\nregulatory, or statutory requirements.  [Violation Risk Factor: High] [Time Horizon:  \r\nSame‐Day Operations, Real‐Time Operations]\r\nrecipient shall sign the NERC Confidentiality Agreement for “Electric System Reliability\r\nData.”","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30167,"TOP-001-5","R4.",null,"Each Balancing Authority, Generator Operator, and Distribution Provider shall inform\r\nits Transmission Operator of its inability to comply with an Operating Instruction\r\nissued by its Transmission Operator. [Violation Risk Factor: High] [Time Horizon:\r\nSame‐Day Operations, Real‐Time Operations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30168,"TOP-001-5","R5.",null,"Each Transmission Operator, Generator Operator, and Distribution Provider shall\r\ncomply with each Operating Instruction issued by its Balancing Authority, unless such\r\naction cannot be physically implemented or it would violate safety, equipment,\r\nregulatory, or statutory requirements.  [Violation Risk Factor: High] [Time Horizon:  \r\nSame‐Day Operations, Real‐Time Operations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30169,"TOP-001-5","R6.",null,"Each Transmission Operator, Generator Operator, and Distribution Provider shall inform its Balancing Authority of its inability to comply with an Operating Instruction issued by its Balancing Authority. [Violation Risk Factor: High] [Time Horizon: Same‐ Day Operations, Real‐Time Operations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30171,"TOP-001-5","R7.",null,"Each Transmission Operator shall assist other Transmission Operators within its\r\nReliability Coordinator Area, if requested and able, provided that the requesting\r\nTransmission Operator has implemented its comparable Emergency procedures,\r\nunless such assistance cannot be physically implemented or would violate safety,\r\nequipment, regulatory, or statutory requirements. [Violation Risk Factor: High] [Time\r\nHorizon: Real‐Time Operations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30172,"TOP-001-5","R8.",null,"Each Transmission Operator shall inform its Reliability Coordinator, known impacted\r\nBalancing Authorities, and known impacted Transmission Operators of its actual or\r\nexpected operations that result in, or could result in, an Emergency.     [Violation Risk\r\nFactor: High] [Time Horizon:  Operations Planning, Same‐Day Operations, Real‐Time\r\nOperations]","2021-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30173,"TOP-001-5","R9.",null,"Each Balancing Authority and Transmission Operator shall notify its Reliability\r\nCoordinator and known impacted interconnected entities of all planned outages, and\r\nunplanned outages of 30 minutes or more, for telemetering and control equipment,\r\nmonitoring and assessment capabilities, and associated communication channels\r\nbetween the affected entities.  [Violation Risk Factor: Medium] [Time Horizon:\r\nOperations Planning, Same‐Day Operations, Real‐Time Operations]","2021-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30699,"TOP-001-6","R1.",null,"Each Transmission Operator shall act to maintain the reliability of its Transmission\nOperator Area via its own actions or by issuing Operating Instructions.  [Violation Risk\nFactor:  High][Time Horizon:  Same‐Day Operations, Real‐time Operations]","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30700,"TOP-001-6","R10.",null,"Each Transmission Operator shall perform the following for determining System\nOperating Limit (SOL) exceedances within its Transmission Operator Area: [Violation\nRisk Factor: High] [Time Horizon: Real‐Time Operations]","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30701,"TOP-001-6","R10.1.",null,"Monitor Facilities within its Transmission Operator Area;","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30702,"TOP-001-6","R10.2.",null,"Monitor the status of  Remedial Action Schemes within its Transmission\nOperator Area;","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30703,"TOP-001-6","R10.3.",null,"Monitor non‐BES facilities within its Transmission Operator Area identified as\nnecessary by the Transmission Operator;","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30704,"TOP-001-6","R10.4.",null,"Obtain and utilize status, voltages, and flow data for Facilities outside its\nTransmission Operator Area identified as necessary by the Transmission\nOperator;","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30705,"TOP-001-6","R10.5.",null,"Obtain and utilize the status of Remedial Action Schemes outside its\nTransmission Operator Area identified as necessary by the Transmission\nOperator; and","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30706,"TOP-001-6","R10.6.",null,"Obtain and utilize status, voltages, and flow data for non‐BES facilities outside\nits Transmission Operator Area identified as necessary by the Transmission\nOperator","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30707,"TOP-001-6","R11.",null,"Each Balancing Authority shall monitor its Balancing Authority Area, including the\nstatus of Remedial Action Schemes that impact generation or Load, in order to\nmaintain generation‐Load‐interchange balance within its Balancing Authority Area\nand support I","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30708,"TOP-001-6","R12.",null,"Each Transmission Operator shall not operate outside any identified Interconnection\nReliability Operating Limit (IROL) for a continuous duration exceeding its associated\nIROL Tv.  [Violation Risk Factor: High] [Time Horizon: Real‐time Operations]","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30709,"TOP-001-6","R13.",null,". Each Transmission Operator shall ensure that a Real‐time Assessment is performed at\nleast once every 30 minutes. [Violation Risk Factor: High] [Time Horizon: Real‐time\nOperations]","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30710,"TOP-001-6","R14.",null,"Each Transmission Operator shall initiate its Operating Plan to mitigate a SOL\nexceedance identified as part of its Real‐time monitoring or Real‐time Assessment.\n[Violation Risk Factor: High] [Time Horizon: Real‐time Operations]","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30711,"TOP-001-6","R15.",null,"Each Transmission Operator shall inform its Reliability Coordinator of actions taken toreturn the System to within limits when a SOL has been exceeded in accordance with its Reliability Coordinator’s SOL methodology.  [Violation Risk Factor: Medium] [Time","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30712,"TOP-001-6","R16.",null,"Each Transmission Operator shall provide its System Operators with the authority to\napprove planned outages and maintenance of its telemetering and control\nequipment, monitoring and assessment capabilities, and associated communication\nchannels between af","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30713,"TOP-001-6","R17.",null,"Each Balancing Authority shall provide its System Operators with the authority to\napprove planned outages and maintenance of its telemetering and control\nequipment, monitoring and assessment capabilities, and associated communication channels between affe","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30714,"TOP-001-6","R18.",null,"Each Transmission Operator shall operate to the most limiting parameter in instances\nwhere there is a difference in SOLs.  [Violation Risk Factor: High] [Time Horizon:\nOperations Planning, Same‐Day Operations, Real‐time Operations]","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30715,"TOP-001-6","R19.",null,"Reserved.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30716,"TOP-001-6","R2.",null,"Each Balancing Authority shall act to maintain the reliability of its Balancing Authority\nArea via its own actions or by issuing Operating Instructions.  [Violation Risk Factor:  \nHigh][Time Horizon:  Same‐Day Operations, Real‐time Operations]","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30717,"TOP-001-6","R20.",null,"Each Transmission Operator shall have data exchange capabilities, with redundant\nand diversely routed data exchange infrastructure within the Transmission Operator's\nprimary Control Center, for the exchange of Real‐time data with its Reliability\nCoordinat","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30718,"TOP-001-6","R21.",null,"Each Transmission Operator shall test its primary Control Center data exchange\ncapabilities specified in Requirement R20 for redundant functionality at least once\nevery 90 calendar days. If the test is unsuccessful, the Transmission Operator shall\ninitiat","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30719,"TOP-001-6","R22.",null,"Reserved.","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30720,"TOP-001-6","R23.",null,"Each Balancing Authority shall have data exchange capabilities, with redundant and\ndiversely routed data exchange infrastructure within the Balancing Authority's\nprimary Control Center, for the exchange of Real‐time data with its Reliability\nCoordinator,","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30721,"TOP-001-6","R24.",null,"Each Balancing Authority shall test its primary Control Center data exchange\ncapabilities specified in Requirement R23 for redundant functionality at least once\nevery 90 calendar days. If the test is unsuccessful, the Balancing Authority shall\ninitiate ac","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30729,"TOP-001-6","R25.",null,"Each Transmission Operator shall use the applicable Reliability Coordinator’s SOL methodology when determining SOL exceedances for Real-time Assessments, Real time monitoring, and Operational Planning Analysis. [Violation Risk Factor: High ] [Time Horizon","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30722,"TOP-001-6","R3.",null,"Each Balancing Authority, Generator Operator, and Distribution Provider shall comply\nwith each Operating Instruction issued by its Transmission Operator(s), unless such\naction cannot be physically implemented or it would violate safety, equipment,\nregulat","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30723,"TOP-001-6","R4.",null,"Each Balancing Authority, Generator Operator, and Distribution Provider shall inform\nits Transmission Operator of its inability to comply with an Operating Instruction\nissued by its Transmission Operator. [Violation Risk Factor: High] [Time Horizon:\nSame‐","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30724,"TOP-001-6","R5.",null,"Each Transmission Operator, Generator Operator, and Distribution Provider shall\ncomply with each Operating Instruction issued by its Balancing Authority, unless such\naction cannot be physically implemented or it would violate safety, equipment,\nregulatory","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30725,"TOP-001-6","R6.",null,"Each Transmission Operator, Generator Operator, and Distribution Provider shall inform its Balancing Authority of its inability to comply with an Operating Instruction issued by its Balancing Authority. [Violation Risk Factor: High] [Time Horizon: Same‐ D","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30726,"TOP-001-6","R7.",null,"Each Transmission Operator shall assist other Transmission Operators within its\nReliability Coordinator Area, if requested and able, provided that the requesting\nTransmission Operator has implemented its comparable Emergency procedures,\nunless such assist","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30727,"TOP-001-6","R8.",null,"Each Transmission Operator shall inform its Reliability Coordinator, known impacted\nBalancing Authorities, and known impacted Transmission Operators of its actual or\nexpected operations that result in, or could result in, an Emergency.     [Violation Risk","2024-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[30728,"TOP-001-6","R9.",null,"Each Balancing Authority and Transmission Operator shall notify its Reliability\nCoordinator and known impacted interconnected entities of all planned outages, and\nunplanned outages of 30 minutes or more, for telemetering and control equipment,\nmonitoring","2024-04-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, GOP, DP, BA","Yes",false,null,false]
[28976,"TOP-002-3","R1.",null,"Each Transmission Operator shall have an Operational Planning Analysis that represents projected System conditions that will allow it to assess whether the planned operations for the next day within its Transmission Operator Area will exceed any of its Facility Ratings or Stability Limits during anticipated normal and Contingency event conditions.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",false,null,false]
[28977,"TOP-002-3","R2.",null,"Each Transmission Operator shall develop a plan to operate within each Interconnection Reliability Operating Limit (IROL) and each System Operating Limit (SOL) which, while not an IROL, has been identified by the Transmission Operator as supporting reliability internal to its Transmission Operator Area, identified as a result of the Operational Planning Analysis performed in Requirement R1.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",false,null,false]
[28978,"TOP-002-3","R3.",null,"Each Transmission Operator shall notify all NERC registered entities identified in the plan(s) cited in Requirement R2 as to their role in those plan(s).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",false,null,false]
[28979,"TOP-002-4","R1.","YES","Each Transmission Operator shall have an Operational Planning Analysis that will allow it to assess whether its planned operations for the next day within its Transmission Operator Area will exceed any of its System Operating Limits (SOLs). [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28980,"TOP-002-4","R1.","YES","Each Transmission Operator shall have an Operational Planning Analysis that will allow it to assess whether its planned operations for the next day within its Transmission Operator Area will exceed any of its System Operating Limits (SOLs). [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28981,"TOP-002-4","R2.","YES","Each Transmission Operator shall have an Operating Plan(s) for next-day operations to address potential System Operating Limit (SOL) exceedances identified as a result of its Operational Planning Analysis as required in Requirement R1. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28982,"TOP-002-4","R2.","YES","Each Transmission Operator shall have an Operating Plan(s) for next-day operations to address potential System Operating Limit (SOL) exceedances identified as a result of its Operational Planning Analysis as required in Requirement R1. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28983,"TOP-002-4","R3.","YES","Each Transmission Operator shall notify entities identified in the Operating Plan(s) cited in Requirement R2 as to their role in those plan(s). [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28984,"TOP-002-4","R3.","YES","Each Transmission Operator shall notify entities identified in the Operating Plan(s) cited in Requirement R2 as to their role in those plan(s). [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28985,"TOP-002-4","R4.",null,"Each Balancing Authority shall have an Operating Plan(s) for the next-day that addresses: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[28986,"TOP-002-4","R4.1.",null,"Expected generation resource commitment and dispatch","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[28987,"TOP-002-4","R4.2.",null,"Interchange scheduling","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[28988,"TOP-002-4","R4.3.",null,"Demand patterns","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[28989,"TOP-002-4","R4.4.",null,"Capacity and energy reserve requirements, including deliverability capability","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[28991,"TOP-002-4","R5.","YES","Each Balancing Authority shall notify entities identified in the Operating Plan(s) cited in Requirement R4 as to their role in those plan(s). [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[28990,"TOP-002-4","R5.","YES","Each Balancing Authority shall notify entities identified in the Operating Plan(s) cited in Requirement R4 as to their role in those plan(s). [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[28992,"TOP-002-4","R6.","YES","Each Transmission Operator shall provide its Operating Plan(s) for next-day operations identified in Requirement R2 to its Reliability Coordinator. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28993,"TOP-002-4","R6.","YES","Each Transmission Operator shall provide its Operating Plan(s) for next-day operations identified in Requirement R2 to its Reliability Coordinator. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[28994,"TOP-002-4","R7.","YES","Each Balancing Authority shall provide its Operating Plan(s) for next-day operations identified in Requirement R4 to its Reliability Coordinator. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[28995,"TOP-002-4","R7.","YES","Each Balancing Authority shall provide its Operating Plan(s) for next-day operations identified in Requirement R4 to its Reliability Coordinator. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2017-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","BA","No",false,null,false]
[29003,"TOP-003-2","R1.","YES","Each Transmission Operator shall create a documented specification for the data necessary for it to perform its Operational Planning Analyses and Real-time monitoring. The specification shall include:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29004,"TOP-003-2","R1.","YES","Each Transmission Operator shall create a documented specification for the data necessary for it to perform its Operational Planning Analyses and Real-time monitoring. The specification shall include:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29005,"TOP-003-2","R1.1.","YES","A list of data and information needed by the Transmission Operator to support its Operational Planning Analyses and Real-time monitoring.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29006,"TOP-003-2","R1.1.","YES","A list of data and information needed by the Transmission Operator to support its Operational Planning Analyses and Real-time monitoring.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29008,"TOP-003-2","R1.2.","YES","A mutually-agreeable format.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29007,"TOP-003-2","R1.2.","YES","A mutually-agreeable format.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29009,"TOP-003-2","R1.3.","YES","A periodicity for providing data.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29010,"TOP-003-2","R1.3.","YES","A periodicity for providing data.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29011,"TOP-003-2","R1.4.","YES","The deadline by which the respondent is to provide the indicated data.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29012,"TOP-003-2","R1.4.","YES","The deadline by which the respondent is to provide the indicated data.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29013,"TOP-003-2","R2.","YES","Each Balancing Authority shall create a documented specification for the data necessary for it to perform its analysis functions and Real-time monitoring. The specification shall include:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[29014,"TOP-003-2","R2.","YES","Each Balancing Authority shall create a documented specification for the data necessary for it to perform its analysis functions and Real-time monitoring. The specification shall include:",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[29015,"TOP-003-2","R2.1.","YES","A list of data and information needed by the Balancing Authority to support its analysis functions and Real-time monitoring.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[29016,"TOP-003-2","R2.1.","YES","A list of data and information needed by the Balancing Authority to support its analysis functions and Real-time monitoring.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[29018,"TOP-003-2","R2.2.","YES","A mutually-agreeable format.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[29017,"TOP-003-2","R2.2.","YES","A mutually-agreeable format.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[29020,"TOP-003-2","R2.3.","YES","A periodicity for providing data.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[29019,"TOP-003-2","R2.3.","YES","A periodicity for providing data.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[29021,"TOP-003-2","R2.4.","YES","The deadline by which the respondent is to provide the indicated data.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[29022,"TOP-003-2","R2.4.","YES","The deadline by which the respondent is to provide the indicated data.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[29023,"TOP-003-2","R3.","YES","Each Transmission Operator shall distribute its data specification, as developed in Requirement R1,to entities that have data required by the Transmission Operator’s Operational Planning Analysis and Real-time monitoring process used in meeting its NERC-mandated reliability requirements.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29024,"TOP-003-2","R3.","YES","Each Transmission Operator shall distribute its data specification, as developed in Requirement R1,to entities that have data required by the Transmission Operator’s Operational Planning Analysis and Real-time monitoring process used in meeting its NERC-mandated reliability requirements.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29026,"TOP-003-2","R4.","YES","Each Balancing Authority shall distribute its data specification, as developed in Requirement R2, to entities that have data required by the Balancing Authority’s analysis functions and Real-time monitoring process used in meeting its NERC-mandated reliability requirements.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[29025,"TOP-003-2","R4.","YES","Each Balancing Authority shall distribute its data specification, as developed in Requirement R2, to entities that have data required by the Balancing Authority’s analysis functions and Real-time monitoring process used in meeting its NERC-mandated reliability requirements.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[29027,"TOP-003-2","R5.","YES","Each Transmission Operator, Balancing Authority, Generator Owner, Generator Operator, Interchange Authority, Load-Serving Entity, Transmission Owner, and Distribution Provider receiving a data specification in Requirement R3 or R4 shall satisfy the obligations of the documented specifications for data.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, LSE, IA, GOP, GO, DP, BA","Yes",true,null,false]
[29028,"TOP-003-2","R5.","YES","Each Transmission Operator, Balancing Authority, Generator Owner, Generator Operator, Interchange Authority, Load-Serving Entity, Transmission Owner, and Distribution Provider receiving a data specification in Requirement R3 or R4 shall satisfy the obligations of the documented specifications for data.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, LSE, IA, GOP, GO, DP, BA","Yes",true,null,false]
[29029,"TOP-003-3","R1.","YES","Each Transmission Operator shall maintain a documented specification for the data necessary for it to perform its Operational Planning Analyses, Real-time monitoring, and Real-time Assessments. The data specification shall include, but not be limited to: [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,true,"For Real Time Monitoring only"]
[29030,"TOP-003-3","R1.","YES","Each Transmission Operator shall maintain a documented specification for the data necessary for it to perform its Operational Planning Analyses, Real-time monitoring, and Real-time Assessments. The data specification shall include, but not be limited to: [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,true,"For Real Time Monitoring only"]
[27934,"TOP-003-3","R1.1.","YES","A list of data and information needed by the Transmission Operator to support its Operational Planning Analyses, Real-time monitoring, and Realtime Assessments including non-BES data and external network data as deemed necessary by the Transmission Operator.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,true]
[27933,"TOP-003-3","R1.1.","YES","A list of data and information needed by the Transmission Operator to support its Operational Planning Analyses, Real-time monitoring, and Realtime Assessments including non-BES data and external network data as deemed necessary by the Transmission Operator.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,true]
[27936,"TOP-003-3","R1.2.","YES","Provisions for notification of current Protection System and Special Protection System status or degradation that impacts System reliability.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,true]
[27935,"TOP-003-3","R1.2.","YES","Provisions for notification of current Protection System and Special Protection System status or degradation that impacts System reliability.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,true]
[27937,"TOP-003-3","R1.3.","YES","A periodicity for providing data.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,true]
[27938,"TOP-003-3","R1.3.","YES","A periodicity for providing data.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,true]
[27940,"TOP-003-3","R1.4.","YES","The deadline by which the respondent is to provide the indicated data.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,true]
[27939,"TOP-003-3","R1.4.","YES","The deadline by which the respondent is to provide the indicated data.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,true]
[27942,"TOP-003-3","R2.","YES","Each Balancing Authority shall maintain a documented specification for the data necessary for it to perform its analysis functions and Real-time monitoring. The data specification shall include, but not be limited to: [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[27941,"TOP-003-3","R2.","YES","Each Balancing Authority shall maintain a documented specification for the data necessary for it to perform its analysis functions and Real-time monitoring. The data specification shall include, but not be limited to: [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[27943,"TOP-003-3","R2.1.","YES","A list of data and information needed by the Balancing Authority to support its analysis functions and Real-time monitoring.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[27944,"TOP-003-3","R2.1.","YES","A list of data and information needed by the Balancing Authority to support its analysis functions and Real-time monitoring.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[27946,"TOP-003-3","R2.2.","YES","Provisions for notification of current Protection System and Special Protection System status or degradation that impacts System reliability.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[27945,"TOP-003-3","R2.2.","YES","Provisions for notification of current Protection System and Special Protection System status or degradation that impacts System reliability.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[29031,"TOP-003-3","R2.3.","YES","A periodicity for providing data.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[29032,"TOP-003-3","R2.3.","YES","A periodicity for providing data.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[29033,"TOP-003-3","R2.4.","YES","The deadline by which the respondent is to provide the indicated data.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[29034,"TOP-003-3","R2.4.","YES","The deadline by which the respondent is to provide the indicated data.","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[29036,"TOP-003-3","R3.","YES","Each Transmission Operator shall distribute its data specification to entities that have data required by the Transmission Operator’s Operational Planning Analyses, Realtime monitoring, and Real-time Assessment. [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,true,"For Real Time Monitoring only"]
[29035,"TOP-003-3","R3.","YES","Each Transmission Operator shall distribute its data specification to entities that have data required by the Transmission Operator’s Operational Planning Analyses, Realtime monitoring, and Real-time Assessment. [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,true,"For Real Time Monitoring only"]
[29038,"TOP-003-3","R4.","YES","Each Balancing Authority shall distribute its data specification to entities that have data required by the Balancing Authority’s analysis functions and Real-time monitoring. [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[29037,"TOP-003-3","R4.","YES","Each Balancing Authority shall distribute its data specification to entities that have data required by the Balancing Authority’s analysis functions and Real-time monitoring. [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2017-01-01","2021-03-31","Retired",null,"LOWER",null,"N/A",null,"N/A","BA","No",false,null,false]
[29039,"TOP-003-3","R5.","YES","Each Transmission Operator, Balancing Authority, Generator Owner, Generator Operator, Load-Serving Entity, Transmission Owner, and Distribution Provider receiving a data specification in Requirement R3 or R4 shall satisfy the obligations of the documented specifications using: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning, Same-Day Operations, Real-time Operations]","2017-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[29040,"TOP-003-3","R5.","YES","Each Transmission Operator, Balancing Authority, Generator Owner, Generator Operator, Load-Serving Entity, Transmission Owner, and Distribution Provider receiving a data specification in Requirement R3 or R4 shall satisfy the obligations of the documented specifications using: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning, Same-Day Operations, Real-time Operations]","2017-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[29041,"TOP-003-3","R5.1.","YES","A mutually agreeable format","2017-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[29042,"TOP-003-3","R5.1.","YES","A mutually agreeable format","2017-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[29044,"TOP-003-3","R5.2.","YES","A mutually agreeable process for resolving data conflicts","2017-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[29043,"TOP-003-3","R5.2.","YES","A mutually agreeable process for resolving data conflicts","2017-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[29046,"TOP-003-3","R5.3.","YES","A mutually agreeable security protocol","2017-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[29045,"TOP-003-3","R5.3.","YES","A mutually agreeable security protocol","2017-04-01","2021-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP, TO, LSE, GOP, GO, DP, BA","Yes",true,null,true]
[30051,"TOP-003-4","R1.","YES","Each Transmission Operator shall maintain a documented specification for the data necessary for it to perform its Operational Planning Analyses, Real-time monitoring, and Real-time Assessments. The data specification shall include, but not be limited to: [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false,"For Real Time Monitoring Only"]
[30050,"TOP-003-4","R1.","YES","Each Transmission Operator shall maintain a documented specification for the data necessary for it to perform its Operational Planning Analyses, Real-time monitoring, and Real-time Assessments. The data specification shall include, but not be limited to: [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false,"For Real Time Monitoring Only"]
[30052,"TOP-003-4","R1.1.","YES","A list of data and information needed by the Transmission Operator to support its Operational Planning Analyses, Real-time monitoring, and Real-time Assessments including non-BES data and external network data as deemed necessary by the Transmission Operator.","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30053,"TOP-003-4","R1.1.","YES","A list of data and information needed by the Transmission Operator to support its Operational Planning Analyses, Real-time monitoring, and Real-time Assessments including non-BES data and external network data as deemed necessary by the Transmission Operator.","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30054,"TOP-003-4","R1.2.","YES","Provisions for notification of current Protection System and Special Protection System status or degradation that impacts System reliability.","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30055,"TOP-003-4","R1.2.","YES","Provisions for notification of current Protection System and Special Protection System status or degradation that impacts System reliability.","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30056,"TOP-003-4","R1.3.","YES","A periodicity for providing data.","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30057,"TOP-003-4","R1.3.","YES","A periodicity for providing data.","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30059,"TOP-003-4","R1.4.","YES","The deadline by which the respondent is to provide the indicated data.","2021-04-01","2023-09-30","Effective","Tools and Applications; TOP","LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30058,"TOP-003-4","R1.4.","YES","The deadline by which the respondent is to provide the indicated data.","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30061,"TOP-003-4","R2.","YES","Each Balancing Authority shall maintain a documented specification for the data necessary for it to perform its analysis functions and Real-time monitoring. The data specification shall include, but not be limited to: [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30060,"TOP-003-4","R2.","YES","Each Balancing Authority shall maintain a documented specification for the data necessary for it to perform its analysis functions and Real-time monitoring. The data specification shall include, but not be limited to: [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30062,"TOP-003-4","R2.1.","YES","A list of data and information needed by the Balancing Authority to support its analysis functions and Real-time monitoring.","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30063,"TOP-003-4","R2.1.","YES","A list of data and information needed by the Balancing Authority to support its analysis functions and Real-time monitoring.","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30064,"TOP-003-4","R2.2.","YES","Provisions for notification of current Protection System and Special Protection System status or degradation that impacts System reliability.","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30065,"TOP-003-4","R2.2.","YES","Provisions for notification of current Protection System and Special Protection System status or degradation that impacts System reliability.","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30066,"TOP-003-4","R2.3.","YES","A periodicity for providing data.","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30067,"TOP-003-4","R2.3.","YES","A periodicity for providing data.","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30068,"TOP-003-4","R2.4.","YES","The deadline by which the respondent is to provide the indicated data.","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30069,"TOP-003-4","R2.4.","YES","The deadline by which the respondent is to provide the indicated data.","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30071,"TOP-003-4","R3.","YES","Each Transmission Operator shall distribute its data specification to entities that have data required by the Transmission Operator’s Operational Planning Analyses, Real-time monitoring, and Real-time Assessment. [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false,"For Real Time Monitoring Only"]
[30070,"TOP-003-4","R3.","YES","Each Transmission Operator shall distribute its data specification to entities that have data required by the Transmission Operator’s Operational Planning Analyses, Real-time monitoring, and Real-time Assessment. [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false,"For Real Time Monitoring Only"]
[30073,"TOP-003-4","R4.","YES","Each Balancing Authority shall distribute its data specification to entities that have data required by the Balancing Authority’s analysis functions and Real-time monitoring. [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30072,"TOP-003-4","R4.","YES","Each Balancing Authority shall distribute its data specification to entities that have data required by the Balancing Authority’s analysis functions and Real-time monitoring. [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2021-04-01","2023-09-30","Effective",null,"LOWER",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30075,"TOP-003-4","R5.","YES","Each Transmission Operator, Balancing Authority, Generator Owner, Generator Operator, Transmission Owner, and Distribution Provider receiving a data specification in Requirement R3 or R4 shall satisfy the obligations of the documented specifications using: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning, Same-Day Operations, Real-time Operations]","2021-04-01","2023-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30074,"TOP-003-4","R5.","YES","Each Transmission Operator, Balancing Authority, Generator Owner, Generator Operator, Transmission Owner, and Distribution Provider receiving a data specification in Requirement R3 or R4 shall satisfy the obligations of the documented specifications using: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning, Same-Day Operations, Real-time Operations]","2021-04-01","2023-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30077,"TOP-003-4","R5.1.","YES","A mutually agreeable format","2021-04-01","2023-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30076,"TOP-003-4","R5.1.","YES","A mutually agreeable format","2021-04-01","2023-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30078,"TOP-003-4","R5.2.","YES","A mutually agreeable process for resolving data conflicts","2021-04-01","2023-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30079,"TOP-003-4","R5.2.","YES","A mutually agreeable process for resolving data conflicts","2021-04-01","2023-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30080,"TOP-003-4","R5.3.","YES","A mutually agreeable process for resolving data conflicts","2021-04-01","2023-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30081,"TOP-003-4","R5.3.","YES","A mutually agreeable process for resolving data conflicts","2021-04-01","2023-09-30","Effective",null,"MEDIUM",null,"N/A",null,"N/A","DP, GOP, GO, BA, TOP, TO","Yes",false,null,false]
[30426,"TOP-003-5","R1.","YES","Each Transmission Operator shall maintain a documented specification for the data necessary for it to perform its Operational Planning Analyses, Real-time monitoring, and Real-time Assessments. The data specification shall include, but not be limited to: [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false,"For Real Time Monitoring Only"]
[30427,"TOP-003-5","R1.","YES","Each Transmission Operator shall maintain a documented specification for the data necessary for it to perform its Operational Planning Analyses, Real-time monitoring, and Real-time Assessments. The data specification shall include, but not be limited to: [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false,"For Real Time Monitoring Only"]
[30428,"TOP-003-5","R1.1.","YES","A list of data and information needed by the Transmission Operator to support its Operational Planning Analyses, Real-time monitoring, and Real-time Assessments including non-BES data and external network data as deemed necessary by the Transmission Operator.","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30429,"TOP-003-5","R1.1.","YES","A list of data and information needed by the Transmission Operator to support its Operational Planning Analyses, Real-time monitoring, and Real-time Assessments including non-BES data and external network data as deemed necessary by the Transmission Operator.","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30430,"TOP-003-5","R1.2.","YES","Provisions for notification of current Protection System and Remedial Action Scheme (RAS) status or degradation that impacts System reliability.","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30431,"TOP-003-5","R1.2.","YES","Provisions for notification of current Protection System and Remedial Action Scheme (RAS) status or degradation that impacts System reliability.","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30432,"TOP-003-5","R1.3.","YES","Provisions for notification of BES generating unit(s)during local forecasted cold weather to include","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30433,"TOP-003-5","R1.3.","YES","Provisions for notification of BES generating unit(s)during local forecasted cold weather to include","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30448,"TOP-003-5","R1.3.","YES","A periodicity for providing data.","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30435,"TOP-003-5","R1.3.1.","YES","Operating limitations based on:","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30434,"TOP-003-5","R1.3.1.","YES","Operating limitations based on:","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30437,"TOP-003-5","R1.3.1.1.","YES","capability and availability;","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30436,"TOP-003-5","R1.3.1.1.","YES","capability and availability;","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30438,"TOP-003-5","R1.3.1.2.","YES","fuel supply and inventory concerns;","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30440,"TOP-003-5","R1.3.1.3.","YES","fuel switching capabilities; and","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30439,"TOP-003-5","R1.3.1.3.","YES","fuel switching capabilities; and","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30441,"TOP-003-5","R1.3.1.4.","YES","environmental constraints","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30450,"TOP-003-5","R1.4.","YES","The deadline by which the respondent is to provide the indicated data.","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30449,"TOP-003-5","R1.4.","YES","The deadline by which the respondent is to provide the indicated data.","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30451,"TOP-003-5","R2.","YES","Each Balancing Authority shall maintain a documented specification for the data necessary for it to perform its analysis functions and Real-time monitoring. The data specification shall include, but not be limited to: [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30452,"TOP-003-5","R2.","YES","Each Balancing Authority shall maintain a documented specification for the data necessary for it to perform its analysis functions and Real-time monitoring. The data specification shall include, but not be limited to: [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30453,"TOP-003-5","R2.1.","YES","A list of data and information needed by the Balancing Authority to support its analysis functions and Real-time monitoring.","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30454,"TOP-003-5","R2.1.","YES","A list of data and information needed by the Balancing Authority to support its analysis functions and Real-time monitoring.","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30455,"TOP-003-5","R2.2.","YES","Provisions for notification of current Protection System and Remedial Action Scheme status or degradation that impacts System reliability.","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30456,"TOP-003-5","R2.2.","YES","Provisions for notification of current Protection System and Remedial Action Scheme status or degradation that impacts System reliability.","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30457,"TOP-003-5","R2.3.","YES","Provisions for notification of BES generating unit(s) status during local forecasted cold weather to include:","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30458,"TOP-003-5","R2.3.","YES","Provisions for notification of BES generating unit(s) status during local forecasted cold weather to include:","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30460,"TOP-003-5","R2.3.1.","YES","Operating limitations based on:","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30459,"TOP-003-5","R2.3.1.","YES","Operating limitations based on:","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30462,"TOP-003-5","R2.3.1.1.","YES","capability and availability;","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30461,"TOP-003-5","R2.3.1.1.","YES","capability and availability;","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30463,"TOP-003-5","R2.3.1.2.","YES","fuel supply and inventory concerns;","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30464,"TOP-003-5","R2.3.1.2.","YES","fuel supply and inventory concerns;","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30465,"TOP-003-5","R2.3.1.3.","YES","fuel switching capabilities; and","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30466,"TOP-003-5","R2.3.1.3.","YES","fuel switching capabilities; and","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30468,"TOP-003-5","R2.3.1.4.","YES","environmental constraints.","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30467,"TOP-003-5","R2.3.1.4.","YES","environmental constraints.","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30472,"TOP-003-5","R2.3.2.1.","YES","design temperature; or","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30471,"TOP-003-5","R2.3.2.1.","YES","design temperature; or","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30474,"TOP-003-5","R2.3.2.2.","YES","historical operating temperature; or","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30473,"TOP-003-5","R2.3.2.2.","YES","historical operating temperature; or","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30475,"TOP-003-5","R2.3.2.3.","YES","current cold weather performance temperature determined by an engineering analysis.","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30476,"TOP-003-5","R2.3.2.3.","YES","current cold weather performance temperature determined by an engineering analysis.","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30477,"TOP-003-5","R2.4.","YES","A periodicity for providing data.","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30478,"TOP-003-5","R2.4.","YES","A periodicity for providing data.","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30479,"TOP-003-5","R2.5.","YES","The deadline by which the respondent is to provide the indicated data.","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30480,"TOP-003-5","R2.5.","YES","The deadline by which the respondent is to provide the indicated data.","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30482,"TOP-003-5","R3.","YES","Each Transmission Operator shall distribute its data specification to entities that have data required by the Transmission Operator’s Operational Planning Analyses, Real-time monitoring, and Real-time Assessment. [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false,"For Real Time Monitoring Only"]
[30481,"TOP-003-5","R3.","YES","Each Transmission Operator shall distribute its data specification to entities that have data required by the Transmission Operator’s Operational Planning Analyses, Real-time monitoring, and Real-time Assessment. [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false,"For Real Time Monitoring Only"]
[30483,"TOP-003-5","R4.","YES","Each Balancing Authority shall distribute its data specification to entities that have data required by the Balancing Authority’s analysis functions and Real-time monitoring. [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30484,"TOP-003-5","R4.","YES","Each Balancing Authority shall distribute its data specification to entities that have data required by the Balancing Authority’s analysis functions and Real-time monitoring. [Violation Risk Factor: Low] [Time Horizon: Operations Planning]","2023-10-01",null,"Future Effective",null,"LOWER",null,"N/A",null,"N/A",null,"No",false,null,false]
[30485,"TOP-003-5","R5.","YES","Each Transmission Operator, Balancing Authority, Generator Owner, Generator Operator, Transmission Owner, and Distribution Provider receiving a data specification in Requirement R3 or R4 shall satisfy the obligations of the documented specifications using: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning, Same-Day Operations, Real-time Operations]","2023-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30486,"TOP-003-5","R5.","YES","Each Transmission Operator, Balancing Authority, Generator Owner, Generator Operator, Transmission Owner, and Distribution Provider receiving a data specification in Requirement R3 or R4 shall satisfy the obligations of the documented specifications using: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning, Same-Day Operations, Real-time Operations]","2023-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30487,"TOP-003-5","R5.1.","YES","A mutually agreeable format","2023-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30488,"TOP-003-5","R5.1.","YES","A mutually agreeable format","2023-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30489,"TOP-003-5","R5.2.","YES","A mutually agreeable process for resolving data conflicts","2023-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30490,"TOP-003-5","R5.2.","YES","A mutually agreeable process for resolving data conflicts","2023-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30491,"TOP-003-5","R5.3.","YES","A mutually agreeable process for resolving data conflicts","2023-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[30492,"TOP-003-5","R5.3.","YES","A mutually agreeable process for resolving data conflicts","2023-10-01",null,"Future Effective",null,"MEDIUM",null,"N/A",null,"N/A",null,"No",false,null,false]
[29060,"TOP-005-3a","R1.",null,"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.”",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A",null,"No",false,null,false]
[29061,"TOP-005-3a","R2.",null,"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 “Electric System Reliability Data,” unless otherwise agreed to by the Balancing Authorities and Transmission Operators with immediate responsibility for operational reliability.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","TOP, BA","No",true,null,false]
[29062,"TOP-005-3a","R3.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"N/A",null,"N/A",null,"N/A","PSE","No",false,null,false]
[29072,"TOP-006-3","R1.",null,"Each Transmission Operator and Balancing Authority shall know the status of all generation and transmission resources available for use. [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)",null,"N/A","TOP, BA","No",true,null,false]
[29073,"TOP-006-3","R1.1.",null,"Each Generator Operator shall inform its Host Balancing Authority and the Transmission Operator of all generation resources available for use. [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)",null,"N/A","GOP","Yes",false,null,false]
[29074,"TOP-006-3","R1.2.",null,"Each Transmission Operator shall inform the Reliability Coordinator and other affected Transmission Operators of all transmission resources available for use. [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)",null,"N/A","TOP","No",true,null,false]
[29075,"TOP-006-3","R1.3.",null,"Each Balancing Authority shall inform its Reliability Coordinator of all generation resources available for use. [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM","LIKELY","MEDIUM (Targeted Controls Required)",null,"N/A","BA","No",false,null,false]
[29076,"TOP-006-3","R2.",null,"Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall monitor applicable transmission line status, real and reactive power flows, voltage, load-tap-changer settings, and status of rotating and static reactive resources. [Violation\nRisk Factor: High] [Time Horizon: Real-time Operations]",null,null,"Never Came Into Effect in Ontario",null,"HIGH","LIKELY","HIGH (Comprehensive Controls Required)",null,"N/A","TOP, RC, BA","No",true,null,true]
[29077,"TOP-006-3","R3.",null,"Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall provide its operating personnel with appropriate technical information concerning protective relays within the Reliability Coordinator Area, the Transmission Operator  Area, and the Balancing Authority Area, respectively. [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]",null,null,"Never Came Into Effect in Ontario",null,"HIGH","LIKELY","HIGH (Comprehensive Controls Required)",null,"N/A","TOP, RC, BA","No",true,null,true]
[29078,"TOP-006-3","R4.",null,"Each Transmission Operator, and Balancing Authority shall have information, including weather forecasts and past load patterns, available to predict the system’s near-term load pattern. [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)",null,"N/A","TOP, BA","No",true,null,true]
[29079,"TOP-006-3","R5.",null,"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. [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[29080,"TOP-006-3","R6.",null,"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.\n[Violation Risk Factor: High] [Time Horizon: Real-time Operations]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[29081,"TOP-006-3","R7.",null,"Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall monitor system frequency. [Violation Risk Factor: High] [Time Horizon: Real-time Operations]",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TOP, RC, BA","No",true,null,true]
[29683,"TOP-010-1(i)","R1.",null,"Each Transmission Operator shall implement an Operating Process or Operating Procedure to address the quality of the Real-time data necessary to perform its Real-time monitoring and Real-time Assessments. The Operating Process or Operating Procedure shall include: [Violation Risk Factor: High] [Time Horizon: Real-time Operations]","2018-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[29684,"TOP-010-1(i)","R1.1.",null,"Criteria for evaluating the quality of Real-time data;","2018-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[29685,"TOP-010-1(i)","R1.2.",null,"Provisions to indicate the quality of Real-time data to the System Operator; and","2018-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[29686,"TOP-010-1(i)","R1.3.",null,"Actions to address Real-time data quality issues with the entity(ies) responsible for providing the data when data quality affects Real-time Assessments.","2018-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true]
[29687,"TOP-010-1(i)","R2.",null,"Each Balancing Authority shall implement an Operating Process or Operating Procedure to address the quality of the Real-time data necessary to perform its analysis functions and Real-time monitoring. The Operating Process or Operating Procedure shall include: [Violation Risk Factor: High] [Time Horizon: Real-time Operations]","2018-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[29688,"TOP-010-1(i)","R2.1.",null,"Criteria for evaluating the quality of Real-time data;","2018-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[29689,"TOP-010-1(i)","R2.2.",null,"Provisions to indicate the quality of Real-time data to the System Operator; and","2018-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[29691,"TOP-010-1(i)","R2.3.",null,"Actions to address Real-time data quality issues with the entity(ies) responsible for providing the data when data quality affects its analysis functions.","2018-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","BA","No",false,null,false]
[29692,"TOP-010-1(i)","R3.",null,"Each Transmission Operator shall implement an Operating Process or Operating Procedure to address the quality of analysis used in its Real-time Assessments. The Operating Process or Operating Procedure shall include: [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]","2018-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true]
[29693,"TOP-010-1(i)","R3.1.",null,"Criteria for evaluating the quality of analysis used in its Real-time Assessments;","2018-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true]
[29694,"TOP-010-1(i)","R3.2.",null,"Provisions to indicate the quality of analysis used in its Real-time Assessments; and","2018-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true]
[29695,"TOP-010-1(i)","R3.3.",null,"Actions to address analysis quality issues affecting its Real-time Assessments.","2018-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,true]
[29696,"TOP-010-1(i)","R4.",null,"Each Transmission Operator and Balancing Authority shall have an alarm process monitor that provides notification(s) to its System Operators when a failure of its Real-time monitoring alarm processor has occurred. [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]","2018-04-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TOP, BA","No",true,null,true]
[29103,"TPL-001-0.1(i)","R1.",null,"The Planning Authority and Transmission Planner shall each demonstrate through a valid assessment that its portion of the 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 (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:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29104,"TPL-001-0.1(i)","R1.1.",null,"Be made annually.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29105,"TPL-001-0.1(i)","R1.2.",null,"Be conducted for near-term (years one through five) and longer-term (years six through ten) planning horizons.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29106,"TPL-001-0.1(i)","R1.3.",null,"Be supported by a current or past study and/or system simulation testing that addresses each of the following categories, 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).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29107,"TPL-001-0.1(i)","R1.3.1.",null,"Cover critical system conditions and study years as deemed appropriate by the entity performing the study.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29108,"TPL-001-0.1(i)","R1.3.2.",null,"Be conducted annually unless changes to system conditions do not warrant such analyses.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29109,"TPL-001-0.1(i)","R1.3.3.",null,"Be conducted beyond the five-year horizon only as needed to address identified marginal conditions that may have longer lead-time solutions.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29110,"TPL-001-0.1(i)","R1.3.4.",null,"Have established normal (pre-contingency) operating procedures in place.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29111,"TPL-001-0.1(i)","R1.3.5.",null,"Have all projected firm transfers modeled.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29112,"TPL-001-0.1(i)","R1.3.6.",null,"Be performed for selected demand levels over the range of forecast system demands.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29113,"TPL-001-0.1(i)","R1.3.7.",null,"Demonstrate that system performance meets Table 1 for Category A (no contingencies).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29114,"TPL-001-0.1(i)","R1.3.8.",null,"Include existing and planned facilities.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29115,"TPL-001-0.1(i)","R1.3.9.",null,"Include Reactive Power resources to ensure that adequate reactive resources are available to meet system performance.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29116,"TPL-001-0.1(i)","R1.4.",null,"Address any planned upgrades needed to meet the performance requirements of Category A.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29117,"TPL-001-0.1(i)","R2.",null,"When system simulations indicate an inability of the systems to respond as prescribed in Reliability Standard TPL-001-0.1(i)_R1, the Planning Authority and Transmission Planner shall each:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29118,"TPL-001-0.1(i)","R2.1.",null,"Provide a written summary of its plans to achieve the required system performance as described above throughout the planning horizon.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29119,"TPL-001-0.1(i)","R2.1.1.",null,"Including a schedule for implementation.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29120,"TPL-001-0.1(i)","R2.1.2.",null,"Including a discussion of expected required in-service dates of facilities.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29121,"TPL-001-0.1(i)","R2.1.3.",null,"Consider lead times necessary to implement plans.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29122,"TPL-001-0.1(i)","R2.2.",null,"Review, in subsequent annual assessments, (where sufficient lead time exists), the continuing need for identified system facilities.  Detailed implementation plans are not needed.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29123,"TPL-001-0.1(i)","R3.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29124,"TPL-001-1","R1.",null,"The Planning Authority and Transmission Planner shall each demonstrate through a valid assessment that its portion of the 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 (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:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29125,"TPL-001-1","R1.1.",null,"Be made annually.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29126,"TPL-001-1","R1.2.",null,"Be conducted for near-term (years one through five) and longer-term (years six through ten) planning horizons.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29127,"TPL-001-1","R1.3.",null,"Be supported by a current or past study and/or system simulation testing that addresses each of the following categories, 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).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29128,"TPL-001-1","R1.3.1.",null,"Cover critical system conditions and study years as deemed appropriate by the entity performing the study.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29129,"TPL-001-1","R1.3.2.",null,"Be conducted annually unless changes to system conditions do not warrant such analyses.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29130,"TPL-001-1","R1.3.3.",null,"Be conducted beyond the five-year horizon only as needed to address identified marginal conditions that may have longer lead-time solutions.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29131,"TPL-001-1","R1.3.4.",null,"Have established normal (pre-contingency) operating procedures in place.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29132,"TPL-001-1","R1.3.5.",null,"Have all projected firm transfers modeled.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29133,"TPL-001-1","R1.3.6.",null,"Be performed for selected demand levels over the range of forecast system demands.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29134,"TPL-001-1","R1.3.7.",null,"Demonstrate that system performance meets Table 1 for Category A (no contingencies).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29135,"TPL-001-1","R1.3.8.",null,"Include existing and planned facilities.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29136,"TPL-001-1","R1.3.9.",null,"Include Reactive Power resources to ensure that adequate reactive resources are available to meet system performance.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29137,"TPL-001-1","R1.4.",null,"Address any planned upgrades needed to meet the performance requirements of Category A.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29138,"TPL-001-1","R2.",null,"When system simulations indicate an inability of the systems to respond as prescribed in Reliability Standard TPL-001-1_R1, the Planning Authority and Transmission Planner shall each:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29139,"TPL-001-1","R2.1.",null,"Provide a written summary of its plans to achieve the required system performance as described above throughout the planning horizon.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29140,"TPL-001-1","R2.1.1.",null,"Including a schedule for implementation.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[27947,"TPL-001-1","R2.1.2.",null,"Including a discussion of expected required in-service dates of facilities.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[27948,"TPL-001-1","R2.1.3.",null,"Consider lead times necessary to implement plans.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[27949,"TPL-001-1","R2.2.",null,"Review, in subsequent annual assessments, (where sufficient lead time exists), the continuing need for identified system facilities. Detailed implementation plans are not needed.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[27950,"TPL-001-1","R3.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[27951,"TPL-001-2","R1.",null,"Each Transmission Planner and Planning Coordinator shall maintain System models within its respective area for performing the studies needed to complete its Planning Assessment. The models shall use data consistent with that provided in accordance with the MOD-010 and MOD-012 standards, supplemented by other sources as needed, including items represented in the Corrective Action Plan, and shall represent projected System conditions. This establishes Category P0 as the normal System condition in Table 1.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[27952,"TPL-001-2","R1.1.",null,"System models shall represent:",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[27953,"TPL-001-2","R1.1.1.",null,"Existing Facilities",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[27954,"TPL-001-2","R1.1.2.",null,"Known outage(s) of generation or Transmission Facility(ies) with a duration of at least six months.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[27955,"TPL-001-2","R1.1.3.",null,"New planned Facilities and changes to existing Facilities",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[27956,"TPL-001-2","R1.1.4.",null,"Real and reactive Load forecasts",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[27957,"TPL-001-2","R1.1.5.",null,"Known commitments for Firm Transmission Service and Interchange",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[27958,"TPL-001-2","R1.1.6.",null,"Resources (supply or demand side) required for Load",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29141,"TPL-001-2","R2.",null,"Each Transmission Planner and Planning Coordinator shall prepare an annual Planning Assessment of its portion of the BES. This Planning Assessment shall use current or qualified past studies (as indicated in Requirement R2, Part 2.6), document assumptions, and document summarized results of the steady state analyses, short circuit analyses, and Stability analyses.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29142,"TPL-001-2","R2.1.",null,"For the Planning Assessment, the Near-Term Transmission Planning Horizon portion of the steady state analysis shall be assessed annually and be supported by current annual studies or qualified past studies as indicated in Requirement R2, Part 2.6. Qualifying studies need to include the following conditions:",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29143,"TPL-001-2","R2.1.1.",null,"System peak Load for either Year One or year two, and for year five.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29144,"TPL-001-2","R2.1.2.",null,"System Off-Peak Load for one of the five years.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29145,"TPL-001-2","R2.1.3.",null,"P1 events in Table 1, with known outages modeled as in Requirement R1, Part 1.1.2, under those System peak or Off-Peak conditions when known outages are scheduled.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29146,"TPL-001-2","R2.1.4.",null,"For each of the studies described in Requirement R2, Parts 2.1.1 and 2.1.2, sensitivity case(s) shall be utilized to demonstrate the impact of changes to the basic assumptions used in the model. To accomplish this, the sensitivity analysis in the Planning Assessment must vary one or more of the following conditions by a sufficient amount to stress the System within a range of credible conditions that demonstrate a measurable change in System response :\n• Real and reactive forecasted Load.\n• Expected transfers.\n• Expected in service dates of new or modified Transmission Facilities.\n• Reactive resource capability.\n• Generation additions, retirements, or other dispatch scenarios.\n• Controllable Loads and Demand Side Management.\n• Duration or timing of known Transmission outages.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29147,"TPL-001-2","R2.1.5.",null,"When an entity’s spare equipment strategy could result in the unavailability of major Transmission equipment that has a lead time of one year or more (such as a transformer), the impact of this possible unavailability on System performance shall be studied. The studies shall be performed for the P0, P1, and P2 categories identified in Table 1 with the conditions that the System is expected to experience during the possible unavailability of the long lead time equipment.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29148,"TPL-001-2","R2.2.",null,"For the Planning Assessment, the Long-Term Transmission Planning Horizon portion of the steady state analysis shall be assessed annually and be supported by the following annual current study, supplemented with qualified past studies as indicated in Requirement R2, Part 2.6:",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29149,"TPL-001-2","R2.2.1.",null,"A current study assessing expected System peak Load conditions for one of the years in the Long-Term Transmission Planning Horizon and the rationale for why that year was selected.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29150,"TPL-001-2","R2.3.",null,"The short circuit analysis portion of the Planning Assessment shall be conducted annually addressing the Near-Term Transmission Planning Horizon and can be supported by current or past studies as qualified in Requirement R2, Part 2.6. The analysis shall be used to determine whether circuit breakers have interrupting capability for Faults that they will be expected to interrupt using the System short circuit model with any planned generation and Transmission Facilities in service which could impact the study area.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29151,"TPL-001-2","R2.4.",null,"For the Planning Assessment, the Near-Term Transmission Planning Horizon portion of the Stability analysis shall be assessed annually and be supported by current or past studies as qualified in Requirement R2, Part2.6. The following studies are required:",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29152,"TPL-001-2","R2.4.1.",null,"System peak Load for one of the five years. System peak Load levels shall include a Load model which represents the expected dynamic behavior of Loads that could impact the study area, considering the behavior of induction motor Loads. An aggregate System Load model which represents the overall dynamic behavior of the Load is acceptable.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29153,"TPL-001-2","R2.4.2.",null,"System Off-Peak Load for one of the five years.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29154,"TPL-001-2","R2.4.3.",null,"For each of the studies described in Requirement R2, Parts 2.4.1 and 2.4.2, sensitivity case(s) shall be utilized to demonstrate the impact of changes to the basic assumptions used in the model. To accomplish this, the sensitivity analysis in the Planning Assessment must vary one or more of the following conditions by a sufficient amount to stress the System within a range of credible conditions that demonstrate a measurable change in performance:\n• Load level, Load forecast, or dynamic Load model assumptions.\n• Expected transfers.\n• Expected in service dates of new or modified Transmission Facilities.\n• Reactive resource capability.\n• Generation additions, retirements, or other dispatch scenarios.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29155,"TPL-001-2","R2.5.",null,"For the Planning Assessment, the Long-Term Transmission Planning Horizon portion of the Stability analysis shall be assessed to address the impact of proposed material generation additions or changes in that timeframe and be supported by current or past studies as qualified in Requirement R2, Part2.6 and shall include documentation to support the technical rationale for determining material changes.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29156,"TPL-001-2","R2.6.",null,"Past studies may be used to support the Planning Assessment if they meet the following requirements:",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29157,"TPL-001-2","R2.6.1.",null,"For steady state, short circuit, or Stability analysis: the study shall be five calendar years old or less, unless a technical rationale can be provided to demonstrate that the results of an older study are still valid.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29158,"TPL-001-2","R2.6.2.",null,"For steady state, short circuit, or Stability analysis: no material changes have occurred to the System represented in the study. Documentation to support the technical rationale for determining material changes shall be included.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29159,"TPL-001-2","R2.7.",null,"For planning events shown in Table 1, when the analysis indicates an inability of the System to meet the performance requirements in Table 1, the Planning Assessment shall include Corrective Action Plan(s) addressing how the performance requirements will be met. Revisions to the Corrective Action Plan(s) are allowed in subsequent Planning Assessments but the planned System shall continue to meet the performance requirements in Table 1. Corrective Action Plan(s) do not need to be developed solely to meet the performance requirements for a single sensitivity case analyzed in accordance with Requirements R2, Parts 2.1.4 and 2.4.3. The Corrective Action Plan(s) shall:",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29160,"TPL-001-2","R2.7.1.",null,"List System deficiencies and the associated actions needed to achieve required System performance. Examples of such actions include:\n• Installation, modification, retirement, or removal of Transmission and generation Facilities and any associated equipment.\n• Installation, modification, or removal of Protection Systems or Special Protection Systems\n• Installation or modification of automatic generation tripping as a response to a single or multiple Contingency to mitigate Stability performance violations.\n• Installation or modification of manual and automatic generation runback/tripping as a response to a single or multiple Contingency to mitigate steady state performance violations.\n• Use of Operating Procedures specifying how long they will be needed as part of the Corrective Action Plan.\n• Use of rate applications, DSM, new technologies, or other initiatives.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29161,"TPL-001-2","R2.7.2.",null,"Include actions to resolve performance deficiencies identified in multiple sensitivity studies or provide a rationale for why actions were not necessary.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29162,"TPL-001-2","R2.7.3.",null,"If situations arise that are beyond the control of the Transmission Planner or Planning Coordinator that prevent the implementation of a Corrective Action Plan in the required timeframe, then the Transmission Planner or Planning Coordinator is permitted to utilize Non-Consequential Load Loss and curtailment of Firm Transmission Service to correct the situation that would normally not be permitted in Table 1, provided that the Transmission Planner or Planning Coordinator documents that they are taking actions to resolve the situation. The Transmission Planner or Planning Coordinator shall document the situation causing the problem, alternatives evaluated, and the use of Non-Consequential Load Loss or curtailment of Firm Transmission Service.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29163,"TPL-001-2","R2.7.4.",null,"Be reviewed in subsequent annual Planning Assessments for continued validity and implementation status of identified System Facilities and Operating Procedures.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29164,"TPL-001-2","R2.8.",null,"For short circuit analysis, if the short circuit current interrupting duty on circuit breakers determined in Requirement R2, Part 2.3 exceeds their Equipment Rating, the Planning Assessment shall include a Corrective Action Plan to address the Equipment Rating violations. The Corrective Action Plan shall:",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29165,"TPL-001-2","R2.8.1.",null,"List System deficiencies and the associated actions needed to achieve required System performance.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29166,"TPL-001-2","R2.8.2.",null,"Be reviewed in subsequent annual Planning Assessments for continued validity and implementation status of identified System Facilities and Operating Procedures.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29167,"TPL-001-2","R3.",null,"For the steady state portion of the Planning Assessment, each Transmission Planner and Planning Coordinator shall perform studies for the Near-Term and Long-Term Transmission Planning Horizons in Requirement R2, Parts 2.1, and 2.2. The studies shall be based on computer simulation models using data provided in Requirement R1.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29168,"TPL-001-2","R3.1.",null,"Studies shall be performed for planning events to determine whether the BES meets the performance requirements in Table 1 based on the Contingency list created in Requirement R3, Part 3.4.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29169,"TPL-001-2","R3.2.",null,"Studies shall be performed to assess the impact of the extreme events which are identified by the list created in Requirement R3, Part 3.5.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29170,"TPL-001-2","R3.3.",null,"Contingency analyses for Requirement R3, Parts 3.1 & 3.2 shall:",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29171,"TPL-001-2","R3.3.1.",null,"Simulate the removal of all elements that the Protection System and other automatic controls are expected to disconnect for each Contingency without operator intervention. The analyses shall include the impact of subsequent:",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29172,"TPL-001-2","R3.3.1.1.",null,"Tripping of generators where simulations show generator bus voltages or high side of the generation step up (GSU) voltages are less than known or assumed minimum generator steady state or ride through voltage limitations. Include in the assessment any assumptions made.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29173,"TPL-001-2","R3.3.1.2.",null,"Tripping of Transmission elements where relay loadability limits are exceeded.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29174,"TPL-001-2","R3.3.2.",null,"Simulate the expected automatic operation of existing and planned devices designed to provide steady state control of electrical system quantities when such devices impact the study area. These devices may include equipment such as phase-shifting transformers, load tap changing transformers, and switched capacitors and inductors.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29175,"TPL-001-2","R3.4.",null,"Those planning events in Table 1, that are expected to produce more severe System impacts on its portion of the BES, shall be identified and a list of those Contingencies to be evaluated for System performance in Requirement R3, Part 3.1 created. The rationale for those Contingencies selected for evaluation shall be available as supporting information.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29176,"TPL-001-2","R3.4.1.",null,"The Planning Coordinator and Transmission Planner shall coordinate with adjacent Planning Coordinators and Transmission Planners to ensure that Contingencies on adjacent Systems which may impact their Systems are included in the Contingency list.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29177,"TPL-001-2","R3.5.",null,"Those extreme events in Table 1 that are expected to produce more severe System impacts shall be identified and a list created of those events to be evaluated in Requirement R3, Part 3.2. The rationale for those Contingencies selected for evaluation shall be available as supporting information. If the analysis concludes there is Cascading caused by the occurrence of extreme events, an evaluation of possible actions designed to reduce the likelihood or mitigate the consequences and adverse impacts of the event(s) shall be conducted.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29178,"TPL-001-2","R4.",null,"For the Stability portion of the Planning Assessment, as described in Requirement R2, Parts 2.4 and 2.5, each Transmission Planner and Planning Coordinator shall perform the Contingency analyses listed in Table 1. The studies shall be based on computer simulation models using data provided in Requirement R1.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29179,"TPL-001-2","R4.1.",null,"Studies shall be performed for planning events to determine whether the BES meets the performance requirements in Table 1 based on the Contingency list created in Requirement R4, Part 4.4.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29180,"TPL-001-2","R4.1.1.",null,"For planning event P1: No generating unit shall pull out of synchronism. A generator being disconnected from the System by fault clearing action or by a Special Protection System is not considered pulling out of synchronism.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29181,"TPL-001-2","R4.1.2.",null,"For planning events P2 through P7: When a generator pulls out of synchronism in the simulations, the resulting apparent impedance swings shall not result in the tripping of any Transmission system elements other than the generating unit and its directly connected Facilities.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29182,"TPL-001-2","R4.1.3.",null,"For planning events P1 through P7: Power oscillations shall exhibit acceptable damping as established by the Planning Coordinator and Transmission Planner.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29183,"TPL-001-2","R4.2.",null,"Studies shall be performed to assess the impact of the extreme events which are identified by the list created in Requirement R4, Part 4.5.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29184,"TPL-001-2","R4.3.",null,"Contingency analyses for Requirement R4, Parts 4.1 and 4.2 shall :",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29185,"TPL-001-2","R4.3.1.",null,"Simulate the removal of all elements that the Protection System and other automatic controls are expected to disconnect for each Contingency without operator intervention. The analyses shall include the impact of subsequent:",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29186,"TPL-001-2","R4.3.1.1.",null,"Successful high speed (less than one second) reclosing and unsuccessful high speed reclosing into a Fault where high speed reclosing is utilized.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29187,"TPL-001-2","R4.3.1.2.",null,"Tripping of generators where simulations show generator bus voltages or high side of the GSU voltages are less than known or assumed generator low voltage ride through capability. Include in the assessment any assumptions made.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29188,"TPL-001-2","R4.3.1.3.",null,"Tripping of Transmission lines and transformers where transient swings cause Protection System operation based on generic or actual relay models.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29189,"TPL-001-2","R4.3.2.",null,"Simulate the expected automatic operation of existing and planned devices designed to provide dynamic control of electrical system quantities when such devices impact the study area. These devices may include equipment such as generation exciter control and power system stabilizers, static var compensators, power flow controllers, and DC Transmission controllers.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29190,"TPL-001-2","R4.4.",null,"Those planning events in Table 1 that are expected to produce more severe System impacts on its portion of the BES, shall be identified, and a list created of those Contingencies to be evaluated in Requirement R4, Part 4.1. The rationale for those Contingencies selected for evaluation shall be available as supporting information.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29191,"TPL-001-2","R4.4.1.",null,"Each Planning Coordinator and Transmission Planner shall coordinate with adjacent Planning Coordinators and Transmission Planners to ensure that Contingencies on adjacent Systems which may impact their Systems are included in the Contingency list.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29192,"TPL-001-2","R4.5.",null,"Those extreme events in Table 1 that are expected to produce more severe System impacts shall be identified and a list created of those events to be evaluated in Requirement R4, Part 4.2. The rationale for those Contingencies selected for evaluation shall be available as supporting information. If the analysis concludes there is Cascading caused by the occurrence of extreme events, an evaluation of possible actions designed to reduce the likelihood or mitigate the consequences of the event(s) shall be conducted.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29193,"TPL-001-2","R5.",null,"Each Transmission Planner and Planning Coordinator shall have criteria for acceptable System steady state voltage limits, post-Contingency voltage deviations, and the transient voltage response for its System. For transient voltage response, the criteria shall at a minimum, specify a low voltage level and a maximum length of time that transient voltages may remain below that level.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29194,"TPL-001-2","R6.",null,"Each Transmission Planner and Planning Coordinator shall define and document, within their Planning Assessment, the criteria or methodology used in the analysis to identify System instability for conditions such as Cascading, voltage instability, or uncontrolled islanding.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29195,"TPL-001-2","R7.",null,"Each Planning Coordinator, in conjunction with each of its Transmission Planners, shall determine and identify each entity’s individual and joint responsibilities for performing the required studies for the Planning Assessment.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29196,"TPL-001-2","R8.",null,"Each Planning Coordinator and Transmission Planner shall distribute its Planning Assessment results to adjacent Planning Coordinators and adjacent Transmission Planners within 90 calendar days of completing its Planning Assessment, and to any functional entity that has a reliability related need and submits a written request for the information within 30 days of such a request.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29197,"TPL-001-2","R8.1.",null,"If a recipient of the Planning Assessment results provides documented comments on the results, the respective Planning Coordinator or Transmission Planner shall provide a documented response to that recipient within 90 calendar days of receipt of those comments.",null,null,"Never Came Into Effect in Ontario",null,"No Individual VRF Assigned",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29198,"TPL-001-3","R1.",null,"The Planning Authority and Transmission Planner shall each demonstrate through a valid assessment that its portion of the 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 (non- recallable reserved) Transmission Services at all Demand levels over the range of forecast system demands, under the\nconditions defined in Category A of Table I. To be considered valid, the Planning Authority and Transmission Planner assessments shall:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29199,"TPL-001-3","R1.1.",null,"Be made annually.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29200,"TPL-001-3","R1.2.",null,"Be conducted for near-term (years one through five) and longer-term (years six through ten) planning horizons.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29201,"TPL-001-3","R1.3.",null,"Be supported by a current or past study and/or system simulation testing that addresses each of the following categories, 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).",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29202,"TPL-001-3","R1.3.1.",null,"Cover critical system conditions and study years as deemed appropriate by the entity performing the study.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29203,"TPL-001-3","R1.3.2.",null,"Be conducted annually unless changes to system conditions do not warrant such analyses.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29204,"TPL-001-3","R1.3.3.",null,"Be conducted beyond the five-year horizon only as needed to address identified marginal conditions that may have longer lead-time solutions.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29205,"TPL-001-3","R1.3.4.",null,"Have established normal (pre-contingency) operating procedures in place.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29206,"TPL-001-3","R1.3.5.",null,"Have all projected firm transfers modeled.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29207,"TPL-001-3","R1.3.6.",null,"Be performed for selected demand levels over the range of forecast system demands.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29208,"TPL-001-3","R1.3.7.",null,"Demonstrate that system performance meets Table 1 for Category A (no contingencies).",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29209,"TPL-001-3","R1.3.8.",null,"Include existing and planned facilities.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29210,"TPL-001-3","R1.3.9.",null,"Include Reactive Power resources to ensure that adequate reactive resources are available to meet system performance.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29211,"TPL-001-3","R1.4.",null,"Address any planned upgrades needed to meet the performance requirements of Category A.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29212,"TPL-001-3","R2.",null,"When system simulations indicate an inability of the systems to respond as prescribed in Reliability Standard TPL-001-3_R1, the Planning Authority and Transmission Planner shall each:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29213,"TPL-001-3","R2.1.",null,"Provide a written summary of its plans to achieve the required system performance as described above throughout the planning horizon.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29214,"TPL-001-3","R2.1.1.",null,"Including a schedule for implementation.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29215,"TPL-001-3","R2.1.2.",null,"Including a discussion of expected required in-service dates of facilities.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29216,"TPL-001-3","R2.1.3.",null,"Consider lead times necessary to implement plans.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29217,"TPL-001-3","R2.2.",null,"Review, in subsequent annual assessments, (where sufficient lead time exists), the continuing need for identified system facilities. Detailed implementation plans are not needed.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29218,"TPL-001-3","R3.",null,"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\nReliability Organization.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29219,"TPL-001-4","R1.",null,"Each Transmission Planner and Planning Coordinator shall maintain System models within its respective area for performing the studies needed to complete its Planning Assessment. The models shall use data consistent with that provided in accordance with the MOD-010 and MOD-012 standards, supplemented by other sources as needed, including items represented in\nthe Corrective Action Plan, and shall represent projected System conditions. This establishes Category P0 as the normal System condition in Table 1. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29220,"TPL-001-4","R1.1.",null,"System models shall represent:","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29221,"TPL-001-4","R1.1.1.",null,"Existing Facilities","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29222,"TPL-001-4","R1.1.2.",null,"Known outage(s) of generation or Transmission Facility(ies) with a duration of at least six months.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29223,"TPL-001-4","R1.1.3.",null,"New planned Facilities and changes to existing Facilities","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29224,"TPL-001-4","R1.1.4.",null,"Real and reactive Load forecasts","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29225,"TPL-001-4","R1.1.5.",null,"Known commitments for Firm Transmission Service and Interchange","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29226,"TPL-001-4","R1.1.6.",null,"Resources (supply or demand side) required for Load","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29227,"TPL-001-4","R2.",null,"Each Transmission Planner and Planning Coordinator shall prepare an annual Planning Assessment of its portion of the BES. This Planning Assessment shall use current or qualified past studies (as indicated in Requirement R2, Part 2.6), document assumptions, and document summarized results of the steady state analyses, short circuit analyses, and Stability analyses. [Violation Risk Factor: High] [Time Horizon: Long-term Planning]","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29228,"TPL-001-4","R2.1.",null,"For the Planning Assessment, the Near-Term Transmission Planning Horizon portion of the steady state analysis shall be assessed annually and be supported by current annual studies or qualified past studies as indicated in Requirement R2, Part 2.6.\nQualifying studies need to include the following conditions:","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29229,"TPL-001-4","R2.1.1.",null,"System peak Load for either Year One or year two, and for year five.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29230,"TPL-001-4","R2.1.2.",null,"System Off-Peak Load for one of the five years.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29231,"TPL-001-4","R2.1.3.",null,"P1 events in Table 1, with known outages modeled as in Requirement R1, Part 1.1.2, under those System peak or Off-Peak conditions when known outages are scheduled.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29232,"TPL-001-4","R2.1.4.",null,"For each of the studies described in Requirement R2, Parts 2.1.1 and 2.1.2, sensitivity case(s) shall be utilized to demonstrate the impact of changes to the basic assumptions used in the model. To accomplish this, the sensitivity analysis in the Planning Assessment must vary one or more of the following conditions by a sufficient amount to stress the System within a range of\ncredible conditions that demonstrate a measurable change in System response :\n Real and reactive forecasted Load.\n Expected transfers.\n Expected in service dates of new or modified Transmission Facilities.\n Reactive resource capability.\n Generation additions, retirements, or other dispatch scenarios.                                                                                                  Controllable Loads and Demand Side Management.\n Duration or timing of known Transmission outages","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29233,"TPL-001-4","R2.1.5.",null,"When an entity’s spare equipment strategy could result in the unavailability of major Transmission equipment that has a lead time of one year or more (such as a transformer), the impact of this possible unavailability on System performance shall be studied. The studies shall be performed for the P0, P1, and P2 categories identified in Table 1 with the conditions that the System is expected to experience during the possible unavailability of the long lead time equipment.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29234,"TPL-001-4","R2.2.",null,"For the Planning Assessment, the Long-Term Transmission Planning Horizon portion of the steady state analysis shall be assessed annually and be supported by the following annual current study, supplemented with qualified past studies as indicated in Requirement R2, Part 2.6:","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29235,"TPL-001-4","R2.2.1.",null,"A current study assessing expected System peak Load conditions for one of the years in the Long-Term Transmission Planning Horizon and the rationale for why that year was selected.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29236,"TPL-001-4","R2.3.",null,"The short circuit analysis portion of the Planning Assessment shall be conducted annually addressing the Near-Term Transmission Planning Horizon and can be supported by current or past studies as qualified in Requirement R2, Part 2.6. The analysis shall be used to determine whether circuit breakers have interrupting capability for Faults that they will be expected to interrupt using the System short circuit model with any planned generation and Transmission Facilities in service which could impact the study area.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29237,"TPL-001-4","R2.4.",null,"For the Planning Assessment, the Near-Term Transmission Planning Horizon portion of the Stability analysis shall be assessed annually and be supported by current or past studies as qualified in Requirement R2, Part2.6. The following studies are required:","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29238,"TPL-001-4","R2.4.1.",null,"System peak Load for one of the five years. System peak Load levels shall include a Load model which represents the expected dynamic behavior of Loads that could impact the study area, considering the behavior of induction motor Loads. An aggregate System Load model which represents the overall dynamic behavior of the Load is acceptable.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29239,"TPL-001-4","R2.4.2.",null,"System Off-Peak Load for one of the five years.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29240,"TPL-001-4","R2.4.3.",null,"For each of the studies described in Requirement R2, Parts 2.4.1 and 2.4.2, sensitivity case(s) shall be utilized to demonstrate the impact of changes to the basic assumptions used in the model. To accomplish this, the sensitivity analysis in the Planning Assessment must vary one or more of the following conditions by a sufficient amount to stress the System within a range of\ncredible conditions that demonstrate a measurable change in performance:                                                                 \n Load level, Load forecast, or dynamic Load model assumptions.\n Expected transfers.\n Expected in service dates of new or modified Transmission Facilities.\n Reactive resource capability.\n Generation additions, retirements, or other dispatch scenarios.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29241,"TPL-001-4","R2.5.",null,"For the Planning Assessment, the Long-Term Transmission Planning Horizon portion of the Stability analysis shall be assessed to address the impact of proposed material generation additions or changes in that timeframe and be supported by current or past\nstudies as qualified in Requirement R2, Part2.6 and shall include documentation to support the technical rationale for determining material changes.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29242,"TPL-001-4","R2.6.",null,"Past studies may be used to support the Planning Assessment if they meet the following requirements:","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29243,"TPL-001-4","R2.6.1.",null,"For steady state, short circuit, or Stability analysis: the study shall be five calendar years old or less, unless a technical rationale can be provided to demonstrate that the results of an older study are still valid.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29244,"TPL-001-4","R2.6.2.",null,"For steady state, short circuit, or Stability analysis: no material changes have occurred to the System represented in the study. Documentation to support the technical rationale for determining material changes shall be included.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29245,"TPL-001-4","R2.7.",null,"For planning events shown in Table 1, when the analysis indicates an inability of the System to meet the performance requirements in Table 1, the Planning Assessment shall include Corrective Action Plan(s) addressing how the performance requirements will be met. Revisions to the Corrective Action Plan(s) are allowed in subsequent Planning Assessments but the planned System shall continue to meet the performance requirements in Table 1. Corrective Action Plan(s) do not need to be developed solely to meet the performance requirements for a single sensitivity case analyzed in accordance with Requirements R2, Parts 2.1.4 and 2.4.3. The Corrective Action Plan(s) shall:","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29246,"TPL-001-4","R2.7.1.",null,"List System deficiencies and the associated actions needed to achieve required System performance. Examples of such actions include:\n Installation, modification, retirement, or removal of Transmission and generation Facilities and any associated equipment.\n Installation, modification, or removal of Protection Systems or Special Protection Systems\n Installation or modification of automatic generation tripping as a response to a single or multiple Contingency to mitigate Stability\nperformance violations.\n Installation or modification of manual and automatic generation runback/tripping as a response to a single or multiple Contingency to mitigate steady state performance violations.\n Use of Operating Procedures specifying how long they will be needed as part of the Corrective Action Plan.\n Use of rate applications, DSM, new technologies, or other initiatives.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29247,"TPL-001-4","R2.7.2.",null,"Include actions to resolve performance deficiencies identified in multiple sensitivity studies or provide a rationale for why actions were not necessary.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29248,"TPL-001-4","R2.7.3.",null,"If situations arise that are beyond the control of the Transmission Planner or Planning Coordinator that prevent the implementation of a Corrective Action Plan in the required timeframe, then the Transmission Planner or Planning Coordinator is permitted to utilize Non-Consequential Load Loss and curtailment of Firm Transmission Service to correct the situation that would normally not be permitted in Table 1, provided that the Transmission Planner or Planning Coordinator documents that they are taking actions to resolve the situation. The Transmission Planner or Planning Coordinator shall document the situation causing the problem, alternatives evaluated, and the use of Non-Consequential Load Loss or curtailment of Firm Transmission Service.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29249,"TPL-001-4","R2.7.4.",null,"Be reviewed in subsequent annual Planning Assessments for continued validity and implementation status of identified System Facilities and Operating Procedures.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29250,"TPL-001-4","R2.8.",null,"For short circuit analysis, if the short circuit current interrupting duty on circuit breakers determined in Requirement R2, Part 2.3 exceeds their Equipment Rating, the Planning Assessment shall include a Corrective Action Plan to address the Equipment\nRating violations. The Corrective Action Plan shall:","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29251,"TPL-001-4","R2.8.1.",null,"List System deficiencies and the associated actions needed to achieve required System performance.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29252,"TPL-001-4","R2.8.2.",null,"Be reviewed in subsequent annual Planning Assessments for continued validity and implementation status of identified System Facilities and Operating Procedures.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29253,"TPL-001-4","R3.",null,"For the steady state portion of the Planning Assessment, each Transmission Planner and Planning Coordinator shall perform studies for the Near-Term and Long-Term Transmission Planning Horizons in Requirement R2, Parts 2.1, and 2.2. The studies shall be based on computer simulation models using data provided in Requirement R1. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29254,"TPL-001-4","R3.1.",null,"Studies shall be performed for planning events to determine whether the BES meets the performance requirements in Table 1 based on the Contingency list created in Requirement R3, Part 3.4.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29255,"TPL-001-4","R3.2.",null,"Studies shall be performed to assess the impact of the extreme events which are identified by the list created in Requirement R3, Part 3.5.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29256,"TPL-001-4","R3.3.",null,"Contingency analyses for Requirement R3, Parts 3.1 & 3.2 shall:","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29257,"TPL-001-4","R3.3.1.",null,"Simulate the removal of all elements that the Protection System and other automatic controls are expected to disconnect for each Contingency without operator intervention. The analyses shall include the impact of subsequent:","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29258,"TPL-001-4","R3.3.1.1.",null,"Tripping of generators where simulations show generator bus voltages or high side of the generation step up (GSU) voltages\nare less than known or assumed minimum generator steady state or ride through voltage limitations. Include in the assessment\nany assumptions made.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29259,"TPL-001-4","R3.3.1.2.",null,"Tripping of Transmission elements where relay loadability limits are exceeded.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29260,"TPL-001-4","R3.3.2.",null,"Simulate the expected automatic operation of existing and planned devices designed to provide steady state control of electrical system quantities when such devices impact the study area. These devices may include equipment such as phase-shifting transformers, load tap changing transformers, and switched capacitors and inductors.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29261,"TPL-001-4","R3.4.",null,"Those planning events in Table 1, that are expected to produce more severe System impacts on its portion of the BES, shall be identified and a list of those Contingencies to be evaluated for System performance in Requirement R3, Part 3.1 created. The\nrationale for those Contingencies selected for evaluation shall be available as supporting information.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29262,"TPL-001-4","R3.4.1.",null,"The Planning Coordinator and Transmission Planner shall coordinate with adjacent Planning Coordinators and Transmission Planners to ensure that Contingencies on adjacent Systems which may impact their Systems are included in the Contingency list.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29263,"TPL-001-4","R3.5.",null,"Those extreme events in Table 1 that are expected to produce more severe System impacts shall be identified and a list created of those events to be evaluated in Requirement R3, Part 3.2. The rationale for those Contingencies selected for evaluation shall be available as supporting information. If the analysis concludes there is Cascading caused by the occurrence of extreme events, an evaluation of possible actions designed to reduce the likelihood or mitigate the consequences and adverse impacts of the event(s) shall be conducted.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29264,"TPL-001-4","R4.",null,"For the Stability portion of the Planning Assessment, as described in Requirement R2, Parts 2.4 and 2.5, each Transmission Planner and Planning Coordinator shall perform the Contingency analyses listed in Table 1. The studies shall be based on computer  simulation models using data provided in Requirement R1. [Violation Risk Factor: Medium] [Time Horizon: Longterm Planning]","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29265,"TPL-001-4","R4.1.",null,"Studies shall be performed for planning events to determine whether the BES meets the performance requirements in Table 1 based on the Contingency list created in Requirement R4, Part 4.4.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29266,"TPL-001-4","R4.1.1.",null,"For planning event P1: No generating unit shall pull out of synchronism. A generator being disconnected from the System by fault clearing action or by a Special Protection System is not considered pulling out of synchronism.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29267,"TPL-001-4","R4.1.2.",null,"For planning events P2 through P7: When a generator pulls out of synchronism in the simulations, the resulting apparent impedance swings shall not result in the tripping of any Transmission system elements other than the generating unit and its directly connected Facilities.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29268,"TPL-001-4","R4.1.3.",null,"For planning events P1 through P7: Power oscillations shall exhibit acceptable damping as established by the Planning Coordinator and Transmission Planner.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29269,"TPL-001-4","R4.2.",null,"Studies shall be performed to assess the impact of the extreme events which are identified by the list created in Requirement R4, Part 4.5.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29270,"TPL-001-4","R4.3.",null,"Contingency analyses for Requirement R4, Parts 4.1 and 4.2 shall :","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29271,"TPL-001-4","R4.3.1.",null,"Simulate the removal of all elements that the Protection System and other automatic controls are expected to disconnect for each Contingency without operator intervention. The analyses shall include the impact of subsequent:","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29272,"TPL-001-4","R4.3.1.1.",null,"Successful high speed (less than one second) reclosing and unsuccessful high speed reclosing into a Fault where high speed\nreclosing is utilized.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29273,"TPL-001-4","R4.3.1.2.",null,"Tripping of generators where simulations show generator bus voltages or high side of the GSU voltages are less than known or\nassumed generator low voltage ride through capability. Include in the assessment any assumptions made.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29274,"TPL-001-4","R4.3.1.3.",null,"Tripping of Transmission lines and transformers where transient swings cause Protection System operation based on generic or\nactual relay models.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29275,"TPL-001-4","R4.3.2.",null,"Simulate the expected automatic operation of existing and planned devices designed to provide dynamic control of electrical system quantities when such devices impact the study area. These devices may include equipment such as generation exciter control and power system stabilizers, static var compensators, power flow controllers, and DC Transmission controllers.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29276,"TPL-001-4","R4.4.",null,"Those planning events in Table 1 that are expected to produce more severe System impacts on its portion of the BES, shall be identified, and a list created of those Contingencies to be evaluated in Requirement R4, Part 4.1. The rationale for those Contingencies selected for evaluation shall be available as supporting information.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29277,"TPL-001-4","R4.4.1.",null,"Each Planning Coordinator and Transmission Planner shall coordinate with adjacent Planning Coordinators and Transmission Planners to ensure that Contingencies on adjacent Systems which may impact their Systems are included in the Contingency list.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29278,"TPL-001-4","R4.5.",null,"Those extreme events in Table 1 that are expected to produce more severe System impacts shall be identified and a list created of those events to be evaluated in Requirement R4, Part 4.2. The rationale for those Contingencies selected for evaluation shall be available as supporting information. If the analysis concludes there is Cascading caused by the occurrence of extreme events, an evaluation of possible actions designed to reduce the likelihood or mitigate the consequences of the event(s) shall be conducted.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29279,"TPL-001-4","R5.",null,"Each Transmission Planner and Planning Coordinator shall have criteria for acceptable System steady state voltage limits, post-Contingency voltage deviations, and the transient voltage response for its System. For transient voltage response, the criteria shall at a minimum, specify a low voltage level and a maximum length of time that transient voltages may remain below that level. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29280,"TPL-001-4","R6.",null,"Each Transmission Planner and Planning Coordinator shall define and document, within their Planning Assessment, the criteria or methodology used in the analysis to identify System instability for conditions such as Cascading, voltage instability, or uncontrolled islanding. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29281,"TPL-001-4","R7.",null,"Each Planning Coordinator, in conjunction with each of its Transmission Planners, shall determine and identify each entity’s individual and joint responsibilities for performing the required studies for the Planning Assessment. [Violation Risk Factor: Low] [Time Horizon: Long-term Planning]","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC, PA","No",false,null,false]
[29282,"TPL-001-4","R8.",null,"Each Planning Coordinator and Transmission Planner shall distribute its Planning Assessment results to adjacent Planning  coordinators and adjacent Transmission Planners within 90 calendar days of completing its Planning Assessment, and to any functional entity that has a reliability related need and submits a written request for the information within 30 days of such\na request. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29283,"TPL-001-4","R8.1.",null,"If a recipient of the Planning Assessment results provides documented comments on the results, the respective Planning Coordinator or Transmission Planner shall provide a documented response to that recipient within 90 calendar days of receipt of those comments.","2015-01-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Quality Check/Verification; Segregation of Duties; Tools and Applications","MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29753,"TPL-001-5","R1.",null,"Each Transmission Planner and Planning Coordinator shall maintain System models within its respective area for performing the studies needed to complete its Planning Assessment. The models shall use data consistent with that provided in accordance with the MOD-032 standard, supplemented by other sources as needed, including items represented in the Corrective Action Plan, and shall represent projected System conditions. This establishes Category P0 as the normal System condition in Table 1. [Violation Risk Factor: High] [Time Horizon: Long-term Planning]","2022-07-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PA, PC, TP","No",false,null,false]
[29754,"TPL-001-5","R1.1.",null,"System models shall represent:","2022-07-01",null,"Effective","Authorization/Approval; Communications; Documentations, Policies and Procedures; Monitoring; Quality Check/Verification; Segregation of Duties; Tools and Applications; Training","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PA, PC, TP","No",false,null,false]
[29755,"TPL-001-5","R1.1.1.",null,"Existing Facilities.","2022-07-01",null,"Effective","Documentations, Policies and Procedures; Authorization/Approval; Communications; Training; Monitoring; Tools and Applications; Quality Check/Verification; Segregation of Duties","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29756,"TPL-001-5","R1.1.2.",null,"New planned Facilities and changes to existing Facilities.","2022-07-01",null,"Effective","Documentations, Policies and Procedures; Authorization/Approval; Communications; Training; Monitoring; Tools and Applications; Quality Check/Verification; Segregation of Duties","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29757,"TPL-001-5","R1.1.3.",null,"Real and reactive Load forecasts.","2022-07-01",null,"Effective","Documentations, Policies and Procedures; Authorization/Approval; Communications; Training; Monitoring; Tools and Applications; Quality Check/Verification; Segregation of Duties","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","PC, PA, TP","No",false,null,false]
[29758,"TPL-001-5","R1.1.4.",null,"Known commitments for Firm Transmission Service and Interchange.","2022-07-01",null,"Effective","Documentations, Policies and Procedures; Authorization/Approval; Communications; Training; Monitoring; Tools and Applications; Quality Check/Verification; Segregation of Duties","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29759,"TPL-001-5","R1.1.5.",null,"Resources (supply or demand side) required for Load.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29760,"TPL-001-5","R2.",null,"Each Transmission Planner and Planning Coordinator shall prepare an annual Planning Assessment of its portion of the BES. This Planning Assessment shall use current or qualified past studies (as indicated in Requirement R2, Part 2.6), document assumptions, and document summarized results of the steady state analyses, short circuit analyses, and Stability analyses. [Violation Risk Factor: High] [Time Horizon: Long-term Planning]","2022-07-01",null,"Effective","Documentations, Policies and Procedures; Authorization/Approval; Communications; Training; Monitoring; Tools and Applications; Quality Check/Verification; Segregation of Duties","HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29761,"TPL-001-5","R2.1.",null,"For the Planning Assessment, the Near-Term Transmission Planning Horizon portion of the steady state analysis shall be assessed annually and be supported by current annual studies or qualified past studies as indicated in Requirement R2, Part 2.6. Qualifying studies need to include the following conditions:","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29762,"TPL-001-5","R2.1.1.",null,"System peak Load for either Year One or year two, and for year five.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29763,"TPL-001-5","R2.1.2.",null,"System Off-Peak Load for one of the five years.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29764,"TPL-001-5","R2.1.3.",null,"For each of the studies described in Requirement R2, Parts 2.1.1 and 2.1.2, sensitivity case(s) shall be utilized to demonstrate the impact of changes to the basic assumptions used in the model. To accomplish this, the sensitivity analysis in the Planning Assessment must vary one or more of the following conditions by a sufficient amount to stress the System within a range of credible conditions that demonstrate a measurable change in System response :\r\n• Real and reactive forecasted Load.\r\n• Expected transfers.\r\n• Expected in service dates of new or modified Transmission Facilities.\r\n• Reactive resource capability.\r\n• Generation additions, retirements, or other dispatch scenarios.\r\n• Controllable Loads and Demand Side Management.\r\n• Duration or timing of known Transmission outages.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29765,"TPL-001-5","R2.1.4.",null,"When known outage(s) of generation or Transmission Facility(ies) are planned in the Near-Term Planning Horizon, the impact of selected known outages on System performance shall be assessed. These known outage(s) shall be selected for assessment consistent with a documented outage coordination procedure or technical rationale by the Planning Coordinator or Transmission Planner. Known outage(s) shall not be excluded solely based upon outage duration. The assessment shall be performed for the P0 and P1 categories identified in Table 1 with the System peak or Off-Peak conditions that the System is expected to experience when the known outage(s) are planned. This assessment shall include, at a minimum known outages expected to produce more severe System impacts on the Planning Coordinator or Transmission Planner’s portion of the BES. Past or current studies may support the selection of known outage(s), if the study(s) has comparable post-Contingency System conditions and configuration such as those following P3 or P6 category events in Table 1.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29767,"TPL-001-5","R2.1.5.",null,"When an entity’s spare equipment strategy could result in the unavailability of major Transmission equipment that has a lead time of one year or more (such as a transformer), the impact of this possible unavailability on System performance shall be assessed. Based upon this assessment, an analysis shall be performed for the P0, P1, and P2 categories identified in Table 1 with the conditions that the System is expected to experience during the possible unavailability of the long lead time equipment.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29769,"TPL-001-5","R2.2.",null,"For the Planning Assessment, the Long-Term Transmission Planning Horizon portion of the steady state analysis shall be assessed annually and be supported by the following annual current study, supplemented with qualified past studies as indicated in Requirement R2, Part 2.6:","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29770,"TPL-001-5","R2.2.1.",null,"A current study assessing expected System peak Load conditions for one of the years in the Long-Term Transmission Planning Horizon and the rationale for why that year was selected.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29771,"TPL-001-5","R2.3.",null,"The short circuit analysis portion of the Planning Assessment shall be conducted annually addressing the Near-Term Transmission Planning Horizon and can be supported by current or past studies as qualified in Requirement R2, Part 2.6. The analysis shall be used to determine whether circuit breakers have interrupting capability for Faults that they will be expected to interrupt using the System short circuit model with any planned generation and Transmission Facilities in service which could impact the study area.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29772,"TPL-001-5","R2.4.",null,"For the Planning Assessment, the Near-Term Transmission Planning Horizon portion of the Stability analysis shall be assessed annually and be supported by current or past studies as qualified in Requirement R2, Part2.6. The following studies are required:","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29773,"TPL-001-5","R2.4.1.",null,"System peak Load for one of the five years. System peak Load levels shall include a Load model which represents the expected dynamic behavior of Loads that could impact the study area, considering the behavior of induction motor Loads. An aggregate System Load model which represents the overall dynamic behavior of the Load is acceptable.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29774,"TPL-001-5","R2.4.2.",null,"System Off-Peak Load for one of the five years.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29775,"TPL-001-5","R2.4.3.",null,"For each of the studies described in Requirement R2, Parts 2.4.1 and 2.4.2, sensitivity case(s) shall be utilized to demonstrate the impact of changes to the basic assumptions used in the model. To accomplish this, the sensitivity analysis in the Planning Assessment must vary one or more of the following conditions by a sufficient amount to stress the System within a range of credible conditions that demonstrate a measurable change in performance:\r\n• Load level, Load forecast, or dynamic Load model assumptions.\r\n• Expected transfers.\r\n• Expected in service dates of new or modified Transmission Facilities.\r\n• Reactive resource capability.\r\n• Generation additions, retirements, or other dispatch scenarios.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29776,"TPL-001-5","R2.4.4.",null,"When known outage(s) of generation or Transmission Facility(ies) are planned in the Near-Term Planning Horizon, the impact of selected known outages on System performance shall be assessed. These known outage(s) shall be selected for assessment consistent with a documented outage coordination procedure or technical rationale by the Planning Coordinator or Transmission Planner. Known outage(s) shall not be excluded solely based upon outage duration. The assessment shall be performed for the P1 categories identified in Table 1 with the System peak or Off-Peak conditions that the System is expected to experience when the known outage(s) are planned. This assessment shall include, at a minimum, those known outages expected to produce more severe System impacts on the Planning Coordinator or Transmission Planner’s portion of the BES. Past or current studies may support the selection of known outage(s), if the study(s) has comparable post-Contingency System conditions and configuration such as those following P3 or P6 category events in Table 1.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29777,"TPL-001-5","R2.4.5.",null,"unavailability of major Transmission equipment that has a lead time of one year or more (such as a transformer), the impact of this possible unavailability on System performance shall be assessed. Based upon this assessment, an analysis shall be performed for the selected P1 and P2 category events identified in Table 1 for which the unavailability is expected to produce more severe System impacts on its portion of the BES. The analysis shall simulate the conditions that the System is expected to experience during the possible unavailability of the long lead time equipment.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29778,"TPL-001-5","R2.5.",null,"For the Planning Assessment, the Long-Term Transmission Planning Horizon portion of the Stability analysis shall be assessed to address the impact of proposed material generation additions or changes in that timeframe and be supported by current or past studies as qualified in Requirement R2, Part2.6 and shall include documentation to support the technical rationale for determining material changes.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29779,"TPL-001-5","R2.6.",null,"Past studies may be used to support the Planning Assessment if they meet the following requirements:","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29780,"TPL-001-5","R2.6.1.",null,"For steady state, short circuit, or Stability analysis: the study shall be five calendar years old or less, unless a technical rationale can be provided to demonstrate that the results of an older study are still valid.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29781,"TPL-001-5","R2.6.2.",null,"For steady state, short circuit, or Stability analysis: no material changes have occurred to the System represented in the study. Documentation to support the technical rationale for determining material changes shall be included.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29782,"TPL-001-5","R2.7.",null,"For planning events shown in Table 1, when the analysis indicates an inability of the System to meet the performance requirements in Table 1, the Planning Assessment shall include Corrective Action Plan(s) addressing how the performance requirements will be met. Revisions to the Corrective Action Plan(s) are allowed in subsequent Planning Assessments, but the planned System shall continue to meet the performance requirements in Table 1. Corrective Action Plan(s) do not need to be developed solely to meet the performance requirements for a single sensitivity case analyzed in accordance with Requirements R2, Parts 2.1.4 and 2.4.3. The Corrective Action Plan(s) shall:","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29783,"TPL-001-5","R2.7.1.",null,"List System deficiencies and the associated actions needed to achieve required System performance. Examples of such actions include:\r\n• Installation, modification, retirement, or removal of Transmission and generation Facilities and any associated equipment.\r\n• Installation, modification, or removal of Protection Systems or Remedial Action Schemes.\r\n• Installation or modification of automatic generation tripping as a response to a single or multiple Contingency to mitigate Stability performance violations.\r\n• Installation or modification of manual and automatic generation runback/tripping as a response to a single or multiple Contingency to mitigate steady state performance violations.\r\n• Use of Operating Procedures specifying how long they will be needed as part of the Corrective Action Plan.\r\n• Use of rate applications, DSM, new technologies, or other initiatives.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29784,"TPL-001-5","R2.7.2.",null,"Include actions to resolve performance deficiencies identified in multiple sensitivity studies or provide a rationale for why actions were not necessary.\r\n• Installation, modification, retirement, or removal of Transmission and generation Facilities and any associated equipment.\r\n• Installation, modification, or removal of Protection Systems or Remedial Action Schemes.\r\n• Installation or modification of automatic generation tripping as a response to a single or multiple Contingency to mitigate Stability performance violations.\r\n• Installation or modification of manual and automatic generation runback/tripping as a response to a single or multiple Contingency to mitigate steady state performance violations.\r\n• Use of Operating Procedures specifying how long they will be needed as part of the Corrective Action Plan.\r\n• Use of rate applications, DSM, new technologies, or other initiatives.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29785,"TPL-001-5","R2.7.3.",null,"If situations arise that are beyond the control of the Transmission Planner or Planning Coordinator that prevent the implementation of a Corrective Action Plan in the required timeframe, then the Transmission Planner or Planning Coordinator is permitted to utilize Non-Consequential Load Loss and curtailment of Firm Transmission Service to correct the situation that would normally not be permitted in Table 1, provided that the Transmission Planner or Planning Coordinator documents that they are taking actions to resolve the situation. The Transmission Planner or Planning Coordinator shall document the situation causing the problem, alternatives evaluated, and the use of Non-Consequential Load Loss or curtailment of Firm Transmission Service.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29786,"TPL-001-5","R2.7.4.",null,"Be reviewed in subsequent annual Planning Assessments for continued validity and implementation status of identified System Facilities and Operating Procedures.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29787,"TPL-001-5","R2.8.",null,"For short circuit analysis, if the short circuit current interrupting duty on circuit breakers determined in Requirement R2, Part 2.3 exceeds their Equipment Rating, the Planning Assessment shall include a Corrective Action Plan to address the Equipment Rating violations. The Corrective Action Plan shall:","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29788,"TPL-001-5","R2.8.1.",null,"List System deficiencies and the associated actions needed to achieve required System performance.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29789,"TPL-001-5","R2.8.2.",null,"Be reviewed in subsequent annual Planning Assessments for continued validity and implementation status of identified System Facilities and Operating Procedures.","2022-07-01",null,"Effective",null,"HIGH","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29790,"TPL-001-5","R3.",null,"For the steady state portion of the Planning Assessment, each Transmission Planner and Planning Coordinator shall perform studies for the Near-Term and Long-Term Transmission Planning Horizons in Requirement R2, Parts 2.1, and 2.2. The studies shall be based on computer simulation models using data provided in Requirement R1. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29791,"TPL-001-5","R3.1.",null,"Studies shall be performed for planning events to determine whether the BES meets the performance requirements in Table 1 based on the Contingency list created in Requirement R3, Part 3.4.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29792,"TPL-001-5","R3.2.",null,"Studies shall be performed to assess the impact of the extreme events which are identified by the list created in Requirement R3, Part 3.5. If the analysis concludes there is Cascading caused by the occurrence of extreme events, an evaluation of possible actions designed to reduce the likelihood or mitigate the consequences and adverse impacts of the event(s) shall be conducted.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29793,"TPL-001-5","R3.3.",null,"Contingency analyses for Requirement R3, Parts 3.1 and 3.2 shall:","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29794,"TPL-001-5","R3.3.1.",null,"Simulate the removal of all elements that the Protection System and other automatic controls are expected to disconnect for each Contingency without operator intervention. The analyses shall include the impact of subsequent:","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29795,"TPL-001-5","R3.3.1.1.",null,"Tripping of generators where simulations show generator bus voltages or high side of the generation step up (GSU) voltages are less than known or assumed minimum generator steady state or ride through voltage limitations. Include in the assessment any assumptions made.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29796,"TPL-001-5","R3.3.1.2.",null,"Tripping of Transmission elements where relay loadability limits are exceeded.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29797,"TPL-001-5","R3.3.2.",null,"Simulate the expected automatic operation of existing and planned devices designed to provide steady state control of electrical system quantities when such devices impact the study area. These devices may include equipment such as phase-shifting transformers, load tap changing transformers, and switched capacitors and inductors.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29798,"TPL-001-5","R3.4.",null,"Those planning events in Table 1 that are expected to produce more severe System impacts on its portion of the BES shall be identified, and a list of those Contingencies to be evaluated for System performance in Requirement R3, Part 3.1 created. The rationale for those Contingencies selected for evaluation shall be available as supporting information.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29799,"TPL-001-5","R3.4.1.",null,"The Planning Coordinator and Transmission Planner shall coordinate with adjacent Planning Coordinators and Transmission Planners to ensure that Contingencies on adjacent Systems which may impact their Systems are included in the Contingency list.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29800,"TPL-001-5","R3.5.",null,"Those extreme events in Table 1 that are expected to produce more severe System impacts shall be identified and a list created of those events to be evaluated in Requirement R3, Part 3.2. The rationale for those Contingencies selected for evaluation shall be available as supporting information.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29801,"TPL-001-5","R4.",null,"For the Stability portion of the Planning Assessment, as described in Requirement R2, Parts 2.4 and 2.5, each Transmission Planner and Planning Coordinator shall perform the Contingency analyses listed in Table 1. The studies shall be based on computer simulation models using data provided in Requirement R1. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29802,"TPL-001-5","R4.1.",null,"Studies shall be performed for planning events to determine whether the BES meets the performance requirements in Table 1 based on the Contingency list created in Requirement R4, Part 4.4.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29803,"TPL-001-5","R4.1.1.",null,"For planning event P1: No generating unit shall pull out of synchronism. A generator being disconnected from the System by fault clearing action or by a Remedial Action Scheme is not considered pulling out of synchronism.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29804,"TPL-001-5","R4.1.2.",null,"For planning events P2 through P7: When a generator pulls out of synchronism in the simulations, the resulting apparent impedance swings shall not result in the tripping of any Transmission system elements other than the generating unit and its directly connected Facilities.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29805,"TPL-001-5","R4.1.3.",null,"For planning events P1 through P7: Power oscillations shall exhibit acceptable damping as established by the Planning Coordinator and Transmission Planner.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29806,"TPL-001-5","R4.2.",null,"Studies shall be performed to assess the impact of the extreme events which are identified by the list created in Requirement R4, Part 4.5. If the analysis concludes there is Cascading caused by the occurrence of extreme events, an evaluation of possible actions designed to reduce the likelihood or mitigate the consequences of the event (s) shall be conducted.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29807,"TPL-001-5","R4.3.",null,"Contingency analyses for Requirement R4, Parts 4.1 and 4.2 shall :","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29808,"TPL-001-5","R4.3.1.",null,"Simulate the removal of all elements that the Protection System and other automatic controls are expected to disconnect for each Contingency without operator intervention. The analyses shall include the impact of subsequent:","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29809,"TPL-001-5","R4.3.1.1.",null,"Successful high speed (less than one second) reclosing and unsuccessful high speed reclosing into a Fault where high speed reclosing is utilized.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29810,"TPL-001-5","R4.3.1.2.",null,"Tripping of generators where simulations show generator bus voltages or high side of the GSU voltages are less than known or assumed generator low voltage ride through capability. Include in the assessment any assumptions made.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29811,"TPL-001-5","R4.3.1.3.",null,"Tripping of Transmission lines and transformers where transient swings cause Protection System operation based on generic or actual relay models.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29812,"TPL-001-5","R4.3.2.",null,"Simulate the expected automatic operation of existing and planned devices designed to provide dynamic control of electrical system quantities when such devices impact the study area. These devices may include equipment such as generation exciter control and power system stabilizers, static var compensators, power flow controllers, and DC Transmission controllers.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29813,"TPL-001-5","R4.4.",null,"Those planning events in Table 1 that are expected to produce more severe System impacts on its portion of the BES, shall be identified, and a list created of those Contingencies to be evaluated in Requirement R4, Part 4.1. The rationale for those Contingencies selected for evaluation shall be available as supporting information.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29814,"TPL-001-5","R4.4.1.",null,"Each Planning Coordinator and Transmission Planner shall coordinate with adjacent Planning Coordinators and Transmission Planners to ensure that Contingencies on adjacent Systems which may impact their Systems are included in the Contingency list.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29815,"TPL-001-5","R4.5.",null,"Those extreme events in Table 1 that are expected to produce more severe System impacts shall be identified and a list created of those events to be evaluated in Requirement R4, Part 4.2. The rationale for those Contingencies selected for evaluation shall be available as supporting information.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29816,"TPL-001-5","R5.",null,"Each Transmission Planner and Planning Coordinator shall have criteria for acceptable System steady state voltage limits, post-Contingency voltage deviations, and the transient voltage response for its System. For transient voltage response, the criteria shall at a minimum, specify a low voltage level and a maximum length of time that transient voltages may remain below that level. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29817,"TPL-001-5","R6.",null,"Each Transmission Planner and Planning Coordinator shall define and document, within their Planning Assessment, the criteria or methodology used in the analysis to identify System instability for conditions such as Cascading, voltage instability, or uncontrolled islanding. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29818,"TPL-001-5","R7.",null,"Each Planning Coordinator, in conjunction with each of its Transmission Planners, shall determine and identify each entity’s individual and joint responsibilities for performing the required studies for the Planning Assessment. [Violation Risk Factor: Low] [Time Horizon: Long-term Planning]","2022-07-01",null,"Effective",null,"LOWER","VERY LIKELY","MEDIUM (Targeted Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29819,"TPL-001-5","R8.",null,"Each Planning Coordinator and Transmission Planner shall distribute its Planning Assessment results to adjacent Planning Coordinators and adjacent Transmission Planners within 90 calendar days of completing its Planning Assessment, and to any functional entity that has a reliability related need and submits a written request for the information within 30 days of such a request. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29820,"TPL-001-5","R8.1.",null,"If a recipient of the Planning Assessment results provides documented comments on the results, the respective Planning Coordinator or Transmission Planner shall provide a documented response to that recipient within 90 calendar days of receipt of those comments.","2022-07-01",null,"Effective",null,"MEDIUM","VERY LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TP, PC, PA","No",false,null,false]
[29284,"TPL-002-0(i)b","R1.",null,"The Planning Authority and Transmission Planner shall each demonstrate through a valid assessment that its portion of the interconnected transmission system is planned such that 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 contingency conditions as defined in Category B of Table I.  To be valid, the Planning Authority and Transmission Planner assessments shall:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29285,"TPL-002-0(i)b","R1.1.",null,"Be made annually.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29286,"TPL-002-0(i)b","R1.2.",null,"Be conducted for near-term (years one through five) and longer-term (years six through ten) planning horizons.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29287,"TPL-002-0(i)b","R1.3.",null,"Be supported by a current or past study and/or system simulation testing that addresses each of the following categories, showing system performance following Category B of Table 1 (single contingencies). The specific elements selected (from each of the following categories) for inclusion in these studies and simulations shall be acceptable to the associated Regional Reliability Organization(s).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29288,"TPL-002-0(i)b","R1.3.1.",null,"Be performed and evaluated only for those Category B 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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29289,"TPL-002-0(i)b","R1.3.10.",null,"Include the effects of existing and planned protection systems, including any backup or redundant systems.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29290,"TPL-002-0(i)b","R1.3.11.",null,"Include the effects of existing and planned control devices.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29291,"TPL-002-0(i)b","R1.3.12.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29292,"TPL-002-0(i)b","R1.3.2.",null,"Cover critical system conditions and study years as deemed appropriate by the responsible entity.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29293,"TPL-002-0(i)b","R1.3.3.",null,"Be conducted annually unless changes to system conditions do not warrant such analyses.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29294,"TPL-002-0(i)b","R1.3.4.",null,"Be conducted beyond the five-year horizon only as needed to address identified marginal conditions that may have longer lead-time solutions.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29295,"TPL-002-0(i)b","R1.3.5.",null,"Have all projected firm transfers modeled.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29296,"TPL-002-0(i)b","R1.3.6.",null,"Be performed and evaluated for selected demand levels over the range of forecast system Demands.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29297,"TPL-002-0(i)b","R1.3.7.",null,"Demonstrate that system performance meets Category B contingencies.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29298,"TPL-002-0(i)b","R1.3.8.",null,"Include existing and planned facilities.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29299,"TPL-002-0(i)b","R1.3.9.",null,"Include Reactive Power resources to ensure that adequate reactive resources are available to meet system performance.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29300,"TPL-002-0(i)b","R1.4.",null,"Address any planned upgrades needed to meet the performance requirements of Category B of Table I.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29301,"TPL-002-0(i)b","R1.5.",null,"Consider all contingencies applicable to Category B.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29302,"TPL-002-0(i)b","R2.",null,"When System simulations indicate an inability of the systems to respond as prescribed in Reliability Standard TPL-002-0(i)b_R1, the Planning Authority and Transmission Planner shall each:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29303,"TPL-002-0(i)b","R2.1.",null,"Provide a written summary of its plans to achieve the required system performance as described above throughout the planning horizon:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29304,"TPL-002-0(i)b","R2.1.1.",null,"Including a schedule for implementation.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29305,"TPL-002-0(i)b","R2.1.2.",null,"Including a discussion of expected required in-service dates of facilities.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29306,"TPL-002-0(i)b","R2.1.3.",null,"Consider lead times necessary to implement plans.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29307,"TPL-002-0(i)b","R2.2.",null,"Review, in subsequent annual assessments, (where sufficient lead time exists), the continuing need for identified system facilities.  Detailed implementation plans are not needed.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29308,"TPL-002-0(i)b","R3.",null,"The Planning Authority and Transmission Planner shall each document the results of its Reliability Assessments and corrective plans and shall annually provide the results to its respective Regional Reliability Organization(s), as required by the Regional Reliability Organization.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29309,"TPL-002-1b","R1.",null,"The Planning Authority and Transmission Planner shall each demonstrate through a valid assessment that its portion of the interconnected transmission system is planned such that 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 contingency conditions as defined in Category B of Table I. To be valid, the Planning Authority and Transmission Planner assessments shall:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29310,"TPL-002-1b","R1.1.",null,"Be made annually.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29311,"TPL-002-1b","R1.2.",null,"Be conducted for near-term (years one through five) and longer-term (years six through ten) planning horizons.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29312,"TPL-002-1b","R1.3.",null,"Be supported by a current or past study and/or system simulation testing that addresses each of the following categories, showing system performance following Category B of Table 1 (single contingencies). The specific elements selected (from each of the following categories) for inclusion in these studies and simulations shall be acceptable to the associated Regional Reliability Organization(s).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29313,"TPL-002-1b","R1.3.1.",null,"Be performed and evaluated only for those Category B 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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29322,"TPL-002-1b","R1.3.10.",null,"Include the effects of existing and planned protection systems, including any backup or redundant systems.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29323,"TPL-002-1b","R1.3.11.",null,"Include the effects of existing and planned control devices.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29324,"TPL-002-1b","R1.3.12.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29314,"TPL-002-1b","R1.3.2.",null,"Cover critical system conditions and study years as deemed appropriate by the responsible entity.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29315,"TPL-002-1b","R1.3.3.",null,"Be conducted annually unless changes to system conditions do not warrant such analyses.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29316,"TPL-002-1b","R1.3.4.",null,"Be conducted beyond the five-year horizon only as needed to address identified marginal conditions that may have longer lead-time solutions.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29317,"TPL-002-1b","R1.3.5.",null,"Have all projected firm transfers modeled.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29318,"TPL-002-1b","R1.3.6.",null,"Be performed and evaluated for selected demand levels over the range of forecast system Demands.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29319,"TPL-002-1b","R1.3.7.",null,"Demonstrate that system performance meets Category B contingencies.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29320,"TPL-002-1b","R1.3.8.",null,"Include existing and planned facilities.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29321,"TPL-002-1b","R1.3.9.",null,"Include Reactive Power resources to ensure that adequate reactive resources are available to meet system performance.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29325,"TPL-002-1b","R1.4.",null,"Address any planned upgrades needed to meet the performance requirements of Category B of Table I.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29340,"TPL-002-1b","R1.5.",null,"Consider all contingencies applicable to Category B.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29341,"TPL-002-1b","R2.",null,"When System simulations indicate an inability of the systems to respond as prescribed in Reliability Standard TPL-002-1_R1, the Planning Authority and Transmission Planner shall each:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29342,"TPL-002-1b","R2.1.",null,"Provide a written summary of its plans to achieve the required system performance as described above throughout the planning horizon:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29343,"TPL-002-1b","R2.1.1.",null,"Including a schedule for implementation.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29344,"TPL-002-1b","R2.1.2.",null,"Including a discussion of expected required in-service dates of facilities.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29345,"TPL-002-1b","R2.1.3.",null,"Consider lead times necessary to implement plans.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29346,"TPL-002-1b","R2.2.",null,"Review, in subsequent annual assessments, (where sufficient lead time exists), the continuing need for identified system facilities. Detailed implementation plans are not needed.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29347,"TPL-002-1b","R3.",null,"The Planning Authority and Transmission Planner shall each document the results of its Reliability Assessments and corrective plans and shall annually provide the results to its respective Regional Reliability Organization(s), as required by the Regional Reliability Organization.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29348,"TPL-002-2b","R1.",null,"The Planning Authority and Transmission Planner shall each demonstrate through a valid assessment that its portion of the interconnected transmission system is planned such that 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 contingency conditions as defined in Category B of Table I. To be valid, the Planning Authority and Transmission Planner assessments shall:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29349,"TPL-002-2b","R1.1.",null,"Be made annually.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29350,"TPL-002-2b","R1.2.",null,"Be conducted for near-term (years one through five) and longer-term (years six through ten) planning horizons.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29351,"TPL-002-2b","R1.3.",null,"Be supported by a current or past study and/or system simulation testing that addresses each of the following categories, showing system performance following Category B of Table 1 (single contingencies). The specific elements selected (from\neach of the following categories) for inclusion in these studies and simulations shall be acceptable to the associated Regional Reliability Organization(s).",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29352,"TPL-002-2b","R1.3.1.",null,"Be performed and evaluated only for those Category B 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\ninformation.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29361,"TPL-002-2b","R1.3.10.",null,"Include the effects of existing and planned protection systems, including any backup or redundant systems.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29362,"TPL-002-2b","R1.3.11.",null,"Include the effects of existing and planned control devices.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29363,"TPL-002-2b","R1.3.12.",null,"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.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29353,"TPL-002-2b","R1.3.2.",null,"Cover critical system conditions and study years as deemed appropriate by the responsible entity.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29354,"TPL-002-2b","R1.3.3.",null,"Be conducted annually unless changes to system conditions do not warrant such analyses.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29355,"TPL-002-2b","R1.3.4.",null,"Be conducted beyond the five-year horizon only as needed to address identified marginal conditions that may have longer lead-time solutions.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29356,"TPL-002-2b","R1.3.5.",null,"Have all projected firm transfers modeled.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29357,"TPL-002-2b","R1.3.6.",null,"Be performed and evaluated for selected demand levels over the range of forecast system Demands.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29358,"TPL-002-2b","R1.3.7.",null,"Demonstrate that system performance meets Category B contingencies.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29359,"TPL-002-2b","R1.3.8.",null,"Include existing and planned facilities.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29360,"TPL-002-2b","R1.3.9.",null,"Include Reactive Power resources to ensure that adequate reactive resources are available to meet system performance.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29364,"TPL-002-2b","R1.4.",null,"Address any planned upgrades needed to meet the performance requirements of Category B of Table I.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29365,"TPL-002-2b","R1.5.",null,"Consider all contingencies applicable to Category B.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29366,"TPL-002-2b","R2.",null,"When System simulations indicate an inability of the systems to respond as prescribed in Reliability Standard TPL-002-1_R1, the Planning Authority and Transmission Planner shall each:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29367,"TPL-002-2b","R2.1.",null,"Provide a written summary of its plans to achieve the required system performance as described above throughout the planning horizon:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29368,"TPL-002-2b","R2.1.1.",null,"Including a schedule for implementation.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29369,"TPL-002-2b","R2.1.2.",null,"Including a discussion of expected required in-service dates of facilities.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29370,"TPL-002-2b","R2.1.3.",null,"Consider lead times necessary to implement plans.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29371,"TPL-002-2b","R2.2.",null,"Review, in subsequent annual assessments, (where sufficient lead time exists), the continuing need for identified system facilities. Detailed implementation plans are not needed.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29372,"TPL-002-2b","R3.",null,"The Planning Authority and Transmission Planner shall each document the results of its Reliability Assessments and corrective plans and shall annually provide the results to its respective Regional Reliability Organization(s), as required by the Regional Reliability Organization.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29373,"TPL-003-0(i)b","R1.",null,"The Planning Authority and Transmission Planner shall each demonstrate through a valid assessment that its portion of the interconnected transmission systems is planned such that 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 contingency conditions as defined in Category C of Table I (attached). The controlled interruption of customer Demand, the planned removal of generators, or the Curtailment of firm (non-recallable reserved) power transfers may be\nnecessary to meet this standard. To be valid, the Planning Authority and Transmission Planner assessments shall:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29374,"TPL-003-0(i)b","R1.1.",null,"Be made annually.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29375,"TPL-003-0(i)b","R1.2.",null,"Be conducted for near-term (years one through five) and longer-term (years six through ten) planning horizons.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29376,"TPL-003-0(i)b","R1.3.",null,"Be supported by a current or past study and/or system simulation testing that addresses each of the following categories, showing system performance following Category C of Table 1 (multiple contingencies). The specific elements selected (from\neach of the following categories) for inclusion in these studies and simulations shall be acceptable to the associated Regional Reliability Organization(s).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29377,"TPL-003-0(i)b","R1.3.1.",null,"Be performed and evaluated only for those Category C 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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29386,"TPL-003-0(i)b","R1.3.10.",null,"Include the effects of existing and planned protection systems, including any backup or redundant systems.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29387,"TPL-003-0(i)b","R1.3.11.",null,"Include the effects of existing and planned control devices.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29388,"TPL-003-0(i)b","R1.3.12.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29378,"TPL-003-0(i)b","R1.3.2.",null,"Cover critical system conditions and study years as deemed appropriate by the responsible entity.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29379,"TPL-003-0(i)b","R1.3.3.",null,"Be conducted annually unless changes to system conditions do not warrant such analyses.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29380,"TPL-003-0(i)b","R1.3.4.",null,"Be conducted beyond the five-year horizon only as needed to address identified marginal conditions that may have longer lead-time solutions.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29381,"TPL-003-0(i)b","R1.3.5.",null,"Have all projected firm transfers modeled.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29382,"TPL-003-0(i)b","R1.3.6.",null,"Be performed and evaluated for selected demand levels over the range of forecast system demands.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29383,"TPL-003-0(i)b","R1.3.7.",null,"Demonstrate that System performance meets Table 1 for Category C contingencies.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29384,"TPL-003-0(i)b","R1.3.8.",null,"Include existing and planned facilities.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29385,"TPL-003-0(i)b","R1.3.9.",null,"Include Reactive Power resources to ensure that adequate reactive resources are available to meet System performance.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29389,"TPL-003-0(i)b","R1.4.",null,"Address any planned upgrades needed to meet the performance requirements of Category C.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29390,"TPL-003-0(i)b","R1.5.",null,"Consider all contingencies applicable to Category C.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29391,"TPL-003-0(i)b","R2.",null,"When system simulations indicate an inability of the systems to respond as prescribed in Reliability Standard TPL-003-0(i)b_R1, the Planning Authority and Transmission Planner shall each:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29392,"TPL-003-0(i)b","R2.1.",null,"Provide a written summary of its plans to achieve the required system performance as described above throughout the planning horizon:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29393,"TPL-003-0(i)b","R2.1.1.",null,"Including a schedule for implementation.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29394,"TPL-003-0(i)b","R2.1.2.",null,"Including a discussion of expected required in-service dates of facilities.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29395,"TPL-003-0(i)b","R2.1.3.",null,"Consider lead times necessary to implement plans.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29396,"TPL-003-0(i)b","R2.2.",null,"Review, in subsequent annual assessments, (where sufficient lead time exists), the continuing need for identified system facilities. Detailed implementation plans are not needed.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29397,"TPL-003-0(i)b","R3.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29398,"TPL-003-1a","R1.",null,"The Planning Authority and Transmission Planner shall each demonstrate through a valid assessment that its portion of the interconnected transmission systems is planned such that 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 contingency conditions as defined in Category C of Table I (attached). The controlled interruption of customer Demand, the planned removal of generators, or the Curtailment of firm (non-recallable reserved) power transfers may be necessary to meet this standard. To be valid, the Planning Authority and Transmission Planner assessments shall:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29399,"TPL-003-1a","R1.1.",null,"Be made annually.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29400,"TPL-003-1a","R1.2.",null,"Be conducted for near-term (years one through five) and longer-term (years six through ten) planning horizons.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29401,"TPL-003-1a","R1.3.",null,"Be supported by a current or past study and/or system simulation testing that addresses each of the following categories, showing system performance following Category C of Table 1 (multiple contingencies). The specific elements selected (from each of the following categories) for inclusion in these studies and simulations shall be acceptable to the associated Regional Reliability Organization(s).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29402,"TPL-003-1a","R1.3.1.",null,"Be performed and evaluated only for those Category C 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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29411,"TPL-003-1a","R1.3.10.",null,"Include the effects of existing and planned protection systems, including any backup or redundant systems.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29412,"TPL-003-1a","R1.3.11.",null,"Include the effects of existing and planned control devices.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29413,"TPL-003-1a","R1.3.12.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29403,"TPL-003-1a","R1.3.2.",null,"Cover critical system conditions and study years as deemed appropriate by the responsible entity.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29404,"TPL-003-1a","R1.3.3.",null,"Be conducted annually unless changes to system conditions do not warrant such analyses.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29405,"TPL-003-1a","R1.3.4.",null,"Be conducted beyond the five-year horizon only as needed to address identified marginal conditions that may have longer lead-time solutions.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29406,"TPL-003-1a","R1.3.5.",null,"Have all projected firm transfers modeled.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29407,"TPL-003-1a","R1.3.6.",null,"Be performed and evaluated for selected demand levels over the range of forecast system demands.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29408,"TPL-003-1a","R1.3.7.",null,"Demonstrate that System performance meets Table 1 for Category C contingencies.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29409,"TPL-003-1a","R1.3.8.",null,"Include existing and planned facilities.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29410,"TPL-003-1a","R1.3.9.",null,"Include Reactive Power resources to ensure that adequate reactive resources are available to meet System performance.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29414,"TPL-003-1a","R1.4.",null,"Address any planned upgrades needed to meet the performance requirements of Category C.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29415,"TPL-003-1a","R1.5.",null,"Consider all contingencies applicable to Category C.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29416,"TPL-003-1a","R2.",null,"When system simulations indicate an inability of the systems to respond as prescribed in Reliability Standard TPL-003-1_R1, the Planning Authority and Transmission Planner shall each:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29417,"TPL-003-1a","R2.1.",null,"Provide a written summary of its plans to achieve the required system performance as described above throughout the planning horizon:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29418,"TPL-003-1a","R2.1.1.",null,"Including a schedule for implementation.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29419,"TPL-003-1a","R2.1.2.",null,"Including a discussion of expected required in-service dates of facilities.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29420,"TPL-003-1a","R2.1.3.",null,"Consider lead times necessary to implement plans.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29421,"TPL-003-1a","R2.2.",null,"Review, in subsequent annual assessments, (where sufficient lead time exists), the continuing need for identified system facilities. Detailed implementation plans are not needed.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29422,"TPL-003-1a","R3.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29423,"TPL-003-2a","R1.",null,"The Planning Authority and Transmission Planner shall each demonstrate through a valid assessment that its portion of the interconnected transmission systems is planned such that 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\nsystem demands, under the contingency conditions as defined in Category C of Table I (attached). The controlled interruption of customer Demand, the planned removal of generators, or the Curtailment of firm (non-recallable reserved) power transfers may be\nnecessary to meet this standard. To be valid, the Planning Authority and Transmission Planner assessments shall:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29424,"TPL-003-2a","R1.1.",null,"Be made annually.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29425,"TPL-003-2a","R1.2.",null,"Be conducted for near-term (years one through five) and longer-term (years six through ten) planning horizons.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29426,"TPL-003-2a","R1.3.",null,"Be supported by a current or past study and/or system simulation testing that addresses each of the following categories, showing system performance following Category C of Table 1 (multiple contingencies). The specific elements selected (from\neach of the following categories) for inclusion in these studies and simulations shall be acceptable to the associated Regional Reliability Organization(s).",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29427,"TPL-003-2a","R1.3.1.",null,"Be performed and evaluated only for those Category C 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.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29436,"TPL-003-2a","R1.3.10.",null,"Include the effects of existing and planned protection systems, including any backup or redundant systems.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29437,"TPL-003-2a","R1.3.11.",null,"Include the effects of existing and planned control devices.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29438,"TPL-003-2a","R1.3.12.",null,"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.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29428,"TPL-003-2a","R1.3.2.",null,"Cover critical system conditions and study years as deemed appropriate by the responsible entity.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29429,"TPL-003-2a","R1.3.3.",null,"Be conducted annually unless changes to system conditions do not warrant such analyses.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29430,"TPL-003-2a","R1.3.4.",null,"Be conducted beyond the five-year horizon only as needed to address identified marginal conditions that may have longer lead-time solutions.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29431,"TPL-003-2a","R1.3.5.",null,"Have all projected firm transfers modeled.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29432,"TPL-003-2a","R1.3.6.",null,"Be performed and evaluated for selected demand levels over the range of forecast system demands.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29433,"TPL-003-2a","R1.3.7.",null,"Demonstrate that System performance meets Table 1 for Category C contingencies.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29434,"TPL-003-2a","R1.3.8.",null,"Include existing and planned facilities.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29435,"TPL-003-2a","R1.3.9.",null,"Include Reactive Power resources to ensure that adequate reactive resources are available to meet System performance.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29439,"TPL-003-2a","R1.4.",null,"Address any planned upgrades needed to meet the performance requirements of Category C.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29440,"TPL-003-2a","R1.5.",null,"Consider all contingencies applicable to Category C.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29441,"TPL-003-2a","R2.",null,"When system simulations indicate an inability of the systems to respond as prescribed in Reliability Standard TPL-003-2_R1, the Planning Authority and Transmission Planner shall each:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29326,"TPL-003-2a","R2.1.",null,"Provide a written summary of its plans to achieve the required system performance as described above throughout the planning horizon:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29327,"TPL-003-2a","R2.1.1.",null,"Including a schedule for implementation.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29328,"TPL-003-2a","R2.1.2.",null,"Including a discussion of expected required in-service dates of facilities.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29329,"TPL-003-2a","R2.1.3.",null,"Consider lead times necessary to implement plans.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29330,"TPL-003-2a","R2.2.",null,"Review, in subsequent annual assessments, (where sufficient lead time exists), the continuing need for identified system facilities. Detailed implementation plans are not needed.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29331,"TPL-003-2a","R3.",null,"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.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29442,"TPL-003-2b","R1.",null,"The Planning Authority and Transmission Planner shall each demonstrate through a valid assessment that its portion of the interconnected transmission systems is planned such that 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 contingency conditions as defined in Category C of Table I (attached). The controlled interruption of customer Demand, the planned removal of generators, or the Curtailment of firm (non-recallable reserved) power transfers may be\nnecessary to meet this standard. To be valid, the Planning Authority and Transmission Planner assessments shall:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29443,"TPL-003-2b","R1.1.",null,"Be made annually.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29444,"TPL-003-2b","R1.2.",null,"Be conducted for near-term (years one through five) and longer-term (years six through ten) planning horizons.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29445,"TPL-003-2b","R1.3.",null,"Be supported by a current or past study and/or system simulation testing that addresses each of the following categories, showing system performance following Category C of Table 1 (multiple contingencies). The specific elements selected (from\neach of the following categories) for inclusion in these studies and simulations shall be acceptable to the associated Regional Reliability Organization(s).",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29446,"TPL-003-2b","R1.3.1.",null,"Be performed and evaluated only for those Category C 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.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29455,"TPL-003-2b","R1.3.10.",null,"Include the effects of existing and planned protection systems, including any backup or redundant systems.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29456,"TPL-003-2b","R1.3.11.",null,"Include the effects of existing and planned control devices.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29457,"TPL-003-2b","R1.3.12.",null,"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.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29447,"TPL-003-2b","R1.3.2.",null,"Cover critical system conditions and study years as deemed appropriate by the responsible entity.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29448,"TPL-003-2b","R1.3.3.",null,"Be conducted annually unless changes to system conditions do not warrant such analyses.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29449,"TPL-003-2b","R1.3.4.",null,"Be conducted beyond the five-year horizon only as needed to address identified marginal conditions that may have longer lead-time solutions.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29450,"TPL-003-2b","R1.3.5.",null,"Have all projected firm transfers modeled.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29451,"TPL-003-2b","R1.3.6.",null,"Be performed and evaluated for selected demand levels over the range of forecast system demands.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29452,"TPL-003-2b","R1.3.7.",null,"Demonstrate that System performance meets Table 1 for Category C contingencies.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29453,"TPL-003-2b","R1.3.8.",null,"Include existing and planned facilities.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29454,"TPL-003-2b","R1.3.9.",null,"Include Reactive Power resources to ensure that adequate reactive resources are available to meet System performance.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29458,"TPL-003-2b","R1.4.",null,"Address any planned upgrades needed to meet the performance requirements of Category C.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29459,"TPL-003-2b","R1.5.",null,"Consider all contingencies applicable to Category C.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29460,"TPL-003-2b","R2.",null,"When system simulations indicate an inability of the systems to respond as prescribed in Reliability Standard TPL-003-2_R1, the Planning Authority and Transmission Planner shall each:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29461,"TPL-003-2b","R2.1.",null,"Provide a written summary of its plans to achieve the required system performance as described above throughout the planning horizon:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29462,"TPL-003-2b","R2.1.1.",null,"Including a schedule for implementation.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29463,"TPL-003-2b","R2.1.2.",null,"Including a discussion of expected required in-service dates of facilities.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29464,"TPL-003-2b","R2.1.3.",null,"Consider lead times necessary to implement plans.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29465,"TPL-003-2b","R2.2.",null,"Review, in subsequent annual assessments, (where sufficient lead time exists), the continuing need for identified system facilities. Detailed implementation plans are not needed.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29466,"TPL-003-2b","R3.",null,"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.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29467,"TPL-004-0(i)a","R1.",null,"The Planning Authority and Transmission Planner shall each demonstrate through a valid 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 Authority’s and Transmission Planner’s\nassessment shall:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29468,"TPL-004-0(i)a","R1.1.",null,"Be made annually.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29469,"TPL-004-0(i)a","R1.2.",null,"Be conducted for near-term (years one through five).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29470,"TPL-004-0(i)a","R1.3.",null,"Be supported by a current or past study and/or system simulation testing that addresses each of the following categories, showing system performance following Category D contingencies of Table I. The specific elements selected (from within\neach of the following categories) for inclusion in these studies and simulations shall be acceptable to the associated Regional Reliability Organization(s).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29471,"TPL-004-0(i)a","R1.3.1.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29472,"TPL-004-0(i)a","R1.3.2.",null,"Cover critical system conditions and study years as deemed appropriate by the responsible entity.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29473,"TPL-004-0(i)a","R1.3.3.",null,"Be conducted annually unless changes to system conditions do not warrant such analyses.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29474,"TPL-004-0(i)a","R1.3.4.",null,"Have all projected firm transfers modeled.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29475,"TPL-004-0(i)a","R1.3.5.",null,"Include existing and planned facilities.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29476,"TPL-004-0(i)a","R1.3.6.",null,"Include Reactive Power resources to ensure that adequate reactive resources are available to meet system performance.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29477,"TPL-004-0(i)a","R1.3.7.",null,"Include the effects of existing and planned protection systems, including any backup or redundant systems.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29478,"TPL-004-0(i)a","R1.3.8.",null,"Include the effects of existing and planned control devices.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29479,"TPL-004-0(i)a","R1.3.9.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29480,"TPL-004-0(i)a","R1.4.",null,"Consider all contingencies applicable to Category D.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29481,"TPL-004-0(i)a","R2.",null,"The Planning Authority and Transmission Planner shall each document the results of its reliability assessments and shall annually provide the results to its entities’ respective NERC Regional Reliability Organization(s), as required by the Regional Reliability Organization.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29482,"TPL-004-1","R1.",null,"The Planning Authority and Transmission Planner shall each demonstrate through a valid 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 Authority’s and Transmission Planner’s assessment shall:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29483,"TPL-004-1","R1.1.",null,"Be made annually.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29484,"TPL-004-1","R1.2.",null,"Be conducted for near-term (years one through five).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29485,"TPL-004-1","R1.3.",null,"Be supported by a current or past study and/or system simulation testing that addresses each of the following categories, showing system performance following Category D contingencies of Table I. The specific elements selected (from within each of the following categories) for inclusion in these studies and simulations shall be acceptable to the associated Regional Reliability Organization(s).",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29486,"TPL-004-1","R1.3.1.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29487,"TPL-004-1","R1.3.2.",null,"Cover critical system conditions and study years as deemed appropriate by the responsible entity.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29488,"TPL-004-1","R1.3.3.",null,"Be conducted annually unless changes to system conditions do not warrant such analyses.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29489,"TPL-004-1","R1.3.4.",null,"Have all projected firm transfers modeled.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29490,"TPL-004-1","R1.3.5.",null,"Include existing and planned facilities.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29491,"TPL-004-1","R1.3.6.",null,"Include Reactive Power resources to ensure that adequate reactive resources are available to meet system performance.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29492,"TPL-004-1","R1.3.7.",null,"Include the effects of existing and planned protection systems, including any backup or redundant systems.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29493,"TPL-004-1","R1.3.8.",null,"Include the effects of existing and planned control devices.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29494,"TPL-004-1","R1.3.9.",null,"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.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29495,"TPL-004-1","R1.4.",null,"Consider all contingencies applicable to Category D.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29496,"TPL-004-1","R2.",null,"The Planning Authority and Transmission Planner shall each document the results of its reliability assessments and shall annually provide the results to its entities’ respective NERC Regional Reliability Organization(s), as required by the Regional Reliability Organization.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TP, PA","No",false,null,false]
[29497,"TPL-004-2","R1.",null,"The Planning Authority and Transmission Planner shall each demonstrate through a valid 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 Authority’s and Transmission Planner’s\nassessment shall:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29498,"TPL-004-2","R1.1.",null,"Be made annually.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29499,"TPL-004-2","R1.2.",null,"Be conducted for near-term (years one through five).",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29500,"TPL-004-2","R1.3.",null,"Be supported by a current or past study and/or system simulation testing that addresses each of the following categories, showing system performance following Category D contingencies of Table I. The specific elements selected (from within\neach of the following categories) for inclusion in these studies and simulations shall be acceptable to the associated Regional Reliability Organization(s).",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29501,"TPL-004-2","R1.3.1.",null,"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.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29502,"TPL-004-2","R1.3.2.",null,"Cover critical system conditions and study years as deemed appropriate by the responsible entity.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29503,"TPL-004-2","R1.3.3.",null,"Be conducted annually unless changes to system conditions do not warrant such analyses.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29504,"TPL-004-2","R1.3.4.",null,"Have all projected firm transfers modeled.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29505,"TPL-004-2","R1.3.5.",null,"Include existing and planned facilities.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29506,"TPL-004-2","R1.3.6.",null,"Include Reactive Power resources to ensure that adequate reactive resources are available to meet system performance.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29507,"TPL-004-2","R1.3.7.",null,"Include the effects of existing and planned protection systems, including any backup or redundant systems.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29508,"TPL-004-2","R1.3.8.",null,"Include the effects of existing and planned control devices.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29509,"TPL-004-2","R1.3.9.",null,"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.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29510,"TPL-004-2","R1.4.",null,"Consider all contingencies applicable to Category D.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29511,"TPL-004-2","R2.",null,"The Planning Authority and Transmission Planner shall each document the results of its reliability assessments and shall annually provide the results to its entities’ respective NERC Regional Reliability Organization(s), as required by the Regional Reliability Organization.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29512,"TPL-004-2a","R1.",null,"The Planning Authority and Transmission Planner shall each demonstrate through a valid 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 Authority’s and Transmission Planner’s\nassessment shall:",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29513,"TPL-004-2a","R1.1.",null,"Be made annually",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29514,"TPL-004-2a","R1.2.",null,"Be conducted for near-term (years one through five).",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29515,"TPL-004-2a","R1.3.",null,"Be supported by a current or past study and/or system simulation testing that addresses each of the following categories, showing system performance following Category D contingencies of Table I. The specific elements selected (from within\neach of the following categories) for inclusion in these studies and simulations shall be acceptable to the associated Regional Reliability Organization(s).",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29516,"TPL-004-2a","R1.3.1.",null,"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.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29517,"TPL-004-2a","R1.3.2.",null,"Cover critical system conditions and study years as deemed appropriate by the responsible entity.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29518,"TPL-004-2a","R1.3.3.",null,"Be conducted annually unless changes to system conditions do not warrant such analyses.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29519,"TPL-004-2a","R1.3.4.",null,"Have all projected firm transfers modeled.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29520,"TPL-004-2a","R1.3.5.",null,"Include existing and planned facilities.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29521,"TPL-004-2a","R1.3.6.",null,"Include Reactive Power resources to ensure that adequate reactive resources are available to meet system performance.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29522,"TPL-004-2a","R1.3.7.",null,"Include the effects of existing and planned protection systems, including any backup or redundant systems.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29523,"TPL-004-2a","R1.3.8.",null,"Include the effects of existing and planned control devices.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29524,"TPL-004-2a","R1.3.9.",null,"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.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29525,"TPL-004-2a","R1.4.",null,"Consider all contingencies applicable to Category D.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29526,"TPL-004-2a","R2.",null,"The Planning Authority and Transmission Planner shall each document the results of its reliability assessments and shall annually provide the results to its entities’ respective NERC Regional Reliability Organization(s), as required by the Regional Reliability Organization.",null,null,"Never Came Into Effect in Ontario",{"$nulls":3},"N/A",null,"N/A","TP, PC, PA","No",false,null,false]
[29527,"TPL-007-1","R1.",null,"Each Planning Coordinator, in conjunction with its Transmission Planner(s), shall identify the individual and joint responsibilities of the Planning Coordinator and Transmission Planner(s) in the Planning Coordinator’s planning area for maintaining models and performing the study or studies needed to complete GMD Vulnerability Assessment(s). [Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2017-07-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29528,"TPL-007-1","R2.",null,"Each responsible entity, as determined in Requirement R1, shall maintain System models and GIC System models of the responsible entity’s planning area for performing the study or studies needed to complete GMD Vulnerability Assessment(s). [Violation Risk Factor: High] [Time Horizon: Long-term Planning]","2018-07-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29529,"TPL-007-1","R3.",null,"Each responsible entity, as determined in Requirement R1, shall have criteria for acceptable System steady state voltage performance for its System during the benchmark GMD event described in Attachment 1. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2022-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29530,"TPL-007-1","R4.",null,"Each responsible entity, as determined in Requirement R1, shall complete a GMD Vulnerability Assessment of the Near-Term Transmission Planning Horizon once every 60 calendar months. This GMD Vulnerability Assessment shall use a study or studies based on models identified in Requirement R2, document assumptions, and document summarized results of the steady state analysis. [Violation Risk Factor: High] [Time Horizon: Long-term Planning]","2022-01-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29531,"TPL-007-1","R4.1.",null,"The study or studies shall include the following conditions:","2022-01-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29532,"TPL-007-1","R4.1.1.",null,"System On-Peak Load for at least one year within the Near-Term Transmission Planning Horizon; and","2022-01-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29533,"TPL-007-1","R4.1.2.",null,"System Off-Peak Load for at least one year within the Near-Term Transmission Planning Horizon.","2022-01-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29534,"TPL-007-1","R4.2.",null,"The study or studies shall be conducted based on the benchmark GMD event described in Attachment 1 to determine whether the System meets the performance requirements in Table 1.","2022-01-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29535,"TPL-007-1","R4.3.",null,"The GMD Vulnerability Assessment shall be provided within 90 calendar days of completion to the responsible entity’s Reliability Coordinator, adjacent Planning Coordinators, adjacent Transmission Planners, and to any functional entity that submits a written request and has a reliability-related need.","2022-01-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29536,"TPL-007-1","R4.3.1.",null,"If a recipient of the GMD Vulnerability Assessment provides documented comments on the results, the responsible entity shall provide a documented response to that recipient within 90 calendar days of receipt of those comments.","2022-01-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29537,"TPL-007-1","R5.",null,"Each responsible entity, as determined in Requirement R1, shall provide GIC flow information to be used for the transformer thermal impact assessment specified in Requirement R6 to each Transmission Owner and Generator Owner that owns an applicable Bulk Electric System (BES) power transformer in the planning area. The GIC flow information shall include: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2019-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29538,"TPL-007-1","R5.1.",null,"The maximum effective GIC value for the worst case geoelectric field orientation for the benchmark GMD event described in Attachment 1. This value shall be provided to the Transmission Owner or Generator Owner that owns each applicable BES power transformer in the planning area.","2019-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29539,"TPL-007-1","R5.2.",null,"The effective GIC time series, GIC(t), calculated using the benchmark GMD event described in Attachment 1 in response to a written request from the Transmission Owner or Generator Owner that owns an applicable BES power transformer in the planning area. GIC(t) shall be provided within 90 calendar days of receipt of the written request and after determination of the maximum effective GIC value in Part 5.1.","2019-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29540,"TPL-007-1","R6.",null,"Each Transmission Owner and Generator Owner shall conduct a thermal impact assessment for its solely and jointly owned applicable BES power transformers where the maximum effective GIC value provided in Requirement R5, Part 5.1, is 75 A per phase or greater. The thermal impact assessment shall: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[29541,"TPL-007-1","R6.1.",null,"Be based on the effective GIC flow information provided in Requirement R5;","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[29542,"TPL-007-1","R6.2.",null,"Document assumptions used in the analysis;","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[29543,"TPL-007-1","R6.3.",null,"Describe suggested actions and supporting analysis to mitigate the impact of GICs, if any; and","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[29544,"TPL-007-1","R6.4.",null,"Be performed and provided to the responsible entities, as determined in Requirement R1, within 24 calendar months of receiving GIC flow information specified in Requirement R5, Part 5.1.","2021-01-01",null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[29545,"TPL-007-1","R7.",null,"Each responsible entity, as determined in Requirement R1, that concludes, through the GMD Vulnerability Assessment conducted in Requirement R4, that their System does not meet the performance requirements of Table 1 shall develop a Corrective Action Plan addressing how the performance requirements will be met. The Corrective Action Plan shall: [Violation Risk Factor: High] [Time Horizon: Long-term Planning]","2022-01-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29546,"TPL-007-1","R7.1.",null,"List System deficiencies and the associated actions needed to achieve required System performance. Examples of such actions include:\n Installation, modification, retirement, or removal of Transmission and generation Facilities and any associated equipment.\n Installation, modification, or removal of Protection Systems or Special Protection Systems.\n Use of Operating Procedures, specifying how long they will be needed as part of the Corrective Action Plan.\n Use of Demand-Side Management, new technologies, or other initiatives.","2022-01-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29547,"TPL-007-1","R7.2.",null,"Be reviewed in subsequent GMD Vulnerability Assessments until it is determined that the System meets the performance requirements contained in Table 1.","2022-01-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29548,"TPL-007-1","R7.3.",null,"Be provided within 90 calendar days of completion to the responsible entity’s Reliability Coordinator, adjacent Planning Coordinator(s), adjacent Transmission Planner(s), functional entities referenced in the Corrective Action Plan, and any functional entity that submits a written request and has a reliability-related need.","2022-01-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29549,"TPL-007-1","R7.3.1.",null,"If a recipient of the Corrective Action Plan provides documented comments on the results, the responsible entity shall provide a documented response to that recipient within 90 calendar days of receipt of those comments.","2022-01-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29572,"TPL-007-2","R1.",null,"Each Planning Coordinator, in conjunction with its Transmission Planner(s), shall identify the individual and joint responsibilities of the Planning Coordinator and Transmission Planner(s) in the Planning Coordinator’s planning area for maintaining models, performing the study or studies needed to complete benchmark and supplemental GMD Vulnerability Assessments, and implementing process(es) to obtain GMD measurement data as specified in this standard.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29613,"TPL-007-2","R10.",null,"Each Transmission Owner and Generator Owner shall conduct a supplemental thermal impact assessment for its solely and jointly owned applicable BES power transformers where the maximum effective GIC value provided in Requirement R9, Part 9.1, is 85 A per phase or greater. The supplemental thermal impact assessment shall:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[29614,"TPL-007-2","R10.1.",null,"Be based on the effective GIC flow information provided in Requirement R9;",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[29615,"TPL-007-2","R10.2.",null,"Document assumptions used in the analysis;",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[29616,"TPL-007-2","R10.3.",null,"Describe suggested actions and supporting analysis to mitigate the impact of GICs, if any; and",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[29617,"TPL-007-2","R10.4.",null,"Be performed and provided to the responsible entities, as determined in Requirement R1, within 24 calendar months of receiving GIC flow information specified in Requirement R9, Part 9.1.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[29618,"TPL-007-2","R11.",null,"Each responsible entity, as determined in Requirement R1, shall implement a process to obtain GIC monitor data from at least one GIC monitor located in the Planning Coordinator's planning area or other part of the system included in the Planning Coordinator's GIC System model.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29619,"TPL-007-2","R12.",null,"Each responsible entity, as determined in Requirement R1, shall implement a process to obtain geomagnetic field data for its Planning Coordinator’s planning area.",null,null,"Never Came Into Effect in Ontario",null,"LOWER",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29573,"TPL-007-2","R2.",null,"Each responsible entity, as determined in Requirement R1, shall maintain System models and GIC System models of the responsible entity’s planning area for performing the study or studies needed to complete benchmark and supplemental GMD Vulnerability Assessments.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29574,"TPL-007-2","R3.",null,"Each responsible entity, as determined in Requirement R1, shall have criteria for acceptable System steady state voltage performance for its System during the GMD events described in Attachment 1.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29575,"TPL-007-2","R4.",null,"Each responsible entity, as determined in Requirement R1, shall complete a benchmark GMD Vulnerability Assessment of the Near-Term Transmission Planning Horizon at least once every 60 calendar months. This benchmark GMD Vulnerability Assessment shall use a study or studies based on models identified in Requirement R2, document assumptions, and document summarized results of the steady state analysis.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29576,"TPL-007-2","R4.1.",null,"The study or studies shall include the following conditions:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29577,"TPL-007-2","R4.1.1.",null,"System On-Peak Load for at least one year within the Near-Term Transmission Planning Horizon; and",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29578,"TPL-007-2","R4.1.2.",null,"System Off-Peak Load for at least one year within the Near-Term Transmission Planning Horizon.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29579,"TPL-007-2","R4.2.",null,"The study or studies shall be conducted based on the benchmark GMD event described in Attachment 1 to determine whether the System meets the performance requirements for the steady state planning benchmark GMD event contained in Table 1.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29580,"TPL-007-2","R4.3.",null,"The benchmark GMD Vulnerability Assessment shall be provided: (i) to the responsible entity’s Reliability Coordinator, adjacent Planning Coordinators, and adjacent Transmission Planners within 90 calendar days of completion, and (ii) to any functional entity that submits a written request and has a reliability-related need within 90 calendar days of receipt of such request or within 90 calendar days of completion of the benchmark GMD Vulnerability Assessment, whichever is later.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29581,"TPL-007-2","R4.3.1.",null,"If a recipient of the benchmark GMD Vulnerability Assessment provides documented comments on the results, the responsible entity shall provide a documented response to that recipient within 90 calendar days of receipt of those comments.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29582,"TPL-007-2","R5.",null,"Each responsible entity, as determined in Requirement R1, shall provide GIC flow information to be used for the benchmark thermal impact assessment of transformers specified in Requirement R6 to each Transmission Owner and Generator Owner that owns an applicable Bulk Electric System (BES) power transformer in the planning area. The GIC flow information shall include:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29583,"TPL-007-2","R5.1.",null,"The maximum effective GIC value for the worst case geoelectric field orientation for the benchmark GMD event described in Attachment 1. This value shall be provided to the Transmission Owner or Generator Owner that owns each applicable BES power transformer in the planning area.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29584,"TPL-007-2","R5.2.",null,"The effective GIC time series, GIC(t), calculated using the benchmark GMD event described in Attachment 1 in response to a written request from the Transmission Owner or Generator Owner that owns an applicable BES power transformer in the planning area. GIC(t) shall be provided within 90 calendar days of receipt of the written request and after determination of the maximum effective GIC value in Part 5.1.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29585,"TPL-007-2","R6.",null,"Each Transmission Owner and Generator Owner shall conduct a benchmark thermal impact assessment for its solely and jointly owned applicable BES power transformers where the maximum effective GIC value provided in Requirement R5, Part 5.1, is 75 A per phase or greater. The benchmark thermal impact assessment shall:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[29586,"TPL-007-2","R6.1.",null,"Be based on the effective GIC flow information provided in Requirement R5;",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[29587,"TPL-007-2","R6.2.",null,"Document assumptions used in the analysis;",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[29588,"TPL-007-2","R6.3.",null,"Describe suggested actions and supporting analysis to mitigate the impact of GICs, if any; and",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[29589,"TPL-007-2","R6.4.",null,"Be performed and provided to the responsible entities, as determined in Requirement R1, within 24 calendar months of receiving GIC flow information specified in Requirement R5, Part 5.1.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[29590,"TPL-007-2","R7.",null,"Each responsible entity, as determined in Requirement R1, that concludes through the benchmark GMD Vulnerability Assessment conducted in Requirement R4 that their System does not meet the performance requirements for the steady state planning benchmark GMD event contained in Table 1, shall develop a Corrective Action Plan (CAP) addressing how the performance requirements will be met. The CAP shall:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29591,"TPL-007-2","R7.1.",null,"List System deficiencies and the associated actions needed to achieve required System performance. Examples of such actions include:\n• Installation, modification, retirement, or removal of Transmission and generation Facilities and any associated equipment.\n• Installation, modification, or removal of Protection Systems or Remedial Action Schemes.\n• Use of Operating Procedures, specifying how long they will be needed as part of the CAP.\n• Use of Demand-Side Management, new technologies, or other initiatives.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29592,"TPL-007-2","R7.2.",null,"Be developed within one year of completion of the benchmark GMD Vulnerability Assessment.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29593,"TPL-007-2","R7.3.",null,"Include a timetable, subject to revision by the responsible entity in Part 7.4, for implementing the selected actions from Part 7.1. The timetable shall:",null,null,"Never Came Into Effect in Ontario",null,"HIGh",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29594,"TPL-007-2","R7.3.1.",null,"Specify implementation of non-hardware mitigation, if any, within two years of development of the CAP; and",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29595,"TPL-007-2","R7.3.2.",null,"Specify implementation of hardware mitigation, if any, within four years of development of the CAP.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29596,"TPL-007-2","R7.4.",null,"Be revised if situations beyond the control of the responsible entity determined in Requirement R1 prevent implementation of the CAP within the timetable for implementation provided in Part 7.3. The revised CAP shall document the following, and be updated at least once every 12 calendar months until implemented:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29597,"TPL-007-2","R7.4.1.",null,"Circumstances causing the delay for fully or partially implementing the selected actions in Part 7.1;",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29598,"TPL-007-2","R7.4.2.",null,"Description of the original CAP, and any previous changes to the CAP, with the associated timetable(s) for implementing the selected actions in Part 7.1; and",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29599,"TPL-007-2","R7.4.3.",null,"Revisions to the selected actions in Part 7.1, if any, including utilization of Operating Procedures if applicable, and the updated timetable for implementing the selected actions.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29600,"TPL-007-2","R7.5.",null,"Be provided: (i) to the responsible entity’s Reliability Coordinator, adjacent Planning Coordinator(s), adjacent Transmission Planner(s), and functional entities referenced in the CAP within 90 calendar days of development or revision, and (ii) to any functional entity that submits a written request and has a reliability-related need within 90 calendar days of receipt of such request or within 90 calendar days of development or revision, whichever is later.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29601,"TPL-007-2","R7.5.1.",null,"If a recipient of the CAP provides documented comments on the results, the responsible entity shall provide a documented response to that recipient within 90 calendar days of receipt of those comments.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29602,"TPL-007-2","R8.",null,"Each responsible entity, as determined in Requirement R1, shall complete a supplemental GMD Vulnerability Assessment of the Near-Term Transmission Planning Horizon at least once every 60 calendar months. This supplemental GMD Vulnerability Assessment shall use a study or studies based on models identified in Requirement R2, document assumptions, and document summarized results of the steady state analysis.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29603,"TPL-007-2","R8.1.",null,"The study or studies shall include the following conditions:",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29604,"TPL-007-2","R8.1.1.",null,"System On-Peak Load for at least one year within the Near-Term Transmission Planning Horizon; and",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29605,"TPL-007-2","R8.1.2.",null,"System Off-Peak Load for at least one year within the Near-Term Transmission Planning Horizon.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29606,"TPL-007-2","R8.2.",null,"The study or studies shall be conducted based on the supplemental GMD event described in Attachment 1 to determine whether the System meets the performance requirements for the steady state planning supplemental GMD event contained in Table 1.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29607,"TPL-007-2","R8.3.",null,"If the analysis concludes there is Cascading caused by the supplemental GMD event described in Attachment 1, an evaluation of possible actions designed to reduce the likelihood or mitigate the consequences and adverse impacts of the event(s) shall be conducted.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29608,"TPL-007-2","R8.4.",null,"The supplemental GMD Vulnerability Assessment shall be provided: (i) to the responsible entity’s Reliability Coordinator, adjacent Planning Coordinators, adjacent Transmission Planners within 90 calendar days of completion, and (ii) to any functional entity that submits a written request and has a reliability-related need within 90 calendar days of receipt of such request or within 90 calendar days of completion of the supplemental GMD Vulnerability Assessment, whichever is later.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29609,"TPL-007-2","R8.4.1.",null,"If a recipient of the supplemental GMD Vulnerability Assessment provides documented comments on the results, the responsible entity shall provide a documented response to that recipient within 90 calendar days of receipt of those comments.",null,null,"Never Came Into Effect in Ontario",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29610,"TPL-007-2","R9.",null,"Each responsible entity, as determined in Requirement R1, shall provide GIC flow information to be used for the supplemental thermal impact assessment of transformers specified in Requirement R10 to each Transmission Owner and Generator Owner that owns an applicable Bulk Electric System (BES) power transformer in the planning area. The GIC flow information shall include:",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29611,"TPL-007-2","R9.1.",null,"The maximum effective GIC value for the worst case geoelectric field orientation for the supplemental GMD event described in Attachment 1. This value shall be provided to the Transmission Owner or Generator Owner that owns each applicable BES power transformer in the planning area.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29612,"TPL-007-2","R9.2.",null,"The effective GIC time series, GIC(t), calculated using the supplemental GMD event described in Attachment 1 in response to a written request from the Transmission Owner or Generator Owner that owns an applicable BES power transformer in the planning area. GIC(t) shall be provided within 90 calendar days of receipt of the written request and after determination of the maximum effective GIC value in Part 9.1.",null,null,"Never Came Into Effect in Ontario",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29832,"TPL-007-3","R1.",null,"Each Planning Coordinator, in conjunction with its Transmission Planner(s), shall\r\nidentify the individual and joint responsibilities of the Planning Coordinator and\r\nTransmission Planner(s) in the Planning Coordinator’s planning area for maintaining\r\nmodels, performing the study or studies needed to complete benchmark and\r\nsupplemental GMD Vulnerability Assessments, and implementing process(es) to\r\nobtain GMD measurement data as specified in this standard. [Violation Risk Factor:\r\nLower] [Time Horizon: Long-term Planning]","2019-07-01","2020-10-01","Retired",null,"LOWER",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29873,"TPL-007-3","R10.",null,"Each Transmission Owner and Generator Owner shall conduct a supplemental\r\nthermal impact assessment for its solely and jointly owned applicable BES power\r\ntransformers where the maximum effective GIC value provided in Requirement R9,\r\nPart 9.1, is 85 A per phase or greater. The supplemental thermal impact assessment\r\nshall: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2022-07-01","2020-10-01","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29874,"TPL-007-3","R10.1.",null,". Be based on the effective GIC flow information provided in Requirement R9;","2022-07-01","2020-10-01","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29875,"TPL-007-3","R10.2.",null,"Document assumptions used in the analysis;","2022-07-01","2020-10-01","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29876,"TPL-007-3","R10.3.",null,". Describe suggested actions and supporting analysis to mitigate the impact of\r\nGICs, if any; and","2022-07-01","2020-10-01","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29877,"TPL-007-3","R10.4.",null,". Be performed and provided to the responsible entities, as determined in\r\nRequirement R1, within 24 calendar months of receiving GIC flow information\r\nspecified in Requirement R9, Part 9.1.","2022-07-01","2020-10-01","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29878,"TPL-007-3","R11.",null,"Each responsible entity, as determined in Requirement R1, shall implement a process\r\nto obtain GIC monitor data from at least one GIC monitor located in the Planning\r\nCoordinator's planning area or other part of the system included in the Planning\r\nCoordinator's GIC System model. [Violation Risk Factor: Lower] [Time Horizon: Longterm Planning]","2021-07-01","2020-10-01","Retired",null,"LOWER",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29879,"TPL-007-3","R12.",null,"Each responsible entity, as determined in Requirement R1, shall implement a process\r\nto obtain geomagnetic field data for its Planning Coordinator’s planning area.\r\n[Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]","2021-07-01","2020-10-01","Retired",null,"LOWER",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29833,"TPL-007-3","R2.",null,"Each responsible entity, as determined in Requirement R1, shall maintain System\r\nmodels and GIC System models of the responsible entity’s planning area for\r\nperforming the study or studies needed to complete benchmark and supplemental\r\nGMD Vulnerability Assessments. [Violation Risk Factor: High] [Time Horizon: Longterm Planning]","2019-07-01","2020-10-01","Retired",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29834,"TPL-007-3","R3.",null,". Each responsible entity, as determined in Requirement R1, shall have criteria for\r\nacceptable System steady state voltage performance for its System during the GMD\r\nevents described in Attachment 1. [Violation Risk Factor: Medium] [Time Horizon:\r\nLong-term Planning]","2023-01-01","2020-10-01","Future Effective",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29835,"TPL-007-3","R4.",null,"Each responsible entity, as determined in Requirement R1, shall complete a\r\nbenchmark GMD Vulnerability Assessment of the Near-Term Transmission Planning\r\nHorizon at least once every 60 calendar months. This benchmark GMD Vulnerability\r\nAssessment shall use a study or studies based on models identified in Requirement R2,\r\ndocument assumptions, and document summarized results of the steady state\r\nanalysis. [Violation Risk Factor: High] [Time Horizon: Long-term Planning]","2023-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29836,"TPL-007-3","R4.1.",null,"The study or studies shall include the following conditions:","2023-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29837,"TPL-007-3","R4.1.1.",null,"System On-Peak Load for at least one year within the Near-Term\r\nTransmission Planning Horizon; and","2023-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29838,"TPL-007-3","R4.1.2.",null,"System Off-Peak Load for at least one year within the Near-Term\r\nTransmission Planning Horizon.","2023-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29839,"TPL-007-3","R4.2.",null,"The study or studies shall be conducted based on the benchmark GMD event\r\ndescribed in Attachment 1 to determine whether the System meets the\r\nperformance requirements for the steady state planning benchmark GMD event\r\ncontained in Table 1.","2023-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29840,"TPL-007-3","R4.3.",null,"The benchmark GMD Vulnerability Assessment shall be provided: (i) to the\r\nresponsible entity’s Reliability Coordinator, adjacent Planning Coordinators, and\r\nadjacent Transmission Planners within 90 calendar days of completion, and (ii) to\r\nany functional entity that submits a written request and has a reliability-related\r\nneed within 90 calendar days of receipt of such request or within 90 calendar\r\ndays of completion of the benchmark GMD Vulnerability Assessment, whichever\r\nis later","2023-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29841,"TPL-007-3","R4.3.1.",null,"If a recipient of the benchmark GMD Vulnerability Assessment provides\r\ndocumented comments on the results, the responsible entity shall\r\nprovide a documented response to that recipient within 90 calendar days\r\nof receipt of those comments.","2023-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","PC, TP","No",false,null,false]
[29842,"TPL-007-3","R5.",null,"Each responsible entity, as determined in Requirement R1, shall provide GIC flow\r\ninformation to be used for the benchmark thermal impact assessment of transformers\r\nspecified in Requirement R6 to each Transmission Owner and Generator Owner that\r\nowns an applicable Bulk Electric System (BES) power transformer in the planning area.\r\nThe GIC flow information shall include: [Violation Risk Factor: Medium] [Time Horizon:\r\nLong-term Planning]","2020-01-01","2020-10-01","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29843,"TPL-007-3","R5.1.",null,"The maximum effective GIC value for the worst case geoelectric field orientation\r\nfor the benchmark GMD event described in Attachment 1. This value shall be\r\nprovided to the Transmission Owner or Generator Owner that owns each\r\napplicable BES power transformer in the planning area.","2020-01-01","2020-10-01","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29844,"TPL-007-3","R5.2.",null,"The effective GIC time series, GIC(t), calculated using the benchmark GMD event\r\ndescribed in Attachment 1 in response to a written request from the\r\nTransmission Owner or Generator Owner that owns an applicable BES power\r\ntransformer in the planning area. GIC(t) shall be provided within 90 calendar\r\ndays of receipt of the written request and after determination of the maximum\r\neffective GIC value in Part 5.1.","2020-01-01","2020-10-01","Retired",null,"MEDIUM",null,"N/A",null,"N/A","PC, TP","No",false,null,false]
[29845,"TPL-007-3","R6.",null,"Each Transmission Owner and Generator Owner shall conduct a benchmark thermal\r\nimpact assessment for its solely and jointly owned applicable BES power transformers\r\nwhere the maximum effective GIC value provided in Requirement R5, Part 5.1, is 75 A\r\nper phase or greater. The benchmark thermal impact assessment shall: [Violation Risk\r\nFactor: Medium] [Time Horizon: Long-term Planning]","2022-07-01","2020-10-01","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29846,"TPL-007-3","R6.1.",null,"Be based on the effective GIC flow information provided in Requirement R5;","2022-07-01","2020-10-01","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29847,"TPL-007-3","R6.2.",null,"Document assumptions used in the analysis;","2022-07-01","2020-10-01","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29848,"TPL-007-3","R6.3.",null,"Describe suggested actions and supporting analysis to mitigate the impact of\r\nGICs, if any; and","2022-07-01","2020-10-01","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29849,"TPL-007-3","R6.4.",null,". Be performed and provided to the responsible entities, as determined in\r\nRequirement R1, within 24 calendar months of receiving GIC flow information\r\nspecified in Requirement R5, Part 5.1.","2022-07-01","2020-10-01","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29850,"TPL-007-3","R7.",null,"Each responsible entity, as determined in Requirement R1, that concludes through\r\nthe benchmark GMD Vulnerability Assessment conducted in Requirement R4 that\r\ntheir System does not meet the performance requirements for the steady state\r\nplanning benchmark GMD event contained in Table 1, shall develop a Corrective \r\nTPL-007-3 – Transmission System Planned Performance for Geomagnetic Disturbance Events\r\nPage 5 of 44\r\nAction Plan (CAP) addressing how the performance requirements will be met. The CAP\r\nshall: [Violation Risk Factor: High] [Time Horizon: Long-term Planning]","2024-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29851,"TPL-007-3","R7.1.",null,"List System deficiencies and the associated actions needed to achieve required\r\nSystem performance. Examples of such actions include:\r\n• Installation, modification, retirement, or removal of Transmission and\r\ngeneration Facilities and any associated equipment.\r\n• Installation, modification, or removal of Protection Systems or Remedial\r\nAction Schemes.\r\n• Use of Operating Procedures, specifying how long they will be needed as\r\npart of the CAP.\r\n• Use of Demand-Side Management, new technologies, or other initiatives.","2024-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29852,"TPL-007-3","R7.2.",null,". Be developed within one year of completion of the benchmark GMD\r\nVulnerability Assessment.","2024-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29853,"TPL-007-3","R7.3.",null,". Include a timetable, subject to revision by the responsible entity in Part 7.4, for\r\nimplementing the selected actions from Part 7.1. The timetable shall:","2024-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29854,"TPL-007-3","R7.3.1.",null,"Specify implementation of non-hardware mitigation, if any, within two\r\nyears of development of the CAP; and","2024-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29855,"TPL-007-3","R7.3.2.",null,"Specify implementation of hardware mitigation, if any, within four years\r\nof development of the CAP.","2024-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29856,"TPL-007-3","R7.4.",null,"Be revised if situations beyond the control of the responsible entity determined\r\nin Requirement R1 prevent implementation of the CAP within the timetable for\r\nimplementation provided in Part 7.3. The revised CAP shall document the\r\nfollowing, and be updated at least once every 12 calendar months until\r\nimplemented:","2024-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29857,"TPL-007-3","R7.4.1.",null,"Circumstances causing the delay for fully or partially implementing the\r\nselected actions in Part 7.1;","2024-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29858,"TPL-007-3","R7.4.2.",null,"Description of the original CAP, and any previous changes to the CAP,\r\nwith the associated timetable(s) for implementing the selected actions in\r\nPart 7.1; and","2024-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29859,"TPL-007-3","R7.4.3.",null,"Revisions to the selected actions in Part 7.1, if any, including utilization of\r\nOperating Procedures if applicable, and the updated timetable for\r\nimplementing the selected actions.","2024-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29860,"TPL-007-3","R7.5.",null,"Be provided: (i) to the responsible entity’s Reliability Coordinator, adjacent\r\nPlanning Coordinator(s), adjacent Transmission Planner(s), and functional\r\nentities referenced in the CAP within 90 calendar days of development or\r\nrevision, and (ii) to any functional entity that submits a written request and has a\r\nreliability-related need within 90 calendar days of receipt of such request or\r\nwithin 90 calendar days of development or revision, whichever is later.","2024-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29861,"TPL-007-3","R7.5.1.",null,"If a recipient of the CAP provides documented comments on the results,\r\nthe responsible entity shall provide a documented response to that\r\nrecipient within 90 calendar days of receipt of those comments.","2024-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29862,"TPL-007-3","R8.",null,"Each responsible entity, as determined in Requirement R1, shall complete a\r\nsupplemental GMD Vulnerability Assessment of the Near-Term Transmission Planning\r\nHorizon at least once every 60 calendar months. This supplemental GMD Vulnerability\r\nAssessment shall use a study or studies based on models identified in Requirement\r\nR2, document assumptions, and document summarized results of the steady state\r\nanalysis. [Violation Risk Factor: High] [Time Horizon: Long-term Planning]","2023-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29863,"TPL-007-3","R8.1.",null,". The study or studies shall include the following conditions:","2023-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29864,"TPL-007-3","R8.1.1.",null,"System On-Peak Load for at least one year within the Near-Term\r\nTransmission Planning Horizon; and","2023-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29865,"TPL-007-3","R8.1.2.",null,"System Off-Peak Load for at least one year within the Near-Term\r\nTransmission Planning Horizon.","2023-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29866,"TPL-007-3","R8.2.",null,"The study or studies shall be conducted based on the supplemental GMD event\r\ndescribed in Attachment 1 to determine whether the System meets the\r\nperformance requirements for the steady state planning supplemental GMD\r\nevent contained in Table 1.","2023-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29867,"TPL-007-3","R8.3.",null,"If the analysis concludes there is Cascading caused by the supplemental GMD\r\nevent described in Attachment 1, an evaluation of possible actions designed to\r\nreduce the likelihood or mitigate the consequences and adverse impacts of the\r\nevent(s) shall be conducted.","2023-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29868,"TPL-007-3","R8.4.",null,"The supplemental GMD Vulnerability Assessment shall be provided: (i) to the\r\nresponsible entity’s Reliability Coordinator, adjacent Planning Coordinators,\r\nadjacent Transmission Planners within 90 calendar days of completion, and (ii) to\r\nany functional entity that submits a written request and has a reliability-related\r\nneed within 90 calendar days of receipt of such request or within 90 calendar\r\ndays of completion of the supplemental GMD Vulnerability Assessment,\r\nwhichever is later.","2023-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29869,"TPL-007-3","R8.4.1.",null,"If a recipient of the supplemental GMD Vulnerability Assessment\r\nprovides documented comments on the results, the responsible entity\r\nshall provide a documented response to that recipient within 90 calendar\r\ndays of receipt of those comments.","2023-01-01","2020-10-01","Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29870,"TPL-007-3","R9.",null,"Each responsible entity, as determined in Requirement R1, shall provide GIC flow\r\ninformation to be used for the supplemental thermal impact assessment of\r\ntransformers specified in Requirement R10 to each Transmission Owner and\r\nGenerator Owner that owns an applicable Bulk Electric System (BES) power\r\ntransformer in the planning area. The GIC flow information shall include: [Violation\r\nRisk Factor: Medium] [Time Horizon: Long-term Planning]","2020-01-01","2020-10-01","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29871,"TPL-007-3","R9.1.",null,"The maximum effective GIC value for the worst case geoelectric field orientation\r\nfor the supplemental GMD event described in Attachment 1. This value shall be\r\nprovided to the Transmission Owner or Generator Owner that owns each\r\napplicable BES power transformer in the planning area.","2020-01-01","2020-10-01","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29872,"TPL-007-3","R9.2.",null,"The effective GIC time series, GIC(t), calculated using the supplemental GMD\r\nevent described in Attachment 1 in response to a written request from the\r\nTransmission Owner or Generator Owner that owns an applicable BES power\r\ntransformer in the planning area. GIC(t) shall be provided within 90 calendar\r\ndays of receipt of the written request and after determination of the maximum\r\neffective GIC value in Part 9.1.","2020-01-01","2020-10-01","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30084,"TPL-007-4","R1.",null,"Each Planning Coordinator, in conjunction with its Transmission Planner(s), shall\r\nidentify the individual and joint responsibilities of the Planning Coordinator and\r\nTransmission Planner(s) in the Planning Coordinator’s planning area for maintaining\r\nmodels, performing the study or studies needed to complete benchmark and\r\nsupplemental GMD Vulnerability Assessments, and implementing process(es) to\r\nobtain GMD measurement data as specified in this standard. [Violation Risk Factor:\r\nLower] [Time Horizon: Long-term Planning]","2020-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30119,"TPL-007-4","R10.",null,"Each Transmission Owner and Generator Owner shall conduct a supplemental\r\nthermal impact assessment for its solely and jointly owned applicable BES power\r\ntransformers where the maximum effective GIC value provided in Requirement R9,\r\nPart 9.1, is 85 A per phase or greater. The supplemental thermal impact assessment\r\nshall: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning]","2022-10-01",null,"Future Effective",null,"Medium",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30120,"TPL-007-4","R10.1.",null,"Be based on the effective GIC flow information provided in Requirement R9;","2022-10-01",null,"Future Effective",null,"Medium",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30121,"TPL-007-4","R10.2.",null,"Document assumptions used in the analysis;","2022-10-01",null,"Future Effective",null,"Medium",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30122,"TPL-007-4","R10.3.",null,"Describe suggested actions and supporting analysis to mitigate the impact of\r\nGICs, if any; and","2022-10-01",null,"Future Effective",null,"Medium",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30123,"TPL-007-4","R10.4.",null,"Be performed and provided to the responsible entities, as determined in\r\nRequirement R1, within 24 calendar months of receiving GIC flow information\r\nspecified in Requirement R9, Part 9.1.","2022-10-01",null,"Future Effective",null,"Medium",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30124,"TPL-007-4","R11.",null,"Each responsible entity, as determined in Requirement R1, that concludes through\r\nthe supplemental GMD Vulnerability Assessment conducted in Requirement R8 that\r\ntheir System does not meet the performance requirements for the steady state\r\nplanning supplemental GMD event contained in Table 1, shall develop a Corrective Action Plan (CAP) addressing how the performance requirements will be met. The CAP\r\nshall: [Violation Risk Factor: High] [Time Horizon: Long-term Planning]","2021-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30125,"TPL-007-4","R11.1.",null,"List System deficiencies and the associated actions needed to achieve required\r\nSystem performance. Examples of such actions include:\r\n• Installation, modification, retirement, or removal of Transmission and\r\ngeneration Facilities and any associated equipment.\r\n• Installation, modification, or removal of Protection Systems or Remedial\r\nAction Schemes.\r\n• Use of Operating Procedures, specifying how long they will be needed as\r\npart of the CAP.\r\n• Use of Demand-Side Management, new technologies, or other initiatives.","2021-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30126,"TPL-007-4","R11.2.",null,"Be developed within one year of completion of the supplemental GMD\r\nVulnerability Assessment.","2021-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30127,"TPL-007-4","R11.3.",null,".Include a timetable, subject to approval for any extension sought under Part\r\n11.4, for implementing the selected actions from Part 11.1. The timetable shall:","2021-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","PC, TP","No",false,null,false]
[30128,"TPL-007-4","R11.3.1.",null,"Specify implementation of non-hardware mitigation, if any, within two\r\nyears of development of the CAP; and","2021-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30129,"TPL-007-4","R11.3.2.",null,"Specify implementation of hardware mitigation, if any, within four years\r\nof development of the CAP.","2021-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30130,"TPL-007-4","R11.4.",null,"Be submitted to the CEA with a request for extension of time if the responsible\r\nentity is unable to implement the CAP within the timetable provided in Part 11.3.\r\nThe submitted CAP shall document the following:","2021-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30131,"TPL-007-4","R11.4.1.",null,"Circumstances causing the delay for fully or partially implementing the\r\nselected actions in Part 11.1 and how those circumstances are beyond\r\nthe control of the responsible entity;","2021-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30132,"TPL-007-4","R11.4.2.",null,"Revisions to the selected actions in Part 11.1, if any, including utilization\r\nof Operating Procedures, if applicable; and","2021-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30133,"TPL-007-4","R11.4.3.",null,"Updated timetable for implementing the selected actions in Part 11.1.","2021-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30134,"TPL-007-4","R11.5.",null,".Be provided: (i) to the responsible entity’s Reliability Coordinator, adjacent\r\nPlanning Coordinator(s), adjacent Transmission Planner(s), and functional\r\nentities referenced in the CAP within 90 calendar days of development or\r\nrevision, and (ii) to any functional entity that submits a written request and has a\r\nreliability-related need within 90 calendar days of receipt of such request or\r\nwithin 90 calendar days of development or revision, whichever is later.","2021-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30135,"TPL-007-4","R11.5.1.",null,"If a recipient of the CAP provides documented comments on the CAP, the\r\nresponsible entity shall provide a documented response to that recipient\r\nwithin 90 calendar days of receipt of those comments.","2021-10-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30136,"TPL-007-4","R12.",null,". Each responsible entity, as determined in Requirement R1, shall implement a process\r\nto obtain GIC monitor data from at least one GIC monitor located in the Planning\r\nCoordinator’s planning area or other part of the system included in the Planning\r\nCoordinator’s GIC System model. [Violation Risk Factor: Lower] [Time Horizon: Longterm Planning]","2021-10-01",null,"Effective",null,"LOWER",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30137,"TPL-007-4","R13.",null,"Each responsible entity, as determined in Requirement R1, shall implement a process\r\nto obtain geomagnetic field data for its Planning Coordinator’s planning area.\r\n[Violation Risk Factor: Lower] [Time Horizon: Long-term Planning]",null,null,"Effective",{"$nulls":3},"N/A",null,"N/A","TP, PC","No",false,null,false]
[30085,"TPL-007-4","R2.",null,"Each responsible entity, as determined in Requirement R1, shall maintain System\r\nmodels and GIC System models of the responsible entity’s planning area for\r\nperforming the study or studies needed to complete benchmark and supplemental\r\nGMD Vulnerability Assessments. [Violation Risk Factor: High] [Time Horizon: Longterm Planning]","2020-10-01",null,"Effective",null,"High",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30086,"TPL-007-4","R3.",null,"Each responsible entity, as determined in Requirement R1, shall have criteria for\r\nacceptable System steady state voltage performance for its System during the GMD\r\nevents described in Attachment 1. [Violation Risk Factor: Medium] [Time Horizon:\r\nLong-term Planning]","2023-04-01",null,"Future Effective",null,"Medium",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30087,"TPL-007-4","R4.",null,"Each responsible entity, as determined in Requirement R1, shall complete a\r\nbenchmark GMD Vulnerability Assessment of the Near-Term Transmission Planning\r\nHorizon at least once every 60 calendar months. This benchmark GMD Vulnerability\r\nAssessment shall use a study or studies based on models identified in Requirement R2,\r\ndocument assumptions, and document summarized results of the steady state\r\nanalysis. [Violation Risk Factor: High] [Time Horizon: Long-term Planning]","2023-04-01",null,"Future Effective",null,"High",null,"N/A",null,"N/A","PC, TP","No",false,null,false]
[30088,"TPL-007-4","R4.1.",null,"The study or studies shall include the following conditions:","2023-04-01",null,"Future Effective",null,"High",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30089,"TPL-007-4","R4.1.1.",null,"System On-Peak Load for at least one year within the Near-Term\r\nTransmission Planning Horizon; and","2023-04-01",null,"Future Effective",null,"High",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30090,"TPL-007-4","R4.1.2.",null,". System Off-Peak Load for at least one year within the Near-Term\r\nTransmission Planning Horizon.","2023-04-01",null,"Future Effective",null,"High",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30091,"TPL-007-4","R4.2.",null,"The study or studies shall be conducted based on the benchmark GMD event\r\ndescribed in Attachment 1 to determine whether the System meets the\r\nperformance requirements for the steady state planning benchmark GMD event\r\ncontained in Table 1.","2023-04-01",null,"Future Effective",null,"High",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30092,"TPL-007-4","R4.3.",null,"The benchmark GMD Vulnerability Assessment shall be provided: (i) to the\r\nresponsible entity’s Reliability Coordinator, adjacent Planning Coordinators, and\r\nadjacent Transmission Planners within 90 calendar days of completion, and (ii) to\r\nany functional entity that submits a written request and has a reliability-related\r\nneed within 90 calendar days of receipt of such request or within 90 calendar\r\ndays of completion of the benchmark GMD Vulnerability Assessment, whichever\r\nis later.","2023-04-01",null,"Future Effective",null,"High",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30093,"TPL-007-4","R4.3.1.",null,"If a recipient of the benchmark GMD Vulnerability Assessment provides\r\ndocumented comments on the results, the responsible entity shall\r\nprovide a documented response to that recipient within 90 calendar days\r\nof receipt of those comments.","2023-04-01",null,"Future Effective",null,"High",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30094,"TPL-007-4","R5.",null,"Each responsible entity, as determined in Requirement R1, shall provide GIC flow\r\ninformation to be used for the benchmark thermal impact assessment of transformers\r\nspecified in Requirement R6 to each Transmission Owner and Generator Owner that\r\nowns an applicable Bulk Electric System (BES) power transformer in the planning area.\r\nThe GIC flow information shall include: [Violation Risk Factor: Medium] [Time Horizon:\r\nLong-term Planning]","2021-04-01",null,"Effective",null,"Medium",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30095,"TPL-007-4","R5.1.",null,"The maximum effective GIC value for the worst case geoelectric field orientation\r\nfor the benchmark GMD event described in Attachment 1. This value shall be\r\nprovided to the Transmission Owner or Generator Owner that owns each\r\napplicable BES power transformer in the planning area.","2021-04-01",null,"Effective",null,"Medium",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30096,"TPL-007-4","R5.2.",null,"The effective GIC time series, GIC(t), calculated using the benchmark GMD event\r\ndescribed in Attachment 1 in response to a written request from the\r\nTransmission Owner or Generator Owner that owns an applicable BES power\r\ntransformer in the planning area. GIC(t) shall be provided within 90 calendar\r\ndays of receipt of the written request and after determination of the maximum\r\neffective GIC value in Part 5.1.","2021-04-01",null,"Effective",null,"Medium",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30097,"TPL-007-4","R6.",null,"Each Transmission Owner and Generator Owner shall conduct a benchmark thermal\r\nimpact assessment for its solely and jointly owned applicable BES power transformers\r\nwhere the maximum effective GIC value provided in Requirement R5, Part 5.1, is 75 A\r\nper phase or greater. The benchmark thermal impact assessment shall: [Violation Risk\r\nFactor: Medium] [Time Horizon: Long-term Planning]","2022-10-01",null,"Future Effective",null,"Medium",null,"N/A",null,"N/A","TO, GO","Yes",false,null,false]
[30098,"TPL-007-4","R7.",null,"Each responsible entity, as determined in Requirement R1, that concludes through Action Plan (CAP) addressing how the performance requirements will be met. The CAP\r\nshall: [Violation Risk Factor: High] [Time Horizon: Long-term Planning]\r\nthe benchmark GMD Vulnerability Assessment conducted in Requirement R4 that\r\ntheir System does not meet the performance requirements for the steady state\r\nplanning benchmark GMD event contained in Table 1, shall develop a Corrective","2024-04-01",null,"Future Effective",null,"High",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30099,"TPL-007-4","R7.1.",null,"List System deficiencies and the associated actions needed to achieve required\r\nSystem performance. Examples of such actions include:\r\n• Installation, modification, retirement, or removal of Transmission and\r\ngeneration Facilities and any associated equipment.\r\n• Installation, modification, or removal of Protection Systems or Remedial\r\nAction Schemes.\r\n• Use of Operating Procedures, specifying how long they will be needed as\r\npart of the CAP.\r\n• Use of Demand-Side Management, new technologies, or other initiatives.","2024-04-01",null,"Future Effective",null,"High",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30100,"TPL-007-4","R7.2.",null,"Be developed within one year of completion of the benchmark GMD\r\nVulnerability Assessment.","2024-04-01",null,"Future Effective",null,"High",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30101,"TPL-007-4","R7.3.",null,"Include a timetable, subject to approval for any extension sought under Part 7.4,\r\nfor implementing the selected actions from Part 7.1. The timetable shall:","2024-04-01",null,"Future Effective",null,"High",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30102,"TPL-007-4","R7.3.1.",null,"Specify implementation of non-hardware mitigation, if any, within two\r\nyears of development of the CAP; and","2024-04-01",null,"Future Effective",null,"High",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30103,"TPL-007-4","R7.3.2.",null,"Specify implementation of hardware mitigation, if any, within four years\r\nof development of the CAP.","2024-04-01",null,"Future Effective",null,"High",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30104,"TPL-007-4","R7.4.",null,"Be submitted to the Compliance Enforcement Authority (CEA) with a request for\r\nextension of time if the responsible entity is unable to implement the CAP within\r\nthe timetable provided in Part 7.3. The submitted CAP shall document the\r\nfollowing:","2024-04-01",null,"Future Effective",null,"High",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30105,"TPL-007-4","R7.4.1.",null,"Circumstances causing the delay for fully or partially implementing the\r\nselected actions in Part 7.1 and how those circumstances are beyond the\r\ncontrol of the responsible entity;","2024-04-01",null,"Future Effective",null,"High",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30106,"TPL-007-4","R7.4.2.",null,"Revisions to the selected actions in Part 7.1, if any, including utilization of\r\nOperating Procedures, if applicable; and","2024-04-01",null,"Future Effective",null,"High",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30107,"TPL-007-4","R7.4.3.",null,"Updated timetable for implementing the selected actions in Part 7.1.","2024-04-01",null,"Future Effective",null,"High",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30108,"TPL-007-4","R7.5.",null,"Be provided: (i) to the responsible entity’s Reliability Coordinator, adjacent\r\nPlanning Coordinator(s), adjacent Transmission Planner(s), and functional\r\nentities referenced in the CAP within 90 calendar days of development or\r\nrevision, and (ii) to any functional entity that submits a written request and has a\r\nreliability-related need within 90 calendar days of receipt of such request or\r\nwithin 90 calendar days of development or revision, whichever is later.","2024-04-01",null,"Future Effective",null,"High",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30109,"TPL-007-4","R7.5.1.",null,"If a recipient of the CAP provides documented comments on the CAP, the\r\nresponsible entity shall provide a documented response to that recipient\r\nwithin 90 calendar days of receipt of those comments","2024-04-01",null,"Future Effective",null,"High",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30110,"TPL-007-4","R8.",null,"Each responsible entity, as determined in Requirement R1, shall complete a\r\nsupplemental GMD Vulnerability Assessment of the Near-Term Transmission Planning\r\nHorizon at least once every 60 calendar months. This supplemental GMD Vulnerability\r\nAssessment shall use a study or studies based on models identified in Requirement\r\nR2, document assumptions, and document summarized results of the steady state\r\nanalysis. [Violation Risk Factor: High] [Time Horizon: Long-term Planning]","2023-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30111,"TPL-007-4","R8.1.",null,"System On-Peak Load for at least one year within the Near-Term\r\nTransmission Planning Horizon; and","2023-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30112,"TPL-007-4","R8.1.2.",null,"System Off-Peak Load for at least one year within the Near-Term\r\nTransmission Planning Horizon.","2023-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30113,"TPL-007-4","R8.2.",null,"The study or studies shall be conducted based on the supplemental GMD event\r\ndescribed in Attachment 1 to determine whether the System meets the\r\nperformance requirements for the steady state planning supplemental GMD\r\nevent contained in Table 1.","2023-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30114,"TPL-007-4","R8.3.",null,"The supplemental GMD Vulnerability Assessment shall be provided: (i) to the\r\nresponsible entity’s Reliability Coordinator, adjacent Planning Coordinators,\r\nadjacent Transmission Planners within 90 calendar days of completion, and (ii) to\r\nany functional entity that submits a written request and has a reliability-related\r\nneed within 90 calendar days of receipt of such request or within 90 calendar\r\ndays of completion of the supplemental GMD Vulnerability Assessment,\r\nwhichever is later.","2023-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30115,"TPL-007-4","R8.3.1.",null,"If a recipient of the supplemental GMD Vulnerability Assessment\r\nprovides documented comments on the results, the responsible entity\r\nshall provide a documented response to that recipient within 90 calendar\r\ndays of receipt of those comments.","2023-04-01",null,"Future Effective",null,"HIGH",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30116,"TPL-007-4","R9.",null,"Each responsible entity, as determined in Requirement R1, shall provide GIC flow\r\ninformation to be used for the supplemental thermal impact assessment of\r\ntransformers specified in Requirement R10 to each Transmission Owner and\r\nGenerator Owner that owns an applicable Bulk Electric System (BES) power\r\ntransformer in the planning area. The GIC flow information shall include: [Violation\r\nRisk Factor: Medium] [Time Horizon: Long-term Planning]","2021-04-01",null,"Effective",null,"Medium",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30117,"TPL-007-4","R9.1.",null,"The maximum effective GIC value for the worst case geoelectric field orientation\r\nfor the supplemental GMD event described in Attachment 1. This value shall be\r\nprovided to the Transmission Owner or Generator Owner that owns each\r\napplicable BES power transformer in the planning area.","2021-04-01",null,"Effective",null,"Medium",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[30118,"TPL-007-4","R9.2.",null,"The effective GIC time series, GIC(t), calculated using the supplemental GMD\r\nevent described in Attachment 1 in response to a written request from the\r\nTransmission Owner or Generator Owner that owns an applicable BES power\r\ntransformer in the planning area. GIC(t) shall be provided within 90 calendar\r\ndays of receipt of the written request and after determination of the maximum\r\neffective GIC value in Part 9.1.","2021-04-01",null,"Effective",null,"Medium",null,"N/A",null,"N/A","TP, PC","No",false,null,false]
[29550,"VAR-001-4","R1.",null,"Each Transmission Operator shall specify a system voltage schedule (which is either a range or a target value with an associated tolerance band) as part of its plan to operate within System Operating Limits and Interconnection Reliability Operating Limits.",null,null,"Retired",null,"HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[29551,"VAR-001-4","R1.1.",null,"Each Transmission Operator shall provide a copy of the voltage schedules (which is either a range or a target value with an associated tolerance band) to its Reliability Coordinator and adjacent Transmission Operators within 30 calendar days of a request.",null,null,"Retired",null,"HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[29552,"VAR-001-4","R2.",null,"Each Transmission Operator shall schedule sufficient reactive resources to regulate voltage levels under normal and Contingency conditions. Transmission Operators can provide sufficient reactive resources through various means including, but not limited to, reactive generation scheduling, transmission line and reactive resource switching, and using controllable load.",null,null,"Retired",null,"HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[29553,"VAR-001-4","R3.",null,"Each Transmission Operator shall operate or direct the Real-time operation of devices to regulate transmission voltage and reactive flow as necessary.",null,null,"Retired",null,"HIGH","LIKELY","HIGH (Comprehensive Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[29554,"VAR-001-4","R4.",null,"The Transmission Operator shall specify the criteria that will exempt generators from: 1) following a voltage or Reactive Power schedule, 2) from having its automatic voltage regulator (AVR) in service or from being in voltage control mode, or 3) from having to make any associated notifications.",null,null,"Retired",null,"LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[29555,"VAR-001-4","R4.1.",null,"If a Transmission Operator determines that a generator has satisfied the exemption criteria, it shall notify the associated Generator Operator.",null,null,"Retired",null,"LOWER","UNLIKELY","LOW (Limited Controls Required)","UNLIKELY","LOW (Adequate Controls)","TOP","No",true,null,false]
[29556,"VAR-001-4","R5.",null,"Each Transmission Operator shall specify a voltage or Reactive Power schedule (which is either a range or a target value with an associated tolerance band) at either the high voltage side or low voltage side of the generator step-up transformer at the Transmission Operator’s discretion.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29557,"VAR-001-4","R5.1.",null,"The Transmission Operator shall provide the voltage or Reactive Power schedule (which is either a range or a target value with an associated tolerance band) to the associated Generator Operator and direct the Generator Operator to comply with the schedule in automatic voltage control mode (the AVR is in service and controlling voltage).",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29558,"VAR-001-4","R5.2.",null,"The Transmission Operator shall provide the Generator Operator with the notification requirements for deviations from the voltage or Reactive Power schedule (which is either a range or a target value with an associated tolerance band).",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29559,"VAR-001-4","R5.3.",null,"The Transmission Operator shall provide the criteria used to develop voltage schedules Reactive Power schedule (which is either a range or a target value with an associated tolerance band) to the Generator Operator within 30 days of receiving a request.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29560,"VAR-001-4","R6.",null,"After consultation with the Generator Owner regarding necessary step-up transformer tap changes and the implementation schedule, the Transmission Operator shall provide documentation to the Generator Owner specifying the required tap changes, a timeframe for making the changes, and technical justification for these changes.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29561,"VAR-001-4.1","R1.",null,"Each Transmission Operator shall specify a system voltage schedule (which is either a range or a target value with an associated tolerance band) as part of its plan to operate within System Operating Limits and Interconnection Reliability Operating Limits.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29562,"VAR-001-4.1","R1.1.",null,"Each Transmission Operator shall provide a copy of the voltage schedules (which is either a range or a target value with an associated tolerance band) to its Reliability Coordinator and adjacent Transmission Operators within 30 calendar days of a request.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29563,"VAR-001-4.1","R2.",null,"Each Transmission Operator shall schedule sufficient reactive resources to regulate voltage levels under normal and Contingency conditions. Transmission Operators can provide sufficient reactive resources through various means including, but not limited to, reactive generation scheduling, transmission line and reactive resource switching, and using controllable load.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29564,"VAR-001-4.1","R3.",null,"Each Transmission Operator shall operate or direct the Real-time operation of devices to regulate transmission voltage and reactive flow as necessary.",null,null,"Retired",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29565,"VAR-001-4.1","R4.",null,"The Transmission Operator shall specify the criteria that will exempt generators from: 1) following a voltage or Reactive Power schedule, 2) from having its automatic voltage regulator (AVR) in service or from being in voltage control mode, or 3) from having to make any associated notifications.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29566,"VAR-001-4.1","R4.1.",null,"If a Transmission Operator determines that a generator has satisfied the exemption criteria, it shall notify the associated Generator Operator.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29567,"VAR-001-4.1","R5.",null,"Each Transmission Operator shall specify a voltage or Reactive Power schedule (which is either a range or a target value with an associated tolerance band) at either the high voltage side or low voltage side of the generator step-up transformer at the Transmission Operator’s discretion.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29568,"VAR-001-4.1","R5.1.",null,"The Transmission Operator shall provide the voltage or Reactive Power schedule (which is either a range or a target value with an associated tolerance band) to the associated Generator Operator and direct the Generator Operator to comply with the schedule in automatic voltage control mode (the AVR is in service and controlling voltage).",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29569,"VAR-001-4.1","R5.2.",null,"The Transmission Operator shall provide the Generator Operator with the notification requirements for deviations from the voltage or Reactive Power schedule (which is either a range or a target value with an associated tolerance band).",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29570,"VAR-001-4.1","R5.3.",null,"The Transmission Operator shall provide the criteria used to develop voltage schedules or Reactive Power schedule (which is either a range or a target value with an associated tolerance band) to the Generator Operator within 30 days of receiving a request.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29571,"VAR-001-4.1","R6.",null,"After consultation with the Generator Owner regarding necessary step-up transformer tap changes and the implementation schedule, the Transmission Operator shall provide documentation to the Generator Owner specifying the required tap changes, a timeframe for making the changes, and technical justification for these changes.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29620,"VAR-001-4.2","R1.",null,"Each Transmission Operator shall specify a system voltage schedule (which is either a range or a target value with an associated tolerance band) as part of its plan to operate within System Operating Limits and Interconnection Reliability Operating Limits.",null,"2019-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29621,"VAR-001-4.2","R1.1.",null,"Each Transmission Operator shall provide a copy of the voltage schedules (which is either a range or a target value with an associated tolerance band) to its Reliability Coordinator and adjacent Transmission Operators within 30 calendar days of a request.",null,"2019-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29622,"VAR-001-4.2","R2.",null,"Each Transmission Operator shall schedule sufficient reactive resources to regulate voltage levels under normal and Contingency conditions. Transmission Operators can provide sufficient reactive resources through various means including, but not limited to, reactive generation scheduling, transmission line and reactive resource switching, and using controllable load.",null,"2019-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29623,"VAR-001-4.2","R3.",null,"Each Transmission Operator shall operate or direct the Real-time operation of devices to regulate transmission voltage and reactive flow as necessary.",null,"2019-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29624,"VAR-001-4.2","R4.",null,"Each Transmission Operator shall specify the criteria that will exempt generators: 1) from following a voltage or Reactive Power schedule, 2) from having its automatic voltage regulator (AVR) in service or from being in voltage control mode, or 3) from having to make any associated notifications.",null,"2019-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29625,"VAR-001-4.2","R4.1.",null,"If a Transmission Operator determines that a generator has satisfied the exemption criteria, it shall notify the associated Generator Operator.",null,"2019-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29626,"VAR-001-4.2","R5.",null,"Each Transmission Operator shall specify a voltage or Reactive Power schedule (which is either a range or a target value with an associated tolerance band) at either the high voltage side or low voltage side of the generator step-up transformer at the Transmission Operator’s discretion.",null,"2019-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29627,"VAR-001-4.2","R5.1.",null,"The Transmission Operator shall provide the voltage or Reactive Power schedule (which is either a range or a target value with an associated tolerance band) to the associated Generator Operator and direct the Generator Operator to comply with the schedule in automatic voltage control mode (the AVR is in service and controlling voltage).",null,"2019-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29628,"VAR-001-4.2","R5.2.",null,"The Transmission Operator shall provide the Generator Operator with the notification requirements for deviations from the voltage or Reactive Power schedule (which is either a range or a target value with an associated tolerance band).",null,"2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29629,"VAR-001-4.2","R5.3.",null,"The Transmission Operator shall provide the criteria used to develop voltage schedules or Reactive Power schedule (which is either a range or a target value with an associated tolerance band) to the Generator Operator within 30 days of receiving a request.",null,"2019-03-31","Retired",null,"MEDIUM",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29630,"VAR-001-4.2","R6.",null,"After consultation with the Generator Owner regarding necessary step-up transformer tap changes and the implementation schedule, the Transmission Operator shall provide documentation to the Generator Owner specifying the required tap changes, a timeframe for making the changes, and technical justification for these changes.",null,"2019-03-31","Retired",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29697,"VAR-001-5","R1.","YES","Each Transmission Operator shall specify a system voltage schedule (which is either a range or a target value with an associated tolerance band) as part of its plan to operate within System Operating Limits and Interconnection Reliability Operating Limits. [Violation Risk Factor: High] [Time Horizon: Operations Planning]","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[30613,"VAR-001-5","R1.","YES","Each Transmission Operator shall specify a system voltage schedule (which is either a range or a target value with an associated tolerance band) as part of its plan to operate within System Operating Limits and Interconnection Reliability Operating Limits. [Violation Risk Factor: High] [Time Horizon: Operations Planning]","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,false]
[29698,"VAR-001-5","R1.1.","YES","Each Transmission Operator shall provide a copy of the voltage schedules (which is either a range or a target value with an associated tolerance band) to its Reliability Coordinator and adjacent Transmission Operators within 30 calendar days of a request.","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[30614,"VAR-001-5","R1.1.","YES","Each Transmission Operator shall provide a copy of the voltage schedules (which is either a range or a target value with an associated tolerance band) to its Reliability Coordinator and adjacent Transmission Operators within 30 calendar days of a request.","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,false]
[29699,"VAR-001-5","R2.","YES","Each Transmission Operator shall schedule sufficient reactive resources to regulate voltage levels under normal and Contingency conditions. Transmission Operators can provide sufficient reactive resources through various means including, but not limited to, reactive generation scheduling, transmission line and reactive resource switching, and using controllable load. [Violation Risk Factor: High] [Time Horizon: Real-time Operations, Same-day Operations, and Operations Planning]","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[30615,"VAR-001-5","R2.","YES","Each Transmission Operator shall schedule sufficient reactive resources to regulate voltage levels under normal and Contingency conditions. Transmission Operators can provide sufficient reactive resources through various means including, but not limited to, reactive generation scheduling, transmission line and reactive resource switching, and using controllable load. [Violation Risk Factor: High] [Time Horizon: Real-time Operations, Same-day Operations, and Operations Planning]","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,false]
[29700,"VAR-001-5","R3.",null,"Each Transmission Operator shall operate or direct the Real-time operation of devices to regulate transmission voltage and reactive flow as necessary. [Violation Risk Factor: High] [Time Horizon: Real-time Operations, Same-day Operations, and Operations Planning]","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,true,"Hydro One operates at direction of IESO"]
[29701,"VAR-001-5","R4.","YES","Each Transmission Operator shall specify the criteria that will exempt generators: 1) from following a voltage or Reactive Power schedule, 2) from having its automatic voltage regulator (AVR) in service or from being in voltage control mode, or 3) from having to make any associated notifications. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[30616,"VAR-001-5","R4.","YES","Each Transmission Operator shall specify the criteria that will exempt generators: 1) from following a voltage or Reactive Power schedule, 2) from having its automatic voltage regulator (AVR) in service or from being in voltage control mode, or 3) from having to make any associated notifications. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,false]
[29702,"VAR-001-5","R4.1.","YES","If a Transmission Operator determines that a generator has satisfied the exemption criteria, it shall notify the associated Generator Operator.","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GOP, TOP","Yes",true,null,false]
[30617,"VAR-001-5","R4.1.","YES","If a Transmission Operator determines that a generator has satisfied the exemption criteria, it shall notify the associated Generator Operator.","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,false]
[29703,"VAR-001-5","R5.",null,"Each Transmission Operator shall specify a voltage or Reactive Power schedule (which is either a range or a target value with an associated tolerance band) at either the high voltage side or low voltage side of the generator step-up transformer at the Transmission Operator’s discretion. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning]","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP","No",true,null,false]
[29704,"VAR-001-5","R5.1.",null,"The Transmission Operator shall provide the voltage or Reactive Power schedule (which is either a range or a target value with an associated tolerance band) to the associated Generator Operator and direct the Generator Operator to comply with the schedule in automatic voltage control mode (the AVR is in service and controlling voltage).","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GOP, TOP","Yes",true,null,false]
[29705,"VAR-001-5","R5.2.","YES","The Transmission Operator shall provide the Generator Operator with the notification requirements for deviations from the voltage or Reactive Power schedule (which is either a range or a target value with an associated tolerance band).","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP","Yes",true,null,false]
[30618,"VAR-001-5","R5.2.","YES","The Transmission Operator shall provide the Generator Operator with the notification requirements for deviations from the voltage or Reactive Power schedule (which is either a range or a target value with an associated tolerance band).","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A",null,"No",true,null,false]
[29706,"VAR-001-5","R5.3.",null,"The Transmission Operator shall provide the criteria used to develop voltage schedules or Reactive Power schedule (which is either a range or a target value with an associated tolerance band) to the Generator Operator within 30 days of receiving a request.","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","TOP, GOP","Yes",true,null,false]
[29709,"VAR-001-5","R6.",null,"After consultation with the Generator Owner regarding necessary step-up transformer tap changes and the implementation schedule, the Transmission Operator shall provide documentation to the Generator Owner specifying the required tap changes, a timeframe for making the changes, and technical justification for these changes. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]","2019-04-01",null,"Effective",null,"HIGH",null,"N/A",null,"N/A","GO, TOP","Yes",true,null,false]
[29645,"VAR-002-4","R1.",null,"The Generator Operator shall operate each generator connected to the interconnected transmission system in the automatic voltage control mode (with its automatic voltage regulator (AVR) in service and controlling voltage) or in a different control mode as instructed by the Transmission Operator unless: 1) the generator is exempted by the Transmission Operator, or 2) the Generator Operator has notified the Transmission Operator of one of the following: [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]\n That the generator is being operated in start-up,1 shutdown,2 or testing mode pursuant to a Real-time communication or a procedure that was previously provided to the Transmission Operator; or\n That the generator is not being operated in automatic voltage control mode or in the control mode that was instructed by the Transmission Operator for a reason other than start-up, shutdown, or testing.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[29646,"VAR-002-4","R2.",null,"Unless exempted by the Transmission Operator, each Generator Operator shall maintain the generator voltage or Reactive Power schedule3 (within each generating Facility’s capabilities4) provided by the Transmission Operator, or otherwise shall meet the conditions of notification for deviations from the voltage or Reactive Power schedule provided by the Transmission Operator. [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[29647,"VAR-002-4","R2.1.",null,"When a generator’s AVR is out of service or the generator does not have an AVR, the Generator Operator shall use an alternative method to control the generator reactive output to meet the voltage or Reactive Power schedule provided by the Transmission Operator.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[29648,"VAR-002-4","R2.2.",null,"When instructed to modify voltage, the Generator Operator shall comply or provide an explanation of why the schedule cannot be met.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[29332,"VAR-002-4","R2.3.",null,"Generator Operators that do not monitor the voltage at the location specified in their voltage schedule shall have a methodology for converting the scheduled voltage specified by the Transmission Operator to the voltage point being monitored by the Generator Operator.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[29333,"VAR-002-4","R3.",null,"Each Generator Operator shall notify its associated Transmission Operator of a status change on the AVR, power system stabilizer, or alternative voltage controlling device within 30 minutes of the change. If the status has been restored within 30 minutes of such change, then the Generator Operator is not required to notify the Transmission Operator of the status change [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[29334,"VAR-002-4","R4.",null,"Each Generator Operator shall notify its associated Transmission Operator within 30 minutes of becoming aware of a change in reactive capability due to factors other than a status change described in Requirement R3. If the capability has been restored within 30 minutes of the Generator Operator becoming aware of such change, then the Generator Operator is not required to notify the Transmission Operator of the change in reactive capability. [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]\n Reporting of status or capability changes as stated in Requirement R4 is not applicable to the individual generating units of dispersed power producing resources identified through Inclusion I4 of the Bulk Electric System definition.",null,null,"Retired",null,"MEDIUM",null,"N/A",null,"N/A","GOP","Yes",false,null,false]
[29335,"VAR-002-4","R5.",null,"The Generator Owner shall provide the following to its associated Transmission Operator and Transmission Planner within 30 calendar days of a request. [Violation Risk Factor: Lower] [Time Horizon: Real-time Operations]",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29336,"VAR-002-4","R5.1.",null,"For generator step-up and auxiliary transformers5 with primary voltages equal to or greater than the generator terminal voltage:",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29337,"VAR-002-4","R5.1.1.",null,"Tap settings.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29338,"VAR-002-4","R5.1.2.",null,"Available fixed tap ranges.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29339,"VAR-002-4","R5.1.3.",null,"Impedance data.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29649,"VAR-002-4","R6.",null,"After consultation with the Transmission Operator regarding necessary step-up transformer tap changes, the Generator Owner shall ensure that transformer tap positions are changed according to the specifications provided by the Transmission Operator, unless such action would violate safety, an equipment rating, a regulatory requirement, or a statutory requirement. [Violation Risk Factor: Lower] [Time Horizon: Real-time Operations]",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29650,"VAR-002-4","R6.1.",null,"If the Generator Owner cannot comply with the Transmission Operator’s specifications, the Generator Owner shall notify the Transmission Operator and shall provide the technical justification.",null,null,"Retired",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29651,"VAR-002-4.1","R1.",null,"The Generator Operator shall operate each generator connected to the interconnected transmission system in the automatic voltage control mode (with its automatic voltage regulator (AVR) in service and controlling voltage) or in a different control mode as instructed by the Transmission Operator unless: 1) the generator is exempted by the Transmission Operator, or 2) the Generator Operator has notified the Transmission Operator of one of the following: [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]\n• That the generator is being operated in start-up,1 shutdown,2 or testing mode pursuant to a Real-time communication or a procedure that was previously provided to the Transmission Operator; or\n• That the generator is not being operated in automatic voltage control mode or in the control mode that was instructed by the Transmission Operator for a reason other than start-up, shutdown, or testing.",null,null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29652,"VAR-002-4.1","R2.",null,"Unless exempted by the Transmission Operator, each Generator Operator shall maintain the generator voltage or Reactive Power schedule3 (within each generating Facility’s capabilities4) provided by the Transmission Operator, or otherwise shall meet the conditions of notification for deviations from the voltage or Reactive Power schedule provided by the Transmission Operator. [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]",null,null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29653,"VAR-002-4.1","R2.1.",null,"When a generator’s AVR is out of service or the generator does not have an AVR, the Generator Operator shall use an alternative method to control the generator reactive output to meet the voltage or Reactive Power schedule provided by the Transmission Operator.",null,null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29654,"VAR-002-4.1","R2.2.",null,"When instructed to modify voltage, the Generator Operator shall comply or provide an explanation of why the schedule cannot be met.",null,null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29655,"VAR-002-4.1","R2.3.",null,"Generator Operators that do not monitor the voltage at the location specified in their voltage schedule shall have a methodology for converting the scheduled voltage specified by the Transmission Operator to the voltage point being monitored by the Generator Operator.",null,null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29656,"VAR-002-4.1","R3.",null,"Each Generator Operator shall notify its associated Transmission Operator of a status change on the AVR, power system stabilizer, or alternative voltage controlling device within 30 minutes of the change. If the status has been restored within 30 minutes of such change, then the Generator Operator is not required to notify the Transmission Operator of the status change. [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]",null,null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29657,"VAR-002-4.1","R4.",null,"Each Generator Operator shall notify its associated Transmission Operator within 30 minutes of becoming aware of a change in reactive capability due to factors other than a status change described in Requirement R3. If the capability has been restored within 30 minutes of the Generator Operator becoming aware of such change, then the Generator Operator is not required to notify the Transmission Operator of the change in reactive capability. [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]\n• Reporting of status or capability changes as stated in Requirement R4 is not applicable to the individual generating units of dispersed power producing resources identified through Inclusion I4 of the Bulk Electric System definition.",null,null,"Effective",null,"MEDIUM",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29658,"VAR-002-4.1","R5.",null,"The Generator Owner shall provide the following to its associated Transmission Operator and Transmission Planner within 30 calendar days of a request. [Violation Risk Factor: Lower] [Time Horizon: Real-time Operations]",null,null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29659,"VAR-002-4.1","R5.1.",null,"For generator step-up and auxiliary transformers5 with primary voltages equal to or greater than the generator terminal voltage:",null,null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29660,"VAR-002-4.1","R5.1.1.",null,"Tap settings.",null,null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29661,"VAR-002-4.1","R5.1.2.",null,"Available fixed tap ranges.",null,null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29662,"VAR-002-4.1","R5.1.3.",null,"Impedance data.",null,null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29663,"VAR-002-4.1","R6.",null,"After consultation with the Transmission Operator regarding necessary step-up transformer tap changes, the Generator Owner shall ensure that transformer tap positions are changed according to the specifications provided by the Transmission Operator, unless such action would violate safety, an equipment rating, a regulatory requirement, or a statutory requirement. [Violation Risk Factor: Lower] [Time Horizon: Real-time Operations]",null,null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]
[29664,"VAR-002-4.1","R6.1.",null,"If the Generator Owner cannot comply with the Transmission Operator’s specifications, the Generator Owner shall notify the Transmission Operator and shall provide the technical justification.",null,null,"Effective",null,"LOWER",null,"N/A",null,"N/A","GO","Yes",false,null,false]

{"sheet":"NPCCDocuments","index":3,"n_rows":33,"n_cols":13,"rows_kept":33}
["ID","NPCC Document","Document Title","NPCC Adoption Date","OEB Start Date","OEB End Date","Review Status in Ontario","USA Approval Status","Mandatory Enforcement Date in Ontario","Inactive Date in Ontario","Status in Ontario","Functional Entities","External Link"]
[{"$nulls":10},"As Of 2022/08/16"]
[46,"Directory # 1","Design and Operation of the Bulk Power System","2012-04-20","2013-12-03","2014-04-02","Not Initiated","Approved","2014-04-03","2017-01-20","Retired","BA, GO, PC, RC, RP, TO, TOP, TP","https://www.npcc.org/Standards/Directories/Directory1_Design%20and%20Oper_20200305.pdf"]
[47,"Directory # 1 V2","Design and Operation of the Bulk Power System","2015-09-30","2016-09-22","2017-01-20","Not Initiated","Approved","2017-01-21","2020-09-16","Retired","BA, GO, PC, RC, RP, TO, TOP, TP","https://www.npcc.org/content/docs/public/program-areas/standards-and-criteria/regional-criteria/directories/directory-01-design-and-operation-of-the-bulk-power-system.pdf"]
[51,"Directory # 2","Emergency Operations","2011-06-01","2013-12-03","2014-04-02","Not Initiated","Approved","2014-04-03","2017-01-20","Retired","BA, RC, TOP","https://www.npcc.org/Standards/Directories/Directory%202%20-%20Emergency%20Operations_20180703.pdf"]
[52,"Directory # 2 V3","Emergency Operations","2015-03-30","2016-09-22","2017-01-20","Not Initiated","Approved","2017-01-21","2018-07-02","Retired","BA, RC, TOP","https://www.npcc.org/content/docs/public/program-areas/standards-and-criteria/regional-criteria/directories/directory-2-emergency-operations-20180703.pdfC:\\Users\\lagans\\AppData\\Local\\Microsoft\\Windows\\INetCache\\Content.Outlook\\IDWC0DRY\\Updated NPCC Links.xlsxSheet1!D3"]
[55,"Directory # 4","Bulk Power System Protection Criteria","2009-12-01","2010-03-15","2010-07-13","Not Initiated","Approved","2010-07-14","2017-01-20","Retired"]
[56,"Directory # 4 V2","Bulk Power System Protection Criteria","2015-09-30","2016-09-22","2017-01-20","Not Initiated","Approved","2017-01-21","2020-11-07","Retired",null,"https://www.npcc.org/content/docs/public/program-areas/standards-and-criteria/regional-criteria/directories/directory-4-tfsp-rev-20200130.pdf"]
[58,"Directory # 5","Reserve","2012-10-11","2013-12-03","2014-04-02","Not Initiated","Approved","2014-04-03","2017-01-20","Retired","BA, DP, GOP, RC","https://www.npcc.org/Standards/Directories/Directory%205%20-%20Reserve_20200116.pdf"]
[59,"Directory # 5 V2","Reserve","2015-03-30","2016-09-22","2017-01-20","Not Initiated","Approved","2017-01-21","2020-04-26","Retired","BA, DP, GOP, RC","https://www.npcc.org/Standards/Directories/Directory_5-Full%20Member%20Approved%20clean%20-GJD%2020150330.pdf"]
[60,"Directory # 6","Reserve Sharing Groups","2012-04-06","2012-04-10","2012-08-08","Not Initiated","Approved","2012-08-09","2017-01-20","Retired","BA, RSG","https://www.npcc.org/Standards/Directories/Directory%206%20Reserve%20Sharing%20Groups%20_20190930.pdf"]
[61,"Directory # 6 V1","Reserve Sharing Groups","2015-03-30","2016-09-22","2017-01-20","Not Initiated","Approved","2017-01-21","2019-09-26","Retired","BA, RSG","https://www.npcc.org/Standards/Directories/Directory%206%20Reserve%20Sharing%20Groups%20Full%20Member%20Approved%20clean%20GJD%2020150330.pdf"]
[63,"Directory # 7","Special Protection Systems","2013-07-09","2013-07-29","2013-11-26","Not Initiated","Approved","2013-11-27","2017-01-20","Retired"]
[64,"Directory # 7 V2","Special Protection Systems","2015-03-31","2016-09-22","2017-01-20","Not Initiated","Approved","2017-01-21",null,"Effective",null,"https://www.npcc.org/Standards/Directories/Directory%207_SPS_%20clean_20150331_GJD.pdf"]
[66,"Directory # 8","System Restoration","2010-10-22","2013-12-03","2014-04-02","Not Initiated","Approved","2014-04-03","2017-01-20","Retired","BA, GO, GOP, RC, TO, TOP","https://www.npcc.org/Standards/Directories/Directory%208%20Revised_20180925.pdf"]
[67,"Directory # 8 V3","System Restoration","2017-10-06","2016-09-22","2017-01-20","Not Initiated","Approved","2017-01-21","2018-09-24","Retired","BA, GO, GOP, RC, TO, TOP","https://www.npcc.org/Standards/Directories/Directory%208%20Revised_20180925.pdf"]
[70,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","2011-12-28","2012-06-28","2012-10-26","Not Initiated","Approved","2012-10-27","2017-01-20","Retired"]
[71,"Directory # 9 V3","Verification of Generator Gross and Net Real Power Capability","2015-03-31","2016-09-22","2017-01-20","Not Initiated","Approved","2017-01-21","2019-07-01","Retired",null,"https://www.npcc.org/Standards/Directories/Directory%209%20-%20Generator%20Real%20Power%20Verification_clean_20150331_GJD.pdf"]
[74,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","2011-12-28","2012-06-28","2012-10-26","Not Initiated","Approved","2012-10-27","2017-01-20","Retired"]
[75,"Directory # 10 V3","Verification of Generator Gross and Net Reactive Power Capability","2015-03-31","2016-09-22","2017-01-20","Not Initiated","Approved","2017-01-21","2019-07-01","Retired",null,"https://www.npcc.org/Standards/Directories/NPCC%20Directory%2010%20-%20Generator%20Reactive%20Power%20Verification_clean%20_20150331_GJD.pdf"]
[76,"Directory # 11","Disturbance Monitoring Equipment Criteria","2016-10-24","2016-11-04","2017-03-04","Not Initiated","Approved","2016-10-24","2020-11-08","Retired","GO, TO","https://www.npcc.org/Standards/Directories/Directory%2011%20-%20Disturbance%20Monitoring%20Equipment%20Criteria_Full%20Member%20Approved_20161027.pdf"]
[79,"Directory # 12","UFLS Program Requirements","2011-01-06","2011-01-06","2011-05-06","Not Initiated","Approved","2011-01-06","2017-06-25","Retired"]
[80,"Directory # 12","UFLS Program Requirements","2013-07-09","2013-07-29","2013-11-26","Not Initiated","Approved",null,"2017-01-20","Update Ontario Enforcement Date"]
[81,"Directory # 12 V4","UFLS Program Requirements","2015-03-30","2015-03-30","2015-03-30","Not Initiated","Approved","2015-03-30",null,"Effective",null,"https://www.npcc.org/Standards/Directories/Directory12%20Full%20Member%20clean%2020150330%20GJD.pdf"]
[84,"Criterion A-01","Criteria for Review and Approval of Documents","2005-03-01","2005-03-01","2005-06-29","Not Initiated","Approved","2005-03-01",null,"Effective"]
[86,"Criterion A-10","Classification of Bulk Power System Elements","2009-12-01","2009-12-01","2010-03-31","Not Initiated","Approved","2009-12-01",null,"Effective"]
[87,"Criterion A-15","Disturbance Monitoring Equipment Criteria","2007-08-23","2007-08-23","2007-12-21","Not Initiated","Approved","2007-08-23",null,"Effective"]
[93,"Directory # 2 V4","Emergency Operations","2018-06-29","2016-04-29","2016-06-29","Not Initiated","Approved","2018-07-03",null,"Effective","BA, RC, TOP","https://www.npcc.org/Standards/Directories/Directory%202%20-%20Emergency%20Operations_20180703.pdf"]
[94,"Directory # 5 V3","Reserve","2019-09-27","2019-09-27","2020-01-25","Not Initiated","Approved","2019-01-16",null,"Effective","BA, DP, GOP, RC","https://www.npcc.org/Standards/Directories/Directory%205%20-%20Reserve_20190930.pdf"]
[96,"Directory # 6 V2","Reserve Sharing Groups","2019-09-27","2019-09-27","2020-01-25","Not Initiated","Approved","2019-09-27",null,"Effective","BA, RSG","https://www.npcc.org/Standards/Directories/Directory%206%20Reserve%20Sharing%20Groups%20_20190930.pdf"]
[97,"Directory # 8 V4","System Restoration","2018-09-25","2018-09-25","2019-01-23","Not Initiated","Approved","2018-09-25",null,"Effective","BA, GO, GOP, RC, TO, TOP","https://www.npcc.org/Standards/Directories/Directory%208%20Revised_20180925.pdf"]
[99,"Directory # 1 V3","Design and Operation of the Bulk Power System","2020-09-09","2020-03-27","2020-07-25",null,"Approved","2020-09-16",null,"Effective","BA, GO, PC, RC, RP, TO, TOP, TP","https://www.npcc.org/content/docs/public/program-areas/standards-and-criteria/regional-criteria/directories/directory-01-design-and-operation-of-the-bulk-power-system.pdf"]
[101,"Directory #11 V1","Disturbance Monitoring Equipment Criteria","2020-11-08","2020-11-08","2020-11-08",null,"Approved","2020-02-08",null,"Effective","GO, TO","#https://www.npcc.org/content/docs/public/program-areas/standards-and-criteria/regional-criteria/directories/directory-11-disturbance-monitoring-equipment-criteria-full-member-approved-20161027.pdf#"]

{"sheet":"NPCCRequirements","index":4,"n_rows":683,"n_cols":11,"rows_kept":683}
[null,"Standards",{"$nulls":4},"Status"]
["ID","NPCC Directory","NPCC Criteria Name","Req't .","Duplicate Requirement","Text of Requirement","Requirement Enforcement Date","Requirement Inactive Date","Status In Ontario","Applicable to MP Registered FE?","Functional Entities"]
[315,"Directory # 1","Design and Operation of the Bulk Power System","R1.",null,"Each Functional Entity that owns equipment shall submit verified information representing the physical or control characteristics of its equipment for system modelling and reliability analysis of the bulk power system in accordance with Requirement R2.","2014-04-03","2017-01-20","Retired","No"]
[339,"Directory # 1","Design and Operation of the Bulk Power System","R10.",null,"Each Transmission Planner and Planning Coordinator shall have 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 operating conditions which are not prohibited by a procedure and coordinate these procedures with materially affected Transmission Planner and Planning Coordinator Areas.","2014-04-03","2017-01-20","Retired","No"]
[340,"Directory # 1","Design and Operation of the Bulk Power System","R11.",null,"Each Planning Coordinator shall conduct and obtain Reliability Coordinating Committee (RCC) approval for its Transmission Review. Appendix B provides guidance for Transmission Reviews.","2014-04-03","2017-01-20","Retired","No"]
[341,"Directory # 1","Design and Operation of the Bulk Power System","R11.1.",null,"A Comprehensive Transmission Review is required at least once every five years or if major or pervasive system changes have occurred. If changes in the planned facilities or forecasted system conditions warrant, the Task Force on System Studies (TFSS) may require a Comprehensive Transmission Review in less than five years.","2014-04-03","2017-01-20","Retired","No"]
[342,"Directory # 1","Design and Operation of the Bulk Power System","R11.2.",null,"The proposal for the type of annual Transmission Review shall be presented to TFSS by March of the year during which the review is conducted. Approval for the type of Transmission Review shall be obtained from the TFSS. The annual Transmission Review shall be presented to the TFSS by April of the following year.","2014-04-03","2017-01-20","Retired","No"]
[343,"Directory # 1","Design and Operation of the Bulk Power System","R11.3.",null,"If the results of the Transmission Review indicate that the planned bulk power system will not be in conformance with NPCC Directory #1, the Transmission Review shall incorporate a corrective action plan to achieve conformance.","2014-04-03","2017-01-20","Retired","No"]
[344,"Directory # 1","Design and Operation of the Bulk Power System","R12.",null,"Each Functional Entity that proposes a new or modified SPS shall consider the complexity of the scheme and the consequences of correct or incorrect operation as well as its benefits.","2014-04-03","2017-01-20","Retired","No"]
[345,"Directory # 1","Design and Operation of the Bulk Power System","R12.1.",null,"Provide a rationale and justification to the TFCP including factors such as project delays, temporary construction configurations, unusual combinations of system conditions, equipment outages and infrequent contingencies.","2014-04-03","2017-01-20","Retired","No"]
[347,"Directory # 1","Design and Operation of the Bulk Power System","R13.","YES","Each Reliability Coordinator and Transmission Operator shall establish normal transfer capabilities and emergency transfer capabilities, for its portion of the bulk power system to meet the respective performance requirements for the contingencies as specified in Table 3.","2014-04-03","2017-01-20","Retired","No"]
[348,"Directory # 1","Design and Operation of the Bulk Power System","R13.","YES","Each Reliability Coordinator and Transmission Operator shall establish normal transfer capabilities and emergency transfer capabilities, for its portion of the bulk power system to meet the respective performance requirements for the contingencies as specified in Table 3.","2014-04-03","2017-01-20","Retired","No"]
[346,"Directory # 1","Design and Operation of the Bulk Power System","R13.","YES","Each Reliability Coordinator and Transmission Operator shall establish normal transfer capabilities and emergency transfer capabilities, for its portion of the bulk power system to meet the respective performance requirements for the contingencies as specified in Table 3.","2014-04-03","2017-01-20","Retired","No"]
[349,"Directory # 1","Design and Operation of the Bulk Power System","R14.","YES","Each Reliability Coordinator and Transmission Operator shall operate to normal transfer capabilities unless an emergency, in accordance with NPCC Directory# 2, is identified.","2014-04-03","2017-01-20","Retired","No"]
[350,"Directory # 1","Design and Operation of the Bulk Power System","R14.","YES","Each Reliability Coordinator and Transmission Operator shall operate to normal transfer capabilities unless an emergency, in accordance with NPCC Directory# 2, is identified.","2014-04-03","2017-01-20","Retired","No"]
[351,"Directory # 1","Design and Operation of the Bulk Power System","R14.","YES","Each Reliability Coordinator and Transmission Operator shall operate to normal transfer capabilities unless an emergency, in accordance with NPCC Directory# 2, is identified.","2014-04-03","2017-01-20","Retired","No"]
[352,"Directory # 1","Design and Operation of the Bulk Power System","R15.","YES","Each Reliability Coordinator and Transmission Operator shall make system adjustments once an emergency has been identified, including the pre-contingency disconnection of firm load, to avoid exceeding emergency transfer capabilities.","2014-04-03","2017-01-20","Retired","No"]
[353,"Directory # 1","Design and Operation of the Bulk Power System","R15.","YES","Each Reliability Coordinator and Transmission Operator shall make system adjustments once an emergency has been identified, including the pre-contingency disconnection of firm load, to avoid exceeding emergency transfer capabilities.","2014-04-03","2017-01-20","Retired","No"]
[354,"Directory # 1","Design and Operation of the Bulk Power System","R16.","YES","Each Reliability Coordinator and Transmission Operator shall assess the status of the bulk power system immediately after the occurrence of any contingency and prepare for the next contingency as specified in Table 3.","2014-04-03","2017-01-20","Retired","No"]
[355,"Directory # 1","Design and Operation of the Bulk Power System","R16.","YES","Each Reliability Coordinator and Transmission Operator shall assess the status of the bulk power system immediately after the occurrence of any contingency and prepare for the next contingency as specified in Table 3.","2014-04-03","2017-01-20","Retired","No"]
[356,"Directory # 1","Design and Operation of the Bulk Power System","R16.1.","YES","Voltage reduction and shedding of firm load shall be deployed to return the system to a secure state, if other system adjustments are not adequate. Voltage reduction need not be initiated and firm load need not be shed to observe a post contingency loading requirement until the contingency occurs, provided that adequate response time for this action is available.","2014-04-03","2017-01-20","Retired","No"]
[357,"Directory # 1","Design and Operation of the Bulk Power System","R16.1.","YES","Voltage reduction and shedding of firm load shall be deployed to return the system to a secure state, if other system adjustments are not adequate. Voltage reduction need not be initiated and firm load need not be shed to observe a post contingency loading requirement until the contingency occurs, provided that adequate response time for this action is available.","2014-04-03","2017-01-20","Retired","No"]
[359,"Directory # 1","Design and Operation of the Bulk Power System","R16.2.","YES","System adjustments shall be completed as quickly as possible following any contingency, but within 30 minutes after the occurrence of any contingency specified in Table 3.","2014-04-03","2017-01-20","Retired","No"]
[358,"Directory # 1","Design and Operation of the Bulk Power System","R16.2.","YES","System adjustments shall be completed as quickly as possible following any contingency, but within 30 minutes after the occurrence of any contingency specified in Table 3.","2014-04-03","2017-01-20","Retired","No"]
[360,"Directory # 1","Design and Operation of the Bulk Power System","R17.","YES","Each Reliability Coordinator shall notify the applicable Reliability Coordinators of forced outages of any facility as per the NPCC Transmission Facilities Notification List and of any other condition which may impact inter-Area reliability.","2014-04-03","2017-01-20","Retired","No"]
[361,"Directory # 1","Design and Operation of the Bulk Power System","R17.","YES","Each Reliability Coordinator shall notify the applicable Reliability Coordinators of forced outages of any facility as per the NPCC Transmission Facilities Notification List and of any other condition which may impact inter-Area reliability.","2014-04-03","2017-01-20","Retired","No"]
[363,"Directory # 1","Design and Operation of the Bulk Power System","R18.","YES","Each Reliability Coordinator shall coordinate scheduled outages of facilities that are on the NPCC Transmission Facilities Notification List sufficiently in advance of the outage to permit the affected Reliability Coordinators to maintain reliability. Appendix F provides guidance for Operational Planning Coordination.","2014-04-03","2017-01-20","Retired","No"]
[362,"Directory # 1","Design and Operation of the Bulk Power System","R18.","YES","Each Reliability Coordinator shall coordinate scheduled outages of facilities that are on the NPCC Transmission Facilities Notification List sufficiently in advance of the outage to permit the affected Reliability Coordinators to maintain reliability. Appendix F provides guidance for Operational Planning Coordination.","2014-04-03","2017-01-20","Retired","No"]
[364,"Directory # 1","Design and Operation of the Bulk Power System","R18.1.","YES","Review and update its Facilities Notification List and submit the list to the NPCC Task Force on Coordination of Operation (TFCO) annually.","2014-04-03","2017-01-20","Retired","No"]
[365,"Directory # 1","Design and Operation of the Bulk Power System","R18.1.","YES","Review and update its Facilities Notification List and submit the list to the NPCC Task Force on Coordination of Operation (TFCO) annually.","2014-04-03","2017-01-20","Retired","No"]
[366,"Directory # 1","Design and Operation of the Bulk Power System","R19.",null,"Each Reliability Coordinator shall coordinate voltage control between Transmission Operator Areas. Appendix G provides guidance for Inter- Reliability Coordinator Area Voltage Control.","2014-04-03","2017-01-20","Retired","No"]
[367,"Directory # 1","Design and Operation of the Bulk Power System","R19.1.",null,"Metering for reactive power resources and voltage controller status shall be consistent between adjacent Transmission Operators.","2014-04-03","2017-01-20","Retired","No"]
[368,"Directory # 1","Design and Operation of the Bulk Power System","R19.2.",null,"Upon request from the TFCO, perform an Inter-Area Voltage Control Assessment.","2014-04-03","2017-01-20","Retired","No"]
[316,"Directory # 1","Design and Operation of the Bulk Power System","R2.","YES","Each Planning Coordinator and Reliability Coordinator shall collect and maintain information needed for system modelling and reliability analysis of the bulk power system.","2014-04-03","2017-01-20","Retired","No"]
[317,"Directory # 1","Design and Operation of the Bulk Power System","R2.","YES","Each Planning Coordinator and Reliability Coordinator shall collect and maintain information needed for system modelling and reliability analysis of the bulk power system.","2014-04-03","2017-01-20","Retired","No"]
[318,"Directory # 1","Design and Operation of the Bulk Power System","R2.","YES","Each Planning Coordinator and Reliability Coordinator shall collect and maintain information needed for system modelling and reliability analysis of the bulk power system.","2014-04-03","2017-01-20","Retired","No"]
[319,"Directory # 1","Design and Operation of the Bulk Power System","R2.1.","YES","System modelling information shall be submitted to an NPCC Task Force upon request.","2014-04-03","2017-01-20","Retired","No"]
[320,"Directory # 1","Design and Operation of the Bulk Power System","R2.1.","YES","System modelling information shall be submitted to an NPCC Task Force upon request.","2014-04-03","2017-01-20","Retired","No"]
[321,"Directory # 1","Design and Operation of the Bulk Power System","R2.1.","YES","System modelling information shall be submitted to an NPCC Task Force upon request.","2014-04-03","2017-01-20","Retired","No"]
[322,"Directory # 1","Design and Operation of the Bulk Power System","R3.","YES","Each Reliability Coordinator shall share and coordinate forecast system information and real-time information to enable and enhance the analysis and modeling of the interconnected bulk power system by security application software on energy management systems.","2014-04-03","2017-01-20","Retired","No"]
[324,"Directory # 1","Design and Operation of the Bulk Power System","R3.","YES","Each Reliability Coordinator shall share and coordinate forecast system information and real-time information to enable and enhance the analysis and modeling of the interconnected bulk power system by security application software on energy management systems.","2014-04-03","2017-01-20","Retired","No"]
[323,"Directory # 1","Design and Operation of the Bulk Power System","R3.","YES","Each Reliability Coordinator shall share and coordinate forecast system information and real-time information to enable and enhance the analysis and modeling of the interconnected bulk power system by security application software on energy management systems.","2014-04-03","2017-01-20","Retired","No"]
[325,"Directory # 1","Design and Operation of the Bulk Power System","R4.",null,"Each Planning Coordinator or Resource Planner shall probabilistically evaluate resource adequacy of its Planning Coordinator Area portion of the bulk power system to demonstrate that the loss of load expectation (LOLE) of disconnecting firm load due to resource deficiencies is, on average, no more than 0.1 days per year.","2014-04-03","2017-01-20","Retired","No"]
[326,"Directory # 1","Design and Operation of the Bulk Power System","R4.1.",null,"Make due allowances for demand uncertainty, scheduled outages and deratings, forced outages and deratings, assistance over interconnections with neighboring Planning Coordinator Areas, transmission transfer capabilities, and capacity and/or load relief from available operating procedures.","2014-04-03","2017-01-20","Retired","No"]
[327,"Directory # 1","Design and Operation of the Bulk Power System","R5.",null,"Each Planning Coordinator shall report and obtain Reliability Coordinating Committee (RCC) approval for its Review of Resource Adequacy. Appendix D provides guidance for the Area Review of Resource Adequacy.","2014-04-03","2017-01-20","Retired","No"]
[328,"Directory # 1","Design and Operation of the Bulk Power System","R5.1.",null,"The Review of Resource Adequacy will be presented to the NPCC Task Force on Coordination of Planning (TFCP). Comprehensive and Interim reviews shall be presented to the TFCP before the beginning of the first time period covered by the assessment.","2014-04-03","2017-01-20","Retired","No"]
[329,"Directory # 1","Design and Operation of the Bulk Power System","R5.2.",null,"A Comprehensive Review of Resource Adequacy is required every three years and will cover a time period of five years. If changes in planned facilities or forecasted system conditions warrant, TFCP may require a Comprehensive Review of Resource Adequacy in less than 3 years.","2014-04-03","2017-01-20","Retired","No"]
[330,"Directory # 1","Design and Operation of the Bulk Power System","R5.3.",null,"In subsequent years, each Planning Coordinator shall conduct an Annual Interim Review of Resource Adequacy that will cover, at a minimum, the remaining years studied in the Comprehensive Review of Resource Adequacy.","2014-04-03","2017-01-20","Retired","No"]
[332,"Directory # 1","Design and Operation of the Bulk Power System","R6.","YES","Each Reliability Coordinator shall coordinate outages and deratings of resources to verify adequate resources will be available to meet the forecasted demand and reserve requirements. Appendix F provides guidance for Operational Planning Coordination.","2014-04-03","2017-01-20","Retired","No"]
[331,"Directory # 1","Design and Operation of the Bulk Power System","R6.","YES","Each Reliability Coordinator shall coordinate outages and deratings of resources to verify adequate resources will be available to meet the forecasted demand and reserve requirements. Appendix F provides guidance for Operational Planning Coordination.","2014-04-03","2017-01-20","Retired","No"]
[334,"Directory # 1","Design and Operation of the Bulk Power System","R6.1.","YES","A Summer and Winter Reliability Assessment will be presented to the NPCC Task Force on Coordination of Operation (TFCO) every year.","2014-04-03","2017-01-20","Retired","No"]
[333,"Directory # 1","Design and Operation of the Bulk Power System","R6.1.","YES","A Summer and Winter Reliability Assessment will be presented to the NPCC Task Force on Coordination of Operation (TFCO) every year.","2014-04-03","2017-01-20","Retired","No"]
[335,"Directory # 1","Design and Operation of the Bulk Power System","R7.",null,"Each Transmission Planner and Planning Coordinator shall plan its bulk power system to have sufficient transmission capability to meet the respective requirements as specified in Table 1 while serving forecasted demand.","2014-04-03","2017-01-20","Retired","No"]
[336,"Directory # 1","Design and Operation of the Bulk Power System","R7.1.",null,"Credible combinations of system conditions which stress the system shall be modelled including, load forecast, inter-Area and intra-Area transfers, transmission configuration, active and reactive resources, generation availability and other dispatch scenarios. All reclosing facilities shall be assumed in service unless it is known that such facilities will be rendered inoperative.","2014-04-03","2017-01-20","Retired","No"]
[337,"Directory # 1","Design and Operation of the Bulk Power System","R8.",null,"Each Transmission Planner and Planning Coordinator shall assess the impact of the extreme contingencies listed in Table 2. Appendix C provides guidance for testing and analyzing extreme contingencies.","2014-04-03","2017-01-20","Retired","No"]
[338,"Directory # 1","Design and Operation of the Bulk Power System","R9.",null,"Each Transmission Planner and Planning Coordinator shall assess the impact of extreme system conditions, one condition at a time, subject to contingencies as listed in the “Extreme System Conditions” category of Table 2.","2014-04-03","2017-01-20","Retired","No"]
[1,"Directory # 1 V2","Design and Operation of the Bulk Power System","R1.",null,"Each Functional Entity that owns equipment shall submit verified information representing the physical or control characteristics of its equipment for system modelling and reliability analysis of the bulk power system in accordance with Requirement R2.","2017-01-21","2020-09-16","Retired","Yes","RP, TP, PC, BA, TOP, RC, TO, GO"]
[2,"Directory # 1 V2","Design and Operation of the Bulk Power System","R10.",null,"Each Transmission Planner and Planning Coordinator shall have 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 operating conditions which are not prohibited by a procedure and coordinate these procedures with materially affected Transmission Planner and Planning Coordinator Areas.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, BA, TOP, RC, TP, PC"]
[3,"Directory # 1 V2","Design and Operation of the Bulk Power System","R11.",null,"Each Planning Coordinator shall conduct and obtain Reliability Coordinating Committee (RCC) approval for its Transmission Review. Appendix B provides guidance for Transmission Reviews.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, BA, TOP, RC, PC"]
[4,"Directory # 1 V2","Design and Operation of the Bulk Power System","R11.1",null,"A Comprehensive Transmission Review is required at least once every five years or if major or pervasive system changes have occurred. If changes in the planned facilities or forecasted system conditions warrant, the Task Force on System Studies (TFSS) may require a Comprehensive Transmission Review in less than five years.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[5,"Directory # 1 V2","Design and Operation of the Bulk Power System","R11.2",null,"The proposal for the type of annual Transmission Review shall be presented to TFSS by March of the year during which the review is conducted. Approval for the type of Transmission Review shall be obtained from the TFSS. The annual Transmission Review shall be presented to the TFSS by April of the following year.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[6,"Directory # 1 V2","Design and Operation of the Bulk Power System","R11.3",null,"If the results of the Transmission Review indicate that the planned bulk power system will not be in conformance with NPCC Directory #1, the Transmission Review shall incorporate a corrective action plan to achieve conformance.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[7,"Directory # 1 V2","Design and Operation of the Bulk Power System","R12.",null,"Each Functional Entity that proposes a new or modified SPS shall consider the complexity of the scheme and the consequences of correct or incorrect operation as well as its benefits.","2017-01-21","2020-09-16","Retired","Yes","RP, TP, PC, BA, TOP, RC, TO, GO"]
[8,"Directory # 1 V2","Design and Operation of the Bulk Power System","R12.1",null,"Provide a rationale and justification to the TFCP including factors such as project delays, temporary construction configurations, unusual combinations of system conditions, equipment outages and infrequent contingencies.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC, TO, GO"]
[11,"Directory # 1 V2","Design and Operation of the Bulk Power System","R13.","YES","Each Reliability Coordinator and Transmission Operator shall establish normal transfer capabilities and emergency transfer capabilities, for its portion of the bulk power system to meet the respective performance requirements for the contingencies as specified in Table 3.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[9,"Directory # 1 V2","Design and Operation of the Bulk Power System","R13.","YES","Each Reliability Coordinator and Transmission Operator shall establish normal transfer capabilities and emergency transfer capabilities, for its portion of the bulk power system to meet the respective performance requirements for the contingencies as specified in Table 3.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[10,"Directory # 1 V2","Design and Operation of the Bulk Power System","R13.","YES","Each Reliability Coordinator and Transmission Operator shall establish normal transfer capabilities and emergency transfer capabilities, for its portion of the bulk power system to meet the respective performance requirements for the contingencies as specified in Table 3.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[13,"Directory # 1 V2","Design and Operation of the Bulk Power System","R14.","YES","Each Reliability Coordinator and Transmission Operator shall operate to normal transfer capabilities unless an emergency, in accordance with NPCC Directory# 2, is identified.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[14,"Directory # 1 V2","Design and Operation of the Bulk Power System","R14.","YES","Each Reliability Coordinator and Transmission Operator shall operate to normal transfer capabilities unless an emergency, in accordance with NPCC Directory# 2, is identified.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[12,"Directory # 1 V2","Design and Operation of the Bulk Power System","R14.","YES","Each Reliability Coordinator and Transmission Operator shall operate to normal transfer capabilities unless an emergency, in accordance with NPCC Directory# 2, is identified.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[15,"Directory # 1 V2","Design and Operation of the Bulk Power System","R15.","YES","Each Reliability Coordinator and Transmission Operator shall make system adjustments once an emergency has been identified, including the pre-contingency disconnection of firm load, to avoid exceeding emergency transfer capabilities.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[16,"Directory # 1 V2","Design and Operation of the Bulk Power System","R15.","YES","Each Reliability Coordinator and Transmission Operator shall make system adjustments once an emergency has been identified, including the pre-contingency disconnection of firm load, to avoid exceeding emergency transfer capabilities.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[17,"Directory # 1 V2","Design and Operation of the Bulk Power System","R16.","YES","Each Reliability Coordinator and Transmission Operator shall assess the status of the bulk power system immediately after the occurrence of any contingency and prepare for the next contingency as specified in Table 3.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[18,"Directory # 1 V2","Design and Operation of the Bulk Power System","R16.","YES","Each Reliability Coordinator and Transmission Operator shall assess the status of the bulk power system immediately after the occurrence of any contingency and prepare for the next contingency as specified in Table 3.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[19,"Directory # 1 V2","Design and Operation of the Bulk Power System","R16.1","YES","Voltage reduction and shedding of firm load shall be deployed to return the system to a secure state, if other system adjustments are not adequate. Voltage reduction need not be initiated and firm load need not be shed to observe a post contingency loading requirement until the contingency occurs, provided that adequate response time for this action is available.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[20,"Directory # 1 V2","Design and Operation of the Bulk Power System","R16.1","YES","Voltage reduction and shedding of firm load shall be deployed to return the system to a secure state, if other system adjustments are not adequate. Voltage reduction need not be initiated and firm load need not be shed to observe a post contingency loading requirement until the contingency occurs, provided that adequate response time for this action is available.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[21,"Directory # 1 V2","Design and Operation of the Bulk Power System","R16.2","YES","System adjustments shall be completed as quickly as possible following any contingency, but within 30 minutes after the occurrence of any contingency specified in Table 3.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[22,"Directory # 1 V2","Design and Operation of the Bulk Power System","R16.2","YES","System adjustments shall be completed as quickly as possible following any contingency, but within 30 minutes after the occurrence of any contingency specified in Table 3.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[23,"Directory # 1 V2","Design and Operation of the Bulk Power System","R17.","YES","Each Reliability Coordinator shall notify the applicable Reliability Coordinators of forced outages of any facility as per the NPCC Transmission Facilities Notification List and of any other condition which may impact inter-Area reliability.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[24,"Directory # 1 V2","Design and Operation of the Bulk Power System","R17.","YES","Each Reliability Coordinator shall notify the applicable Reliability Coordinators of forced outages of any facility as per the NPCC Transmission Facilities Notification List and of any other condition which may impact inter-Area reliability.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[26,"Directory # 1 V2","Design and Operation of the Bulk Power System","R18.","YES","Each Reliability Coordinator shall coordinate scheduled outages of facilities that are on the NPCC Transmission Facilities Notification List sufficiently in advance of the outage to permit the affected Reliability Coordinators to maintain reliability. Appendix F provides guidance for Operational Planning Coordination.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[25,"Directory # 1 V2","Design and Operation of the Bulk Power System","R18.","YES","Each Reliability Coordinator shall coordinate scheduled outages of facilities that are on the NPCC Transmission Facilities Notification List sufficiently in advance of the outage to permit the affected Reliability Coordinators to maintain reliability. Appendix F provides guidance for Operational Planning Coordination.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[28,"Directory # 1 V2","Design and Operation of the Bulk Power System","R18.1.","YES","Review and update its Facilities Notification List and submit the list to the NPCC Task Force on Coordination of Operation (TFCO) annually.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[27,"Directory # 1 V2","Design and Operation of the Bulk Power System","R18.1.","YES","Review and update its Facilities Notification List and submit the list to the NPCC Task Force on Coordination of Operation (TFCO) annually.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[29,"Directory # 1 V2","Design and Operation of the Bulk Power System","R19.",null,"Each Reliability Coordinator shall coordinate voltage control between Transmission Operator Areas. Appendix G provides guidance for Inter- Reliability Coordinator Area Voltage Control.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[30,"Directory # 1 V2","Design and Operation of the Bulk Power System","R19.1.",null,"Metering for reactive power resources and voltage controller status shall be consistent between adjacent Transmission Operators.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[31,"Directory # 1 V2","Design and Operation of the Bulk Power System","R19.2.",null,"Upon request from the TFCO, perform an Inter-Area Voltage Control Assessment.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[33,"Directory # 1 V2","Design and Operation of the Bulk Power System","R2.","YES","Each Planning Coordinator and Reliability Coordinator shall collect and maintain information needed for system modelling and reliability analysis of the bulk power system.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[32,"Directory # 1 V2","Design and Operation of the Bulk Power System","R2.","YES","Each Planning Coordinator and Reliability Coordinator shall collect and maintain information needed for system modelling and reliability analysis of the bulk power system.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, BA, TOP, RC, PC"]
[34,"Directory # 1 V2","Design and Operation of the Bulk Power System","R2.","YES","Each Planning Coordinator and Reliability Coordinator shall collect and maintain information needed for system modelling and reliability analysis of the bulk power system.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[37,"Directory # 1 V2","Design and Operation of the Bulk Power System","R2.1.","YES","System modelling information shall be submitted to an NPCC Task Force upon request.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[36,"Directory # 1 V2","Design and Operation of the Bulk Power System","R2.1.","YES","System modelling information shall be submitted to an NPCC Task Force upon request.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[35,"Directory # 1 V2","Design and Operation of the Bulk Power System","R2.1.","YES","System modelling information shall be submitted to an NPCC Task Force upon request.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, BA, TOP, RC, PC"]
[38,"Directory # 1 V2","Design and Operation of the Bulk Power System","R3.","YES","Each Reliability Coordinator shall share and coordinate forecast system information and real-time information to enable and enhance the analysis and modeling of the interconnected bulk power system by security application software on energy management systems.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[39,"Directory # 1 V2","Design and Operation of the Bulk Power System","R3.","YES","Each Reliability Coordinator shall share and coordinate forecast system information and real-time information to enable and enhance the analysis and modeling of the interconnected bulk power system by security application software on energy management systems.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[40,"Directory # 1 V2","Design and Operation of the Bulk Power System","R3.","YES","Each Reliability Coordinator shall share and coordinate forecast system information and real-time information to enable and enhance the analysis and modeling of the interconnected bulk power system by security application software on energy management systems.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[41,"Directory # 1 V2","Design and Operation of the Bulk Power System","R4.",null,"Each Planning Coordinator or Resource Planner shall probabilistically evaluate resource adequacy of its Planning Coordinator Area portion of the bulk power system to demonstrate that the loss of load expectation (LOLE) of disconnecting firm load due to resource deficiencies is, on average, no more than 0.1 days per year.","2017-01-21","2020-09-16","Retired","Yes","TP, GO, TO, BA, TOP, RC, RP, PC"]
[42,"Directory # 1 V2","Design and Operation of the Bulk Power System","R4.1.",null,"Make due allowances for demand uncertainty, scheduled outages and deratings, forced outages and deratings, assistance over interconnections with neighboring Planning Coordinator Areas, transmission transfer capabilities, and capacity and/or load relief from available operating procedures.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, TP, BA, TOP, RC, RP, PC"]
[43,"Directory # 1 V2","Design and Operation of the Bulk Power System","R5.",null,"Each Planning Coordinator shall report and obtain Reliability Coordinating Committee (RCC) approval for its Review of Resource Adequacy. Appendix D provides guidance for the Area Review of Resource Adequacy.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, TP, RP, PC, BA, TOP, PC"]
[44,"Directory # 1 V2","Design and Operation of the Bulk Power System","R5.1",null,"The Review of Resource Adequacy will be presented to the NPCC Task Force on Coordination of Planning (TFCP). Comprehensive and Interim reviews shall be presented to the TFCP before the beginning of the first time period covered by the assessment.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, BA, TOP, RC, PC"]
[45,"Directory # 1 V2","Design and Operation of the Bulk Power System","R5.2.",null,"A Comprehensive Review of Resource Adequacy is required every three years and will cover a time period of five years. If changes in planned facilities or forecasted system conditions warrant, TFCP may require a Comprehensive Review of Resource Adequacy in less than 3 years.","2017-01-21","2020-09-16","Retired","Yes","PC, TO, GO, RP, TP, PC, BA, TOP, RC, PC"]
[46,"Directory # 1 V2","Design and Operation of the Bulk Power System","R5.3.",null,"In subsequent years, each Planning Coordinator shall conduct an Annual Interim Review of Resource Adequacy that will cover, at a minimum, the remaining years studied in the Comprehensive Review of Resource Adequacy.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, BA, TOP, RC, PC"]
[47,"Directory # 1 V2","Design and Operation of the Bulk Power System","R6.","YES","Each Reliability Coordinator shall coordinate outages and deratings of resources to verify adequate resources will be available to meet the forecasted demand and reserve requirements. Appendix F provides guidance for Operational Planning Coordination.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, PC, TP, BA, TOP, RC"]
[48,"Directory # 1 V2","Design and Operation of the Bulk Power System","R6.","YES","Each Reliability Coordinator shall coordinate outages and deratings of resources to verify adequate resources will be available to meet the forecasted demand and reserve requirements. Appendix F provides guidance for Operational Planning Coordination.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[50,"Directory # 1 V2","Design and Operation of the Bulk Power System","R6.1","YES","A Summer and Winter Reliability Assessment will be presented to the NPCC Task Force on Coordination of Operation (TFCO) every year.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[49,"Directory # 1 V2","Design and Operation of the Bulk Power System","R6.1","YES","A Summer and Winter Reliability Assessment will be presented to the NPCC Task Force on Coordination of Operation (TFCO) every year.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, TP, PC, BA, TOP, RC"]
[51,"Directory # 1 V2","Design and Operation of the Bulk Power System","R7.",null,"Each Transmission Planner and Planning Coordinator shall plan its bulk power system to have sufficient transmission capability to meet the respective requirements as specified in Table 1 while serving forecasted demand.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, BA, TOP, RC, TP, PC"]
[52,"Directory # 1 V2","Design and Operation of the Bulk Power System","R7.1.",null,"Credible combinations of system conditions which stress the system shall be modelled including, load forecast, inter-Area and intra-Area transfers, transmission configuration, active and reactive resources, generation availability and other dispatch scenarios. All reclosing facilities shall be assumed in service unless it is known that such facilities will be rendered inoperative.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, BA, TOP, RC, TP, PC"]
[53,"Directory # 1 V2","Design and Operation of the Bulk Power System","R8.",null,"Each Transmission Planner and Planning Coordinator shall assess the impact of the extreme contingencies listed in Table 2. Appendix C provides guidance for testing and analyzing extreme contingencies.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, BA, TOP, RC, TP, PC"]
[54,"Directory # 1 V2","Design and Operation of the Bulk Power System","R9.",null,"Each Transmission Planner and Planning Coordinator shall assess the impact of extreme system conditions, one condition at a time, subject to contingencies as listed in the “Extreme System Conditions” category of Table 2.","2017-01-21","2020-09-16","Retired","Yes","TO, GO, RP, BA, TOP, RC, TP, PC"]
[698,"Directory # 1 V3","Design and Operation of the Bulk Power System","R.10.",null,"Each Transmission Planner and Planning Coordinator shall have 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 operating conditions which are not prohibited by a procedure and coordinate these procedures with materially affected Transmission Planner and Planning Coordinator Areas.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[600,"Directory # 1 V3","Design and Operation of the Bulk Power System","R1.",null,"Each Functional Entity that owns equipment shall submit verified information representing the physical or control characteristics of its equipment for system modelling and reliability analysis of the bulk power system in accordance with Requirement R2.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[699,"Directory # 1 V3","Design and Operation of the Bulk Power System","R11.",null,"Each Planning Coordinator shall conduct and obtain Reliability Coordinating Committee (RCC) approval for its Transmission Review. Appendix B provides guidance for Transmission Reviews.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[700,"Directory # 1 V3","Design and Operation of the Bulk Power System","R11.1.",null,"A Comprehensive Transmission Review is required at least once every five years or if major or pervasive system changes have occurred. If changes in the planned facilities or forecasted system conditions warrant, the Task Force on System Studies (TFSS) may require a Comprehensive Transmission Review in less than five years.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[701,"Directory # 1 V3","Design and Operation of the Bulk Power System","R11.2.",null,"The proposal for the type of annual Transmission Review shall be presented to TFSS by March of the year during which the review is conducted. Approval for the type of Transmission Review shall be obtained from the TFSS. The annual Transmission Review shall be presented to the TFSS by April of the following year.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[702,"Directory # 1 V3","Design and Operation of the Bulk Power System","R11.3.",null,"If the results of the Transmission Review indicate that the planned bulk power system will not be in conformance with NPCC Directory #1, the Transmission Review shall incorporate a corrective action plan to achieve conformance.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[703,"Directory # 1 V3","Design and Operation of the Bulk Power System","R12.",null,"Each Functional Entity that proposes a new or modified SPS shall consider the complexity of the scheme and the consequences of correct or incorrect operation as well as its benefits.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[704,"Directory # 1 V3","Design and Operation of the Bulk Power System","R12.1.",null,"Provide a rationale and justification to the TFCP including factors such as project delays, temporary construction configurations, unusual combinations of system conditions, equipment outages and infrequent contingencies.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[707,"Directory # 1 V3","Design and Operation of the Bulk Power System","R13.","YES","Each Reliability Coordinator and Transmission Operator shall establish normal transfer capabilities and emergency transfer capabilities, for its portion of the bulk power system to meet the respective performance requirements for the contingencies as specified in Table 3.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[706,"Directory # 1 V3","Design and Operation of the Bulk Power System","R13.","YES","Each Reliability Coordinator and Transmission Operator shall establish normal transfer capabilities and emergency transfer capabilities, for its portion of the bulk power system to meet the respective performance requirements for the contingencies as specified in Table 3.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[705,"Directory # 1 V3","Design and Operation of the Bulk Power System","R13.","YES","Each Reliability Coordinator and Transmission Operator shall establish normal transfer capabilities and emergency transfer capabilities, for its portion of the bulk power system to meet the respective performance requirements for the contingencies as specified in Table 3.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[708,"Directory # 1 V3","Design and Operation of the Bulk Power System","R14.","YES","Each Reliability Coordinator and Transmission Operator shall operate to normal transfer capabilities unless an emergency, in accordance with NPCC Directory# 2, is identified.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[709,"Directory # 1 V3","Design and Operation of the Bulk Power System","R14.","YES","Each Reliability Coordinator and Transmission Operator shall operate to normal transfer capabilities unless an emergency, in accordance with NPCC Directory# 2, is identified.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[710,"Directory # 1 V3","Design and Operation of the Bulk Power System","R14.","YES","Each Reliability Coordinator and Transmission Operator shall operate to normal transfer capabilities unless an emergency, in accordance with NPCC Directory# 2, is identified.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[712,"Directory # 1 V3","Design and Operation of the Bulk Power System","R15.","YES","Each Reliability Coordinator and Transmission Operator shall make system adjustments once an emergency has been identified, including the pre-contingency disconnection of firm load, to avoid exceeding emergency transfer capabilities.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[711,"Directory # 1 V3","Design and Operation of the Bulk Power System","R15.","YES","Each Reliability Coordinator and Transmission Operator shall make system adjustments once an emergency has been identified, including the pre-contingency disconnection of firm load, to avoid exceeding emergency transfer capabilities.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[713,"Directory # 1 V3","Design and Operation of the Bulk Power System","R16.","YES","Each Reliability Coordinator and Transmission Operator shall assess the status of the bulk power system immediately after the occurrence of any contingency and prepare for the next contingency as specified in Table 3.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[714,"Directory # 1 V3","Design and Operation of the Bulk Power System","R16.","YES","Each Reliability Coordinator and Transmission Operator shall assess the status of the bulk power system immediately after the occurrence of any contingency and prepare for the next contingency as specified in Table 3.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[715,"Directory # 1 V3","Design and Operation of the Bulk Power System","R16.1","YES","Voltage reduction and shedding of firm load shall be deployed to return the system to a secure state, if other system adjustments are not adequate. Voltage reduction need not be initiated and firm load need not be shed to observe a post contingency loading requirement until the contingency occurs, provided that adequate response time for this action is available.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[716,"Directory # 1 V3","Design and Operation of the Bulk Power System","R16.1","YES","Voltage reduction and shedding of firm load shall be deployed to return the system to a secure state, if other system adjustments are not adequate. Voltage reduction need not be initiated and firm load need not be shed to observe a post contingency loading requirement until the contingency occurs, provided that adequate response time for this action is available.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[717,"Directory # 1 V3","Design and Operation of the Bulk Power System","R16.2.","YES","System adjustments shall be completed as quickly as possible following any contingency, but within 30 minutes after the occurrence of any contingency specified in Table 3.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[718,"Directory # 1 V3","Design and Operation of the Bulk Power System","R16.2.","YES","System adjustments shall be completed as quickly as possible following any contingency, but within 30 minutes after the occurrence of any contingency specified in Table 3.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[719,"Directory # 1 V3","Design and Operation of the Bulk Power System","R17.","YES","Each Reliability Coordinator shall notify the applicable Reliability Coordinators of forced outages of any facility as per the NPCC Transmission Facilities Notification List and of any other condition which may impact inter-Area reliability.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[720,"Directory # 1 V3","Design and Operation of the Bulk Power System","R17.","YES","Each Reliability Coordinator shall notify the applicable Reliability Coordinators of forced outages of any facility as per the NPCC Transmission Facilities Notification List and of any other condition which may impact inter-Area reliability.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[722,"Directory # 1 V3","Design and Operation of the Bulk Power System","R18.","YES","Each Reliability Coordinator shall coordinate scheduled outages of facilities that are on the NPCC Transmission Facilities Notification List sufficiently in advance of the outage to permit the affected Reliability Coordinators to maintain reliability. Appendix F provides guidance for Operational Planning Coordination.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[721,"Directory # 1 V3","Design and Operation of the Bulk Power System","R18.","YES","Each Reliability Coordinator shall coordinate scheduled outages of facilities that are on the NPCC Transmission Facilities Notification List sufficiently in advance of the outage to permit the affected Reliability Coordinators to maintain reliability. Appendix F provides guidance for Operational Planning Coordination.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[724,"Directory # 1 V3","Design and Operation of the Bulk Power System","R18.1.","YES","Review and update its Facilities Notification List and submit the list to the NPCC Task Force on Coordination of Operation (TFCO) annually.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[723,"Directory # 1 V3","Design and Operation of the Bulk Power System","R18.1.","YES","Review and update its Facilities Notification List and submit the list to the NPCC Task Force on Coordination of Operation (TFCO) annually.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[725,"Directory # 1 V3","Design and Operation of the Bulk Power System","R19.",null,"Each Reliability Coordinator shall coordinate voltage control between Transmission Operator Areas. Appendix G provides guidance for Inter- Reliability Coordinator Area Voltage Control.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[726,"Directory # 1 V3","Design and Operation of the Bulk Power System","R19.1",null,"Metering for reactive power resources and voltage controller status shall be consistent between adjacent Transmission Operators.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[727,"Directory # 1 V3","Design and Operation of the Bulk Power System","R19.2.",null,"Upon request from the TFCO, perform an Inter-Area Voltage Control Assessment.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[618,"Directory # 1 V3","Design and Operation of the Bulk Power System","R2.","YES","Each Planning Coordinator and Reliability Coordinator shall collect and maintain information needed for system modelling and reliability analysis of the bulk power system.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[632,"Directory # 1 V3","Design and Operation of the Bulk Power System","R2.","YES","Each Planning Coordinator and Reliability Coordinator shall collect and maintain information needed for system modelling and reliability analysis of the bulk power system.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[610,"Directory # 1 V3","Design and Operation of the Bulk Power System","R2.","YES","Each Planning Coordinator and Reliability Coordinator shall collect and maintain information needed for system modelling and reliability analysis of the bulk power system.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[611,"Directory # 1 V3","Design and Operation of the Bulk Power System","R2.1.","YES","System modelling information shall be submitted to an NPCC Task Force upon request.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[612,"Directory # 1 V3","Design and Operation of the Bulk Power System","R2.1.","YES","System modelling information shall be submitted to an NPCC Task Force upon request.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[613,"Directory # 1 V3","Design and Operation of the Bulk Power System","R2.1.","YES","System modelling information shall be submitted to an NPCC Task Force upon request.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[614,"Directory # 1 V3","Design and Operation of the Bulk Power System","R3.","YES","Each Reliability Coordinator shall share and coordinate forecast system information and real-time information to enable and enhance the analysis and modeling of the interconnected bulk power system by security application software on energy management systems.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[617,"Directory # 1 V3","Design and Operation of the Bulk Power System","R3.","YES","Each Reliability Coordinator shall share and coordinate forecast system information and real-time information to enable and enhance the analysis and modeling of the interconnected bulk power system by security application software on energy management systems.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[615,"Directory # 1 V3","Design and Operation of the Bulk Power System","R3.","YES","Each Reliability Coordinator shall share and coordinate forecast system information and real-time information to enable and enhance the analysis and modeling of the interconnected bulk power system by security application software on energy management systems.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[674,"Directory # 1 V3","Design and Operation of the Bulk Power System","R4.","YES","Each Planning Coordinator or Resource Planner shall probabilistically evaluate resource adequacy of its Planning Coordinator Area portion of the bulk power system to demonstrate that the loss of load expectation (LOLE) of disconnecting firm load due to resource deficiencies is, on average, no more than 0.1 days per year.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[675,"Directory # 1 V3","Design and Operation of the Bulk Power System","R4.","YES","ach Planning Coordinator or Resource Planner shall probabilistically evaluate resource adequacy of its Planning Coordinator Area portion of the bulk power system to demonstrate that the loss of load expectation (LOLE) of disconnecting firm load due to resource deficiencies is, on average, no more than 0.1 days per year.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[685,"Directory # 1 V3","Design and Operation of the Bulk Power System","R4.1.","YES","Make due allowances for demand uncertainty, scheduled outages and deratings, forced outages and deratings, assistance over interconnections with neighboring Planning Coordinator Areas, transmission transfer capabilities, and capacity and/or load relief from available operating procedures.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[684,"Directory # 1 V3","Design and Operation of the Bulk Power System","R4.1.","YES","Make due allowances for demand uncertainty, scheduled outages and deratings, forced outages and deratings, assistance over interconnections with neighboring Planning Coordinator Areas, transmission transfer capabilities, and capacity and/or load relief from available operating procedures.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[686,"Directory # 1 V3","Design and Operation of the Bulk Power System","R5.",null,"Each Planning Coordinator shall report and obtain Reliability Coordinating Committee (RCC) approval for its Review of Resource Adequacy. Appendix D provides guidance for the Area Review of Resource Adequacy.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[687,"Directory # 1 V3","Design and Operation of the Bulk Power System","R5.1.",null,"The Review of Resource Adequacy will be presented to the NPCC Task Force on Coordination of Planning (TFCP). Comprehensive and Interim reviews shall be presented to the TFCP before the beginning of the first time period covered by the assessment.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[688,"Directory # 1 V3","Design and Operation of the Bulk Power System","R5.2.",null,"A Comprehensive Review of Resource Adequacy is required every three years and will cover a time period of five years. If changes in planned facilities or forecasted system conditions warrant, TFCP may require a Comprehensive Review of Resource Adequacy in less than 3 years.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[689,"Directory # 1 V3","Design and Operation of the Bulk Power System","R5.3",null,"In subsequent years, each Planning Coordinator shall conduct an Annual Interim Review of Resource Adequacy that will cover, at a minimum, the remaining years studied in the Comprehensive Review of Resource Adequacy.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[691,"Directory # 1 V3","Design and Operation of the Bulk Power System","R6.","YES","Each Reliability Coordinator shall coordinate outages and deratings of resources to verify adequate resources will be available to meet the forecasted demand and reserve requirements. Appendix F provides guidance for Operational Planning Coordination.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[690,"Directory # 1 V3","Design and Operation of the Bulk Power System","R6.","YES","Each Reliability Coordinator shall coordinate outages and deratings of resources to verify adequate resources will be available to meet the forecasted demand and reserve requirements. Appendix F provides guidance for Operational Planning Coordination.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[693,"Directory # 1 V3","Design and Operation of the Bulk Power System","R6.1.","YES","A Summer and Winter Reliability Assessment will be presented to the NPCC Task Force on Coordination of Operation (TFCO) every year.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[692,"Directory # 1 V3","Design and Operation of the Bulk Power System","R6.1.","YES","A Summer and Winter Reliability Assessment will be presented to the NPCC Task Force on Coordination of Operation (TFCO) every year.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[694,"Directory # 1 V3","Design and Operation of the Bulk Power System","R7.",null,"Each Transmission Planner and Planning Coordinator shall plan its bulk power system to have sufficient transmission capability to meet the respective requirements as specified in Table 1 while serving forecasted demand.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[695,"Directory # 1 V3","Design and Operation of the Bulk Power System","R7.1.",null,"Credible combinations of system conditions which stress the system shall be modelled including, load forecast, inter-Area and intra-Area transfers, transmission configuration, active and reactive resources, generation availability and other dispatch scenarios. All reclosing facilities shall be assumed in service unless it is known that such facilities will be rendered inoperative.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[696,"Directory # 1 V3","Design and Operation of the Bulk Power System","R8.",null,"Each Transmission Planner and Planning Coordinator shall assess the impact of the extreme contingencies listed in Table 2. Appendix C provides guidance for testing and analyzing extreme contingencies.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[697,"Directory # 1 V3","Design and Operation of the Bulk Power System","R9.",null,"Each Transmission Planner and Planning Coordinator shall assess the impact of extreme system conditions, one condition at a time, subject to contingencies as listed in the “Extreme System Conditions” category of Table 2.","2020-09-17",null,"Effective","Yes","TO, GO, TP, RP, PC, BA, TOP, RC"]
[197,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R1.","YES","Developing the List of Generators or Generation Facilities to be Verified \nTransmission Operators shall develop and maintain documentation of those generators or generation facilities that must verify the Gross Reactive Power Capability and Net Reactive Power Capability for the summer and winter capability seasons. The documentation maintained by the Transmission Operator shall include the following:","2017-01-21","2019-07-01","Retired","No","TOP"]
[158,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R1.","YES","Developing the List of Generators or Generation Facilities to be Verified \nTransmission Operators shall develop and maintain documentation of those generators or generation facilities that must verify the Gross Reactive Power Capability and Net Reactive Power Capability for the summer and winter capability seasons. The documentation maintained by the Transmission Operator shall include the following:","2017-01-21","2019-07-01","Retired","No","TOP"]
[198,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R1.1.","YES","All generators or generation facilities Declared Gross Reactive Power Capability and Declared Net Reactive Power Capability and seasonal auxiliary load reactive power requirements. (Reference Appendix B).","2017-01-21","2019-07-01","Retired","No","TOP"]
[159,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R1.1.","YES","All generators or generation facilities Declared Gross Reactive Power Capability and Declared Net Reactive Power Capability and seasonal auxiliary load reactive power requirements. (Reference Appendix B).","2017-01-21","2019-07-01","Retired","No","TOP"]
[160,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R1.2.","YES","All generators or generation facilities Verified Gross Reactive Power Capability and Verified Net Reactive Power Capability, verification date and method of verification.","2017-01-21","2019-07-01","Retired","No","TOP"]
[199,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R1.2.","YES","All generators or generation facilities Verified Gross Reactive Power Capability and Verified Net Reactive Power Capability, verification date and method of verification.","2017-01-21","2019-07-01","Retired","No","TOP"]
[200,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R1.3.","YES","Discrepancies between a Generator Owner’s declared and verified Gross Reactive Power Capability and Net Reactive Power Capability, the reason for such discrepancies and the Generator Owner’s plan to address the discrepancies.","2017-01-21","2019-07-01","Retired","No","TOP"]
[161,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R1.3.","YES","Discrepancies between a Generator Owner’s declared and verified Gross Reactive Power Capability and Net Reactive Power Capability, the reason for such discrepancies and the Generator Owner’s plan to address the discrepancies.","2017-01-21","2019-07-01","Retired","No","TOP"]
[201,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R1.4.","YES","Generator Owner supplied Gross Reactive Power Capability and Net Reactive Power Capability testing, manufacturer data, performance tracking or operating historical data, certification documentation, as specified by the Transmission Operator.","2017-01-21","2019-07-01","Retired","No","TOP"]
[162,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R1.4.","YES","Generator Owner supplied Gross Reactive Power Capability and Net Reactive Power Capability testing, manufacturer data, performance tracking or operating historical data, certification documentation, as specified by the Transmission Operator.","2017-01-21","2019-07-01","Retired","No","TOP"]
[163,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R1.5.","YES","Generators or generation facilities exempted from the verification requirements and the basis for their exemption (see Section 1.5).","2017-01-21","2019-07-01","Retired","No","TOP"]
[202,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R1.5.","YES","Generators or generation facilities exempted from the verification requirements and the basis for their exemption (see Section 1.5).","2017-01-21","2019-07-01","Retired","No","TOP"]
[172,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R10.",null,"If a Transmission Operator determines that the difference between the Declared Gross Reactive Power Capability and the Declared Net Reactive Power Capability of a generator or generation facility is insignificant for NPCC Bulk Power System reliability analysis, then periodic verification will be required for only one numerical value.","2017-01-21","2019-07-01","Retired","No","TOP"]
[173,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R11.",null,"If a Transmission Operator determines that only the lagging or leading Gross Reactive Power Capability and Net Reactive Power Capability of a generator or generation facility is required for NPCC Bulk Power System reliability analysis, then periodic verification will be required only for that specific reactive power capability value.","2017-01-21","2019-07-01","Retired","No","TOP"]
[174,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R12.",null,"The Generator Owner shall provide generator or generation facility Declared Gross Reactive Power Capability and Declared Net Reactive Power Capability to the Transmission Operator.","2017-01-21","2019-07-01","Retired","No","GO"]
[175,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R13.",null,"The Generator Owner shall provide evidence, upon request, to the Transmission Operator that the generator or generation facility Gross Reactive Power Capability and Net Reactive Power Capability have been verified.","2017-01-21","2019-07-01","Retired","No","GO"]
[176,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R14.",null,"The Generator Owner shall report to the Transmission Operator any discrepancies between Declared and Verified Gross Reactive Power Capability and Net Reactive Power Capability within a time frame specified by the Transmission Operator and develop and implement a plan to resolve the discrepancies.","2017-01-21","2019-07-01","Retired","Yes","TOP, GO"]
[177,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R15.",null,"The Generator Owner shall determine and report to the Transmission Operator the generator or generation facility reactive power seasonal auxiliary loads (including common station loads). 1.4 Verification Criteria for Generator and Generation Facility Reactive Power Capability","2017-01-21","2019-07-01","Retired","No","GO"]
[178,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R16.",null,"The Generator Owner shall comply with Transmission Operator requests for periodic verification of Gross Reactive Power Capability and Net Reactive Power Capability of their generators or generation facilities.","2017-01-21","2019-07-01","Retired","No","GO"]
[179,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R17.",null,"The Generator Owner shall verify the Gross Reactive Power Capability and Net Reactive Power Capability of their generators or generation facilities according to their types. As specified by the Transmission Operator, the verification shall include any of the following:\n · Testing, \n· Use of operating historical data, \n· Commissioning data (for new generators only),\n · Performance tracking data acquired during the same seasonal capability period.","2017-01-21","2019-07-01","Retired","No","GO"]
[180,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R18.",null,"The Generator Owner shall verify the Gross Reactive Power Capability and Net Reactive Power Capability of Thermal Generators, Internal Combustion Generators, Gas Turbine Generators, Combined Cycle and Hydro Generators or generators operated as a synchronous condenser on the average leading reactive power output for at least a 15 consecutive minute period and average lagging reactive power output for at least a 60 consecutive minute period.","2017-01-21","2019-07-01","Retired","No","GO"]
[181,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R19.",null,"The Generator Owner shall verify the Gross Reactive Power Capability and Net Reactive Power Capability of Intermittent power resources (wind, tidal or geo-thermal generators) on performance tracking data. Manufacturers’ data or commissioning data can be used until sufficient performance tracking data is available to verify generator or generation facilities lagging and leading reactive capabilities.","2017-01-21","2019-07-01","Retired","No","GO"]
[164,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R2.",null,"1.2 Establishing the Generator Reactive Power Capability Verification Program\nThe Transmission Operator shall establish and document a program to periodically verify the Gross Reactive Power Capability and Net Reactive Power Capability of all generators and generation facilities that are subject to periodic seasonal Gross Reactive Power Capability and Net Reactive Power Capability verification.","2017-01-21","2019-07-01","Retired","No","TOP"]
[182,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R20.",null,"The Generator Owner shall verify the Gross Reactive Power Capability and Net Reactive Power Capability for multiple generator facilities when limited by common elements on the reactive power capability of the facility and not the sum of the capabilities of the individual generators.","2017-01-21","2019-07-01","Retired","No","GO"]
[183,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R21.",null,"The Generator Owner shall identify any equipment or other factor that will limit the capability of the generator or generation facility to meet its Declared Gross Reactive Power Capability or Declared Net Reactive Power Capability. 1.5 Exemption of Generators or Generation Facilities from Seasonal Verification Testing","2017-01-21","2019-07-01","Retired","No","GO"]
[184,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R22.",null,"The Generator Owner shall notify the Transmission Operator and request an exemption if it cannot conduct seasonal capability testing of a generator or generation facility for any of the reasons listed below. \n· Adverse impact on transmission system reliability\n · Potential damage to transmission system or generator equipment\n · Environment conditions\n · Governmental regulatory or operating license limitations \n· An extended outage to the generator or generation facility","2017-01-21","2019-07-01","Retired","No","GO"]
[185,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R23.",null,"The Transmission Operator shall, within 30 calendar days of receiving notification from a Generator Owner that it is requesting an exemption because it cannot perform verification for the required seasonal period, notify the Generator Owner whether its generator will be exempted from the seasonal capability testing. Where the exemption is approved, the Transmission Operator shall coordinate with the Generator Owner to reschedule the verification for the next seasonal verification period.","2017-01-21","2019-07-01","Retired","No","TOP"]
[186,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R24.",null,"The Generator Owner for a generator or generation facility exempted from seasonal capability testing shall submit the following to the Transmission Operator:\n · For existing generators, generator operation records, manufacturer data, or performance tracking for the previous applicable seasonal verification period for this generator or generation facility. \n· Engineering analysis in conjunction with performance tracking data to justify any difference between a generator's or generation facility’s declared capability and previous applicable seasonal performance tracking data. \n· For new generators only, commissioning data.","2017-01-21","2019-07-01","Retired","No","GO"]
[203,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R3.","YES","The Transmission Operator shall provide any changes to its verification process to the Generator Owners within 30 calendar days of issue.","2017-01-21","2019-07-01","Retired","No","TOP"]
[165,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R3.","YES","The Transmission Operator shall provide any changes to its verification process to the Generator Owners within 30 calendar days of issue.","2017-01-21","2019-07-01","Retired","No","TOP"]
[166,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R4.","YES","The Transmission Operator shall establish and document requirements for a Generator Owner to notify the Transmission Operator within a specified time period when its generator or generation facility cannot achieve the Declared Gross Reactive Power Capability or Declared Net Reactive Power Capability because of equipment issues.","2017-01-21","2019-07-01","Retired","No","TOP"]
[204,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R4.","YES","The Transmission Operator shall establish and document requirements for a Generator Owner to notify the Transmission Operator within a specified time period when its generator or generation facility cannot achieve the Declared Gross Reactive Power Capability or Declared Net Reactive Power Capability because of equipment issues.","2017-01-21","2019-07-01","Retired","No","TOP"]
[167,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R5.","YES","The Transmission Operator shall establish and document a time frame for the Generator Owner to address equipment issues that result in a generator or generation facility not achieving the Declared Gross Reactive Power Capability and Declared Net Reactive Power Capability.","2017-01-21","2019-07-01","Retired","No","TOP"]
[205,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R5.","YES","The Transmission Operator shall establish and document a time frame for the Generator Owner to address equipment issues that result in a generator or generation facility not achieving the Declared Gross Reactive Power Capability and Declared Net Reactive Power Capability.","2017-01-21","2019-07-01","Retired","No","TOP"]
[206,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R6.","YES","The Transmission Operator shall establish and document the real power level at which the verification shall be performed, recognizing that the verification of lagging and leading reactive power capabilities should normally be performed during on-peak and off-peak hours, respectively.","2017-01-21","2019-07-01","Retired","No","TOP"]
[168,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R6.","YES","The Transmission Operator shall establish and document the real power level at which the verification shall be performed, recognizing that the verification of lagging and leading reactive power capabilities should normally be performed during on-peak and off-peak hours, respectively.","2017-01-21","2019-07-01","Retired","No","TOP"]
[169,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R7.","YES","The Transmission Operator shall establish and document those intermittent or small generating units whose capability may be represented by verification results of a single generating unit.","2017-01-21","2019-07-01","Retired","No","TOP"]
[170,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R8.",null,"1.3 Implementing the Generator Reactive Power Capability Verification Program\nThe Transmission Operator shall request Generator Owners to verify the seasonal Gross Reactive Power Capability and Net Reactive Power Capability of their generators or generation facilities that are subject to periodic seasonal Gross Reactive Power Capability and Net Reactive Power Capability verification every five (5) years or more frequently as required by the Transmission Operator. The two (2) capability seasons are defined as summer and winter as specified by the Transmission Operator.","2017-01-21","2019-07-01","Retired","No","TOP"]
[171,"Directory # 10","Verification of Generator Gross and Net Reactive Power Capability","R9.",null,"If a Transmission Operator determines that only one seasonal generating capability value is required for NPCC Bulk Power System reliability analysis, then periodic verification will be required only for that particular season.","2017-01-21","2019-07-01","Retired","No","TOP"]
[56,"Directory # 11","Disturbance Monitoring Equipment Criteria","R1.",null,"Each Transmission Owner and Generator Owner shall provide SER capability. This capability shall:","2016-10-24","2020-11-08","Retired","No","TO, GO"]
[57,"Directory # 11","Disturbance Monitoring Equipment Criteria","R1.1.",null,"Be provided at all BPS facilities.","2016-10-24","2020-11-08","Retired","No","TO, GO"]
[58,"Directory # 11","Disturbance Monitoring Equipment Criteria","R1.2.",null,"Be provided at generating facilities where the generator step up transformer is a BPS element.","2016-10-24","2020-11-08","Retired","No","TO, GO"]
[59,"Directory # 11","Disturbance Monitoring Equipment Criteria","R1.3.",null,"Monitor and record status change for the following:","2016-10-24","2020-11-08","Retired","No","TO, GO"]
[60,"Directory # 11","Disturbance Monitoring Equipment Criteria","R1.3.1.",null,"Transmission and generator circuit breaker positions","2016-10-24","2020-11-07","Retired","No","TO, GO"]
[61,"Directory # 11","Disturbance Monitoring Equipment Criteria","R1.3.2.",null,"Protective relay tripping for all protection groups that operate to trip circuit breakers","2016-10-24","2020-11-07","Retired","No","TO, GO"]
[62,"Directory # 11","Disturbance Monitoring Equipment Criteria","R1.3.3.",null,"Teleprotection keying and receive","2016-10-24","2020-11-07","Retired","No","TO, GO"]
[63,"Directory # 11","Disturbance Monitoring Equipment Criteria","R2.",null,"Each Transmission Owner shall have fault recording capability that determines the current zero time for loss of BPS elements.","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[64,"Directory # 11","Disturbance Monitoring Equipment Criteria","R3.",null,"Each Transmission Owner shall be able to determine fault recording data for the following elements at facilities, where FR is required as per R2 above:","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[65,"Directory # 11","Disturbance Monitoring Equipment Criteria","R3.1.",null,"All transmission lines.","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[66,"Directory # 11","Disturbance Monitoring Equipment Criteria","R3.2.",null,"Transformers with the primary terminal and at least one secondary terminal operated at 100 kV or higher and phase shifters (phase angle regulators).","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[67,"Directory # 11","Disturbance Monitoring Equipment Criteria","R3.3.",null,"Shunt capacitors, shunt reactors.","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[68,"Directory # 11","Disturbance Monitoring Equipment Criteria","R3.4.",null,"Generator interconnection where the generator step up transformer is a BPS element. This includes monitoring the high voltage or low voltage terminal of the generator step up transformer.","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[69,"Directory # 11","Disturbance Monitoring Equipment Criteria","R3.5.",null,"Dynamic VAR Devices.","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[70,"Directory # 11","Disturbance Monitoring Equipment Criteria","R3.6.",null,"HVDC terminals.","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[71,"Directory # 11","Disturbance Monitoring Equipment Criteria","R4.",null,"Each Transmission Owner shall record for faults, sufficient electrical quantities for each element in R3 to determine the following:","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[72,"Directory # 11","Disturbance Monitoring Equipment Criteria","R4.1.",null,"Three phase-to-neutral voltages. (Common bus-side voltages may be used for lines.)","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[73,"Directory # 11","Disturbance Monitoring Equipment Criteria","R4.2.",null,"Three phase currents and neutral currents.","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[74,"Directory # 11","Disturbance Monitoring Equipment Criteria","R4.3.",null,"Polarizing currents and voltages, if used.","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[75,"Directory # 11","Disturbance Monitoring Equipment Criteria","R4.4.",null,"Frequency.","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[76,"Directory # 11","Disturbance Monitoring Equipment Criteria","R5.",null,"Each Transmission Owner shall provide fault recording with the following capabilities:","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[77,"Directory # 11","Disturbance Monitoring Equipment Criteria","R5.1.",null,"Each FR record duration shall be a minimum of one (1) second with at least 2 cycles of pre-trigger data.","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[78,"Directory # 11","Disturbance Monitoring Equipment Criteria","R5.2.",null,"Each FR shall have a minimum recording rate of 16 samples per cycle.","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[79,"Directory # 11","Disturbance Monitoring Equipment Criteria","R5.3.",null,"Each FR shall be set to trigger for at least the following:","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[80,"Directory # 11","Disturbance Monitoring Equipment Criteria","R5.3.1.",null,"Monitored phase overcurrents set at 1.5 pu or less of rated CT secondary current or protective relay tripping for all protection groups.","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[55,"Directory # 11","Disturbance Monitoring Equipment Criteria","R5.3.2.",null,"Neutral (residual) overcurrent set at 0.2 pu or less of rated CT secondary current.","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[81,"Directory # 11","Disturbance Monitoring Equipment Criteria","R5.3.3.",null,"Monitored phase undervoltage set at 0.85 pu or greater.","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[82,"Directory # 11","Disturbance Monitoring Equipment Criteria","R5.4.",null,"Document additional triggers and deviations from the settings in 5.3.2 and 5.3.3 when local conditions dictate.","2016-10-24","2020-11-07","Retired","No","GO, TO"]
[83,"Directory # 11","Disturbance Monitoring Equipment Criteria","R6.",null,"Each Transmission Owner and Generator Owner shall time synchronize all SER and FR data for BPS elements to meet the following:","2016-10-24","2020-11-07","Retired","No","TO, GO"]
[84,"Directory # 11","Disturbance Monitoring Equipment Criteria","R6.1.",null,"Synchronization to Coordinated Universal Time (UTC) with or without a local time offset.","2016-10-24","2020-11-07","Retired","No","TO, GO"]
[85,"Directory # 11","Disturbance Monitoring Equipment Criteria","R6.2.",null,"Synchronized device clock accuracy within ± 2 milliseconds of UTC.","2016-10-24","2020-11-07","Retired","No","TO, GO"]
[86,"Directory # 11","Disturbance Monitoring Equipment Criteria","R6.3.",null,"Monthly verification of time synchronization shall be provided or the loss of time synchronization shall be monitored and alarmed to a control center staffed 24 hours a day, 7 days a week (24/7).","2016-10-24","2020-11-07","Retired","No","TO, GO"]
[87,"Directory # 11","Disturbance Monitoring Equipment Criteria","R7.",null,"FR settings in the software shall be verified every six (6) years.","2016-10-24","2020-11-07","Retired","No","TO, GO"]
[88,"Directory # 11","Disturbance Monitoring Equipment Criteria","R8.",null,"Each Transmission Owner and Generator Owner shall, within 90-calendar days of the discovery of a failure of the recording capability including time synchronization for the SER or FR data, either:\r\n• Restore the recording capability, or\r\n• Develop and implement a documented corrective action plan.","2016-10-24","2020-11-07","Retired","No","TO, GO"]
[89,"Directory # 11","Disturbance Monitoring Equipment Criteria","R9.",null,"Each Transmission Owner and Generator Owner shall provide, upon request, all SER and FR data for BPS elements to the Responsible Entity, Regional Entity, or NERC in accordance with the following:","2016-10-24","2020-11-07","Retired","No","TO, GO"]
[90,"Directory # 11","Disturbance Monitoring Equipment Criteria","R9.1.",null,"FR data shall contain all monitored channels. SER records shall contain station name, date, time resolved to milliseconds, SER point name, status.","2016-10-24","2020-11-07","Retired","No","TO, GO"]
[91,"Directory # 11","Disturbance Monitoring Equipment Criteria","R9.2.",null,"Data will be retrievable for the period of 10-calendar days, inclusive of the day the data was recorded.","2016-10-24","2020-11-07","Retired","No","TO, GO"]
[92,"Directory # 11","Disturbance Monitoring Equipment Criteria","R9.3.",null,"Data will be provided within 30-calendar days of a request unless an extension is granted by the requestor.","2016-10-24","2020-11-07","Retired","No","TO, GO"]
[93,"Directory # 11","Disturbance Monitoring Equipment Criteria","R9.4.",null,"SER data will be provided in ASCII Comma Separated Value (CSV) format following Attachment 2 of NERC PRC-002-2.","2016-10-24","2020-11-07","Retired","No","TO, GO"]
[94,"Directory # 11","Disturbance Monitoring Equipment Criteria","R9.5.",null,"FR data will be provided in electronic files that are formatted in conformance with C37.111, (IEEE Standard for Common Format for Transient Data Exchange (COMTRADE), revision C37.111-1999 or later.","2016-10-24","2020-11-07","Retired","No","TO, GO"]
[95,"Directory # 11","Disturbance Monitoring Equipment Criteria","R9.6.",null,"Data files will be named in conformance with C37.232, IEEE Standard for Common Format for Naming Time Sequence Data Files (COMNAME), revision C37.232-2011 or later.","2016-10-24","2020-11-07","Retired","No","TO, GO"]
[633,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R1.",null,"Each Transmission Owner and Generator Owner shall provide SER capability. This capability shall:","2020-11-08",null,"Effective","No","TO, GO"]
[634,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R1.1.",null,"Be provided at all BPS facilities.","2020-11-08",null,"Effective","No","TO, GO"]
[635,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R1.2.",null,"Be provided at generating facilities where the generator step up transformer is a BPS element.","2020-11-08",null,"Effective","No","TO, GO"]
[636,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R1.3.",null,"Monitor and record status change for the following:","2020-11-08",null,"Effective","No","TO, GO"]
[637,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R1.3.1.",null,"Transmission and generator circuit breaker positions","2020-11-08",null,"Effective","No","TO, GO"]
[638,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R1.3.2.",null,"Protective relay tripping for all protection groups that operate to trip circuit breakers","2020-11-08",null,"Effective","No","TO, GO"]
[639,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R1.3.3.",null,"Teleprotection keying and receive","2020-11-08",null,"Effective","No","TO, GO"]
[640,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R2.",null,"Each Transmission Owner shall have fault recording capability that determines the current zero time for loss of BPS elements.","2020-11-08",null,"Effective","No","TO, GO"]
[641,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R3.",null,"Each Transmission Owner shall be able to determine fault recording data for the following elements at facilities, where FR is required as per R2 above:","2020-11-08",null,"Effective","No","TO, GO"]
[642,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R3.1.",null,"All transmission lines.","2020-11-08",null,"Effective","No","TO, GO"]
[643,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R3.2.",null,"Transformers with the primary terminal and at least one secondary terminal operated at 100 kV or higher and phase shifters (phase angle regulators).","2020-11-08",null,"Effective","No","TO, GO"]
[644,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R3.3.",null,"Shunt capacitors, shunt reactors.","2020-11-08",null,"Effective","No","TO, GO"]
[645,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R3.4.",null,"Generator interconnection where the generator step up transformer is a BPS element. This includes monitoring the high voltage or low voltage terminal of the generator step up transformer.","2020-11-08",null,"Effective","No","TO, GO"]
[646,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R3.5.",null,"Dynamic VAR Devices.","2020-11-08",null,"Effective","No","TO, GO"]
[647,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R3.6.",null,"HVDC terminals.","2020-11-08",null,"Effective","No","TO, GO"]
[648,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R4.",null,"Each Transmission Owner shall record for faults, sufficient electrical quantities for each element in R3 to determine the following:","2020-11-08",null,"Effective","No","TO, GO"]
[649,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R4.1.",null,"Three phase-to-neutral voltages. (Common bus-side voltages may be used for lines.)","2020-11-08",null,"Effective","No","TO, GO"]
[650,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R4.2.",null,"Three phase currents and neutral currents.","2020-11-08",null,"Effective","No","TO, GO"]
[651,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R4.3.",null,"Polarizing currents and voltages, if used.","2020-11-08",null,"Effective","No","TO, GO"]
[652,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R4.4.",null,"Frequency.","2020-11-08",null,"Effective","No","TO, GO"]
[653,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R5.",null,"Each Transmission Owner shall provide fault recording with the following capabilities:","2020-11-08",null,"Effective","No","TO, GO"]
[654,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R5.1.",null,"Each FR record duration shall be a minimum of one (1) second with at least 2 cycles of pre-trigger data.","2020-11-08",null,"Effective","No","TO, GO"]
[655,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R5.2.",null,"Each FR shall have a minimum recording rate of 16 samples per cycle.","2020-11-08",null,"Effective","No","TO, GO"]
[656,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R5.3.",null,"Each FR shall be set to trigger for at least the following:","2020-11-08",null,"Effective","No","TO, GO"]
[657,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R5.3.1.",null,"Monitored phase overcurrents set at 1.5 pu or less of rated CT secondary current or protective relay tripping for all protection groups.","2020-11-08",null,"Effective","No","TO, GO"]
[658,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R5.3.2.",null,"Neutral (residual) overcurrent set at 0.2 pu or less of rated CT secondary current.","2020-11-08",null,"Effective","No","TO, GO"]
[659,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R5.3.3.",null,"Monitored phase undervoltage set at 0.85 pu or greater.","2020-11-08",null,"Effective","No","TO, GO"]
[660,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R5.4.",null,"Document additional triggers and deviations from the settings in 5.3.2 and 5.3.3 when local conditions dictate.","2020-11-08",null,"Effective","No","TO, GO"]
[661,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R6.",null,"Each Transmission Owner and Generator Owner shall time synchronize all SER and FR data for BPS elements to meet the following:","2020-11-08",null,"Effective","No","TO, GO"]
[662,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R6.1.",null,"Synchronization to Coordinated Universal Time (UTC) with or without a local time offset.","2020-11-08",null,"Effective","No","TO, GO"]
[663,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R6.2.",null,"Synchronized device clock accuracy within ± 2 milliseconds of UTC.","2020-11-08",null,"Effective","No","TO, GO"]
[664,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R6.3.",null,"Monthly verification of time synchronization shall be provided or the loss of time synchronization shall be monitored and alarmed to a control center staffed 24 hours a day, 7 days a week (24/7).","2020-11-08",null,"Effective","No","TO, GO"]
[665,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R7.",null,"FR settings in the software shall be verified every six (6) years.","2020-11-08",null,"Effective","No","TO, GO"]
[666,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R8.",null,"Each Transmission Owner and Generator Owner shall, within 90-calendar days of the discovery of a failure of the recording capability including time synchronization for the SER or FR data, either:\r\n• Restore the recording capability, or\r\n• Develop and implement a documented corrective action plan.","2020-11-08",null,"Effective","No","TO, GO"]
[667,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R9.",null,"Each Transmission Owner and Generator Owner shall provide, upon request, all SER and FR data for BPS elements to the Responsible Entity, Regional Entity, or NERC in accordance with the following:","2020-11-08",null,"Effective","No","TO, GO"]
[668,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R9.1.",null,"FR data shall contain all monitored channels. SER records shall contain station name, date, time resolved to milliseconds, SER point name, status.","2020-11-08",null,"Effective","No","TO, GO"]
[669,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R9.2.",null,"Data will be retrievable for the period of 10-calendar days, inclusive of the day the data was recorded.","2020-11-08",null,"Effective","No","TO, GO"]
[670,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R9.3.",null,"Data will be provided within 30-calendar days of a request unless an extension is granted by the requestor.","2020-11-08",null,"Effective","No","TO, GO"]
[671,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R9.4.",null,"SER data will be provided in ASCII Comma Separated Value (CSV) format following Attachment 2 of NERC PRC-002-2.","2020-11-08",null,"Effective","No","TO, GO"]
[672,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R9.5.",null,"FR data will be provided in electronic files that are formatted in conformance with C37.111, (IEEE Standard for Common Format for Transient Data Exchange (COMTRADE), revision C37.111-1999 or later.","2020-11-08",null,"Effective","No","TO, GO"]
[673,"Directory # 11 V1","Disturbance Monitoring Equipment Criteria","R9.6.",null,"Data files will be named in conformance with C37.232, IEEE Standard for Common Format for Naming Time Sequence Data Files (COMNAME), revision C37.232-2011 or later.","2020-11-08",null,"Effective","No","TO, GO"]
[269,"Directory # 2","Emergency Operations","R1.",null,"The Transmission Operator, Balancing Authority and Reliability Coordinator shall observe normal transfer capabilities unless there is insufficient capacity or voltage support in a Balancing Authority or Transmission Operator area, in which case emergency transfer capabilities may be used prior to shedding firm load. Emergency transfer capabilities shall not be exceeded.","2014-04-03","2017-01-20","Retired","No","TOP, RC, BA"]
[97,"Directory # 2","Emergency Operations","R1.1.",null,"The Transmission Operator, Balancing Authority and Reliability Coordinator shall have documented procedures to indicate the circumstances under which normal and emergency transfer capabilities limits are applied.","2014-04-03","2017-01-20","Retired","No","TOP, RC, BA"]
[98,"Directory # 2","Emergency Operations","R2.",null,"Each Balancing Authority and Transmission Operator shall have the capability to manually shed at least fifty percent of its area load in ten minutes or less. Manual load shedding plans shall not interrupt bulk power system elements.","2014-04-03","2017-01-20","Retired","No","TOP, RC, BA"]
[99,"Directory # 2","Emergency Operations","R2.1.",null,"The Balancing Authority and Transmission Operator shall review\nmanual load shedding procedures at least annually to ensure that the\nproper amount of load can be shed within the time limits prescribed.","2014-04-03","2017-01-20","Retired","No","TOP, RC, BA"]
[369,"Directory # 2 V3","Emergency Operations","R1.",null,"The Transmission Operator, Balancing Authority and Reliability Coordinator shall observe normal transfer capabilities unless there is insufficient capacity or voltage support in a Balancing Authority or Transmission Operator area, in which case emergency transfer capabilities may be used prior to shedding firm load. Emergency transfer capabilities shall not be exceeded.","2017-01-21","2018-07-02","Retired","No","TOP, BA, RC"]
[370,"Directory # 2 V3","Emergency Operations","R1.1.",null,"The Transmission Operator, Balancing Authority and Reliability Coordinator shall have documented procedures to indicate the circumstances under which normal and emergency transfer capabilities limits are applied.","2017-01-21","2018-07-02","Retired","No","TOP, BA, RC"]
[371,"Directory # 2 V3","Emergency Operations","R2.",null,"Each Balancing Authority and Transmission Operator shall have the capability to manually shed at least fifty percent of its area load in ten minutes or less. Manual load shedding plans shall not interrupt bulk power system elements.","2017-01-21","2018-07-02","Retired","No","TOP, BA, RC"]
[372,"Directory # 2 V3","Emergency Operations","R2.1.",null,"The Balancing Authority and Transmission Operator shall review manual load shedding procedures at least annually to ensure that the proper amount of load can be shed within the time limits prescribed.","2017-01-21","2018-07-02","Retired","No","TOP, BA, RC"]
[314,"Directory # 2 V4","Emergency Operations","R1.",null,"The Transmission Operator, Balancing Authority and Reliability Coordinator shall observe normal transfer capabilities unless there is insufficient capacity or voltage support in a Balancing Authority or Transmission Operator area, in which case emergency transfer capabilities may be used prior to shedding firm load. Emergency transfer capabilities shall not be exceeded.","2018-07-03",null,"Effective","No","TOP, BA, RC"]
[311,"Directory # 2 V4","Emergency Operations","R1.1.",null,"The Transmission Operator, Balancing Authority and Reliability Coordinator shall have documented procedures to indicate the circumstances under which normal and emergency transfer capabilities limits are applied.","2018-07-03",null,"Effective","No","TOP, BA, RC"]
[312,"Directory # 2 V4","Emergency Operations","R2.",null,"Each Balancing Authority and Transmission Operator shall have the capability to manually shed at least fifty percent of its area load in ten minutes or less. Manual load shedding plans shall not interrupt bulk power system elements.","2018-07-03",null,"Effective","No","TOP, BA, RC"]
[313,"Directory # 2 V4","Emergency Operations","R2.1.",null,"The Balancing Authority and Transmission Operator shall review\nmanual load shedding procedures at least annually to ensure that the\nproper amount of load can be shed within the time limits prescribed.","2018-07-03",null,"Effective","No","TOP, BA, RC"]
[308,"Directory # 5","Reserve","R1.",null,"Each Balancing Authority shall have ten-minute reserve available to it that is at least equal to its first contingency loss. NPCC ten-minute reserve meets the requirements for the Contingency Reserve requirements within the NERC standards.\r\n• If a Balancing Authority becomes deficient in ten-minute reserve or forecasts a deficiency, it shall restore its ten-minute reserve as soon as possible and within the duration specified in the appropriate NERC standard.\r\n• If a Balancing Authority cannot restore its ten-minute reserve per requirement R2, it shall minimize the magnitude and duration of the ten-minute reserve deficiency.","2014-04-03","2017-01-20","Retired","Yes","RC, BA, GOP, DP"]
[285,"Directory # 5","Reserve","R10.",null,"Resources allocating inter-Balancing Area reserve shall not offer the same reserve to more than one acquiring Balancing Authority for the same scheduling interval.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[286,"Directory # 5","Reserve","R11.",null,"A Balancing Authority shall ensure that reserve is distributed so that it can be utilized without exceeding applicable element ratings or transfer limitations.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[287,"Directory # 5","Reserve","R12.",null,"A Balancing Authority providing reserve to another Balancing Authority through direct procurement, bilateral, multi-lateral operating agreements, or through reserve sharing agreements, shall deliver an increase in energy as requested, up to the amount of reserve agreed upon.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[288,"Directory # 5","Reserve","R13.",null,"A Balancing Authority shall not curtail an existing or planned non-recallable energy schedule in order to support the activation of reserve, unless agreed to by all affected Balancing Authorities.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[289,"Directory # 5","Reserve","R14.",null,"A Balancing Authority providing or receiving inter-Balancing Area reserve shall meet the following requirements:","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[290,"Directory # 5","Reserve","R14.1.",null,"Decision-making related to the specific resources to be activated to provide inter-Balancing Area reserve shall be restricted to the affected Balancing Authorities.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[291,"Directory # 5","Reserve","R14.2.",null,"The provision of inter-Balancing Area reserve shall be limited to adjacent Balancing Authorities only, unless specifically facilitated by an approved NPCC procedure or multilateral Balancing Authority/Reliability Coordinator procedure.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[292,"Directory # 5","Reserve","R14.3.",null,"Shall agree on Interchange Schedule modifications when activating and terminating inter-Balancing Area reserve.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[293,"Directory # 5","Reserve","R14.4.",null,"Where Dynamic Transfers are used to activate inter-Balancing Area reserve, it shall be agreed to by the affected Balancing Authorities, and approved by the TFCO.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[294,"Directory # 5","Reserve","R15.",null,"A Balancing Authority shall activate inter-Balancing Area reserve within 5 minutes if utilized for a NERC DCS Balancing Contingency Event or a NPCC reportable event.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[295,"Directory # 5","Reserve","R16.",null,"A Balancing Authority acquiring inter-Balancing Area reserve shall notify the host Balancing Authority and affected Reliability Coordinators when changes are made to the scheduling of inter-Balancing Area reserve.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[296,"Directory # 5","Reserve","R17.","YES","A Balancing Authority providing (allocating or activating) inter- Balancing Area reserve, not as part of a Reserve Sharing Group, shall not count that reserve to meet its own reserve requirement.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[297,"Directory # 5","Reserve","R18.","YES","A Balancing Authority providing recallable energy to another Balancing Authority shall advise the other Balancing Authority that the energy is recallable, and shall inform the receiving Balancing Authority of any change to the recallable status of this energy.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[298,"Directory # 5","Reserve","R19.","YES","A Balancing Authority shall meet its Operating Reserve requirement using capacity available from resources internal to its Balancing Authority or by using capacity that is deliverable from another Balancing Authority.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[271,"Directory # 5","Reserve","R2.",null,"Each Balancing Authority shall have thirty-minute reserve available to it that is at least equal to one-half its second contingency loss.\r\n• A Balancing Authority deficient in thirty-minute reserve for four hours, or forecasting a deficiency of any duration beyond a four-hour horizon, shall eliminate the deficiency if possible,","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[299,"Directory # 5","Reserve","R20.","YES","A Balancing Authority delivering recallable energy to another Balancing Authority may count that energy toward meeting their Operating Reserve requirement.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[300,"Directory # 5","Reserve","R21.","YES","A Balancing Authority receiving recallable energy from another Balancing Authority must carry additional Operating Reserve at least equal to the amount of recallable energy being received.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[301,"Directory # 5","Reserve","R22.",null,"Balancing Authorities participating in the “Simultaneous Activation of Ten-Minute Reserve”, (SAR) program shall conform to the procedures, as specified in Attachment B.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[302,"Directory # 5","Reserve","R23.",null,"Balancing Authorities participating in the “ACE Diversity Interchange”, (ADI) program shall conform to the procedures, as specified in Attachment C.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[272,"Directory # 5","Reserve","R3.",null,"A Balancing Authority’s requirement for synchronized reserve available within ten minutes shall be calculated by the twentieth day of each month, for the previous month, and shall be applied at the beginning of the next month.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[273,"Directory # 5","Reserve","R4.",null,"A Balancing Authority’s requirement for synchronized reserve available within ten minutes shall be adjusted as follows:","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[274,"Directory # 5","Reserve","R4.1",null,"A Balancing Authority’s maximum requirement for synchronized reserve available within ten minutes shall be 100 percent of its ten-minute reserve. A Balancing Authority’s minimum requirement for synchronized reserve available within ten minutes shall be 25 percent of its ten-minute reserve.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[275,"Directory # 5","Reserve","R4.2.",null,"A Balancing Authority’s calculated requirement for synchronized reserve available within ten minutes shall increase by 20 percent of the ten-minute reserve requirement for every time it fails to return its ACE to pre-contingency values or to zero within fifteen minutes following the start of a reportable event that is less than a NERC reportable Balancing Contingency Event. Recovery of reporting ACE occurs when a Balancing Authority returns its reporting ACE to pre-contingency values (if it’s pre-contingency reporting ACE was negative) or to zero (if it’s pre-contingency reporting ACE was positive or equal to zero).","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[276,"Directory # 5","Reserve","R4.3.",null,"A Balancing Authority’s calculated requirement for synchronized reserve available within ten minutes may only be reduced by a maximum of 20 percent of the ten-minute reserve requirement, per month following the implementation month of any synchronized reserve requirement increase per R4.2.\r\nR5. If a Balancing Authority becomes deficient in synchronized","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[277,"Directory # 5","Reserve","R5.",null,"If a Balancing Authority becomes deficient in synchronized reserve available within ten minutes, it shall restore its synchronized reserve available within ten minutes in accordance with R1 for the restoration of ten-minute reserve.\r\nRefer to Attachment A for example scenarios of synchronized reserve requirement penalty adjustments.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[278,"Directory # 5","Reserve","R6.",null,"A Balancing Authority’s synchronized reserve, ten-minute reserve, and thirty-minute reserve, if activated, shall be sustainable for at least one hour from the time of activation.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[279,"Directory # 5","Reserve","R7.",null,"A Balancing Authority shall not count synchronized reserve, ten-minute reserve, or thirty-minute reserve from loads that are already counted in other demand response programs and would result in double counting the same capacity.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[280,"Directory # 5","Reserve","R8.",null,"A Balancing Authority shall not count synchronized reserve from a load if the reduction in load is dependent on starting a generator to replace energy that is supplied from the grid.","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[281,"Directory # 5","Reserve","R9.",null,"The Balancing Authority shall specify the following criteria for resources to be eligible to provide synchronized reserve, ten-minute reserve, or thirty-minute reserve:","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[282,"Directory # 5","Reserve","R9.1.",null,"Requirements for metering and testing","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[283,"Directory # 5","Reserve","R9.2.",null,"Requirements for continuously meeting the dispatch instructions","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[284,"Directory # 5","Reserve","R9.3.",null,"Requirements for operating capabilities and response rates","2014-04-03","2017-01-20","Retired","Yes","DP, GOP, BA, RC"]
[373,"Directory # 5 V2","Reserve","R1.",null,"Each Balancing Authority shall have ten-minute reserve available to it that is at least equal to its first contingency loss. NPCC ten-minute reserve meets the requirements for the Contingency Reserve requirements within the NERC standards.\r\n• If a Balancing Authority becomes deficient in ten-minute reserve or forecasts a deficiency, it shall restore its ten-minute reserve as soon as possible and within the duration specified in the appropriate NERC standard.\r\n• If a Balancing Authority cannot restore its ten-minute reserve per requirement R2, it shall minimize the magnitude and duration of the ten-minute reserve deficiency.","2017-01-21","2019-01-15","Retired","No"]
[388,"Directory # 5 V2","Reserve","R10.",null,"Resources allocating inter-Balancing Area reserve shall not offer the same reserve to more than one acquiring Balancing Authority for the same scheduling interval.","2017-01-21","2019-01-15","Retired","No"]
[389,"Directory # 5 V2","Reserve","R11.",null,"A Balancing Authority shall ensure that reserve is distributed so that it can be utilized without exceeding applicable element ratings or transfer limitations.","2017-01-21","2019-01-15","Retired","No"]
[390,"Directory # 5 V2","Reserve","R12.",null,"A Balancing Authority providing reserve to another Balancing Authority through direct procurement, bilateral, multi-lateral operating agreements, or through reserve sharing agreements, shall deliver an increase in energy as requested, up to the amount of reserve agreed upon.","2017-01-21","2019-01-15","Retired","No"]
[391,"Directory # 5 V2","Reserve","R13.",null,"A Balancing Authority shall not curtail an existing or planned non-recallable energy schedule in order to support the activation of reserve, unless agreed to by all affected Balancing Authorities.","2017-01-21","2019-01-15","Retired","No"]
[392,"Directory # 5 V2","Reserve","R14.",null,"A Balancing Authority providing or receiving inter-Balancing Area reserve shall meet the following requirements:","2017-01-21","2019-01-15","Retired","No"]
[393,"Directory # 5 V2","Reserve","R14.1.",null,"Decision-making related to the specific resources to be activated to provide inter-Balancing Area reserve shall be restricted to the affected Balancing Authorities.","2017-01-21","2019-01-15","Retired","No"]
[394,"Directory # 5 V2","Reserve","R14.2.",null,"The provision of inter-Balancing Area reserve shall be limited to adjacent Balancing Authorities only, unless specifically facilitated by an approved NPCC procedure or multilateral Balancing Authority/Reliability Coordinator procedure.","2017-01-21","2019-01-15","Retired","No"]
[395,"Directory # 5 V2","Reserve","R14.3.",null,"Shall agree on Interchange Schedule modifications when activating and terminating inter-Balancing Area reserve.","2017-01-21","2019-01-15","Retired","No"]
[396,"Directory # 5 V2","Reserve","R14.4.",null,"Where Dynamic Transfers are used to activate inter-Balancing Area reserve, it shall be agreed to by the affected Balancing Authorities, and approved by the TFCO.","2017-01-21","2019-01-15","Retired","No"]
[397,"Directory # 5 V2","Reserve","R15.",null,"A Balancing Authority shall activate inter-Balancing Area reserve within 5 minutes if utilized for a NERC DCS Balancing Contingency Event or a NPCC reportable event.","2017-01-21","2019-01-15","Retired","No"]
[398,"Directory # 5 V2","Reserve","R16.",null,"A Balancing Authority acquiring inter-Balancing Area reserve shall notify the host Balancing Authority and affected Reliability Coordinators when changes are made to the scheduling of inter-Balancing Area reserve.","2017-01-21","2019-01-15","Retired","No"]
[399,"Directory # 5 V2","Reserve","R17.","YES","A Balancing Authority providing (allocating or activating) inter- Balancing Area reserve, not as part of a Reserve Sharing Group, shall not count that reserve to meet its own reserve requirement.","2017-01-21","2019-01-15","Retired","No"]
[400,"Directory # 5 V2","Reserve","R18.","YES","A Balancing Authority providing recallable energy to another Balancing Authority shall advise the other Balancing Authority that the energy is recallable, and shall inform the receiving Balancing Authority of any change to the recallable status of this energy.","2017-01-21","2019-01-15","Retired","No"]
[401,"Directory # 5 V2","Reserve","R19.","YES","A Balancing Authority shall meet its Operating Reserve requirement using capacity available from resources internal to its Balancing Authority or by using capacity that is deliverable from another Balancing Authority.","2017-01-21","2019-01-15","Retired","No"]
[374,"Directory # 5 V2","Reserve","R2.",null,"Each Balancing Authority shall have thirty-minute reserve available to it that is at least equal to one-half its second contingency loss. A Balancing Authority deficient in thirty-minute reserve for four hours, or forecasting a deficiency of any duration beyond a four-hour horizon, shall eliminate the deficiency if possible, or minimize the magnitude and duration of the deficiency.","2017-01-21","2019-01-15","Retired","No"]
[402,"Directory # 5 V2","Reserve","R20.","YES","A Balancing Authority delivering recallable energy to another Balancing Authority may count that energy toward meeting their Operating Reserve requirement.","2017-01-21","2019-01-15","Retired","No"]
[403,"Directory # 5 V2","Reserve","R21.","YES","A Balancing Authority receiving recallable energy from another Balancing Authority must carry additional Operating Reserve at least equal to the amount of recallable energy being received.","2017-01-21","2019-01-15","Retired","No"]
[404,"Directory # 5 V2","Reserve","R22.",null,"Balancing Authorities participating in the “Simultaneous Activation of Ten-Minute Reserve”, (SAR) program shall conform to the procedures, as specified in Attachment B.","2017-01-21","2019-01-15","Retired","No"]
[405,"Directory # 5 V2","Reserve","R23.",null,"Balancing Authorities participating in the “ACE Diversity Interchange”, (ADI) program shall conform to the procedures, as specified in Attachment C.","2017-01-21","2019-01-15","Retired","No"]
[375,"Directory # 5 V2","Reserve","R3.",null,"A Balancing Authority’s requirement for synchronized reserve available within ten minutes shall be calculated by the twentieth day of each month, for the previous month, and shall be applied at the beginning of the next month.","2017-01-21","2019-01-15","Retired","No"]
[376,"Directory # 5 V2","Reserve","R4.",null,"A Balancing Authority’s requirement for synchronized reserve available within ten minutes shall be adjusted as follows:","2017-01-21","2019-01-15","Retired","No"]
[377,"Directory # 5 V2","Reserve","R4.1.",null,"A Balancing Authority’s maximum requirement for synchronized reserve available within ten minutes shall be 100 percent of its ten-minute reserve. A Balancing Authority’s minimum requirement for synchronized reserve available within ten minutes shall be 25 percent of its ten-minute reserve.","2017-01-21","2019-01-15","Retired","No"]
[378,"Directory # 5 V2","Reserve","R4.2.",null,"A Balancing Authority’s calculated requirement for synchronized reserve available within ten minutes shall increase by 20 percent of the ten-minute reserve requirement for every time it fails to return its ACE to pre-contingency values or to zero within fifteen minutes following the start of a reportable event that is less than a NERC reportable Balancing Contingency Event. Recovery of reporting ACE occurs when a Balancing Authority returns its reporting ACE to pre-contingency values (if it’s pre-contingency reporting ACE was negative) or to zero (if it’s pre-contingency reporting ACE was positive or equal to zero).","2017-01-21","2019-01-15","Retired","No"]
[379,"Directory # 5 V2","Reserve","R4.3.",null,"A Balancing Authority’s calculated requirement for synchronized reserve available within ten minutes may only be reduced by a maximum of 20 percent of the ten-minute reserve requirement, per month following the implementation month of any synchronized reserve requirement increase per R4.2.","2017-01-21","2019-01-15","Retired","No"]
[380,"Directory # 5 V2","Reserve","R5.",null,"If a Balancing Authority becomes deficient in synchronized reserve available within ten minutes, it shall restore its synchronized reserve available within ten minutes in accordance with R1 for the restoration of ten-minute reserve.\r\nRefer to Attachment A for example scenarios of synchronized reserve requirement penalty adjustments.","2017-01-21","2019-01-15","Retired","No"]
[381,"Directory # 5 V2","Reserve","R6.",null,"A Balancing Authority’s synchronized reserve, ten-minute reserve, and thirty-minute reserve, if activated, shall be sustainable for at least one hour from the time of activation.","2017-01-21","2019-01-15","Retired","No"]
[382,"Directory # 5 V2","Reserve","R7.",null,"A Balancing Authority shall not count synchronized reserve, ten-minute reserve, or thirty-minute reserve from loads that are already counted in other demand response programs and would result in double counting the same capacity.","2017-01-21","2019-01-15","Retired","No"]
[383,"Directory # 5 V2","Reserve","R8.",null,"A Balancing Authority shall not count synchronized reserve from a load if the reduction in load is dependent on starting a generator to replace energy that is supplied from the grid.","2017-01-21","2019-01-15","Retired","No"]
[384,"Directory # 5 V2","Reserve","R9.",null,"The Balancing Authority shall specify the following criteria for resources to be eligible to provide synchronized reserve, ten-minute reserve, or thirty-minute reserve:","2017-01-21","2019-01-15","Retired","No"]
[385,"Directory # 5 V2","Reserve","R9.1.",null,"Requirements for metering and testing","2017-01-21","2019-01-15","Retired","No"]
[386,"Directory # 5 V2","Reserve","R9.2.",null,"Requirements for continuously meeting the dispatch instructions","2017-01-21","2019-01-15","Retired","No"]
[387,"Directory # 5 V2","Reserve","R9.3.",null,"Requirements for operating capabilities and response rates","2017-01-21","2019-01-15","Retired","No"]
[270,"Directory # 5 V3","Reserve","R1.",null,"Each Balancing Authority shall have ten-minute reserve available to it that is at least equal to its first contingency loss. NPCC ten-minute reserve meets the requirements for the Contingency Reserve requirements within the NERC standards.\r\n• If a Balancing Authority becomes deficient in ten-minute reserve or forecasts a deficiency, it shall restore its ten-minute reserve as soon as possible and within the duration specified in the appropriate NERC standard.\r\n• If a Balancing Authority cannot restore its ten-minute reserve per requirement R2, it shall minimize the magnitude and duration","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[420,"Directory # 5 V3","Reserve","R10.",null,"Resources allocating inter-Balancing Area reserve shall not offer the same reserve to more than one acquiring Balancing Authority for the same scheduling interval.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[421,"Directory # 5 V3","Reserve","R11.",null,"A Balancing Authority shall ensure that reserve is distributed so that it can be utilized without exceeding applicable element ratings or transfer limitations.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[422,"Directory # 5 V3","Reserve","R12.",null,"A Balancing Authority providing reserve to another Balancing Authority through direct procurement, bilateral, multi-lateral operating agreements, or through reserve sharing agreements, shall deliver an increase in energy as requested, up to the amount of reserve agreed upon.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[423,"Directory # 5 V3","Reserve","R13.",null,"A Balancing Authority shall not curtail an existing or planned non-recallable energy schedule in order to support the activation of reserve, unless agreed to by all affected Balancing Authorities.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[424,"Directory # 5 V3","Reserve","R14.",null,"A Balancing Authority providing or receiving inter-Balancing Area reserve shall meet the following requirements:","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[425,"Directory # 5 V3","Reserve","R14.1.",null,"Decision-making related to the specific resources to be activated to provide inter-Balancing Area reserve shall be restricted to the affected Balancing Authorities.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[426,"Directory # 5 V3","Reserve","R14.2.",null,"The provision of inter-Balancing Area reserve shall be limited to adjacent Balancing Authorities only, unless specifically facilitated by an approved NPCC procedure or multilateral Balancing Authority/Reliability Coordinator procedure.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[427,"Directory # 5 V3","Reserve","R14.3.",null,"Shall agree on Interchange Schedule modifications when activating and terminating inter-Balancing Area reserve.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[428,"Directory # 5 V3","Reserve","R14.4.",null,"Where Dynamic Transfers are used to activate inter-Balancing Area reserve, it shall be agreed to by the affected Balancing Authorities, and approved by the TFCO.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[429,"Directory # 5 V3","Reserve","R15.",null,"A Balancing Authority shall activate inter-Balancing Area reserve within 5 minutes if utilized for a NERC DCS Balancing Contingency Event or a NPCC reportable event.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[430,"Directory # 5 V3","Reserve","R16.",null,"A Balancing Authority acquiring inter-Balancing Area reserve shall notify the host Balancing Authority and affected Reliability Coordinators when changes are made to the scheduling of inter-Balancing Area reserve.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[431,"Directory # 5 V3","Reserve","R17.","YES","A Balancing Authority providing (allocating or activating) inter- Balancing Area reserve, not as part of a Reserve Sharing Group, shall not count that reserve to meet its own reserve requirement.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[432,"Directory # 5 V3","Reserve","R18.","YES","A Balancing Authority providing recallable energy to another Balancing Authority shall advise the other Balancing Authority that the energy is recallable, and shall inform the receiving Balancing Authority of any change to the recallable status of this energy.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[433,"Directory # 5 V3","Reserve","R19.","YES","A Balancing Authority shall meet its Operating Reserve requirement using capacity available from resources internal to its Balancing Authority or by using capacity that is deliverable from another Balancing Authority.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[406,"Directory # 5 V3","Reserve","R2.",null,"Each Balancing Authority shall have thirty-minute reserve available to it that is at least equal to one-half its second contingency loss. • A Balancing Authority deficient in thirty-minute reserve for four hours, or forecasting a deficiency of any duration beyond a four-hour horizon, shall eliminate the deficiency if possible, or minimize the magnitude and duration of the deficiency.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[434,"Directory # 5 V3","Reserve","R20.","YES","A Balancing Authority delivering recallable energy to another Balancing Authority may count that energy toward meeting their Operating Reserve requirement.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[435,"Directory # 5 V3","Reserve","R21.","YES","A Balancing Authority receiving recallable energy from another Balancing Authority must carry additional Operating Reserve at least equal to the amount of recallable energy being received.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[436,"Directory # 5 V3","Reserve","R22.",null,"Balancing Authorities participating in the “Simultaneous Activation of Ten-Minute Reserve”, (SAR) program shall conform to the procedures, as specified in Attachment B.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[437,"Directory # 5 V3","Reserve","R23.",null,"Balancing Authorities participating in the “ACE Diversity Interchange”, (ADI) program shall conform to the procedures, as specified in Attachment C.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[407,"Directory # 5 V3","Reserve","R3.",null,"A Balancing Authority’s requirement for synchronized reserve available within ten minutes shall be calculated by the twentieth day of each month, for the previous month, and shall be applied at the beginning of the next month.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[408,"Directory # 5 V3","Reserve","R4.",null,"A Balancing Authority’s requirement for synchronized reserve available within ten minutes shall be adjusted as follows:","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[409,"Directory # 5 V3","Reserve","R4.1.",null,"A Balancing Authority’s maximum requirement for synchronized reserve available within ten minutes shall be 100 percent of its ten-minute reserve. A Balancing Authority’s minimum requirement for synchronized reserve available within ten minutes shall be 25 percent of its ten-minute reserve.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[410,"Directory # 5 V3","Reserve","R4.2.",null,"A Balancing Authority’s calculated requirement for synchronized reserve available within ten minutes shall increase by 20 percent of the ten-minute reserve requirement for every time it fails to return its ACE to pre-contingency values or to zero within fifteen minutes following the start of a reportable event that is less than a NERC reportable Balancing Contingency Event. Recovery of reporting ACE occurs when a Balancing Authority returns its reporting ACE to pre-contingency values (if it’s pre-contingency reporting ACE was negative) or to zero (if it’s pre-contingency reporting ACE was positive or equal to zero).","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[411,"Directory # 5 V3","Reserve","R4.3.",null,"A Balancing Authority’s calculated requirement for synchronized reserve available within ten minutes may only be reduced by a maximum of 20 percent of the ten-minute reserve requirement, per month following the implementation month of any synchronized reserve requirement increase per R4.2.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[412,"Directory # 5 V3","Reserve","R5.",null,"If a Balancing Authority becomes deficient in synchronized reserve available within ten minutes, it shall restore its synchronized reserve available within ten minutes in accordance with R1 for the restoration of ten-minute reserve.\r\nRefer to Attachment A for example scenarios of synchronized reserve requirement penalty adjustments.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[413,"Directory # 5 V3","Reserve","R6.",null,"A Balancing Authority’s synchronized reserve, ten-minute reserve, and thirty-minute reserve, if activated, shall be sustainable for at least one hour from the time of activation.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[414,"Directory # 5 V3","Reserve","R7.",null,"A Balancing Authority shall not count synchronized reserve, ten-minute reserve, or thirty-minute reserve from loads that are already counted in other demand response programs and would result in double counting the same capacity.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[415,"Directory # 5 V3","Reserve","R8.",null,"A Balancing Authority shall not count synchronized reserve from a load if the reduction in load is dependent on starting a generator to replace energy that is supplied from the grid.","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[416,"Directory # 5 V3","Reserve","R9.",null,"The Balancing Authority shall specify the following criteria for resources to be eligible to provide synchronized reserve, ten-minute reserve, or thirty-minute reserve:","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[417,"Directory # 5 V3","Reserve","R9.1.",null,"Requirements for metering and testing","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[418,"Directory # 5 V3","Reserve","R9.2.",null,"Requirements for continuously meeting the dispatch instructions","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[419,"Directory # 5 V3","Reserve","R9.3.",null,"Requirements for operating capabilities and response rates","2019-01-16","2020-04-25","Retired","Yes","DP, GOP, BA, RC"]
[438,"Directory # 6","Reserve Sharing Groups","R1.",null,"The Balancing Authorities (BAs) participating in a Reserve Sharing Group (RSG) shall have a RSG Agreement that meets the requirements as specified in section 5.2.","2012-08-09","2017-01-20","Retired","No"]
[439,"Directory # 6","Reserve Sharing Groups","R2.",null,"Each RSG shall provide their RSG Agreement to the Task Force for Coordination of Operation for review before it is implemented.","2012-08-09","2017-01-20","Retired","No"]
[440,"Directory # 6","Reserve Sharing Groups","R2.1.",null,"New RSG Agreements and future changes to existing RSG Agreements shall be approved by the Reliability Coordinating Committee (RCC).","2012-08-09","2017-01-20","Retired","No"]
[441,"Directory # 6","Reserve Sharing Groups","R3.",null,"The Balancing Authorities (BAs) participating in a Reserve Sharing Group (RSG) shall be adjoining BAs unless they have a wheeling agreement with the intermediary BA or BAs.","2012-08-09","2017-01-20","Retired","No"]
[442,"Directory # 6","Reserve Sharing Groups","R4.",null,"Each RSG shall provide the Task Force on Coordination of Operation with a quantitative estimate of the change in reliability risk related to a RSG agreement for review before their RSG Agreement is implemented.\r\nThere are a number of studies that could be performed to analyze the change in reliability risk such as:\r\n• Megawatt Loss Probability Method\r\n• Statistical analysis on the NPCC reportable events reports (NERC Form CR-1 reports)/Chronological event database\r\n• Other comparable methods that produce the required reliability risk estimate.","2012-08-09","2017-01-20","Retired","No"]
[443,"Directory # 6","Reserve Sharing Groups","R5.",null,"Each RSG Agreement shall specify the following:","2012-08-09","2017-01-20","Retired","No"]
[444,"Directory # 6","Reserve Sharing Groups","R5.1.",null,"The BAs participating in the RSG.","2012-08-09","2017-01-20","Retired","No"]
[453,"Directory # 6","Reserve Sharing Groups","R5.10.",null,"Details of how the activation and termination of RSGE are coordinated with simultaneous activation of ten-minute reserve (SAR) energy, other existing reserve activation agreements and other RSGs.","2012-08-09","2017-01-20","Retired","No"]
[454,"Directory # 6","Reserve Sharing Groups","R5.11.",null,"The Ramp to be utilized for Schedule changes when RSGE is activated and/or terminated.","2012-08-09","2017-01-20","Retired","No"]
[455,"Directory # 6","Reserve Sharing Groups","R5.12.",null,"The maximum duration for which the RSGE can be activated.","2012-08-09","2017-01-20","Retired","No"]
[456,"Directory # 6","Reserve Sharing Groups","R5.13.",null,"Times within which the RSG Coordinator shall:\r\n• Communicate changes in availability and deliverability of RSGE that are reported to it\r\n• Develop allocation shares, if necessary\r\n• Specify Schedule changes to activate RSGE\r\n• Adjust Schedules to terminate the delivery of RSGE.","2012-08-09","2017-01-20","Retired","No"]
[457,"Directory # 6","Reserve Sharing Groups","R5.14.",null,"The communication method(s) to be used to exchange information with the RSG Coordinator.","2012-08-09","2017-01-20","Retired","No"]
[458,"Directory # 6","Reserve Sharing Groups","R5.15.",null,"The information that must be exchanged between the RSG Coordinator and participating BAs and between the RSG Coordinator and other RSG Coordinators and the SAR Coordinator.","2012-08-09","2017-01-20","Retired","No"]
[459,"Directory # 6","Reserve Sharing Groups","R5.16.",null,"Requirements for the payback of any delivered RSGE.","2012-08-09","2017-01-20","Retired","No"]
[460,"Directory # 6","Reserve Sharing Groups","R5.17.",null,"How transmission capability is utilized for planning and ensuring the availability and deliverability of RSGE.","2012-08-09","2017-01-20","Retired","No"]
[461,"Directory # 6","Reserve Sharing Groups","R5.18.",null,"The allocation between participating BAs, of any penalties resulting from the violation of NPCC or NERC criteria or standards.","2012-08-09","2017-01-20","Retired","No"]
[462,"Directory # 6","Reserve Sharing Groups","R5.19.",null,"RSGE shall meet the sustainability requirements specified in NPCC Directory 5 Reserve.","2012-08-09","2017-01-20","Retired","No"]
[445,"Directory # 6","Reserve Sharing Groups","R5.2.",null,"The BA acting as the RSG Coordinator.","2012-08-09","2017-01-20","Retired","No"]
[446,"Directory # 6","Reserve Sharing Groups","R5.3.",null,"Intermediary BAs that have agreed to facilitate the transfer of Reserve Sharing Group Energy (RSGE) between non adjacent BAs in a RSG, through the intermediary BA Area(s)_ without utilizing the RSGE or providing reserve for other BAs. Such BAs will be designated as a wheeling only BA and are not part of the RSG.","2012-08-09","2017-01-20","Retired","No"]
[447,"Directory # 6","Reserve Sharing Groups","R5.4.",null,"The effective date of the RSG Agreement and the renewal, review and termination dates, if applicable.","2012-08-09","2017-01-20","Retired","No"]
[448,"Directory # 6","Reserve Sharing Groups","R5.5.",null,"The reserve product(s) being shared (e.g. ten-minute reserve, ten-minute synchronized reserve and/or thirty-minute reserve).","2012-08-09","2017-01-20","Retired","No"]
[449,"Directory # 6","Reserve Sharing Groups","R5.6.",null,"The minimum amount of each reserve product required by each of the participating BAs.","2012-08-09","2017-01-20","Retired","No"]
[450,"Directory # 6","Reserve Sharing Groups","R5.7.",null,"The conditions under which a participating BA will declare that they are unable to provide RSGE.","2012-08-09","2017-01-20","Retired","No"]
[451,"Directory # 6","Reserve Sharing Groups","R5.8.",null,"The method for determining RSGE share sizes for the participating BAs.","2012-08-09","2017-01-20","Retired","No"]
[452,"Directory # 6","Reserve Sharing Groups","R5.9.",null,"The conditions under which RSGE may be activated, including any time limits after a contingency occurs.","2012-08-09","2017-01-20","Retired","No"]
[464,"Directory # 6 V1","Reserve Sharing Groups","R1.",null,"The Balancing Authorities (BAs) participating in a Reserve Sharing Group (RSG) shall have a RSG Agreement that meets the requirements as specified in section 5.2.","2017-01-21","2019-09-26","Retired","No"]
[463,"Directory # 6 V1","Reserve Sharing Groups","R2.",null,"Each RSG shall provide their RSG Agreement to the Task Force for Coordination of Operation for review before it is implemented.","2017-01-21","2019-09-26","Retired","No"]
[465,"Directory # 6 V1","Reserve Sharing Groups","R2.1.",null,"New RSG Agreements and future changes to existing RSG Agreements shall be approved by the Reliability Coordinating Committee (RCC).","2017-01-21","2019-09-26","Retired","No"]
[466,"Directory # 6 V1","Reserve Sharing Groups","R3.",null,"The Balancing Authorities (BAs) participating in a Reserve Sharing Group (RSG) shall be adjoining BAs unless they have a wheeling agreement with the intermediary BA or BAs.","2017-01-21","2019-09-26","Retired","No"]
[467,"Directory # 6 V1","Reserve Sharing Groups","R4.",null,"Each RSG shall provide the Task Force on Coordination of Operation with a quantitative estimate of the change in reliability risk related to a RSG agreement for review before their RSG Agreement is implemented.\r\nThere are a number of studies that could be performed to analyze the change in reliability risk such as:\r\n• Megawatt Loss Probability Method\r\n• Statistical analysis on the NPCC reportable events reports (NERC Form CR-1 reports)/Chronological event database\r\n• Other comparable methods that produce the required reliability risk estimate.","2017-01-21","2019-09-26","Retired","No"]
[468,"Directory # 6 V1","Reserve Sharing Groups","R5.",null,"Each RSG Agreement shall specify the following:","2017-01-21","2019-09-26","Retired","No"]
[469,"Directory # 6 V1","Reserve Sharing Groups","R5.1.",null,"The BAs participating in the RSG.","2017-01-21","2019-09-26","Retired","No"]
[478,"Directory # 6 V1","Reserve Sharing Groups","R5.10.",null,"Details of how the activation and termination of RSGE are coordinated with simultaneous activation of ten-minute reserve (SAR) energy, other existing reserve activation agreements and other RSGs.","2017-01-21","2019-09-26","Retired","No"]
[479,"Directory # 6 V1","Reserve Sharing Groups","R5.11.",null,"The Ramp to be utilized for Schedule changes when RSGE is activated and/or terminated.","2017-01-21","2019-09-26","Retired","No"]
[480,"Directory # 6 V1","Reserve Sharing Groups","R5.12.",null,"The maximum duration for which the RSGE can be activated.","2017-01-21","2019-09-26","Retired","No"]
[481,"Directory # 6 V1","Reserve Sharing Groups","R5.13.",null,"Times within which the RSG Coordinator shall:\r\n• Communicate changes in availability and deliverability of RSGE that are reported to it\r\n• Develop allocation shares, if necessary\r\n• Specify Schedule changes to activate RSGE\r\n• Adjust Schedules to terminate the delivery of RSGE.","2017-01-21","2019-09-26","Retired","No"]
[482,"Directory # 6 V1","Reserve Sharing Groups","R5.14.",null,"The communication method(s) to be used to exchange information with the RSG Coordinator.","2017-01-21","2019-09-26","Retired","No"]
[483,"Directory # 6 V1","Reserve Sharing Groups","R5.15.",null,"The information that must be exchanged between the RSG Coordinator and participating BAs and between the RSG Coordinator and other RSG Coordinators and the SAR Coordinator.","2017-01-21","2019-09-26","Retired","No"]
[484,"Directory # 6 V1","Reserve Sharing Groups","R5.16.",null,"Requirements for the payback of any delivered RSGE.","2017-01-21","2019-09-26","Retired","No"]
[485,"Directory # 6 V1","Reserve Sharing Groups","R5.17.",null,"How transmission capability is utilized for planning and ensuring the availability and deliverability of RSGE.","2017-01-21","2019-09-26","Retired","No"]
[486,"Directory # 6 V1","Reserve Sharing Groups","R5.18.",null,"The allocation between participating BAs, of any penalties resulting from the violation of NPCC or NERC criteria or standards.","2017-01-21","2019-09-26","Retired","No"]
[487,"Directory # 6 V1","Reserve Sharing Groups","R5.19.",null,"RSGE shall meet the sustainability requirements specified in NPCC Directory 5 Reserve.","2017-01-21","2019-09-26","Retired","No"]
[470,"Directory # 6 V1","Reserve Sharing Groups","R5.2.",null,"The BA acting as the RSG Coordinator.","2017-01-21","2019-09-26","Retired","No"]
[471,"Directory # 6 V1","Reserve Sharing Groups","R5.3.",null,"Intermediary BAs that have agreed to facilitate the transfer of Reserve Sharing Group Energy (RSGE) between non adjacent BAs in a RSG, through the intermediary BA Area(s)_ without utilizing the RSGE or providing reserve for other BAs. Such BAs will be designated as a wheeling only BA and are not part of the RSG.","2017-01-21","2019-09-26","Retired","No"]
[472,"Directory # 6 V1","Reserve Sharing Groups","R5.4.",null,"The effective date of the RSG Agreement and the renewal, review and termination dates, if applicable.","2017-01-21","2019-09-26","Retired","No"]
[473,"Directory # 6 V1","Reserve Sharing Groups","R5.5.",null,"The reserve product(s) being shared (e.g. ten-minute reserve, ten-minute synchronized reserve and/or thirty-minute reserve).","2017-01-21","2019-09-26","Retired","No"]
[474,"Directory # 6 V1","Reserve Sharing Groups","R5.6.",null,"The minimum amount of each reserve product required by each of the participating BAs.","2017-01-21","2019-09-26","Retired","No"]
[475,"Directory # 6 V1","Reserve Sharing Groups","R5.7.",null,"The conditions under which a participating BA will declare that they are unable to provide RSGE.","2017-01-21","2019-09-26","Retired","No"]
[476,"Directory # 6 V1","Reserve Sharing Groups","R5.8.",null,"The method for determining RSGE share sizes for the participating BAs.","2017-01-21","2019-09-26","Retired","No"]
[477,"Directory # 6 V1","Reserve Sharing Groups","R5.9.",null,"The conditions under which RSGE may be activated, including any time limits after a contingency occurs.","2017-01-21","2019-09-26","Retired","No"]
[100,"Directory # 6 V2","Reserve Sharing Groups","R1.",null,"Reserve Sharing Group Requirements: \nThe Balancing Authorities (BAs) participating in a Reserve Sharing Group (RSG) shall have a RSG Agreement that meets the requirements as specified in section 5.2.","2019-09-27",null,"Effective","No","RSG, BA"]
[101,"Directory # 6 V2","Reserve Sharing Groups","R2.",null,"Each RSG shall provide their RSG Agreement to the Regional Entity for review before it is implemented.","2019-09-27",null,"Effective","No","RSG, BA"]
[303,"Directory # 6 V2","Reserve Sharing Groups","R2.1.",null,"New RSG Agreements and future changes to existing RSG Agreements shall be approved by the Reliability Coordinating Committee (RCC).","2019-09-27",null,"Effective","No","RSG, BA"]
[102,"Directory # 6 V2","Reserve Sharing Groups","R3.",null,"The Balancing Authorities (BAs) participating in a Reserve Sharing Group (RSG) shall be adjoining BAs unless they have a wheeling agreement with the intermediary BA or BAs.","2019-09-27",null,"Effective","No","RSG, BA"]
[103,"Directory # 6 V2","Reserve Sharing Groups","R4.",null,"Each RSG shall provide the Task Force on Coordination of Operation with a quantitative estimate of the change in reliability risk related to a RSG agreement for review before their RSG Agreement is implemented.\r\nThere are a number of studies that could be performed to analyze the change in reliability risk such as:\r\n• Megawatt Loss Probability Method\r\n• Statistical analysis on the NPCC reportable events reports (NERC Form CR-1 reports)/Chronological event database\r\n• Other comparable methods that produce the required reliability risk estimate.","2019-09-27",null,"Effective","No","RSG, BA"]
[104,"Directory # 6 V2","Reserve Sharing Groups","R5.",null,"Reserve Sharing Group Agreement Requirements:\nEach RSG Agreement shall specify the following:","2019-09-27",null,"Effective","No","RSG, BA"]
[105,"Directory # 6 V2","Reserve Sharing Groups","R5.1.",null,"The BAs participating in the RSG.","2019-09-27",null,"Effective","No","RSG, BA"]
[114,"Directory # 6 V2","Reserve Sharing Groups","R5.10.",null,"Details of how the activation and termination of RSGE are coordinated with Simultaneous Activation of Reserve Energy, other existing reserve activation agreements and other RSGs.","2019-09-27",null,"Effective","No","RSG, BA"]
[115,"Directory # 6 V2","Reserve Sharing Groups","R5.11.",null,"The ramp duration to be utilized for schedule changes when RSGE is activated and/or terminated.","2019-09-27",null,"Effective","No","RSG, BA"]
[116,"Directory # 6 V2","Reserve Sharing Groups","R5.12.",null,"The maximum duration for which the RSGE can be activated.","2019-09-27",null,"Effective","No","RSG, BA"]
[117,"Directory # 6 V2","Reserve Sharing Groups","R5.13.",null,"Times within which the RSG Coordinator shall:\r\n• Communicate changes in availability and deliverability of RSGE that are reported to it\r\n• Develop allocation shares, if necessary\r\n• Specify Schedule changes to activate RSGE\r\n• Adjust Schedules to terminate the delivery of RSGE.","2019-09-27",null,"Effective","No","RSG, BA"]
[118,"Directory # 6 V2","Reserve Sharing Groups","R5.14.",null,"The communication method(s) to be used to exchange information with the RSG Coordinator.","2019-09-27",null,"Effective","No","RSG, BA"]
[119,"Directory # 6 V2","Reserve Sharing Groups","R5.15.",null,"The information that must be exchanged between the RSG Coordinator and participating BAs and between the RSG Coordinator and other RSG Coordinators and the SAR Coordinator.","2019-09-27",null,"Effective","No","RSG, BA"]
[120,"Directory # 6 V2","Reserve Sharing Groups","R5.16.",null,"Requirements for the payback of any delivered RSGE.","2019-09-27",null,"Effective","No","RSG, BA"]
[121,"Directory # 6 V2","Reserve Sharing Groups","R5.17.",null,"How transmission capability is utilized for planning and ensuring the availability and deliverability of RSGE.","2019-09-27",null,"Effective","No","RSG, BA"]
[122,"Directory # 6 V2","Reserve Sharing Groups","R5.18.",null,"The allocation between participating BAs, of any penalties resulting from the violation of NPCC or NERC criteria or standards.","2019-09-27",null,"Effective","No","RSG, BA"]
[123,"Directory # 6 V2","Reserve Sharing Groups","R5.19.",null,"RSGE shall meet the sustainability requirements specified in NPCC Directory 5 Reserve.","2019-09-27",null,"Effective","No","RSG, BA"]
[106,"Directory # 6 V2","Reserve Sharing Groups","R5.2.",null,"The BA acting as the Coordinator for the RSG.","2019-09-27",null,"Effective","No","RSG, BA"]
[107,"Directory # 6 V2","Reserve Sharing Groups","R5.3.",null,"Intermediary BAs that have agreed to facilitate the transfer of Reserve Sharing Group Energy (RSGE) between non adjacent BAs in a RSG, through their BA Area without utilizing the RSGE or providing reserve for other BAs. Such BAs will be designated as a wheeling only BA and are not part of the RSG.","2019-09-27",null,"Effective","No","RSG, BA"]
[108,"Directory # 6 V2","Reserve Sharing Groups","R5.4.",null,"The effective date of the RSG Agreement and the renewal, review and termination dates if applicable.","2019-09-27",null,"Effective","No","RSG, BA"]
[109,"Directory # 6 V2","Reserve Sharing Groups","R5.5.",null,"The reserve product(s) being shared (e.g. ten minute, ten minute synchronized and thirty minute).","2019-09-27",null,"Effective","No","RSG, BA"]
[110,"Directory # 6 V2","Reserve Sharing Groups","R5.6.",null,"The minimum amount of each reserve product required by each of the participating BAs.","2019-09-27",null,"Effective","No","RSG, BA"]
[111,"Directory # 6 V2","Reserve Sharing Groups","R5.7.",null,"The conditions under which a participating BA will declare that they are unable to provide RSGE.","2019-09-27",null,"Effective","No","RSG, BA"]
[112,"Directory # 6 V2","Reserve Sharing Groups","R5.8.",null,"The method for determining RSGE share sizes for the participating BAs.","2019-09-27",null,"Effective","No","RSG, BA"]
[113,"Directory # 6 V2","Reserve Sharing Groups","R5.9.",null,"The conditions under which RSGE may be activated, including any time limits after a contingency occurs.","2019-09-27",null,"Effective","No","RSG, BA"]
[488,"Directory # 8","System Restoration","R1.","YES","Each Reliability Coordinator shall develop and maintain a restoration plan for its Reliability Coordinator Area that shall:","2014-04-03","2017-01-20","Retired","No"]
[489,"Directory # 8","System Restoration","R1.1.","YES","Identify the Reliability Coordinator Area’s basic minimum power system(s).","2014-04-03","2017-01-20","Retired","No"]
[490,"Directory # 8","System Restoration","R1.2.","YES","Address the priority of restoring off-site power to nuclear plants;","2014-04-03","2017-01-20","Retired","No"]
[491,"Directory # 8","System Restoration","R1.3.","YES","Identify interconnection points with adjacent Reliability Coordinator areas;","2014-04-03","2017-01-20","Retired","No"]
[492,"Directory # 8","System Restoration","R1.4.","YES","Identify parameters to synchronize adjacent basic minimum power systems;","2014-04-03","2017-01-20","Retired","No"]
[493,"Directory # 8","System Restoration","R1.5.","YES","Address coordination of system restoration with neighboring Reliability Coordinator areas;","2014-04-03","2017-01-20","Retired","No"]
[494,"Directory # 8","System Restoration","R1.6.","YES","Provide for the re-energization of transmission systems to major generating stations, including inter-area tie points;","2014-04-03","2017-01-20","Retired","No"]
[495,"Directory # 8","System Restoration","R1.7.","YES","Address electrical island stabilization;","2014-04-03","2017-01-20","Retired","No"]
[496,"Directory # 8","System Restoration","R1.8.","YES","Identify provisions for fuel resources to support operation of any supplementary generators (e.g., a diesel generator) necessary for operating key facilities consistent with the expected requirements of the Restoration Plan.","2014-04-03","2017-01-20","Retired","No"]
[519,"Directory # 8","System Restoration","R10.",null,"Each functional entity shall test its backup power supplies identified as critical components as specified below. Where there are separate backup power arrangements at a key facility for transmission or generating station equipment and telecommunication equipment, they shall be separately identified in the critical components list and shall be inspected and tested individually.","2014-04-03","2017-01-20","Retired","No"]
[520,"Directory # 8","System Restoration","R10.1.",null,"Equipment Inspection: A battery and/or battery charger identified as a critical component shall be inspected in accordance with maintenance activities and maintenance intervals specified in PRC-005-Protection System, Automatic Reclosing, and Sudden Pressure Relaying Maintenance. (Reference: Table 1; Test KF-1)","2014-04-03","2017-01-20","Retired","No"]
[521,"Directory # 8","System Restoration","R10.2.",null,"Equipment Verification\r\nA battery and battery charger identified as critical components shall be verified in accordance with maintenance activities and maintenance intervals specified in PRC-005 Protection System, Automatic Reclosing, and Sudden Pressure Relaying Maintenance. (Reference: Table 1; Test KF-2)","2014-04-03","2017-01-20","Retired","No"]
[522,"Directory # 8","System Restoration","R10.3.",null,"Confirm that all Critical Component Loads can be Supplied\r\nThe owner of batteries or battery chargers identified as critical components shall confirm that all critical component loads are connected to and can be supplied by the batteries and battery chargers. At least every sixty (60) calendar months, or when modifications are made to the key facility, the functional entity owner shall confirm through its design review or through testing that all critical component loads are connected to and can be sufficiently supplied by the batteries and battery chargers. (Reference: Table 1; Test KF-3)","2014-04-03","2017-01-20","Retired","No"]
[523,"Directory # 8","System Restoration","R10.4.",null,"Startup and Run Test\r\nThe owner of a backup power generator identified as a critical component of a key facility, shall perform a monthly startup and run test on that backup power generator for a minimum run time of fifteen (15) minutes. (Reference: Table 1; Test KF-5).\r\nNote: This test also applies to supplemental generation required for blackstart capability and to a control center and telecommunication center backup power generator.","2014-04-03","2017-01-20","Retired","No"]
[524,"Directory # 8","System Restoration","R10.5.",null,"Startup, Transfer and Load Test\r\nThe owner of a backup power generator identified as a critical component of a key facility shall verify that the backup power generator will pick up the critical component load following the loss of station service. Note: This test also applies to a control center and telecommunication center backup power generator.\r\nFor automatically started backup power generators, a startup, transfer and run test simulating the loss of station service will be performed every twelve (12) calendar months for a duration of at least thirty (30) minutes. (Reference: Table 1; Test KF-6)\r\nFor manually started backup power generators, the asset owner shall every twelve (12) calendar months start the generator and verify stable operation for thirty (30) minutes while supplying critical component loads. (Reference: Table 1; Test KF-6) Note: Power sources used to start blackstart units will be excluded from test KF-6.","2014-04-03","2017-01-20","Retired","No"]
[525,"Directory # 8","System Restoration","R11.",null,"Each functional entity identified as owning key facilities shall test its critical components in the control centers and the telecommunication centers identified as key facilities to demonstrate that the computer systems will be functional when required for system restoration, without dependencies on power sources that may be unavailable during a partial or complete system blackout.","2014-04-03","2017-01-20","Retired","No"]
[526,"Directory # 8","System Restoration","R11.1.",null,"AC Supply Interruption Test\r\nThe uninterruptible power supply (UPS) systems in control centers and telecommunication centers shall be tested every twelve (12) calendar months by interrupting AC supply and verifying that all critical component loads are supplied for a time that is sufficient for backup power sources to restore the AC input to the UPS. (Reference: Table 1; Test CC-1)","2014-04-03","2017-01-20","Retired","No"]
[527,"Directory # 8","System Restoration","R11.2.",null,"Computer Redundancy (SCADA/EMS) Test\r\nEach functional entity identified as owning a key facility shall test its computer redundancy (SCADA/EMS) features every six (6) calendar months to ensure computer systems (SCADA/EMS) continue to function adequately. (Reference: Table 1; Test CC--2)","2014-04-03","2017-01-20","Retired","No"]
[528,"Directory # 8","System Restoration","R12.",null,"Each functional entity owning a generating station with blackstart capability shall verify such capability as follows:","2014-04-03","2017-01-20","Retired","No"]
[529,"Directory # 8","System Restoration","R12.1.",null,"Operations voice communications and auxiliary systems such as Supervisory Control and Data Acquisition (SCADA) that are required for blackstart shall be verified at least every twelve (12) calendar months to operate adequately without dependency on the interconnected system or other unrelated unit for any source of station service.","2014-04-03","2017-01-20","Retired","No"]
[530,"Directory # 8","System Restoration","R12.2.",null,"A generating station with blackstart capability shall be tested every twelve (12) calendar months for successful equipment startup and energize a transmission element or a generating station switchyard element if that doesn’t involve the disconnection of load that is not dedicated generating station load to conduct the test. Verify stable operation while isolated from the bulk power system for a minimum of ten minutes. (Reference: Table 1; Test BS-1). (Reference: Appendix A-Table 1; Test No. BS-1)","2014-04-03","2017-01-20","Retired","No"]
[531,"Directory # 8","System Restoration","R13.","YES","Reliability Coordinators shall determine the number of units within a generating station that are to be tested for blackstart capability as required by their respective system restoration plans, and shall notify the applicable functional entity.","2014-04-03","2017-01-20","Retired","No"]
[532,"Directory # 8","System Restoration","R14.","YES","Each Reliability Coordinator shall confirm that the functional entity owning a generating station with blackstart capability that is part of the basic minimum power system has completed a successful blackstart test consistent with the objectives of the Reliability Coordinator’s system restoration plan.","2014-04-03","2017-01-20","Retired","No"]
[533,"Directory # 8","System Restoration","R15.",null,"A functional entity that has confirmed the loss of functionality of a critical component shall report to the Transmission Operator responsible for operating that critical component of that critical component’s loss of functional availability as soon as possible but no longer than 15 minutes after becoming aware of the condition.","2014-04-03","2017-01-20","Retired","No"]
[534,"Directory # 8","System Restoration","R15.1.",null,"The Transmission Operator shall report to its Reliability Coordinator as soon as possible but no longer than 15 minutes after the functional entity has made the Transmission Operator aware of the loss of functionality of the critical component.\r\nExamples of such conditions are but not limited to:\r\n• Loss of control of remote equipment;\r\n• Complete loss of AC or DC service supply;\r\n• Loss of blackstart facilities.","2014-04-03","2017-01-20","Retired","No"]
[535,"Directory # 8","System Restoration","R16.",null,"A functional entity that has confirmed the loss of redundancy of a critical component shall report to the Transmission Operator responsible for that critical component as soon as possible but no longer than 12 hours after the functional entity’s staff has confirmed the loss of redundancy for the critical component.\r\nExamples of such conditions are:\r\n• Loss of a redundant AC or DC service supply;\r\n• Loss of redundant blackstart critical components.","2014-04-03","2017-01-20","Retired","No"]
[536,"Directory # 8","System Restoration","R17.",null,"A functional entity that has scheduled a maintenance condition of a critical component that will result in the loss of functionality of that critical component shall report that maintenance condition to the Transmission Operator responsible for the critical component at least 24 hours prior to that scheduled loss of functionality.","2014-04-03","2017-01-20","Retired","No"]
[537,"Directory # 8","System Restoration","R17.1.",null,"The functional entity shall report to the Transmission Operator responsible for the critical component as soon as possible after the loss of functionality has occurred.","2014-04-03","2017-01-20","Retired","No"]
[538,"Directory # 8","System Restoration","R17.2.",null,"If the scheduled maintenance condition causing the loss of functionality of a critical component affects the functionality of a key facility, the Transmission Operator responsible for the critical component shall report this scheduled maintenance condition to its Reliability Coordinator.","2014-04-03","2017-01-20","Retired","No"]
[539,"Directory # 8","System Restoration","R18.",null,"A functional entity shall report the actions to be taken to restore a critical component’s availability or redundancy to the Transmission Operator responsible for the critical component as soon as known.","2014-04-03","2017-01-20","Retired","No"]
[540,"Directory # 8","System Restoration","R18.1.",null,"The functional entity shall report to the Transmission Operator responsible for that critical component the anticipated time that the critical components functionality will be restored.","2014-04-03","2017-01-20","Retired","No"]
[541,"Directory # 8","System Restoration","R18.2.",null,"The functional entity shall report to the Transmission Operator responsible for maintaining redundancy for a critical component the anticipated time that the critical component’s redundancy will be restored.","2014-04-03","2017-01-20","Retired","No"]
[542,"Directory # 8","System Restoration","R19.",null,"A functional entity shall report the date and time when the functional availability of a critical component is restored to the Transmission Operator responsible for the critical component as soon as known.","2014-04-03","2017-01-20","Retired","No"]
[497,"Directory # 8","System Restoration","R2.","YES","In determining the basic minimum power system, the Reliability Coordinator shall involve all affected parties or functional entities.","2014-04-03","2017-01-20","Retired","No"]
[498,"Directory # 8","System Restoration","R3.","YES","The Reliability Coordinator shall ensure that the basic minimum power system includes the ability to:","2014-04-03","2017-01-20","Retired","No"]
[499,"Directory # 8","System Restoration","R3.1.","YES","Utilize generator blackstart capability;","2014-04-03","2017-01-20","Retired","No"]
[500,"Directory # 8","System Restoration","R3.2.","YES","Form an electrical island(s);","2014-04-03","2017-01-20","Retired","No"]
[501,"Directory # 8","System Restoration","R3.3.","YES","Synchronize electrical islands; and","2014-04-03","2017-01-20","Retired","No"]
[502,"Directory # 8","System Restoration","R3.4.","YES","Permit the continuation of the system restoration plan.","2014-04-03","2017-01-20","Retired","No"]
[503,"Directory # 8","System Restoration","R4.","YES","Each Reliability Coordinator shall identify key facilities and shall inform each functional entity of its identified key facilities.","2014-04-03","2017-01-20","Retired","No"]
[504,"Directory # 8","System Restoration","R5.",null,"Each functional entity identified as the owner of a newly identified or proposed key facility:","2014-04-03","2017-01-20","Retired","No"]
[505,"Directory # 8","System Restoration","R5.1.",null,"Shall identify the associated critical components for that key facility prior to implementation of the proposed facility as a key facility.","2014-04-03","2017-01-20","Retired","No"]
[506,"Directory # 8","System Restoration","R5.2.",null,"Shall provide a list of critical components associated with the proposed key facility upon request of the Reliability Coordinator within the timeframe requested.","2014-04-03","2017-01-20","Retired","No"]
[507,"Directory # 8","System Restoration","R5.3.",null,"Shall ensure that all applicable testing outlined in Appendix A has been successfully completed prior to implementation, or within the timeframe requested by the Reliability Coordinator, of the proposed key facility.","2014-04-03","2017-01-20","Retired","No"]
[508,"Directory # 8","System Restoration","R6.",null,"Each functional entity identified as the owner of an existing key facility:","2014-04-03","2017-01-20","Retired","No"]
[509,"Directory # 8","System Restoration","R6.1.",null,"Shall provide any updates, additions or deletions to the list of critical components for each identified key facility upon request of the Reliability Coordinator within the timeframe requested.","2014-04-03","2017-01-20","Retired","No"]
[510,"Directory # 8","System Restoration","R6.2.",null,"Shall ensure that all applicable testing outlined in Appendix A has been successfully completed for any updated or additional critical components associated with each identified key facility.","2014-04-03","2017-01-20","Retired","No"]
[511,"Directory # 8","System Restoration","R7.","YES","Following the occurrence of an event that required implementation of a system restoration plan and upon request of the Task Force on Coordination of Operation (TFCO):","2014-04-03","2017-01-20","Retired","No"]
[512,"Directory # 8","System Restoration","R7.1.","YES","The Reliability Coordinator shall report on the performance of its plan within the timeframe requested by the TFCO.","2014-04-03","2017-01-20","Retired","No"]
[513,"Directory # 8","System Restoration","R7.2.","YES","The Transmission Operator shall report on the performance of its plan within the timeframe requested by the TFCO.","2014-04-03","2017-01-20","Retired","No"]
[514,"Directory # 8","System Restoration","R8.",null,"Each functional entity which has been identified as owning a key facility shall:","2014-04-03","2017-01-20","Retired","No"]
[515,"Directory # 8","System Restoration","R8.1.",null,"Perform the tests outlined in Appendix A - Table 1","2014-04-03","2017-01-20","Retired","No"]
[516,"Directory # 8","System Restoration","R8.2.",null,"Maintain records of the test results","2014-04-03","2017-01-20","Retired","No"]
[517,"Directory # 8","System Restoration","R8.3.",null,"Provide evidence, upon request, to the Reliability Coordinator and Transmission Operator within the timeframe requested that the tests specified in sub-Requirement R8.1 have been met.","2014-04-03","2017-01-20","Retired","No"]
[518,"Directory # 8","System Restoration","R9.",null,"Each functional entity that owns a cable pressurization system at a key facility shall test for satisfactory operation of both the primary pressurization system and/or the backup pressurization system (if applicable) ability(s) to maintain pressure upon loss of power to the key facility.\r\nThis capability is required during a blackout to maintain the availability of cables for service and to preclude any damage to the cables as a result of the loss of dielectric strength. This test shall be conducted every six (6) calendar months by demonstrating that the required pressures can be maintained for a minimum of thirty (30) minutes.","2014-04-03","2017-01-20","Retired","No"]
[543,"Directory # 8 V3","System Restoration","R1.","YES","Each Reliability Coordinator shall develop and maintain a restoration plan for its Reliability Coordinator Area that shall:","2017-01-21","2018-09-24","Retired","No"]
[544,"Directory # 8 V3","System Restoration","R1.1.","YES","System Restoration","2017-01-21","2018-09-24","Retired","No"]
[545,"Directory # 8 V3","System Restoration","R1.2.","YES","Address the priority of restoring off-site power to nuclear plants;","2017-01-21","2018-09-24","Retired","No"]
[546,"Directory # 8 V3","System Restoration","R1.3.","YES","Identify interconnection points with adjacent Reliability Coordinator areas;","2017-01-21","2018-09-24","Retired","No"]
[547,"Directory # 8 V3","System Restoration","R1.4.","YES","Identify parameters to synchronize adjacent basic minimum power systems;","2017-01-21","2018-09-24","Retired","No"]
[548,"Directory # 8 V3","System Restoration","R1.5.","YES","Address coordination of system restoration with neighboring Reliability Coordinator areas;","2017-01-21","2018-09-24","Retired","No"]
[549,"Directory # 8 V3","System Restoration","R1.6.","YES","Provide for the re-energization of transmission systems to major generating stations, including inter-area tie points;","2017-01-21","2018-09-24","Retired","No"]
[550,"Directory # 8 V3","System Restoration","R1.7.","YES","Address electrical island stabilization;","2017-01-21","2018-09-24","Retired","No"]
[551,"Directory # 8 V3","System Restoration","R1.8.","YES","Identify provisions for fuel resources to support operation of any supplementary generators (e.g., a diesel generator) necessary for operating key facilities consistent with the expected requirements of the Restoration Plan.","2017-01-21","2018-09-24","Retired","No"]
[574,"Directory # 8 V3","System Restoration","R10.",null,"Each functional entity shall test its backup power supplies identified as critical components as specified below. Where there are separate backup power arrangements at a key facility for transmission or generating station equipment and telecommunication equipment, they shall be separately identified in the critical components list and shall be inspected and tested individually.","2017-01-21","2018-09-24","Retired","No"]
[575,"Directory # 8 V3","System Restoration","R10.1.",null,"Equipment Inspection: A battery and/or battery charger identified as a critical component shall be inspected in accordance with maintenance activities and maintenance intervals specified in PRC-005-Protection System, Automatic Reclosing, and Sudden Pressure Relaying Maintenance. (Reference: Table 1; Test KF-1)","2017-01-21","2018-09-24","Retired","No"]
[576,"Directory # 8 V3","System Restoration","R10.2.",null,"Equipment Verification\r\nA battery and battery charger identified as critical components shall be verified in accordance with maintenance activities and maintenance intervals specified in PRC-005 Protection System, Automatic Reclosing, and Sudden Pressure Relaying Maintenance. (Reference: Table 1; Test KF-2)","2017-01-21","2018-09-24","Retired","No"]
[577,"Directory # 8 V3","System Restoration","R10.3.",null,"Confirm that all Critical Component Loads can be Supplied\r\nThe owner of batteries or battery chargers identified as critical components shall confirm that all critical component loads are connected to and can be supplied by the batteries and battery chargers. At least every sixty (60) calendar months, or when modifications are made to the key facility, the functional entity owner shall confirm through its design review or through testing that all critical component loads are connected to and can be sufficiently supplied by the batteries and battery chargers. (Reference: Table 1; Test KF-3)","2017-01-21","2018-09-24","Retired","No"]
[578,"Directory # 8 V3","System Restoration","R10.4.",null,"Startup and Run Test\r\nThe owner of a backup power generator identified as a critical component of a key facility, shall perform a monthly startup and run test on that backup power generator for a minimum run time of fifteen (15) minutes. (Reference: Table 1; Test KF-5).\r\nNote: This test also applies to supplemental generation required for blackstart capability and to a control center and telecommunication center backup power generator.","2017-01-21","2018-09-24","Retired","No"]
[579,"Directory # 8 V3","System Restoration","R10.5.",null,"Startup, Transfer and Load Test\r\nThe owner of a backup power generator identified as a critical component of a key facility shall verify that the backup power generator will pick up the critical component load following the loss of station service. Note: This test also applies to a control center and telecommunication center backup power generator.\r\nFor automatically started backup power generators, a startup, transfer and run test simulating the loss of station service will be performed every twelve (12) calendar months for a duration of at least thirty (30) minutes. (Reference: Table 1; Test KF-6)\r\nFor manually started backup power generators, the asset owner shall every twelve (12) calendar months start the generator and verify stable operation for thirty (30) minutes while supplying critical component loads. (Reference: Table 1; Test KF-6) Note: Power sources used to start blackstart units will be excluded from test KF-6.\r\nThe owner of a backup power generator identified as a critical component of a key facility shall verify that the backup power generator will pick up the critical component load following the loss of station service.","2017-01-21","2018-09-24","Retired","No"]
[580,"Directory # 8 V3","System Restoration","R11.",null,"Each functional entity identified as owning key facilities shall test its critical components in the control centers and the telecommunication centers identified as key facilities to demonstrate that the computer systems will be functional when required for system restoration, without dependencies on power sources that may be unavailable during a partial or complete system blackout.","2017-01-21","2018-09-24","Retired","No"]
[581,"Directory # 8 V3","System Restoration","R11.1.",null,"AC Supply Interruption Test\r\nThe uninterruptible power supply (UPS) systems in control centers and telecommunication centers shall be tested every twelve (12) calendar months by interrupting AC supply and verifying that all critical component loads are supplied for a time that is sufficient for backup power sources to restore the AC input to the UPS. (Reference: Table 1; Test CC-1)","2017-01-21","2018-09-24","Retired","No"]
[582,"Directory # 8 V3","System Restoration","R11.2.",null,"Computer Redundancy (SCADA/EMS) Test\r\nEach functional entity identified as owning a key facility shall test its computer redundancy (SCADA/EMS) features every six (6) calendar months to ensure computer systems (SCADA/EMS) continue to function adequately. (Reference: Table 1; Test CC--2)","2017-01-21","2018-09-24","Retired","No"]
[583,"Directory # 8 V3","System Restoration","R12.",null,"Each functional entity owning a generating station with blackstart capability shall verify such capability as follows:","2017-01-21","2018-09-24","Retired","No"]
[584,"Directory # 8 V3","System Restoration","R12.1.",null,"Operations voice communications and auxiliary systems such as Supervisory Control and Data Acquisition (SCADA) that are required for blackstart shall be verified at least every twelve (12) calendar months to operate adequately without dependency on the interconnected system or other unrelated unit for any source of station service.","2017-01-21","2018-09-24","Retired","No"]
[585,"Directory # 8 V3","System Restoration","R12.2.",null,"A generating station with blackstart capability shall be tested every twelve (12) calendar months for successful equipment startup and energize a transmission element or a generating station switchyard element if that doesn’t involve the disconnection of load that is not dedicated generating station load to conduct the test. Verify stable operation while isolated from the bulk power system for a minimum of ten minutes. (Reference: Table 1; Test BS-1). (Reference: Appendix A-Table 1; Test No. BS-1)","2017-01-21","2018-09-24","Retired","No"]
[586,"Directory # 8 V3","System Restoration","R13.","YES","Reliability Coordinators shall determine the number of units within a generating station that are to be tested for blackstart capability as required by their respective system restoration plans, and shall notify the applicable functional entity.","2017-01-21","2018-09-24","Retired","No"]
[587,"Directory # 8 V3","System Restoration","R14.","YES","Each Reliability Coordinator shall confirm that the functional entity owning a generating station with blackstart capability that is part of the basic minimum power system has completed a successful blackstart test consistent with the objectives of the Reliability Coordinator’s system restoration plan.","2017-01-21","2018-09-24","Retired","No"]
[588,"Directory # 8 V3","System Restoration","R15.",null,"A functional entity that has confirmed the loss of functionality of a critical component shall report to the Transmission Operator responsible for operating that critical component of that critical component’s loss of functional availability as soon as possible but no longer than 15 minutes after becoming aware of the condition.","2017-01-21","2018-09-24","Retired","No"]
[589,"Directory # 8 V3","System Restoration","R15.1.",null,"The Transmission Operator shall report to its Reliability Coordinator as soon as possible but no longer than 15 minutes after the functional entity has made the Transmission Operator aware of the loss of functionality of the critical component.\r\nExamples of such conditions are but not limited to:\r\n• Loss of control of remote equipment;\r\n• Complete loss of AC or DC service supply;\r\n• Loss of blackstart facilities.","2017-01-21","2018-09-24","Retired","No"]
[590,"Directory # 8 V3","System Restoration","R16.",null,"A functional entity that has confirmed the loss of redundancy of a critical component shall report to the Transmission Operator responsible for that critical component as soon as possible but no longer than 12 hours after the functional entity’s staff has confirmed the loss of redundancy for the critical component.\r\nExamples of such conditions are:\r\n• Loss of a redundant AC or DC service supply;\r\n• Loss of redundant blackstart critical components.","2017-01-21","2018-09-24","Retired","No"]
[591,"Directory # 8 V3","System Restoration","R17.",null,"A functional entity that has scheduled a maintenance condition of a critical component that will result in the loss of functionality of that critical component shall report that maintenance condition to the Transmission Operator responsible for the critical component at least 24 hours prior to that scheduled loss of functionality.","2017-01-21","2018-09-24","Retired","No"]
[592,"Directory # 8 V3","System Restoration","R17.1.",null,"The functional entity shall report to the Transmission Operator responsible for the critical component as soon as possible after the loss of functionality has occurred.","2017-01-21","2018-09-24","Retired","No"]
[593,"Directory # 8 V3","System Restoration","R17.2.",null,"If the scheduled maintenance condition causing the loss of functionality of a critical component affects the functionality of a key facility, the Transmission Operator responsible for the critical component shall report this scheduled maintenance condition to its Reliability Coordinator.","2017-01-21","2018-09-24","Retired","No"]
[594,"Directory # 8 V3","System Restoration","R18.",null,"A functional entity shall report the actions to be taken to restore a critical component’s availability or redundancy to the Transmission Operator responsible for the critical component as soon as known.","2017-01-21","2018-09-24","Retired","No"]
[595,"Directory # 8 V3","System Restoration","R18.1.",null,"The functional entity shall report to the Transmission Operator responsible for that critical component the anticipated time that the critical components functionality will be restored.","2017-01-21","2018-09-24","Retired","No"]
[596,"Directory # 8 V3","System Restoration","R18.2.",null,"The functional entity shall report to the Transmission Operator responsible for maintaining redundancy for a critical component the anticipated time that the critical component’s redundancy will be restored.","2017-01-21","2018-09-24","Retired","No"]
[597,"Directory # 8 V3","System Restoration","R19.",null,"A functional entity shall report the date and time when the functional availability of a critical component is restored to the Transmission Operator responsible for the critical component as soon as known.","2017-01-21","2018-09-24","Retired","No"]
[552,"Directory # 8 V3","System Restoration","R2.","YES","In determining the basic minimum power system, the Reliability Coordinator shall involve all affected parties or functional entities.","2017-01-21","2018-09-24","Retired","No"]
[553,"Directory # 8 V3","System Restoration","R3.","YES","The Reliability Coordinator shall ensure that the basic minimum power system includes the ability to:","2017-01-21","2018-09-24","Retired","No"]
[554,"Directory # 8 V3","System Restoration","R3.1.","YES","Utilize generator blackstart capability;","2017-01-21","2018-09-24","Retired","No"]
[555,"Directory # 8 V3","System Restoration","R3.2.","YES","Form an electrical island(s);","2017-01-21","2018-09-24","Retired","No"]
[556,"Directory # 8 V3","System Restoration","R3.3.","YES","Synchronize electrical islands; and","2017-01-21","2018-09-24","Retired","No"]
[557,"Directory # 8 V3","System Restoration","R3.4.","YES","Permit the continuation of the system restoration plan.","2017-01-21","2018-09-24","Retired","No"]
[558,"Directory # 8 V3","System Restoration","R4.","YES","Each Reliability Coordinator shall identify key facilities and shall inform each functional entity of its identified key facilities.","2017-01-21","2018-09-24","Retired","No"]
[559,"Directory # 8 V3","System Restoration","R5.",null,"Each functional entity identified as the owner of a newly identified or proposed key facility:","2017-01-21","2018-09-24","Retired","No"]
[560,"Directory # 8 V3","System Restoration","R5.1.",null,"Shall identify the associated critical components for that key facility prior to implementation of the proposed facility as a key facility.","2017-01-21","2018-09-24","Retired","No"]
[561,"Directory # 8 V3","System Restoration","R5.2.",null,"Shall provide a list of critical components associated with the proposed key facility upon request of the Reliability Coordinator within the timeframe requested.","2017-01-21","2018-09-24","Retired","No"]
[562,"Directory # 8 V3","System Restoration","R5.3.",null,"Shall ensure that all applicable testing outlined in Appendix A has been successfully completed prior to implementation, or within the timeframe requested by the Reliability Coordinator, of the proposed key facility.","2017-01-21","2018-09-24","Retired","No"]
[563,"Directory # 8 V3","System Restoration","R6.",null,"Each functional entity identified as the owner of an existing key facility:","2017-01-21","2018-09-24","Retired","No"]
[564,"Directory # 8 V3","System Restoration","R6.1.",null,"Shall provide any updates, additions or deletions to the list of critical components for each identified key facility upon request of the Reliability Coordinator within the timeframe requested.","2017-01-21","2018-09-24","Retired","No"]
[565,"Directory # 8 V3","System Restoration","R6.2.",null,"Shall ensure that all applicable testing outlined in Appendix A has been successfully completed for any updated or additional critical components associated with each identified key facility.","2017-01-21","2018-09-24","Retired","No"]
[566,"Directory # 8 V3","System Restoration","R7.","YES","Following the occurrence of an event that required implementation of a system restoration plan and upon request of the Task Force on Coordination of Operation (TFCO):","2017-01-21","2018-09-24","Retired","No"]
[567,"Directory # 8 V3","System Restoration","R7.1.","YES","The Reliability Coordinator shall report on the performance of its plan within the timeframe requested by the TFCO.","2017-01-21","2018-09-24","Retired","No"]
[568,"Directory # 8 V3","System Restoration","R7.2.","YES","The Transmission Operator shall report on the performance of its plan within the timeframe requested by the TFCO.","2017-01-21","2018-09-24","Retired","No"]
[569,"Directory # 8 V3","System Restoration","R8.",null,"Each functional entity which has been identified as owning a key facility shall:","2017-01-21","2018-09-24","Retired","No"]
[570,"Directory # 8 V3","System Restoration","R8.1.",null,"Perform the tests outlined in Appendix A - Table 1","2017-01-21","2018-09-24","Retired","No"]
[571,"Directory # 8 V3","System Restoration","R8.2.",null,"Maintain records of the test results","2017-01-21","2018-09-24","Retired","No"]
[572,"Directory # 8 V3","System Restoration","R8.3.",null,"Provide evidence, upon request, to the Reliability Coordinator and Transmission Operator within the timeframe requested that the tests specified in sub-Requirement R8.1 have been met.","2017-01-21","2018-09-24","Retired","No"]
[573,"Directory # 8 V3","System Restoration","R9.",null,"Each functional entity that owns a cable pressurization system at a key facility shall test for satisfactory operation of both the primary pressurization system and/or the backup pressurization system (if applicable) ability(s) to maintain pressure upon loss of power to the key facility.\r\nThis capability is required during a blackout to maintain the availability of cables for service and to preclude any damage to the cables as a result of the loss of dielectric strength. This test shall be conducted every six (6) calendar months by demonstrating that the required pressures can be maintained for a minimum of thirty (30) minutes.","2017-01-21","2018-09-24","Retired","No"]
[208,"Directory # 8 V4","System Restoration","R1.","YES","Each Reliability Coordinator shall develop and maintain a restoration plan for its Reliability Coordinator Area that shall:","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[209,"Directory # 8 V4","System Restoration","R1.1.","YES","Identify the Reliability Coordinator Area’s basic minimum power system(s).","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[210,"Directory # 8 V4","System Restoration","R1.2.","YES","Address the priority of restoring off-site power to nuclear plants;","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[211,"Directory # 8 V4","System Restoration","R1.3.","YES","Identify interconnection points with adjacent Reliability Coordinator areas;","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[212,"Directory # 8 V4","System Restoration","R1.4.","YES","Identify parameters to synchronize adjacent basic minimum power systems;","2018-09-25",null,"Effective","Yes","GOP, GO, TOP, BA, TO, RC"]
[213,"Directory # 8 V4","System Restoration","R1.5.","YES","Address coordination of system restoration with neighboring Reliability Coordinator areas;","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[214,"Directory # 8 V4","System Restoration","R1.6.","YES","Provide for the re-energization of transmission systems to major generating stations, including inter-area tie points;","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[215,"Directory # 8 V4","System Restoration","R1.7.","YES","Address electrical island stabilization;","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[216,"Directory # 8 V4","System Restoration","R1.8.","YES","Identify provisions for fuel resources to support operation of any supplementary generators (e.g., a diesel generator) necessary for operating key facilities consistent with the expected requirements of the Restoration Plan.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[263,"Directory # 8 V4","System Restoration","R10.",null,"Each functional entity shall test its backup power supplies identified as critical components as specified below. Where there are separate backup power arrangements at a key facility for transmission or generating station equipment and telecommunication equipment, they shall be separately identified in the critical components list and shall be inspected and tested individually.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[218,"Directory # 8 V4","System Restoration","R10.1.",null,"Equipment Inspection: A battery and/or battery charger identified as a critical component shall be inspected in accordance with maintenance activities and maintenance intervals specified in PRC-005-Protection System, Automatic Reclosing, and Sudden Pressure Relaying Maintenance. (Reference: Table 1; Test KF-1)","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[219,"Directory # 8 V4","System Restoration","R10.2.",null,"Equipment Verification: A battery and battery charger identified as critical components shall be verified in accordance with maintenance activities and maintenance intervals specified in PRC-005 Protection System, Automatic Reclosing, and Sudden Pressure Relaying Maintenance. (Reference: Table 1; Test KF-2)","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[220,"Directory # 8 V4","System Restoration","R10.3.",null,"Confirm that all Critical Component Loads can be Supplied: The owner of batteries or battery chargers identified as critical components shall confirm that all critical component loads are connected to and can be supplied by the batteries and battery chargers. At least every sixty (60) calendar months, or when modifications are made to the key facility, the functional entity owner shall confirm through its design review or through testing that all critical component loads are connected to and can be sufficiently supplied by the batteries and battery chargers. (Reference: Table 1; Test KF-3)","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[221,"Directory # 8 V4","System Restoration","R10.4.",null,"Startup and Run Test: The owner of a backup power generator identified as a critical component of a key facility, shall perform a monthly startup and run test on that backup power generator for a minimum run time of fifteen (15) minutes. (Reference: Table 1; Test KF-5).\r\nNote: This test also applies to supplemental generation required for blackstart capability and to a control center and telecommunication center backup power generator.","2018-09-25",null,"Effective","Yes","GOP, GO, TOP, BA, TO, RC"]
[222,"Directory # 8 V4","System Restoration","R10.5.",null,"Startup, Transfer and Load Test: The owner of a backup power generator identified as a critical component of a key facility shall verify that the backup power generator will pick up the critical component load following the loss of station service.\r\n\r\nNote: This test also applies to a control center and telecommunication center backup power generator.\r\nFor automatically started backup power generators, a startup, transfer and run test simulating the loss of station service will be performed every twelve (12) calendar months for a duration of at least thirty (30) minutes. (Reference: Table 1; Test KF-6)\r\nFor manually started backup power generators, the asset owner shall every twelve (12) calendar months start the generator and verify stable operation for thirty (30) minutes while supplying critical component loads. (Reference: Table 1; Test KF-6) Note: Power sources used to start blackstart units will be excluded from test KF-6.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[223,"Directory # 8 V4","System Restoration","R11.",null,"Each functional entity identified as owning key facilities shall test its critical components in the control centers and the telecommunication centers identified as key facilities to demonstrate that the computer systems will be functional when required for system restoration, without dependencies on power sources that may be unavailable during a partial or complete system blackout.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[224,"Directory # 8 V4","System Restoration","R11.1.",null,"AC Supply Interruption Test: The uninterruptible power supply (UPS) systems in control centers and telecommunication centers shall be tested every twelve (12) calendar months by interrupting AC supply and verifying that all critical component loads are supplied for a time that is sufficient for backup power sources to restore the AC input to the UPS. (Reference: Table 1; Test CC-1)","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[225,"Directory # 8 V4","System Restoration","R11.2.",null,"Computer Redundancy (SCADA/EMS) Test\n     Each functional entity identified as owning a key facility shall test its computer redundancy (SCADA/EMS) features every six (6) calendar months to ensure computer systems (SCADA/EMS) continue to function adequately. (Reference: Table 1; Test No. BS-1)","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[226,"Directory # 8 V4","System Restoration","R12.",null,"Each functional entity owning a generating station with blackstart capability shall verify such capability as follows:","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[227,"Directory # 8 V4","System Restoration","R12.1.",null,"Operations voice communications and auxiliary systems such as Supervisory Control and Data Acquisition (SCADA) that are required for blackstart shall be verified at least every twelve (12) calendar months to operate adequately without dependency on the interconnected system or other unrelated unit for any source of station service.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[228,"Directory # 8 V4","System Restoration","R12.2.",null,"A generating station with blackstart capability shall be tested every twelve (12) calendar months for successful equipment startup and energize a transmission element or a generating station switchyard element if that doesn’t involve the disconnection of load that is not dedicated generating station load to conduct the test. Verify stable operation while isolated from the bulk power system for a minimum of ten minutes. (Reference: Table 1; Test BS-1). (Reference: Appendix A-Table 1; Test No. BS-1)","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[229,"Directory # 8 V4","System Restoration","R13.","YES","Reliability Coordinators shall determine the number of units within a generating station that are to be tested for blackstart capability as required by their respective system restoration plans, and shall notify the applicable functional entity.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[230,"Directory # 8 V4","System Restoration","R14.","YES","Each Reliability Coordinator shall confirm that the functional entity owning a generating station with blackstart capability that is part of the basic minimum power system has completed a successful blackstart test consistent with the objectives of the Reliability Coordinator’s system restoration plan.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[231,"Directory # 8 V4","System Restoration","R15.",null,"A functional entity that has confirmed the loss of functionality of a critical component shall report to the Transmission Operator responsible for operating that critical component of that critical component’s loss of functional availability as soon as possible but no longer than 15 minutes after becoming aware of the condition.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[232,"Directory # 8 V4","System Restoration","R15.1.",null,"The Transmission Operator shall report to its Reliability Coordinator as soon as possible but no longer than 15 minutes after the functional entity has made the Transmission Operator aware of the loss of functionality of the critical component.\r\nExamples of such conditions are but not limited to:\r\n• Loss of control of remote equipment;\r\n• Complete loss of AC or DC service supply;\r\n• Loss of blackstart facilities.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[233,"Directory # 8 V4","System Restoration","R16.",null,"A functional entity that has confirmed the loss of redundancy of a critical component shall report to the Transmission Operator responsible for that critical component as soon as possible but no longer than 12 hours after the functional entity’s staff has confirmed the loss of redundancy for the critical component.\r\nExamples of such conditions are:\r\n• Loss of a redundant AC or DC service supply;\r\n• Loss of redundant blackstart critical components.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[234,"Directory # 8 V4","System Restoration","R17.",null,"A functional entity that has scheduled a maintenance condition of a critical component that will result in the loss of functionality of that critical component shall report that maintenance condition to the Transmission Operator responsible for the critical component at least 24 hours prior to that scheduled loss of functionality.\r\nR17.1 The functional entity shall report to the Transmission","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[235,"Directory # 8 V4","System Restoration","R17.1.",null,"The functional entity shall report to the Transmission Operator responsible for the critical component as soon as possible after the loss of functionality has occurred.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[236,"Directory # 8 V4","System Restoration","R17.2.",null,"If the scheduled maintenance condition causing the loss of functionality of a critical component affects the functionality of a key facility, the Transmission Operator responsible for the critical component shall report this scheduled maintenance condition to its Reliability Coordinator.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[237,"Directory # 8 V4","System Restoration","R18.",null,"A functional entity shall report the actions to be taken to restore a critical component’s availability or redundancy to the Transmission Operator responsible for the critical component as soon as known.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[238,"Directory # 8 V4","System Restoration","R18.1.",null,"The functional entity shall report to the Transmission Operator responsible for that critical component the anticipated time that the critical components functionality will be restored.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[239,"Directory # 8 V4","System Restoration","R18.2.",null,"The functional entity shall report to the Transmission Operator responsible for maintaining redundancy for a critical component the anticipated time that the critical component’s redundancy will be restored.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[240,"Directory # 8 V4","System Restoration","R19.",null,"A functional entity shall report the date and time when the functional availability of a critical component is restored to the Transmission Operator responsible for the critical component as soon as known.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[241,"Directory # 8 V4","System Restoration","R2.","YES","In determining the basic minimum power system, the Reliability Coordinator shall involve all affected parties or functional entities.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[242,"Directory # 8 V4","System Restoration","R3.","YES","The Reliability Coordinator shall ensure that the basic minimum power system includes the ability to:","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[243,"Directory # 8 V4","System Restoration","R3.1.","YES","Utilize blackstart generators;","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[244,"Directory # 8 V4","System Restoration","R3.2.","YES","Form an electrical island;","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[245,"Directory # 8 V4","System Restoration","R3.3.","YES","synchronize electrical islands; and","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[246,"Directory # 8 V4","System Restoration","R3.4.","YES","Permit the continuation of the system restoration plan.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[247,"Directory # 8 V4","System Restoration","R4.","YES","Each Reliability Coordinator shall identify key facilities and shall inform each functional entity of its identified key facilities.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[248,"Directory # 8 V4","System Restoration","R5.",null,"Each functional entity identified as the owner of a newly identified or proposed key facility:","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[249,"Directory # 8 V4","System Restoration","R5.1.",null,"Shall identify the associated critical components for that key facility prior to implementation of the proposed facility as a key facility.","2018-09-25",null,"Effective","Yes","GOP, GO, TOP, BA, TO, RC"]
[258,"Directory # 8 V4","System Restoration","R5.2.",null,"Shall provide a list of critical components associated with the proposed key facility upon request of the Reliability Coordinator within the timeframe requested.","2018-09-25",null,"Effective","Yes","GOP, GO, TOP, BA, TO, RC"]
[259,"Directory # 8 V4","System Restoration","R5.3.",null,"Shall ensure that all applicable testing outlined in Appendix A has been successfully completed prior to implementation, or within the timeframe requested by the Reliability Coordinator, of the proposed key facility.","2018-09-25",null,"Effective","Yes","GOP, GO, TOP, BA, TO, RC"]
[260,"Directory # 8 V4","System Restoration","R6.",null,"Each functional entity identified as the owner of an existing key facility:","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[261,"Directory # 8 V4","System Restoration","R6.1.",null,"Shall provide any updates, additions or deletions to the list of critical components for each identified key facility upon request of the Reliability Coordinator within the timeframe requested.","2018-09-25",null,"Effective","Yes","GOP, GO, TOP, BA, TO, RC"]
[262,"Directory # 8 V4","System Restoration","R6.2.",null,"Shall ensure that all applicable testing outlined in Appendix A has been successfully completed for any updated or additional critical components associated with each identified key facility.","2018-09-25",null,"Effective","Yes","BA, TO, RC, GOP, GO, TOP"]
[250,"Directory # 8 V4","System Restoration","R7.","YES","Following the occurrence of an event that required implementation of a system restoration plan and upon request of the Task Force on Coordination of Operation (TFCO):","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[251,"Directory # 8 V4","System Restoration","R7.1.","YES","The Reliability Coordinator shall report on the performance of its plan within the timeframe requested by the TFCO.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[252,"Directory # 8 V4","System Restoration","R7.2.","YES","The Transmission Operator shall report on the performance of its plan within the timeframe requested by the TFCO.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[253,"Directory # 8 V4","System Restoration","R8.",null,"Each functional entity which has been identified as owning a key facility shall:","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[254,"Directory # 8 V4","System Restoration","R8.1.",null,"Perform the tests outlined in Appendix A - Table 1","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[255,"Directory # 8 V4","System Restoration","R8.2.",null,"Maintain records of the test results","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[256,"Directory # 8 V4","System Restoration","R8.3.",null,"Provide evidence, upon request, to the Reliability Coordinator and Transmission Operator within the timeframe requested that the tests specified in sub-Requirement R8.1 have been met.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[257,"Directory # 8 V4","System Restoration","R9.",null,"Each functional entity that owns a cable pressurization system at a key facility shall test for satisfactory operation of both the primary pressurization system and/or the backup pressurization system (if applicable) ability(s) to maintain pressure upon loss of power to the key facility.\r\nThis capability is required during a blackout to maintain the availability of cables for service and to preclude any damage to the cables as a result of the loss of dielectric strength. This test shall be conducted every six (6) calendar months by demonstrating that the required pressures can be maintained for a minimum of thirty (30) minutes.","2018-09-25",null,"Effective","Yes","GOP, GO, TO, BA, TOP, RC"]
[139,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R11",null,"The Generator Owner shall provide generator or generation facility Declared Gross Real Power Capability and Declared Net Real Power Capability to the Transmission Operator.","2017-01-21","2019-07-01","Retired","No"]
[187,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R1.","YES","Developing the List of Generators or Generation Facilities to be verified\nThe Transmission Operator shall develop and maintain documentation of those generators or generation facilities that must verify the Gross Real Power Capability and Net Real Power Capability for the summer and winter capability seasons. The documentation maintained by the Transmission Operator shall include the following:","2017-01-21","2019-07-01","Retired","No"]
[124,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R1.","YES","Developing the List of Generators or Generation Facilities to be verified\nThe Transmission Operator shall develop and maintain documentation of those generators or generation facilities that must verify the Gross Real Power Capability and Net Real Power Capability for the summer and winter capability seasons. The documentation maintained by the Transmission Operator shall include the following:","2017-01-21","2019-07-01","Retired","No"]
[125,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R1.1.","YES","All generators or generation facilities Declared Gross Real Power Capability and Declared Net Real Power Capability.","2017-01-21","2019-07-01","Retired","No","TOP"]
[188,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R1.1.","YES","All generators or generation facilities Declared Gross Real Power Capability and Declared Net Real Power Capability.","2017-01-21","2019-07-01","Retired","No"]
[189,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R1.2.","YES","All generators or generation facilities Verified Gross Real Power Capability and Verified Net Real Power Capability, verification date and method of verification.","2017-01-21","2019-07-01","Retired","No","TOP"]
[126,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R1.2.","YES","All generators or generation facilities Verified Gross Real Power Capability and Verified Net Real Power Capability, verification date and method of verification.","2017-01-21","2019-07-01","Retired","No","TOP"]
[190,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R1.3.","YES","Discrepancies between a Generator Owner’s declared and verified Gross Real Power Capability and Net Real Power Capability, the reason for such discrepancies and the Generator Owner’s plan to address the discrepancies.","2017-01-21","2019-07-01","Retired","No","TOP"]
[127,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R1.3.","YES","Discrepancies between a Generator Owner’s declared and verified Gross Real Power Capability and Net Real Power Capability, the reason for such discrepancies and the Generator Owner’s plan to address the discrepancies.","2017-01-21","2019-07-01","Retired","No","TOP"]
[128,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R1.4.","YES","Generator Owner supplied Gross Real Power Capability and Net Real Power Capability testing, manufacturer data, performance tracking or operating historical data, certification documentation, as specified by the Transmission Operator.","2017-01-21","2019-07-01","Retired","No","TOP"]
[191,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R1.4.","YES","Generator Owner supplied Gross Real Power Capability and Net Real Power Capability testing, manufacturer data, performance tracking or operating historical data, certification documentation, as specified by the Transmission Operator.","2017-01-21","2019-07-01","Retired","No","TOP"]
[192,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R1.5.","YES","All generators or generation facilities exempted from the verification requirements and the basis for their exemption (see Section 1.5)","2017-01-21","2019-07-01","Retired","No","TOP"]
[129,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R1.5.","YES","All generators or generation facilities exempted from the verification requirements and the basis for their exemption (see Section 1.5)","2017-01-21","2019-07-01","Retired","No","TOP"]
[138,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R10.",null,"If a Transmission Operator determines that the difference between the Declared Gross Real Power and Declared Net Real Power Capability of a generator or generation facility is insignificant for NPCC Bulk Power System reliability analysis, then periodic verification will be required for only one numerical value.","2017-01-21","2019-07-01","Retired","No","TOP"]
[140,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R12.",null,"The Generator Owner shall provide evidence, upon request, to the Transmission Operator that the generator or generation facility Gross Real Power Capability and Net Real Power Capability have been verified.","2017-01-21","2019-07-01","Retired","No"]
[141,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R13.",null,"The Generator Owner shall report to the Transmission Operator any discrepancies between declared and verified Gross Real Power Capability or Net Real Power Capability within a time frame specified by the Transmission Operator and develop and implement a plan to resolve the discrepancies.","2017-01-21","2019-07-01","Retired","No","TOP"]
[142,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R14.",null,"The Generator Owner shall determine and report to the Transmission Operator the generator or generation facility real power seasonal auxiliary loads (including common station loads). 1.4 Verification Criteria for Generator and Generation Facility Real Power Capability","2017-01-21","2019-07-01","Retired","No"]
[143,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R15.",null,"The Generator Owner shall comply with Transmission Operator requests for periodic verification of Gross Real Power Capability and Net Real Power Capability of their generators or generation facilities.","2017-01-21","2019-07-01","Retired","No"]
[144,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R16.",null,"The Generator Owner shall verify the Gross Real Power Capability and Net Real Power Capability of thermal generators on the basis of operation for no less than one hour.","2017-01-21","2019-07-01","Retired","No"]
[145,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R16.1.",null,"The verification of thermal generator’s capability shall include any of the following:\n · Testing, \n· Use of operating historical data,\n · Commissioning data (for new generators only),\n· Performance tracking data acquired during the same seasonal capability period.","2017-01-21","2019-07-01","Retired","No"]
[146,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R17.",null,"The Generator Owner shall verify the Gross Real Power Capability and Net Real Power Capability of internal combustion generators and gas turbine generators. The verification shall correspond to operation for no less than one hour under the ambient conditions established in R6 for which the Gross Real Power Capability and Net Real Power Capability are being claimed.","2017-01-21","2019-07-01","Retired","No"]
[147,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R17.1.",null,"The verification of internal combustion and gas turbine generators capability shall include any of the following: \n· Testing, \n· Use of operating historical data, \n· Commissioning data (for new generators only),\n · Performance tracking data acquired during the same seasonal capability period.","2017-01-21","2019-07-01","Retired","No"]
[148,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R18.",null,"The Generator Owner shall verify the Gross Real Power Capability and Net Real Power Capability of hydro generators either on a generation facility or on an individual generator basis. The Gross Real Power Capability and Net Real Power Capability shall be determined on the basis of the availability of sufficient water at an adequate head to provide the output for no less than one hour.","2017-01-21","2019-07-01","Retired","No"]
[149,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R18.1.",null,"The verification of hydro generator’s capability shall include any of the following: \n· Testing, \n· Use of operating historical data, \n· Commissioning data (for new generators only), \n· Performance tracking data acquired during the same seasonal capability period.","2017-01-21","2019-07-01","Retired","No"]
[150,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R19.",null,"The Generator Owner shall verify the Gross Real Power Capability and Net Real Power Capability of combined cycle generators on a generation facility, individual generator or on a generator stage basis for no less than one hour under the ambient conditions established by the Transmission Operator in R6 for which the Gross Real Power Capability and Net Real Power Capability are being claimed.","2017-01-21","2019-07-01","Retired","No"]
[151,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R19.1.",null,"The verification of a combined cycle generator’s capability shall include any of the following: \n· Testing, \n· Use of operating historical data, \n· Commissioning data (for new generators only), \n· Performance tracking data acquired during the same seasonal capability period.","2017-01-21","2019-07-01","Retired","No","TOP"]
[130,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R2.",null,"Establishing the Generator Real Power Capability Verification Program\nThe Transmission Operator shall establish and document a program to periodically verify the Gross Real Power Capability and Net Real Power Capability of all generators and generation facilities that are subject to periodic seasonal Gross Real Power Capability and Net Real Power Capability verification.","2017-01-21","2019-07-01","Retired","No","TOP"]
[152,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R20.",null,"The Generator Owner shall verify the Gross Real Power Capability and Net Real Power Capability of intermittent power resources (wind, solar, tidal geo-thermal, etc.) using any of the following: \n· Manufacturer’s data, \n· Performance tracking, \n· Operating historical data","2017-01-21","2019-07-01","Retired","No"]
[153,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R21.",null,"The Generator Owner shall verify the Gross Real Power Capability and Net Real Power Capability of multiple generator facilities when limited by common elements based on the real power capability of the facility and not the sum of the capabilities of the individual generators.","2017-01-21","2019-07-01","Retired","No","TOP"]
[154,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R22.",null,"The Generator Owner shall identify any equipment or other factor that will limit the capability of the generator or generation facility to meet its Declared Gross Real Power Capability or Declared Net Real Power Capability. 1.5 Exemption of Generators or Generation Facilities from Verification Testing","2017-01-21","2019-07-01","Retired","No","TOP"]
[155,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R23.",null,"The Generator Owner shall notify the Transmission Operator and request an exemption if it cannot conduct seasonal capability testing of a generator or generation facility for any of the reasons listed below. \n· Adverse impact on transmission system reliability \n· Potential damage to transmission system or generator equipment \n· Environment conditions \n· Governmental regulatory or operating license limitations\n · An extended outage to the generator or generation facility","2017-01-21","2019-07-01","Retired","No"]
[156,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R24.","YES","The Transmission Operator shall, within 30 calendar days of receiving notification from a Generator Owner that it is requesting an exemption because it cannot perform verification for the required seasonal period, notify the Generator Owner whether its generator will be exempted from the seasonal capability testing. Where the exemption is approved, the Transmission Operator shall coordinate with the Generator Owner to reschedule the verification for the next seasonal verification period.","2017-01-21","2019-07-01","Retired","No","TOP"]
[196,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R24.","YES","The Transmission Operator shall, within 30 calendar days of receiving notification from a Generator Owner that it is requesting an exemption because it cannot perform verification for the required seasonal period, notify the Generator Owner whether its generator will be exempted from the seasonal capability testing. Where the exemption is approved, the Transmission Operator shall coordinate with the Generator Owner to reschedule the verification for the next seasonal verification period.","2017-01-21","2019-07-01","Retired","No","TOP"]
[157,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R25.",null,"The Generator Owner for a generator or generation facility exempted from seasonal capability testing shall submit the following to the Transmission Operator: \n· For existing generators, generator operation records, manufacturer data, or performance tracking for the previous applicable seasonal verification period for this generator or generation facility. \n· Engineering analysis in conjunction with performance tracking data to justify any difference between a generators or generation facilities declared capability and previous applicable seasonal performance tracking data. \n· For new generators only, commissioning data.","2017-01-21","2019-07-01","Retired","No"]
[193,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R3.","YES","The Transmission Operator shall provide any changes to its verification process to the Generator Owners within 30 calendar days of issue.","2017-01-21","2019-07-01","Retired","No","TOP"]
[131,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R3.","YES","The Transmission Operator shall provide any changes to its verification process to the Generator Owners within 30 calendar days of issue.","2017-01-21","2019-07-01","Retired","No","TOP"]
[194,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R4.","YES","The Transmission Operator shall establish and document requirements for a Generator Owner to notify the Transmission Operator within a specified time period when its generator or generation facility cannot achieve the Declared Gross Real Power Capability or Declared Net Real Power Capability because of equipment issues.","2017-01-21","2019-07-01","Retired","No","TOP"]
[132,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R4.","YES","The Transmission Operator shall establish and document requirements for a Generator Owner to notify the Transmission Operator within a specified time period when its generator or generation facility cannot achieve the Declared Gross Real Power Capability or Declared Net Real Power Capability because of equipment issues.","2017-01-21","2019-07-01","Retired","No","TOP"]
[195,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R5.","YES","The Transmission Operator shall establish and document a time frame for the Generator Owner to address equipment issues that result in a generator or generation facility not achieving the Declared Gross Real Power Capability or Declared Net Real Power Capability.","2017-01-21","2019-07-01","Retired","No"]
[133,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R5.","YES","The Transmission Operator shall establish and document a time frame for the Generator Owner to address equipment issues that result in a generator or generation facility not achieving the Declared Gross Real Power Capability or Declared Net Real Power Capability.","2017-01-21","2019-07-01","Retired","No"]
[134,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R6.",null,"The Transmission Operator shall establish and document the ambient conditions that correspond to the summer and winter capability seasons for which the Gross Real Power Capability and Net Real Power Capability are verified.","2017-01-21","2019-07-01","Retired","No"]
[135,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R7.",null,"The Transmission Operator shall establish and document those intermittent or small generating units whose capability may be represented by verification results of a single generating unit.","2017-01-21","2019-07-01","Retired","No"]
[207,"Directory # 9","Verification of Generator Gross and Net Reactive Power Capability","R7.","YES","The Transmission Operator shall establish and document those intermittent or small generating units whose capability may be represented by verification results of a single generating unit.","2017-01-21","2019-07-01","Retired","No","TOP"]
[136,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R8.",null,"Implementing the Generator Real Power Capability Verification Program\nThe Transmission Operator shall request Generator Owners to verify the seasonal Gross Real Power Capability and Net Real Power Capability of their generators or generation facilities that are subject to periodic seasonal Gross Real Power Capability and Net Real Power Capability verification every three (3) years or more frequently as required by the Transmission Operator. The two (2) capability seasons are defined as summer and winter as specified by the Transmission Operator.","2017-01-21","2019-07-01","Retired","No","TOP"]
[137,"Directory # 9","Verification of Generator Gross and Net Real Power Capability","R9.",null,"If a Transmission Operator determines that only one seasonal generating capability value is required for NPCC Bulk Power System reliability analysis, then periodic verification will be required only for that particular season.","2017-01-21","2019-07-01","Retired","No","TOP"]

{"sheet":"NPCC Paragraph Documents ","index":5,"n_rows":136,"n_cols":41,"rows_kept":136}
["NPCC Criteria or Directory","NPCC Criteria or Directory Name","Paragraph No.","Req'ment No.","Effective or Retired?","Effective Date","Text of Requirement","BA","DP","GO","GOP","IA","LSE","NERC","PA","PC","PSE","RC","RE","RP","RRO","RSC","TO","TOP","TP","TSP","Directory # 1","Directory # 2","Directory # 3","Directory # 4","Directory # 5","Directory # 6","Directory # 7","Directory # 8","Directory # 9","Directory # 10","Directory # 11","Directory # 12","Criterion A-01","Criterion A-10","Criterion A-15"]
["Directory # 4","Bulk Power System Protection Criteria","5.0",{"$f":"VLOOKUP($A2,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C2,LEN($C2)-2)","v":"Dir-4_0"},"Effective","2020-01-30","NPCC Full Member, More Stringent Criteria\n     These Criteria are in addition, more stringent or more specific than the NERC or any Regional Reliability standard requirements.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A2,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A2,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A2,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A2,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A2,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A2,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A2,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A2,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A2,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A2,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A2,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A2,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A2,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria",5.1,{"$f":"VLOOKUP($A3,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C3,LEN($C3)-2)","v":"Dir-4_1"},"Effective","2020-01-30","General Criteria\nThe intent of the criteria established in this Directory is to ensure dependable and secure operation of the protection systems for bulk power system. For those protective relays intended for removal of faults from the bulk power system, dependability is paramount, and the redundancy provisions of the criteria shall apply. For protective relays installed for reasons other than fault sensing such as overload, etc., security is paramount, and the redundancy provisions of the criteria do not apply. The relative effect on the bulk power system of a failure of a protection system to operate when desired versus an unintended operation shall be weighed carefully in selecting design parameters as follows.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A3,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A3,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A3,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A3,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A3,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A3,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A3,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A3,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A3,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A3,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A3,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A3,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A3,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria",5.2,{"$f":"VLOOKUP($A4,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C4,LEN($C4)-2)","v":"Dir-4_2"},"Effective","2020-01-30","Criteria for Dependability",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A4,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A4,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A4,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A4,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A4,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A4,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A4,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A4,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A4,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A4,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A4,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A4,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A4,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.2.1",{"$f":"VLOOKUP($A5,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C5,LEN($C5)-2)","v":"Dir-4_2.1"},"Effective","2020-01-30","Except as identified otherwise in these criteria, all elements of the bulk power system shall 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.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A5,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A5,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A5,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A5,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A5,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A5,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A5,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A5,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A5,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A5,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A5,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A5,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A5,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.2.1.1",{"$f":"VLOOKUP($A6,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C6,LEN($C6)-2)","v":"Dir-4_2.1.1"},"Effective","2020-01-30","The failure of a merging unit shall not lead to the momentary or permanent loss of more than one protection group per element.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.2.2",{"$f":"VLOOKUP($A7,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C7,LEN($C7)-2)","v":"Dir-4_2.2"},"Effective","2020-01-30","Except as identified otherwise in these criteria, the two protection groups shall not share the same component. If the two protection groups share a redundant component in order to achieve improved reliability, the galvanic isolation and physical separation of the two protection groups shall not be compromised. This is to ensure that a single component failure or malfunction will not prevent both protection groups from performing their protective functions.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A7,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A7,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A7,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A7,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A7,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A7,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A7,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A7,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A7,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A7,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A7,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A7,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A7,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.2.2.1",{"$f":"VLOOKUP($A8,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C8,LEN($C8)-2)","v":"Dir-4_2.2.1"},"Effective","2020-01-30","Each protection group shall be supplied from its own DC circuit and that DC circuit shall not be used in any other protection group protecting the same element. Any non-protection control or monitoring circuits shall be supplied from a separately protected DC circuit. Non-protection control or monitoring circuits include but are not limited to closing, reclosing, SCADA, and DME functions.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.2.3",{"$f":"VLOOKUP($A9,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C9,LEN($C9)-2)","v":"Dir-4_2.3"},"Effective","2020-01-30","Means shall be provided to trip all necessary local and remote breakers in the event that a breaker fails to clear a fault. This protection need not be duplicated. If breaker failure protection is duplicated, the exceptions as allowed in 5.12.3 and 5.15.1 for single breaker failure protection do not apply.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A9,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A9,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A9,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A9,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A9,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A9,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A9,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A9,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A9,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A9,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A9,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A9,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A9,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.2.4",{"$f":"VLOOKUP($A10,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C10,LEN($C10)-2)","v":"Dir-4_2.4"},"Effective","2020-01-30","On installations where free-standing or column-type current transformers are provided on one side of the breaker only, resulting in a protection blind spot, protection shall be provided locally to detect faults to ground occurring in the protections’ blind spot area..",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.2.5",{"$f":"VLOOKUP($A11,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C11,LEN($C11)-2)","v":"Dir-4_2.5"},"Effective","2020-01-30","When frame ground protection is used, then frame ground and breaker failure protections are two local independent protections for the blind spot between the current transformer and the circuit breaker. Neither of these protections need be duplicated. Both of these protections shall be designed so as to not be disabled by the same failure. The frame ground protection and breaker failure protection will in fact provide independent protections for the blind spot.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria",5.3,{"$f":"VLOOKUP($A12,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C12,LEN($C12)-2)","v":"Dir-4_3"},"Effective","2020-01-30","Criteria for Security\nProtection systems shall be designed to isolate only the faulted element, except in those circumstances where additional elements are tripped intentionally to preserve system integrity, or where isolating additional elements has no impact outside the local area",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A12,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A12,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A12,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A12,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A12,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A12,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A12,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A12,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A12,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A12,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A12,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A12,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A12,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria",5.4,{"$f":"VLOOKUP($A13,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C13,LEN($C13)-2)","v":"Dir-4_4"},"Effective","2020-01-30","Criteria for Dependability and Security",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A13,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A13,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A13,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A13,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A13,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A13,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A13,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A13,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A13,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A13,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A13,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A13,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A13,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.4.1",{"$f":"VLOOKUP($A14,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C14,LEN($C14)-2)","v":"Dir-4_4.1"},"Effective","2020-01-30","The thermal capability of all protection system components shall be adequate to withstand rated maximum short time and continuous loading of the associated protected elements.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A14,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A14,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A14,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A14,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A14,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A14,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A14,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A14,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A14,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A14,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A14,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A14,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A14,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.4.2",{"$f":"VLOOKUP($A15,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C15,LEN($C15)-2)","v":"Dir-4_4.2"},"Effective","2020-01-30","Position or state of control devices that can disable protections shall be monitored and annunciated to allow prompt attention by appropriate operating authorities. These devices include but are not limited to communication cutoff switches, relay test mode switch, and protection scheme cutoff switches.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A15,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A15,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A15,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A15,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A15,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A15,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A15,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A15,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A15,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A15,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A15,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A15,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A15,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.4.3",{"$f":"VLOOKUP($A16,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C16,LEN($C16)-2)","v":"Dir-4_4.3"},"Effective","2020-01-30","When a Local Area Network (LAN) is used as part of the protection system, relay hardware, network paths, network hardware and merging unit shall be continuously monitored and annunciated for software failure, hardware failure and/or communication failure in order to allow prompt attention by the appropriate operating authorities.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A16,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A16,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A16,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A16,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A16,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A16,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A16,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A16,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A16,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A16,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A16,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A16,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A16,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.4.4",{"$f":"VLOOKUP($A17,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C17,LEN($C17)-2)","v":"Dir-4_4.4"},"Effective","2020-01-30","Short Circuit Models used to assess protection scheme design and to develop protection settings shall take into account minimum and maximum fault levels and mutual effects of parallel transmission lines. Details of neighboring systems shall be modeled wherever they can affect results significantly.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A17,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A17,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A17,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A17,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A17,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A17,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A17,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A17,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A17,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A17,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A17,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A17,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A17,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.4.5",{"$f":"VLOOKUP($A18,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C18,LEN($C18)-2)","v":"Dir-4_4.5"},"Effective","2020-01-30","Protection system components with redundant power supplies shall be powered from the same DC battery system.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.4.6",{"$f":"VLOOKUP($A19,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C19,LEN($C19)-2)","v":"Dir-4_4.6"},"Effective","2020-01-30","Contact outputs used for tripping interrupting devices shall be properly rated to make and carry the DC current for the tripping circuits that they are applied to.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria",5.5,{"$f":"VLOOKUP($A20,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C20,LEN($C20)-2)","v":"Dir-4_5"},"Effective","2020-01-30","Operating Time Criteria\nBulk power system protection shall take corrective action within times determined by studies in accordance with Directory No. 1, Design and Operation of the Bulk Power System.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A20,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A20,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A20,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A20,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A20,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A20,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A20,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A20,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A20,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A20,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A20,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A20,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A20,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria",5.6,{"$f":"VLOOKUP($A21,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C21,LEN($C21)-2)","v":"Dir-4_6"},"Effective","2020-01-30","Current Transformer Criteria\nCurrent transformers (CTs) associated with protection systems shall have adequate steady-state and transient characteristics for their intended function as follows:",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A21,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A21,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A21,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A21,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A21,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A21,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A21,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A21,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A21,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A21,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A21,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A21,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A21,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.6.1",{"$f":"VLOOKUP($A22,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C22,LEN($C22)-2)","v":"Dir-4_6.1"},"Effective","2020-01-30","The output of each current transformer secondary winding shall be designed to remain within acceptable limits for the connected burdens under all anticipated fault currents to ensure correct operation of the protection system.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A22,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A22,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A22,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A22,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A22,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A22,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A22,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A22,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A22,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A22,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A22,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A22,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A22,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.6.2",{"$f":"VLOOKUP($A23,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C23,LEN($C23)-2)","v":"Dir-4_6.2"},"Effective","2020-01-30","The thermal and mechanical capabilities of the CT at the operating tap shall be adequate to prevent damage under maximum fault conditions and normal or emergency system loading conditions.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A23,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A23,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A23,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A23,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A23,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A23,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A23,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A23,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A23,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A23,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A23,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A23,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A23,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.6.3",{"$f":"VLOOKUP($A24,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C24,LEN($C24)-2)","v":"Dir-4_6.3"},"Effective","2020-01-30","For protection groups to be independent, they shall be supplied from separate current transformer secondary windings.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A24,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A24,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A24,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A24,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A24,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A24,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A24,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A24,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A24,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A24,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A24,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A24,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A24,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.6.4",{"$f":"VLOOKUP($A25,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C25,LEN($C25)-2)","v":"Dir-4_6.4"},"Effective","2020-01-30","Interconnected current transformer secondary wiring shall be grounded at only one point.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A25,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A25,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A25,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A25,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A25,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A25,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A25,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A25,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A25,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A25,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A25,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A25,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A25,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.6.5",{"$f":"VLOOKUP($A26,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C26,LEN($C26)-2)","v":"Dir-4_6.5"},"Effective","2020-01-30","Current transformers shall be connected so that adjacent protection zones overlap.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A26,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A26,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A26,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A26,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A26,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A26,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A26,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A26,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A26,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A26,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A26,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A26,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A26,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria",5.7,{"$f":"VLOOKUP($A27,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C27,LEN($C27)-2)","v":"Dir-4_7"},"Effective","2020-01-30","Voltage Transformer and Potential Devices Criteria\nVoltage transformers and potential devices associated with protection systems shall have adequate steady-state and transient characteristics for their intended functions as follows:",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A27,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A27,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A27,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A27,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A27,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A27,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A27,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A27,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A27,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A27,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A27,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A27,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A27,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.7.1",{"$f":"VLOOKUP($A28,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C28,LEN($C28)-2)","v":"Dir-4_7.1"},"Effective","2020-01-30","Voltage transformers and potential devices shall have adequate volt-ampere capacity to supply the connected burden while maintaining their rated accuracy over their specified primary voltage range.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A28,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A28,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A28,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A28,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A28,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A28,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A28,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A28,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A28,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A28,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A28,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A28,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A28,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.7.2",{"$f":"VLOOKUP($A29,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C29,LEN($C29)-2)","v":"Dir-4_7.2"},"Effective","2020-01-30","The two protection groups protecting an element shall be supplied from separate voltage sources. The two protection groups may be supplied from separate secondary windings on one transformer or potential device, provided all of the following requirements are met:",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A29,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A29,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A29,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A29,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A29,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A29,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A29,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A29,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A29,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A29,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A29,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A29,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A29,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.7.2.1",{"$f":"VLOOKUP($A30,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C30,LEN($C30)-2)","v":"Dir-4_7.2.1"},"Effective","2020-01-30","Complete loss of one or more phase voltages does not prevent all tripping of the protected element;",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A30,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A30,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A30,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A30,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A30,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A30,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A30,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A30,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A30,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A30,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A30,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A30,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A30,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.7.2.2",{"$f":"VLOOKUP($A31,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C31,LEN($C31)-2)","v":"Dir-4_7.2.2"},"Effective","2020-01-30","Each secondary winding has sufficient capacity to permit fuse protection of the circuit;",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A31,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A31,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A31,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A31,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A31,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A31,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A31,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A31,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A31,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A31,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A31,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A31,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A31,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.7.2.3",{"$f":"VLOOKUP($A32,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C32,LEN($C32)-2)","v":"Dir-4_7.2.3"},"Effective","2020-01-30","Each secondary winding circuit is adequately fuse protected.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A32,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A32,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A32,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A32,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A32,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A32,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A32,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A32,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A32,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A32,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A32,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A32,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A32,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.7.3",{"$f":"VLOOKUP($A33,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C33,LEN($C33)-2)","v":"Dir-4_7.3"},"Effective","2020-01-30","The wiring from each voltage transformer secondary winding shall not be grounded at more than one point.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A33,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A33,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A33,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A33,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A33,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A33,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A33,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A33,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A33,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A33,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A33,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A33,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A33,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria",5.8,{"$f":"VLOOKUP($A34,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C34,LEN($C34)-2)","v":"Dir-4_8"},"Effective","2020-01-30","Batteries and Direct Current (DC) Supply Criteria\nDC supplies associated with protection shall be designed to have a high degree of dependability as follows:",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A34,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A34,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A34,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A34,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A34,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A34,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A34,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A34,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A34,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A34,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A34,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A34,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A34,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.8.1",{"$f":"VLOOKUP($A35,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C35,LEN($C35)-2)","v":"Dir-4_8.1"},"Effective","2020-01-30","No single battery or DC power supply failure shall prevent both independent protection groups from performing the intended function. Each battery shall be provided with its own charger. Physical separation shall be maintained between the two station batteries or DC power supplies used to supply the independent protection groups.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A35,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A35,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A35,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A35,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A35,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A35,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A35,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A35,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A35,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A35,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A35,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A35,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A35,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.8.2",{"$f":"VLOOKUP($A36,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C36,LEN($C36)-2)","v":"Dir-4_8.2"},"Effective","2020-01-30","Each station battery shall have sufficient capacity to permit operation of the station, in the event of a loss of its battery charger or the ac supply source, for the period of time necessary to transfer the load to the other station battery or re-establish the supply source. Each station battery and its associated charger shall have sufficient capacity to supply the total DC load of the station.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A36,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A36,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A36,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A36,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A36,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A36,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A36,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A36,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A36,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A36,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A36,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A36,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A36,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.8.3",{"$f":"VLOOKUP($A37,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C37,LEN($C37)-2)","v":"Dir-4_8.3"},"Effective","2020-01-30","A transfer arrangement shall be provided to permit connecting the total load to either station battery without creating areas where, prior to failure of either a station battery or a charger, a single event can disable both DC supplies.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A37,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A37,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A37,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A37,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A37,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A37,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A37,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A37,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A37,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A37,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A37,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A37,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A37,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.8.4",{"$f":"VLOOKUP($A38,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C38,LEN($C38)-2)","v":"Dir-4_8.4"},"Effective","2020-01-30","The battery chargers and all DC circuits shall be protected against short circuits. All protective devices shall be coordinated to minimize the number of DC circuits interrupted.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A38,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A38,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A38,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A38,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A38,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A38,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A38,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A38,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A38,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A38,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A38,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A38,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A38,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.8.5",{"$f":"VLOOKUP($A39,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C39,LEN($C39)-2)","v":"Dir-4_8.5"},"Effective","2020-01-30","DC systems shall be continuously monitored and annunciated to detect abnormal voltage levels (both high and low), DC grounds, and loss of ac to the battery chargers, in order to allow prompt attention by the appropriate operating authorities.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A39,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A39,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A39,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A39,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A39,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A39,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A39,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A39,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A39,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A39,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A39,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A39,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A39,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.8.6",{"$f":"VLOOKUP($A40,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C40,LEN($C40)-2)","v":"Dir-4_8.6"},"Effective","2020-01-30","Protection group DC sources shall be continuously monitored to detect loss of voltage in order to allow prompt attention by the appropriate operating authorities.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A40,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A40,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A40,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A40,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A40,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A40,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A40,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A40,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A40,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A40,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A40,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A40,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A40,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria",5.9,{"$f":"VLOOKUP($A41,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C41,LEN($C41)-2)","v":"Dir-4_9"},"Effective","2020-01-30","Station Service ac Supply Criteria\nOn bulk power system facilities there shall be two sources of station service ac supply, each capable of carrying at least all the critical loads associated with protection systems.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A41,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A41,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A41,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A41,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A41,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A41,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A41,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A41,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A41,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A41,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A41,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A41,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A41,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.10",{"$f":"VLOOKUP($A42,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C42,LEN($C42)-2)","v":"Dir-4_10"},"Effective","2020-01-30","Circuit Breaker\n",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A42,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A42,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A42,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A42,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A42,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A42,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A42,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A42,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A42,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A42,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A42,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A42,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A42,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.10.1",{"$f":"VLOOKUP($A43,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C43,LEN($C43)-2)","v":"Dir-4_10.1"},"Effective","2020-01-30","No single trip coil failure shall prevent both independent protection groups from performing the intended function. The design of a breaker with two trip coils shall be such that the breaker will operate if both trip coils are energized simultaneously. The correct operation of this design shall be verified by tests.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.10.2",{"$f":"VLOOKUP($A44,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C44,LEN($C44)-2)","v":"Dir-4_10.2"},"Effective","2020-01-30","Each trip coil shall be monitored in a fail-safe manner for continuity and presence of corresponding DC voltage and annunciated to allow prompt attention by appropriate operating authorities.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.11",{"$f":"VLOOKUP($A45,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C45,LEN($C45)-2)","v":"Dir-4_11"},"Effective","2020-01-30","Teleprotection Criteria\n",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A45,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A45,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A45,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A45,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A45,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A45,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A45,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A45,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A45,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A45,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A45,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A45,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A45,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.11.1",{"$f":"VLOOKUP($A46,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C46,LEN($C46)-2)","v":"Dir-4_11.1"},"Effective","2020-01-30","Communication facilities required for teleprotection shall be designed to have a level of performance consistent with that required of the protection system, and shall meet the following:",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A46,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A46,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A46,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A46,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A46,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A46,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A46,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A46,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A46,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A46,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A46,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A46,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A46,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.11.1.1",{"$f":"VLOOKUP($A47,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C47,LEN($C47)-2)","v":"Dir-4_11.1.1"},"Effective","2020-01-30","Where each of the two protection groups protecting the same bulk power system element requires a communication channel:",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A47,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A47,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A47,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A47,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A47,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A47,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A47,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A47,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A47,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A47,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A47,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A47,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A47,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.11.1.1.1",{"$f":"VLOOKUP($A48,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C48,LEN($C48)-2)","v":"Dir-4_11.1.1.1"},"Effective","2020-01-30","The equipment for each protection group shall be separated physically on non-adjacent panels and designed to minimize the risk of both protection groups being disabled simultaneously by a single event or condition.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.11.1.1.2",{"$f":"VLOOKUP($A49,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C49,LEN($C49)-2)","v":"Dir-4_11.1.1.2"},"Effective","2020-01-30","The communication medium outside the substation physical perimeter for each protection group shall be designed to minimize the risk of both protection groups being disabled simultaneously by a single event or condition. In addition, physical separation of the communication media shall be three feet at a minimum. In cases where constraints do not allow three feet separation, this distance may be reduced if a proposed alternative design can achieve comparable physical protection of the communication medium.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.11.1.2",{"$f":"VLOOKUP($A50,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C50,LEN($C50)-2)","v":"Dir-4_11.1.2"},"Effective","2020-01-30","Teleprotection equipment shall be monitored to detect loss of equipment to allow prompt attention by the appropriate operating authorities.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A50,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A50,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A50,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A50,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A50,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A50,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A50,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A50,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A50,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A50,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A50,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A50,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A50,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.11.1.3",{"$f":"VLOOKUP($A51,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C51,LEN($C51)-2)","v":"Dir-4_11.1.3"},"Effective","2020-01-30","Teleprotection communication channels shall be designed with continuous monitoring and alarming for loss of function to allow prompt attention by appropriate operating authorities. For teleprotection communication channels that utilize ON/OFF signaling that cannot be continuously monitored, the design shall provide daily automated testing for the presence of the channel health and alarming for loss of function to allow prompt attention by appropriate operating authorities.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A51,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A51,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A51,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A51,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A51,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A51,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A51,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A51,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A51,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A51,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A51,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A51,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A51,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.11.1.4",{"$f":"VLOOKUP($A52,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C52,LEN($C52)-2)","v":"Dir-4_11.1.4"},"Effective","2020-01-30","Teleprotection equipment shall be provided with means to test for proper signal adequacy where provisions for automated testing are not provided.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A52,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A52,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A52,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A52,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A52,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A52,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A52,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A52,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A52,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A52,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A52,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A52,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A52,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.11.1.5",{"$f":"VLOOKUP($A53,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C53,LEN($C53)-2)","v":"Dir-4_11.1.5"},"Effective","2020-01-30","Teleprotection equipment shall be powered by the substation batteries or other sources independent from the power system.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A53,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A53,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A53,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A53,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A53,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A53,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A53,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A53,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A53,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A53,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A53,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A53,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A53,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.11.1.6",{"$f":"VLOOKUP($A54,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C54,LEN($C54)-2)","v":"Dir-4_11.1.6"},"Effective","2020-01-30","Except as identified otherwise in these criteria, the two teleprotection groups shall not share the same component.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.11.1.6.1",{"$f":"VLOOKUP($A55,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C55,LEN($C55)-2)","v":"Dir-4_11.1.6.1"},"Effective","2020-01-30","The use of a single communication tower for the radio communication systems used by two protection groups protecting a single element is permitted as long as directional diversity of the communication signals is achieved.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A55,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A55,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A55,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A55,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A55,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A55,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A55,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A55,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A55,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A55,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A55,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A55,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A55,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.12",{"$f":"VLOOKUP($A56,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C56,LEN($C56)-2)","v":"Dir-4_12"},"Effective","2020-01-30","Environment",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A56,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A56,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A56,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A56,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A56,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A56,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A56,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A56,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A56,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A56,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A56,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A56,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A56,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.12.1",{"$f":"VLOOKUP($A57,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C57,LEN($C57)-2)","v":"Dir-4_12.1"},"Effective","2020-01-30","Each separate protection group and teleprotection protecting the same system element shall be on different non-adjacent vertical mounting assemblies or enclosures, except as noted in 5.12.7.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A57,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A57,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A57,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A57,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A57,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A57,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A57,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A57,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A57,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A57,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A57,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A57,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A57,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.12.2",{"$f":"VLOOKUP($A58,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C58,LEN($C58)-2)","v":"Dir-4_12.2"},"Effective","2020-01-30","Protection group LAN devices for redundant protection groups shall be on different non-adjacent vertical mounting assemblies or enclosures, except as noted in 5.12.7.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A58,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A58,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A58,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A58,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A58,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A58,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A58,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A58,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A58,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A58,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A58,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A58,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A58,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.12.3",{"$f":"VLOOKUP($A59,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C59,LEN($C59)-2)","v":"Dir-4_12.3"},"Effective","2020-01-30","Wiring for separate protection groups and teleprotections protecting the same system element shall not be in the same cable or terminated in the same panel. The sole exception is cable termination on single non-redundant breaker failure panels.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A59,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A59,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A59,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A59,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A59,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A59,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A59,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A59,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A59,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A59,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A59,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A59,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A59,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.12.4",{"$f":"VLOOKUP($A60,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C60,LEN($C60)-2)","v":"Dir-4_12.4"},"Effective","2020-01-30","The use of fiber optics for separate protection groups and teleprotections protecting the same system element shall not result in a common mode failure.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A60,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A60,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A60,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A60,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A60,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A60,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A60,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A60,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A60,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A60,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A60,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A60,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A60,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.12.5",{"$f":"VLOOKUP($A61,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C61,LEN($C61)-2)","v":"Dir-4_12.5"},"Effective","2020-01-30","Cabling for separate protection groups and teleprotections protecting the same system element shall be physically separated. This can be accomplished by being in different raceways, trays, trenches, etc. Cable separation shall be achieved up to the breaker control cabinet or equipment control cabinet.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.12.6",{"$f":"VLOOKUP($A62,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C62,LEN($C62)-2)","v":"Dir-4_12.6"},"Effective","2020-01-30","In the event a common raceway is used, cabling for separate protection groups protecting the same element shall be separated by a non-flammable barrier.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.12.7",{"$f":"VLOOKUP($A63,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C63,LEN($C63)-2)","v":"Dir-4_12.7"},"Effective","2020-01-30","Electronic devices physically located outdoor in the substation yard which serve as components of separate protection groups, protecting the same element, shall be physically separated. This can be accomplished by separate enclosures, or by a non-flammable barrier.",null,"DP","GO"]
["Directory # 4","Bulk Power System Protection Criteria","5.12.8",{"$f":"VLOOKUP($A64,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C64,LEN($C64)-2)","v":"Dir-4_12.8"},"Effective","2020-01-30","An electronic device, which serves as a component of a protection group, and is physically located near the primary equipment and outside of the control house, may be subject to more severe environmental conditions than if it was located inside of a building. These environmental conditions may include extreme temperatures, corrosive atmosphere, and electromagnetic interference (EMI). Electronic device selection and secondary enclosure design (“cabinets”) shall ensure that environmental conditions do not reduce protection group reliability and availability and that the electronic devices contained therein are not subject to the environmental conditions above the accepted limits specified by the IEEE or IEC. Any outdoor enclosure shall have as a minimum a NEMA 4X rating for non-EMI related environmental conditions.",null,"DP","GO"]
["Directory # 4","Bulk Power System Protection Criteria","5.13",{"$f":"VLOOKUP($A65,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C65,LEN($C65)-2)","v":"Dir-4_13"},"Effective","2020-01-30","Grounding Criteria\nAn entity shall have established as part of its substation design procedures or specifications, a mandatory method of designing the substation ground grid, which:",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A65,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A65,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A65,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A65,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A65,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A65,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A65,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A65,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A65,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A65,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A65,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A65,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A65,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.13.1",{"$f":"VLOOKUP($A66,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C66,LEN($C66)-2)","v":"Dir-4_13.1"},"Effective","2020-01-30","Can be traced to a recognized calculation methodology",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A66,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A66,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A66,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A66,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A66,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A66,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A66,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A66,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A66,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A66,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A66,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A66,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A66,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.13.2",{"$f":"VLOOKUP($A67,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C67,LEN($C67)-2)","v":"Dir-4_13.2"},"Effective","2020-01-30","Considers cable shielding",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A67,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A67,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A67,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A67,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A67,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A67,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A67,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A67,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A67,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A67,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A67,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A67,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A67,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.13.3",{"$f":"VLOOKUP($A68,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C68,LEN($C68)-2)","v":"Dir-4_13.3"},"Effective","2020-01-30","Considers equipment grounding and its impact on the operation of the live tank frame ground protection.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A68,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A68,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A68,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A68,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A68,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A68,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A68,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A68,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A68,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A68,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A68,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A68,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A68,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.14",{"$f":"VLOOKUP($A69,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C69,LEN($C69)-2)","v":"Dir-4_14"},"Effective","2020-01-30","Transmission Line Protection Criteria",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A69,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A69,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A69,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A69,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A69,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A69,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A69,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A69,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A69,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A69,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A69,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A69,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A69,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.14.1",{"$f":"VLOOKUP($A70,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C70,LEN($C70)-2)","v":"Dir-4_14.1"},"Effective","2020-01-30","Protection system settings shall not constitute a loading limitation as per NERC requirement/standard. In cases where NERC approved exceptions are used the limits thus imposed shall be adhered to as system operating constraints.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A70,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A70,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A70,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A70,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A70,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A70,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A70,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A70,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A70,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A70,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A70,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A70,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A70,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.14.2",{"$f":"VLOOKUP($A71,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C71,LEN($C71)-2)","v":"Dir-4_14.2"},"Effective","2020-01-30","A pilot protection shall be so designed that its failure or misoperation will not affect the operation of any other pilot protection on that same element.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A71,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A71,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A71,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A71,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A71,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A71,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A71,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A71,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A71,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A71,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A71,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A71,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A71,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.15",{"$f":"VLOOKUP($A72,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C72,LEN($C72)-2)","v":"Dir-4_15"},"Effective","2020-01-30","Breaker Failure Protection Criteria\nMeans shall be provided to trip all necessary local and remote breakers in the event that a breaker fails to clear a fault, as follows.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A72,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A72,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A72,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A72,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A72,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A72,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A72,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A72,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A72,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A72,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A72,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A72,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A72,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.15.1",{"$f":"VLOOKUP($A73,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C73,LEN($C73)-2)","v":"Dir-4_15.1"},"Effective","2020-01-30","Non-redundant breaker failure protection shall be initiated by each of the protection groups which trip the breaker, with the optional exception of a breaker failure protection for an adjacent breaker.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A73,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A73,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A73,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A73,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A73,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A73,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A73,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A73,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A73,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A73,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A73,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A73,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A73,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.15.2",{"$f":"VLOOKUP($A74,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C74,LEN($C74)-2)","v":"Dir-4_15.2"},"Effective","2020-01-30","For redundant breaker failure protection, each breaker failure protection shall be initiated only by its respective protection groups which trip the breaker (i.e.: System 1 line protection initiates System 1 breaker failure protection), with the optional exception of a breaker failure protection for an adjacent breaker.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A74,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A74,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A74,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A74,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A74,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A74,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A74,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A74,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A74,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A74,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A74,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A74,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A74,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.15.3",{"$f":"VLOOKUP($A75,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C75,LEN($C75)-2)","v":"Dir-4_15.3"},"Effective","2020-01-30","For redundant breaker failure protections, system 1 breaker failure protection shall only operate system 1 trip coil of the associated backup breakers needed to clear the fault and system 2 breaker failure protection shall only operate system 2 trip coil of the associated backup breakers needed to clear the fault.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.15.4",{"$f":"VLOOKUP($A76,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C76,LEN($C76)-2)","v":"Dir-4_15.4"},"Effective","2020-01-30","Fault current detectors shall be used to determine if a breaker has failed to interrupt a fault current.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.15.5",{"$f":"VLOOKUP($A77,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C77,LEN($C77)-2)","v":"Dir-4_15.5"},"Effective","2020-01-30","A series breaker can be an acceptable means of providing fault clearing for a failed circuit breaker, in lieu of breaker-failure protection. This requires both series breakers be in the same overlapping zones of relay protection, and both series breakers are tripped by these same protection zones.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.16",{"$f":"VLOOKUP($A78,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C78,LEN($C78)-2)","v":"Dir-4_16"},"Effective","2020-01-30","Design to Facilitate Testing and Maintenance",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A78,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A78,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A78,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A78,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A78,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A78,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A78,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A78,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A78,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A78,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A78,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A78,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A78,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.16.1",{"$f":"VLOOKUP($A79,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C79,LEN($C79)-2)","v":"Dir-4_16.1"},"Effective","2020-01-30","The design of protection systems both in terms of circuitry and physical arrangement shall facilitate periodic testing and maintenance.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.16.2",{"$f":"VLOOKUP($A80,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C80,LEN($C80)-2)","v":"Dir-4_16.2"},"Effective","2020-01-30","When a Local Area Network (LAN) is used as part of the protection system, the design shall provide the ability to isolate the operation of protective relaying, while maintaining a network communication path to give personnel the ability to view relay response while under test.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.16.3",{"$f":"VLOOKUP($A81,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C81,LEN($C81)-2)","v":"Dir-4_16.3"},"Effective","2020-01-30","When a Local Area Network (LAN) is used as part of the protection system,the network architecture shall provide a dedicated and secure means for personnel to connect to the LAN for testing, troubleshooting and operational purposes.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.16.4",{"$f":"VLOOKUP($A82,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C82,LEN($C82)-2)","v":"Dir-4_16.4"},"Effective","2020-01-30","Test facilities or test procedures shall be designed such that they do not compromise the independence of the redundant design aspects of the protection systems.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.16.5",{"$f":"VLOOKUP($A83,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C83,LEN($C83)-2)","v":"Dir-4_16.5"},"Effective","2020-01-30","If a segmented testing approach is used, test procedures and test facilities shall be designed to ensure that related tests properly overlap. Proper overlap is ensured if each portion of circuitry is seen to perform its intended function, such as operating a relay from either a real or test stimulus, while observing some common reliable downstream indicator.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.16.6",{"$f":"VLOOKUP($A84,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C84,LEN($C84)-2)","v":"Dir-4_16.6"},"Effective","2020-01-30","When a Local Area Network (LAN) is used as part of the protection system, network monitoring tools shall be deployed to facilitate troubleshooting/corrective maintenance.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.17",{"$f":"VLOOKUP($A85,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C85,LEN($C85)-2)","v":"Dir-4_17"},"Effective","2020-01-30","Design to Facilitate Analysis of Protection System Performance",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A85,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A85,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A85,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A85,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A85,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A85,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A85,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A85,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A85,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A85,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A85,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A85,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A85,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.17.1",{"$f":"VLOOKUP($A86,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C86,LEN($C86)-2)","v":"Dir-4_17.1"},"Effective","2020-01-30","Event recording capability shall be provided to permit analysis of the protection systems’ performance.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A86,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A86,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A86,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A86,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A86,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A86,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A86,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A86,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A86,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A86,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A86,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A86,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A86,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.18",{"$f":"VLOOKUP($A87,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C87,LEN($C87)-2)","v":"Dir-4_18"},"Effective","2020-01-30","Commissioning Testing",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A87,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A87,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A87,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A87,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A87,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A87,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A87,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A87,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A87,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A87,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A87,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A87,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A87,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.18.1",{"$f":"VLOOKUP($A88,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C88,LEN($C88)-2)","v":"Dir-4_18.1"},"Effective","2020-01-30","Each protection group shall be functionally tested to verify the dependability and security aspects of the design, when initially placed in service and when modifications are made.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A88,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A88,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A88,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A88,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A88,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A88,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A88,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A88,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A88,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A88,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A88,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A88,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A88,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.19",{"$f":"VLOOKUP($A89,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C89,LEN($C89)-2)","v":"Dir-4_19"},"Effective","2020-01-30","HVdc System Protection Criteria",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A89,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A89,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A89,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A89,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A89,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A89,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A89,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A89,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A89,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A89,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A89,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A89,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A89,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.19.1",{"$f":"VLOOKUP($A90,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C90,LEN($C90)-2)","v":"Dir-4_19.1"},"Effective","2020-01-30","The ac portion of an HVdc converter station, up to the valve-side terminals of the converter transformers, shall be protected in accordance with these criteria.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A90,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A90,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A90,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A90,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A90,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A90,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A90,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A90,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A90,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A90,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A90,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A90,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A90,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.19.2",{"$f":"VLOOKUP($A91,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C91,LEN($C91)-2)","v":"Dir-4_19.2"},"Effective","2020-01-30","Multiple commutation failures, unordered power reversals, and faults in the converter bridges and the dc portion of the HVdc link which are severe enough to disturb the bulk power system shall be detected by more than one independent control or protection group and appropriate corrective action shall be taken, in accordance with the considerations in these criteria.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A91,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A91,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A91,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A91,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A91,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A91,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A91,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A91,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A91,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A91,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A91,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A91,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A91,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.20",{"$f":"VLOOKUP($A92,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C92,LEN($C92)-2)","v":"Dir-4_20"},"Effective","2020-01-30","Criteria for protection systems utilizing IEC 61850 protocol",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A92,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A92,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A92,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A92,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A92,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A92,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A92,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A92,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A92,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A92,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A92,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A92,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A92,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.20.1",{"$f":"VLOOKUP($A93,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C93,LEN($C93)-2)","v":"Dir-4_20.1"},"Effective","2020-01-30","Loss of one protection group’s sampled value data stream shall not momentarily or permanently compromise the redundant protection group’s sampled value data stream, unless studies demonstrate that the total clearing time including momentary interruption is acceptable.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A93,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A93,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A93,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A93,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A93,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A93,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A93,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A93,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A93,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A93,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A93,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A93,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A93,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.20.2",{"$f":"VLOOKUP($A94,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C94,LEN($C94)-2)","v":"Dir-4_20.2"},"Effective","2020-01-30","If process bus is employed for both protection groups protecting the same element, a single device failure shall not lead to momentary or permanent loss of time synchronization for both protection groups.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A94,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A94,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A94,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A94,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A94,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A94,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A94,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A94,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A94,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A94,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A94,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A94,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A94,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.20.3",{"$f":"VLOOKUP($A95,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C95,LEN($C95)-2)","v":"Dir-4_20.3"},"Effective","2020-01-30","Protection related data shall take priority over other types of data that are transported over the same LAN. LANs used for protection shall be designed such that the protection response shall not be adversely impacted during stressed network conditions. Due to the possibilities for non-protection network traffic such as DME record retrieval, security video streaming, phasor measurements, etc., protection message response time shall meet the critical clearing time requirements in all network loading conditions.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A95,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A95,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A95,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A95,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A95,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A95,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A95,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A95,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A95,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A95,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A95,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A95,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A95,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.20.4",{"$f":"VLOOKUP($A96,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C96,LEN($C96)-2)","v":"Dir-4_20.4"},"Effective","2020-01-30","The actual propagation times through LANs used for protection during stressed network conditions shall be included in the calculation of clearing times of protected element. Network congestion occurs when a link or node is carrying so much data that its quality of service deteriorates. Typical effects include queuing delay, packet loss or the blocking of new connections.",null,"DP","GO",{"$nulls":12},"TO",{"$nulls":3},{"$f":"IF(AA$1=$A96,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A96,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A96,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A96,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A96,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A96,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A96,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A96,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A96,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A96,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A96,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A96,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A96,#REF!,\" \")","v":" "}]
["Directory # 4","Bulk Power System Protection Criteria","5.20.5",{"$f":"VLOOKUP($A97,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C97,LEN($C97)-2)","v":"Dir-4_20.5"},"Effective","2020-01-30","The failure of a single network device shall not momentarily or permanently disable both protection groups, unless studies demonstrate that the total clearing time including momentary interruption2 is acceptable.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.20.6",{"$f":"VLOOKUP($A98,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C98,LEN($C98)-2)","v":"Dir-4_20.6"},"Effective","2020-01-30","The network topology shall be designed in a way that will ensure that a single broken path does not momentarily or permanently disable both protection groups, unless studies demonstrate that the total clearing time including momentary interruption is acceptable.",null,"DP","GO",{"$nulls":12},"TO"]
["Directory # 4","Bulk Power System Protection Criteria","5.20.7",{"$f":"VLOOKUP($A99,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C99,LEN($C99)-2)","v":"Dir-4_20.7"},"Effective","2020-01-30","Analog to digital conversion, processing and communication latency shall maintain a level of speed and accuracy that, at a minimum, meets current utility protection performance.",null,"DP","go",{"$nulls":12},"to"]
["Directory # 12","Underfrequency Load Shedding Program Requirements",5.1,{"$f":"VLOOKUP($A100,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C100,LEN($C100)-2)","v":"Dir-12_1"},"Effective","2017-01-21","Under frequency Load Shedding Program – General Criteria\n     The intent of the NPCC automatic Under frequency Load Shedding program is to ensure that declining frequency is arrested and recovered in accordance with established NPCC performance requirements stipulated in this document, as follows:","BA",null,"GO",{"$nulls":13},"TOP",null,null,{"$f":"IF(AA$1=$A100,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A100,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A100,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A100,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A100,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A100,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A100,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A100,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A100,#REF!,\" \")","v":" "},null,null,{"$f":"IF(AM$1=$A100,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A100,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A100,#REF!,\" \")","v":" "}]
["Directory # 12","Underfrequency Load Shedding Program Requirements","5.1.1",{"$f":"VLOOKUP($A101,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C101,LEN($C101)-2)","v":"Dir-12_1.1"},"Effective",{"$f":"IF($E101=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2017-01-21"},"Frequency decline is arrested at no less than 58.0 Hz for the portions of NPCC in the Eastern Interconnection and 56.0 Hz for the portion of NPCC in the Québec Interconnection.","BA",null,"GO",{"$nulls":13},"TOP",null,null,{"$f":"IF(AA$1=$A101,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A101,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A101,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A101,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A101,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A101,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A101,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A101,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A101,#REF!,\" \")","v":" "},null,null,{"$f":"IF(AM$1=$A101,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A101,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A101,#REF!,\" \")","v":" "}]
["Directory # 12","Underfrequency Load Shedding Program Requirements","5.1.2",{"$f":"VLOOKUP($A102,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C102,LEN($C102)-2)","v":"Dir-12_1.2"},"Effective",{"$f":"IF($E102=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2017-01-21"},"Frequency does not remain below 58.5 Hz for greater than 10 seconds, and does not remain below 59.5 Hz for greater than 30 seconds, for a generation deficiency of up to 25% of the load.","BA",null,"GO",{"$nulls":13},"TOP",null,null,{"$f":"IF(AA$1=$A102,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A102,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A102,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A102,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A102,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A102,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A102,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A102,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A102,#REF!,\" \")","v":" "},null,null,{"$f":"IF(AM$1=$A102,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A102,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A102,#REF!,\" \")","v":" "}]
["Directory # 12","Underfrequency Load Shedding Program Requirements",5.2,{"$f":"VLOOKUP($A103,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C103,LEN($C103)-2)","v":"Dir-12_2"},"Effective",{"$f":"IF($E103=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2017-01-21"},"Under frequency Load Shedding Program – Eastern Interconnection specific Requirements\n     Each Balancing Authority in the NPCC portion of the Eastern Interconnection shall develop an automatic Under frequency Load Shedding Program that meets the following requirements, unless an alternative plan is submitted by the Balancing Authority for review by the NPCC Task Forces on Coordination of Operation and System Studies and approved by the NPCC Reliability Coordinating Committee:","BA",null,"GO",{"$nulls":13},"TOP",null,null,{"$f":"IF(AA$1=$A103,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A103,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A103,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A103,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A103,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A103,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A103,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A103,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A103,#REF!,\" \")","v":" "},null,null,{"$f":"IF(AM$1=$A103,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A103,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A103,#REF!,\" \")","v":" "}]
["Directory # 12","Underfrequency Load Shedding Program Requirements","5.2.1",{"$f":"VLOOKUP($A104,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C104,LEN($C104)-2)","v":"Dir-12_2.1"},"Effective",{"$f":"IF($E104=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2017-01-21"},"The program shall consist of five stages of load shedding to be provided by entities with 100 MW or more of end-use load connected to its facilities with the following attributes:\n\nStage 1:\nThreshold Setting: 59.5 Hz\nBlock Size: 6.5% - 7.5%\nCumulative Load shed as % of TO or DP Load: 6.5% - 7.5%\nTotal Operating Time: 300 ms\n\nStage 2:\nThreshold Setting: 59.3 Hz\nBlock Size: 6.5% - 7.5%\nCumulative Load shed as % of TO or DP Load: 13.5% - 14.5%\nTotal Operating Time: 300 ms\n\nStage 3:\nThreshold Setting: 59.1 Hz\nBlock Size: 6.5% - 7.5%\nCumulative Load shed as % of TO or DP Load: 20.5% - 21.5%\nTotal Operating Time: 300 ms\n\nStage 4:\nThreshold Setting: 58.9 Hz\nBlock Size: 6.5% - 7.5%\nCumulative Load shed as % of TO or DP Load: 27.5% - 28.5%\nTotal Operating Time: 300 ms\n\nStage 5:\nThreshold Setting: 59.5 Hz\nBlock Size: 2% - 3%\nCumulative Load shed as % of TO or DP Load: 29.5% - 31.5%\nTotal Operating Time: 10 ms\n\nNote: Total operating time is the load-weighted average for all load within a Balancing Authority area, with maximum deviation for any load limited to ±50 ms. ","BA",null,"GO",{"$nulls":13},"TOP",null,null,{"$f":"IF(AA$1=$A104,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A104,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A104,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A104,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A104,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A104,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A104,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A104,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A104,#REF!,\" \")","v":" "},null,null,{"$f":"IF(AM$1=$A104,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A104,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A104,#REF!,\" \")","v":" "}]
["Directory # 12","Underfrequency Load Shedding Program Requirements","5.2.2",{"$f":"VLOOKUP($A105,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C105,LEN($C105)-2)","v":"Dir-12_2.2"},"Effective",{"$f":"IF($E105=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2017-01-21"},"The program shall consist of two stages of load shedding to be provided by entities with 50 MW or more and less than 100 MW of end-use load connected to its facilities with the following attributes:\n\nStage 1:\nThreshold Setting: 59.5 Hz\nBlock Size: 14% - 25%\nCumulative Load Shed as % of TO or DP Load: 14% - 25% \nTotal Operating Time  = 300 ms\n\nStage 2:\nThreshold Setting: 59.1 Hz\nBlock Size: 14% - 25%\nCumulative Load Shed as % of TO or DP Load: 28% - 50% \nTotal Operating Time  = 300 ms\n\nNote: Total operating time is the load-weighted average for all load within a Balancing Authority area, with maximum deviation for any load limited to ±50 ms.","BA",null,"GO",{"$nulls":13},"TOP",null,null,{"$f":"IF(AA$1=$A105,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A105,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A105,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A105,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A105,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A105,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A105,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A105,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A105,#REF!,\" \")","v":" "},null,null,{"$f":"IF(AM$1=$A105,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A105,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A105,#REF!,\" \")","v":" "}]
["Directory # 12","Underfrequency Load Shedding Program Requirements","5.2.3",{"$f":"VLOOKUP($A106,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C106,LEN($C106)-2)","v":"Dir-12_2.3"},"Effective",{"$f":"IF($E106=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2017-01-21"},"The program shall consist of one stage of load shedding to be provided by entities with 25 MW or more and less than 50 MW of end-use load connected to its facilities with the following attributes:\n\nStage 1:\nThreshold Setting: 59.5 Hz\nBlock Size: 28% - 50%\nCumulative Load Shed as % of TO or DP Load: 28% - 50% \nTotal Operating Time  = 300 ms\n\nNote: Total operating time is the load-weighted average for all load within a Balancing Authority area, with maximum deviation for any load limited to ±50 ms.","BA",null,"GO",{"$nulls":13},"TOP",null,null,{"$f":"IF(AA$1=$A106,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A106,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A106,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A106,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A106,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A106,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A106,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A106,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A106,#REF!,\" \")","v":" "},null,null,{"$f":"IF(AM$1=$A106,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A106,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A106,#REF!,\" \")","v":" "}]
["Directory # 12","Underfrequency Load Shedding Program Requirements","5.2.4",{"$f":"VLOOKUP($A107,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C107,LEN($C107)-2)","v":"Dir-12_2.4"},"Effective",{"$f":"IF($E107=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2017-01-21"},"Entities with less than 25 MW of end-use load connected to its facilities are exempt from providing UFLS.","BA",null,"GO",{"$nulls":13},"TOP",null,null,{"$f":"IF(AA$1=$A107,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A107,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A107,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A107,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A107,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A107,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A107,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A107,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A107,#REF!,\" \")","v":" "},null,null,{"$f":"IF(AM$1=$A107,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A107,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A107,#REF!,\" \")","v":" "}]
["Directory # 12","Underfrequency Load Shedding Program Requirements","5.2.5",{"$f":"VLOOKUP($A108,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C108,LEN($C108)-2)","v":"Dir-12_2.5"},"Effective",{"$f":"IF($E108=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2017-01-21"},"Entities with less than 100 MW of end-use load connected to its facilities may collectively implement by mutual agreement with one or more entities within the same island (BA shall identify the appropriate island for entities participating in the program) identified an aggregated automatic UFLS program that sheds load based on the frequency thresholds in section 5.2.1 as an alternative to implementing the applicable program in section 5.2.2 or 5.2.3.","BA",null,"GO",{"$nulls":13},"TOP",null,null,{"$f":"IF(AA$1=$A108,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A108,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A108,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A108,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A108,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A108,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A108,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A108,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A108,#REF!,\" \")","v":" "},null,null,{"$f":"IF(AM$1=$A108,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A108,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A108,#REF!,\" \")","v":" "}]
["Directory # 12","Underfrequency Load Shedding Program Requirements","5.2.6",{"$f":"VLOOKUP($A109,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C109,LEN($C109)-2)","v":"Dir-12_2.6"},"Effective",{"$f":"IF($E109=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2017-01-21"},"Under frequency threshold relays shall be set to a nominal total operating time of 300 ms, from the time when frequency passes through the set point to the time of circuit breaker contact opening (including any communications time delay), with a minimum relay operating time to be no less than 100 ms when the rate of frequency decay is 0.2 Hz per second.","BA",null,"GO",{"$nulls":13},"TOP",null,null,{"$f":"IF(AA$1=$A109,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A109,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A109,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A109,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A109,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A109,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A109,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A109,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A109,#REF!,\" \")","v":" "},null,null,{"$f":"IF(AM$1=$A109,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A109,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A109,#REF!,\" \")","v":" "}]
["Directory # 12","Underfrequency Load Shedding Program Requirements","5.3",{"$f":"VLOOKUP($A110,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C110,LEN($C110)-2)","v":"Dir-12_3"},"Effective",{"$f":"IF($E110=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2017-01-21"},"Under frequency Load Shedding Program – Québec Interconnection Specific Requirements\nThe Balancing Authority in the Québec Interconnection shall develop an automatic Under frequency Load Shedding Program that meets the following requirements, unless an alternative plan is submitted by the Balancing Authority for review by the NPCC Task Forces on Coordination of Operation and System Studies and approved by the NPCC Reliability Coordinating Committee:","BA",null,"GO",{"$nulls":13},"TOP",null,null,{"$f":"IF(AA$1=$A110,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A110,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A110,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A110,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A110,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A110,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A110,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A110,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A110,#REF!,\" \")","v":" "},null,null,{"$f":"IF(AM$1=$A110,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A110,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A110,#REF!,\" \")","v":" "}]
["Directory # 12","Underfrequency Load Shedding Program Requirements","5..3.1",{"$f":"VLOOKUP($A111,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C111,LEN($C111)-2)","v":"Dir-12_.3.1"},"Effective",{"$f":"IF($E111=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2017-01-21"},"The program shall consist of five threshold stages and four rate-of-change (slope) stages of load shedding as depicted in Table 2.\n\nTable 2 - UFLS Paramters for the Quebec Interconnection portion of NPCC\nThreshold Stage 1:\nRate: - \nFrequency: 58.5 Hz\nMW at System Peak: 1000 MW (This stage shed fixed independant of system load level)\nMvar at System Peak: 1000 Mvar\nTotal Operating Time: 300 ms\nThreshold Stage 2:\nRate: - \nFrequency: 58.0 Hz\nMW at System Peak: 800 MW (This stage shed fixed independant of system load level)\nMvar at System Peak: 800 Mvar\nTotal Operating Time: 300 ms\nThreshold Stage 3:\nRate: - \nFrequency: 57.5 Hz\nMW at System Peak: 800 MW\nMvar at System Peak: 800 Mvar\nTotal Operating Time: 300 ms\nThreshold Stage 4:\nRate: - \nFrequency: 57.0 Hz\nMW at System Peak: 800 MW\nMvar at System Peak: 800 Mvar\nTotal Operating Time: 300 ms\nThreshold Stage 5(anti-stall):\nRate: - \nFrequency: 59.0 Hz\nMW at System Peak: 500 MW\nMvar at System Peak: 500 Mvar\nTotal Operating Time: 20 ms\nSlope Stage 1:\nRate: - 0.3 Hz/s\nFrequency: 58.5 Hz\nMW at System Peak: 400 MW\nMvar at System Peak: 400 Mvar\nTotal Operating Time: 300 ms\nSlope Stage 2:\nRate: - 0.4 Hz/s\nFrequency: 59.8 Hz\nMW at System Peak: 800 MW (This stage shed fixed independant of system load level)\nMvar at System Peak: 800 Mvar\nTotal Operating Time: 300 ms\nSlope Stage 3:\nRate: - 0.6 Hz/s\nFrequency: 59.8 Hz\nMW at System Peak: 800 MW (This stage shed fixed independant of system load level)\nMvar at System Peak: 800 Mvar\nTotal Operating Time: 300 ms\nSlope Stage 4:\nRate: - 0.9 Hz/s\nFrequency: 59.8 Hz\nMW at System Peak: 800 MW\nMvar at System Peak: 800 Mvar\nTotal Operating Time: 300 ms","BA",null,"GO",{"$nulls":13},"TOP",null,null,{"$f":"IF(AA$1=$A111,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A111,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A111,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A111,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A111,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A111,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A111,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A111,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A111,#REF!,\" \")","v":" "},null,null,{"$f":"IF(AM$1=$A111,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A111,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A111,#REF!,\" \")","v":" "}]
["Directory # 12","Underfrequency Load Shedding Program Requirements",5.4,{"$f":"VLOOKUP($A112,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C112,LEN($C112)-2)","v":"Dir-12_4"},"Effective",{"$f":"IF($E112=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2017-01-21"},"Generator Under frequency Protection Requirements\n     Generators shall not be tripped for under-frequency conditions in the area above the curve in Figure 1, except as provided for in Sections 5.4.1 and 5.4.2.","BA",null,"GO",{"$nulls":13},"TOP",null,null,{"$f":"IF(AA$1=$A112,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A112,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A112,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A112,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A112,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A112,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A112,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A112,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A112,#REF!,\" \")","v":" "},null,null,{"$f":"IF(AM$1=$A112,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A112,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A112,#REF!,\" \")","v":" "}]
["Directory # 12","Underfrequency Load Shedding Program Requirements","5.4.1",{"$f":"VLOOKUP($A113,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C113,LEN($C113)-2)","v":"Dir-12_4.1"},"Effective",{"$f":"IF($E113=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2017-01-21"},"It is recognized that, in special cases, requirements may dictate generator trip in the region above the curve. In those cases, the Generator Owner shall so notify its Balancing Authority and shall ensure through alternate arrangements, that automatic load shedding additional to the amount set out in Section 5.2 and in Section 5.3, equivalent (+/- 5%) to the amount of generation to be tripped, is provided. Such cases shall be reviewed by the Task Force on Coordination of Operation.","BA",null,"GO",{"$nulls":13},"TOP",null,null,{"$f":"IF(AA$1=$A113,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A113,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A113,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A113,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A113,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A113,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A113,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A113,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A113,#REF!,\" \")","v":" "},null,null,{"$f":"IF(AM$1=$A113,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A113,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A113,#REF!,\" \")","v":" "}]
["Directory # 12","Underfrequency Load Shedding Program Requirements","5.4.2",{"$f":"VLOOKUP($A114,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C114,LEN($C114)-2)","v":"Dir-12_4.2"},"Effective",{"$f":"IF($E114=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2017-01-21"},"Generator Owners shall not increase the under frequency trip settings or make other modifications to the existing exempt generators (that trip above the curve in Figure 1) that may cause these generators to, directly or indirectly, trip at a higher frequency.","BA",null,"GO",{"$nulls":13},"TOP",null,null,{"$f":"IF(AA$1=$A114,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A114,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A114,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A114,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A114,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A114,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A114,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A114,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A114,#REF!,\" \")","v":" "},null,null,{"$f":"IF(AM$1=$A114,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A114,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A114,#REF!,\" \")","v":" "}]
["Directory # 12","Underfrequency Load Shedding Program Requirements","5.1",{"$f":"VLOOKUP($A115,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C115,LEN($C115)-2)","v":"Dir-12_1"},"Effective",{"$f":"IF($E115=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2017-01-21"},"UFLS Program Assessment Requirements","BA",null,"GO",{"$nulls":13},"TOP",null,null,{"$f":"IF(AA$1=$A115,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A115,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A115,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A115,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A115,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A115,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A115,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A115,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A115,#REF!,\" \")","v":" "},null,null,{"$f":"IF(AM$1=$A115,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A115,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A115,#REF!,\" \")","v":" "}]
["Directory # 12","Underfrequency Load Shedding Program Requirements","5.5.1",{"$f":"VLOOKUP($A116,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C116,LEN($C116)-2)","v":"Dir-12_5.1"},"Effective",{"$f":"IF($E116=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2017-01-21"},"Studies shall be performed by the associated Transmission Operator to ensure satisfactory voltage and loading conditions after automatic load shedding.","BA",null,"GO",{"$nulls":13},"TOP",null,null,{"$f":"IF(AA$1=$A116,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A116,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A116,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A116,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A116,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A116,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A116,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A116,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A116,#REF!,\" \")","v":" "},null,null,{"$f":"IF(AM$1=$A116,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A116,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A116,#REF!,\" \")","v":" "}]
["Directory # 12","Underfrequency Load Shedding Program Requirements","5.5.2",{"$f":"VLOOKUP($A117,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C117,LEN($C117)-2)","v":"Dir-12_5.2"},"Effective",{"$f":"IF($E117=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2017-01-21"},"The Task Force on System Studies shall conduct a study to coordinate the Automatic Under frequency Load Shedding Program among the NPCC Balancing Authorities, in accordance with the timeline indicated within NERC standard PRC-006-1.","BA",null,"GO",{"$nulls":13},"TOP",null,null,{"$f":"IF(AA$1=$A117,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A117,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A117,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A117,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A117,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A117,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A117,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A117,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A117,#REF!,\" \")","v":" "},null,null,{"$f":"IF(AM$1=$A117,#REF!,\" \")","v":" "},{"$f":"IF(AN$1=$A117,#REF!,\" \")","v":" "},{"$f":"IF(AO$1=$A117,#REF!,\" \")","v":" "}]
["Criterion A-10","Classification of Bulk Power System Elements","3.0",{"$f":"VLOOKUP($A118,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C118,LEN($C118)-2)","v":"A-10_0"},"Effective",{"$f":"IF($E118=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2009-12-01"},"Classification of Bulk Power System Elements",{"$nulls":17},"TP",null,{"$f":"IF(AA$1=$A118,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A118,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A118,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A118,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A118,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A118,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A118,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A118,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A118,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A118,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A118,#REF!,\" \")","v":" "},null,{"$f":"IF(AO$1=$A118,#REF!,\" \")","v":" "}]
["Criterion A-10","Classification of Bulk Power System Elements","3.1",{"$f":"VLOOKUP($A119,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C119,LEN($C119)-2)","v":"A-10_1"},"Effective",{"$f":"IF($E119=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2009-12-01"},"Testing Conditions and Assumptions\n     Studies conducted for the purpose of determining the elements of the bulk power system shall assume the following conditions:",{"$nulls":17},"TP",null,{"$f":"IF(AA$1=$A119,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A119,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A119,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A119,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A119,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A119,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A119,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A119,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A119,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A119,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A119,#REF!,\" \")","v":" "},null,{"$f":"IF(AO$1=$A119,#REF!,\" \")","v":" "}]
["Criterion A-10","Classification of Bulk Power System Elements","3.1.1",{"$f":"VLOOKUP($A120,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C120,LEN($C120)-2)","v":"A-10_1.1"},"Effective",{"$f":"IF($E120=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2009-12-01"},"Power flow transfers, load and generation patterns expected to exist for the period under study which stress the system in a manner critical to the classification of the bus to be tested. All reclosing facilities rendered inoperative.",{"$nulls":17},"TP",null,{"$f":"IF(AA$1=$A120,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A120,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A120,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A120,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A120,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A120,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A120,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A120,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A120,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A120,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A120,#REF!,\" \")","v":" "},null,{"$f":"IF(AO$1=$A120,#REF!,\" \")","v":" "}]
["Criterion A-10","Classification of Bulk Power System Elements","3.1.2",{"$f":"VLOOKUP($A121,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C121,LEN($C121)-2)","v":"A-10_1.2"},"Effective",{"$f":"IF($E121=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2009-12-01"},"Operation of Special Protection Systems, undervoltage load shedding and underfrequency load shedding modeled as designed.",{"$nulls":17},"TP",null,{"$f":"IF(AA$1=$A121,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A121,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A121,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A121,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A121,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A121,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A121,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A121,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A121,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A121,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A121,#REF!,\" \")","v":" "},null,{"$f":"IF(AO$1=$A121,#REF!,\" \")","v":" "}]
["Criterion A-10","Classification of Bulk Power System Elements","3.1.3",{"$f":"VLOOKUP($A122,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C122,LEN($C122)-2)","v":"A-10_1.3"},"Effective",{"$f":"IF($E122=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2009-12-01"},"Load models used in the Transient Stability Test are consistent with Area practices for the studies of rotor angle stability.",{"$nulls":17},"TP",null,{"$f":"IF(AA$1=$A122,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A122,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A122,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A122,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A122,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A122,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A122,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A122,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A122,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A122,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A122,#REF!,\" \")","v":" "},null,{"$f":"IF(AO$1=$A122,#REF!,\" \")","v":" "}]
["Criterion A-10","Classification of Bulk Power System Elements","3.1.4",{"$f":"VLOOKUP($A123,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C123,LEN($C123)-2)","v":"A-10_1.4"},"Effective",{"$f":"IF($E123=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2009-12-01"},"Load models used for steady state testing are either constant MVA or are based on actual system testing with LTC movement.",{"$nulls":17},"TP",null,{"$f":"IF(AA$1=$A123,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A123,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A123,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A123,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A123,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A123,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A123,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A123,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A123,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A123,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A123,#REF!,\" \")","v":" "},null,{"$f":"IF(AO$1=$A123,#REF!,\" \")","v":" "}]
["Criterion A-10","Classification of Bulk Power System Elements","3.1.5",{"$f":"VLOOKUP($A124,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C124,LEN($C124)-2)","v":"A-10_1.5"},"Effective",{"$f":"IF($E124=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2009-12-01"},"Stability simulation runs until the system response can be clearly determined.",{"$nulls":17},"TP",null,{"$f":"IF(AA$1=$A124,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A124,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A124,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A124,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A124,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A124,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A124,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A124,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A124,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A124,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A124,#REF!,\" \")","v":" "},null,{"$f":"IF(AO$1=$A124,#REF!,\" \")","v":" "}]
["Criterion A-10","Classification of Bulk Power System Elements","3.1.6",{"$f":"VLOOKUP($A125,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C125,LEN($C125)-2)","v":"A-10_1.6"},"Effective",{"$f":"IF($E125=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2009-12-01"},"Generic or detailed relay models to monitor, after tripping of remote terminals, the potential for tripping of un-faulted elements.",{"$nulls":17},"TP",null,{"$f":"IF(AA$1=$A125,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A125,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A125,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A125,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A125,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A125,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A125,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A125,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A125,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A125,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A125,#REF!,\" \")","v":" "},null,{"$f":"IF(AO$1=$A125,#REF!,\" \")","v":" "}]
["Criterion A-10","Classification of Bulk Power System Elements","3.2",{"$f":"VLOOKUP($A126,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C126,LEN($C126)-2)","v":"A-10_2"},"Effective",{"$f":"IF($E126=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2009-12-01"},"Test Methodology\n     Both transient stability and steady-state tests are used to determine the impact on system performance resulting from power system faults. \n     Testing is based on application of a bus fault at a single voltage level that is uncleared locally. Tripping of un-faulted elements associated with clearing the test fault does not constitute a significant adverse impact. \n     Depending on system configuration or topology, testing only faults at buses can fail to uncover significant adverse impacts arising from a design criteria contingency involving the loss of two adjacent transmission circuits on a common tower. Hence, specific tests in 1c and 2c below are designed to assess this contingency for its potential significant adverse impact outside of the local area. \n     A transient stability test may be done first to identify buses at which faults may cause a significant adverse impact outside of the local area. \n     For those buses which are not classified as bulk power system in the transient stability test, a steady-state test is used to identify buses at which faults may cause a significant adverse impact outside of the local area.\n\nStep 1 - Transient Stability Test\n     Simulate the transient stability condition of a three-phase fault with delayed clearing at the bus under test (step 1a). If the test results in a positive bulk power system determination, more detailed testing (step 1b) may be applied to obtain a more precise determination.\n1a.  Apply a three-phase fault for at least 10 seconds at the bus that is being tested. Do not open any of the elements connected to the bus for the duration of the fault. After 10 seconds, simulate tripping of all terminals of each element connected to the bus under test. In cases where there is no fault interrupting device at the remote terminal of an element, open all terminals of all elements between the bus under test and the interrupting device(s) that will open to clear the fault. This test is performed as an efficient, but conservative method for evaluating the impacts of:\n• bus faults which would result in faster clearing time, and\n• faults off the bus.\nIt is recognized that due to the conservative nature of this test some elements could be classified unnecessarily as part of the bulk power system. If the above test results in a positive bulk power system determination, the following additional testing may be utilized to obtain a more precise determination. Subsequent testing utilizes design clearing times for the conditions being tested, as stated below.\n",{"$nulls":17},"TP",null,{"$f":"IF(AA$1=$A126,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A126,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A126,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A126,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A126,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A126,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A126,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A126,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A126,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A126,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A126,#REF!,\" \")","v":" "},null,{"$f":"IF(AO$1=$A126,#REF!,\" \")","v":" "}]
["Criterion A-10","Classification of Bulk Power System Elements","3.2",{"$f":"VLOOKUP($A127,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C127,LEN($C127)-2)","v":"A-10_2"},"Effective",{"$f":"IF($E127=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2009-12-01"},"Test Methodology (continued from previous row)\n1b.  Apply a three-phase fault at the bus, which is uncleared locally and trip the remote terminals of all elements that will open to clear the fault. Remote clearing times shall be based on design fault clearing times, assuming no communications from the station under test to the remote terminals. Transformers and other elements connected to the bus shall only be tripped by operation of independent remote protection groups capable of clearing a fault on the bus under test.\nSome protection groups (e.g. directional comparison blocking) at remote terminals may provide high-speed fault clearing for faults at the bus under test. In order to test the effects of longer fault clearing times for fault conditions when these remote protection groups would not provide high speed fault clearing, for either test (1a) or (1b) above:\n• High-speed fault clearing at remote terminals must be ignored; or\n• Testing must vary the placement of the 3-phase fault on the elements connected to the bus under test to include locations beyond the reach of the high-speed tripping relay element at the remote terminal.\nHowever, the protective relay settings may be reviewed to determine whether the bus could be classified as not part of the bulk power system if faster remote fault clearing can be achieved. If protective relay settings are modified, an assessment shall be conducted to ensure that the faster clearing time does not compromise the security of the protection system. Until the protective relay settings are modified, the bus must be classified as bulk power system.\n1c.  The test above is meant to cover the majority of design criteria contingencies. However, the elements associated with the bus under test must be reviewed to ensure adverse consequences resulting from a design criteria contingency involving the loss of two adjacent transmission circuits on a common tower are not overlooked. If a circuit terminating at the bus under test shares a multiple circuit tower with an adjacent circuit that does not terminate at the bus under test, the adjacent circuit design contingency must also be assessed. In such cases, simultaneous permanent phase to ground faults on different phases of each of two adjacent transmission circuits shall be applied at critical common tower locations. The fault on the circuit associated with the bus under test which is uncleared locally, shall be simulated with normal fault clearing at the remote terminal and on the adjacent circuit.\n(Not part of 1c) If the fault has a significant adverse impact outside of the local area, the bus is classified as part of the bulk power system. For buses not classified as part of bulk power system in Step 1, continue with the Steady State Test in step 2.",{"$nulls":17},"TP",null,{"$f":"IF(AA$1=$A127,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A127,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A127,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A127,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A127,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A127,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A127,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A127,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A127,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A127,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A127,#REF!,\" \")","v":" "},null,{"$f":"IF(AO$1=$A127,#REF!,\" \")","v":" "}]
["Criterion A-10","Classification of Bulk Power System Elements","3.2",{"$f":"VLOOKUP($A128,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C128,LEN($C128)-2)","v":"A-10_2"},"Effective",{"$f":"IF($E128=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2009-12-01"},"Test Methodology (continued from previous row)\nStep 2 - Steady State Test\nSimulate the post-contingency steady-state conditions based on one of the following outcomes of the fault applied to the bus under test:\n2a.  If the fault was cleared based on design fault clearing times in the Transient Stability Test, open the same elements that were opened to clear the fault in the Transient Test. Post-contingency conditions shall reflect operation of all automatic devices. \n2b.  If the fault was not cleared based on design fault clearing times in the Transient Stability Test, assume that the fault propagates to the nearest location where it can be detected by independent protection groups and open the elements that would be opened by the protection groups to clear the fault. Note that because fault clearing will occur at interrupting devices capable of clearing the fault, it may be necessary to open multiple elements between the bus under test and the relevant interrupting devices, for example, a transmission line and transformer in series as shown in Figure 2. \n2c.  As in Step 1, the steady state test above is meant to cover the majority of design criteria contingencies. However, the elements associated with the bus under test must be reviewed to ensure adverse consequences resulting from a design criteria contingency involving the loss of two adjacent transmission circuits on a common tower are not overlooked. The post-contingency analysis must assess the loss of any adjacent circuit on common towers with a circuit terminating at the bus under test in addition to the elements associated with the bus under test. \n(Not part of 2c)  Voltages and thermal loading will be assessed for significant adverse impact outside of the local area following automatic actions. In cases where a power flow solution is not obtained, other techniques shall be used to assess the impact of the event on the power system. If the fault has a significant adverse impact outside of the local area, the bus is classified as part of the bulk power system. Note that Step 2 can be done prior to Step 1. If a bus is classified as part of the bulk power system by the Steady State Test (Step 2), the Transient Stability Test (Step 1) need not be done for that bus.",{"$nulls":17},"TP",null,{"$f":"IF(AA$1=$A128,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A128,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A128,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A128,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A128,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A128,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A128,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A128,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A128,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A128,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A128,#REF!,\" \")","v":" "},null,{"$f":"IF(AO$1=$A128,#REF!,\" \")","v":" "}]
["Criterion A-10","Classification of Bulk Power System Elements","3.3",{"$f":"VLOOKUP($A129,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C129,LEN($C129)-2)","v":"A-10_3"},"Effective",{"$f":"IF($E129=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2009-12-01"},"Utilization of Test Results to Classify on an Element-by-Element Basis.\n     Classification of bulk power system elements is achieved by applying the results of the above tests to the elements connected to the tested bus.\n     An element with only one terminal such as a generator, shunt reactor, or capacitor bank, is classified as part of the bulk power system if the bus at which it is connected is classified as part of the bulk power system. \n     An element with multiple terminals such as a transformer or transmission line is classified as part of the bulk power system if any terminal of the element is connected to a bus that is classified as part of the bulk power system. The bulk power system classification may be limited to only a portion of the element if all of the following conditions are met:\n• At least one terminal is connected to a bus that is not part of the bulk power system.\n• The Steady State Test has been applied at the buses connected to all terminals of the element and none of these buses have been classified as part of the bulk power system based on results of the Steady State Test.\n• The Transient Stability Test has been applied between the terminals of the element to identify those portions of the element for which the Transient Stability Test will not result in a significant adverse impact outside of the local area.",{"$nulls":17},"TP",null,{"$f":"IF(AA$1=$A129,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A129,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A129,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A129,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A129,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A129,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A129,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A129,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A129,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A129,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A129,#REF!,\" \")","v":" "},null,{"$f":"IF(AO$1=$A129,#REF!,\" \")","v":" "}]
["Criterion A-10","Classification of Bulk Power System Elements","3.4",{"$f":"VLOOKUP($A130,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C130,LEN($C130)-2)","v":"A-10_4"},"Effective",{"$f":"IF($E130=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2009-12-01"},"Documentation\n     Documentation for Bulk Power System classification shall include:",{"$nulls":17},"TP",null,{"$f":"IF(AA$1=$A130,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A130,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A130,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A130,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A130,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A130,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A130,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A130,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A130,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A130,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A130,#REF!,\" \")","v":" "},null,{"$f":"IF(AO$1=$A130,#REF!,\" \")","v":" "}]
["Criterion A-10","Classification of Bulk Power System Elements","3.4.1",{"$f":"VLOOKUP($A131,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C131,LEN($C131)-2)","v":"A-10_4.1"},"Effective",{"$f":"IF($E131=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2009-12-01"},"The rationale for the test conditions and assumptions used that are not listed above in 3.1.",{"$nulls":17},"TP",null,{"$f":"IF(AA$1=$A131,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A131,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A131,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A131,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A131,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A131,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A131,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A131,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A131,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A131,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A131,#REF!,\" \")","v":" "},null,{"$f":"IF(AO$1=$A131,#REF!,\" \")","v":" "}]
["Criterion A-10","Classification of Bulk Power System Elements","3.4.2",{"$f":"VLOOKUP($A132,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C132,LEN($C132)-2)","v":"A-10_4.2"},"Effective",{"$f":"IF($E132=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2009-12-01"},"The criteria used in evaluating the result of the testing including but not limited to stability, voltage, and thermal performance.",{"$nulls":17},"TP",null,{"$f":"IF(AA$1=$A132,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A132,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A132,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A132,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A132,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A132,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A132,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A132,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A132,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A132,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A132,#REF!,\" \")","v":" "},null,{"$f":"IF(AO$1=$A132,#REF!,\" \")","v":" "}]
["Criterion A-10","Classification of Bulk Power System Elements","3.4.3",{"$f":"VLOOKUP($A133,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C133,LEN($C133)-2)","v":"A-10_4.3"},"Effective",{"$f":"IF($E133=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2009-12-01"},"Detailed result of the testing shall be provided upon request.",{"$nulls":17},"TP",null,{"$f":"IF(AA$1=$A133,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A133,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A133,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A133,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A133,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A133,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A133,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A133,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A133,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A133,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A133,#REF!,\" \")","v":" "},null,{"$f":"IF(AO$1=$A133,#REF!,\" \")","v":" "}]
["Criterion A-10","Classification of Bulk Power System Elements","4.0",{"$f":"VLOOKUP($A134,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C134,LEN($C134)-2)","v":"A-10_0"},"Effective",{"$f":"IF($E134=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2009-12-01"},"Application and List Maintenance\n     Each Area shall be responsible for the application of the Classification of Bulk Power System Elements as described in this document and shall submit proposed changes and supporting documentation to the Task Force on System Studies (TFSS).\n     The “NPCC Bulk Power System List” will be maintained by the TFSS. Additions to and removals from the NPCC Bulk Power System List will be submitted by TFSS to the Reliability Coordinating Committee (RCC) for approval.",{"$nulls":17},"TP",null,{"$f":"IF(AA$1=$A134,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A134,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A134,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A134,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A134,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A134,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A134,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A134,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A134,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A134,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A134,#REF!,\" \")","v":" "},null,{"$f":"IF(AO$1=$A134,#REF!,\" \")","v":" "}]
["Criterion A-10","Classification of Bulk Power System Elements","4.1",{"$f":"VLOOKUP($A135,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C135,LEN($C135)-2)","v":"A-10_1"},"Effective",{"$f":"IF($E135=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2009-12-01"},"Addition of Elements to the Bulk Power System List \n     When application of this methodology identifies an element that was not part of the bulk power system should be classified as a bulk power system element, documentation of the analysis shall be presented to the TFSS. Once classification of the element is recommended by TFSS and approved by the RCC the element will be added to the NPCC Bulk Power System List with the appropriate comments and information. All task forces and the Compliance Committee will be notified once an element is approved by the RCC to be added to the Bulk Power System List. Within three months of an element being added to the Bulk Power System List, a plan and schedule for achieving compliance shall be provided to TFSP for review and acceptance. TFSP may require modifications to the proposed plan and schedule.",{"$nulls":17},"TP",null,{"$f":"IF(AA$1=$A135,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A135,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A135,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A135,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A135,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A135,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A135,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A135,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A135,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A135,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A135,#REF!,\" \")","v":" "},null,{"$f":"IF(AO$1=$A135,#REF!,\" \")","v":" "}]
["Criterion A-10","Classification of Bulk Power System Elements","4.2",{"$f":"VLOOKUP($A136,'[2]Effective Dates & Stewards'!$B$3:$C$17,2,FALSE)&RIGHT($C136,LEN($C136)-2)","v":"A-10_2"},"Effective",{"$f":"IF($E136=\"Retired\",\" \",VLOOKUP(A:A,'[2]Effective Dates & Stewards'!B$3:D$17,3,FALSE))","v":"2009-12-01"},"Removal of Elements from the Bulk Power System List \n     When application of this methodology identifies a bulk power system element that no longer should be classified as a bulk power system element, documentation of the analysis shall be submitted to the TFSS. If reclassification of the element is recommended by TFSS and approved by the RCC, the element will be removed from the NPCC Bulk Power System List.",{"$nulls":17},"TP",null,{"$f":"IF(AA$1=$A136,#REF!,\" \")","v":" "},{"$f":"IF(AB$1=$A136,#REF!,\" \")","v":" "},{"$f":"IF(AC$1=$A136,#REF!,\" \")","v":" "},null,{"$f":"IF(AE$1=$A136,#REF!,\" \")","v":" "},{"$f":"IF(AF$1=$A136,#REF!,\" \")","v":" "},{"$f":"IF(AG$1=$A136,#REF!,\" \")","v":" "},{"$f":"IF(AH$1=$A136,#REF!,\" \")","v":" "},{"$f":"IF(AI$1=$A136,#REF!,\" \")","v":" "},{"$f":"IF(AJ$1=$A136,#REF!,\" \")","v":" "},null,{"$f":"IF(AL$1=$A136,#REF!,\" \")","v":" "},{"$f":"IF(AM$1=$A136,#REF!,\" \")","v":" "},null,{"$f":"IF(AO$1=$A136,#REF!,\" \")","v":" "}]