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.
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
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.
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)
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.
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.
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).
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.
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.
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.
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: 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
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.
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.
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.
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.
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.
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.
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.
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
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
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.
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.
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
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.
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
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
*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
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
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.
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).
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.
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)
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.
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).
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.
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.
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).
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.
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 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.
(Column "B")
Demand-Side Management
Blackstart Resource
Bulk-Power System
New
Cascading
New
Distribution Provider
Element
Generator Operator
Generator Owner
NEW
Interchange Authority
Interconnection
Load-Serving Entity
New
NEW
NEW
New
New
Planning Authority
Point of Receipt
Reactive Power
Real Power
Reliability Coordinator
Reliability Standard
Reliable Operation
NEW
Resource Planner
NEW
Transmission Customer
Transmission Operator
Transmission Owner
Transmission Planner
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 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
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
When capitalized, any one of the four major electric system networks in North
America: Eastern, Western, ERCOT and Quebec.
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.
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).
N/A
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 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 ($)