1 / 5

Handling of Contingencies that Island Resource Nodes

This article discusses the handling of contingencies in the network operations model to eliminate inadvertent islanding. It proposes steps to eliminate non-breakered points of interconnection and ensure consistency in contingency modeling.

ariley
Download Presentation

Handling of Contingencies that Island Resource Nodes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Handling of Contingencies that Island Resource Nodes Shams Siddiqi, Ph.D. Crescent Power, Inc. (512) 619-3532 shams@crescentpower.net QMWG Meeting July 9, 2018

  2. How this Issue Arises? • Network Operations Modeling Expectations for TSPs, REs, and QSEs: "Single element contingencies will be programmatically generated and appended to each CIM model." "The typical modeling criteria for contingency definitions are straightforward; contingencies are modeled breaker-to-breaker between autotransformers, non-radial AC transmission lines, or between a generator and its high-side breaker.“ “ERCOT will submit NOMCRs and model double contingencies in NMMS after consulting with the owners of the equipment in the double contingencies.” • Thus, programmatically generated single contingencies do not include radial lines and, logically, double contingencies also do not result in islanding in the normal status of Network Operations Model • Thus, all islanding contingencies are either (1) due to non-breakered temporary POIs or (2) inadvertent due to change in network topology, i.e. transmission element outages • Solution: (1) ERCOT no longer allows non-breakered POIs and is eliminating existing such POIs and (2) Run contingency generation tool with current network model (that includes outages) and eliminate contingencies from approved Contingency List that are not in list of contingencies from this run – no radial/islanding contingency would be modeled in SCED/DAM/CRR

  3. Impact of Inadvertent Radial T-1 • Inadvertent radial T-1 with Islanding of G1 (G1’s output under this contingency is distributed to all other responsive generators on system – GDF): • Min 10*G1 + 20*G2 + 50*G3 ST: a) G1+G2+G3 = 180; b) G2+0.5*G1 <= 40 • G1=80, G2=0, G3=100, SPa=50, SPb =-80, LMP1=$40, LMP2=-$30, LMP3=$50 • If this radial T-1 ignored, then G1=120, G2=40, G3=20, LMP1=LMP3=$50, LMP2=$20 • Big negative impact on G1 due to T-1 with islanding from $6k to $3.2k in revenues • For G1 under T-1, dispatch of 80MW with LMP1=$40 seems inconsistent (since 120MW offered at $10/MWh) • If G1 consists of multiple units, this T-1 contingency is much more severe than regular G-1 contingency since G-1 contingency only takes out one unit at a time x

  4. Proposed Next Steps • Evaluate cost of running contingency generation tool with current network model (that includes outages) and eliminate contingencies from approved Contingency List that are not in list of contingencies from this run or other means of eliminating inadvertent islanding • Formalize ERCOT handling of various contingencies in CRR, DAM and RTM in a new Other Binding Documents for market transparency and so that changes can be made as needed

  5. Proposal: Eliminate Inadvertent Islanding

More Related