MIS LOG IN

NPRR824

Summary

Title Alignment of EEA Level 3 with NERC Reliability Standards EOP-011-1 and BAL-001-2
Next Group
Next Step
Status Approved on 06/13/2017
Effective Dates
07/01/2017

Action

Date Gov Body Action Taken Next steps
06/13/2017 BOARD Approved
05/25/2017 TAC Recommended for Approval Board for consideration
05/11/2017 PRS Recommended for Approval TAC for consideration
04/13/2017 PRS Recommended for Approval PRS for Impact Analysis review

Voting Record

Date Gov Body Motion Result
06/13/2017 BOARD To approve NPRR824 as recommended by TAC in the 5/25/17 TAC Report Passed
05/25/2017 TAC To recommend approval of NPRR824 as recommended by PRS in the 5/11/17 PRS Report Passed
05/11/2017 PRS To endorse and forward to TAC the 4/13/17 PRS Report, as revised by PRS, and the Impact Analysis for NPRR824 Passed
04/13/2017 PRS To recommend approval of NPRR824 as submitted Passed

Background

Status: Approved
Date Posted: Mar 29, 2017
Sponsor: ERCOT
Urgent: No
Sections: 6.5.9.4, 6.5.9.4.1, and 6.5.9.4.2
Description: This Nodal Protocol Revision Request (NPRR) aligns Protocol language with the following North American Electric Reliability Corporation (NERC) Reliability Standards: 1) Attachment 1, Energy Emergency Alerts, of EOP-011-1, Emergency Operations, requires ERCOT, as the Reliability Coordinator, to declare an Energy Emergency Alert (EEA) Level 3 if ERCOT is unable to maintain its Physical Responsive Capability (PRC) above a minimum Contingency Reserve requirement of 1,375 MW. This NPRR adds language to address this standard; and 2) BAL-001-2, Real Power Balancing Control Performance, requires clock-minute average system frequency to not stay below 59.91 Hz for greater than 30 consecutive minutes. This NPRR increases the current EEA Level 3 frequency threshold from 59.80 Hz to 59.91 Hz and modifies EEA Level 2 language to include a timing component of being below 59.91 Hz for 15 consecutive minutes or more. These tiered timing milestones will align progressively more aggressive actions as the 30 consecutive minute requirement is approached to address this standard.
Reason: Regulatory requirements

Key Documents

Related Content