MIS LOG IN

NPRR607

Summary

Title: Short-Term System Adequacy Report Posting Modification
Next Group:
Next Step:
Status: Approved on 06/10/2014
Effective Dates:
07/01/2014

Action

Date Gov Body Action Taken Next Steps
06/10/2014 BOARD Approved
05/29/2014 TAC Recommended for Approval ERCOT Board for consideration
05/15/2014 PRS Recommended for Approval TAC for consideration
04/10/2014 PRS Recommended for Approval PRS for Impact Analysis review

Voting Record

Date Gov Body Motion Result
06/10/2014 BOARD To approve as recommended in the 5/29/14 TAC Report Passed
05/29/2014 TAC To recommend approval as recommended by PRS in the 5/15/14 PRS Report. Passed
05/15/2014 PRS To endorse and forward the 4/10/14 PRS Report and Impact Analysis to TAC Passed
04/10/2014 PRS To recommend approval as submitted Passed

Vote tallies here reflect individual votes, not the weight of the votes by market segment. Affirmative votes are not recorded in these vote tallies. For additional details on the voting record, please consult the Recommendation or Action Report, or the official vote tally if available, as posted in the key documents.

Background

Status: Approved
Date Posted: Mar 24, 2014
Sponsor: ERCOT
Urgent: No
Sections: 3.2.3
Description: Following system implementation of NPRR479, Hourly Reporting of Resource Outaged Capacity, ERCOT Staff observed that Short-Term Adequacy Reports related to aggregate Resource Outage levels were posted hourly but without the capability to post intra-hour reports based on "detection of a change in status" as required by Section 3.2.3. The current hourly implementation exceeds the parameters of subsection (d)(2) of P.U.C Subst. R. 25.505, Resource Adequacy in the Electric Reliability Council of Texas Power Region, which requires daily postings. This NPRR aligns the Protocols with current ERCOT business practice for posting the Short-Term System Adequacy Report by removing language requiring ERCOT to post the report upon detection of a change to Resource Status that changes the availability of a Resource.
Reason: Aligns Protocols with current business practice

Key Documents

Related Content