Download:
pdf |
pdfStandard IRO-008-1 – Reliability Coordinator Operational Analyses and Real-time Assessments
A. Introduction
1.
Title:
Reliability Coordinator Operational Analyses and Real-time
Assessments
2.
Number:
3.
Purpose: To prevent instability, uncontrolled separation, or cascading outages that
adversely impact the reliability of the interconnection by ensuring that the Bulk
Electric System is assessed during the operations horizon.
4.
Applicability
IRO-008-1
4.1. Reliability Coordinator.
5.
Proposed Effective Date:
In those jurisdictions where no regulatory approval is required, the standard shall
become effective on the latter of either April 1, 2009 or the first day of the first
calendar quarter, three months after BOT adoption.
In those jurisdictions where regulatory approval is required, the standard shall become
effective on the latter of either April 1, 2009 or the first day of the first calendar
quarter, three months after applicable regulatory approval.
B. Requirements
R1.
Each Reliability Coordinator shall perform an Operational Planning Analysis to assess
whether the planned operations for the next day within its Wide Area, will exceed any
of its Interconnection Reliability Operating Limits (IROLs) during anticipated normal
and Contingency event conditions. (Violation Risk Factor: High) (Time Horizon:
Operations Planning)
R2.
Each Reliability Coordinator shall perform a Real-Time Assessment at least once every
30 minutes to determine if its Wide Area is exceeding any IROLs or is expected to
exceed any IROLs. (Violation Risk Factor: High) (Time Horizon: Real-time
Operations)
R3.
When a Reliability Coordinator determines that the results of an Operational Planning
Analysis or Real-Time Assessment indicates the need for specific operational actions
to prevent or mitigate an instance of exceeding an IROL, the Reliability Coordinator
shall share its results with those entities that are expected to take those actions.
(Violation Risk Factor: Medium) (Time Horizon: Real-time Operations or Same Day
Operations)
C. Measures
M1. The Reliability Coordinator shall have, and make available upon request, the results of
its Operational Planning Analyses.
M2. The Reliability Coordinator shall have, and make available upon request, evidence to
show it conducted a Real-Time Assessment at least once every 30 minutes. This
evidence could include, but is not limited to, dated computer log showing times the
assessment was conducted, dated checklists, or other evidence.
Page 1 of 4
Standard IRO-008-1 – Reliability Coordinator Operational Analyses and Real-time Assessments
M3. The Reliability Coordinator shall have and make available upon request, evidence to
confirm that it shared the results of its Operational Planning Analyses or Real-Time
Assessments with those entities expected to take actions based on that information.
This evidence could include, but is not limited to, dated operator logs, dated voice
recordings, dated transcripts of voice records, dated facsimiles, or other evidence.
D. Compliance
1.
Compliance Monitoring Process
1.1. Compliance Enforcement Authority
For Reliability Coordinators that work for the Regional Entity, the ERO shall
serve as the Compliance Enforcement Authority.
For Reliability Coordinators that do not work for the Regional Entity, the
Regional Entity shall serve as the Compliance Enforcement Authority.
1.2. Compliance Monitoring Period and Reset Time Frame
Not applicable.
1.3. Compliance Monitoring and Enforcement Processes
Compliance Audits
Self-Certifications
Spot Checking
Compliance Violation Investigations
Self-Reporting
Complaints
1.4. Data Retention
The Reliability Coordinator shall keep data or evidence to show compliance as
identified below unless directed by its Compliance Enforcement Authority to
retain specific evidence for a longer period of time as part of an investigation:
The Compliance Enforcement Authority shall keep the last audit records and all
requested and submitted subsequent audit records.
The Reliability Coordinator shall retain evidence for Requirement R1, Measure
M1 and Requirement R2, Measure M2 for a rolling 30 days. The Reliability
Coordinator shall keep evidence for Requirement R3, Measure M3 for a rolling
three months.
1.5. Additional Compliance Information
None.
Page 2 of 4
Standard IRO-008-1 – Reliability Coordinator Operational Analyses and Real-time Assessments
2.
Violation Severity Levels
Requirement
Lower
Moderate
High
Severe
R1
Performed an Operational
Planning Analysis that covers
all aspects of the requirement
for all except one of 30 days
Performed an Operational
Planning Analysis that
covers all aspects of the
requirement for all except
two of 30 days.
Performed an Operational
Planning Analysis that
covers all aspects of the
requirement for all except
three of 30 days.
Missed performing an
Operational Planning
Analysis that covers all
aspects of the requirement
for four or more of 30 days.
R2
For any sample 24 hour period
within the 30 day retention
period, a Real-time Assessment
was not conducted for one 30minute period. within that 24hour period (R2)
For any sample 24 hour
period within the 30 day
retention period, Real-time
Assessments were not
conducted for two 30minute periods within that
24-hour period (R2)
For any sample 24 hour
period within the 30 day
retention period, Real-time
Assessments were not
conducted for three 30minute periods within that
24-hour period (R2)
For any sample 24 hour
period within the 30 day
retention period, Real-time
Assessments were not
conducted for more than
three 30-minute periods
within that 24-hour period
(R2)
R3
N/A
N/A
N/A
The Reliability Coordinator
failed to share the results of
its analyses or assessments
with any of the entities that
were required to take action.
Page 3 of 4
Standard IRO-008-1 – Reliability Coordinator Operational Analyses and Real-time Assessments
E. Regional Variances
None
F. Associated Documents
None
Version History
Version
Date
Action
1
October 17,
2008
Adopted by NERC Board of Trustees
1
March 17,
2011
Order issued by FERC approving IRO008-1 (approval effective 5/23/11)
1
February 28,
2014
Updated VSLs and VRF’s based on
June 24, 2013 approval.
Change Tracking
Page 4 of 4
File Type | application/octet-stream |
File Title | NERC |
File Modified | 0000-00-00 |
File Created | 0000-00-00 |