Você está na página 1de 181

INSTRUCTIONS FOR EXTERNAL STAKEHOLDERS

To Registered Entities – British Columbia Mandatory Reliability Standards Program,

Please review each new and revised Standard (and corresponding redlines) as per the links provided from the BC Hydro Re
www.bchydro.com/energy-in-bc/our_system/transmission/transmission-system/reliability.html.

NOTE: The 7 new and 30 revised Standards have been broken out into their requirements to enable stakeholders to provid
detailed comments per requirement.

Complete the 'Stnds Feedback Survey Form' (the yellow tab), and for each Standard assessed, please complete the follow

a. Insert the name and applicable functions of your registered entity at the top of the 'Stnds Feedback Survey Form'
as indicated by the red text.

b. Entity Comments, Organizational Activities and Reliability/Suitability Impact (Column "I"): Please advise if there
necessary to maintain compliance, or if changes are required, please describe a list of high-level incremental activities re
Please also indicate if there are any noted reliability/suitability impacts (technical or administrative) that could pose a cha
Examples of suitability impacts: References made to unapproved standards, standard requirements depend on NERC
functional roles/responsibilities (i.e. Planning Coordinator), references to undefined processes/procedures, etc..

c. Estimated Incremental/New Costs Associated with Revision/New Standard/Requirement, if any ($) (Columns “J”
if any associated with:
- the adoption of a new Standard; or
- a revision to a Standard compared to the immediately preceding version currently adopted by BCUC.

Please indicate which costs are one-time versus ongoing, and ensure the assumptions associated with each estimate are
BC Hydro will use this information to develop recommendations to the BCUC regarding the potential impacts of each
reliability Standard on registered entities for inclusion in the Report.

d. BCUC Implementation Time (Column “L”):


Please include an assessment of the amount of time your organization would reasonably require to come into complianc
with the Standard/requirement once adopted by the BCUC (i.e. 6 months from adoption, immediately after adoption, etc.
will use this information to recommend an overall implementation time for each Standard/requirement for inclusion in the

Regards,

Patricia Robertson
Reliability Compliance Manager
British Columbia Hydro and Power Authority
(604)-455-4233
patricia.robertson@bchydro.com

Vijay Raghunathan
Senior Reliability Compliance Specialist
British Columbia Hydro and Power Authority
(604)-516-8958
vijay.raghunathan@bchydro.com
INSTRUCTIONS FOR EXTERNAL STAKEHOLDERS

To Registered Entities – British Columbia Mandatory Reliability Standards Program,

Please review each new and revised Standard (and corresponding redlines) as per the links provided from the BC Hydro Reliability we
www.bchydro.com/energy-in-bc/our_system/transmission/transmission-system/reliability.html.

NOTE: The 7 new and 30 revised Standards have been broken out into their requirements to enable stakeholders to provide
detailed comments per requirement.

Complete the 'Stnds Feedback Survey Form' (the yellow tab), and for each Standard assessed, please complete the following fields:

a. Insert the name and applicable functions of your registered entity at the top of the 'Stnds Feedback Survey Form'
as indicated by the red text.

b. Entity Comments, Organizational Activities and Reliability/Suitability Impact (Column "I"): Please advise if there are no cha
necessary to maintain compliance, or if changes are required, please describe a list of high-level incremental activities required to re
Please also indicate if there are any noted reliability/suitability impacts (technical or administrative) that could pose a challenge to po
Examples of suitability impacts: References made to unapproved standards, standard requirements depend on NERC approvals
functional roles/responsibilities (i.e. Planning Coordinator), references to undefined processes/procedures, etc..

c. Estimated Incremental/New Costs Associated with Revision/New Standard/Requirement, if any ($) (Columns “J” and "K"),
if any associated with:
- the adoption of a new Standard; or
- a revision to a Standard compared to the immediately preceding version currently adopted by BCUC.

Please indicate which costs are one-time versus ongoing, and ensure the assumptions associated with each estimate are captured
BC Hydro will use this information to develop recommendations to the BCUC regarding the potential impacts of each
reliability Standard on registered entities for inclusion in the Report.

d. BCUC Implementation Time (Column “L”):


Please include an assessment of the amount of time your organization would reasonably require to come into compliance
with the Standard/requirement once adopted by the BCUC (i.e. 6 months from adoption, immediately after adoption, etc.). BC Hyd
will use this information to recommend an overall implementation time for each Standard/requirement for inclusion in the Report.

Regards,

Patricia Robertson
Reliability Compliance Manager
British Columbia Hydro and Power Authority
(604)-455-4233
patricia.robertson@bchydro.com

Vijay Raghunathan
Senior Reliability Compliance Specialist
British Columbia Hydro and Power Authority
(604)-516-8958
vijay.raghunathan@bchydro.com
e.
n.
ined
Disclaimer: This information has been prepared as input into BC Hydro's tenth assessment report on Mandatory Reliability Standards and is based on information available to BC Hydro as of the date sent. It should not be relied upon for any other
INSERT YOUR ENTITY NAME AND FUNCTIONAL REGISTRATIONS APPLICABLE TO YOUR ENTITY (i.e. TO, DP, GO, DP, etc.):

FERC Approved
New/Revised
FERC Approved Revision(s) to
Standard/Requirement Current BCUC Adopted Standards to Functional Applicability of FERC Approved
Standard Name and Description Standard/Requirement listed in Standard Version
(Select the respective link be Superseded Standards/Requirements
History
to open the Standards)

Name: Analysis and Mitigation of Transmission and Generation


Protection System Misoperations
2.1a - Errata to a currently adopted Standard. Edited R2 TO, DP (that owns a transmission Protection
EXAMPLE 1 - PRC-004-2.1a PRC-004-2a
to add “…and generator interconnection Facility…” System), GO
Description: Ensure all transmission and generation Protection
System Misoperations affecting the reliability of the Bulk Electric
System (BES) are analyzed and mitigated.

Name: System Restoration and Blackstart Resources


EOP-005-1
EXAMPLE 2 - EOP-005-2 R17Description: Ensure plans, Facilities, and personnel are 2 - Replaces EOP-005-1 and incorporates elements of
and GOP (with a Blackstart Resource)
prepared to enable System restoration from Blackstart Resources EOP-009-0.
to assure reliability is maintained during restoration and priority is
EOP-009-0
placed on restoring the Interconnection.

Name: Cyber Security — Security Management Controls

Description: To specify consistent and sustainable security


management controls that establish responsibility and 6 - Updated requirement to include policies for low
CIP-003-6-R1 CIP-003-5 BA, DP, GO, GOP, IA, RC, TO, TOP, TP
accountability to protect BES Cyber Systems against impact BES Cyber Systems (moved from CIP-003-5
compromise that could lead to misoperation or instability in the Requirement 2). No material changes.
Bulk Electric System
(BES).

Name: Cyber Security — Security Management Controls


6 - New requirement to have documented and
Description: To specify consistent and sustainable security
implemented plans for low impact BES Cyber Systems
management controls that establish responsibility and
CIP-003-6-R2 CIP-003-5 pertaining to the topics of security awareness, physical BA, DP, GO, GOP, IA, RC, TO, TOP, TP
accountability to protect BES Cyber Systems against
security controls, electronic access controls, and Cyber
compromise that could lead to misoperation or instability in the
Security Incident Reponse.
Bulk Electric System
(BES).

Name: Cyber Security — Security Management Controls

Description: To specify consistent and sustainable security


management controls that establish responsibility and
CIP-003-6-R3 CIP-003-5 6 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TO, TOP, TP
accountability to protect BES Cyber Systems against
compromise that could lead to misoperation or instability in the
Bulk Electric System
(BES).
Name: Cyber Security — Security Management Controls

Description: To specify consistent and sustainable security


management controls that establish responsibility and
CIP-003-6-R4 CIP-003-5 6 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TO, TOP, TP
accountability to protect BES Cyber Systems against
compromise that could lead to misoperation or instability in the
Bulk Electric System
(BES).

Name: Cyber Security — Personnel & Training

Description; To minimize the risk against compromise that could


lead to misoperation or instability in the Bulk Electric System
CIP-004-6 - R1 CIP-004-5.1 6 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TO, TOP
(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.

Name: Cyber Security — Personnel & Training

Description; To minimize the risk against compromise that could


6 - Additional training component on cyber security risks
lead to misoperation or instability in the Bulk Electric System
CIP-004-6 - R2 CIP-004-5.1 related to interconnectivity of BES Cyber Systems with BA, DP, GO, GOP, IA, RC, TO, TOP
(BES) from individuals accessing BES Cyber Systems by
Transient Cyber Assets and Removeable Media.
requiring an appropriate level of personnel risk assessment,
training, and security awareness in
support of protecting BES Cyber Systems.

Name: Cyber Security — Personnel & Training

Description; To minimize the risk against compromise that could


lead to misoperation or instability in the Bulk Electric System
CIP-004-6 - R3 CIP-004-5.1 6 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TO, TOP
(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.

Name: Cyber Security — Personnel & Training

Description; To minimize the risk against compromise that could


lead to misoperation or instability in the Bulk Electric System
CIP-004-6 - R4 CIP-004-5.1 6 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TO, TOP, TP
(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.

Name: Cyber Security — Personnel & Training

Description; To minimize the risk against compromise that could


lead to misoperation or instability in the Bulk Electric System
CIP-004-6 - R5 CIP-004-5.1 6 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TO, TOP
(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.
Name: Cyber Security — Physical Security of BES Cyber
Systems 6 - Update to Requirement (Part 1.10) to include
protective controls for nonprogrammable
CIP-006-6 -R1 Description: To manage physical access to Bulk Electric System CIP-006-5 communication components outside of High Impact BA, DP, GO, GOP, IA, RC, TOP, TSP
(BES) Cyber Systems by specifying a physical security plan in Physical Security Perimeters in the Physical Security
support of protecting BES Cyber Systems against compromise Plan
that could lead to misoperation or instability in the BES.

Name: Cyber Security — Physical Security of BES Cyber


Systems

CIP-006-6 -R2 Description: To manage physical access to Bulk Electric System CIP-006-5 6 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TOP, TSP
(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.

Name: Cyber Security — Physical Security of BES Cyber


Systems

CIP-006-6 -R3 Description: To manage physical access to Bulk Electric System CIP-006-5 6 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TOP, TSP
(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.

Name: Cyber Security — System Security Management

Description: To manage system security by specifying select 6 - Change to Part 1.2 to also apply to
CIP-007-6-R1 technical, operational, and procedural requirements in support of CIP-007-5 nonprogrammable communication components located BA, DP, GO, GOP, IA, RC, TO, TOP
protecting BES Cyber Systems against compromise that could inside both a PSP and an ESP.
lead to misoperation or instability in the Bulk Electric System
(BES).

Name: Cyber Security — System Security Management

Description: To manage system security by specifying select


CIP-007-6-R2 technical, operational, and procedural requirements in support of CIP-007-5 6 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TO, TOP
protecting BES Cyber Systems against compromise that could
lead to misoperation or instability in the Bulk Electric System
(BES).

Name: Cyber Security — System Security Management

Description: To manage system security by specifying select


CIP-007-6-R3 technical, operational, and procedural requirements in support of CIP-007-5 6 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TO, TOP
protecting BES Cyber Systems against compromise that could
lead to misoperation or instability in the Bulk Electric System
(BES).
Name: Cyber Security — System Security Management

Description: To manage system security by specifying select


CIP-007-6-R4 technical, operational, and procedural requirements in support of CIP-007-5 6 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TO, TOP
protecting BES Cyber Systems against compromise that could
lead to misoperation or instability in the Bulk Electric System
(BES).

Name: Cyber Security — System Security Management

Description: To manage system security by specifying select


CIP-007-6-R5 technical, operational, and procedural requirements in support of CIP-007-5 6 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TO, TOP
protecting BES Cyber Systems against compromise that could
lead to misoperation or instability in the Bulk Electric System
(BES).

Name: Cyber Security — Recovery Plans for BES Cyber


Systems

CIP-009-6 R1 Description: To recover reliability functions performed by BES CIP-009-5 6 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TOP, TP
Cyber Systems by specifying recovery plan requirements in
support of the continued stability, operability, and reliability of the
BES.

Name: Cyber Security — Recovery Plans for BES Cyber


Systems

CIP-009-6 R2 Description: To recover reliability functions performed by BES CIP-009-5 6 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TO, TOP
Cyber Systems by specifying recovery plan requirements in
support of the continued stability, operability, and reliability of the
BES.

Name: Cyber Security — Recovery Plans for BES Cyber


Systems

CIP-009-6 R3 Description: To recover reliability functions performed by BES CIP-009-5 6 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TO, TOP
Cyber Systems by specifying recovery plan requirements in
support of the continued stability, operability, and reliability of the
BES.

Name: Cyber Security — Configuration Change Management


and Vulnerability Assessments

Description: To prevent and detect unauthorized changes to


CIP-010-2 R1 BES Cyber Systems by specifying configuration change CIP-010-1 2 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TO, TOP
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).
Name: Cyber Security — Configuration Change Management
and Vulnerability Assessments

Description: To prevent and detect unauthorized changes to


CIP-010-2 R2 BES Cyber Systems by specifying configuration change CIP-010-1 2 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TO, TOP
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).
Name: Cyber Security — Configuration Change Management
and Vulnerability Assessments

Description: To prevent and detect unauthorized changes to


CIP-010-2 R3 BES Cyber Systems by specifying configuration change CIP-010-1 2 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TO, TOP
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).
Name: Cyber Security — Configuration Change Management
and Vulnerability Assessments

Description: To prevent and detect unauthorized changes to 2 - New Requirement; As per Attachment 1 plans
CIP-010-2 R4 BES Cyber Systems by specifying configuration change CIP-010-1 should be updated or created to address Transient BA, DP, GO, GOP, IA, RC, TO, TOP
management and vulnerability assessment requirements in Cyber Assets and Removable Media
support of protecting BES Cyber Systems from compromise that
could lead to misoperation or instability in the Bulk Electric
System (BES).

Name: Cyber Security — Information Protection

Description: To prevent unauthorized access to BES Cyber


CIP-011-2 R1 System Information by specifying information protection CIP-011-1 2 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TO, TOP
requirements in support of protecting BES Cyber Systems against
compromise that could lead to misoperation
or instability in the Bulk Electric System (BES).

Name: Cyber Security — Information Protection

Description: To prevent unauthorized access to BES Cyber


CIP-011-2 R2 System Information by specifying information protection CIP-011-1 2 - No Material Changes to the Requirements BA, DP, GO, GOP, IA, RC, TO, TOP
requirements in support of protecting BES Cyber Systems against
compromise that could lead to misoperation
or instability in the Bulk Electric System (BES).

Name: Communications
COM-001-3 R1 COM-001-2.1 3 - No Material Changes to the Requirements RC
Description: To establish Interpersonal Communication
capabilities necessary to maintain reliability.
Name: Communications
COM-001-3 R2 COM-001-2.1 3 - No Material Changes to the Requirements RC
Description: To establish Interpersonal Communication
capabilities necessary to maintain reliability.

Name: Communications
COM-001-3 R3 COM-001-2.1 3 - No Material Changes to the Requirements TOP
Description: To establish Interpersonal Communication
capabilities necessary to maintain reliability.

Name: Communications
COM-001-3 R4 COM-001-2.1 3 - No Material Changes to the Requirements TOP
Description: To establish Interpersonal Communication
capabilities necessary to maintain reliability.

Name: Communications
COM-001-3 R5 COM-001-2.1 3 - No Material Changes to the Requirements BA
Description: To establish Interpersonal Communication
capabilities necessary to maintain reliability.

Name: Communications
COM-001-3 R6 COM-001-2.1 3 - No Material Changes to the Requirements BA
Description: To establish Interpersonal Communication
capabilities necessary to maintain reliability.

Name: Communications
COM-001-3 R7 COM-001-2.1 3 - No Material Changes to the Requirements DP
Description: To establish Interpersonal Communication
capabilities necessary to maintain reliability.
Name: Communications
COM-001-3 R8 COM-001-2.1 3 - No Material Changes to the Requirements GOP
Description: To establish Interpersonal Communication
capabilities necessary to maintain reliability.

Name: Communications
COM-001-3 R9 COM-001-2.1 3 - No Material Changes to the Requirements RC, TOP, BA
Description: To establish Interpersonal Communication
capabilities necessary to maintain reliability.

Name: Communications
COM-001-3 R10 COM-001-2.1 3 - No Material Changes to the Requirements RC, TOP, BA
Description: To establish Interpersonal Communication
capabilities necessary to maintain reliability.

Name: Communications
COM-001-3 R11 COM-001-2.1 3 - No Material Changes to the Requirements DP, GOP
Description: To establish Interpersonal Communication
capabilities necessary to maintain reliability.

Name: Communications
3- New Requirement; increased obligations for inter-
COM-001-3 R12 COM-001-2.1 Control Center and field-to-Control Center RC, TOP, GOP, BA
Description: To establish Interpersonal Communication
communications
capabilities necessary to maintain reliability.

Name: Communications
3 - New Requirement; increased obligations for inter-
COM-001-3 R13 COM-001-2.1 Control Center and field-to-Control Center DP
Description: To establish Interpersonal Communication
communications
capabilities necessary to maintain reliability.
3 - Minor changes including replacement of term
Name: Event Reporting
Special Protection System with Remedial Action
EOP-004-3 R1 EOP-004-2 Scheme, updates made to reporting email addresses DP, GO, GOP, RC, TO, TOP, BA
Description: To improve the reliability of the Bulk Electric System
per Attachment, and align with most recent version of
by requiring the reporting of events by Responsible Entities.
NERC Rules of Procedure

3 - Minor changes including replacement of term


Name: Event Reporting
Special Protection System with Remedial Action
EOP-004-3 R2 EOP-004-2 Scheme, updates made to reporting email addresses DP, GO, GOP, RC, TO, TOP
Description: To improve the reliability of the Bulk Electric System
per Attachment 1, and to align with most recent version
by requiring the reporting of events by Responsible Entities.
of NERC Rules of Procedure.

3 - Minor changes including replacement of term


Name: Event Reporting
Special Protection System with Remedial Action
EOP-004-3 R3 EOP-004-2 Scheme, updates made to reporting email addresses DP, GO, GOP, RC, TO, TOP
Description: To improve the reliability of the Bulk Electric System
per Attachment 1, and to align with most recent version
by requiring the reporting of events by Responsible Entities.
of NERC Rules of Procedure.

Name: Emergency Operations


NEW; consolidates and replaces EOP-
001-2.1b, EOP-002-3.1, and in
Description: To address the effects of operating Emergencies by
conjunction with PRC-010-2
EOP-011-1 R1 ensuring each Transmission Operator and Balancing Authority N/A TOP
Requirement 1 (adoption held in
has developed Operating Plan(s) to mitigate operating
abeyance in B.C. due to PA/PC
Emergencies, and that those plans are coordinated within a
dependencies), replaces EOP-003-1.
Reliability Coordinator Area.

Name: Emergency Operations


NEW; consolidates and replaces EOP-
001-2.1b, EOP-002-3.1, and in
Description: To address the effects of operating Emergencies by
conjunction with PRC-010-2
EOP-011-1 R2 ensuring each Transmission Operator and Balancing Authority N/A BA
Requirement 1 (adoption held in
has developed Operating Plan(s) to mitigate operating
abeyance in B.C. due to PA/PC
Emergencies, and that those plans are coordinated within a
dependencies), replaces EOP-003-1.
Reliability Coordinator Area.

Name: Emergency Operations


NEW; consolidates and replaces EOP-
001-2.1b, EOP-002-3.1, and in
Description: To address the effects of operating Emergencies by
conjunction with PRC-010-2
EOP-011-1 R3 ensuring each Transmission Operator and Balancing Authority N/A RC
Requirement 1 (adoption held in
has developed Operating Plan(s) to mitigate operating
abeyance in B.C. due to PA/PC
Emergencies, and that those plans are coordinated within a
dependencies), replaces EOP-003-1.
Reliability Coordinator Area.
Name: Emergency Operations
NEW; consolidates and replaces EOP-
001-2.1b, EOP-002-3.1, and in
Description: To address the effects of operating Emergencies by
conjunction with PRC-010-2
EOP-011-1 R4 ensuring each Transmission Operator and Balancing Authority N/A TOP, BA
Requirement 1 (adoption held in
has developed Operating Plan(s) to mitigate operating
abeyance in B.C. due to PA/PC
Emergencies, and that those plans are coordinated within a
dependencies), replaces EOP-003-1.
Reliability Coordinator Area.

Name: Emergency Operations


NEW; consolidates and replaces EOP-
001-2.1b, EOP-002-3.1, and in
Description: To address the effects of operating Emergencies by
conjunction with PRC-010-2
EOP-011-1 R5 ensuring each Transmission Operator and Balancing Authority N/A RC
Requirement 1 (adoption held in
has developed Operating Plan(s) to mitigate operating
abeyance in B.C. due to PA/PC
Emergencies, and that those plans are coordinated within a
dependencies), replaces EOP-003-1.
Reliability Coordinator Area.

Name: Emergency Operations


NEW; consolidates and replaces EOP-
001-2.1b, EOP-002-3.1, and in
Description: To address the effects of operating Emergencies by
conjunction with PRC-010-2
EOP-011-1 R6 ensuring each Transmission Operator and Balancing Authority N/A RC
Requirement 1 (adoption held in
has developed Operating Plan(s) to mitigate operating
abeyance in B.C. due to PA/PC
Emergencies, and that those plans are coordinated within a
dependencies), replaces EOP-003-1.
Reliability Coordinator Area.

4 - Adjusted MVCD values in Table 2 for alternating


Name: Transmission Vegetation Management
current systems, consistent with findings reported in
report filed on August 12, 2015 in Docket No. RM12-4-
Description: To maintain a reliable electric transmission system
002 consistent with FERC’s directive in Order No. 777,
by using a defense-in-depth strategy to manage vegetation
FAC-003-4 R1 FAC-003-3 and based on empirical testing results for flashover GO, TO
located on transmission rights of way (ROW) and minimize
distances between conductors and vegetation.
encroachments from vegetation located adjacent to the ROW,
thus preventing the risk of those vegetation-related outages that
4 - Minor verbiage changes in order to align with
could lead to Cascading.
effective Rules of Procedure

Name: Transmission Vegetation Management

Description: To maintain a reliable electric transmission system


by using a defense-in-depth strategy to manage vegetation
FAC-003-4 R2 FAC-003-3 4 - No Material Changes to the Requirements GO, TO
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.

Name: Transmission Vegetation Management

Description: To maintain a reliable electric transmission system


by using a defense-in-depth strategy to manage vegetation
FAC-003-4 R3 FAC-003-3 4 - No Material Changes to the Requirements GO, TO
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.
Name: Transmission Vegetation Management

Description: To maintain a reliable electric transmission system


by using a defense-in-depth strategy to manage vegetation
FAC-003-4 R4 FAC-003-3 4 - No Material Changes to the Requirements GO, TO
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.

Name: Transmission Vegetation Management

Description: To maintain a reliable electric transmission system


by using a defense-in-depth strategy to manage vegetation
FAC-003-4 R5 FAC-003-3 4 - No Material Changes to the Requirements GO, TO
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.

Name: Transmission Vegetation Management

Description: To maintain a reliable electric transmission system


by using a defense-in-depth strategy to manage vegetation
FAC-003-4 R6 FAC-003-3 4 - No Material Changes to the Requirements GO, TO
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.

Name: Transmission Vegetation Management

Description: To maintain a reliable electric transmission system


by using a defense-in-depth strategy to manage vegetation 4 - Minor verbiage changes pertaining to vegetation
FAC-003-4 R7 FAC-003-3 GO, TO
located on transmission rights of way (ROW) and minimize growth rates.
encroachments from vegetation located adjacent to the ROW,
thus preventing the risk of those vegetation-related outages that
could lead to Cascading.

Name: System Operating Limits Methodology for the Planning


Horizon
3 - Updated with definition and implementation of
FAC-010-3 R1 Description: To ensure that System Operating Limits (SOLs) FAC-010-2.1 PA
Remedial Action Scheme
used in the reliable planning of the Bulk Electric System (BES)
are determined based on an established methodology or
methodologies.

Name: System Operating Limits Methodology for the Planning


Horizon
3 - Updated with definition and implementation of
FAC-010-3 R2 Description: To ensure that System Operating Limits (SOLs) FAC-010-2.1 PA
Remedial Action Scheme
used in the reliable planning of the Bulk Electric System (BES)
are determined based on an established methodology or
methodologies.
Name: System Operating Limits Methodology for the Planning
Horizon
3 - Updated with definition and implementation of
FAC-010-3 R3 Description: To ensure that System Operating Limits (SOLs) FAC-010-2.1 PA
Remedial Action Scheme
used in the reliable planning of the Bulk Electric System (BES)
are determined based on an established methodology or
methodologies.

Name: System Operating Limits Methodology for the Planning


Horizon
3 - Updated with definition and implementation of
FAC-010-3 R4 Description: To ensure that System Operating Limits (SOLs) FAC-010-2.1 PA
Remedial Action Scheme
used in the reliable planning of the Bulk Electric System (BES)
are determined based on an established methodology or
methodologies.

Name: System Operating Limits Methodology for the Planning


Horizon
3 - Updated with definition and implementation of
FAC-010-3 R5 Description: To ensure that System Operating Limits (SOLs) FAC-010-2.1 PA
Remedial Action Scheme
used in the reliable planning of the Bulk Electric System (BES)
are determined based on an established methodology or
methodologies.

Name: System Operating Limits Methodology for the Operations


Horizon
3 - Updated with definition and implementation of
FAC-011-3 R1 Description: To ensure that System Operating Limits (SOLs) FAC-011-2 RC
Remedial Action Scheme
used in the reliable operation of the Bulk Electric System (BES)
are determined based on an established methodology or
methodologies.

Name: System Operating Limits Methodology for the Operations


Horizon
3 - Updated with definition and implementation of
FAC-011-3 R2 Description: To ensure that System Operating Limits (SOLs) FAC-011-2 RC
Remedial Action Scheme
used in the reliable operation of the Bulk Electric System (BES)
are determined based on an established methodology or
methodologies.

Name: System Operating Limits Methodology for the Operations


Horizon
3 - Updated with definition and implementation of
FAC-011-3 R3 Description: To ensure that System Operating Limits (SOLs) FAC-011-2 RC
Remedial Action Scheme
used in the reliable operation of the Bulk Electric System (BES)
are determined based on an established methodology or
methodologies.
Name: System Operating Limits Methodology for the Operations
Horizon
3 - Updated with definition and implementation of
FAC-011-3 R4 Description: To ensure that System Operating Limits (SOLs) FAC-011-2 RC
Remedial Action Scheme
used in the reliable operation of the Bulk Electric System (BES)
are determined based on an established methodology or
methodologies.

Name: Reliability Coordination – Responsibilities 4 - Multiple requirements are retired and remaining are
consolidated and reordered. Additional details are
IRO-001-4 R1 IRO-001-1.1; in conjunction with IRO-002-4, IRO-008-2, IRO-010-2, IRO-014-3, and IRO-017-1, also replaces IRO-002-2,
RC IRO-003-2, IRO-004-2, IRO-005-3.1a, IRO-008
Description: To establish the responsibility of Reliability provided but not material.
Coordinators to act or direct other entities to act.

Name: Reliability Coordination – Responsibilities 4 - Multiple requirements are retired and remaining are
consolidated and reordered. Additional details are
IRO-001-4 R2 IRO-001-1.1; in conjunction with IRO-002-4, IRO-008-2, IRO-010-2, IRO-014-3, and IRO-017-1, also replaces IRO-002-2,
TOP, GOP,IRO-003-2,
BA, DP IRO-004-2, IRO-005-3.1a, IRO-008
Description: To establish the responsibility of Reliability provided but not material.
Coordinators to act or direct other entities to act.

Name: Reliability Coordination – Responsibilities 4 - Multiple requirements are retired and remaining are
consolidated and reordered. Additional details are
IRO-001-4 R3 IRO-001-1.1; in conjunction with IRO-002-4, IRO-008-2, IRO-010-2, IRO-014-3, and IRO-017-1, also replaces IRO-002-2,
TOP, GOP,IRO-003-2,
BA, DP IRO-004-2, IRO-005-3.1a, IRO-008
Description: To establish the responsibility of Reliability provided but not material.
Coordinators to act or direct other entities to act.

Name: Reliability Coordination – Monitoring and Analysis


4 - Minor clarifying verbiage upgrades, organization,
and presentation changes. Material change include
IRO-002-4 R1 Description: Provide System Operators with the capabilities IRO-002-2; in conjunction with IRO-001-4, IRO-008-2, IRO-010-2, IRO-014-3, and IRO-017-1, also replaces IRO-001-1.1,RC
IRO-003-2, IRO-004-2, IRO-005-3.1a, IRO-008-
clarifying terms to align with emerging transmission
necessary to monitor and analyze data needed to perform their
operations standards.
reliability functions.

Name: Reliability Coordination – Monitoring and Analysis


4 - Minor clarifying verbiage upgrades, organization,
and presentation changes. Material change include
IRO-002-4 R2 Description: Provide System Operators with the capabilities IRO-002-2; in conjunction with IRO-001-4, IRO-008-2, IRO-010-2, IRO-014-3, and IRO-017-1, also replaces IRO-001-1.1,RC
IRO-003-2, IRO-004-2, IRO-005-3.1a, IRO-008-
clarifying terms to align with emerging transmission
necessary to monitor and analyze data needed to perform their
operations standards.
reliability functions.
Name: Reliability Coordination – Monitoring and Analysis
4 - Minor clarifying verbiage upgrades, organization,
and presentation changes. Material change include
IRO-002-4 R3 Description: Provide System Operators with the capabilities IRO-002-2; in conjunction with IRO-001-4, IRO-008-2, IRO-010-2, IRO-014-3, and IRO-017-1, also replaces IRO-001-1.1,RC
IRO-003-2, IRO-004-2, IRO-005-3.1a, IRO-008-
clarifying terms to align with emerging transmission
necessary to monitor and analyze data needed to perform their
operations standards.
reliability functions.

Name: Reliability Coordination – Monitoring and Analysis

IRO-002-4 R4 Description: Provide System Operators with the capabilities IRO-002-2; in conjunction with IRO-001-4,
4 -IRO-008-2,
No MaterialIRO-010-2,
Changes toIRO-014-3,
the Requirements
and IRO-017-1, also replaces IRO-001-1.1,RC
IRO-003-2, IRO-004-2, IRO-005-3.1a, IRO-008-
necessary to monitor and analyze data needed to perform their
reliability functions.

Name: Reliability Coordinator Operational Analyses and Real-


time Assessments
2 - Update to include System Operating Limits (SOLs)
IRO-008-2 R1 IRO-008-1; in conjunction with IRO-001-4, IRO-002-4, IRO-010-2, IRO-014-3, and IRO-017-1, also replaces IRO-001-1.1,RC
IRO-002-2, IRO-003-2, IRO-004-2, IRO-005-3.1
in next-day Operation Planning
Description: Perform analyses and assessments to prevent
instability, uncontrolled separation, or Cascading.

Name: Reliability Coordinator Operational Analyses and Real-


2 - Update to include System Operating Limits (SOLs)
time Assessments
in next-day Operation Planning; include Additional
IRO-008-2 R2 IRO-008-1; in conjunction with IRO-001-4, IRO-002-4, IRO-010-2, IRO-014-3, and IRO-017-1, also replaces IRO-001-1.1,RC
IRO-002-2, IRO-003-2, IRO-004-2, IRO-005-3.1
Document require for Operating Plan and defintion; and
Description: Perform analyses and assessments to prevent
increase Data Retention requirements.
instability, uncontrolled separation, or Cascading.

Name: Reliability Coordinator Operational Analyses and Real-


2 - Update to include System Operating Limits (SOLs)
time Assessments
in next-day Operation Planning; include Additional
IRO-008-2 R3 IRO-008-1; in conjunction with IRO-001-4, IRO-002-4, IRO-010-2, IRO-014-3, and IRO-017-1, also replaces IRO-001-1.1,RC
IRO-002-2, IRO-003-2, IRO-004-2, IRO-005-3.1
Document require for Operating Plan and defintion; and
Description: Perform analyses and assessments to prevent
increase Data Retention requirements.
instability, uncontrolled separation, or Cascading.

Name: Reliability Coordinator Operational Analyses and Real-


2 - Update to include System Operating Limits (SOLs)
time Assessments
in next-day Operation Planning; include Additional
IRO-008-2 R4 IRO-008-1; in conjunction with IRO-001-4, IRO-002-4, IRO-010-2, IRO-014-3, and IRO-017-1, also replaces IRO-001-1.1,RC
IRO-002-2, IRO-003-2, IRO-004-2, IRO-005-3.1
Document require for Operating Plan and defintion; and
Description: Perform analyses and assessments to prevent
increase Data Retention requirements.
instability, uncontrolled separation, or Cascading.
Name: Reliability Coordinator Operational Analyses and Real-
2 - Update to include System Operating Limits (SOLs)
time Assessments
in next-day Operation Planning; include Additional
IRO-008-2 R5 IRO-008-1; in conjunction with IRO-001-4, IRO-002-4, IRO-010-2, IRO-014-3, and IRO-017-1, also replaces IRO-001-1.1,RC
IRO-002-2, IRO-003-2, IRO-004-2, IRO-005-3.1
Document require for Operating Plan and defintion; and
Description: Perform analyses and assessments to prevent
increase Data Retention requirements.
instability, uncontrolled separation, or Cascading.

Name: Reliability Coordinator Operational Analyses and Real-


2 - Update to include System Operating Limits (SOLs)
time Assessments
in next-day Operation Planning; include Additional
IRO-008-2 R6 IRO-008-1; in conjunction with IRO-001-4, IRO-002-4, IRO-010-2, IRO-014-3, and IRO-017-1, also replaces IRO-001-1.1,RC
IRO-002-2, IRO-003-2, IRO-004-2, IRO-005-3.1
Document require for Operating Plan and defintion; and
Description: Perform analyses and assessments to prevent
increase Data Retention requirements.
instability, uncontrolled separation, or Cascading.

Name: Reliability Coordinator Actions to Operate Within IROLs


2 - New version combines two existing requirements,
Description: To prevent instability, uncontrolled separation, or
revises existing language to clearly delineate applicable
IRO-009-2 R1 cascading outages that adversely impact the reliability of the IRO-009-1 RC
entities and the specific actions required, and removes
interconnection by ensuring prompt action to prevent or mitigate
unnecessary language
instances of exceeding Interconnection Reliability Operating
Limits (IROLs).

Name: Reliability Coordinator Actions to Operate Within IROLs


2 - New version combines two existing requirements,
Description: To prevent instability, uncontrolled separation, or
revises existing language to clearly delineate applicable
IRO-009-2 R2 cascading outages that adversely impact the reliability of the IRO-009-1 RC
entities and the specific actions required, and removes
interconnection by ensuring prompt action to prevent or mitigate
unnecessary language
instances of exceeding Interconnection Reliability Operating
Limits (IROLs).

Name: Reliability Coordinator Actions to Operate Within IROLs


2 - New version combines two existing requirements,
Description: To prevent instability, uncontrolled separation, or
revises existing language to clearly delineate applicable
IRO-009-2 R3 cascading outages that adversely impact the reliability of the IRO-009-1 RC
entities and the specific actions required, and removes
interconnection by ensuring prompt action to prevent or mitigate
unnecessary language
instances of exceeding Interconnection Reliability Operating
Limits (IROLs).

Name: Reliability Coordinator Actions to Operate Within IROLs


2 - New version combines two existing requirements,
Description: To prevent instability, uncontrolled separation, or
revises existing language to clearly delineate applicable
IRO-009-2 R4 cascading outages that adversely impact the reliability of the IRO-009-1 RC
entities and the specific actions required, and removes
interconnection by ensuring prompt action to prevent or mitigate
unnecessary language
instances of exceeding Interconnection Reliability Operating
Limits (IROLs).
Name: Reliability Coordinator Data Specification and Collection
2 - Updated with clarifying langague, new defintitions,
Description: To prevent instability, uncontrolled separation, or and provisions to include non-BES data, real time
IRO-010-2 R1 IRO-010-1a; in conjunction with IRO-001-4, IRO-002-4, IRO-008-2, IRO-014-3, and IRO-017-1, also replaces IRO-001-1.1,
RCIRO-002-2, IRO-003-2, IRO-004-2, IRO-005-3.
Cascading outages that adversely impact reliability, by ensuring monitoring, operational analysis, and real time
the Reliability Coordinator has the data it needs to monitor and assessments
assess the operation of its Reliability Coordinator Area.

Name: Reliability Coordinator Data Specification and Collection


2 - Updated with clarifying langague, new defintitions,
Description: To prevent instability, uncontrolled separation, or and provisions to include non-BES data, real time
IRO-010-2 R2 IRO-010-1a; in conjunction with IRO-001-4, IRO-002-4, IRO-008-2, IRO-014-3, and IRO-017-1, also replaces IRO-001-1.1,
RCIRO-002-2, IRO-003-2, IRO-004-2, IRO-005-3.
Cascading outages that adversely impact reliability, by ensuring monitoring, operational analysis, and real time
the Reliability Coordinator has the data it needs to monitor and assessments
assess the operation of its Reliability Coordinator Area.

Name: Reliability Coordinator Data Specification and Collection


2 - Updated with clarifying langague, new defintitions,
Description: To prevent instability, uncontrolled separation, or and provisions to include non-BES data, real time
IRO-010-2 R3 IRO-010-1a; in conjunction with IRO-001-4, IRO-002-4, IRO-008-2, IRO-014-3, and IRO-017-1, also replaces
RC, BA,
IRO-001-1.1,
GO, GOP, LSE,
IRO-002-2,
TOP, TO,
IRO-003-2,
DP IRO-004-2, IRO-005-3.
Cascading outages that adversely impact reliability, by ensuring monitoring, operational analysis, and real time
the Reliability Coordinator has the data it needs to monitor and assessments
assess the operation of its Reliability Coordinator Area.

Name: Coordination Among Reliability Coordinators


3 - Updated with clarifying terms including Operating
Description: To ensure that each Reliability Coordinator’s Plans, Operating Procedures, and Emergency
IRO-014-3 R1 IRO-014-1; in conjunction with IRO-001-4, IRO-002-4, IRO-008-2, IRO-010-2, and IRO-017-1, also replaces IRO-001-1.1,RC
IRO-002-2, IRO-003-2, IRO-004-2, IRO-005-3.1
operations are coordinated such that they will not adversely conditions; certain requirements consolidated and/or
impact other Reliability Coordinator Areas and to preserve the reworded to enhance readability.
reliability benefits of interconnected operations.

Name: Coordination Among Reliability Coordinators


3 - Updated with clarifying terms including Operating
Description: To ensure that each Reliability Coordinator’s Plans, Operating Procedures, and Emergency
IRO-014-3 R2 IRO-014-1; in conjunction with IRO-001-4, IRO-002-4, IRO-008-2, IRO-010-2, and IRO-017-1, also replaces IRO-001-1.1,RC
IRO-002-2, IRO-003-2, IRO-004-2, IRO-005-3.1
operations are coordinated such that they will not adversely conditions; certain requirements consolidated and/or
impact other Reliability Coordinator Areas and to preserve the reworded to enhance readability.
reliability benefits of interconnected operations.

Name: Coordination Among Reliability Coordinators


3 - Updated with clarifying terms including Operating
Description: To ensure that each Reliability Coordinator’s Plans, Operating Procedures, and Emergency
IRO-014-3 R3 IRO-014-1; in conjunction with IRO-001-4, IRO-002-4, IRO-008-2, IRO-010-2, and IRO-017-1, also replaces IRO-001-1.1,RC
IRO-002-2, IRO-003-2, IRO-004-2, IRO-005-3.1
operations are coordinated such that they will not adversely conditions; certain requirements consolidated and/or
impact other Reliability Coordinator Areas and to preserve the reworded to enhance readability.
reliability benefits of interconnected operations.
Name: Coordination Among Reliability Coordinators
3 - Updated with clarifying terms including Operating
Description: To ensure that each Reliability Coordinator’s Plans, Operating Procedures, and Emergency
IRO-014-3 R4 IRO-014-1; in conjunction with IRO-001-4, IRO-002-4, IRO-008-2, IRO-010-2, and IRO-017-1, also replaces IRO-001-1.1,RC
IRO-002-2, IRO-003-2, IRO-004-2, IRO-005-3.1
operations are coordinated such that they will not adversely conditions; certain requirements consolidated and/or
impact other Reliability Coordinator Areas and to preserve the reworded to enhance readability.
reliability benefits of interconnected operations.

Name: Coordination Among Reliability Coordinators


3 - Updated with clarifying terms including Operating
Description: To ensure that each Reliability Coordinator’s Plans, Operating Procedures, and Emergency
IRO-014-3 R5 IRO-014-1; in conjunction with IRO-001-4, IRO-002-4, IRO-008-2, IRO-010-2, and IRO-017-1, also replaces IRO-001-1.1,RC
IRO-002-2, IRO-003-2, IRO-004-2, IRO-005-3.1
operations are coordinated such that they will not adversely conditions; certain requirements consolidated and/or
impact other Reliability Coordinator Areas and to preserve the reworded to enhance readability.
reliability benefits of interconnected operations.

Name: Coordination Among Reliability Coordinators


3 - Updated with clarifying terms including Operating
Description: To ensure that each Reliability Coordinator’s Plans, Operating Procedures, and Emergency
IRO-014-3 R6 IRO-014-1; in conjunction with IRO-001-4, IRO-002-4, IRO-008-2, IRO-010-2, and IRO-017-1, also replaces IRO-001-1.1,RC
IRO-002-2, IRO-003-2, IRO-004-2, IRO-005-3.1
operations are coordinated such that they will not adversely conditions; certain requirements consolidated and/or
impact other Reliability Coordinator Areas and to preserve the reworded to enhance readability.
reliability benefits of interconnected operations.

Name: Coordination Among Reliability Coordinators


3 - Updated with clarifying terms including Operating
Description: To ensure that each Reliability Coordinator’s Plans, Operating Procedures, and Emergency
IRO-014-3 R7 IRO-014-1; in conjunction with IRO-001-4, IRO-002-4, IRO-008-2, IRO-010-2, and IRO-017-1, also replaces IRO-001-1.1,RC
IRO-002-2, IRO-003-2, IRO-004-2, IRO-005-3.1
operations are coordinated such that they will not adversely conditions; certain requirements consolidated and/or
impact other Reliability Coordinator Areas and to preserve the reworded to enhance readability.
reliability benefits of interconnected operations.

NEW; in conjunction with IRO-001-4,


Name: Outage Coordination IRO-002-4, IRO-008-2, IRO-010-2, and
IRO-014-3, replaces IRO-001-1.1, IRO-
IRO-017-1 R1 Description: To ensure that outages are properly coordinated in 002-2, IRO-003-2, IRO-004-2, IRO- N/A RC
the Operations Planning time horizon and Near-Term 005-3.1a, IRO-008-1, IRO-010-1a,
Transmission Planning Horizon. IRO-014-1, IRO-015-1, IRO-016-1, and
PER-001-0.2.

NEW; in conjunction with IRO-001-4,


Name: Outage Coordination IRO-002-4, IRO-008-2, IRO-010-2, and
IRO-014-3, replaces IRO-001-1.1, IRO-
IRO-017-1 R2 Description: To ensure that outages are properly coordinated in 002-2, IRO-003-2, IRO-004-2, IRO- N/A TOP, BA
the Operations Planning time horizon and Near-Term 005-3.1a, IRO-008-1, IRO-010-1a,
Transmission Planning Horizon. IRO-014-1, IRO-015-1, IRO-016-1, and
PER-001-0.2.
NEW; in conjunction with IRO-001-4,
Name: Outage Coordination IRO-002-4, IRO-008-2, IRO-010-2, and
IRO-014-3, replaces IRO-001-1.1, IRO-
IRO-017-1 R3 Description: To ensure that outages are properly coordinated in 002-2, IRO-003-2, IRO-004-2, IRO- N/A PC, TP
the Operations Planning time horizon and Near-Term 005-3.1a, IRO-008-1, IRO-010-1a,
Transmission Planning Horizon. IRO-014-1, IRO-015-1, IRO-016-1, and
PER-001-0.2.

NEW; in conjunction with IRO-001-4,


Name: Outage Coordination IRO-002-4, IRO-008-2, IRO-010-2, and
IRO-014-3, replaces IRO-001-1.1, IRO-
IRO-017-1 R4 Description: To ensure that outages are properly coordinated in 002-2, IRO-003-2, IRO-004-2, IRO- N/A PC, TP
the Operations Planning time horizon and Near-Term 005-3.1a, IRO-008-1, IRO-010-1a,
Transmission Planning Horizon. IRO-014-1, IRO-015-1, IRO-016-1, and
PER-001-0.2.

Name: Reliability Coordinator Real-time Reliability Monitoring and


Analysis Capabilities
IRO-018-1 R1 NEW N/A RC
Description: Establish requirements for Real-time monitoring and
analysis capabilities to support reliable System operations.

Name: Reliability Coordinator Real-time Reliability Monitoring and


Analysis Capabilities
IRO-018-1 R2 NEW N/A RC
Description: Establish requirements for Real-time monitoring and
analysis capabilities to support reliable System operations.

Name: Reliability Coordinator Real-time Reliability Monitoring and


Analysis Capabilities
IRO-018-1 R3 NEW N/A RC
Description: Establish requirements for Real-time monitoring and
analysis capabilities to support reliable System operations.

Name: Rated System Path Methodology

Description: To increase consistency and reliability in the


2a - Updated with term "Remedial Action Scheme" and
MOD-029-2a R1 development and documentation of transfer capability MOD-029-1a TOP
align with definition thereto
calculations for short-term use performed by
entities using the Rated System Path Methodology to support
analysis and system operations.
Name: Rated System Path Methodology

Description: To increase consistency and reliability in the


2a - Updated with term "Remedial Action Scheme" and
MOD-029-2a R2 development and documentation of transfer capability MOD-029-1a TOP
align with definition thereto
calculations for short-term use performed by
entities using the Rated System Path Methodology to support
analysis and system operations.

Name: Rated System Path Methodology

Description: To increase consistency and reliability in the


2a - Updated with term "Remedial Action Scheme" and
MOD-029-2a R3 development and documentation of transfer capability MOD-029-1a TOP
align with definition thereto
calculations for short-term use performed by
entities using the Rated System Path Methodology to support
analysis and system operations.

Name: Rated System Path Methodology

Description: To increase consistency and reliability in the


2a - Updated with term "Remedial Action Scheme" and
MOD-029-2a R4 development and documentation of transfer capability MOD-029-1a TOP
align with definition thereto
calculations for short-term use performed by
entities using the Rated System Path Methodology to support
analysis and system operations.

Name: Rated System Path Methodology

Description: To increase consistency and reliability in the


2a - Updated with term "Remedial Action Scheme" and
MOD-029-2a R5 development and documentation of transfer capability MOD-029-1a TSP
align with definition thereto
calculations for short-term use performed by
entities using the Rated System Path Methodology to support
analysis and system operations.

Name: Rated System Path Methodology

Description: To increase consistency and reliability in the


2a - Updated with term "Remedial Action Scheme" and
MOD-029-2a R6 development and documentation of transfer capability MOD-029-1a TSP
align with definition thereto
calculations for short-term use performed by
entities using the Rated System Path Methodology to support
analysis and system operations.

Name: Rated System Path Methodology

Description: To increase consistency and reliability in the


2a - Updated with term "Remedial Action Scheme" and
MOD-029-2a R7 development and documentation of transfer capability MOD-029-1a TSP
align with definition thereto
calculations for short-term use performed by
entities using the Rated System Path Methodology to support
analysis and system operations.
Name: Rated System Path Methodology

Description: To increase consistency and reliability in the


2a - Updated with term "Remedial Action Scheme" and
MOD-029-2a R8 development and documentation of transfer capability MOD-029-1a TSP
align with definition thereto
calculations for short-term use performed by
entities using the Rated System Path Methodology to support
analysis and system operations.

Name: Flowgate Methodology

Description: To increase consistency and reliability in the


3 - Updated with term "Remedial Action Scheme" and
MOD-030-3 R1 development and documentation of transfer capability MOD-30-2 TSP
align with definition thereto
calculations for short-term use performed by entities using the
Flowgate Methodology to support analysis and system
operations.

Name: Flowgate Methodology

Description: To increase consistency and reliability in the


3 - Updated with term "Remedial Action Scheme" and
MOD-030-3 R2 development and documentation of transfer capability MOD-30-2 TOP
align with definition thereto
calculations for short-term use performed by entities using the
Flowgate Methodology to support analysis and system
operations.

Name: Flowgate Methodology

Description: To increase consistency and reliability in the


3 - Updated with term "Remedial Action Scheme" and
MOD-030-3 R3 development and documentation of transfer capability MOD-30-2 TOP
align with definition thereto
calculations for short-term use performed by entities using the
Flowgate Methodology to support analysis and system
operations.

Name: Flowgate Methodology

Description: To increase consistency and reliability in the


3 - Updated with term "Remedial Action Scheme" and
MOD-030-3 R4 development and documentation of transfer capability MOD-30-2 TSP
align with definition thereto
calculations for short-term use performed by entities using the
Flowgate Methodology to support analysis and system
operations.

Name: Flowgate Methodology

Description: To increase consistency and reliability in the


3 - Updated with term "Remedial Action Scheme" and
MOD-030-3 R5 development and documentation of transfer capability MOD-30-2 TSP
align with definition thereto
calculations for short-term use performed by entities using the
Flowgate Methodology to support analysis and system
operations.
Name: Flowgate Methodology

Description: To increase consistency and reliability in the


3 - Updated with term "Remedial Action Scheme" and
MOD-030-3 R6 development and documentation of transfer capability MOD-30-2 TSP
align with definition thereto
calculations for short-term use performed by entities using the
Flowgate Methodology to support analysis and system
operations.

Name: Flowgate Methodology

Description: To increase consistency and reliability in the


3 - Updated with term "Remedial Action Scheme" and
MOD-030-3 R7 development and documentation of transfer capability MOD-30-2 TSP
align with definition thereto
calculations for short-term use performed by entities using the
Flowgate Methodology to support analysis and system
operations.

Name: Flowgate Methodology

Description: To increase consistency and reliability in the


3 - Updated with term "Remedial Action Scheme" and
MOD-030-3 R8 development and documentation of transfer capability MOD-30-2 TSP
align with definition thereto
calculations for short-term use performed by entities using the
Flowgate Methodology to support analysis and system
operations.

Name: Flowgate Methodology

Description: To increase consistency and reliability in the


3 - Updated with term "Remedial Action Scheme" and
MOD-030-3 R9 development and documentation of transfer capability MOD-30-2 TSP
align with definition thereto
calculations for short-term use performed by entities using the
Flowgate Methodology to support analysis and system
operations.

Name: Flowgate Methodology

Description: To increase consistency and reliability in the


3 - Updated with term "Remedial Action Scheme" and
MOD-030-3 R10 development and documentation of transfer capability MOD-30-2 TSP
align with definition thereto
calculations for short-term use performed by entities using the
Flowgate Methodology to support analysis and system
operations.

Name: Flowgate Methodology

Description: To increase consistency and reliability in the


3 - Updated with term "Remedial Action Scheme" and
MOD-030-3 R11 development and documentation of transfer capability MOD-30-2 TSP
align with definition thereto
calculations for short-term use performed by entities using the
Flowgate Methodology to support analysis and system
operations.
Name: Demand Energy Data

Description: To provide authority for applicable entities to collect


MOD-031-2 R1 MOD-031-1 2 - No Material Changes to the Requirements BA, PC
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.

Name: Demand Energy Data

Description: To provide authority for applicable entities to collect


MOD-031-2 R2 MOD-031-1 2 - No Material Changes to the Requirements BA, PC
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.

Name: Demand Energy Data

Description: To provide authority for applicable entities to collect


MOD-031-2 R3 MOD-031-1 2 - Change reference from R2 to R1 BA, PC
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.

Name: Demand Energy Data


2 - Provides an exclusion clause pertaining to
Description: To provide authority for applicable entities to collect Confidentilaity of BES data as per NERC Rules of
MOD-031-2 R4 MOD-031-1 BA, PC, TP, RP, LSE, DP
Demand, energy and related data to support reliability studies Procedure
and assessments and to enumerate the responsibilities and
obligations of requestors and respondents of that data.

Name: Protection System and Remedial Action Scheme


Misoperation
2 - Updated with term "Remedial Action Scheme" and
PRC-004-WECC-2 R1 Description: Regional Reliability Standard to ensure all PRC-004-WECC-1 align with definition thereto; Updated relevant tables for GO, TO
transmission and generation Protection System and Remedial applicable entities
Action Scheme (RAS) Misoperations on Transmission Paths and
RAS defined in section 4 are analyzed and/or mitigated.

Name: Protection System and Remedial Action Scheme


Misoperation
2 - Updated with term "Remedial Action Scheme" and
PRC-004-WECC-2 R2 Description: Regional Reliability Standard to ensure all PRC-004-WECC-1 align with definition thereto; Updated relevant tables for GO, TO
transmission and generation Protection System and Remedial applicable entities
Action Scheme (RAS) Misoperations on Transmission Paths and
RAS defined in section 4 are analyzed and/or mitigated.
Name: Protection System and Remedial Action Scheme
Misoperation
2 - Updated with term "Remedial Action Scheme" and
PRC-004-WECC-2 R3 Description: Regional Reliability Standard to ensure all PRC-004-WECC-1 align with definition thereto; Updated relevant tables for GO, TO
transmission and generation Protection System and Remedial applicable entities
Action Scheme (RAS) Misoperations on Transmission Paths and
RAS defined in section 4 are analyzed and/or mitigated.

Name: Protection System, Automatic Reclosing, and Sudden


Pressure Relaying Maintenance
2 - Updated to include Automatic Reclosers and
PRC-005-6 R1 Description: To document and implement programs for the PRC-005-2(i) DP, GO, TO
Sudden Pressure Relaying
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.

Name: Protection System, Automatic Reclosing, and Sudden


Pressure Relaying Maintenance

PRC-005-6 R2 Description: To document and implement programs for the PRC-005-2(i) 2 - No Material Changes to the Requirements DP, GO, TO
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.

Name: Protection System, Automatic Reclosing, and Sudden


Pressure Relaying Maintenance
2 - Updated to include Automatic Reclosers and
PRC-005-6 R3 Description: To document and implement programs for the PRC-005-2(i) DP, GO, TO
Sudden Pressure Relaying
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.

Name: Protection System, Automatic Reclosing, and Sudden


Pressure Relaying Maintenance
2 - Updated to include Automatic Reclosers and
PRC-005-6 R4 Description: To document and implement programs for the PRC-005-2(i) DP, GO, TO
Sudden Pressure Relaying
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.

Name: Protection System, Automatic Reclosing, and Sudden


Pressure Relaying Maintenance
2 - Updated to include Automatic Reclosers and
PRC-005-6 R5 Description: To document and implement programs for the PRC-005-2(i) DP, GO, TO
Sudden Pressure Relaying
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.
Name: Remedial Action Scheme Data and Documentation

Description: To ensure that all Remedial Action Schemes (RAS)


1 - Updated with term "Remedial Action Scheme" and
PRC-015-1 R1 are properly designed, meet performance requirements, and are PRC-015-0 DP, GO, TO
align with definition
coordinated with other protection systems. To ensure that
maintenance and testing programs are developed and
misoperations are analyzed and corrected.

Name: Remedial Action Scheme Data and Documentation

Description: To ensure that all Remedial Action Schemes (RAS)


1 - Updated with term "Remedial Action Scheme" and
PRC-015-1 R2 are properly designed, meet performance requirements, and are PRC-015-0 DP, GO, TO
align with definition
coordinated with other protection systems. To ensure that
maintenance and testing programs are developed and
misoperations are analyzed and corrected.

Name: Remedial Action Scheme Data and Documentation

Description: To ensure that all Remedial Action Schemes (RAS)


1 - Updated with term "Remedial Action Scheme" and
PRC-015-1 R3 are properly designed, meet performance requirements, and are PRC-015-0 DP, GO, TO
align with definition
coordinated with other protection systems. To ensure that
maintenance and testing programs are developed and
misoperations are analyzed and corrected.

Name: Remedial Action Scheme Misoperations

Description: To ensure that all Remedial Action Schemes (RAS)


1 - Updated with term "Remedial Action Scheme" and
PRC-016-1 R1 are properly designed, meet performance requirements, and are PRC-016-0.1 DP, GO, TO
align with definition
coordinated with other protection systems. To ensure that
maintenance and testing programs are developed and
misoperations are analyzed and corrected.

Name: Remedial Action Scheme Misoperations

Description: To ensure that all Remedial Action Schemes (RAS)


1 - Updated with term "Remedial Action Scheme" and
PRC-016-1 R2 are properly designed, meet performance requirements, and are PRC-016-0.1 DP, GO, TO
align with definition
coordinated with other protection systems. To ensure that
maintenance and testing programs are developed and
misoperations are analyzed and corrected.

Name: Remedial Action Scheme Misoperations

Description: To ensure that all Remedial Action Schemes (RAS)


1 - Updated with term "Remedial Action Scheme" and
PRC-016-1 R3 are properly designed, meet performance requirements, and are PRC-016-0.1 DP, GO, TO
align with definition
coordinated with other protection systems. To ensure that
maintenance and testing programs are developed and
misoperations are analyzed and corrected.
Name: Remedial Action Scheme Maintenance and Testing

Description: To ensure that all Remedial Action Schemes (RAS)


1 - Updated with term "Remedial Action Scheme" and
PRC-017-1 R1 are properly designed, meet performance requirements, and are PRC-017-0 DP, GO, TO
align with definition
coordinated with other protection systems. To ensure that
maintenance and testing programs are developed and
misoperations are analyzed and corrected.

Name: Remedial Action Scheme Maintenance and Testing

Description: To ensure that all Remedial Action Schemes (RAS)


1 - Updated with term "Remedial Action Scheme" and
PRC-017-1 R2 are properly designed, meet performance requirements, and are PRC-017-0 DP, GO, TO
align with definition
coordinated with other protection systems. To ensure that
maintenance and testing programs are developed and
misoperations are analyzed and corrected.

Name: Transmission Relay Loadability

Description: Protective relay settings shall not limit transmission


1 - Updated with term "Remedial Action Scheme" and
PRC-023-4 R1 loadability; not interfere with system operators’ ability to take PRC-023-3 DP, GO, TO
align with definition
remedial action to protect system reliability and; be set to reliably
detect all fault conditions and protect the electrical network from
these faults.

Name: Transmission Relay Loadability

Description: Protective relay settings shall not limit transmission


1 - Updated with term "Remedial Action Scheme" and
PRC-023-4 R2 loadability; not interfere with system operators’ ability to take PRC-023-3 DP, GO, TO
align with definition
remedial action to protect system reliability and; be set to reliably
detect all fault conditions and protect the electrical network from
these faults.

Name: Transmission Relay Loadability

Description: Protective relay settings shall not limit transmission


1 - Updated with term "Remedial Action Scheme" and
PRC-023-4 R3 loadability; not interfere with system operators’ ability to take PRC-023-3 DP, GO, TO
align with definition
remedial action to protect system reliability and; be set to reliably
detect all fault conditions and protect the electrical network from
these faults.

Name: Transmission Relay Loadability

Description: Protective relay settings shall not limit transmission


1 - Updated with term "Remedial Action Scheme" and
PRC-023-4 R4 loadability; not interfere with system operators’ ability to take PRC-023-3 DP, GO, TO
align with definition
remedial action to protect system reliability and; be set to reliably
detect all fault conditions and protect the electrical network from
these faults.
Name: Transmission Relay Loadability

Description: Protective relay settings shall not limit transmission


1 - Updated with term "Remedial Action Scheme" and
PRC-023-4 R5 loadability; not interfere with system operators’ ability to take PRC-023-3 DP, GO, TO
align with definition
remedial action to protect system reliability and; be set to reliably
detect all fault conditions and protect the electrical network from
these faults.

Name: Transmission Relay Loadability

Description: Protective relay settings shall not limit transmission


1 - Updated with term "Remedial Action Scheme" and
PRC-023-4 R6 loadability; not interfere with system operators’ ability to take PRC-023-3 PC
align with definition
remedial action to protect system reliability and; be set to reliably
detect all fault conditions and protect the electrical network from
these faults.

Name: Relay Performance During Stable Power Swings

PRC-026-1 R1 Desription: To ensure that load-responsive protective relays are NEW N/A PC
expected to not trip in response to stable power swings during
non-Fault conditions.

Name: Relay Performance During Stable Power Swings

PRC-026-1 R2 Desription: To ensure that load-responsive protective relays are NEW N/A GO, TO
expected to not trip in response to stable power swings during
non-Fault conditions.

Name: Relay Performance During Stable Power Swings

PRC-026-1 R3 Desription: To ensure that load-responsive protective relays are NEW N/A GO, TO
expected to not trip in response to stable power swings during
non-Fault conditions.

Name: Relay Performance During Stable Power Swings

PRC-026-1 R4 Desription: To ensure that load-responsive protective relays are NEW N/A GO, TO
expected to not trip in response to stable power swings during
non-Fault conditions.
Name: Transmission Operations
3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R1 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
TOP TOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.

Name: Transmission Operations


3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R2 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
BA TOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.

Name: Transmission Operations


3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R3 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
BA,DP, GOP
TOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.

Name: Transmission Operations


3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R4 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
BA,DP, GOP
TOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.

Name: Transmission Operations


3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R5 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
DP, GOP, TOP
TOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.

Name: Transmission Operations


3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R6 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
DP, GOP, TOP
TOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.
Name: Transmission Operations
3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R7 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
TOP TOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.

Name: Transmission Operations


3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R8 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
TOP TOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.

Name: Transmission Operations


3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R9 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
BA, TOPTOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.

Name: Transmission Operations


3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R10 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
TOP TOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.

Name: Transmission Operations


3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R11 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
BA TOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.

Name: Transmission Operations


3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R12 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
TOP TOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.
Name: Transmission Operations
3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R13 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
TOP TOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.

Name: Transmission Operations


3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R14 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
TOP TOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.

Name: Transmission Operations


3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R15 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
TOP TOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.

Name: Transmission Operations


3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R16 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
TOP TOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.

Name: Transmission Operations


3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R17 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
BA TOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.

Name: Transmission Operations


3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R18 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
TOP TOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.
Name: Transmission Operations
3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R19 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
TOP TOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.

Name: Transmission Operations


3 - Update with new definitions for Operator Area and
Operating Instructions.
Description: To prevent instability, uncontrolled separation, or
TOP-001-3 R20 TOP-001-1a; in conjunction with TOP-002-4,
3 - Include
TOP-003-3,
new requirements
also replacesfor
TOP-002-2.1b,
monitoring and
TOP-003-1, TOP-004-2, TOP-005-2a,
BA TOP-006-2, TOP-007-0, TOP-008-1 .
Cascading outages that adversely impact the reliability of the
managing System Operating Limits.
Interconnection by ensuring prompt action to prevent or mitigate
3 - Enhance data sharing.
such occurrences.

Name: Operations Planning


4 - Update with new definitions for Operator Area and
Operating Planning Analysis
TOP-002-4 R1 Description: To ensure that Transmission Operators and TOP-002-2.1b; in conjunction with TOP-001-3 and TOP-003-3, also replaces TOP-001-1a, TOP-003-1, TOP-004-2, TOP-005-2a,
TOP TOP-006-2, TOP-007-0, TOP-008-1.
4 - Include new requirements for monitoring and
Balancing Authorities have plans for operating within specified
managing System Operating Limits.
limits.

Name: Operations Planning


4 - Update with new definitions for Operator Area and
Operating Planning Analysis
TOP-002-4 R2 Description: To ensure that Transmission Operators and TOP-002-2.1b; in conjunction with TOP-001-3 and TOP-003-3, also replaces TOP-001-1a, TOP-003-1, TOP-004-2, TOP-005-2a,
TOP TOP-006-2, TOP-007-0, TOP-008-1.
4 - Include new requirements for monitoring and
Balancing Authorities have plans for operating within specified
managing System Operating Limits.
limits.

Name: Operations Planning


4 - Update with new definitions for Operator Area and
Operating Planning Analysis
TOP-002-4 R3 Description: To ensure that Transmission Operators and TOP-002-2.1b; in conjunction with TOP-001-3 and TOP-003-3, also replaces TOP-001-1a, TOP-003-1, TOP-004-2, TOP-005-2a,
TOP TOP-006-2, TOP-007-0, TOP-008-1.
4 - Include new requirements for monitoring and
Balancing Authorities have plans for operating within specified
managing System Operating Limits.
limits.

Name: Operations Planning


4 - Update with new definitions for Operator Area and
Operating Planning Analysis
TOP-002-4 R4 Description: To ensure that Transmission Operators and TOP-002-2.1b; in conjunction with TOP-001-3 and TOP-003-3, also replaces TOP-001-1a, TOP-003-1, TOP-004-2, TOP-005-2a,
BA TOP-006-2, TOP-007-0, TOP-008-1.
4 - Include new requirements for monitoring and
Balancing Authorities have plans for operating within specified
managing System Operating Limits.
limits.
Name: Operations Planning
4 - Update with new definitions for Operator Area and
Operating Planning Analysis
TOP-002-4 R5 Description: To ensure that Transmission Operators and TOP-002-2.1b; in conjunction with TOP-001-3 and TOP-003-3, also replaces TOP-001-1a, TOP-003-1, TOP-004-2, TOP-005-2a,
BA TOP-006-2, TOP-007-0, TOP-008-1.
4 - Include new requirements for monitoring and
Balancing Authorities have plans for operating within specified
managing System Operating Limits.
limits.

Name: Operations Planning


4 - Update with new definitions for Operator Area and
Operating Planning Analysis
TOP-002-4 R6 Description: To ensure that Transmission Operators and TOP-002-2.1b; in conjunction with TOP-001-3 and TOP-003-3, also replaces TOP-001-1a, TOP-003-1, TOP-004-2, TOP-005-2a,
TOP TOP-006-2, TOP-007-0, TOP-008-1.
4 - Include new requirements for monitoring and
Balancing Authorities have plans for operating within specified
managing System Operating Limits.
limits.

Name: Operations Planning


4 - Update with new definitions for Operator Area and
Operating Planning Analysis
TOP-002-4 R7 Description: To ensure that Transmission Operators and TOP-002-2.1b; in conjunction with TOP-001-3 and TOP-003-3, also replaces TOP-001-1a, TOP-003-1, TOP-004-2, TOP-005-2a,
BA TOP-006-2, TOP-007-0, TOP-008-1.
4 - Include new requirements for monitoring and
Balancing Authorities have plans for operating within specified
managing System Operating Limits.
limits.

3 - Update with new definitions for Operational Planning


Name: Operational Reliability Data Analysis,Real-time Assessment and include reference
to System Operating Limits
TOP-003-3 R1 Description: To ensure that the Transmission Operator and TOP-003-1; in conjunction with TOP-001-3
3 - and
Expanded
TOP-002-4,
requirement
also replaces
to include
TOP-001-1a,
non-BES data
TOP-002-2.1b,
and TOP-004-2, TOP-005-2a,
TOP TOP-006-2, TOP-007-0, TOP-008-1.
Balancing Authority have data needed to fulfill their operational external network data
and planning responsibilities. 3 - Upgraded notification and communication
requirements

3 - Update with new definitions for Operational Planning


Name: Operational Reliability Data Analysis,Real-time Assessment and include reference
to System Operating Limits
TOP-003-3 R2 Description: To ensure that the Transmission Operator and TOP-003-1; in conjunction with TOP-001-3
3 - and
Expanded
TOP-002-4,
requirement
also replaces
to include
TOP-001-1a,
non-BES data
TOP-002-2.1b,
and TOP-004-2, TOP-005-2a,
BA TOP-006-2, TOP-007-0, TOP-008-1.
Balancing Authority have data needed to fulfill their operational external network data
and planning responsibilities. 3 - Upgraded notification and communication
requirements

3 - Update with new definitions for Operational Planning


Name: Operational Reliability Data Analysis,Real-time Assessment and include reference
to System Operating Limits
TOP-003-3 R3 Description: To ensure that the Transmission Operator and TOP-003-1; in conjunction with TOP-001-3
3 - and
Expanded
TOP-002-4,
requirement
also replaces
to include
TOP-001-1a,
non-BES data
TOP-002-2.1b,
and TOP-004-2, TOP-005-2a,
TOP TOP-006-2, TOP-007-0, TOP-008-1.
Balancing Authority have data needed to fulfill their operational external network data
and planning responsibilities. 3 - Upgraded notification and communication
requirements
3 - Update with new definitions for Operational Planning
Name: Operational Reliability Data Analysis,Real-time Assessment and include reference
to System Operating Limits
TOP-003-3 R4 Description: To ensure that the Transmission Operator and TOP-003-1; in conjunction with TOP-001-3
3 - and
Expanded
TOP-002-4,
requirement
also replaces
to include
TOP-001-1a,
non-BES data
TOP-002-2.1b,
and TOP-004-2, TOP-005-2a,
BA TOP-006-2, TOP-007-0, TOP-008-1.
Balancing Authority have data needed to fulfill their operational external network data
and planning responsibilities. 3 - Upgraded notification and communication
requirements

3 - Update with new definitions for Operational Planning


Name: Operational Reliability Data Analysis,Real-time Assessment and include reference
to System Operating Limits
TOP-003-3 R5 Description: To ensure that the Transmission Operator and TOP-003-1; in conjunction with TOP-001-3
3 - and
Expanded
TOP-002-4,
requirement
also replaces
to include
TOP-001-1a,
non-BES data
TOP-002-2.1b,
and TOP-004-2,
TOP, BA, GO,
TOP-005-2a,
GOP, LSE,
TOP-006-2,
TO, DP TOP-007-0, TOP-008-1.
Balancing Authority have data needed to fulfill their operational external network data
and planning responsibilities. 3 - Upgraded notification and communication
requirements

Name: Real-time Reliability Monitoring and Analysis Capabilities


TOP-010-1 R1 NEW N/A TOP
Description: Establish requirements for Real-time monitoring and
analysis capabilities to support reliable System operations.

Name: Real-time Reliability Monitoring and Analysis Capabilities


TOP-010-1 R2 NEW N/A BA
Description: Establish requirements for Real-time monitoring and
analysis capabilities to support reliable System operations.

Name: Real-time Reliability Monitoring and Analysis Capabilities


TOP-010-1 R3 NEW N/A TOP
Description: Establish requirements for Real-time monitoring and
analysis capabilities to support reliable System operations.

Name: Real-time Reliability Monitoring and Analysis Capabilities


TOP-010-1 R4 NEW N/A BA,TOP
Description: Establish requirements for Real-time monitoring and
analysis capabilities to support reliable System operations.
TPL-001-0.1

TPL-002-0b
Name: Transmission System Planning Performance
Requirements
4 - Complete revision. Revision of TPL-001-1; includes
merging and upgrading requirements of TPL-001-0,
TPL-001-4 R1 Description: Establish Transmission system planning TPL-002-0, TPL-003-0, and TPL-004-0 into one, single, TP, PC
performance requirements within the planning horizon to develop comprehensive, coordinated standard: TPL-001-2; and
a Bulk Electric System (BES) that will operate reliably over a retirement of TPL-005-0 and TPL-006-0.
broad spectrum of System conditions and following a wide range
of probable Contingencies.
TPL-003-0b

TPL-004-0a

TPL-001-0.1

TPL-002-0b
Name: Transmission System Planning Performance
Requirements
4 - Complete revision. Revision of TPL-001-1; includes
merging and upgrading requirements of TPL-001-0,
TPL-001-4 R2 Description: Establish Transmission system planning TPL-002-0, TPL-003-0, and TPL-004-0 into one, single, TP, PC
performance requirements within the planning horizon to develop comprehensive, coordinated standard: TPL-001-2; and
a Bulk Electric System (BES) that will operate reliably over a retirement of TPL-005-0 and TPL-006-0.
broad spectrum of System conditions and following a wide range
of probable Contingencies.
Name: Transmission System Planning Performance
Requirements
4 - Complete revision. Revision of TPL-001-1; includes
merging and upgrading requirements of TPL-001-0,
TPL-001-4 R2 Description: Establish Transmission system planning TPL-002-0, TPL-003-0, and TPL-004-0 into one, single, TP, PC
performance requirements within the planning horizon to develop comprehensive, coordinated standard: TPL-001-2; and
a Bulk Electric System (BES) that will operate reliably over a retirement of TPL-005-0 and TPL-006-0.
broad spectrum of System conditions and following a wide range
of probable Contingencies.
TPL-003-0b

TPL-004-0a

TPL-001-0.1

TPL-002-0b
Name: Transmission System Planning Performance
Requirements
4 - Complete revision. Revision of TPL-001-1; includes
merging and upgrading requirements of TPL-001-0,
TPL-001-4 R3 Description: Establish Transmission system planning TPL-002-0, TPL-003-0, and TPL-004-0 into one, single, TP, PC
performance requirements within the planning horizon to develop comprehensive, coordinated standard: TPL-001-2; and
a Bulk Electric System (BES) that will operate reliably over a retirement of TPL-005-0 and TPL-006-0.
broad spectrum of System conditions and following a wide range
of probable Contingencies.
TPL-003-0b

TPL-004-0a
TPL-001-0.1

TPL-002-0b
Name: Transmission System Planning Performance
Requirements
4 - Complete revision. Revision of TPL-001-1; includes
merging and upgrading requirements of TPL-001-0,
TPL-001-4 R4 Description: Establish Transmission system planning TPL-002-0, TPL-003-0, and TPL-004-0 into one, single, TP, PC
performance requirements within the planning horizon to develop comprehensive, coordinated standard: TPL-001-2; and
a Bulk Electric System (BES) that will operate reliably over a retirement of TPL-005-0 and TPL-006-0.
broad spectrum of System conditions and following a wide range
of probable Contingencies.
TPL-003-0b

TPL-004-0a

TPL-001-0.1

TPL-002-0b
Name: Transmission System Planning Performance
Requirements
4 - Complete revision. Revision of TPL-001-1; includes
merging and upgrading requirements of TPL-001-0,
TPL-001-4 R5 Description: Establish Transmission system planning TPL-002-0, TPL-003-0, and TPL-004-0 into one, single, TP, PC
performance requirements within the planning horizon to develop comprehensive, coordinated standard: TPL-001-2; and
a Bulk Electric System (BES) that will operate reliably over a retirement of TPL-005-0 and TPL-006-0.
broad spectrum of System conditions and following a wide range
of probable Contingencies.
Name: Transmission System Planning Performance
Requirements
4 - Complete revision. Revision of TPL-001-1; includes
merging and upgrading requirements of TPL-001-0,
TPL-001-4 R5 Description: Establish Transmission system planning TPL-002-0, TPL-003-0, and TPL-004-0 into one, single, TP, PC
performance requirements within the planning horizon to develop comprehensive, coordinated standard: TPL-001-2; and
a Bulk Electric System (BES) that will operate reliably over a retirement of TPL-005-0 and TPL-006-0.
broad spectrum of System conditions and following a wide range
of probable Contingencies.
TPL-003-0b

TPL-004-0a

TPL-001-0.1

TPL-002-0b
Name: Transmission System Planning Performance
Requirements
4 - Complete revision. Revision of TPL-001-1; includes
merging and upgrading requirements of TPL-001-0,
TPL-001-4 R6 Description: Establish Transmission system planning TPL-002-0, TPL-003-0, and TPL-004-0 into one, single, TP, PC
performance requirements within the planning horizon to develop comprehensive, coordinated standard: TPL-001-2; and
a Bulk Electric System (BES) that will operate reliably over a retirement of TPL-005-0 and TPL-006-0.
broad spectrum of System conditions and following a wide range
of probable Contingencies.
TPL-003-0b

TPL-004-0a
TPL-001-0.1

TPL-002-0b
Name: Transmission System Planning Performance
Requirements
4 - Complete revision. Revision of TPL-001-1; includes
merging and upgrading requirements of TPL-001-0,
TPL-001-4 R7 Description: Establish Transmission system planning TPL-002-0, TPL-003-0, and TPL-004-0 into one, single, PC
performance requirements within the planning horizon to develop comprehensive, coordinated standard: TPL-001-2; and
a Bulk Electric System (BES) that will operate reliably over a retirement of TPL-005-0 and TPL-006-0.
broad spectrum of System conditions and following a wide range
of probable Contingencies.
TPL-003-0b

TPL-004-0a

TPL-001-0.1

TPL-002-0b
Name: Transmission System Planning Performance
Requirements
4 - Complete revision. Revision of TPL-001-1; includes
merging and upgrading requirements of TPL-001-0,
TPL-001-4 R8 Description: Establish Transmission system planning TPL-002-0, TPL-003-0, and TPL-004-0 into one, single, TP, PC
performance requirements within the planning horizon to develop comprehensive, coordinated standard: TPL-001-2; and
a Bulk Electric System (BES) that will operate reliably over a retirement of TPL-005-0 and TPL-006-0.
broad spectrum of System conditions and following a wide range
of probable Contingencies.
Name: Transmission System Planning Performance
Requirements
4 - Complete revision. Revision of TPL-001-1; includes
merging and upgrading requirements of TPL-001-0,
TPL-001-4 R8 Description: Establish Transmission system planning TPL-002-0, TPL-003-0, and TPL-004-0 into one, single, TP, PC
performance requirements within the planning horizon to develop comprehensive, coordinated standard: TPL-001-2; and
a Bulk Electric System (BES) that will operate reliably over a retirement of TPL-005-0 and TPL-006-0.
broad spectrum of System conditions and following a wide range
of probable Contingencies.
TPL-003-0b

TPL-004-0a

Name: Transmission System Planned Performance for


Geomagnetic Disturbance Events
TPL-007-1 R1 NEW N/A PC, TP
Description: Establish requirements for Transmission system
planned performance during geomagnetic disturbance (GMD)
events.

Name: Transmission System Planned Performance for


Geomagnetic Disturbance Events
TPL-007-1 R2 NEW N/A PC, TP
Description: Establish requirements for Transmission system
planned performance during geomagnetic disturbance (GMD)
events.

Name: Transmission System Planned Performance for


Geomagnetic Disturbance Events
TPL-007-1 R3 NEW N/A PC, TP
Description: Establish requirements for Transmission system
planned performance during geomagnetic disturbance (GMD)
events.

Name: Transmission System Planned Performance for


Geomagnetic Disturbance Events
TPL-007-1 R4 NEW N/A PC, TP
Description: Establish requirements for Transmission system
planned performance during geomagnetic disturbance (GMD)
events.
Name: Transmission System Planned Performance for
Geomagnetic Disturbance Events
TPL-007-1 R5 NEW N/A PC, TP
Description: Establish requirements for Transmission system
planned performance during geomagnetic disturbance (GMD)
events.

Name: Transmission System Planned Performance for


Geomagnetic Disturbance Events
TPL-007-1 R6 NEW N/A TO, GO
Description: Establish requirements for Transmission system
planned performance during geomagnetic disturbance (GMD)
events.

Name: Transmission System Planned Performance for


Geomagnetic Disturbance Events
TPL-007-1 R7 NEW N/A PC, TP
Description: Establish requirements for Transmission system
planned performance during geomagnetic disturbance (GMD)
events.
not be relied upon for any other purpose.

FERC Order No., Order Date and Order Publication US Effective Date of FERC Order Ruling Approving FERC Approved Standard/Requirement Implementation Time Provided and US Enforcement Date
Date Standard(s) (Each cell is linked to the respective implementation plan and effective dates if applicable)
(Each cell is linked to the respective FERC Order if (Each cell is linked to the respective effective dates
applicable) of the FERC Approval Ruling if applicable)

Implementation Time: In those jurisdictions where regulatory approval is required, all requirements become
Docket No. RM12-16-000; Order No. 785; September effective upon approval.
25-Nov-2013
19, 2013
US Enforcement Date: 2013-11-25

Implementation Time: Twenty-four months after the first day of the first calendar quarter following applicable
Docket No. RM10-16-000; Order No. 749; March 17, regulatory approval.
23-May-2011
2011
US Enforcement Date: 2013-07-01

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an
Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an
Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an
Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an
Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RM15-14-000; January 21, 2016 31-Mar-2016 Implementation Time: The later of April 1, 2016 or the first day of the first calendar quarter that is three calendar months after the date that the standard is approved by an

Docket No. RD16-9-000; October 28, 2016 28-Oct-2016 Implementation Plan: The first day of the first calendar quarter that is nine (9) months after the date that the standards is approved by the applicable gov
Docket No. RD16-9-000; October 28, 2016 28-Oct-2016 Implementation Plan: The first day of the first calendar quarter that is nine (9) months after the date that the standards is approved by the applicable gov

Docket No. RD16-9-000; October 28, 2016 28-Oct-2016 Implementation Plan: The first day of the first calendar quarter that is nine (9) months after the date that the standards is approved by the applicable gov

Docket No. RD16-9-000; October 28, 2016 28-Oct-2016 Implementation Plan: The first day of the first calendar quarter that is nine (9) months after the date that the standards is approved by the applicable gov

Docket No. RD16-9-000; October 28, 2016 28-Oct-2016 Implementation Plan: The first day of the first calendar quarter that is nine (9) months after the date that the standards is approved by the applicable gov

Docket No. RD16-9-000; October 28, 2016 28-Oct-2016 Implementation Plan: The first day of the first calendar quarter that is nine (9) months after the date that the standards is approved by the applicable gov

Docket No. RD16-9-000; October 28, 2016 28-Oct-2016 Implementation Plan: The first day of the first calendar quarter that is nine (9) months after the date that the standards is approved by the applicable gov
Docket No. RD16-9-000; October 28, 2016 28-Oct-2016 Implementation Plan: The first day of the first calendar quarter that is nine (9) months after the date that the standards is approved by the applicable gov

Docket No. RD16-9-000; October 28, 2016 28-Oct-2016 Implementation Plan: The first day of the first calendar quarter that is nine (9) months after the date that the standards is approved by the applicable gov

Docket No. RD16-9-000; October 28, 2016 28-Oct-2016 Implementation Plan: The first day of the first calendar quarter that is nine (9) months after the date that the standards is approved by the applicable gov

Docket No. RD16-9-000; October 28, 2016 28-Oct-2016 Implementation Plan: The first day of the first calendar quarter that is nine (9) months after the date that the standards is approved by the applicable gov

Docket No. RD16-9-000; October 28, 2016 28-Oct-2016 Implementation Plan: The first day of the first calendar quarter that is nine (9) months after the date that the standards is approved by the applicable gov

Docket No. RD16-9-000; October 28, 2016 28-Oct-2016 Implementation Plan: The first day of the first calendar quarter that is nine (9) months after the date that the standards is approved by the applicable gov
Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015The Reliability Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standards an

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015The Reliability Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standards an

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015The Reliability Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standards an
Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015The Reliability Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standards an

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015The Reliability Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standards an

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015The Reliability Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standards an

Docket No. RD16-4-000; March 14, 2016 26-Apr-2016 Implementation Plan: The first day of the first calendar quarter that is 3 months after the effective date of the applicable governmental authority’s order a

Docket No. RD16-4-000; March 14, 2016 26-Apr-2016 Implementation Plan: The first day of the first calendar quarter that is 3 months after the effective date of the applicable governmental authority’s order a

Docket No. RD16-4-000; March 14, 2016 26-Apr-2016 Implementation Plan: The first day of the first calendar quarter that is 3 months after the effective date of the applicable governmental authority’s order a
Docket No. RD16-4-000; March 14, 2016 26-Apr-2016 Implementation Plan: The first day of the first calendar quarter that is 3 months after the effective date of the applicable governmental authority’s order a

Docket No. RD16-4-000; March 14, 2016 26-Apr-2016 Implementation Plan: The first day of the first calendar quarter that is 3 months after the effective date of the applicable governmental authority’s order a

Docket No. RD16-4-000; March 14, 2016 26-Apr-2016 Implementation Plan: The first day of the first calendar quarter that is 3 months after the effective date of the applicable governmental authority’s order a

Docket No. RD16-4-000; March 14, 2016 26-Apr-2016 Implementation Plan: The first day of the first calendar quarter that is 3 months after the effective date of the applicable governmental authority’s order a

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o
Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o
Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an
Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an
Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RD15-7-000; December 04, 2015 4-Dec-2015 Reliability Standard IRO-009-2 shall become effective on the first day of the first calendar quarter after the date that the standard is approved by an app

Docket No. RD15-7-000; December 04, 2015 4-Dec-2015 Reliability Standard IRO-009-2 shall become effective on the first day of the first calendar quarter after the date that the standard is approved by an app

Docket No. RD15-7-000; December 04, 2015 4-Dec-2015 Reliability Standard IRO-009-2 shall become effective on the first day of the first calendar quarter after the date that the standard is approved by an app

Docket No. RD15-7-000; December 04, 2015 4-Dec-2015 Reliability Standard IRO-009-2 shall become effective on the first day of the first calendar quarter after the date that the standard is approved by an app
Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Requirement R1 shall become effective on the first day of the first calendar quarter that is nine (9) months after the date that the standard is approved b

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Requirement R2 shall become effective on the first day of the first calendar quarter that is nine (9) months after the date that the standard is approved b

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Requirement R3 shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approve

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an
Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an
Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RD16-6-000; September 22, 2016 22-Sep-2016 All Requirements shall become effective on the first day of the first calendar quarter that is 18 months after the date that this standard is approved by an

Docket No. RD16-6-000; September 22, 2016 22-Sep-2016 All Requirements shall become effective on the first day of the first calendar quarter that is 18 months after the date that this standard is approved by an

Docket No. RD16-6-000; September 22, 2016 22-Sep-2016 All Requirements shall become effective on the first day of the first calendar quarter that is 18 months after the date that this standard is approved by an

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o
Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o
Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o
Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o
Docket No. RM14-12-000, Order No. 804; Issue Date: February 19, 2015; Publication
27-Apr-2015
Date: February 24, 2015 Standard becomes effective on the first day of the first calendar quarter that is six months after the date that this standard is approved by applicable reg

Docket No. RM14-12-000, Order No. 804; Issue Date: February 19, 2015; Publication
27-Apr-2015
Date: February 24, 2015 Standard becomes effective on the first day of the first calendar quarter that is six months after the date that this standard is approved by applicable reg

Docket No. RM14-12-000, Order No. 804; Issue Date: February 19, 2015; Publication
27-Apr-2015
Date: February 24, 2015 Standard becomes effective on the first day of the first calendar quarter that is six months after the date that this standard is approved by applicable reg

Docket No. RM14-12-000, Order No. 804; Issue Date: February 19, 2015; Publication
27-Apr-2015
Date: February 24, 2015 Standard becomes effective on the first day of the first calendar quarter that is six months after the date that this standard is approved by applicable reg

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o
Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RD16-2-000; December 18, 2015 18-Dec-2015 Implementation Plan: The first full day of the first calendar quarter after the date that the standard is approved by an applicable regulatory authorities.

Docket No. RD16-2-000; December 18, 2015 18-Dec-2015 Implementation Plan: The first full day of the first calendar quarter after the date that the standard is approved by an applicable regulatory authorities.

Docket No. RD16-2-000; December 18, 2015 18-Dec-2015 Implementation Plan: The first full day of the first calendar quarter after the date that the standard is approved by an applicable regulatory authorities.

Docket No. RD16-2-000; December 18, 2015 18-Dec-2015 Implementation Plan: The first full day of the first calendar quarter after the date that the standard is approved by an applicable regulatory authorities.

Docket No. RD16-2-000; December 18, 2015 18-Dec-2015 Implementation Plan: The first full day of the first calendar quarter after the date that the standard is approved by an applicable regulatory authorities.
Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o
Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015Implementation Plan: The first day of the first calendar quarter that is tewelve months beyond the date that this standard is approved by applicable regu

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o
Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-13-000, Order No. 818; Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 25, 2015

Except as noted below, the revised Reliability Standards and the revised definition of “Remedial Action Scheme” shall become effective on the first day o

Docket No. RM15-8-000, Order No. 823; Issue Date: March 17, 2016; Publication
23-May-2016
Date: March 24, 2016 Requirement R1First day of the first full calendar year that is 12 months after the date that the standard is approved by an applicable governmental auth

Docket No. RM15-8-000, Order No. 823; Issue Date: March 17, 2016; Publication
23-May-2016
Date: March 24, 2016 Requirement R2First day of the first full calendar year that is 36 months after the date that the standard is approved by an applicable governmental auth

Docket No. RM15-8-000, Order No. 823; Issue Date: March 17, 2016; Publication
23-May-2016
Date: March 24, 2016 Requirement R3First day of the first full calendar year that is 36 months after the date that the standard is approved by an applicable governmental auth

Docket No. RM15-8-000, Order No. 823; Issue Date: March 17, 2016; Publication
23-May-2016
Date: March 24, 2016 Requirement R4First day of the first full calendar year that is 36 months after the date that the standard is approved by an applicable governmental auth
Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an
Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an
Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an
Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an
Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an
Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RM15-16-000, Order No. 817;Issue Date: November 19, 2015; Publication
26-Jan-2016
Date: November 27, 2015 Standard shall become effective on the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an

Docket No. RD16-6-000; September 22, 2016 22-Sep-2016 All Requirements shall become effective on the first day of the first calendar quarter that is 18 months after the date that this standard is approved by an

Docket No. RD16-6-000; September 22, 2016 22-Sep-2016 All Requirements shall become effective on the first day of the first calendar quarter that is 18 months after the date that this standard is approved by an

Docket No. RD16-6-000; September 22, 2016 22-Sep-2016 All Requirements shall become effective on the first day of the first calendar quarter that is 18 months after the date that this standard is approved by an

Docket No. RD16-6-000; September 22, 2016 22-Sep-2016 All Requirements shall become effective on the first day of the first calendar quarter that is 18 months after the date that this standard is approved by an
Docket No. RM12-1-000 and RM13-9-000, Order 786; Issue Date: October 17,23-Dec-2013
2013; Publication Date: October 23,
Requirements
2013 R1 and R7 as well as the definitions shall become effective on the first day of the first calendar quarter, 12 months after applicable regula

Docket No. RM12-1-000 and RM13-9-000, Order 786; Issue Date: October 17,23-Dec-2013
2013; Publication Date: October 23,
Except
2013as indicated below, Requirements R2 through R6 and Requirement R8 shall become effective on the first day of the first calendar quarter, 24 mo
Docket No. RM12-1-000 and RM13-9-000, Order 786; Issue Date: October 17,23-Dec-2013
2013; Publication Date: October 23,
Except
2013as indicated below, Requirements R2 through R6 and Requirement R8 shall become effective on the first day of the first calendar quarter, 24 mo

Docket No. RM12-1-000 and RM13-9-000, Order 786; Issue Date: October 17,23-Dec-2013
2013; Publication Date: October 23,
Except
2013as indicated below, Requirements R2 through R6 and Requirement R8 shall become effective on the first day of the first calendar quarter, 24 mo
Docket No. RM12-1-000 and RM13-9-000, Order 786; Issue Date: October 17,23-Dec-2013
2013; Publication Date: October 23,
Except
2013as indicated below, Requirements R2 through R6 and Requirement R8 shall become effective on the first day of the first calendar quarter, 24 mo

FERC Order 786 dated 10/17/13Docket No. RM12-1-000 and RM13-9-00014523-Dec-2013


FERC ¶ 61,051 Except as indicated below, Requirements R2 through R6 and Requirement R8 shall become effective on the first day of the first calendar quarter, 24 mo
FERC Order 786 dated 10/17/13Docket No. RM12-1-000 and RM13-9-00014523-Dec-2013
FERC ¶ 61,051 Except as indicated below, Requirements R2 through R6 and Requirement R8 shall become effective on the first day of the first calendar quarter, 24 mo

Docket No. RM12-1-000 and RM13-9-000, Order 786; Issue Date: October 17,23-Dec-2013
2013; Publication Date: October 23,
Except
2013as indicated below, Requirements R2 through R6 and Requirement R8 shall become effective on the first day of the first calendar quarter, 24 mo
Docket No. RM12-1-000 and RM13-9-000, Order 786; Issue Date: October 17,23-Dec-2013
2013; Publication Date: October 23,
Requirements
2013 R1 and R7 as well as the definitions shall become effective on the first day of the first calendar quarter, 12 months after applicable regula

Docket No. RM12-1-000 and RM13-9-000, Order 786; Issue Date: October 17,23-Dec-2013
2013; Publication Date: October 23,
Except
2013as indicated below, Requirements R2 through R6 and Requirement R8 shall become effective on the first day of the first calendar quarter, 24 mo
Docket No. RM12-1-000 and RM13-9-000, Order 786; Issue Date: October 17,23-Dec-2013
2013; Publication Date: October 23,
Except
2013as indicated below, Requirements R2 through R6 and Requirement R8 shall become effective on the first day of the first calendar quarter, 24 mo

Docket No. RD15-11-000, Order No. 830; Issue Date: September 22, 2016; Publication
29-Nov-2016
Date: September 30, 2016Implementation Plan: Requirement R1 shall become effective on the first day of the first calendar quarter that is six months after the date that this stand

Docket No. RD15-11-000, Order No. 830; Issue Date: September 22, 2016; Publication
29-Nov-2016
Date: September 30, 2016Implementation Plan: Requirement R2 shall become effective on the first day of the first calendar quarter that is 18 months after the date that this standa

Docket No. RD15-11-000, Order No. 830; Issue Date: September 22, 2016; Publication
29-Nov-2016
Date: September 30, 2016Implementation Plan: Requirement R3, Requirement R4, and Requirement R7 shall become effective on the first day of the first calendar quarter that is

Docket No. RD15-11-000, Order No. 830; Issue Date: September 22, 2016; Publication
29-Nov-2016
Date: September 30, 2016Implementation Plan: Requirement R3, Requirement R4, and Requirement R7 shall become effective on the first day of the first calendar quarter that is
Docket No. RD15-11-000, Order No. 830; Issue Date: September 22, 2016; Publication
29-Nov-2016
Date: September 30, 2016Implementation Plan: Requirement R5 shall become effective on the first day of the first calendar quarter that is 24 months after the date that this standa

Docket No. RD15-11-000, Order No. 830; Issue Date: September 22, 2016; Publication
29-Nov-2016
Date: September 30, 2016Implementation Plan: Requirement R5 shall become effective on the first day of the first calendar quarter that is 48 months after the date that this standa

Docket No. RD15-11-000, Order No. 830; Issue Date: September 22, 2016; Publication
29-Nov-2016
Date: September 30, 2016Implementation Plan: Requirement R3, Requirement R4, and Requirement R7 shall become effective on the first day of the first calendar quarter that is
Estimated Incremental/New Costs Associated with Revision/New
Stakeholder Comments Organizational Activities and Standard/Requirement, if any ($)
BCUC Implementation Time
Reliability/Suitability Impact
(Press Alt-Enter to insert a carriage return in a cell)
(Press Alt-Enter to insert a carriage return in a cell)
Cost Cost
One Time ($) Ongoing ($)

Need to update documentation and implement training. $5,000 0 One year after adoption by the BCUC.

The later of July 1, 2013 (to algin with the U.S. effective date)
No incremental changes expected. 0 0
or Immediately after adoption by the BCUC
Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.
Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.
**NOTE: This requirement was
**NOTE: This requirement was retired by
**NOTE: This requirement was retired by FERC (U.S) on retired by FERC (U.S) on January **NOTE: This requirement was retired by FERC (U.S) on
FERC (U.S) on January 21, 2014. Do not
January 21, 2014. Do not assess this requirement. 21, 2014. Do not assess this January 21, 2014. Do not assess this requirement.
assess this requirement.
requirement.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.
Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.
Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.
Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.
Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.
Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.
Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.

Note: This requirement applies to the Reliability Coordinator Note: This requirement applies to the Reliability Coordinator
function which no B.C. entity is registered as. Please do not N/A N/A function which no B.C. entity is registered as. Please do not
provide feedback here unless necessary. provide feedback here unless necessary.
NOTE: This requirement applies
only to the PC role (not yet defined in NOTE: This requirement applies only to the PC role (not yet
NOTE: This requirement applies only to the PC role (not yet
BC). Only provide feedback if N/A defined in BC). Only provide feedback if necessary here.
defined in BC). Only provide feedback if necessary here.
necessary here.

NOTE: This requirement applies


only to the PC role (not yet defined in
NOTE: This requirement applies only to the PC role (not yet NOTE: This requirement applies only to the PC role (not yet
BC). Only provide feedback if N/A
defined in BC). Only provide feedback if necessary here. defined in BC). Only provide feedback if necessary here.
necessary here.

NOTE: This requirement is


dependent on information provided
NOTE: This requirement is dependent on information NOTE: This requirement is dependent on information provided
by the PC role (not yet defined in
provided by the PC role (not yet defined in BC) pursuant to N/A by the PC role (not yet defined in BC) pursuant to Requirement 1.
BC) pursuant to Requirement 1.
Requirement 1. Only provide feedback if necessary here. Only provide feedback if necessary here.
Only provide feedback if
necessary here.

NOTE: This requirement is


NOTE: This requirement is dependent on information dependent on information provided
NOTE: This requirement is dependent on information provided
provided by the PC role (not yet defined in BC) pursuant to by the PC role (not yet defined in
N/A by the PC role (not yet defined in BC) pursuant to Requirements
Requirements 1 and 2. Only provide feedback if necessary BC) pursuant to Requirements 1 and
1 and 2. Only provide feedback if necessary here.
here. 2. Only provide feedback if
necessary here.

NOTE: This requirement is


NOTE: This requirement is dependent on information dependent on information provided
NOTE: This requirement is dependent on information provided
provided by the PC role (not yet defined in BC) pursuant to by the PC role (not yet defined in
N/A by the PC role (not yet defined in BC) pursuant to Requirements
Requirements 1, 2, and 3. Only provide feedback if BC) pursuant to Requirements 1, 2,
1, 2, and 3. Only provide feedback if necessary here.
necessary here. and 3. Only provide feedback if
necessary here.
NOTE: This standard was originally included for assessment
under Assessment Report No. 8, but adoption was held by the
BCUC pending reassessment per Order R-38-15. As such,
this standard is now up for reassessment.

NOTE: This standard was originally included for assessment


under Assessment Report No. 8, but adoption was held by the
BCUC pending reassessment per Order R-38-15. As such,
this standard is now up for reassessment.
NOTE: This standard was originally included for assessment
under Assessment Report No. 8, but adoption was held by the
BCUC pending reassessment per Order R-38-15. As such,
this standard is now up for reassessment.

NOTE: This standard was originally included for assessment


under Assessment Report No. 8, but adoption was held by the NOTE: This requirement applies to the PC role (not yet defined
BCUC pending reassessment per Order R-38-15. As such, in BC). Only provide feedback if necessary here.
this standard is now up for reassessment.
NOTE: This standard was originally included for assessment
under Assessment Report No. 8, but adoption was held by the
BCUC pending reassessment per Order R-38-15. As such,
this standard is now up for reassessment.

NOTE: This standard was originally included for assessment


under Assessment Report No. 8, but adoption was held by the
BCUC pending reassessment per Order R-38-15. As such,
this standard is now up for reassessment.
NOTE: This standard was originally included for assessment
under Assessment Report No. 8, but adoption was held by the
BCUC pending reassessment per Order R-38-15. As such,
this standard is now up for reassessment.

NOTE: This standard was originally included for assessment


under Assessment Report No. 8, but adoption was held by the
BCUC pending reassessment per Order R-38-15. As such,
this standard is now up for reassessment.
NOTE: This requirement applies to the PC role (not yet
defined in BC) in conjunction with the TP role. Only provide
NOTE: This requirement applies to
feedback if necessary here. This standard was originally NOTE: This requirement applies to the PC
the PC role (not yet defined in BC) in NOTE: This requirement applies to the PC role (not yet defined in
included for assessment under Assessment Report No. 8, but role (not yet defined in BC) in conjunction
conjunction with the TP role. Only BC) in conjunction with the TP role. Only provide feedback if
adoption was held by the BCUC pending reassessment per with the TP role. Only provide feedback if
provide feedback if necessary necessary here.
Order R-38-15. As such, this standard is now up for necessary here.
here.
reassessment.

NOTE: This standard was originally included for assessment


under Assessment Report No. 8, but adoption was held by the
BCUC pending reassessment per Order R-38-15. As such,
this standard is now up for reassessment.
NOTE: This standard was originally included for assessment
under Assessment Report No. 8, but adoption was held by the
BCUC pending reassessment per Order R-38-15. As such,
this standard is now up for reassessment.

NOTE: This requirement applies to


NOTE: This requirement applies to the PC role (not yet the PC role (not yet defined in BC) in NOTE: This requirement applies to the PC role (not yet defined
defined in BC) in conjunction with the TP role. Only provide conjunction with the TP role. Only N/A in BC) in conjunction with the TP role. Only provide feedback if
feedback if necessary here. provide feedback if necessary necessary here.
here.

NOTE: This requirement applies to


NOTE: This requirement applies to the PC role (not yet the PC role (not yet defined in BC) in NOTE: This requirement applies to the PC role (not yet defined
defined in BC) in conjunction with the TP role. Only provide conjunction with the TP role. Only N/A in BC) in conjunction with the TP role. Only provide feedback if
feedback if necessary here. provide feedback if necessary necessary here.
here.

NOTE: This requirement applies to


NOTE: This requirement applies to the PC role (not yet the PC role (not yet defined in BC) in NOTE: This requirement applies to the PC role (not yet defined
defined in BC) in conjunction with the TP role. Only provide conjunction with the TP role. Only N/A in BC) in conjunction with the TP role. Only provide feedback if
feedback if necessary here. provide feedback if necessary necessary here.
here.

NOTE: This requirement applies to


NOTE: This requirement applies to the PC role (not yet the PC role (not yet defined in BC) in NOTE: This requirement applies to the PC role (not yet defined
defined in BC) in conjunction with the TP role. Only provide conjunction with the TP role. Only N/A in BC) in conjunction with the TP role. Only provide feedback if
feedback if necessary here. provide feedback if necessary necessary here.
here.
NOTE: This requirement applies to
NOTE: This requirement applies to the PC role (not yet the PC role (not yet defined in BC) in NOTE: This requirement applies to the PC role (not yet defined
defined in BC) in conjunction with the TP role. Only provide conjunction with the TP role. Only N/A in BC) in conjunction with the TP role. Only provide feedback if
feedback if necessary here. provide feedback if necessary necessary here.
here.

NOTE: This requirement is


dependent on information provided
NOTE: This requirement is dependent on information NOTE: This requirement is dependent on information provided
by the PC role (not yet defined in
provided by the PC role (not yet defined in BC) in conjunction N/A by the PC role (not yet defined in BC) in conjunction with the TP
BC) in conjunction with the TP role.
with the TP role. Only provide feedback if necessary here. role. Only provide feedback if necessary here.
Only provide feedback if
necessary here.

NOTE: This requirement applies to


NOTE: This requirement applies to the PC role (not yet the PC role (not yet defined in BC) in NOTE: This requirement applies to the PC role (not yet defined
defined in BC) in conjunction with the TP role. Only provide conjunction with the TP role. Only N/A in BC) in conjunction with the TP role. Only provide feedback if
feedback if necessary here. provide feedback if necessary necessary here.
here.
INSTRUCTIONS FOR EXTERNAL STAKEHOLDERS

To Registered Entities – British Columbia Mandatory Reliability Standards Program,

Please review the revised NERC Glossary of Terms (November 28, 2016) as per the links provided from the BC Hydro Relia
www.bchydro.com/energy-in-bc/our_system/transmission/transmission-system/reliability.html.

Complete the 'Glossary Feedback Survey Form' (the red tab), and for each Term assessed, please complete the following

a. Insert the name and applicable functions of your registered entity at the top of the 'Glossary Feedback Survey Form' W
as indicated by the red text.

b. Stakeholder Comments (Column "H"): Please provide a high-level list of activities required by your entity to mitigate/e
based on the revised or new Term's definitions.
Please also indicate what high-level incremental activities or new activities need to be completed in order to become com

c. The Estimated Incremental Cost Associated with Revised/New Term/Definition (Columns “I” and "J"), if any assoc
- a revision to a Term/Definition compared to the BCUC adopted version; or
- the adoption of a new Term/Definition.

Please indicate which costs are one-time versus ongoing, and identify the assumptions associated with each estimate.
BC Hydro will use this information to develop recommendations to the BCUC regarding the potential impacts of each
Term on registered entities for inclusion in the Report.

d. BCUC Implementation Time (Column “K”):


Please include an assessment of the amount of time your organization would reasonably require to come into compliance
with the Glossary Term and definition once adopted by the BCUC (i.e. 6 months from adoption, immediately after adoptio
Hydro will use this information to recommend an overall implementation time for each Glossary Term and definition for inc

Regards,

Patricia Robertson
Reliability Compliance Manager
British Columbia Hydro and Power Authority
(604)-455-4233
patricia.robertson@bchydro.com

Vijay Raghunathan
Senior Reliability Compliance Specialist
British Columbia Hydro and Power Authority
(604)-516-8958
vijay.raghunathan@bchydro.com
INSTRUCTIONS FOR EXTERNAL STAKEHOLDERS

To Registered Entities – British Columbia Mandatory Reliability Standards Program,

Please review the revised NERC Glossary of Terms (November 28, 2016) as per the links provided from the BC Hydro Reliability webs
www.bchydro.com/energy-in-bc/our_system/transmission/transmission-system/reliability.html.

Complete the 'Glossary Feedback Survey Form' (the red tab), and for each Term assessed, please complete the following fields:

a. Insert the name and applicable functions of your registered entity at the top of the 'Glossary Feedback Survey Form' Worksheet
as indicated by the red text.

b. Stakeholder Comments (Column "H"): Please provide a high-level list of activities required by your entity to mitigate/eliminate im
based on the revised or new Term's definitions.
Please also indicate what high-level incremental activities or new activities need to be completed in order to become compliant.

c. The Estimated Incremental Cost Associated with Revised/New Term/Definition (Columns “I” and "J"), if any associated with:
- a revision to a Term/Definition compared to the BCUC adopted version; or
- the adoption of a new Term/Definition.

Please indicate which costs are one-time versus ongoing, and identify the assumptions associated with each estimate.
BC Hydro will use this information to develop recommendations to the BCUC regarding the potential impacts of each
Term on registered entities for inclusion in the Report.

d. BCUC Implementation Time (Column “K”):


Please include an assessment of the amount of time your organization would reasonably require to come into compliance
with the Glossary Term and definition once adopted by the BCUC (i.e. 6 months from adoption, immediately after adoption, etc.). BC
Hydro will use this information to recommend an overall implementation time for each Glossary Term and definition for inclusion in th

Regards,

Patricia Robertson
Reliability Compliance Manager
British Columbia Hydro and Power Authority
(604)-455-4233
patricia.robertson@bchydro.com

Vijay Raghunathan
Senior Reliability Compliance Specialist
British Columbia Hydro and Power Authority
(604)-516-8958
vijay.raghunathan@bchydro.com
Reliability website:

owing fields:

orm' Worksheet

gate/eliminate impacts

me compliant.

associated with:

ate.
h

pliance
doption, etc.). BC
for inclusion in the Report.
Disclaimer: This information has been prepared as input into BC Hydro's tenth assessment report on Mandatory Reliab
INSERT YOUR ENTITY NAME AND FUNCTIONAL REGISTRATIONS APPLICABLE TO YOUR ENTITY (i.e. TO, DP, GO, DP

FERC Approved New/Revised/Retired NERC Glossary of Terms from Acronym


the November 28, 2016 Glossary of Terms (If Available)

_EXAMPLE: Demand-Side Management

DSM
*Glossary term is specific to the new MOD-031-1 standard in addition to
currently adopted BAL-002-WECC-2, EOP-002-3.1, MOD-16-1.1, MOD-017-
0.1, MOD-019-0.1 MOD-020-0 and MOD-021-1 standards

BES Cyber Asset

*Glossary term is specific to the new CIP Version 6 suite of standards (CIP-
003-6, CIP-004-6, CIP-006-6, CIP-007-6, CIP-009-6, CIP-010-2, and CIP- BCA
011-2) in addition to the currently adopted CIP Version 5 suite of standards
(CIP-002-5.1, CIP-003-5, CIP-004-5.1, CIP-005-5, CIP-006-5, CIP-007-5,
CIP-008-5, CIP-009-5, CIP-010-1, and CIP-011-1).

Blackstart Resource
N/A
*Glossary term is general in nature
Bulk-Power System
N/A
*Glossary term is general in nature

Bus-tie Breaker
N/A
*Glossary term is specific to the TPL-001-4 standard.

Cascading
N/A
*Glossary term is general in nature

Consequential Load Loss


N/A
*Glossary term is specific to the TPL-001-4 standard.

Distribution Provider
DP
*Glossary term is general in nature

Element
N/A
*Glossary term is general in nature

Generator Operator
GOP
*Glossary term is general in nature
Generator Owner
GO
*Glossary term is general in nature

Geomagnetic Disturbance Vulnerability Assessment or GMD


Vulnerability Assessment
GMD
*Glossary term is specific to the new TPL-007-1 standard.

Interchange Authority
IA
*Glossary term is general in nature

Interconnected
Operations Service
N/A
*Glossary term is general in nature

Interconnection
N/A
*Glossary term is general in nature

Load-Serving Entity
LSE
*Glossary term is general in nature
Long-Term Transmission Planning Horizon
N/A
*Glossary term is specific to the TPL-001-4 standard.

Low Impact BES Cyber System Electronic Access Point


LEAP
*Glossary term is specific to the new CIP-003-6 standard

Low Impact External Routable Connectivity


LERC
*Glossary term is specific to the new CIP-003-6 standard

Non-Consequential Load Loss


N/A
*Glossary term is specific to the TPL-001-4 standard.

Planning Assessment
N/A
*Glossary term is specific to the TPL-001-4 standard.

Planning Authority
PA
*Glossary term is general in nature
Point of Receipt
POR
*Glossary term is general in nature

Protected Cyber
Assets

*Glossary term is specific to the new CIP Version 6 suite of standards (CIP-
PCA
003-6, CIP-004-6, CIP-006-6, CIP-007-6, CIP-009-6, CIP-010-2, and CIP-
011-2) in addition to the currently adopted CIP Version 5 suite of standards
(CIP-002-5.1, CIP-003-5, CIP-004-5.1, CIP-005-5, CIP-006-5, CIP-007-5,
CIP-008-5, CIP-009-5, CIP-010-1, and CIP-011-1).

Protection System Maintenance Program (PRC-005-6)


PSMP
*Glossary term is specific to the new PRC-005-6 standard.

Reactive Power
N/A
*Glossary term is general in nature

Real Power
N/A
*Glossary term is general in nature

Reliability Coordinator
RC
*Glossary term is general in nature
Reliability Standard
N/A
*Glossary term is general in nature

Reliable Operation
N/A
*Glossary term is general in nature

Removable Media
N/A
*Glossary term is specific to the new CIP-010-2 standard.

Reserve Sharing Group


N/A
*Glossary term is general in nature

Special Protection System


Resource
(Remedial Planner
Action Scheme)
RP
*Glossary term is*Glossary
specific toterm is general instandard
the PRC-010-2 nature which is held in
abeyance in B.C., and is indirectly referenced from the PRC-006-2 (also
held in abeyance in B.C.) via the term Special Protection System - SPS, as SPS
well as the currently adopted CIP-002-3/5.1, EOP-004-2, FAC-010-2.1, FAC-
011-2, IRO-005-3.1a, MOD-029-1a, MOD-030-2, NUC-001-2/3, PRC-001-
1.1, PRC-004-WECC-1, PRC-005-2(i), PRC-015-0, PRC-016-0.1, PRC-017-
0, PRC-021-1, PRC-023-1/2/3, TOP-005-2a, TPL-001-0.1, TPL-002-0b, TPL-
003-0b, TPL-004-0a
System Operating Limit
N/A
*Glossary term is general in nature

Transient Cyber Asset


N/A
*Glossary term is specific to the new CIP-010-2 standard.

Transmission Customer
N/A
*Glossary term is general in nature

Transmission Operator
TOP
*Glossary term is general in nature
Transmission Owner
TO
*Glossary term is general in nature
Transmission Planner
N/A
*Glossary term is general in nature
Transmission Service Provider
TSP
*Glossary term is general in nature
h assessment report on Mandatory Reliability Standards and is based on information available to BC Hydro as of the date sent. It
LE TO YOUR ENTITY (i.e. TO, DP, GO, DP, etc.):

FERC Approved New/Revised NERC Term Definitions against Terms and Definitions
listed in Columns "E" and "F"
(changes to definition indicated by red text; deletions are not indicated)

All activities or programs undertaken by any applicable entity to achieve a reduction in


Demand.

A Cyber Asset that if rendered unavailable, degraded, or misused would, within 15 minutes of
its required operation, misoperation, or non ‐operation, adversely impact one or more
Facilities, systems, or equipment, which, if destroyed, degraded, or otherwise rendered
unavailable when needed, would affect the reliable operation of the Bulk Electric System.
Redundancy of affected Facilities, systems, and equipment shall not be considered when
determining adverse impact. Each BES Cyber Asset is included in one or more BES Cyber
Systems.

A generating unit(s) and its associated set of equipment which has the ability to be started
without support from the System or is designed to remain energized without
connection to the remainder of the System, with the ability to energize a bus, meeting the
Transmission Operator’s restoration plan needs for Real and Reactive Power capability,
frequency and voltage control, and that has been included in the Transmission Operator’s
restoration plan.
Bulk- Power System:
(A) facilities and control systems necessary for operating an interconnected electric energy
transmission network (or any portion thereof); and
(B) electric energy from generation facilities needed to maintain transmission system
reliability.
The term does not include facilities used in the local distribution of electric energy. (Note that
the terms “Bulk-Power System” or “Bulk Power System” shall have the same
meaning.)

A circuit breaker that is positioned to connect two individual substation bus configurations.

The uncontrolled successive loss of System Elements triggered by an incident at any


location. Cascading results in widespread electric service interruption that cannot be
restrained from sequentially spreading beyond an area predetermined by studies.

All Load that is no longer served by the Transmission system as a result of Transmission
Facilities being removed from service by a Protection System operation designed to isolate
the fault.

Provides and operates the “wires” between the transmission system and the end-use
customer. For those end-use customers who are served at transmission voltages, the
Transmission Owner also serves as the Distribution Provider. Thus, the Distribution Provider
is not defined by a specific voltage, but rather as performing the distribution
function at any voltage.

Any electrical device with terminals that may be connected to other electrical devices such as
a generator, transformer, circuit breaker, bus section, or transmission line. An
Element may be comprised of one or more components.

The entity that operates generating Facility(ies) and performs the functions of supplying
energy and Interconnected Operations Services.
Entity that owns and maintains generating Facility(ies).

Documented evaluation of potential susceptibility to voltage collapse, Cascading, or localized


damage of equipment due to geomagnetic disturbances.

The responsible entity that authorizes the implementation of valid and balanced Interchange
Schedules between Balancing Authority Areas, and ensures communication of
Interchange information for reliability assessment purposes.

A service (exclusive of basic energy and Transmission Services) that is required to support
the Reliable Operation of interconnected Bulk Electric Systems.

A geographic area in which the operation of Bulk Power System components is synchronized
such that the failure of one or more of such components may adversely affect the ability of
the operators of other components within the system to maintain Reliable Operation of the
Facilities within their control. When capitalized, any one of the four
major electric system networks in North America: Eastern, Western, ERCOT and Quebec.

Secures energy and Transmission Service (and related Interconnected Operations Services)
to serve the electrical demand and energy requirements of its end-use customers.
Transmission planning period that covers years six through ten or beyond when required to
accommodate any known longer lead time projects that may take longer than ten years to
complete.

A Cyber Asset interface that controls Low Impact External Routable Connectivity. The Cyber
Asset containing the LEAP
may reside at a location external to the asset or assets containing low impact BES Cyber
Systems.
Direct user‐initiated interactive access or a direct device ‐to ‐device connection to a low impact
BES Cyber System(s) from a Cyber Asset outside the asset containing those low impact BES
Cyber System(s) via a bi‐directional routable protocol connection. Point ‐to ‐point
communications between intelligent electronic devices that use routable communication
protocols for time‐sensitive protection or control functions between Transmission station or
substation assets containing low impact BES Cyber Systems are excluded from this
definition (examples of this communication include, but are not limited to, IEC 61850 GOOSE
or vendor proprietary protocols).

Non-Interruptible Load loss that does not include: (1) Consequential Load Loss, (2) the
response of voltage sensitive Load, or (3) Load that is disconnected from the System by end-
user equipment.

Documented evaluation of future Transmission System performance and Corrective Action


Plans to remedy identified deficiencies.

The responsible entity that coordinates and integrates transmission Facilities and service
plans, resource plans, and Protection Systems.
A location that the Transmission Service Provider specifies on its transmission system where
an Interchange Transaction enters or a generator delivers its output.

One or more Cyber Assets connected using a routable protocol within or on an Electronic
Security Perimeter that is not part of the highest impact BES Cyber System within the
same Electronic Security Perimeter. The impact rating of Protected Cyber Assets is equal to
the highest rated BES Cyber System in the same ESP.

An ongoing program by which Protection System, Automatic Reclosing, and Sudden


Pressure Relaying Components are kept in working order and proper operation of
malfunctioning Components is restored. A maintenance program for a specific Component
includes one or more of the following activities:
• Verify — Determine that the Component is functioning correctly.
• Monitor — Observe the routine in‐service operation of the Component.
• Test — Apply signals to a Component to observe functional performance or output
behavior, or to diagnose problems.
• Inspect — Examine for signs of Component failure, reduced performance or degradation.
• Calibrate — Adjust the operating threshold or measurement accuracy of a measuring
element to meet the intended performance requirement.

The portion of electricity that establishes and sustains the electric and magnetic fields of
alternating-current equipment. Reactive Power must be supplied to most types
of magnetic equipment, such as motors and transformers. It also must supply the reactive
losses on transmission facilities. Reactive Power is provided by generators, synchronous
condensers, or electrostatic equipment such as capacitors and directly influences electric
system voltage. It is usually expressed in kilovars (kvar) or megavars (Mvar).

The portion of electricity that supplies energy to the Load.


The entity that is the highest level of authority who is responsible for the Reliable Operation
of the Bulk Electric System, has the Wide Area view of the Bulk Electric System, and has the
operating tools, processes and procedures, including the authority to prevent or mitigate
emergency operating situations in both next-day analysis and real-time operations. The
Reliability Coordinator has the purview that is broad enough to enable the calculation of
Interconnection Reliability Operating Limits, which may be based on the operating
parameters of transmission systems beyond any Transmission Operator’s vision.
A requirement, approved by the United States Federal Energy Regulatory Commission under
Section 215 of the Federal Power Act, or approved or recognized by an applicable
governmental authority in other jurisdictions, to provide for [Reliable Operation] of the [Bulk-
Power System]. The term includes requirements for the operation of existing [Bulk-Power
System] facilities, including cybersecurity protection, and the design of planned additions or
modifications to such facilities to the extent necessary to provide for [Reliable Operation] of
the [Bulk-Power System], but the term does not include any requirement to enlarge such
facilities or to construct new transmission capacity or generation capacity.

Operating the elements of the [Bulk-Power System] within equipment and electric system
thermal, voltage, and stability limits so that instability, uncontrolled separation,
or cascading failures of such system will not occur as a result of a sudden disturbance,
including a cybersecurity incident, or unanticipated failure of system elements.

Storage media that (i) are not Cyber Assets, (ii) are capable of transferring executable code,
(iii) can be used to store, copy, move, or access data, and (iv) are directly connected for 30
consecutive calendar days or less to a BES Cyber Asset, a network within an ESP, or a
Protected Cyber Asset. Examples include, but are not limited to, floppy disks, compact disks,
USB flash drives, external hard drives, and other flash memory cards/drives that contain
nonvolatile memory.
A group whose members consist of two or more Balancing Authorities that collectively
maintain, allocate, and supply operating reserves required for each Balancing Authority’s
use in recovering from contingencies within the group.
Scheduling energy from an Adjacent Balancing Authority to aid recovery need not constitute
reserve sharing provided the transaction is ramped in over a period the supplying
party could reasonably be expected to load generation in (e.g., ten minutes). If the
transaction is ramped in quicker (e.g., between zero and ten minutes) then, for the
The entityof
purposes that develops acontrol
disturbance long-term (generallythe
performance, oneareas
year become
and beyond) plan for
a Reserve the resource
Sharing Group.
adequacy of specific loads (customer demand and energy requirements) within
a Planning Authority area.

See “Remedial Action Scheme”


The value (such as MW, Mvar, amperes, frequency or volts) that satisfies the most limiting of
the prescribed operating criteria for a specified system configuration to ensure
operation within acceptable reliability criteria. System Operating Limits are based upon
certain operating criteria.
These include, but are not limited to:
• Facility Ratings (applicable pre- and post-Contingency Equipment Ratings or Facility
Ratings)
• transient stability ratings (applicable pre- and post-Contingency stability limits)
• voltage stability ratings (applicable pre- and post-Contingency voltage stability)
• system voltage limits (applicable pre- and post-Contingency voltage limits)

A Cyber Asset that (i) is capable of transmitting or transferring executable code, (ii) is not
included in a BES Cyber System, (iii) is not a Protected Cyber Asset (PCA), and (iv) is
directly connected (e.g., using Ethernet, serial, Universal Serial Bus, or wireless, including
near field or Bluetooth communication) for 30 consecutive calendar days or less to a BES
Cyber Asset, a network within an ESP, or a PCA. Examples include, but are not limited to,
Cyber Assets used for data transfer, vulnerability assessment, maintenance, or
troubleshooting purposes.
1. Any eligible customer (or its designated agent) that can or does execute a Transmission
Service agreement or can or does receive Transmission Service.
2. Any of the following entities: Generator Owner, Load-Serving Entity, or Purchasing-Selling
Entity.

The entity responsible for the reliability of its “local” transmission system, and that operates
or directs the operations of the transmission Facilities.

The entity that owns and maintains transmission Facilities.

The entity that develops a long-term (generally one year and beyond) plan for the reliability
(adequacy) of the interconnected bulk electric transmission systems within its
portion of the Planning Authority area.

The entity that administers the transmission tariff and provides Transmission Service to
Transmission Customers under applicable Transmission Service agreements.
ailable to BC Hydro as of the date sent. It should not be relied upon for any other purpose.

Current BCUC Adopted Terms from


December 7, 2015 Glossary of Terms

(Column "B")

Demand-Side Management

BES Cyber Asset

Blackstart Resource
Bulk-Power System

New

Cascading

New

Distribution Provider

Element

Generator Operator
Generator Owner

NEW

Interchange Authority

Interconnected Operations Service

Interconnection

Load-Serving Entity
New

NEW

NEW

New

New

Planning Authority
Point of Receipt

Protected Cyber Assets

Protection System Maintenance Program


(PRC-005-2)

Reactive Power

Real Power

Reliability Coordinator
Reliability Standard

Reliable Operation

NEW

Reserve Sharing Group

Resource Planner

Special Protection System


(Remedial Action Scheme)
System Operating Limit

NEW

Transmission Customer

Transmission Operator

Transmission Owner

Transmission Planner

Transmission Service Provider


should not be relied upon for any other purpose.

Current BCUC Adopted


Definition from December 7, 2015
Glossary of Terms

The term for all activities or programs undertaken by Load-Serving Entity or its
customers to influence the amount or timing of electricity they use.

A Cyber Asset that if rendered unavailable, degraded, or misused would, within 15


minutes of its required operation, misoperation, or non-operation, adversely impact
one or more Facilities, systems, or equipment, which, if destroyed, degraded, or
otherwise rendered unavailable when needed, would affect the reliable operation
of the Bulk Electric System. Redundancy of affected Facilities, systems, and
equipment shall not be considered when determining adverse impact.
Each BES Cyber Asset is included in one or more BES Cyber Systems. (A Cyber
Asset is not a BES Cyber Asset if, for 30 consecutive calendar days or less, it is
directly connected to a network within an ESP, a Cyber Asset within an ESP, or to a
BES Cyber Asset, and it is used for data transfer, vulnerability assessment,
maintenance, or troubleshooting purposes.)

A generating unit(s) and its associated set of equipment which has the ability to be
started without support from the System or is designed to remain energized without
connection to the remainder of the System, with the ability to energize a bus,
meeting the Transmission Operator’s restoration plan needs for real and reactive
power capability, frequency and voltage control, and that has been included in the
Transmission Operator’s restoration plan.
A) facilities and control systems necessary for operating an interconnected electric
energy transmission network (or any portion thereof); and
(B) electric energy from generation facilities needed to maintain transmission
system reliability.
The term does not include facilities used in the local distribution of electric energy.

N/A

The uncontrolled successive loss of system elements triggered by an incident at


any location. Cascading results in widespread electric service interruption that
cannot be restrained from sequentially spreading beyond an area
predetermined by studies.

N/A

Provides and operates the “wires” between the transmission system and the end-
use customer. For those end-use customers who are served at transmission
voltages, the Transmission Owner also serves as the Distribution Provider. Thus,
the Distribution Provider is not defined by a specific voltage, but rather as
performing the Distribution function at any voltage.

Any electrical device with terminals that may be connected to other electrical
devices such as a generator, transformer, circuit breaker, bus section, or
transmission line. An element may be comprised of one or more components.

The entity that operates generating unit(s) and performs the functions of supplying
energy and Interconnected Operations Services.
Entity that owns and maintains generating units.

N/A

The responsible entity that authorizes implementation of valid and balanced


Interchange Schedules between Balancing Authority Areas, and ensures
communication of Interchange information for reliability assessment
purposes.

A service (exclusive of basic energy and transmission services) that is required to


support the reliable operation of interconnected Bulk Electric Systems.

When capitalized, any one of the four major electric system networks in North
America: Eastern, Western, ERCOT and Quebec.

Secures energy and transmission service (and related Interconnected Operations


Services) to serve the electrical demand and energy requirements of its end-use
customers.
N/A

N/A

N/A

N/A

N/A

The responsible entity that coordinates and integrates transmission facility and
service plans, resource plans, and protection systems.
A location that the Transmission Service Provider specifies on its transmission
system where an Interchange Transaction enters or a Generator delivers its output.

One or more Cyber Assets connected using a routable protocol within or on an


Electronic Security Perimeter that is not part of the highest impact BES Cyber
System within the same Electronic Security Perimeter. The impact rating
of Protected Cyber Assets is equal to the highest rated BES Cyber System in the
same ESP. A Cyber Asset is not a Protected Cyber Asset if, for 30 consecutive
calendar days or less, it is connected either to a Cyber Asset within the ESP or to
the network within the ESP, and it is used for data transfer, vulnerability
assessment, maintenance, or troubleshooting purposes.

An ongoing program by which Protection System components are kept in working


order and proper operation of malfunctioning components is restored. A
maintenance program for a specific component includes one or more of the
following activities:
Verify — Determine that the component is functioning correctly.
Monitor — Observe the routine in-service operation of the component.
Test — Apply signals to a component to observe functional performance or output
behavior, or to diagnose problems.
Inspect — Examine for signs of component failure, reduced performance or
degradation.
Calibrate — Adjust the operating threshold or measurement accuracy of a
measuring element to meet the intended performance requirement.

The portion of electricity that establishes and sustains the electric and magnetic
fields of alternating-current equipment. Reactive power must be supplied to most
types of magnetic equipment, such as motors and transformers. It also must
supply the reactive losses on transmission facilities. Reactive power is provided by
generators, synchronous condensers, or electrostatic equipment such as
capacitors and directly influences electric system voltage. It is usually expressed in
kilovars (kvar) or megavars (Mvar).

The portion of electricity that supplies energy to the load.


The entity that is the highest level of authority who is responsible for the reliable
operation of the Bulk Electric System, has the Wide Area view of the Bulk Electric
System, and has the operating tools, processes and procedures, including the
authority to prevent or mitigate emergency operating situations in both next-day
analysis and real-time operations. The Reliability Coordinator has the purview that
is broad enough to enable the calculation of Interconnection Reliability Operating
Limits, which may be based on the operating parameters of transmission systems
beyond any Transmission Operator’s vision.
A requirement, approved by the United States Federal Energy Regulatory
Commission under this Section 215 of the Federal Power Act, or approved or
recognized by an applicable governmental authority in other jurisdictions, to
provide for reliable operation [Reliable Operation] of the bulk-power system [Bulk-
Power System]. The term includes requirements for the operation of existing
bulkpower system [Bulk-Power System] facilities, including cybersecurity
protection, and the design of planned additions or modifications to such facilities to
the extent necessary to provide for reliable operation [Reliable Operation] of the
bulk-power system [Bulk-Power System], but the term does not include any
requirement to enlarge such facilities or to construct new transmission capacity or
generation capacity.

Operating the elements of the bulk-power system [Bulk-Power System] within


equipment and electric system thermal, voltage, and stability limits so that
instability, uncontrolled separation, or cascading failures of such system will not
occur as a result of a sudden disturbance, including a cybersecurity incident, or
unanticipated failure of system elements.

N/A

A group whose members consist of two or more Balancing Authorities that


collectively maintain, allocate, and supply operating reserves required for each
Balancing Authority’s use in recovering from contingencies within the group.
Scheduling energy from an Adjacent Balancing Authority to aid recovery need not
constitute reserve sharing provided the transaction is ramped in over a period the
supplying party could reasonably be expected to load generation in (e.g., ten
minutes). If the transaction is ramped in quicker (e.g., between zero and ten
minutes)
The entitythen,
that for the purposes of Disturbance
(generally Control
one yearPerformance,
and beyond)the Areas
develops a long-term plan for the
become a
An automaticReserve Sharing
protection Group.
systemloads
designed to detect abnormal or predetermined
resource adequacy of specific (customer demand and energy requirements)
system
within a conditions, and takeArea.
Planning Authority corrective actions other than and/or in addition to the
isolation of faulted components to maintain system reliability. Such action may
include changes in demand, generation (MW and Mvar), or system configuration to
maintain system stability, acceptable voltage, or power flows. An SPS does not
include (a) underfrequency or undervoltage load shedding or (b) fault conditions
that must be isolated or (c) out-of-step relaying (not designed as an integral part of
an SPS). Also called Remedial Action Scheme.
The value (such as MW, MVar, Amperes, Frequency or Volts) that satisfies the
most limiting of the prescribed operating criteria for a specified system
configuration to ensure operation within acceptable reliability criteria. System
Operating Limits are based upon certain operating criteria.
These include, but are not limited to:
Facility Ratings (Applicable pre- and post-Contingency equipment or facility
ratings)
Transient Stability Ratings (Applicable pre- and post-Contingency Stability Limits)
Voltage Stability Ratings (Applicable pre- and post-Contingency Voltage Stability)
System Voltage Limits (Applicable pre- and post-Contingency Voltage Limits)

N/A

1. Any eligible customer (or its designated agent) that can or does execute a
transmission service agreement or can or does receive transmission service.
2. Any of the following responsible entities: Generator Owner, Load-Serving Entity,
or Purchasing-Selling Entity.

The entity responsible for the reliability of its “local” transmission system, and that
operates or directs the operations of the transmission facilities.

The entity that owns and maintains transmission facilities.

The entity that develops a long-term (generally one year and beyond) plan for the
reliability (adequacy) of the interconnected bulk electric transmission systems
within its portion of the Planning Authority Area.
The entity that administers the transmission tariff and provides Transmission
Service to Transmission Customers under applicable Transmission Service
agreements.
Effective Date of
FERC Approval Date of
New/Revised/Retired NERC
New/Revised/Retired NERC Term and
Term and Definition in United
Definition
States

19-Feb-15 1-Jul-16

21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16
21-Jan-16 1-Jul-16

17-Oct-13 1-Jan-15

21-Jan-16 1-Jul-16

17-Oct-13 1-Jan-15

21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16
21-Jan-16 1-Jul-16

22-Sep-16 1-Jul-17

21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16
17-Oct-13 1-Jan-15

21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16

17-Oct-13 1-Jan-15

17-Oct-13 1-Jan-15

21-Jan-16 1-Jul-16
21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16

18-Dec-15 1-Jan-16

21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16
21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16

23-Jun-16 1-Apr-17
21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16

21-Jan-16 1-Jul-16
Estimated Incremental/New Costs As
with Revised/New Glossary Term and
Stakeholder Comments if any ($)
(Press Alt-Enter to insert a carriage return in a cell)

Cost
One Time ($)

No Change 0
NOTE: This Glossary Term was included initially under Assessment Report No. 8,
however, adoption was held by the BCUC pending further reassessment per Order
R-38-15. As such, this Glossary Term is now up for reassessment. A separate TPL-
001-4 specific report will be filed per the BCUC's request. Please provide any
feedback here.

NOTE: This Glossary Term was included initially under Assessment Report No. 8,
however, adoption was held by the BCUC pending further reassessment per Order
R-38-15. As such, this Glossary Term is now up for reassessment. A separate TPL-
001-4 specific report will be filed per the BCUC's request. Please provide any
feedback here.
NOTE: This Glossary Term was included initially under Assessment Report No. 8,
however, adoption was held by the BCUC pending further reassessment per Order
R-38-15. As such, this Glossary Term is now up for reassessment. A separate TPL-
001-4 specific report will be filed per the BCUC's request. Please provide any
feedback here.

NOTE: This Glossary Term was included initially under Assessment Report No. 8,
however, adoption was held by the BCUC pending further reassessment per Order
R-38-15. As such, this Glossary Term is now up for reassessment. A separate TPL-
001-4 specific report will be filed per the BCUC's request. Please provide any
feedback here.
NOTE: This Glossary Term was included initially under Assessment Report No. 8,
however, adoption was held by the BCUC pending further reassessment per Order
R-38-15. As such, this Glossary Term is now up for reassessment. A separate TPL-
001-4 specific report will be filed per the BCUC's request. Please provide any
feedback here.
ncremental/New Costs Associated
/New Glossary Term and Definition
if any ($) BCUC Implementation Time
(Press Alt-Enter to insert a carriage return in a cell)

Cost
Ongoing ($)

Coincide with effective date of MOD-031-1


0
standard after adoption by BCUC

Você também pode gostar