NERC Petition Exhibit B (Implementations Plan) in RM15-16

Exhibit B
Implementation Plan for Proposed Reliability Standards and Definitions

Implementation Plan

Project 2014-03 Revisions to TOP/IRO Reliability Standards
Requested Approvals

•
•
•
•
•
•
•
•
•

TOP-001-3 Transmission Operations
TOP-002-4 Operations Planning
TOP-003-3 Operational Reliability Data
IRO-001-4 Reliability Coordination - Responsibilities and Authorities
IRO-002-4 Reliability Coordination — Analysis Tools
IRO-008-2 Reliability Coordinator Operational Analyses and Real-time Assessments
IRO-010-2 Reliability Coordinator Data Specification and Collection
IRO-014-3 Coordination Among Reliability Coordinators
IRO-017-1 Outage Coordination

Requested Retirements (two groups of standards)

1. Existing Approved Standards
o TOP-001-1a Reliability Responsibilities and Authorities
o TOP-002—2.1b Normal Operations Planning
o TOP-003-1 Planned Outage Coordination
o TOP-004-2 Transmission Operations
o TOP-005-2a Operational Reliability Information
o TOP-006-2 Monitoring System Conditions
o TOP-007-0 Reporting System Operating Limit (SOL) and Interconnection Reliability
Operating Limit (IROL) Violations
o TOP-008-1 Response to Transmission Limit Violations
o IRO-001-1.1 Reliability Coordination — Responsibilities and Authorities
o IRO-002-2 Reliability Coordination — Facilities
o IRO-003-2 Reliability Coordination – Wide Area View
o IRO-004-2 Reliability Coordination – Operations Planning
o IRO-005-3.1a Reliability Coordination — Current Day Operations
o IRO-008-1 Reliability Coordinator Operational Analyses and Real-time Assessments
o IRO-010-1a Reliability Coordinator Data Specification and Collection
o IRO-014-1 Coordination Among Reliability Coordinators
o IRO-015-1 Notifications and Information Exchange Between Reliability Coordinators
o IRO-016-1 Coordination of Real-time Activities Between Reliability Coordinators
o PER-001-0.2 Operating Personnel Responsibility and Authority

2. Filed with FERC but not approved – these standards were filed with FERC but never approved and
will be retired as part of this project. Upon Board approval of replacement standards, NERC will
request the Board to rescind its approval of these standards and petition FERC to withdraw its
petition for approval of these standards:
o TOP-001-2 Transmission Operations
o TOP-002-3 Operations Planning
o TOP-003-2 Operational Reliability Data
o IRO-001-3 Reliability Coordination - Responsibilities and Authorities
o IRO-002-3 Reliability Coordination — Analysis Tools
o IRO-005-4 Reliability Coordination — Current Day Operations
o IRO-014-2 Coordination Among Reliability Coordinators
o PRC-001-2 System Protection Coordination
Prerequisite Approvals 1

Definition of Operating Instruction (filed with proposed COM-002-4).
COM-001-2 – Communications (filed with proposed COM-002-4)
Revisions to Defined Terms in the NERC Glossary

The Standards Drafting Team proposes retiring the following Board-approved definitions:
Original definition – approved by the Board but never adopted by FERC; will
be withdrawn as part of this project, consistent with the approach for the
standards that were filed with FERC and not approved. Definition: A
Reliability Directive
communication initiated by a Reliability Coordinator, Transmission
Operator, or Balancing Authority where action by the recipient is necessary
to address an Emergency or Adverse Reliability Impacts.
The Standards Drafting Team proposes revising the following Board-approved definitions:
Original definition: An analysis of the expected system conditions for the
next day’s operation. (That analysis may be performed either a day ahead or
as much as 12 months ahead.) Expected system conditions include things
such as load forecast(s), generation output levels, and known system
Operational
constraints (transmission facility outages, generator outages, equipment
Planning Analysis
limitations, etc.).
Revised definition: An evaluation of projected system conditions to assess
anticipated (pre-Contingency) and potential (post-Contingency) conditions
for next-day operations. The evaluation shall reflect applicable inputs
including, but not limited to, load forecasts; generation output levels;
In the event approval of COM-001-2 and the definition of Operating Instruction do not occur prior to the approval of the standards and
definitions revised or developed in Project 2014-03, the currently enforceable standards and definitions would remain effective until those
approvals have occurred, and the new or revised standards in Project 2014-03 shall become effective concurrent with the effective date of
COM-001-2 and the definition of Operating Instruction.

1

Implementation Plan | Project 2014-03 Revisions to TOP/IRO Reliability Standards

2

Real-time
Assessment

Interchange; known Protection System and Special Protection System status
or degradation; Transmission outages; generator outages; Facility Ratings;
and identified phase angle and equipment limitations. (Operational Planning
Analysis may be provided through internal systems or through third-party
services.)
Original definition: An examination of existing and expected system
conditions, conducted by collecting and reviewing immediately available
data.
Revised definition: An evaluation of system conditions using Real-time data
to assess existing (pre-Contingency) and potential (post-Contingency)
operating conditions. The assessment shall reflect applicable inputs
including, but not limited to: load, generation output levels, known
Protection System and Special Protection System status or degradation,
Transmission outages, generator outages, Interchange, Facility Ratings, and
identified phase angle and equipment limitations. (Real-time Assessment
may be provided through internal systems or through third-party services.)

The definitions were revised in response to issues raised in NOPR paragraphs 55, 73, and 74 on analysis
and monitoring of SOLs in all time horizons, NOPR paragraph 70 (updating study results in Real-time), and
NOPR paragraph 78 (Protection System coordination). The phase angle item was added in response to
SW Outage Report recommendation 27.
Background

On April 16, 2013, NERC submitted two petitions requesting Commission approval of TOP and IRO
standards. One petition addresses three revised TOP Reliability Standards: TOP-001-2 (Transmission
Operations), TOP-002-3 (Operations Planning), TOP-003-2 (Operational Reliability Data), and one
Protection Systems (PRC) Reliability Standard, PRC-001-2 (System Protection Coordination) (collectively,
the “TOP Standards”) to replace the eight currently-effective TOP standards. The second petition
addresses four revised IRO Reliability Standards: IRO-001-3 (Responsibilities and Authorities), IRO-002-3
(Analysis Tools), IRO-005-4 (Current Day Operations), and IRO-014-2 (Coordination Among Reliability
Coordinators) (collectively, the “IRO Standards”) to replace six currently-effective IRO standards.
On November 21, 2013, the Commission issued a NOPR in response to these petitions. The NOPR
proposed to remand the proposed TOP and IRO Standards. In the NOPR, the Commission raises a
concern that NERC “has removed critical reliability aspects that are included in the currently-effective
standards without adequately addressing these aspects in the proposed standards.” For example, the
Commission cites the fact that the proposed TOP standards do not require Transmission Operators to
plan and operate within all System Operating Limits (“SOLs”), which is a requirement in the currently
effective standards.

Implementation Plan | Project 2014-03 Revisions to TOP/IRO Reliability Standards

3

On December 20, 2013, NERC filed a motion requesting that the Commission defer action on the NOPR
until January 31, 2015 to provide NERC and the industry the opportunity to thoroughly examine the
technical concerns raised in the NOPR. This deferral would provide an opportunity for the industry,
NERC, and FERC to work toward a common understanding and afford time to review the proposed TOP
and IRO standards through the NERC standards development process to address the concerns set forth in
the NOPR. That motion to defer action was granted by the Commission on January 14, 2014.
On February 12, 2014, the Standards Committee appointed a Standard Drafting Team to take on the task
of revising the aforementioned standards in response to the NOPR issues and the recommendations
made by the Independent Expert Review Panel, the IRO FYRT, and the SW Outage Report and this
implementation plan is developed from the changes made to the standards revised by that project.
General Considerations

The twelve month implementation period for all of the standards except TOP-003-3 and IRO-010-2 is
intended to allow time for entities to update processes and train operators on the revised requirements.
All of the Requirements in proposed TOP-003-3 and IRO-010-2 except TOP-003-3, Requirements R5 and
IRO-010-2, Requirement R3 become effective three months earlier, in order to provide recipients of data
requests from their Reliability Coordinators, Transmission Operators, and/or Balancing Authorities time
to respond to the request for data.
Applicable Entities

•
•
•
•
•
•
•
•
•
•

Reliability Coordinator
Balancing Authority
Transmission Owner
Transmission Operator
Distribution Provider
Generator Owner
Generator Operator
Load-Serving Entity
Planning Coordinator
Transmission Planner

Implementation Plan | Project 2014-03 Revisions to TOP/IRO Reliability Standards

4

Effective Date for Standards
1. If the Prerequisite Approvals occur on or before Approval of the standards in Project
2014-03:

•

For all standards except proposed TOP-003-3 and proposed IRO-010-2:
The 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 applicable governmental authority
or as otherwise provided for in a jurisdiction where approval by an applicable governmental
authority is required for a standard to go into effect. Where approval by an applicable
governmental authority is not required, the standard shall become effective on the first day of the
first calendar quarter that is twelve (12) months after the date the standard is adopted by the
NERC Board of Trustees or as otherwise provided for in that jurisdiction.

•

For proposed TOP-003-3:
All requirements except Requirement R5 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 by an
applicable governmental authority or as otherwise provided for in a jurisdiction where approval
by an applicable governmental authority is required for a standard to go into effect. Where
approval by an applicable governmental authority is not required, the standard shall become
effective on the first day of the first calendar quarter that is nine (9) months after the date the
standard is adopted by the NERC Board of Trustees or as otherwise provided for in that
jurisdiction.
Requirement R5 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 applicable governmental authority
or as otherwise provided for in a jurisdiction where approval by an applicable governmental
authority is required for a standard to go into effect. Where approval by an applicable
governmental authority is not required, the standard shall become effective on the first day of
the first calendar quarter that is twelve (12) months after the date the standard is adopted by the
NERC Board of Trustees or as otherwise provided for in that jurisdiction.
The reason for the difference in effective dates for proposed TOP-003-3 is to allow applicable
entities to have time to properly respond to the data specification requests.

•

For proposed IRO-010-2:
Requirement R1 and 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 by an applicable governmental
authority or as otherwise provided for in a jurisdiction where approval by an applicable
governmental authority is required for a standard to go into effect. Where approval by an
applicable governmental authority is not required, Requirements R1 and R2 shall become

Implementation Plan | Project 2014-03 Revisions to TOP/IRO Reliability Standards

5

effective on the first day of the first calendar quarter that is nine (9) months after the date the
standard is adopted by the NERC Board of Trustees or as otherwise provided for in that
jurisdiction.
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 approved by an applicable governmental authority
or as otherwise provided for in a jurisdiction where approval by an applicable governmental
authority is required for a standard to go into effect. Where approval by an applicable
governmental authority is not required, Requirement R3 shall become effective on the first day of
the first calendar quarter that is twelve (12) months after the date the standard is adopted by the
NERC Board of Trustees or as otherwise provided for in that jurisdiction.
The reason for the difference in effective dates for proposed IRO-010-2 is to allow applicable
entities to have time to properly respond to the data specification requests.
2. If the approval of the standards in Project 2014-03 occurs concurrent with or before
the Prerequisite Approvals:

•

For all standards except proposed TOP-003-3 and proposed IRO-010-2:
The standard shall become effective concurrently with COM-001-2 and the definition of
Operating Instruction.

•

For proposed TOP-003-3:
All requirements except Requirement R5 shall become effective on the first day of the first
calendar quarter that is nine (9) months after the date that the definition of Operating
Instruction is approved by an applicable governmental authority or as otherwise provided for
in a jurisdiction where approval by an applicable governmental authority is required for a
standard to go into effect. Where approval by an applicable governmental authority is not
required, the standard shall become effective on the first day of the first calendar quarter
that is nine (9) months after the date COM-001-2 is adopted by the NERC Board of Trustees or
as otherwise provided for in that jurisdiction.
Requirement R5 shall become effective on the first day of the first calendar quarter that is
twelve (12) months after the date that the definition of Operating Instruction is approved by
an applicable governmental authority or as otherwise provided for in a jurisdiction where
approval by an applicable governmental authority is required for a standard to go into effect.
Where approval by an applicable governmental authority is not required, the standard shall
become effective on the first day of the first calendar quarter that is twelve (12) months after
the date the definition of Operating Instruction is adopted by the NERC Board of Trustees or
as otherwise provided for in that jurisdiction.

Implementation Plan | Project 2014-03 Revisions to TOP/IRO Reliability Standards

6

The reason for the difference in effective dates for proposed TOP-003-3 is to allow applicable
entities to have time to properly respond to the data specification requests.
•

For proposed IRO-010-2:
Requirement R1 and R2 shall become effective on the first day of the first calendar quarter
that is nine (9) months after the date that the definition of Operating Instruction is approved
by an applicable governmental authority or as otherwise provided for in a jurisdiction where
approval by an applicable governmental authority is required for a standard to go into effect.
Where approval by an applicable governmental authority is not required, Requirements R1
and R2 shall become effective on the first day of the first calendar quarter that is nine (9)
months after the date the standard is adopted by the NERC Board of Trustees or as otherwise
provided for in that jurisdiction.
Requirement R3 shall become effective on the first day of the first calendar quarter that is
twelve (12) months after the date that the definition of Operating Instruction is approved by
an applicable governmental authority or as otherwise provided for in a jurisdiction where
approval by an applicable governmental authority is required for a standard to go into effect.
Where approval by an applicable governmental authority is not required, Requirement R3
shall become effective on the first day of the first calendar quarter that is twelve (12) months
after the date the standard is adopted by the NERC Board of Trustees or as otherwise
provided for in that jurisdiction.

•

Standards for Retirement:
Midnight of the day before the first day of the first calendar quarter that is twelve (12) months
after the date that the standards in Project 2014-03 are approved by an applicable governmental
authority or as otherwise provided for in a jurisdiction where approval by an applicable
governmental authority is required for a standard to go into effect. Where approval by an
applicable governmental authority is not required, the standards shall be retired at midnight of
the day before the first day of the first calendar quarter that is twelve (12) months after the date
the standards in Project 2014-03 are adopted by the NERC Board of Trustees or as otherwise
provided for in that jurisdiction.

•

Definition of Reliability Directive:
Midnight of the day before the first day of the first calendar quarter that is twelve (12) months
after the date that the standards in Project 2014-03 are approved by an applicable governmental
authority or as otherwise provided for in a jurisdiction where approval by an applicable
governmental authority is required for a standard to go into effect. Where approval by an
applicable governmental authority is not required, the definition shall be retired at midnight of
the day before the first day of the first calendar quarter that is twelve (12) months after the date
the standards in Project 2014-03 are adopted by the NERC Board of Trustees or as otherwise
provided for in that jurisdiction.

Implementation Plan | Project 2014-03 Revisions to TOP/IRO Reliability Standards

7

Implementation Plan for Definitions

The definitions of Operational Planning Analysis and Real-time Assessment shall become effective on the
first day of the first calendar quarter that is ten (10) months after the date that the definitions are
approved by an applicable governmental authority or as otherwise provided for in a jurisdiction where
approval by an applicable governmental authority is required for a definitions to go into effect. Where
approval by an applicable governmental authority is not required, the definitions shall become effective
on the first day of the first calendar quarter that is ten (10) months after the date the definitions are
adopted by the NERC Board of Trustees or as otherwise provided for in that jurisdiction.
The definitions are used in proposed IRO-010-2, Requirements R1 and R2 and in proposed TOP-003-3,
Requirements R1 and R3 so it is necessary that the definitions become effective concurrent with those
requirements.
The two definitions are also employed in the following proposed project standards: TOP-001-3, TOP-0024, and IRO-008-2. These definitions are not used in any other standards, either approved or in
development in any other project.

Implementation Plan | Project 2014-03 Revisions to TOP/IRO Reliability Standards

8