Status Standard Version Purpose Implementation Plan

Inactive 12/19/2012 4/1/2014 6/30/2016

To control Interconnection frequency within defined limits. 08/15/2013 7/1/2016

To maintain Interconnection steady-state frequency within defined limits. 08/15/2013 4/1/2014

Inactive 08/05/2010 4/1/2012 12/31/2017

Inactive 11/07/2012 2/17/2017

Inactive 11/5/2015 12/31/2017

8/10/2017 1/1/2018

Inactive 11/07/2012 10/1/2014 1/23/2017

11/2/2016 1/24/2017

2/7/2013 11/13/2015

Title (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

BAL-001-1 Real Power Balancing Control Performance To maintain Interconnection steady-state frequency within defined limits by balancing real power demand and supply in real-time.

Mandatory Subject to

EnforcementBAL-001-2 Real Power Balancing Control Performance Implementation Plan

Mandatory Subject to

EnforcementBAL-001-TRE-1 Primary Frequency Response in the ERCOT Region Implementation Plan

BAL-002-1 Disturbance Control Performance

The purpose of the Disturbance Control Standard (DCS) is to ensure the Balancing Authority is able to utilize its Contingency Reserve to balance resources and demand and return Interconnection frequency within defined limits following a Reportable Disturbance. Because generator failures are far more common than significant losses of load and because Contingency Reserve activation does not typically apply to the loss of load, the application of DCS is limited to the loss of supply and does not apply to the loss of load.

Implementation Plan

BAL-002-1a Disturbance Control Performance

The purpose of the Disturbance Control Standard (DCS) is to ensure the Balancing Authority is able to utilize its Contingency Reserve to balance resources and demand and return Interconnection frequency within defined limits following a Reportable Disturbance. Because generator failures are far more common than significant losses of load and because Contingency Reserve activation does not typically apply to the loss of load, the application of DCS is limited to the loss of supply and does not apply to the loss of load.

Implementation Plan

BAL-002-2 Disturbance Control Standard – Contingency Reserve for Recovery from a Balancing Contingency EventTo ensure the Balancing Authority or Reserve Sharing Group balances resources and demand and returns the Balancing Authority's or Reserve Sharing Group's Area Control Error to defined values (subject to applicable limits) following a Reportable Balancing Contingency Event.

Implementation Plan

Mandatory Subject to

EnforcementBAL-002-2(i) Disturbance Control Standard – Contingency Reserve for Recovery from a Balancing Contingency Event

To ensure the Balancing Authority or Reserve Sharing Group balances resources and demand and returns the Balancing Authority's or Reserve Sharing Group's Area Control Error to defined values (subject to applicable limits) following a Reportable Balancing Contingency Event.

Implementation Plan

BAL-002-WECC-2 Contingency Reserve To specify the quantity and types of Contingency Reserve required to ensure reliability under normal and abnormal conditions. Implementation Plan

Mandatory Subject to

EnforcementBAL-002-WECC-2a Contingency Reserve To specify the quantity and types of Contingency Reserve required to ensure reliability under

normal and abnormal conditions. Implementation Plan

Mandatory Subject to

EnforcementBAL-003-1.1 Frequency Response and Frequency Bias Setting

To require sufficient Frequency Response from the Balancing Authority (BA) to maintain Interconnection Frequency within predefined bounds by arresting frequency deviations and supporting frequency until the frequency is restored to its scheduled value. To provide consistent methods for measuring Frequency Response and determining the Frequency Bias Setting.

Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

Inactive 2/8/2005 6/18/2007 4/1/2017

12/19/2012 4/1/2014 9/30/2018

2/8/2018 10/1/2018

3/8/2012 9/13/2012 12/31/2018

2/11/2016 1/1/2019

11/5/2009 4/1/2011 12/31/2018

8/10/2017 1/1/2018

Inactive 8/5/2009 5/23/2011 12/31/2017

BAL-004-0 Time Error Correction The purpose of this standard is to ensure that Time Error Corrections are conducted in a manner that does not adversely affect the reliability of the Interconnection. Implementation Plan

Mandatory Subject to

EnforcementBAL-004-WECC-02 Automatic Time Error Correction

To maintain Interconnection frequency and to ensure that Time Error Corrections and Primary Inadvertent Interchange (PII) payback are effectively conducted in a manner that does not adversely affect the reliability of the Interconnection.

Subject to Future Enforcement BAL-004-WECC-3 Automatic Time Error Correction To maintain Interconnection frequency and to ensure that Time Error Corrections and Primary

Inadvertent Interchange (PII) payback are effectively conducted in a manner that does not adversely affect the reliability of the Interconnection.

Implementation Plan

Mandatory Subject to

EnforcementBAL-005-0.2b Automatic Generation Control

This standard establishes requirements for Balancing Authority Automatic Generation Control (AGC) necessary to calculate Area Control Error (ACE) and to routinely deploy the Regulating Reserve. The standard also ensures that all facilities and load electrically synchronized to the Interconnection are included within the metered boundary of a Balancing Area so that balancing of resources and demand can be achieved.

Implementation Plan

Subject to Future Enforcement BAL-005-1 Balancing Authority Control

This standard establishes requirements for acquiring data necessary to calculate Reporting Area Control Error (Reporting ACE). The standard also specifies a minimum periodicity, accuracy, and availability requirement for acquisition of the data and for providing the information to the System Operator.

Implementation Plan

Mandatory Subject to

EnforcementBAL-006-2 Inadvertent Interchange

This standard defines a process for monitoring Balancing Authorities to ensure that, over the long term, Balancing Authority Areas do not excessively depend on other Balancing Authority Areas in the Interconnection for meeting their demand or Interchange obligations.

Implementation Plan

Mandatory Subject to

EnforcementBAL-502-RF-03 Planning Resource Adequacy Analysis, Assessment and Documentation

To establish common criteria, based on “one day in ten year” loss of Loadexpectation principles, for the analysis, assessment and documentation of Resource Adequacy for Load in the ReliabilityFirst Corporation (RF) region

BAL-502-RFC-02 Planning Resource Adequacy Analysis, Assessment and Documentation To establish common criteria, based on “one day in ten year” loss of Load expectation principles, for the analysis, assessment and documentation of Resource Adequacy for Load in the ReliabilityFirst Corporation (RFC) region.

Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

Inactive 12/16/2009 10/1/2010 6/30/2016

Inactive 2/7/2013 6/30/2016

Inactive 9/27/2013 7/1/2016 12/26/2016

CIP-002-3 Cyber Security — Critical Cyber Asset Identification

NERC Standards CIP-002-3 through CIP-009-3 provide a cyber security framework for the identification and protection of Critical Cyber Assets to support reliable operation of the Bulk Electric System.These standards recognize the differing roles of each entity in the operation of the Bulk Electric System, the criticality and vulnerability of the assets needed to manage Bulk Electric System reliability, and the risks to which they are exposed. Business and operational demands for managing and maintaining a reliable Bulk Electric System increasingly rely on Cyber Assets supporting critical reliability functions and processes to communicate with each other, across functions and organizations, for services and data. This results in increased risks to these Cyber Assets.Standard CIP-002-3 requires the identification and documentation of the Critical Cyber Assets associated with the Critical Assets that support the reliable operation of the Bulk Electric System. These Critical Assets are to be identified through the application of a risk-based assessment.

Implementation Plan

CIP-002-3b Cyber Security — Critical Cyber Asset Identification

NERC Standards CIP-002-3 through CIP-009-3 provide a cyber security framework for the identification and protection of Critical Cyber Assets to support reliable operation of the Bulk Electric System.These standards recognize the differing roles of each entity in the operation of the Bulk Electric System, the criticality and vulnerability of the assets needed to manage Bulk Electric System reliability, and the risks to which they are exposed. Business and operational demands for managing and maintaining a reliable Bulk Electric System increasingly rely on Cyber Assets supporting critical reliability functions and processes to communicate with each other, across functions and organizations, for services and data. This results in increased risks to these Cyber Assets.Standard CIP-002-3 requires the identification and documentation of the Critical Cyber Assets associated with the Critical Assets that support the reliable operation of the Bulk Electric System. These Critical Assets are to be identified through the application of a risk-based assessment.

Implementation Plan

CIP-002-5.1 Cyber Security — BES Cyber System Categorization

To identify and categorize BES Cyber Systems and their associated BES Cyber Assets for the application of cyber security requirements commensurate with the adverse impact that loss, compromise, or misuse of those BES Cyber Systems could have on the reliable operation of the BES. Identification and categorization of BES Cyber Systems support appropriate protection against compromises that could lead to misoperation or instability in the BES.

Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

11/2/2016 12/27/2016

Inactive 12/16/2009 10/1/2010 6/30/2016

Inactive 11/7/2013 6/30/2016 Implementation Plan

Inactive 11/26/2012 6/30/2016

2/12/2015 7/1/2016 12/31/2019

2/9/2017 1/1/2020

Inactive 5/24/2012 12/12/2012 6/30/2016

Inactive 9/27/2013 6/30/2016

2/12/2015 7/1/2016

Mandatory Subject to

EnforcementCIP-002-5.1a Cyber Security - BES Cyber System Categorization

To identify and categorize BES Cyber Systems and their associated BES Cyber Assets for the application of cyber security requirements commensurate with the adverse impact that loss, compromise, or misuse of those BES Cyber Systems could have on the reliable operation of the BES. Identification and categorization of BES Cyber Systems support appropriate protection against compromises that could lead to misoperation or instability in the BES.

Implementation Plan

CIP-003-3 Cyber Security — Security Management ControlsStandard CIP-003-3 requires that Responsible Entities have minimum security management controls in place to protect Critical Cyber Assets. Standard CIP-003-3 should be read as part of a group of standards numbered Standards CIP-002-3 through CIP-009-3.

Implementation Plan

CIP-003-3a Cyber Security — Security Management ControlsStandard CIP-003-3 requires that Responsible Entities have minimum security management controls in place to protect Critical Cyber Assets. Standard CIP-003-3 should be read as part of a group of standards numbered Standards CIP-002-3 through CIP-009-3.

CIP-003-5 Cyber Security — Security Management ControlsTo specify consistent and sustainable security management controls that establish responsibility and accountability to protect BES Cyber Systems against compromise that could lead to misoperation or instability in the BES.

Implementation Plan

Mandatory Subject to

EnforcementCIP-003-6 Cyber Security — Security Management Controls

To specify consistent and sustainable security management controls that establish responsibility and accountability to protect BES Cyber Systems against compromise that could lead to misoperation or instability in the Bulk Electric System (BES).

Implementation Plan

Subject to Future Enforcement CIP-003-7 Cyber Security — Security Management Controls

To specify consistent and sustainable security management controls that establish responsibility and accountability to protect BES Cyber Systems against compromise that could lead to misoperation or instability in the Bulk Electric System (BES).

Implementation Plan

CIP-004-3a Cyber Security — Personnel & Training

Standard CIP-004-3 requires that personnel having authorized cyber or authorized unescorted physical access to Critical Cyber Assets, including contractors and service vendors, have an appropriate level of personnel risk assessment, training, and security awareness. Standard CIP-004-3 should be read as part of a group of standards numbered Standards CIP-002-3 through CIP-009-3.

Implementation Plan

CIP-004-5.1 Cyber Security — Personnel & TrainingTo minimize the risk against compromise that could lead to misoperation or instability in the BES from individuals accessing BES Cyber Systems by requiring an appropriate level of personnel risk assessment, training, and security awareness in support of protecting BES Cyber Systems.

Implementation Plan

Mandatory Subject to

EnforcementCIP-004-6 Cyber Security — Personnel & Training

To minimize the risk against compromise that could lead to misoperation or instability in the Bulk Electric System (BES) from individuals accessing BES Cyber Systems by requiring an appropriate level of personnel risk assessment, training, and security awareness in support of protecting BES Cyber Systems.

Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

Inactive 2/16/2010 2/2/2011 6/30/2016

11/26/2012 7/1/2016

8/10/2017

Inactive 2/16/2010 5/19/2011 6/30/2016

Inactive 11/26/2012 6/30/2016

11/13/2014 7/1/2016

Inactive 12/16/2009 10/1/2010 6/30/2016

Inactive 11/7/2013 6/30/2016

Inactive 11/26/2012 6/30/2016

2/12/2015 7/1/2016

CIP-005-3a Cyber Security — Electronic Security Perimeter(s)Standard CIP-005-3 requires the identification and protection of the Electronic Security Perimeter(s) inside which all Critical Cyber Assets reside, as well as all access points on the perimeter. Standard CIP-005-3 should be read as part of a group of standards numbered Standards CIP-002-3 through CIP-009-3.

Implementation Plan

Mandatory Subject to

EnforcementCIP-005-5 Cyber Security — Electronic Security Perimeter(s)

To manage electronic access to BES Cyber Systems by specifying a controlled Electronic Security Perimeter in support of protecting BES Cyber Systems against compromise that could lead to misoperation or instability in the BES.

Implementation Plan

Filed and Pending Regulatory Approval

CIP-005-6 Cyber Security - Electronic Perimeter(s)To manage electronic access to BES Cyber Systems by specifying acontrolled Electronic Security Perimeter in support of protecting BES Cyber Systemsagainst compromise that could lead to misoperation or instability in the BES.

Implementation Plan

CIP-006-3c Cyber Security — Physical Security of Critical Cyber AssetsStandard CIP-006-3 is intended to ensure the implementation of a physical security program for the protection of Critical Cyber Assets. Standard CIP-006-3 should be read as part of a group of standards numbered Standards CIP-002-3 through CIP-009-3.

Implementation Plan

CIP-006-5 Cyber Security — Physical Security of BES Cyber SystemsTo manage physical access to BES Cyber Systems by specifying a physical security plan in support of protecting BES Cyber Systems against compromise that could lead to misoperation or instability in the BES.

Implementation Plan

Mandatory Subject to

EnforcementCIP-006-6 Cyber Security — Physical Security of BES Cyber Systems

To manage physical access to Bulk Electric System (BES) Cyber Systems by specifying a physical security plan in support of protecting BES Cyber Systems against compromise that could lead to misoperation or instability in the BES.

Implementation Plan

CIP-007-3a Cyber Security — Systems Security ManagementStandard CIP-007-3 requires Responsible Entities to define methods, processes, and procedures for securing those systems determined to be Critical Cyber Assets, as well as the other (non-critical) Cyber Assets within the Electronic Security Perimeter(s). Standard CIP-007-3 should be read as part of a group of standards numbered Standards CIP-002-3 through CIP-009-3.

Implementation Plan

CIP-007-3b Cyber Security — Systems Security ManagementStandard CIP-007-3 requires Responsible Entities to define methods, processes, and procedures for securing those systems determined to be Critical Cyber Assets, as well as the other (non-critical) Cyber Assets within the Electronic Security Perimeter(s). Standard CIP-007-3 should be read as part of a group of standards numbered Standards CIP-002-3 through CIP-009-3.

Implementation Plan

CIP-007-5 Cyber Security — System Security ManagementTo manage system security by specifying select technical, operational, and procedural requirements in support of protecting BES Cyber Systems against compromise that could lead to misoperation or instability in the BES.

Implementation Plan

Mandatory Subject to

EnforcementCIP-007-6 Cyber Security — System Security Management

To manage system security by specifying select technical, operational, and procedural requirements in support of protecting BES Cyber Systems against compromise that could lead to misoperation or instability in the Bulk Electric System (BES).

Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

Inactive 12/16/2009 10/1/2010 6/30/2016

11/26/2012 7/1/2016

Inactive 12/16/2009 10/1/2010 6/30/2016

Inactive 11/26/2012 6/30/2016

11/13/2014 7/1/2016

Inactive 11/26/2012 6/30/2016

2/12/2015 7/1/2016

8/10/2017

Inactive 11/26/2012 6/30/2016

2/12/2015 7/1/2016

8/10/2017

CIP-008-3 Cyber Security — Incident Reporting and Response PlanningStandard CIP-008-3 ensures the identification, classification, response, and reporting of Cyber Security Incidents related to Critical Cyber Assets. Standard CIP-008-23 should be read as part of a group of standards numbered Standards CIP-002-3 through CIP-009-3.

Implementation Plan

Mandatory Subject to

EnforcementCIP-008-5 Cyber Security — Incident Reporting and Response Planning To mitigate the risk to the reliable operation of the BES as the result of a Cyber Security

Incident by specifying incident response requirements. Implementation Plan

CIP-009-3 Cyber Security — Recovery Plans for Critical Cyber AssetsStandard CIP-009-3 ensures that recovery plan(s) are put in place for Critical Cyber Assets and that these plans follow established business continuity and disaster recovery techniques and practices. Standard CIP-009-3 should be read as part of a group of standards numbered Standards CIP-002-3 through CIP-009-3.

Implementation Plan

CIP-009-5 Cyber Security — Recovery Plans for BES Cyber Systems To recover reliability functions performed by BES Cyber Systems by specifying recovery plan requirements in support of the continued stability, operability, and reliability of the BES. Implementation Plan

Mandatory Subject to

EnforcementCIP-009-6 Cyber Security — Recovery Plans for BES Cyber Systems To recover reliability functions performed by BES Cyber Systems by specifying recovery plan

requirements in support of the continued stability, operability, and reliability of the BES. Implementation Plan

CIP-010-1 Cyber Security — Configuration Change Management and Vulnerability AssessmentsTo prevent and detect unauthorized changes to BES Cyber Systems by specifying configuration change management and vulnerability assessment requirements in support of protecting BES Cyber Systems from compromise that could lead to misoperation or instability in the BES.

Implementation Plan

Mandatory Subject to

EnforcementCIP-010-2 Cyber Security — Configuration Change Management and Vulnerability Assessments

To prevent and detect unauthorized changes to BES Cyber Systems by specifying configuration change management and vulnerability assessment requirements in support of protecting BES Cyber Systems from compromise that could lead to misoperation or instability in the Bulk Electric System (BES).

Implementation Plan

Filed and Pending Regulatory Approval

CIP-010-3 Cyber Security - Configuration Change Management and VulnerabilityTo prevent and detect unauthorized changes to BES Cyber Systems byspecifying configuration change management and vulnerability assessmentrequirements in support of protecting BES Cyber Systems from compromise thatcould lead to misoperation or instability in the Bulk Electric System (BES).

Implementation Plan

CIP-011-1 Cyber Security — Information ProtectionTo prevent unauthorized access to BES Cyber System Information by specifying information protection requirements in support of protecting BES Cyber Systems against compromise that could lead to misoperation or instability in the BES.

Implementation Plan

Mandatory Subject to

EnforcementCIP-011-2 Cyber Security — Information Protection

To prevent unauthorized access to BES Cyber System Information by specifying information protection requirements in support of protecting BES Cyber Systems against compromise that could lead to misoperation or instability in the Bulk Electric System (BES).

Implementation Plan

Filed and Pending Regulatory Approval

CIP-013-1 Cyber Security - Supply chain Risk ManagementTo mitigate cyber security risks to the reliable operation of the BulkElectric System (BES) by implementing security controls for supply chain riskmanagement of BES Cyber Systems.

Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

Inactive 5/13/2014 10/1/2015 10/1/2015

5/7/2015 10/2/2015

Inactive 10/29/2008 5/13/2009 9/30/2015

Inactive To establish Interpersonal Communication capabilities necessary to maintain reliability. 11/7/2012 11/13/2015 9/30/2017

8/11/2016 10/1/2017

Inactive 11/1/2006 6/18/2007 6/30/2016

Inactive 2/9/2012 6/30/2016

Inactive To ensure Emergency communications between operating personnel are effective. 11/7/2012 6/30/2016

5/7/2014 7/1/2016

Inactive 3/8/2012 7/1/2013 3/31/2017

Inactive 3/8/2012 9/13/2012 3/31/2017

Inactive 11/4/2010 10/1/2013 3/31/2017

CIP-014-1 Physical SecurityTo identify and protect Transmission stations and Transmission substations, and their associated primary control centers, that if rendered inoperable or damaged as a result of a physical attack could result in widespread instability, uncontrolled separation, or Cascading within an Interconnection.

Implementation Plan

Mandatory Subject to

EnforcementCIP-014-2 Physical Security

To identify and protect Transmission stations and Transmission substations, and their associated primary control centers, that if rendered inoperable or damaged as a result of a physical attack could result in instability, uncontrolled separation, or Cascading within an Interconnection.

Implementation Plan

COM-001-1.1 TelecommunicationsEach Reliability Coordinator, Transmission Operator and Balancing Authority needs adequate and reliable telecommunications facilities internally and with others for the exchange of Interconnection and operating information necessary to maintain reliability.

Implementation Plan

COM-001-2.1 Communications Implementation Plan

Mandatory Subject to

EnforcementCOM-001-3 Communications

To establish Interpersonal Communication capabilities necessary to maintain reliability. Implementation Plan

COM-002-2 Communication and CoordinationTo ensure Balancing Authorities, Transmission Operators, and Generator Operators have adequate communications and that these communications capabilities are staffed and available for addressing a real-time emergency condition. To ensure communications by operating personnel are effective.

Implementation Plan

COM-002-2a Communication and CoordinationTo ensure Balancing Authorities, Transmission Operators, and Generator Operators have adequate communications and that these communications capabilities are staffed and available for addressing a real-time emergency condition. To ensure communications by operating personnel are effective.

Implementation Plan

COM-002-3 Communication and Coordination Implementation Plan

Mandatory Subject to

EnforcementCOM-002-4 Operating Personnel Communications Protocols

To improve communications for the issuance of Operating Instructions with predefined communications protocols to reduce the possibility of miscommunication that could lead to action or inaction harmful to the reliability of the Bulk Electric System (BES).

Implementation Plan

EOP-001-2.1b Emergency Operations PlanningEach Transmission Operator and Balancing Authority needs to develop, maintain, and implement a set of plans to mitigate operating emergencies. These plans need to be coordinated with other Transmission Operators and Balancing Authorities, and the Reliability Coordinator.

Implementation Plan

EOP-002-3.1 Capacity and Energy Emergencies To ensure Reliability Coordinators and Balancing Authorities are prepared for capacity and energy emergencies. Implementation Plan

EOP-003-2 Load Shedding PlansA Balancing Authority and Transmission Operator operating with insufficient generation or transmission capacity must have the capability and authority to shed load rather than risk an uncontrolled failure of the Interconnection.

Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

Inactive 11/7/2012 1/1/2014 3/31/2017

11/13/2014 4/1/2017 3/31/2019

2/9/2017 4/1/2019

8/5/2009 7/1/2013 3/31/2019

2/9/2017 4/1/2019

8/5/2009 7/1/2013 3/31/2019

2/9/2017 4/1/2019

8/5/2010 7/1/2013 3/31/2019

2/9/2017 4/1/2019

11/7/2013 4/1/2015

11/13/2014 4/1/2017

EOP-004-2 Event Reporting To improve the reliability of the Bulk Electric System by requiring the reporting of events by Responsible Entities. Implementation Plan

Mandatory Subject to

EnforcementEOP-004-3 Event Reporting To improve the reliability of the Bulk Electric System by requiring the reporting of events by

Responsible Entities. Implementation Plan

Subject to Future Enforcement EOP-004-4 Event Reporting To improve the reliability of the Bulk Electric System by requiring the reporting of events by

Responsible Entities. Implementation Plan

Mandatory Subject to

EnforcementEOP-005-2 System Restoration from Blackstart Resources

Ensure plans, Facilities, and personnel are prepared to enable System restoration from Blackstart Resources to assure reliability is maintained during restoration and priority is placed on restoring the Interconnection.

Implementation Plan

Subject to Future Enforcement EOP-005-3 System Restoration from Blackstart Resources

Ensure plans, Facilities, and personnel are prepared to enable System restoration from Blackstart Resources to ensure reliability is maintained during restoration and priority is placed on restoring the Interconnection.

Implementation Plan

Mandatory Subject to

EnforcementEOP-006-2 System Restoration Coordination

Ensure plans are established and personnel are prepared to enable effective coordination of the System restoration process to ensure reliability is maintained during restoration and priority is placed on restoring the Interconnection.

Implementation Plan

Subject to Future Enforcement EOP-006-3 System Restoration Coordination

Ensure plans are established and personnel are prepared to enable effective coordination of the System restoration process to ensure reliability is maintained during restoration and priority is placed on restoring the Interconnection.

Implementation Plan

Mandatory Subject to

EnforcementEOP-008-1 Loss of Control Center Functionality Ensure continued reliable operations of the Bulk Electric System (BES) in the event that a

control center becomes inoperable. Implementation Plan

Subject to Future Enforcement EOP-008-2 Loss of Control Center Functionality Ensure continued reliable operations of the Bulk Electric System (BES) in the event that a

control center becomes inoperable. Implementation Plan

Mandatory Subject to

EnforcementEOP-010-1 Geomagnetic Disturbance Operations To mitigate the effects of geomagnetic disturbance (GMD) events by implementing Operating

Plans, Processes, and Procedures. Implementation Plan

Mandatory Subject to

EnforcementEOP-011-1 Emergency Operations

To address the effects of operating Emergencies by ensuring each Transmission Operator and Balancing Authority has developed Operating Plan(s) to mitigate operating Emergencies, and that those plans are coordinated within a Reliability Coordinator Area.

Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

8/14/2014 1/1/2016 12/31/2018

2/11/2016 1/1/2019

8/14/2014 1/1/2016

Inactive 5/9/2012 7/1/2014 9/30/2016

2/11/2016 10/1/2016

5/24/2011 1/1/2013

Inactive 11/5/2009 4/19/2010 3/31/2017

11/13/2014 4/1/2017

Inactive 6/24/2008 4/29/2009 3/31/2017

Mandatory Subject to

EnforcementFAC-001-2 Facility Interconnection Requirements

To avoid adverse impacts on the reliability of the Bulk Electric System, Transmission Owners and applicable Generator Owners must document and make Facility interconnection requirements available so that entities seeking to interconnect will have the necessary information.

Implementation Plan

Subject to Future Enforcement FAC-001-3 Facility Interconnection Requirements

To avoid adverse impacts on the reliability of the Bulk Electric System, Transmission Owners and applicable Generator Owners must document and make Facility interconnection requirements available so that entities seeking to interconnect will have the necessary information.

Implementation Plan

Mandatory Subject to

EnforcementFAC-002-2 Facility Interconnection Studies To study the impact of interconnecting new or materially modified Facilities on the Bulk Electric

System. Implementation Plan

FAC-003-3 Transmission Vegetation Management To maintain a reliable electric transmission system by using a defense-in-depth strategy to manage vegetation located on transmission rights of way (ROW) and minimize encroachments from vegetation located adjacent to the ROW, thus preventing the risk of those vegetation-related outages that could lead to Cascading.

Implementation Plan

Mandatory Subject to

EnforcementFAC-003-4 Transmission Vegetation Management

To maintain a reliable electric transmission system by using a defense-in-depth strategy to manage vegetation located on transmission rights of way (ROW) and minimize encroachments from vegetation located adjacent to the ROW, thus preventing the risk of those vegetation-related outages that could lead to Cascading.

Implementation Plan

Mandatory Subject to

EnforcementFAC-008-3 Facility Ratings

To ensure that Facility Ratings used in the reliable planning and operation of the Bulk Electric System (BES) are determined based on technically sound principles. A Facility Rating is essential for the determination of System Operating Limits.

Implementation Plan

FAC-010-2.1 System Operating Limits Methodology for the Planning Horizon To ensure that System Operating Limits (SOLs) used in the reliable planning of the Bulk Electric System (BES) are determined based on an established methodology or methodologies.

Mandatory Subject to

EnforcementFAC-010-3 System Operating Limits Methodology for the Planning Horizon To ensure that System Operating Limits (SOLs) used in the reliable planning of the Bulk Electric

System (BES) are determined based on an established methodology or methodologies. Implementation Plan

FAC-011-2 System Operating Limits Methodology for the Operations Horizon To ensure that System Operating Limits (SOLs) used in the reliable operation of the Bulk Electric System (BES) are determined based on an established methodology or methodologies. Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

11/13/2014 4/1/2017

1/24/2011 4/1/2013

6/24/2008 4/29/2009

Inactive 10/29/2008 7/1/2011 6/30/2018

2/8/2018 7/1/2018

8/20/2014 11/26/2014

2/6/2014 10/1/2014

8/20/2014 11/26/2014

Mandatory Subject to

EnforcementFAC-011-3 System Operating Limits Methodology for the Operations HorizonTo ensure that System Operating Limits (SOLs) used in the reliable operation of the Bulk Electric

System (BES) are determined based on an established methodology or methodologies. Implementation Plan

Mandatory Subject to

EnforcementFAC-013-2 Assessment of Transfer Capability for the Near-Term Transmission Planning Horizon

To ensure that Planning Coordinators have a methodology for, and perform an annual assessment to identify potential future Transmission System weaknesses and limiting Facilities that could impact the Bulk Electric System’s (BES) ability to reliably transfer energy in the Near-Term Transmission Planning Horizon.

Implementation Plan

Mandatory Subject to

EnforcementFAC-014-2 Establish and Communicate System Operating Limits

To ensure that System Operating Limits (SOLs) used in the reliable planning and operation of the Bulk Electric System (BES) are determined based on an established methodology or methodologies.

Implementation Plan

FAC-501-WECC-1 Transmission MaintenanceTo ensure the Transmission Owner of a transmission path identified in the table titled “Major WECC Transfer Paths in the Bulk Electric System” including associated facilities has a Transmission Maintenance and Inspection Plan (TMIP); and performs and documents maintenance and inspection activities in accordance with the TMIP.

Mandatory Subject to

EnforcementFAC-501-WECC-2 Transmission Maintenance

To ensure the Transmission Owner of a transmission path identified in Attachment B, Major WECC Transfer Paths in the Bulk Electric System, including associated facilities has a Transmission Maintenance and Inspection Plan (TMIP); and performs and documents maintenance and inspection activities in accordance with the TMIP.

Implementation Plan

Mandatory Subject to

EnforcementINT-004-3.1 Dynamic Transfers To ensure Dynamic Schedules and Pseudo-Ties are communicated and accounted for

appropriately in congestion management procedures. Implementation Plan

Mandatory Subject to

EnforcementINT-006-4 Evaluation of Interchange Transactions To ensure that responsible entities conduct a reliability assessment of each Arranged

Interchange before it is implemented. Implementation Plan

Mandatory Subject to

EnforcementINT-009-2.1 Implementation of Interchange To ensure that Balancing Authorities implement the Interchange as agreed upon in the

Interchange confirmation process. Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

8/20/2014 11/26/2014 Implementation Plan

Inactive 8/20/2014 11/26/2014 10/15/2015 Implementation Plan

Inactive 10/29/2008 5/13/2009 3/31/2017

Withdrawn 8/16/2012 1/26/2016

To establish the responsibility of Reliability Coordinators to act or direct other entities to act. 11/13/2014 4/1/2017

Inactive 10/17/2008 10/1/2011 3/31/2017

Withdrawn 8/4/2011 1/26/2016

Inactive 11/13/2014 4/1/2017 9/30/2017

2/9/2017 10/1/2017

Inactive 11/1/2006 6/18/2007 3/31/2017

Mandatory Subject to

EnforcementINT-010-2.1 Interchange Initiation and Modification for Reliability To provide guidance for required actions on Confirmed Interchange or Implemented

Interchange to address reliability.

INT-011-1.1 Intra-Balancing Authority Transaction Identification To ensure that transfers within a Balancing Authority Area using Point to Point Transmission Service are communicated and accounted for in congestion management procedures.

IRO-001-1.1 Reliability Coordination — Responsibilities and Authorities

Reliability Coordinators must have the authority, plans, and agreements in place to immediately direct reliability entities within their Reliability Coordinator Areas to re-dispatch generation, reconfigure transmission, or reduce load to mitigate critical conditions to return the system to a reliable state. If a Reliability Coordinator delegates tasks to others, the Reliability Coordinator retains its responsibilities for complying with NERC and regional standards. Standards of conduct are necessary to ensure the Reliability Coordinator does not act in a manner that favors one market participant over another.

Implementation Plan

IRO-001-3 Reliability Coordination – Responsibilities and Authorities To establish the authority of Reliability Coordinators to direct other entities to prevent an Emergency or Adverse Reliability Impacts to the Bulk Electric System. Implementation Plan

Mandatory Subject to

EnforcementIRO-001-4 Reliability Coordination – Responsibilities Implementation Plan

IRO-002-2 Reliability Coordination — Facilities Reliability Coordinators need information, tools and other capabilities to perform their responsibilities.

IRO-002-3 Reliability Coordination – Analysis ToolsTo ensure that Reliability Coordinators provide their System Operators with authority with respect to analysis tool outages and to have procedures to mitigate effects of analysis tool outages.

Implementation Plan

IRO-002-4 Reliability Coordination – Monitoring and Analysis Provide System Operators with the capabilities necessary to monitor and analyze data needed to perform their reliability functions. Implementation Plan

Mandatory Subject to

EnforcementIRO-002-5 Reliability Coordination – Monitoring and Analysis To provide System Operators with the capabilities necessary to monitor and analyze data

needed to perform their reliability functions.Implementation Plan

IRO-003-2 Reliability Coordination — Wide-Area View The Reliability Coordinator must have a wide-area view of its own Reliability Coordinator Area and that of neighboring Reliability Coordinators. Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

Inactive 10/17/2008 10/1/2011 3/31/2017

Inactive 11/13/2014 9/13/2012 3/31/2017

Withdrawn 8/4/2011 1/26/2016

11/4/2010 7/1/2011 Implementation Plan

Inactive 11/4/2010 7/1/2011 3/31/2016 Implementation Plan

8/13/2015 4/1/2016

11/3/2011 7/1/2012

Mitigation of transmission overloads due to unscheduled flow on Qualified Transfer Paths. 2/7/2013 7/1/2014

Inactive 10/17/2008 10/1/2011 3/31/2017

11/13/2014 4/1/2017

IRO-004-2 Reliability Coordination — Operations Planning

Each Reliability Coordinator must conduct next-day reliability analyses for its Reliability Coordinator Area to ensure the Bulk Electric System can be operated reliably in anticipated normal and Contingency conditions. System studies must be conducted to highlight potential interface and other operating limits, including overloaded transmission lines and transformers, voltage and stability limits, etc. Plans must be developed to alleviate System Operating Limit (SOL) and Interconnection Reliability Operating Limit (IROL) violations.

IRO-005-3.1a Reliability Coordination — Current Day OperationsThe Reliability Coordinator must be continuously aware of conditions within its Reliability Coordinator Area and include this information in its reliability assessments. The Reliability Coordinator must monitor Bulk Electric System parameters that may have significant impacts upon the Reliability Coordinator Area and neighboring Reliability Coordinator Areas.

Implementation Plan

IRO-005-4 Reliability Coordination — Current Day Operations To ensure that entities are notified when an expected or actual event with Adverse Reliability Impacts is identified. Implementation Plan

Mandatory Subject to

EnforcementIRO-006-5 Reliability Coordination — Transmission Loading Relief (TLR)

To ensure coordinated action between Interconnections when implementing Interconnection-wide transmission loading relief procedures to prevent or manage potential or actual SOL and IROL exceedances to maintain reliability of the bulk electric system.

IRO-006-EAST-1 Transmission Loading Relief Procedure for the Eastern InterconnectionTo provide an Interconnection-wide transmission loading relief procedure (TLR) for the Eastern Interconnection that can be used to prevent and/or mitigate potential or actual System Operating Limit (SOL) and Interconnection Reliability Operating Limit (IROL) exceedances to maintain reliability of the Bulk Electric System (BES).

Mandatory Subject to

EnforcementIRO-006-EAST-2 Transmission Loading Relief Procedure for the Eastern Interconnection

To coordinate action between Reliability Coordinators within the Eastern Interconnection when implementing transmission loading relief procedures (TLR) for the Eastern Interconnection to prevent or manage potential or actual System Operating Limit (SOL) and Interconnection Reliability Operating Limit (IROL) exceedances to maintain reliability of the Bulk Electric System (BES).

Implementation Plan

Mandatory Subject to

EnforcementIRO-006-TRE-1 IROL and SOL Mitigation in the ERCOT Region

To provide and execute transmission loading relief procedures that can be used to mitigate SOL or IROL exceedances for the purpose of maintaining reliable operation of the bulk electric system in the ERCOT Region.

Implementation Plan

Mandatory Subject to

EnforcementIRO-006-WECC-2 Qualified Transfer Path Unscheduled Flow (USF) Relief

IRO-008-1 Reliability Coordinator Operational Analyses and Real-time Assessments To prevent instability, uncontrolled separation, or cascading outages that adversely impact the reliability of the interconnection by ensuring that the Bulk Electric System is assessed during the operations horizon.

Implementation Plan

Mandatory Subject to

EnforcementIRO-008-2 Reliability Coordinator Operational Analyses and Real-time AssessmentsPerform analyses and assessments to prevent instability, uncontrolled separation, or

Cascading. Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

8/13/2015 1/1/2016

Inactive 8/5/2009 10/1/2011 3/31/2017

11/13/2014 1/1/2017

Inactive 2/7/2006 6/18/2007 3/31/2017

Withdrawn 8/4/2011 1/26/2016

11/13/2014 4/1/2017

Inactive 2/7/2006 6/18/2007 3/31/2017

Inactive 2/7/2006 6/18/2007 3/31/2017

11/13/2014 4/1/2017

Inactive 5/5/2016 3/31/2018

11/2/2016 4/1/2018

11/5/2009 4/1/2011

Mandatory Subject to

EnforcementIRO-009-2 Reliability Coordinator Actions to Operate Within IROLs

To prevent instability, uncontrolled separation, or cascading outages that adversely impact the reliability of the interconnection by ensuring prompt action to prevent or mitigate instances of exceeding Interconnection Reliability Operating Limits (IROLs).

Implementation Plan

IRO-010-1a Reliability Coordinator Data Specification and Collection To prevent instability, uncontrolled separation, or cascading outages that adversely impact the reliability of the interconnection by ensuring the Reliability Coordinator has the data it needs to monitor and assess the operation of its Reliability Coordinator Area.

Mandatory Subject to

EnforcementIRO-010-2 Reliability Coordinator Data Specification and Collection

To prevent instability, uncontrolled separation, or Cascading outages that adversely impact reliability, by ensuring the Reliability Coordinator has the data it needs to monitor and assess the operation of its Reliability Coordinator Area.

Implementation Plan

IRO-014-1 Procedures, Processes, or Plans to Support Coordination Between Reliability CoordinatorsTo ensure that each Reliability Coordinator’s operations are coordinated such that they will not have an Adverse Reliability Impact on other Reliability Coordinator Areas and to preserve the reliability benefits of interconnected operations.

Implementation Plan

IRO-014-2 Coordination Among Reliability CoordinatorsTo ensure that each Reliability Coordinator’s operations are coordinated such that they will not have an Adverse Reliability Impact on other Reliability Coordinator Areas and to preserve the reliability benefits of interconnected operations.

Mandatory Subject to

EnforcementIRO-014-3 Coordination Among Reliability Coordinators

To ensure that each Reliability Coordinator’s operations are coordinated such that they will not adversely impact other Reliability Coordinator Areas and to preserve the reliability benefits of interconnected operations.

Implementation Plan

IRO-015-1 Notifications and Information Exchange Between Reliability CoordinatorsTo ensure that each Reliability Coordinator’s operations are coordinated such that they will not have an Adverse Reliability Impact on other Reliability Coordinator Areas and to preserve the reliability benefits of interconnected operations.

Implementation Plan

IRO-016-1 Coordination of Real-time Activities Between Reliability Coordinators To ensure that each Reliability Coordinator’s operations are coordinated such that they will not have an Adverse Reliability Impact on other Reliability Coordinator Areas and to preserve the reliability benefits of interconnected operations.

Implementation Plan

Mandatory Subject to

EnforcementIRO-017-1 Outage Coordination To ensure that outages are properly coordinated in the Operations Planning time horizon and

Near-Term Transmission Planning Horizon. Implementation Plan

IRO-018-1 Reliability Coordinator Real-time Reliability Monitoring and Analysis CapabilitiesEstablish requirements for Real-time monitoring and analysis capabilities to support reliable System operations. Implementation Plan

Mandatory Subject to

EnforcementIRO-018-1(i) Reliability Coordinator Real-time Reliability Monitoring and Analysis CapabilitiesEstablish requirements for Real-time monitoring and analysis capabilities to support reliable

System operations. Implementation Plan

Mandatory Subject to

EnforcementMOD-001-1a Available Transmission System Capability To ensure that calculations are performed by Transmission Service Providers to maintain

awareness of available transmission system capability and future flows on their own systems as well as those of their neighbors

Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

2/6/2014

11/13/2008 4/1/2011

8/26/2008 4/1/2011

Inactive 2/8/2005 6/18/2007 6/30/2016

Inactive 2/8/2005 6/30/2016 Implementation Plan

Inactive 2/8/2005 6/18/2007 6/30/2016

Inactive 5/2/2006 6/30/2016

Inactive 2/8/2005 6/30/2016 Implementation Plan

Inactive 2/8/2005 6/30/2016 Implementation Plan

Inactive 10/29/2008 6/30/2016

Filed and Pending Regulatory Approval

MOD-001-2 Available Transmission System CapabilityTo ensure that determinations of available transmission system capability are determined in a manner that supports the reliable operation of the Bulk-Power System (BPS) and that the methodology and data underlying those determinations are disclosed to those registered entities that need such information for reliability purposes.

Implementation Plan

Mandatory Subject to

EnforcementMOD-004-1 Capacity Benefit Margin To promote the consistent and reliable calculation, verification, preservation, and use of

Capacity Benefit Margin (CBM) to support analysis and system operations. Implementation Plan

Mandatory Subject to

EnforcementMOD-008-1 Transmission Reliability Margin Calculation Methodology To promote the consistent and reliable calculation, verification, preservation, and use of

Transmission Reliability Margin (TRM) to support analysis and system operations. Implementation Plan

MOD-010-0 Steady-State Data for Modeling and Simulation of the Interconnected Transmission SystemTo establish consistent data requirements, reporting procedures, and system models to be used in the analysis of the reliability of the Interconnected Transmission Systems. Implementation Plan

MOD-011-0 Maintenance and Distribution of Steady-State Data Requirements and Reporting ProceduresTo establish consistent data requirements, reporting procedures, and system models to be used in the analysis of the reliability of the interconnected transmission systems.

MOD-012-0 Dynamics Data for Modeling and Simulation of the Interconnected Transmission System.To establish consistent data requirements, reporting procedures, and system models to be used in the analysis of the reliability of the interconnected transmission systems. Implementation Plan

MOD-013-1 Maintenance and Distribution of Dynamics Data Requirements and Reporting ProceduresTo establish consistent data requirements, reporting procedures, and system models to be used in the analysis of the reliability of the interconnected transmission systems. Implementation Plan

MOD-014-0 Development of Steady-State System Models To establish consistent data requirements, reporting procedures, and system models to be used in the analysis of the reliability of the interconnected transmission systems.

MOD-015-0 Development of Dynamics System Models To establish consistent data requirements, reporting procedures, and system models to be used in the analysis of the reliability of the interconnected transmission systems.

MOD-015-0.1 Development of Dynamics System Models To establish consistent data requirements, reporting procedures, and system models to be used in the analysis of the reliability of the interconnected transmission systems. Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

Inactive 10/29/2008 5/13/2009 6/30/2016

Inactive 10/29/2008 5/13/2009 6/30/2016

Inactive 2/8/2005 6/18/2007 6/30/2016

Inactive 10/29/2008 5/13/2009 6/30/2016

2/8/2005 6/18/2007

Inactive 8/5/2010 4/1/2011 6/30/2016

Inactive 2/7/2006 6/30/2016

MOD-016-1.1 Documentation of Data Reporting Requirements for Actual and Forecast Demands, Net Energy for Load, and Controllable Demand-Side Management

Ensure that accurate, actual Demand data is available to support assessments and validation of past events and databases. Forecast Demand data is needed to perform future system assessments to identify the need for system reinforcements for continued reliability. In addition, to assist in proper real-time operating, Load information related to controllable Demand-Side Management (DSM) programs is needed.

Implementation Plan

MOD-017-0.1 Aggregated Actual and Forecast Demands and Net Energy for Load

To ensure that assessments and validation of past events and databases can be performed, reporting of actual Demand data is needed. Forecast demand data is needed to perform future system assessment to identify the need for system reinforcement for continued reliability. In addition to assist in proper real-time operating, load information related to controllable Demand-Side Management programs is needed.

Implementation Plan

MOD-018-0 Treatment of Nonmember Demand Data and How Uncertainties are Addressed in the Forecasts of Demand and Net Energy for Load

To ensure that Assessments and validation of past events and databases can be performed, reporting of actual demand data is needed. Forecast demand data is needed to perform future system assessments to identify the need for system reinforcement for continued reliability. In addition, to assist in proper real-time operating, load information related to controllable Demand-Side Management programs is needed.

Implementation Plan

MOD-019-0.1 Reporting of Interruptible Demands and Direct Control Load Management

To ensure that assessments and validation of past events and databases can be performed, reporting of actual demand data is needed. Forecast demand data is needed to perform future system assessments to identify the need for system reinforcement for continued reliability. In addition, to assist in proper real-time operating, load information related to controllable Demand-Side Management programs is needed.

Implementation Plan

Mandatory Subject to

EnforcementMOD-020-0 Providing Interruptible Demands and Direct Control Load Management Data to System Operators and Reliability Coordinators

To ensure that assessments and validation of past events and databases can be performed, reporting of actual demand data is needed. Forecast demand data is needed to perform future system assessments to identify the need for system reinforcement for continued reliability. In addition to assist in proper real-time operating, load information related to controllable Demand-Side Management programs is needed.

Implementation Plan

MOD-021-1 Documentation of the Accounting Methodology for the Effects of Demand-Side Management in Demand and Energy Forecasts.

To ensure that assessments and validation of past events and databases can be performed, reporting of actual Demand data is needed. Forecast demand data is needed to perform future system assessments to identify the need for system reinforcement for continued reliability. In addition, to assist in proper real-time operating, load information related to Demand-Side Management (DSM) programs is needed.

Implementation Plan

MOD-024-1 Verification of Generator Gross and Net Real Power Capability To ensure accurate information on generator gross and net Real Power capability is available for steady-state models used to assess Bulk Electric System reliability. Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

Inactive 2/7/2006 6/30/2016

2/7/2013 7/1/2016

2/7/2013 7/1/2014

2/7/2013 7/1/2014

2/9/2012 10/1/2013

Inactive 11/5/2009 4/1/2011 3/31/2017

11/13/2014 4/1/2017

Inactive 2/10/2009 4/1/2011 3/31/2017

11/13/2014 4/1/2017

MOD-025-1 Verification of Generator Gross and Net Reactive Power CapabilityTo ensure accurate information on generator gross and net Reactive Power capability is available for steady-state models used to assess Bulk Electric System reliability. Implementation Plan

Mandatory Subject to

EnforcementMOD-025-2 Verification and Data Reporting of Generator Real and Reactive Power Capability and Synchronous Condenser Reactive Power Capability

To ensure that accurate information on generator gross and net Real and Reactive Power capability and synchronous condenser Reactive Power capability is available for planning models used to assess Bulk Electric System (BES) reliability.

Implementation Plan

Mandatory Subject to

EnforcementMOD-026-1 Verification of Models and Data for Generator Excitation Control System or Plant Volt/Var Control Functions

To verify that the generator excitation control system or plant volt/var control function model (including the power system stabilizer model and the impedance compensator model) and the model parameters used in dynamic simulations accurately represent the generator excitation control system or plant volt/var control function behavior when assessing Bulk Electric System (BES) reliability.

Implementation Plan

Mandatory Subject to

EnforcementMOD-027-1 Verification of Models and Data for Turbine/Governor and Load Control or Active Power/Frequency Control Functions

To verify that the turbine/governor and load control or active power/frequency control model and the model parameters, used in dynamic simulations that assess Bulk Electric System (BES) reliability, accurately represent generator unit real power response to system frequency variations.

Implementation Plan

Mandatory Subject to

EnforcementMOD-028-2 Area Interchange Methodology

To increase consistency and reliability in the development and documentation of Transfer Capability calculations for short-term use performed by entities using the Area Interchange Methodology to support analysis and system operations.

Implementation Plan

MOD-029-1a Rated System Path MethodologyTo increase consistency and reliability in the development and documentation of transfer capability calculations for short-term use performed by entities using the Rated System Path Methodology to support analysis and system operations.

Implementation Plan

Mandatory Subject to

EnforcementMOD-029-2a Rated System Path Methodology

To increase consistency and reliability in the development and documentation of transfer capability calculations for short-term use performed by entities using the Rated System Path Methodology to support analysis and system operations.

Implementation Plan

MOD-030-2 Flowgate MethodologyTo increase consistency and reliability in the development and documentation of transfer capability calculations for short-term use performed by entities using the Flowgate Methodology to support analysis and system operations.

Implementation Plan

Mandatory Subject to

EnforcementMOD-030-3 Flowgate Methodology

To increase consistency and reliability in the development and documentation of transfer capability calculations for short-term use performed by entities using the Flowgate Methodology to support analysis and system operations.

Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

Inactive 5/7/2014 7/1/2016 9/30/2016

11/5/2015 10/1/2016

2/6/2014 7/1/2015

2/6/2014 7/1/2017

8/14/2014 1/1/2016

Inactive 3/8/2012 9/13/2012 3/31/2017

2/17/2011 10/1/2012

5/10/2018

2/10/2009 4/1/2011

Inactive 2/10/2009 4/1/2013 6/30/2016

2/6/2014 7/1/2016

8/11/2016 10/1/2020

MOD-031-1 Demand and Energy Data To provide authority for applicable entities to collect Demand, energy and related data to support reliability studies and assessments and to enumerate the responsibilities and obligations of requestors and respondents of that data.

Implementation Plan

Mandatory Subject to

EnforcementMOD-031-2 Demand and Energy Data

To provide authority for applicable entities to collect Demand, energy and related data to support reliability studies and assessments and to enumerate the responsibilities and obligations of requestors and respondents of that data.

Implementation Plan

Mandatory Subject to

EnforcementMOD-032-1 Data for Power System Modeling and Analysis

To establish consistent modeling data requirements and reporting procedures for development of planning horizon cases necessary to support analysis of the reliability of the interconnected transmission system.

Implementation Plan

Mandatory Subject to

EnforcementMOD-033-1 Steady-State and Dynamic System Model Validation

To establish consistent validation requirements to facilitate the collection of accurate data and building of planning models to analyze the reliability of the interconnected transmission system.

Implementation Plan

Mandatory Subject to

EnforcementNUC-001-3 Nuclear Plant Interface Coordination This standard requires coordination between Nuclear Plant Generator Operators and

Transmission Entities for the purpose of ensuring nuclear plant safe operation and shutdown. Implementation Plan

PER-001-0.2 Operating Personnel Responsibility and AuthorityTransmission Operator and Balancing Authority operating personnel must have the responsibility and authority to implement real-time actions to ensure the stable and reliable operation of the Bulk Electric System.

Implementation Plan

Mandatory Subject to

EnforcementPER-003-1 Operating Personnel Credentials

To ensure that System Operators performing the reliability-related tasks of the Reliability Coordinator, Balancing Authority and Transmission Operator are certified through the NERC System Operator Certification Program when filling a Real-time operating position responsible for control of the Bulk Electric System.

Implementation Plan

Filed and Pending Regulatory Approval

PER-003-2 Operating Personnel CredentialsTo ensure that System Operators performing the reliability-related tasks of the Reliability Coordinator, Balancing Authority and Transmission Operator are certified through the NERC System Operator Certification Program when filling a Real-time operating position responsible for control of the Bulk Electric System.

Implementation Plan

Mandatory Subject to

EnforcementPER-004-2 Reliability Coordination — Staffing Reliability Coordinators must have sufficient, competent staff to perform the Reliability

Coordinator functions. Implementation Plan

PER-005-1 System Personnel TrainingTo ensure that System Operators performing real-time, reliability-related tasks on the North American Bulk Electric System (BES) are competent to perform those reliability-related tasks. The competency of System Operators is critical to the reliability of the North American Bulk Electric System.

Implementation Plan

Mandatory Subject to

EnforcementPER-005-2 Operations Personnel Training To ensure that personnel performing or supporting Real-time operations

on the Bulk Electric System are trained using a systematic approach. Implementation Plan

Subject to Future Enforcement PER-006-1 Specific Training for Personnel To ensure that personnel are trained on specific topics essential to reliability to perform or

support Real-time operations of the Bulk Electric System. Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

To ensure system protection is coordinated among operating entities. 2/12/2015 5/29/2015 9/30/2020

Withdrawn To ensure system protection is coordinated among operating entities. 5/29/2012 1/26/2016

Inactive 8/2/2006 6/30/2016

11/13/2014 7/1/2016

Inactive 11/4/2010 10/20/2013 7/1/2016

Inactive 2/7/2006 6/30/2016

Inactive PRC-004-2 8/5/2010 9/25/2011

Inactive 11/13/2014 5/29/2015 6/30/2016

Inactive PRC-004-2.1a 2/9/2012 11/25/2013 5/28/2015

Inactive PRC-004-2a 2/17/2011 4/1/2012 11/24/2013

Inactive PRC-004-3 8/14/2014 6/30/2016

Inactive 11/13/2014 6/30/2016

Inactive 6/22/2015 7/1/2016 4/1/2017

6/22/2015 4/2/2017

Inactive 10/29/2008 10/1/2011 3/31/2017

Mandatory Subject to

EnforcementPRC-001-1.1(ii) System Protection Coordination Implementation Plan

PRC-001-2 System Protection Coordination

PRC-002-1 Define Regional Disturbance Monitoring and Reporting RequirementsEnsure that Regional Reliability Organizations establish requirements for installation of Disturbance Monitoring Equipment (DME) and reporting of Disturbance data to facilitate analyses of events and verify system models.

Implementation Plan

Mandatory Subject to

EnforcementPRC-002-2 Disturbance Monitoring and Reporting Requirements

To have adequate data available to facilitate analysis of Bulk Electric System (BES) Disturbances. Implementation Plan

PRC-002-NPCC-01 Disturbance MonitoringEnsure that adequate disturbance data is available to facilitate Bulk Electric System event analyses. All references to equipment and facilities herein unless otherwise noted will be to Bulk Electric System (BES) elements.

Implementation Plan

PRC-003-1 Regional Procedure for Analysis of Misoperations of Transmission and Generation Protection SystemsTo ensure all transmission and generation Protection System Misoperations affecting the reliability of the Bulk Electric System (BES) are analyzed and mitigated. Implementation Plan

Analysis and Mitigation of Transmission and Generation Protection System MisoperationsEnsure all transmission and generation Protection System Misoperations affecting the reliability of the Bulk Electric System (BES) are analyzed and mitigated. Implementation Plan

PRC-004-2.1(i)aAnalysis and Mitigation of Transmission and Generation Protection System Misoperations

Ensure all transmission and generation Protection System Misoperations affecting the reliability of the Bulk Electric System (BES) are analyzed and mitigated. Implementation Plan

Analysis and Mitigation of Transmission and Generation Protection System MisoperationsEnsure all transmission and generation Protection System Misoperations affecting the reliability of the Bulk Electric System (BES) are analyzed and mitigated. Implementation Plan

Analysis and Mitigation of Transmission and Generation Protection System MisoperationsEnsure all transmission and generation Protection System Misoperations affecting the reliability of the Bulk Electric System (BES) are analyzed and mitigated. Implementation Plan

Protection System Misoperation Identification and Correction Identify and correct the causes of Misoperations of Protection Systems for Bulk Electric System (BES) Elements. Implementation Plan

PRC-004-4 Project 2014-01 Standards Applicability for Dispersed Generation ResourcesIdentify and correct the causes of Misoperations of Protection Shystems for Bulk Electric System (BES) Elements. Implementation Plan

PRC-004-4(i) Protection System Misoperation Identification and Correction Identify and correct the causes of Misoperations of Protection Systems for Bulk Electric System (BES) Elements. Implementation Plan

Mandatory Subject to

EnforcementPRC-004-5(i) Protection System Misoperation Identification and Correction Identify and correct the causes of Misoperations of Protection Systems for Bulk Electric System

(BES) Elements. Implementation Plan

PRC-004-WECC-1 Protection System and Remedial Action Scheme MisoperationRegional Reliability Standard to ensure all transmission and generation Protection System and Remedial Action Scheme (RAS) Misoperations on Transmission Paths and RAS defined in section 4 are analyzed and/or mitigated.

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

11/13/2014 4/1/2017

5/9/2012 11/25/2013 3/31/2027

Inactive 11/7/2012 4/1/2015 5/28/2015

Inactive 11/13/2014 5/29/2015 12/31/2016

Inactive 11/13/2014 12/31/2015

Inactive 11/7/2013 12/31/2015

Inactive 11/13/2014 12/31/2015

Mandatory Subject to

EnforcementPRC-004-WECC-2 Protection System and Remedial Action Scheme Misoperation

Regional Reliability Standard to ensure all transmission and generation Protection System and Remedial Action Scheme (RAS) Misoperations on Transmission Paths and RAS defined in section 4 are analyzed and/or mitigated.

Implementation Plan

Mandatory Subject to

EnforcementPRC-005-1.1b Transmission and Generation Protection System Maintenance and Testing To ensure all transmission and generation Protection Systems affecting the reliability of the

Bulk Electric System (BES) are maintained and tested. Implementation Plan

PRC-005-2 Protection System MaintenanceTo document and implement programs for the maintenance of all Protection Systems affecting the reliability of the Bulk Electric System (BES) so that these Protection Systems are kept in working order.

Implementation Plan

PRC-005-2(i) Protection System MaintenanceTo document and implement programs for the maintenance of all Protection Systems affecting the reliability of the Bulk Electric System (BES) so that these Protection Systems are kept in working order.

Implementation Plan

PRC-005-2(ii) Protection System Maintenance To document and implement programs for the maintenance of all Protection Systems affecting the reliability of the Bulk Electric System (BES) so that these Protection Systems are kept in working order.

Implementation Plan

PRC-005-3 Protection System and Automatic Reclosing Maintenance To document and implement programs for the maintenance of all Protection Systems and Automatic Reclosing affecting the reliability of the Bulk Electric System (BES) so that they are kept in working order.

Implementation Plan

PRC-005-3(i) Protection System and Automatic Reclosing Maintenance To document and implement programs for the maintenance of all Protection Systems and Automatic Reclosing affecting the reliability of the Bulk Electric System (BES) so that they are kept in working order.

Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

Inactive 11/13/2014 4/1/2017 12/31/2015

Inactive 11/13/2014 12/31/2015

Inactive 5/7/2015 12/31/2015

11/5/2015 1/1/2016

Inactive 11/13/2014 10/1/2015 9/30/2017

8/10/2017 10/1/2017

2/9/2012 7/1/2015

Inactive 11/3/2011 4/1/2014 12/31/2017

8/10/2017 1/1/2018

2/8/2005 6/18/2007 3/31/2027 Implementation Plan

Inactive 2/8/2005 6/18/2007 3/31/2017

PRC-005-3(ii) Protection System and Automatic Reclosing Maintenance To document and implement programs for the maintenance of all Protection Systems and Automatic Reclosing affecting the reliability of the Bulk Electric System (BES) so that they are kept in working order.

Implementation Plan

PRC-005-4 Protection System, Automatic Reclosing, and Sudden Pressure Relaying To document and implement programs for the maintenance of all Protection Systems, Automatic Reclosing, and Sudden Pressure Relaying affecting the reliability of the Bulk Electric System (BES) so that they are kept in working order.

Implementation Plan

PRC-005-5 Protection System, Automatic Reclosing, and Sudden Pressure Relaying To document and implement programs for the maintenance of all Protection Systems, Automatic Reclosing, and Sudden Pressure Relaying affecting the reliability of the Bulk Electric System (BES) so that they are kept in working order.

Implementation Plan

Mandatory Subject to

EnforcementPRC-005-6 Protection System, Automatic Reclosing, and Sudden Pressure Relaying Maintenance

To document and implement programs for the maintenance of all Protection Systems, Automatic Reclosing, and Sudden Pressure Relaying affecting the reliability of the Bulk Electric System (BES) so that they are kept in working order.

Implementation Plan

PRC-006-2 Automatic Underfrequency Load SheddingTo establish design and documentation requirements for automatic underfrequency load shedding (UFLS) programs to arrest declining frequency, assist recovery of frequency following underfrequency events and provide last resort system preservation measures.

Implementation Plan

Mandatory Subject to

EnforcementPRC-006-3 Automatic Underfrequency Load Shedding

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

Mandatory Subject to

EnforcementPRC-006-NPCC-1 Automatic Underfrequency Load Shedding

To provide a regional reliability standard that ensures the development of an effective automatic underfrequency load shedding (UFLS) program in order to preserve the security and integrity of the bulk power system during declining system frequency events in coordination with the NERC UFLS reliability standard characteristics.

Implementation Plan

PRC-006-SERC–01 Automatic Underfrequency Load Shedding RequirementsTo establish consistent and coordinated requirements for the design, implementation, and analysis of automatic underfrequency load shedding (UFLS) programs among all SERC applicable entities.

Implementation Plan

Mandatory Subject to

EnforcementPRC-006-SERC-02 Automatic Underfrequency Load Shedding Requirements

To establish consistent and coordinated requirements for the design,implementation, and analysis of automatic underfrequency load shedding (UFLS)programs among all SERC applicable entities.

Mandatory Subject to

EnforcementPRC-008-0 Implementation and Documentation of Underfrequency Load Shedding Equipment Maintenance ProgramProvide last resort system preservation measures by implementing an Under Frequency Load

Shedding (UFLS) program.

PRC-010-0 Technical Assessment of the Design and Effectiveness of Undervoltage Load Shedding Program.Provide System preservation measures in an attempt to prevent system voltage collapse or voltage instability by implementing an Undervoltage Load Shedding (UVLS) program. Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

Inactive 11/13/2014 4/1/2017 4/1/2017

5/7/2015 4/2/2017

2/8/2005 6/18/2007 3/31/2027 Implementation Plan

Pending Inactive 2/8/2005 Implementation Plan

Pending Inactive 11/13/2014 12/31/2020

5/5/2016 1/1/2021

Pending Inactive 2/8/2005

Pending Inactive 11/13/2014 12/31/2020

Pending Inactive 2/8/2005

Pending Inactive 11/13/2014 12/31/2020

Inactive 2/8/2005 6/18/2007 3/31/2017

PRC 010 1‐ ‐ Undervoltage Load Shedding To establish an integrated and coordinated approach to the design, evaluation, and reliable operation of Undervoltage Load Shedding Programs (UVLS Programs). Implementation Plan

Mandatory Subject to

EnforcementPRC-010-2 Undervoltage Load Shedding To establish an integrated and coordinated approach to the design, evaluation, and reliable

operation of Undervoltage Load Shedding Programs (UVLS Programs). Implementation Plan

Mandatory Subject to

EnforcementPRC-011-0 Undervoltage Load Shedding System Maintenance and Testing Provide system preservation measures in an attempt to prevent system voltage collapse or

voltage instability by implementing an Undervoltage Load Shedding (UVLS) program.

PRC-012-0 Special Protection System Review ProcedureTo ensure that all Special Protection Systems (SPS) are properly designed, meet performance requirements, and are coordinated with other protection systems. To ensure that maintenance and testing programs are developed and misoperations are analyzed and corrected.

PRC-012-1 Remedial Action Scheme Review ProcedureTo ensure that all Remedial Action Schemes (RAS) are properly designed, meet performance requirements, and are coordinated with other protection systems. To ensure that maintenance and testing programs are developed and misoperations are analyzed and corrected.

Implementation Plan

Subject to Future Enforcement PRC-012-2 Remedial Action Schemes To ensure that Remedial Action Schemes (RAS) do not introduce unintentional or unacceptable

reliability risks to the Bulk Electric System (BES). Implementation Plan

PRC-013-0 Special Protection System Database To ensure that all Special Protection Systems (SPSs) are properly designed, meet performance requirements, and are coordinated with other protection systems. Implementation Plan

PRC-013-1 Remedial Action Scheme Database To ensure that all Remedial Action Schemes (RAS) are properly designed, meet performance requirements, and are coordinated with other protection systems. Implementation Plan

PRC-014-0 Special Protection System AssessmentTo ensure that all Special Protection Systems (SPS) are properly designed, meet performance requirements, and are coordinated with other protection systems. To ensure that maintenance and testing programs are developed and misoperations are analyzed and corrected.

Implementation Plan

PRC-014-1 Remedial Action Scheme AssessmentTo ensure that all Remedial Action Schemes (RAS) are properly designed, meet performance requirements, and are coordinated with other protection systems. To ensure that maintenance and testing programs are developed and misoperations are analyzed and corrected.

Implementation Plan

PRC-015-0 Special Protection System Data and DocumentationTo ensure that all Special Protection Systems (SPS) are properly designed, meet performance requirements, and are coordinated with other protection systems. To ensure that maintenance and testing programs are developed and misoperations are analyzed and corrected.

Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

11/13/2014 4/1/2017 12/31/2020

Inactive 10/29/2008 5/13/2009 3/31/2017

11/13/2014 4/1/2017 12/31/2020

Inactive 2/8/2005 6/18/2007 3/31/2017

11/13/2014 4/1/2017 3/31/2027

8/2/2006 6/18/2007 6/30/2022

Inactive 2/7/2013 7/1/2016 6/30/2016

2/12/2015 7/1/2016

Mandatory Subject to

EnforcementPRC-015-1 Remedial Action Scheme Data and Documentation

To ensure that all Remedial Action Schemes (RAS) are properly designed, meet performance requirements, and are coordinated with other protection systems. To ensure that maintenance and testing programs are developed and misoperations are analyzed and corrected.

Implementation Plan

PRC-016-0.1 Special Protection System MisoperationsTo ensure that all Special Protection Systems (SPS) are properly designed, meet performance requirements, and are coordinated with other protection systems. To ensure that maintenance and testing programs are developed and misoperations are analyzed and corrected.

Implementation Plan

Mandatory Subject to

EnforcementPRC-016-1 Remedial Action Scheme Misoperations

To ensure that all Remedial Action Schemes (RAS) are properly designed, meet performance requirements, and are coordinated with other protection systems. To ensure that maintenance and testing programs are developed and misoperations are analyzed and corrected.

Implementation Plan

PRC-017-0 Special Protection System Maintenance and TestingTo ensure that all Special Protection Systems (SPS) are properly designed, meet performance requirements, and are coordinated with other protection systems. To ensure that maintenance and testing programs are developed and misoperations are analyzed and corrected.

Implementation Plan

Mandatory Subject to

EnforcementPRC-017-1 Remedial Action Scheme Maintenance and Testing

To ensure that all Remedial Action Schemes (RAS) are properly designed, meet performance requirements, and are coordinated with other protection systems. To ensure that maintenance and testing programs are developed and misoperations are analyzed and corrected.

Implementation Plan

Mandatory Subject to

EnforcementPRC-018-1 Disturbance Monitoring Equipment Installation and Data ReportingEnsure that Disturbance Monitoring Equipment (DME) is installed and that Disturbance data is

reported in accordance with regional requirements to facilitate analyses of events. Implementation Plan

PRC-019-1 Coordination of Generating Unit or Plant Capabilities, Voltage Regulating Controls, and ProtectionTo verify coordination of generating unit Facility or synchronous condenser voltage regulating controls, limit functions, equipment capabilities and Protection System settings. Implementation Plan

Mandatory Subject to

EnforcementPRC-019-2 Coordination of Generating Unit or Plant Capabilities, Voltage Regulating Controls, and ProtectionTo verify coordination of generating unit Facility or synchronous condenser voltage regulating

controls, limit functions, equipment capabilities and Protection System settings. Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

Pending Inactive 2/7/2006 3/31/2017

Inactive 2/7/2006 6/18/2007 3/31/2017

Inactive 2/7/2006 6/18/2007 3/31/2017

Inactive 11/7/2013 10/1/2014 3/31/2017

11/13/2014 4/1/2017

Inactive 5/9/2013 7/1/2016 6/30/2016

2/12/2015 7/1/2016

Inactive 8/15/2013 10/1/2014 6/30/2018

2/8/2018 7/1/2018

12/17/2014 1/1/2018

PRC-020-1 Under-Voltage Load Shedding Program DatabaseEnsure that a regional database is maintained for Under-Voltage Load Shedding (UVLS) programs implemented by entities within the Region to mitigate the risk of voltage collapse or voltage instability in the Bulk Electric System (BES). Ensure the UVLS database is available for Regional studies and for dynamic studies and simulations of the BES.

PRC-021-1 Under-Voltage Load Shedding Program DataEnsure data is provided to support the Regional database maintained for Under-Voltage Load Shedding (UVLS) programs that were implemented to mitigate the risk of voltage collapse or voltage instability in the Bulk Electric System (BES).

PRC-022-1 Under-Voltage Load Shedding Program Performance Ensure that Under Voltage Load Shedding (UVLS) programs perform as intended to mitigate the risk of voltage collapse or voltage instability in the Bulk Electric System (BES).

PRC-023-3 Transmission Relay LoadabilityProtective relay settings shall not limit transmission loadability; not interfere with system operators’ ability to take remedial action to protect system reliability and; be set to reliably detect all fault conditions and protect the electrical network from these faults.

Implementation Plan

Mandatory Subject to

EnforcementPRC-023-4 Transmission Relay Loadability

Protective relay settings shall not limit transmission loadability; not interfere with system operators’ ability to take remedial action to protect system reliability and; be set to reliably detect all fault conditions and protect the electrical network from these faults.

Implementation Plan

PRC-024-1 Generator Frequency and Voltage Protective Relay Settings Ensure Generator Owners set their generator protective relays such that generating units remain connected during defined frequency and voltage excursions. Implementation Plan

Mandatory Subject to

EnforcementPRC-024-2 Generator Frequency and Voltage Protective Relay Settings Ensure Generator Owners set their generator protective relays such that generating units

remain connected during defined frequency and voltage excursions. Implementation Plan

PRC-025-1 Generator Relay LoadabilityTo set load-responsive protective relays associated with generation Facilities at a level to prevent unnecessary tripping of generators during a system disturbance for conditions that do not pose a risk of damage to the associated equipment.

Implementation Plan

Mandatory Subject to

EnforcementPRC-025-2 Generator Relay Loadability

To set load-responsive protective relays associated with generation Facilities at a level to prevent unnecessary tripping of generators during a system disturbance for conditions that do

not pose a risk of damage to the associated equipment.Implementation Plan

Mandatory Subject to

EnforcementPRC-026-1 Relay Performance During Stable Power Swings To ensure that load-responsive protective relays are expected to not trip in response to stable

power swings during non-Fault conditions. Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

11/5/2015 10/1/2020

Inactive 5/12/2010 11/21/2011 3/31/2017

Withdrawn 5/9/2012 1/26/2016

Inactive 2/12/2015 4/1/2017 6/30/2018

2/9/2017 7/1/2018

Inactive 4/11/2012 9/13/2012 3/31/2017

Withdrawn To ensure that Transmission Operators have plans for operating within specified limits 5/9/2012 1/26/2016

11/13/2014 4/1/2017

Inactive 10/17/2008 10/1/2011 3/31/2017

Withdrawn 5/9/2012 1/26/2016

11/13/2014 1/1/2017

Inactive 11/1/2006 1/22/2009 3/31/2017

Inactive 10/17/2008 10/1/2011 3/31/2017

Inactive To ensure critical reliability parameters are monitored in real-time. 10/17/2008 10/1/2011 3/31/2017

Subject to Future Enforcement PRC-027-1 Coordination of Protection Systems for Performance During Faults

To maintain the coordination of Protection Systems installed to detect and isolate Faults on Bulk Electric System (BES) Elements, such that those Protection Systems operate in the intended sequence during Faults.

Clean Version: (With Errata Change) Implementation Plan

TOP-001-1a Reliability Responsibilities and AuthoritiesTo ensure reliability entities have clear decision-making authority and capabilities to take appropriate actions or direct the actions of others to return the transmission system to normal conditions during an emergency.

Implementation Plan

TOP-001-2 Transmission OperationsTo prevent instability, uncontrolled separation, or cascading outages that adversely impact the reliability of the Interconnection by ensuring prompt action to prevent or mitigate such occurrences.

Implementation Plan

TOP-001-3 Transmission OperationsTo prevent instability, uncontrolled separation, or Cascading outages that adversely impact the reliability of the Interconnection by ensuring prompt action to prevent or mitigate such occurrences.

Implementation Plan

Mandatory Subject to

EnforcementTOP-001-4 Transmission Operations

To prevent instability, uncontrolled separation, or Cascading outages that adversely impact the reliability of the Interconnection by ensuring prompt action to prevent or mitigate such occurrences.

Implementation Plan

TOP-002-2.1b Normal Operations Planning Current operations plans and procedures are essential to being prepared for reliable operations, including response for unplanned events.

TOP-002-3 Operations Planning Implementation Plan

Mandatory Subject to

EnforcementTOP-002-4 Operations Planning To ensure that Transmission Operators and Balancing Authorities have plans for operating

within specified limits. Implementation Plan

TOP-003-1 Planned Outage CoordinationScheduled generator and transmission outages that may affect the reliability of interconnected operations must be planned and coordinated among Balancing Authorities, Transmission Operators, and Reliability Coordinators.

Implementation Plan

TOP-003-2 Operational Reliability Data To ensure that the Transmission Operator and Balancing Authority have the data needed to fulfill their operational planning and Real-time monitoring responsibilities. Implementation Plan

Mandatory Subject to

EnforcementTOP-003-3 Operational Reliability Data To ensure that the Transmission Operator and Balancing Authority have data needed to fulfill

their operational and planning responsibilities. Implementation Plan

TOP-004-2 Transmission OperationsTo ensure that the transmission system is operated so that instability, uncontrolled separation, or cascading outages will not occur as a result of the most severe single Contingency and specified multiple Contingencies.

TOP-005-2a Operational Reliability Information To ensure reliability entities have the operating data needed to monitor system conditions within their areas. Implementation Plan

TOP-006-2 Monitoring System Conditions Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

Inactive To ensure critical reliability parameters are monitored in real-time. 11/7/2012 3/18/2015

Inactive 2/8/2005 6/18/2007 3/31/2017

Inactive 2/6/2014 6/18/2014 3/10/2017

Inactive To ensure Transmission Operators take actions to mitigate SOL and IROL violations. 11/1/2006 6/18/2007 3/31/2017

Inactive 5/5/2016 3/31/2018

11/2/2016 4/1/2018

2/7/2013 1/1/2015

12/17/2014 7/1/2017

11/9/2017

Inactive 2/6/2014 11/13/2015 9/25/2017

8/10/2017 9/26/2017

Inactive 11/13/2014 5/29/2015 9/25/2017

8/10/2017 9/26/2017

TOP-006-3 Monitoring System Conditions Implementation Plan

TOP-007-0 Reporting System Operating Limit (SOL) and Interconnection Reliability Operating Limit (IROL) ViolationsThis standard ensures SOL and IROL violations are being reported to the Reliability Coordinator so that the Reliability Coordinator may evaluate actions being taken and direct additional corrective actions as needed.

Implementation Plan

TOP-007-WECC-1a System Operating Limits When actual flows on Major WECC Transfer Paths exceed System Operating Limits (SOL), their associated schedules and actual flows are not exceeded for longer than a specified time.

TOP-008-1 Response to Transmission Limit Violations Implementation Plan

TOP-010-1 Real-time Reliability Monitoring and Analysis Capabilities Establish requirements for Real-time monitoring and analysis capabilities to support reliable System operations. Implementation Plan

Mandatory Subject to

EnforcementTOP-010-1(i) Real-time Reliability Monitoring and Analysis Capabilities Establish requirements for Real-time monitoring and analysis capabilities to support reliable

System operations. Implementation Plan

Mandatory Subject to

EnforcementTPL-001-4 Transmission System Planning Performance Requirements

Establish Transmission system planning performance requirements within the planning horizon to develop a Bulk Electric System (BES) that will operate reliably over a broad spectrum of System conditions and following a wide range of probable Contingencies.

Implementation Plan

Mandatory Subject to

EnforcementTPL-007-1 Transmission System Planned Performance for Geomagnetic Disturbance EventsEstablish requirements for Transmission system planned performance during geomagnetic

disturbance (GMD) events. Implementation Plan

Filed and Pending Regulatory Approval

TPL-007-2 Transmission System Planned Performance for Geomagnetic Disturbance EventsEstablish requirements for Transmission system planned performance during geomagnetic disturbance (GMD) events. Implementation Plan

VAR-001-4.1 Voltage and Reactive ControlTo ensure that voltage levels, reactive flows, and reactive resources are monitored, controlled, and maintained within limits in Real-time to protect equipment and the reliable operation of the Interconnection.

Implementation Plan

Mandatory Subject to

EnforcementVAR-001-4.2 Voltage and Reactive Control

To ensure that voltage levels, reactive flows, and reactive resources are monitored,controlled, and maintained within limits in Real-time to protect equipment and the reliableoperation of the Interconnection.

Implementation Plan

VAR-002-4 Generator Operation for Maintaining Network Voltage SchedulesTo ensure generators provide reactive support and voltage control, within generating Facility capabilities, in order to protect equipment and maintain reliable operation of the Interconnection.

Implementation Plan

Mandatory Subject to

EnforcementVAR-002-4.1 Generator Operation for Maintaining Network Voltage Schedules

To ensure generators provide reactive support and voltage control, within generatingFacility capabilities, in order to protect equipment and maintain reliable operation of theInterconnection.

Implementation Plan

Status Standard Version Purpose Implementation PlanTitle (with Link to Project Page)

Board Adopted Date

Effective Date of Standard

Inactive Date

11/13/2014 4/1/2015

Inactive 11/13/2014 4/1/2015 6/30/2017

Inactive 2/9/2017 7/1/2017 9/25/2017

8/10/2017 9/26/2017

Mandatory Subject to

EnforcementVAR-002-WECC-2 Automatic Voltage Regulators (AVR) To ensure that Automatic Voltage Regulators on synchronous generators and condensers shall

be kept in service and controlling voltage. Implementation Plan

VAR-501-WECC-2 Power System Stabilizer (PSS) To ensure that Power System Stabilizers (PSS) on synchronous generators shall be kept in service. Implementation Plan

VAR-501-WECC-3 Power System Stabilizer (PSS)To ensure the Western Interconnection is operated in a coordinated manner under normal and abnormal conditions by establishing the performance criteria for WECC power system stabilizers.

Implementation Plan

Mandatory Subject to

EnforcementVAR-501-WECC-3.1 Power System Stabilizer (PSS)

To ensure the Western Interconnection is operated in a coordinated manner under normal and abnormal conditions by establishing the performance criteria for WECC power system stabilizers.

Related Documents Lessons Learned Compliance Guidance

Replaced BAL-001-1 4/16/2015

1/16/2014

1/19/2017

N/A

11/13/2015

Public Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

10/16/2013 RSAW

RSAW

Please see the implementation plan for specific compliance dates and timeframes.

01/10/2011 RSAW

BAL-002-1a was never approved or amended by FERC; notice of withdrawal filed 2/2/2017 following FERC approval of BAL-002-2.

RSAW

RSAW

11/21/2013

RSAW

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

N/A

5/30/2018

N/A

The retirement of BAL-004-0 is contingent upon the retirement of NAESB WEQ-006 Manual Time Error Correction Business Practice Standard.

3/16/2007 RSAW

10/16/2013

9/13/2012 RSAW

Requirement 3 becomes inactive 12/31/2018. Other requirements become inactive 1/1/2019. 1/06/2011 RSAW

3/17/2011

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

11/22/2013

3/31/2010 RSAW

RSAW

Errata approved by the SC on 9/27/2013. See also CIP V5 Effective Dates here under Key Resources: http://www.nerc.com/pa/CI/Pages/Transition-Program.aspx

RSAW CIP Version 5 Transition Program 5/20/2016: Compliance Guidance Updates

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

11/22/2013

4/19/2018

Errata approved by the SC on 9/27/2013 11/22/2013

Interpretation Interpretation of CIP-002-5.1 for Energy Sector Security Consortium (EnergySec)

3/31/2010 RSAW

RSAW

CIP Version 5 Transition Program

With the approval of CIP-003-7 and its associated Implementation Plan, entities will not be required to implement CIP-003-6, Requirement R2, Attachment 1, Sections 2 and 3. Instead, entities will implement CIP-003-7, Requirement R2, Attachment 1 Sections 2 and 3 on January 1, 2020. See Implementation Plan for CIP-003-7.

RSAW CIP Version 5 Transition Program 5/20/2016: Compliance Guidance Updates

12/12/2012 RSAW

CIP Version 5 Transition Program

Located under Key Resources: CIP V5 Effective Dates RSAW CIP Version 5 Transition Program 5/20/2016: Compliance Guidance Updates

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

11/22/2013

11/22/2013

11/22/2013

2/02/2011 RSAW

Located under Key Resources: CIP V5 Effective Dates RSAW CIP Version 5 Transition Program 5/20/2016: Compliance Guidance Updates

5/19/2011 RSAW

CIP Version 5 Transition Program

Located under Key Resources: CIP V5 Effective Dates RSAW CIP Version 5 Transition Program 5/20/2016: Compliance Guidance Updates

The version number was updated from CIP-007-3 to CIP-007-3a to incorporate the approved interpretation that should have previously been appended.

3/31/2010 RSAW

RSAW

CIP Version 5 Transition Program

Located under Key Resources: CIP V5 Effective Dates RSAW CIP Version 5 Transition Program 5/20/2016: Compliance Guidance Updates

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

11/22/2013

11/22/2013

11/22/2013

11/22/2013

3/31/2010 RSAW

Located under Key Resources: CIP V5 Effective Dates RSAW CIP Version 5 Transition Program 5/20/2016: Compliance Guidance Updates

3/31/2010 RSAW

CIP Version 5 Transition Program

Located under Key Resources: CIP V5 Effective Dates RSAW CIP Version 5 Transition Program 5/20/2016: Compliance Guidance Updates

CIP Version 5 Transition Program

Located under Key Resources: CIP V5 Effective Dates RSAW CIP Version 5 Transition Program 5/20/2016: Compliance Guidance Updates

CIP Version 5 Transition Program

Located under Key Resources: CIP V5 Effective Dates RSAW CIP Version 5 Transition Program 5/20/2016: Compliance Guidance Updates

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

11/20/2014

7/14/2015

Requirement R4 becomes inactive 6/30/2016

11/13/2015

4/16/2015

10/28/16: Compliance Guidance Updates

RSAW

5/13/2009

RSAW

RSAW

3/16/2007 RSAW

RSAW

RSAW

EOP-011-1 consolidates the requirements in three existing Reliability Standards: EOP-001-2.1b, EOP-002-3.1 and EOP-003-2 into a single Reliability Standard.

9/13/2012 RSAW

EOP-011-1 consolidates the requirements in three existing Reliability Standards: EOP-001-2.1b, EOP-002-3.1 and EOP-003-2 into a single Reliability Standard.

9/13/2012 RSAW

EOP-011-1 consolidates the requirements in three existing Reliability Standards: EOP-001-2.1b, EOP-002-3.1 and EOP-003-2 into a single Reliability Standard.

5/07/2012 RSAW

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

11/19/2015

1/18/2018

1/18/2018

1/18/2018

1/18/2018

11/19/2015

6/20/2013 RSAW

Entities with newly classified “Remedial Action Scheme” (RAS) resulting from the application of the revised definition must be fully compliant with all Reliability Standards applicable RAS twenty-four (24) months from the Effective Date of the revised definition of RAS. This additional time applies only to existing schemes that must transition to RAS due to the revised definition.

RSAW

3/17/2011 RSAW

3/17/2011 RSAW

4/21/2011 RSAW

A FERC order was issued on June 19, 2014, approving EOP-010-1. Requirement 2 of Reliability Standard EOP-010-1 will not become effective until the first day following retirement of Reliability Standard IRO-005-3.1a.

6/19/2014 RSAW

EOP-011-1 consolidates the requirements in three existing Reliability Standards: EOP-001-2.1b, EOP-002-3.1 and EOP-003-2 into a single Reliability Standard.

RSAW

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

11/6/2014

11/6/2014

11/19/2015

RSAW

RSAW

A FERC order was issued on September 19, 2013, approving FAC-003-3. This standard becomes enforceable on July 1, 2014 for Transmission Owners. For Generator Owners, R3 becomes enforceable on January 1, 2015 and all other requirements (R1, R2, R4, R5, R6, and R7) will become enforceable on January 1, 2016.

9/19/2013 RSAW 10/28/16: Compliance Guidance Updates

RSAW

11/17/2011 RSAW

4/19/2010 RSAW

Entities with newly classified “Remedial Action Scheme” (RAS) resulting from the application of the revised definition must be fully compliant with all Reliability Standards applicable RAS twenty-four (24) months from the Effective Date of the revised definition of RAS. This additional time applies only to existing schemes that must transition to RAS due to the revised definition.

RSAW

3/20/2009 RSAW

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

11/19/2015

4/21/2011

5/30/2018

Replaced INT-006-3

Entities with newly classified “Remedial Action Scheme” (RAS) resulting from the application of the revised definition must be fully compliant with all Reliability Standards applicable RAS twenty-four (24) months from the Effective Date of the revised definition of RAS. This additional time applies only to existing schemes that must transition to RAS due to the revised definition.

RSAW

11/17/2011 RSAW

3/20/2009 RSAW

Replaced INT-004-3. Requirement R3 will become effective on the first calendar day two calendar quarters after the NAESB Electric Industry Registry is able to accept Pseudo-Tie registrations. All existing and future Pseudo-Ties are to be registered in the NAESB Electric Industry Registry. The retirement date for INT-004-3 and the enforcement date for INT-004-3.1 have been coordinated to ensure seamless transition from the original to the errata Reliability Standard on the date of Commission approval for the errata Reliability Standard.

11/26/2014 RSAW

6/30/2014 RSAW

Replaced INT-009-2. The retirement date for INT-009-2 and the enforcement date for INT-009-2.1 have been coordinated to ensure seamless transition from the original to the errata Reliability Standard on the date of Commission approval for the errata Reliability Standard.

11/26/2014 RSAW

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

FERC approved withdrawal of standard

11/19/2015

FERC approved withdrawal of standard

11/19/2015

Replaced INT-010-2. The retirement date for INT-010-2 and the enforcement date for INT-010-2.1 have been coordinated to ensure seamless transition from the original to the errata Reliability Standard on the date of Commission approval for the errata Reliability Standard.

11/26/2014 RSAW

Replaced INT-011-1. The retirement date for INT-011-1 and the enforcement date for INT-011-1.1 have been coordinated to ensure seamless transition from the original to the errata Reliability Standard on the date of Commission approval for the errata Reliability Standard.

11/26/2014 RSAW

5/13/2009 RSAW

RSAW

3/17/2011 RSAW

RSAW

RSAW

3/16/2007 RSAW

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

FERC approved withdrawal of standard

12/4/2015

N/A

N/A

11/19/2015

3/17/2011 RSAW

9/13/2012 RSAW

4/21/2011 RSAW

4/21/2011

RSAW

5/31/2012

5/13/2014

3/17/2011 RSAW

RSAW

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

12/4/2015

11/19/2015

FERC approved withdrawal of standard

11/19/2015

11/19/2015

9/22/2016

RSAW

3/17/2011 RSAW

RSAW

3/16/2007 RSAW

RSAW

3/16/2007 RSAW

3/16/2007 RSAW

RSAW

IRO-018-1(i) became enforceable 4/1/2018, therefore IRO-018-1 will never be enforceable.

VRF designations for Requirement R1 of IRO-018-1 and Requirements R1 and R2 of TOP-010-1 changed to high. RSAW

On September 16, 2010, FERC issued an order (in Docket No. RD10-5-000) approving an interpretation of MOD-001-1, creating MOD-001-1a. The effective date of April 1, 2011 did not change.

9/16/2010 RSAW

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

11/24/2009 RSAW

11/24/2009 RSAW

MOD-010-0 retires midnight of the day immediately prior to the Effective Date of MOD-032-1, Requirement R2, in the particular Jurisdiction in which the new standard is becoming effective.

3/16/2007 RSAW

MOD-011-0 retires midnight of the day immediately prior to the Effective Date of MOD-032-1, Requirement R2, in the particular Jurisdiction in which the new standard is becoming effective.

MOD-012-0 retires midnight of the day immediately prior to the Effective Date of MOD-032-1, Requirement R2, in the particular Jurisdiction in which the new standard is becoming effective.

3/16/2007 RSAW

MOD-013-1 retires midnight of the day immediately prior to the Effective Date of MOD-032-1, Requirement R2, in the particular Jurisdiction in which the new standard is becoming effective.

MOD-014-0 retires midnight of the day immediately prior to the Effective Date of MOD-032-1, Requirement R2, in the particular Jurisdiction in which the new standard is becoming effective.

This Standard was not approved by FERC in Order 693. See Standards Under Development page or Reliability Standards Development Plan for more information.

This standard was not approved by FERC in Order 693. MOD-015-0.1 retires midnight of the day immediately prior to the Effective Date of MOD-032-1, Requirement R2, in the particular Jurisdiction in which the new standard is becoming effective.

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

5/13/2009 RSAW

5/13/2009 RSAW

3/16/2007 RSAW

5/13/2009 RSAW

3/16/2007 RSAW

1/10/2011 RSAW

This Standard was not approved by FERC in Order 693. See Standards Under Development page or Reliability Standards Development Plan for more information.

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

3/20/2014

3/20/2014

3/20/2014

11/19/2015

11/19/2015

This Standard was not approved by FERC in Order 693. See Standards Under Development page or Reliability Standards Development Plan for more information.

Please see the Implementation Plan for specific compliance dates and timeframes. RSAW

Please see the Implementation Plan for specific compliance dates and timeframes. RSAW

RSAW

7/18/2013 RSAW

9/16/2010 RSAW

Entities with newly classified “Remedial Action Scheme” (RAS) resulting from the application of the revised definition must be fully compliant with all Reliability Standards applicable RAS twenty-four (24) months from the Effective Date of the revised definition of RAS. This additional time applies only to existing schemes that must transition to RAS due to the revised definition.

RSAW

11/24/2009 RSAW

Entities with newly classified “Remedial Action Scheme” (RAS) resulting from the application of the revised definition must be fully compliant with all Reliability Standards applicable RAS twenty-four (24) months from the Effective Date of the revised definition of RAS. This additional time applies only to existing schemes that must transition to RAS due to the revised definition.

RSAW

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

2/19/2015

5/1/2014

11/4/2014

6/19/2014

6/7/2018

RSAW

RSAW

Please see the implementation plan for specific compliance dates and timeframes. 5/1/2014 RSAW

RSAW

RSAW

9/13/2012 RSAW

9/15/2011 RSAW

Please note: The effective date in the standard refers to the retirements in PER-004-1. 11/18/2010 RSAW

11/18/2010 RSAW

RSAW

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

FERC approved withdrawal of standard

See Implementation Plan for phased-in compliance dates.

N/A

1/10/2011

9/19/2013

9/26/2011

5/13/2015

5/29/2015

N/A

Requirements 2, 5 and 6 are inactive as of 3/31/2017 due to TOP/IRO standards. Replaced by TOP/IRO standards, PER-006-1 and

5/29/2015 RSAW

This Standard was not approved by FERC in Order 693. See Standards Under Development page or Reliability Standards Development Plan for more information.

RSAW

This standard has a phased implementation. Please see the Implementation Plan for further compliance date information. This standard was approved by FERC on 10/20/2011.

10/20/2011

This Standard was not approved by FERC in Order 693. See Standards Under Development page or Reliability Standards Development Plan for more information.

5/29/2015 RSAW

The Implementation Plan for PRC-004-4 provides that PRC-004-4 becomes enforcable on the effective date for PRC-004-3. Because of this, PRC-004-3 will never become enforceable.

PRC-004-4 was superseded by PRC-004-4(i) and will never be enforceable.

RSAW

RSAW

4/21/2011

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

11/19/2015 N/A

Replaced with PRC-005-1.1b

12/19/2013

To be retired 12/31/2016 by PRC-005-6 Implementation Plan. 5/29/2015

Retired by PRC-005-6; PRC-005-2(ii) was never enforceable11/19/2015

Retired by PRC-005-6; PRC-005-3 was never enforceable.

Retired by PRC-005-6; PRC-005-3(i) was never enforceable.

NERC filed a joint petition March 9, 2018 for approval of retirement of PRC-004-WECC-2.

Entities with newly classified “Remedial Action Scheme” (RAS) resulting from the application of the revised definition must be fully compliant with all Reliability Standards applicable RAS twenty-four (24) months from the Effective Date of the revised definition of RAS. This additional time applies only to existing schemes that must transition to RAS due to the revised definition.

9/19/2013 RSAW

The enforcement date for PRC-005-2 has been corrected from the date first posted. The enforcement date for PRC-005-2 will be April 1, 2015, which is the first date entities must be compliant with part of the standard. The implementation plan for PRC-005-2 includes specific compliance dates and timeframes for each of the Requirements. The regulatory approval date in the U.S. is February 24, 2014. Entities should use this date as a starting point for calculating the compliance dates for each of the Requirements as detailed in the implementation plan.

RSAW

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

Retired by PRC-005-6; PRC-005-3(ii) was never enforceable.11/19/2015

Retired by PRC-005-6; PRC-005-4 was never enforceable.

12/18/2015

12/18/2015

2/21/2013 N/A

4/29/2013 N/A

Approved by Board of Trustees; replaced and retired by PRC-005-6; PRC-005-5 was never enforceable.

Supplemental Reference and FAQ Please see the implementation plan for guidance on phased-in enforcement dates. RSAW

3/04/2015 RSAW

Reliability Standard PRC-006-3 revises the regional Variance for the Québec Interconnection as necessary to account for the physical characteristics and operational practices of that Interconnection. No changes have been made to any of the continent-wide Requirements of Reliability Standard PRC-006-21 nor the regional Variance for the Western Electricity Coordinating Council Interconnection.

RSAW

See the implementation plan for guidance on phased-in enforcement dates

3/16/2007 RSAW

3/16/2007 RSAW

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

11/19/2015

11/19/2015 RSAW

3/16/2007 RSAW

This Standard was not approved by FERC in Order 693. See Standards Under Development page or Reliability Standards Development Plan for more information.

Because Reliability Standards PRC-012-0, PRC-013-0, and PRC-014-0 were never approved or remanded, Reliability Standards PRC-012-1, PRC-013-1, and PRC-014-1 were only developed for ‘completeness’ and are not enforceable.

This Standard was not approved by FERC in Order 693. See Standards Under Development page or Reliability Standards Development Plan for more information.

Because Reliability Standards PRC-012-0, PRC-013-0, and PRC-014-0 were never approved or remanded, Reliability Standards PRC-012-1, PRC-013-1, and PRC-014-1 were only developed for ‘completeness’ and are not enforceable.

This Standard was not approved by FERC in Order 693. See Standards Under Development page or Reliability Standards Development Plan for more information.

Because Reliability Standards PRC-012-0, PRC-013-0, and PRC-014-0 were never approved or remanded, Reliability Standards PRC-012-1, PRC-013-1, and PRC-014-1 were only developed for ‘completeness’ and are not enforceable.

3/16/2007 RSAW

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

11/19/2015

11/19/2015

11/19/2015

3/20/2014

5/29/2015

Entities with newly classified “Remedial Action Scheme” (RAS) resulting from the application of the revised definition must be fully compliant with all Reliability Standards applicable RAS twenty-four (24) months from the Effective Date of the revised definition of RAS. This additional time applies only to existing schemes that must transition to RAS due to the revised definition.

RSAW

5/13/2009 RSAW

Entities with newly classified “Remedial Action Scheme” (RAS) resulting from the application of the revised definition must be fully compliant with all Reliability Standards applicable RAS twenty-four (24) months from the Effective Date of the revised definition of RAS. This additional time applies only to existing schemes that must transition to RAS due to the revised definition.

RSAW

3/16/2007 RSAW

Entities with newly classified “Remedial Action Scheme” (RAS) resulting from the application of the revised definition must be fully compliant with all Reliability Standards applicable RAS twenty-four (24) months from the Effective Date of the revised definition of RAS. This additional time applies only to existing schemes that must transition to RAS due to the revised definition.

RSAW

3/16/2007 RSAW

Please see the Implementation Plan for specific compliance dates and timeframes. The standard become inactive 6/30/16.

Please see the Implementation Plan for Version 1 for specific compliance dates and timeframes. RSAW

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

11/19/2015

3/20/2014

5/29/2015

Replaces PRC-025-1. 5/2/2018

3/17/2016

This Standard was not approved by FERC in Order 693. See Standards Under Development page or Reliability Standards Development Plan for more information.

3/16/2007 RSAW

3/16/2007 RSAW

07/17/2014 RSAW

Entities with newly classified “Remedial Action Scheme” (RAS) resulting from the application of the revised definition must be fully compliant with all Reliability Standards applicable RAS twenty-four (24) months from the Effective Date of the revised definition of RAS. This additional time applies only to existing schemes that must transition to RAS due to the revised definition.

RSAW

Please see the Implementation Plan for specific compliance dates and timeframes. The standard become inactive 6/30/16.

Please see the Implementation Plan for Version 1 for specific compliance dates and timeframes. RSAW

See Implementation Plan. For applicable relays where the entity has determined replacement or removal is not necessary, the entity shall be compliant by 10/1/2019. For applicable relays where the entity has determined replacement or removal is necessary, the entity shall be compliant by 10/1/2021.

7/17/2014 RSAW

Requirement R1 is effective 1/1/2018. Requirements R2, R3 and R4 are effective 1/1/2020. RSAW

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

6/7/2018

FERC approved withdrawal of standard

11/19/2015

4/17/2017

FERC approved withdrawal of standard

11/19/2015

FERC approved withdrawal of standard

11/19/2015

Redline version of Implementation Plan

9/15/2011 RSAW

RSAW

RSAW

9/13/2012 RSAW

RSAW

3/17/2011 RSAW

For the Requirement R3 and R4 VSLs only, the intent of the SDT is to start with the Severe VSL first and then to work your way to the left until you find the situation that fits. In this manner, the VSL will not be discriminatory by size of entity. If a small entity has just one affected reliability entity to inform, the intent is that that situation would be a Severe violation.

RSAW

1/22/2009 RSAW

3/17/2011 RSAW

3/17/2011 RSAW

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

N/A

9/22/2016

See Implementation Plan for phased-in compliance dates. 9/22/2016

11/13/2015

3/16/2007 RSAW

6/18/2014

6/16/2007 RSAW

TOP-010-1(i) became enforceable 4/1/2018, therefore TOP-010-1 will never be enforceable.

VRF designations for Requirement R1 of IRO-018-1 and Requirements R1 and R2 of TOP-010-1 changed to high. RSAW

TPL-001-4 was adopted by the Board of Trustees as TPL-001-3, but a discrepancy in numbering was identified and corrected prior to filing with the regulatory agencies.

10/17/2013 RSAW

RSAW 10/28/16: Compliance Guidance Updates

RSAW

RSAW

5/29/2015 RSAW

RSAW

Related Documents Lessons Learned Compliance GuidancePublic Notes FERC Orders(Date Issued)

RSAWs(Enforceable

Standards Only)

N/A

N/A

NERC filed a joint petition March 7, 2018 for approval of retirement of VAR-002-WECC-2. 3/03/2015

3/03/2015

Requirement R3 has an effective date of July 1, 2017 for units placed in first-time service after regulatory approval. R3 has an effective date of July 1, 2022 for units placed in service prior to final regulatory approval.

Requirement R3 has an effective date of July 1, 2017 for units placed in first-time service after regulatory approval. R3 has an effective date of July 1, 2022 for units placed in service prior to final regulatory approval.

Version Date Owner

1.0 10/01/2015

1.1 10/9/2015

1.2 10/13/2015 Standards Information (bkn)

1.3 10/22/2015 Standards Information (mb)

1.4 11/16/2015 Standards Information (mb)

1.5 12/1/2015 Standards Information (mb)

1.6. 12/7/2015 Standards Information (mb)

1.7 12/8/2015 Standards Information (mb)

2 12/11/2015 Standards Information (mb)

This is a living document that is updated based on standard(s) status changes and currentRSAWs once they are posted to the Compliance and Enforcement web page.

Standards Information

Email sarcomm@nerc.net with questions

Standards Information

2.1 12/18/2015 Standards Information (mb)

2.2 12/29/2015 Standards Information (mb)

2.3 12/31/2015 Standards Information (NS)

2.4 1/1/2016 Standards Information (mb)

2.5 1/6/2016 Standards Information (NS)

2.6 1/19/2016 Standards Information (mb)

2.7 1/20/2016 Standards Information (NS)2.8 1/21/2016 Standards Information (NS)

2.9 1/27/2016 Standards Information (mb)

2.1 2/3/2016 Standards Information (NS)2.11 2/4/2016 Standards Information (NS)

2.12 2/5/2016 Standards Information (NS)

2.13 2/8/2016 Standards Information (NS)

2.14 2/16/2016 Standards Information (mb)2.15 2/17/2016 Standards Information (mb)2.16 2/18/2019 Standards Information (NS)

2.17 2/26/2016 Standards Information (mb)

2.18 3/2/2016 Standards Information (mb)

2.18 3/2/2016 Standards Information (mb)

2.19 3/14/2016 Standards Information (mb)2.2 3/15/2016 Standards Information (mb)

2.21 3/15/2016 Standards Information (mb)2.22 3/29/2016 Standards Information (mb)

2.23 3/30/2016 Standards Information (mb)

2.24 4/1/2016 Standards Information (mb)

2.25 4/11/2016 Standards Information (mb)2.26 4/14/2016 Standards Information (mb)2.27 4/22/2016 Standards Information (mb)2.28 4/27/2016 Standards Information (mb)2.29 5/10/2016 Standards Information (mb)

2.3 5/17/2016 Standards Information (mb)

2.31 5/26/2016 Standards Information (mb)2.32 6/3/2016 Standards Information (mb)

3 6/9/2016 Standards Information (mb)

3.1 6/24/2016 Standards Information (mb)

3.2 7/1/2016 Standards Information (mb)

3.2 7/1/2016 Standards Information (mb)

3.3 7/11/2016 Standards Information (mb)3.4 7/19/2016 Standards Information (mb)3.5 7/25/2016 Standards Information (mb)3.6 7/28/2016 Standards Information (mb)3.7 8/8/2016 Standards Information (jmb)3.8 8/15/2016 Standards Information (mb)3.9 8/16/2016 Standards Information (mb)3.1 8/17/2016 Standards Information (mb)

3.11 8/26/2016 Standards Information (mb)3.12 9/8/2016 Standards Information (mb)3.13 9/29/2016 Standards Information (mb)3.14 10/3/2016 Standards Information (mb)3.15 10/5/2016 Standards Information (mb)3.16 10/14/2016 Standards Information (mb)3.17 11/4/2016 Standards Information (mb)3.18 11/7/2016 Standards Information (mb)3.19 11/7/2016 Standards Information (mb)

3.2 11/9/2016 Standards Information (mb)

3.2 11/9/2016 Standards Information (mb)3.21 11/28/2016 Standards Information (mb)3.22 11/29/2016 Standards Information (mb)

3.23 1/4/2017 Standards Information (mb)

3.24 1/5/2017 Standards Information (mb)

3.25 1/20/2017 Standards Information (mb)

3.26 1/23/2017 Standards Information (mb)

3.27 1/25/2017 Standards Information (mb)3.28 2/6/2017 Standards Information (mb)3.29 2/16/2017 Standards Information (mb)3.3 3/2/2017 Standards Information (mb)

3.31 3/3/2017 Standards Information (mb)3.32 3/8/2017 Standards Information (mb)3.33 3/8/2017 Standards Information (mb)

3.34 3/10/2017 Standards Information (mb)

3.35 3/15/2017 Standards Information (mb)

4 3/15/2017 Standards Information (mb)4.1 3/17/2017 Standards Information (mb)4.2 3/28/2017 Standards Information (mb)4.2 3/28/2017 Standards Information (mb)4.2 3/28/2017 Standards Information (mb)

4.3 4/3/2017 Standards Information (mb)

4.3 4/3/2017 Standards Information (mb)

4.4 4/10/2017 Standards Information (mb)

4.5 4/24/2017 Standards Information (mb)

4.6 5/2/2017 Standards Information (mb)

4.7 5/22/2017 Standards Information (mb)

4.8 5/25/2017 Standards Information (mb)4.9 6/12/2017 Standards Information (mb)4.1 6/21/2017 Standards Information (mb)

4.11 7/3/2017 Standards Information (mb)

4.12 7/14/2017 Standards Information (mb)

New Pending Inactive Status: A standard becomes Pending Inactive once determined that it will not become enforceable and has been superseded by another standard. The status will change to inactive at midnight on the day immediately prior to the effective date of the superseding standard.

4.13 8/28/2017 Standards Information (mb)

4.14 9/6/2017 Standards Information (mb)4.15 9/7/2017 Standards Information (mb)4.16 9/12/2017 Standards Information (mb)4.17 9/21/2017 Standards Information (mb)

4.18 9/27/2017 Standards Information (mb)

4.19 10/2/2017 Standards Information (mb)

4.2 10/4/2017 Standards Information (mb)

4.21 10/5/2017 Standards Information (mb)

4.22 10/11/2017 Standards Information (mb)4.23 10/12/2017 Standards Information (mb)

4.24 10/12/2017 Standards Information (mb)

4.25 10/25/2017 Standards Information (mb)4.26 11/12/2017 Standards Information (mb)4.27 11/15/2017 Standards Information (mb)4.28 12/5/2017 Standards Information (mb)

4.29 1/2/2018 Standards Information (mb)

4.3 1/18/2018 Standards Information (mb)

4.31 1/22/2018 Standards Information (mb)4.32 1/24/2018 Standards Information (mb)4.33 2/5/2018 Standards Information (NS)4.34 2/16/2018 Standards Information (NS)4.35 3/8/2018 Standards Information (NS)4.36 3/12/2018 Standards Information (NS)

4.37 3/26/2018 Standards Information (NS)

4.38 3/29/2018 Standards Information (NS)

4.39 4/23/2018 Standards Information (NS)

4.4 4/30/2018 Standards Information (NS)

4.41 5/14/2018 Standards Information (NS)

4.42 5/25/2018 Standards Information (NS)

4.43 6/6/2018 Standards Information (NS)

4.44 6/15/2018 Standards Information (NS)

4.45 6/26/2018 Standards Information (NS)

4.46 7/2/2018 Standards Information (NS)

Change Tracking

New

PRC-023-2 corrected Enforcement date to 7/1/2012PRC-006-1 removed duplicate

PRC-006-1 updated status to inactive effective 9/30/2015PRC-006-2 updated status to mandatory subject to enforcement effective 10/1/2015

CIP-014-1 updated status to inactive effective 10/1/2015CIP-014-2 updated status to mandatory subject to enforcement effective 10/2/2015

BAL-001-TRE-1 added COM-001-2 updated status to mandatory subject to enforcement effective 10/1/2015

PRC-006-NPCC-1 updated status to mandatory subject to enforcement effective 7/01/2015PRC-006-SERC-01 updated status to mandatory subject to enforcement effective 4/01/2014

Updated Enforcement and Inactive dates for: IRO-006-EAST-2, IRO-006-EAST-1, IRO-009-1, IRO-009-2

This is a living document that is updated based on standard(s) status changes and currentRSAWs once they are posted to the Compliance and Enforcement web page.

NUC-001-2.1 Added inactive date 12/31/2015PRC-005-3 Corrected the inactive date to 12/31/2015

PRC-005-5 Updated to Filed and PendingPRC-027-1 AddedBAL-002-2 Added

MOD-031-2 AddedPRC-005-6 Added

Added Enforcement Dates: PRC-010-1, PRC-010-2, EOP-011-1, PRC-004-5, BAL-003-1.1, COM-001-2.1, VAR-001-4.1

Added Inactive Dates:EOP-001-2.1b, EOP-002-3.1, EOP-003-2, PRC-004-4, PRC-010-0, PRC-020-1, PRC-021-1, PRC-022-1, PRC-010-1, BAL-003-1, COM-001-2, VAR-

001-4

Added Enforcement Dates:TOP-001-3, TOP-002-4, TOP-003-3, IRO-001-4, IRO-002-4, IRO-008-2, IRO-010-2, IRO-014-3, IRO-017-1

Added Inactive Dates:IRO-001-1.1, IRO-002-2, IRO-003-2, IRO-004-2, IRO-005-3.1a, IRO-008-1, IRO-010-1a, IRO-14-1, IRO-015-1

IRO-016-1, PER-001-0.2, TOP-001-1a, TOP-002-2.1b, TOP-003-1, TOP-004-2, TOP-005-2a, TOP-006-2, TOP-007-0, TOP-008-1Updated:

PRC-004-3(i), PRC-004-4(i), PRC-004-5, PRC-004-5(i)

Updated spreadsheet to include additional columns: Implementation Plans, RSAWs, Notes, FERC Order Date.

Changed spreadsheet name from US | Standards | Purpose | Status to: US Standard One-Stop-Shop

Corrected PRC-002-2 status to "Subject to Future Enforcement"

Updated PRC-005-2(i) Implementation Plan (Errata May 2015)

Updated implementation plans for PRC-004-4(i) and PRC-004-5(i)Added project age for PRC-00404(i) and PRC-004-5(i). Updated RSAWS for EOP-005-2 and IRO-009-2.

Updated status BAL-002-2 - "Filed and pending regulatory approva"Updated status PRC-023-2 to "Inactive"

Inactive standards: TPL-001-0.1(i), TPL-002-0(i)b, TPL-003-0(i)b, TPL-004-0(i)a, Added BAL-005-1

Added FAC-001-3 and FAC-003-4

Changed status of FAC-003-4 to Filed and Pending Reg Approval

Updated status of PRC-026-1

Added inactive dates for the following standards:PRC-005-2(i), PRC-005-1b, PRC-005-2(ii), PRC-005-3, PRC-005-3(i), PRC-005-3(ii), PRC-005-4, PRC-005-5

Added enforcement date for PRC-005-6

PRC-005-2(i) Changed the inactive date to 12/31/2016Changed the status of the following standards to inactive: PRC-004-3, PRC-004-3(i), PRC-004-4 and PRC-004-5.

Changed the status to inactive for: TPL-001-0.1, TPL-002-0b, TPL-003-0b, TPL-004-0a, PRC-005-2(ii), PRC-005-3, PRC-005-3(i), PRC-005-3(ii), PRC-005-4, PRC-005-5, IRO-009-1,

NUC-001-2.1, FAC-002-1, FAC-001-1Changed the status to Mandatory Subject to Enforcement:

FAC-001-2, FAC-002-2, IRO-009-2, NUC-001-3, PRC-005-6

Updated MOD-026-1 to remove inactive dateChanged status of PRC-004-5(i) to Subject to Future Enforcement

Added Lessons Learned column and link to CIP Version 5 Transition Program for V5 and V6 CIP standardsUpdated status and enforcement dates for: CIP-003-6, CIP-004-6, CIP-006-6, CIP-007-6, CIP-009-6, CIP-010-2, CIP-011-2

Added Inactive dates for: CIP-003-5, CIP-004-5.1, CIP-006-5, CIP-007-5, CIP-009-5, CIP-010-1, CIP-011-1

Updated status, FERC Order link, enforcement date and public notes for: EOP-004-3, PRC-023-4, FAC-010-3, FAC-011-3, MOD-030-3, MOD-029-2a, PRC-015-1, PRC-004-WECC-2, PRC-016-1. Added inactive dates for

Added implementation plan for TPL-001-4, TPL-002-0(i)b, TPL-003-0(i)b, TPL-004-0(i)b. Added FERC Order date/link and enforcement date for TPL-001-0.1(i), TPL-02(i)b, TPL-003-0(i)b, TPL-004-0(i)a, PRC-017-1. Updated inactive dates for PRC-017-0 and PRC-017-1.

Updated MOD-031-2 enforcement date and MOD-031-1 inactive dateUpdated CIP V5 enforcement and inactive dates

CIP-002-3, CIP-003-3, CIP-004-3a, CIP-005-3a, CIP-006-3c, CIP-007-3a, CIP-008-3, CIP-009-3 updated inactive date based on 2/25/16 FERC Order.

Update inactive dates for PRC-008-0 and PRC-011-0.Added PRC-005 inactive standards for added clarity.Added a link to Glossary of Terms on Resource tab

Added a Related Documents column for supporting material associated with the standard

Added withdrawn status to: TOP-001-2, TOP-002-3, TOP-003-2, IRO-001-3, IRO-002-3, IRO-005-4, IRO-014-2, PRC-001-2

PRC-012-1, PRC-013-1 and PRC-014-1: changed status to Filed and Pending Regulatory Approval and added a public note.Corrected inactive date of PRC-004-4(i) to 4/1/2017

Changed status of BAL-005-1 and FAC-001-3Changed status of FAC-003-4. Added dates for FAC-003-3 and FAC-003-4

Added IRO-018-1, TOP-010-1, PRC-012-2

Updated status of IRO-018-1 and TOP-010-1 Added link to CIP V5 Effective Dates for associated standards

Replaced BAL-001-TRE-1

Added RSAWS: FAC-003-4 and MOD-031-2Updated MOD-019-0.1 to show as inactiveAdded updated RSAWs for FAC-003-4 and PER-005-2 (Errata Changes)changed status of INT-011-1.1 to inactivechanged status of PRC-012-2 to Filed and PendingAdded COM-001-3. Filed and PendingAdded PER-006-1 Pending Regulatory ApprovalPRC-002-NPCC-01 InactivePRC-027-1 Implementation Plans addedPRC-027-1 and PER-006-1 Filed and Pending Regulatory ApprovalIRO-018-1, TOP-010-1 and TPL-007-1 Subject to Future Enforcement Dates status changechanged status: FAC-003-3, FAC-003-4, MOD-031-1, MOD-031-2IRO-018-1, TOP-010-1 and TPL-007-1 Enforcement Dates entered and Updated Implementation Plan linkedAdded RSAWs IRO-010-2 and TOP-003-3changed status COM-001-3; added inactive date for COM-001-2.1; added CIP-002-5.1a Added IRO-018-1(i), TOP-010-1(i) and BAL-002-WECC-2achanged the status of IRO-018-1(i) and TOP-010-1(i) to Filed and Pending Regulatory approval

changed status of BAL-002-WECC-2a to Filed and Pending Regulatory approvalchanged status of CIP-002-5.1a to Filed and Pending Regulatory approvalAdded a Compliance Guidance link to the following standards: CIP-014-1, FAC-003-3, and TPL-007-1

Changed status of IRO-006-EAST-1 and IRO-006-EAST-2Updated/Add RSAW links for: COM-002-4, PER-005-2, PRC-002-2, IRO-006-EAST-2, PRC-004-4(i), PRC-019-2, NUC-001-3

Added RSAWS: BAL-001-2, MOD-031-1, PRC-024-2Added Revised RSAW: PRC-005-6

Added new column: Compliance Guidance Added link to CIP V5 standards referencing 5/20/2016 updates

Subject to enforcement: BAL-001-2, COM-002-4, CIP-002-5.1, CIP-003-6, CIP-004-6, CIP-005-5, CIP-006-6, CIP-007-6, CIP-008-5, CIP-009-6, CIP-010-2, CIP-011-2, MOD-025-2, MOD-031-1, PER-005-2, PRC-002-2, PRC-004-4(i), PRC-019-2, PRC-024-2

Inactive: BAL-001-1, CIP-002-3, CIP-002-3b, CIP-003-3, CIP-003-3a, CIP-003-5, CIP-004-3a, CIP-004-5.1, CIP-005-3a, CIP-006-3C, CIP-006-5, CIP-007-3a, CIP-007-3b, CIP-007-5, CIP-008-3, CIP-009-3, CIP-009-5, CIP-010-1, CIP-011-1, COM-001-1.1 R4, COM-002-2, COM-002-2A, COM-002-3, MOD-010-0, MOD-011-0, MOD-012-0, MOD-013-1, MOD-014-0, MOD-015-0, MOD-015-0.1, MOD-016-1.1, MOD-017-0.1, MOD-018-0, MOD-021-1, MOD-024-1, MOD-025-1, PER-005-1, PRC-002-1, PRC-003-1, PRC-004-2.1(i)a, PRC-004-3, PRC-004-3(i), PRC-004-4, PRC-019-1, PRC-024-1

Added RSAWs IRO-001-4, IRO-002-4, IRO-008-2, MOD-029-2a, MOD-030-3, PRC-015-1, PRC-016-1, PRC-017-1, PRC-023-4 which become effective on April 1, 2017. PRC-004-5(i) becomes effective on April 2, 2017.

changed status of TOP-003-3 to Mandatory Subject to Enforcement

updated the status of BAL-002-2

Changed status of BAL-002-WECC-2 to inactive; changed status of BAL-002-WECC-2a to Subject to Mandatory EnforcementUpdated BAL-002-2 with effective date. Added Inactive date for BAL-002-1Added EOP-004-4, EOP-005-3, EOP-006-3, and EOP-008-2 as Pending Regulatory FilingAdded CIP-003-7, IRO-002-5, TOP-001-4, VAR-501-WECC-3Changed status of CIP-003-7 to Filed and Pending Regulatory ApprovalChanged status of IRO-002-5 and TOP-001-4 to Filed and Pending Regulatory ApprovalAdded RSAWs for TOP-001-3, FAC-010-3, EOP-011-1, and EOP-004-3

Changed header column from Enforcement Date to 'Effective Date of Standard'Changed BAL-004-0 to inactiveChanged the status of EOP-004-4, EOP-005-3, EOP-006-3, and EOP-008-2 to Filed and Pending Regulatory ApprovalChanged the status of VAR-501-WECC-3 to Filed and Pending Regulatory ApprovalChanged the status of TOP-007-WECC-1a to Inactive

Added RSAW for MOD-033-1

Changed the status of VAR-501-WECC-3 to Subject to Future Enforcement and added Inactive date for VAR-501-WECC-2

Changed the status of BAL-002-1a to inactive. Changed the status of BAL-004-0 to Subject to Enforcement. (See Public Note column.)Replaced updated RSAWS for COM-001-2.1, TOP-001-3, TPL-007-1, VAR-001-4.1 and MOD-025-2Added RSAW for COM-001-3CIP-014-1 changed to inactive status; IRO-010-2 to mandatory enforcement

Updated project page link for PRC-014-1 to project 2010-05.3 phase 3

Changed status of TOP-010-1(i), TOP-010-1, IRO-018-1(i) and IRO-018-1 and added Enforcement Dates.Changed the status and dates of CIP-002-5.1 and CIP-002-5.1a

Added RSAWs for TOP-002-4 and FAC-011-3. Changed the status of BAL-004-0 to Pending Inactive. Changed the Board Adopted Date of CIP-006-6 to 11/13/2014.

Added RSAWS for IRO-014-3, IRO-017-1, and PRC-010-2.Changed the status of BAL-002-1a to Pending Inactive

Changed status: VAR-501-WECC-3 to Filed and Pending Regulatory Approval;Changed status to Pending Inactive: PRC-020-0, PRC-012-0, PRC-012-1, PRC-13-0, PRC-013-1, PRC-014-0, PRC-014-1, RIO-018-1, TOP-010-1

New Pending Inactive Status: A standard becomes Pending Inactive once determined that it will not become enforceable and has been superseded by another standard. The status will change to inactive at midnight on the day

Changed to Mandatory Enforceable: EOP-004-3, EOP-011-1, FAC-010-3, FAC-011-3, IRO-001-4, IRO-002-4, IRO-008-2, IRO-014-3, IRO-017-1, MOD-029-2a, MOD-030-3, PRC-004-5(i), PRC-004-WECC-2, PRC-010-2, PRC-015-1, PRC-016-1, PRC-017-1, PRC-023-4, TOP-001-3, TOP-002-4

Changed to Inactive: EOP-001-2.1b, EOP-002-3.1, EOP-003-2, EOP-004-2, FAC-010-2.1, FAC-011-2, IRO-001-1.1, IRO-002-2, IRO-003-2, IRO-005-3.1a, IRO-008-1, IRO-010-1a, IRO-014-1, IRO-015-1, IRO-016-1, MOD-029-1a, MOD-030-2, PER-001-0.2, PRC-004-4(i), PRC-004-5, PRC-004-WECC-1, PRC-010-0, PRC-010-1, PRC-015-0, PRC-016-0.1, PRC-017-0, PRC-022-1, PRC-023-3, TOP-001-1a, TOP-002-2.1b, TOP-003-1, TOP-004-2, TOP-005-2a, TOP-006-2, TOP-007-0, TOP-008-1

Changed status of IRO-002-5 and TOP-001-4 to Subject to Future Enforcement and added Effective Dates. Added Inactive dates for IRO-002-4 and TOP-001-3.

MOD-033-1, TPL-007-1 and VAR-501-WECC-3 changed to subject to enforcement. VAR-501-WECC-2 changed to inactive status.Added public note for PRC-025-1.

Added VAR-501-WECC-3.1, BAL-502-RF-03, and PRC-006-3Changed the status of BAL-502-RF-03 to Filed and Pending Regulatory ApprovalChanged the status of PRC-006-SERC-02 to Filed and Pending Regulatory ApprovalAdded effective date for PRC-006-3 and inactive date for PRC-006-2.

Changed the status of: COM-001-3, COM-001-2.1; IRO-002-5, IRO-002-4; PRC-006-3, PRC-006-2

Adjusted the effective date of VAR-002-4.1 and inactive date of VAR-002-4Added RSAWS: BAL-002-2, IRO-018-1(i), TOP-010-1(i), PRC-026-1

Added effective dates for PRC-006-SERC-02, BAL-502-RF-03 . Added inactive dates for PRC-006-SERC-01, BAL-502-RF-02Added TPL-007-2Updated TOP-006-3 status to inactiveUpdated RSAWS: PRC-006-3, VAR-001-4.2, and VAR-002-4.1

Changed status to Subject to Future Enforcement: EOP-004-4, EOP-005-3, EOP-006-3, EOP-008-2Changed status of TPL-007-2 to Filed and Pending Regulatory ApprovalUpdated inactive date for BAL-002-2 and added effective date for BAL-002-2(i).Added PRC-025-2, FAC-501-WECC-2 and BAL-004-WECC-3 as Pending Regulatory Filing.Added public notes for VAR-002-WECC-2Updated status of BAL-004-WECC-3 to Filed and Pending Regulatory Approval. Added public note.

Added Inactive date to BAL-004-0 and updated status to Inactive.

Updated public note for CIP-003-6. Added PER-003-2 as Filed and Pending Regulatory Approval.

Updated the following standards: BAL-002-2(i), CIP-005-6, CIP-010-3, CIP-013-1, PRC-006-SERC-02, VAR-001-4.2, VAR-002-4.1. Added RSAW IRO-002-5.

Changed the status of CIP-005-6, CIP-010-3 and CIP-013-1 to Filed and Pending Regulatory Approval.BAL-005-1, FAC-001-3, PRC-012-2 FERC approved - Effective Dates to be entered soon.VAR-001-4.2, VAR-002-4.1, VAR-501-WECC-3.1 - FERC approved - Effective Dates to be entered soon.

Added Effective Date for PRC-012-2. Added Inactive Dates for: PRC-012-1, PRC-013-1, PRC-014-1, PRC-015-1, PRC-016-1. Added a public note for PRC-006-3 for clarification.

Added Effective Dates for BAL-005-1, FAC-001-3, VAR-001-4.2, VAR-002-4.1, VAR-501-WECC-3.1. Added Inactive Dates for: VAR-001-4.1, VAR-002-4, VAR-501-WECC-3, BAL-005-0.2b, BAL-006-2, FAC-001-2

VAR-001-4.2 and VAR-501-WECC-3.1 were updated to reflect a 9/26/17 effective date. VAR-001-4.1 and VAR-501-WECC-3 inactive dates were updated to reflect 9/25/2017.

Changed the status of the following to subject to enforcement: BAL-002-2; BAL-502-RF-03; PRC-006-SERC-02; PRC-026-1.Changed the status of the following to inactive: BAL-002-1; BAL-502-RFC-02; PRC-006-SERC-01

Replace with an errata Implementation Plan for TPL-007-2. Non-substantive changes were made to ensure that, in the event of prompt regulatory approval, entities would not have to comply with TPL-007 requirements under the TPL-007-2 Implementation Plan before the dates originally set forth in the TPL-007-1 Implementation Plan.

Added effective date to EOP-004-4, EOP-005-3, EOP-006-3, EOP-008-2. Added RSAWs for BAL-003-1.1 and INT-004-3.1 to reflect correct standards' names. Updated status of PRC-025-2and FAC-501-WECC-2 to Filed and Pending.

Added effective date and updated IRO-018-1(i), TOP-010-1(i) and BAL-002-2(i) status to Subject to Enforcement. Added Inactive dates to IRO-018-1, TOP-010-1 and updated status to Inactive. Added inactive date to EOP-004-3, EOP-005-2, EOP-006-2 and EOP-008-1. Updated status of EOP-004-4, EOP-005-3, EOP-006-3 and EOP-008-2 to Subject to Future Enforcement.

Updated status of CIP-003-7 to "Subject to Future Enforcement" and added effective date; Added Inactive Date for CIP-003-6. Added FERC Order.

Updated status of PRC-025-2 to "Subject to Future Enforcement"; added effective date. Added FERC Order link and date. Added inactive date to PRC-025-1.

Updated link to the CIP-003-7 Implementation Plan.

Updated status of PER-006-1 and PRC-027-1 to Subject to Future Enforcement; added effective date. Added inactive dates to PRC-001-1.1(ii).

Updated public note for CIP-003-6. Updated status of BAL-004-WECC-3 and FAC-501-WECC-2. Added inactive dates to BAL-004-WECC-2 and FAC-501-WECC-1.

Updated status of FAC-501-WECC-1, PRC-025-1 and TOP-001-3 to Inactive. Updated status of FAC-501-WECC-2, PRC-025-2 and TOP-001-4 to Mandatory Subject to Enforcement. Added FERC Order date and link for TOP-001-4.

The One-Stop-Shop is jointly owned by Standards and Compliance.

Standards

Glossary of Terms

NERC and FERC Filings and Orders/Rules

NERC Standards Numbering System

Reliability Standards

US Enforcement Dates

The One-Stop-Shop is jointly owned by Standards and Compliance.

Compliance

Navigate to the RSAW page from the NERC homepage:

Reliability Standard Audit Worksheets (RSAWs)

-        Navigate to “Compliance & Enforcement” (either through ‘Program Areas & Departments’ in the heading row or the middle box in the bottom row of the main section of the NERC homepage)

-        In the navigation section on the left hand side, under the ‘Compliance Tools and Auditor Resources’ section heading click on the link to “Reliability Standards Audit Worksheet (RSAWs)”

Implementation Study, Lessons Learned, and FAQs