Federal Register, Volume 75, Number 226, November 24, 2010, Pages 71519-72652 Page: 71,620
viii, 72651, iv p. ; 28 cm.View a full description of this periodical.
Extracted Text
The following text was automatically extracted from the image on this page using optical character recognition software:
Federal Register/Vol. 75, No. 226/Wednesday, November 24, 2010/Proposed Rules
address this directive. NERC states that
this directive is being considered in
Project 2009-02-Real-time Tools and
Analysis Capabilities.
NOPR Proposal
46. Under section 215(d)(2) of the
FPA, the Commission proposes to
approve Reliability Standard IRO-002-
2. The Commission proposes to find that
the data specification requirements of
proposed Reliability Standard IRO-001-
la are more explicit than the direction
provided in Requirement R2 of IRO-
002-1. In addition, the Commission
accepts NERC's commitment to develop
a minimum set of capabilities that
should be made available to reliability
coordinators.
3. IRO-004-2
47. NERC proposes to revise IRO-
004-1 by retiring Requirements R1
through R6. To implement these
revisions, NERC requests Commission
approval of Reliability Standard IRO-
004-2. The purpose of IRO-004-2 is to
require each reliability coordinator to
conduct next-day reliability analyses for
its reliability coordinator area to ensure
the bulk electric system can be operated
reliably in anticipated normal and
contingency conditions. IRO-004-2
would apply to balancing authorities,
transmission operators, and
transmission service providers.
48. NERC states that, upon approval
of proposed IRO-008-1, Requirement
R1 of the currently-effective IRO-004-1
should be retired because the
requirement only requires a next-day
reliability analysis of its own reliability
coordinator area as opposed to its Wide-
Area, which also would include critical
flow and status information from
adjacent reliability coordinator areas to
allow the calculation of IROLs. NERC
explains that because proposed IRO-
008-1 requires the reliability
coordinator to assess a wider area than
is currently required by IRO-004-1, the
reliability coordinator is required to
continuously look beyond its own area
boundaries and assess a broader portion
of the interconnected Bulk-Power
System. NERC further states that the
purpose of conducting a day-ahead
analysis is not to "ensure" but to "assess"
the system and, thus, Requirement R1 of
currently-effective IRO-004-1 is
inaccurate.
49. NERC also seeks to retire
Requirement R2 of IRO-004-1, which
requires each reliability coordinator to
"pay particular attention to parallel
flows to ensure one reliability
coordinator area does not place anunacceptable or undue burden on an
adjacent reliability coordinator area."37
NERC states that the phrase "to pay
particular attention to" is neither clear
nor measurable. NERC asserts that the
requirements in currently-effective IRO-
014, IRO-015, and IRO-016 are aimed at
ensuring that reliability coordinators
coordinate their actions with one
another and act in the best interest of
the interconnection as a whole. In
addition, NERC explains that, under the
Functional Model, the transmission
operator is responsible for the real-time
operation of the transmission system
with the reliability coordinator
providing oversight of the transmission
operator's actions, directing additional
or alternate actions when needed. NERC
states that the requirements proposed in
the new IRO Reliability Standards focus
specifically on IROLs and are inclusive
of any reliability implications due to
parallel flows.
50. In support of retiring
Requirements R1 and R2 of IRO-004-1,
NERC posits that under the Functional
Model, the reliability coordinator is the
functional entity with primary
responsibility for IROLs and the
transmission operator is the functional
entity with primary responsibility for
SOLs. NERC states that, under certain
circumstances, the transmission
operator may request the assistance of
its reliability coordinator in developing
an SOL but the responsibility for
addressing the SOL remains with the
transmission operator.38 NERC explains
that, under the Functional Model and
Requirement R11 of Reliability Standard
TOP-002-2, the transmission operator
is responsible for conducting analyses to
identify where there may be instances of
exceeding SOLs. NERC also states that,
under TOP-008-1, the transmission
operator is responsible for taking actions
to either prevent or mitigate instances of
exceeding SOLs. NERC states that, by
contrast, it is the reliability coordinator
that is responsible for ensuring that
IROLs are developed for its reliability
coordinator area in accordance with a
methodology developed by the
reliability coordinator. Further, NERC
states that the transmission operator
must share its SOLs with its reliability
coordinator, and the reliability
coordinator must share any SOLs it
develops with its transmission operator.
NERC states that the reliability
coordinator monitors the status of some,
but not all, SOLs.
3Reliability Standard IRO-004-1, Requirement
R2.
38Se Reliability Standard TOP-008-1, requiringtransmission operators to take action to prevent or
mitigate violations of SOLs.51. NERC also contends that, upon
proposed Reliability Standard IRO-009-
1 becoming effective, Requirements R3
and R6 of currently-effective IRO-004-
0 should be retired. Under Requirement
R3 of IRO-004-0, reliability
coordinators must, in conjunction with
its transmission operators and balancing
authorities, develop action plans,
including for reducing load to return
transmission loading to within
acceptable SOLs or IROLs. NERC states
that the use of the phrase, "in
conjunction with" is not supported by
the responsibilities of the reliability
coordinator in the Functional Model
and would be inconsistent with the
requirements of proposed Reliability
Standard IRO-009-1. NERC also states
that proposed Requirement R3 of IRO-
009-1 includes language that is more
explicit than the language in
Requirement R6 of existing Reliability
Standard IRO-004-1.
52. Finally, NERC proposes to retire
Requirements R4 and R5 from IRO-004-
1. Requirement R4 requires each
transmission operator, balancing
authority, transmission owner, generator
owner, generator operator, and load-
serving entity in the reliability
coordinator area to provide information
required for system studies. NERC
proposes to retire Requirement R4
because it identifies only a fraction of
the reliability-related data needed by the
reliability coordinator. Requirement R5
requires each reliability coordinator to
share the results of its system studies
with other reliability coordinators and
transmission operators, balancing
authorities, and transmission service
providers within its reliability
coordinator area. NERC states that
proposed Reliability IRO-010-la offers
a suitable replacement for currently-
effective Requirements R4 and R5
because IRO-010-la requires reliability
coordinators to know, in advance, what
data and information it needs and what
data and information it needs to share
with other reliability entities. In
addition, requirement R3 of proposed
Reliability Standard IRO-008-1 would
require the reliability coordinator to
share the results of its analyses with
entities within its reliability coordinator
area.
NOPR Proposal
53. Under section 215(d)(2) of the
FPA, the Commission proposes to
approve Reliability Standard IRO-004-
2, as just, reasonable, not unduly
discriminatory or preferential, and in
the public interest. The Commission
recognizes NERC's efforts to more
clearly define which functional entityhas the ultimate responsibility for SOLs
71620
Upcoming Pages
Here’s what’s next.
Search Inside
This issue can be searched. Note: Results may vary based on the legibility of text within the document.
Tools / Downloads
Get a copy of this page or view the extracted text.
Citing and Sharing
Basic information for referencing this web page. We also provide extended guidance on usage rights, references, copying or embedding.
Reference the current page of this Periodical.
United States. Office of the Federal Register. Federal Register, Volume 75, Number 226, November 24, 2010, Pages 71519-72652, periodical, November 24, 2010; Washington D.C.. (https://digital.library.unt.edu/ark:/67531/metadc52807/m1/110/: accessed April 23, 2024), University of North Texas Libraries, UNT Digital Library, https://digital.library.unt.edu; crediting UNT Libraries Government Documents Department.