NPRR514, Seasonal Generation Resource Wholesale Market Subcommittee April 12, 2013 Amanda Frazier.

Slides:



Advertisements
Similar presentations
Outage Coordination Process and New Equipment 1. Introduction This presentation is intended to increase knowledge of outage coordination and NOMCR submittal.
Advertisements

February 25, 2011 Demand Side Working Group EILS Update Mark Patterson ERCOT, Manager Demand Integration.
Chad V. Seely Assistant General Counsel Tab 6.2: User Fee – Digital Certificate Fee Finance & Audit Committee Meeting ERCOT Public November 12, 2012.
PLWG Report to ROS July 9, PGRRs needing vote PGRR043 – FIS Scoping Amendment – PGRR043 moves the Subsynchronous Resonance (SSR) Study out of the.
April 15, TAC Report to the ERCOT Board April 15, 2003.
NPRRs NPRR680 Allow QSEs to Self-Arrange AS Quantities Greater Than Their AS Obligation. This Nodal Protocol Revision Request (NPRR) proposes to allow.
ERS Update for DSWG June 1, Agenda June – September 2012 Procurement XML Project Update Clearing Price discussion NPRR 451 Q & A.
April 23 rd OWG UFLS Survey & Power Factor Review.
QSE/RE Transmission Facilities Outage Coordination Workshop.
July 30, 2015 TAC Meeting Update to COPS Michelle Trenary August 12, 2015.
NPRR 365 Change in Resource Outage Approvals from 8 to 45 or 90 Days Woody Rickerson Director Grid Coordination
Large Generator Interconnection Procedures Reform Stakeholder Meeting February 19, 2009.
Public-Private Education Facilities and Infrastructure Act 2002 (PPEA) Joe Damico.
ERCOT RMR Basics Ino González Supervisor, S&B Market Analysis.
1 Project Update and Summary of Project Priority List (PPL) Activity to Date August 14, 2014.
ROS Feb 2006 The Model Curtis Crews Network Model Engineering Supervisor
SPS policy – Information Presentation Presentation to ROS June 16, 2004.
March 26, 2015 Technical Advisory Committee (TAC) Update to RMS Kathy Scott April 7, 2015 TAC Update to RMS 1.
NPRR 219 & Outage Scheduler Enhancement Workshop April 28, 2014.
Section 5.9 – added export language Each ERS Generator site must have an interconnection agreement with its TDSP prior to submitting an ERS offer and must.
NPRR425 - Creation of a WGR Group for GREDP and Base Point Deviation Evaluation and Mixing Turbine Types Within a WGR Art Deller, P.E. RARF Workshop 8/29/13.
ISO Comparison – CAISO Alex Lee (ERCOT)
Profiling Working Group 1 PWG Update Report By Ernie Podraza of Direct Energy ERCOT PWG Chair Ed Echols Of Oncor ERCOT PWG Vice Chair for COPS Meeting.
September 2012 Wholesale Market Subcommittee Report to Technical Advisory Committee.
December 18, 2014 Technical Advisory Committee (TAC) Update to RMS Kathy Scott January 6, 2015 TAC Update to RMS 1.
MIG TF Voting Items Market Participant Notification Period (Transmission outage) – =1 Year Interconnection Date for Protocol Considerations – First Interconnection.
Transmission Outage Process April Purpose In compliance with the Protocols and the Electric Reliability Council of Texas (ERCOT) Operating Guides,
April 2, 2008 CRR Team Update PCRRs CRR Team UpdateApril 2, 2008 Table of contents 1.What is a PCRR? 2.Which NOIEs are eligible for PCRRs? 3.What.
RMR Task Force Decision Points for ERCOT Technical Advisory Committee April 3, 2003.
Transmission Customer Forum Operating Agreement Update Cheryl Johnson 9/21/06.
May 11, 2012 RPG meeting YTP Scope and Process – RPG Comments.
Outage Planning Subcommittee Mark Wilson. Outage Planning Subcommittee Created to address Market Participant concerns with existing rules and procedures.
ERS Update – DSWG Presentation September 21, 2012.
Outage Scheduler Transition Plan Kenneth Ragsdale NATF.
1 TAC Report to the ERCOT Board February 16, 2005.
Distributed Renewable Generation Profile Implementation Plan.
September 25 and October 23, 2014 Technical Advisory Committee (TAC) Update to RMS Kathy Scott October 28, 2014 TAC Update to RMS 1.
Distributed Generation Registration June 30, 2008.
Harika Basaran 11/05/2014 TAC October 23, 2014 Meeting Update to Commercial Operations Subcommittee.
Scheduling and Operating Transmission Devices in the Nodal Environment.
ERS Overview of Upcoming Changes.  Procedure Changes – ERS Generator Resources  Reporting Requirements – ERS Load Resources with Back-Up Generators.
Resource Registration Update Dana Showalter Patrick Coon May 5, 2008.
Texas Nodal 1 Nodal Operations Model Posting NATF Sep 29, 2009 Matt Mereness, ERCOT.
Lead from the front Texas Nodal 1 High-Level Overview of draft NPRR implementing PUCT Rule Posting Requirements January 8,
1/07/2014 QMWG – RUC and AS update QMWG – ERCOT Update ERCOT Market Analysis.
1 TAC Report to the ERCOT Board November 14, 2006.
Protocol Revision Subcommittee Tom Burke April 5, 2012.
Capacity, Demand and Reserves Report Bill Bojorquez Board of Directors Meeting May 16, 2007.
ERCOT Transmission Planning Process Overview and Recommendations November 6, 2002.
Demand Side Working Group March 5, 2010 Mary Anne Brelinsky EDF Trading North America.
Current Stakeholder Timelines for Emergency Issues May 6, 2008 TPTF.
1 Project Prioritization Review May 14, Approved Revision Requests “Not Started” – Planned to Start in Future Months Revision Request Target Start.
Transition Plan Network Operations Model Change Requests 5/26/2010.
Current Nodal OS Design 1.The NMMS database will have an OWNER and an OPERATOR designation for each piece of equipment in the model. The OWNER and OPERATOR.
1 Summary of TAC Procedures for COPS & PRS May 17, 2005.
Network Operations Model Go-Live Decision Kenneth Ragsdale TAC July 1, 2010.
1 Summary of TAC Procedures May 5, Revision of TAC Procedures Project began in October 2004 to incorporate the Commercial Operations Subcommittee.
Generation Adequacy Task Force Meeting April 10, 2014.
NPRRs 705NPRR Provides Consistency for References to the End Date of the Generation Interconnection Process. In the Resource Interconnection Handbook,
Impact of not including proposed generators lacking RARF data in the planning models Planning Guide Section 6.9 Issues February 17, 2016.
MISUG Meeting Materials ERCOT 7/26/ MISUG Agenda 1.Antitrust AdmonitionJ. Lavas9:30 a.m. 2.IntroductionsJ. Lavas9:30 a.m. 3.Market Data Transparency.
February 26, 2015 Technical Advisory Committee (TAC) Update to RMS Kathy Scott March 3, 2015 TAC Update to RMS 1.
Current Nodal OS Design 1.The NMMS database will have an OWNER and an OPERATOR designation for each piece of equipment in the model. The OWNER and OPERATOR.
Reliability Must Run Workshop RMR Study Process May 24, 2016.
PLWG Review 6.9 and the Interconnection process
Resource Cost Working Group
ERCOT CRR Update to CMWG
NPRR 816 / Vendor Index Definitions
NPRRs NPRR654 Discontinue Ancillary Service Requirement Methodology Assessment Report. This Nodal Protocol Revision Request (NPRR) proposes the discontinuation.
Transmission Outage Coordination
Presentation transcript:

NPRR514, Seasonal Generation Resource Wholesale Market Subcommittee April 12, 2013 Amanda Frazier

Existing Process for Suspension of Operation  Resource Entity must notify ERCOT in writing no less than 90 days prior to suspending operation for a period of greater than 180 days [ ]  Mothballed Generation Resource is removed from the ERCOT model [ (2)]  ERCOT shall make an initial determination within 24 days of whether the Resource is required to support ERCOT transmission system reliability [ (3)]  Within 60 days after receiving the Part 1 Notification, ERCOT shall make a final assessment of whether the Generation Resource is required to support ERCOT system reliability [ (5)]  ERCOT to issue Market Notices related to notifications, initial and final determinations [ (1), (3)(d) and (5)] 1

Existing Process for Return to Service  Resource Entity must notify ERCOT by April 1 and October 1 every year the estimated lead time required for each Mothballed Resource to be returned to service and probability of return to service for the next ten years [ (1)]  For modeling purposes, ERCOT and TSPs shall rely on most recent submittal of Section 22, Attachment E and Section 22, Attachment H [ ]  A Resource Entity with a Mothballed Generation Resource that has been in mothballed status for 90 days or more shall notify ERCOT in writing no less than 30 days prior to the date on which the Resource Entity intends to return a Mothballed Generation Resource to service by completing a Notification of Change of Resource Designation, Section 22, Attachment H [ (3)] 2

Existing Process for Planned Outage  Resource Entity provides ERCOT a Planned Outage Schedule, and for resources other than reliability Resources, ERCOT must accept requests submitted to ERCOT more than 45 days before the proposed start date of the outage [3.1.6(1)]  Resource may return from outage at any time, with as little as 2 hours notice to ERCOT [ ]  No market notice of Resource’s start of or return from Planned Outage status 3

NPRR514 Process for Seasonal Generation Operation  Resource Entity notifies ERCOT 90 days prior to initial change to Seasonal Operation status [ (1)] through completion of a Notification of Suspension of Operations, Parts I and II with a new designation available in Part II, suspend operation on a year-round basis and begin operation on a seasonal basis with a starting date and ending date specified (same as current process for Notification of Suspension of Operations).  A Generation Resource requesting seasonal operation must be available June 1 through September 30.  New Section , ERCOT Evaluation of Seasonal Mothball Status says: –Within 30 days after receiving the Notification of Suspension of Operations ERCOT shall make an assessment of whether the Resource is required to support ERCOT system reliability during the portion of the year the Resource would be unavailable. –Within 60 days after receiving the Notification of Suspension of Operations ERCOT shall make a final assessment of whether the Resource is required to support ERCOT system reliability during the portion of the year the Resource would be unavailable. 4

NPRR514 Process for Seasonal Generation Operation (cont.)  A Mothballed Generation Resource operating under a Seasonal Operation Period shall: –Remain modeled in ERCOT systems at all times and when it is not available shall be shown on outage in the Outage Scheduler –Not need to annually notify ERCOT of such status –Notify ERCOT in writing at least 15 days prior if the date of initial annual operation is prior to June 1 –Notify ERCOT in writing at least 15 days prior if the date it intends to suspend operation is later than September 30 –Notify ERCOT in writing at least 15 days prior to the date it intends to return the Generation Resource to year-round operation –Notify ERCOT in writing at least 90 days prior to the date it intends to be suspended indefinitely  ERCOT may request a Generation Resource operating under a Seasonal Operation Period be available earlier than June 1 or later than September 30 and must issue a Notice as soon as practicable. 5

NPRR514 Process for Seasonal Generation Operation (cont.)  ERCOT may evaluate, on an annual basis, Generation Resources operating under a Seasonal Operation Period for RMR Service during the portion of the year that the Resource is unavailable.  The existing requirement for ERCOT to issue a Market Notice prior to entering RMR Agreement negotiations with the Generation Resource will continue to apply [ (5)].  ERCOT retains its authority to “prevent an anticipated Emergency Condition relating to serving Load in the current or next Season by procuring existing capacity that may be used to maintain ERCOT System reliability in a manner not otherwise delineated in these Protocols and the Operating Guides,” [ (2)], and must follow the process outlined. 6

Benefits of NPRR514  Eliminates the necessity of using the existing cumbersome process of “mothballing” and “un-mothballing” Generation Resources that want to operate on a seasonal basis.  Provides greater transparency of a Generation Resource’s operational plans to the whole market.  Reduces time and resources necessary for both ERCOT and the Generation Resource owner to allow seasonal operation.  Provides ERCOT with additional flexibility to bring a Generation Resource back prior to June 1 or keep it available past September 30 if needed to provide adequate system reliability. 7

Resource decides to operate seasonally and submits a Notification of Suspension of Operations form to ERCOT 90 days notice to ERCOT Oct. 1 On Jan. 1, Resource is unavailable to market Jan. 1 Seasonal Operation Timeline (Example) 8 Resource unavailable to Market Within 30 days, ERCOT makes its initial determination Within 60 days, ERCOT makes its final determination If ERCOT approves seasonal operation, the unit is NOT removed from the ERCOT models during the mothballed period. ERCOT may ask the Resource at anytime during the seasonal operation period to stay in the market after Sept. 30 for reliability purposes, Market Notice of ERCOT request ERCOT may ask the Resource at anytime during the mothballed period to come back earlier than June 1 for reliability purposes, Market Notice of negotiations Sept. 30 Resource exits the market With 15 day notice, Resource may return to the market earlier than June 1, notice posted on MIS Resource available to the market June 1 Resource returns to the market With 15 day notice, Resource may return to the market later than September 30 or have the Resource return to the market year round, notice posted on MIS ERCOT may evaluate, on an annual basis, Generation Resources operating under a Seasonal Operation Period for RMR Service during the portion of the year that the Resource is unavailable. Regular RMR notification requirements apply Resource available to the market Resource unavailable Resource unavailable to Market Sept. 30June 1 Year 0Year 1Year 2 ONDJFMAMJJASONDJFMAMJJASOND OperationalMothballSeasonalMothballSeasonalMothball

9 Seasonal Operation Timeline Resource Entity and Market Notifications 90 days notice to ERCOT Resource unavailable to Market Resource available to the market Resource unavailable to Market Resource available to the market Resource unavailable If a Resource intends to return to service later than September 30, the Resource shall notify ERCOT in writing by September 15. ERCOT posts notification on MIS Secure site as soon as practicable. Resource not required to notify ERCOT annually of seasonal Operation. Resource must notify ERCOT at least 15 days prior to the date it intends to return to year-round operation. ERCOT posts notification on the MIS Secure site as soon as practicable. Resource must notify ERCOT at least 90 days prior to the date on which it intends to suspend operation indefinitely. ERCOT to post on MIS Secure Site. Section applies. ERCOT may request a Resource operating under Seasonal Operation to be available earlier than June 1 or later than September 30. Market Notice of any negotiation and ERCOT shall post notification on the MIS Secure site if Resource is returning. Upon receipt of Notification of Suspension of Operations indicating Seasonal Operation, ERCOT shall Post notification on MIS Secure site. Section applies.