NPRR #696 · Revision Request
NPRR696 Price Correction Process Following a SCED Failure
ReasonAddresses current operational issues, Market efficiencies or enhancements
Created2015-05-14
Approved2016-08-09
Sections Affected
6.36.5.9.2
Summary
The existing process for managing price corrections following a Security-Constrained Economic Dispatch (SCED) failure creates situations where pricing outcomes are uncertain and may not reflect market conditions. When ERCOT experiences a SCED failure, the last good price is used for Settlement for the period of time when SCED does not execute. Following the failure, SCED resumes execution but ERCOT continues to take the necessary manual actions specified in paragraph (3) of Section 6.5.9.2, Failure of the SCED Process. to stabilize the system. During this stabilization period, ERCOT may or may not correct prices depending on their determination of whether the prices were erroneous or not. This creates price uncertainty for Market Participants that are actively transacting in the market. In addition, the manual actions taken in paragraph (3) of Section 6.5.9.2 following the SCED failure can significantly influence the pricing outcomes and produce results which do not reflect market conditions. This Nodal Protocol Revision Request (NPRR) establishes a price correction policy which uses the last good price for Settlement until ERCOT no longer requires manual action to stabilize the system following a SCED failure. ERCOT provides notice to Market Participants of the occurrence of a SCED failure by declaring a Watch in accordance with paragraph (1) of Section 6.5.9.2. Once the system has stabilized following a SCED failure and ERCOT no longer requires manual intervention, ERCOT will cancel the Watch in accordance with paragraph (4) of Section 6.5.9.2. By correcting prices for Settlement Intervals corresponding to the active Watch period, Market Participants will have transparency to known prices which reflect the last good SCED execution.
Timeline
-
Apr 27 '15
PRSFiled by Bill Barnes on behalf of Reliant Energy Retail Services, LLC
-
May 14 '15
PRS PRS MeetingPRSDeferred/Tabled Tabled Referred → WMS“To table NPRR696 and refer the issue to WMS.” — Passed→ Language Consideration
- Jun 3 '15
- Jun 11 '15
-
Jul 8 '15
Listed without action at 9 meetings (Jul 8 '15 – Oct 15 '15)
- Nov 4 '15
-
Nov 12 '15
Listed without action at 1 meeting
- Dec 2 '15
-
Dec 10 '15
PRS PRS MeetingPRSDeferred/Tabled Tabled Referred → WMS“To continue to table NPRR696 and refer the issue to WMS.” — Passed→ Language Consideration
- Jan 6 '16
-
Jan 14 '16
Listed without action at 2 meetings (Jan 14 '16 – Feb 3 '16)
- Feb 11 '16
-
Mar 2 '16
Listed without action at 3 meetings (Mar 2 '16 – Mar 23 '16)
- Apr 6 '16
-
Apr 14 '16
Listed without action at 3 meetings (Apr 14 '16 – May 4 '16)
- May 12 '16
- Jun 8 '16
-
Jun 16 '16
PRS PRS MeetingPRSRecommended for Approval Recommended for approval Amended by the Oct 19 '15 Reliant comments“To recommend approval of NPRR696 as amended by the 10/19/15 Reliant comments.” — Passed→ Impact Analysis Consideration
-
Jun 22 '16
Listed without action at 1 meeting
-
Jul 14 '16
PRS PRS MeetingPRSRecommended for Approval Recommended for approval Forwarded → TAC“To endorse and forward to TAC the 6/16/16 PRS Report as revised by PRS and the Impact Analysis for NPRR696.” — Passed→ Revision Request Consideration
-
Jul 28 '16
TAC TAC MeetingTACRecommended for Approval Recommended for approval“To recommend approval of NPRR696 as recommended by PRS in the 7/14/16 PRS Report.” — Passed→ Revision Request Consideration
-
Aug 9 '16
BOARD Board of Directors MeetingBOARDApproved Approved“Approved NPRR696 as recommended by TAC in the 7/28/16 TAC Report.” — Passed
- Sep 19 '16