1 / 22

Constraint Competitiveness Tests, an Overview

Constraint Competitiveness Tests, an Overview. Congestion Management Working Group. Overview of the Competitiveness Constraints Test (CCT) Key Implementation Notes Data Structure for Inputs. Overview of the Competitiveness Constraints Test (CCT). Two test procedures are employed in the CCT:

Download Presentation

Constraint Competitiveness Tests, an Overview

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. Constraint Competitiveness Tests, an Overview Congestion Management Working Group

  2. Overview of the Competitiveness Constraints Test (CCT) • Key Implementation Notes • Data Structure for Inputs

  3. Overview of the Competitiveness Constraints Test (CCT) • Two test procedures are employed in the CCT: • In Test Procedure 1 the effective capacity available to resolve the constraint on both the import and export side is first determined. The available effective capacity is then used to compute the Element Competitiveness Index (ECI), an index similar to the Herfindahl-Hirschman Index (HHI) on the import and export side. • Determine effective capacity available to resolve the constraint on the import side • Determine effective capacity available to resolve the constraint on the export port side • Determine Element Competitive Index (ECI) • In Test Procedure 2, analysis is conducted to check for the existence of any pivotal player.

  4. Test 1-A Import ECI Limit E i Generation Effective load (max withdraw) Eff. Cap.> (Load +Limit) Entity a b c n . . . . .

  5. Test 1-B Export ECI Limit E i Generation Effective load Eff. Cap. > (Load -Limit) Entity a b c n . . . . . Test 2 – Pivotal Player • Remove Largest Entity • Balance System Power • If load can be served (PP does not exist)

  6. HHI: Measuring Market Concentration • Market Concentration is a function of the number of firms in a market and their respective market shares • Herfindahl-Hirschman Index ("HHI") is a widely used measure of market concentration – also used by the Dept. of Justice (DOJ) • The HHI is calculated by summing the squares of the individual market shares (in percentage) of all the participants • HHI gives proportionately greater weight to the market shares of the larger firms, in accord with their relative importance in competitive interactions • DOJ divides spectrum of market concentration as follows: • Unconcentrated (HHI below 1000) • Moderately concentrated (HHI between 1000 and 1800), and • Highly concentrated (HHI above 1800) Note: Taken from Shams Siddiqi presentation 10/16/2006

  7. HHI: Examples • Ex 1: Market consisting of 5 equally sized entities each controlling 10,000 MW • Each entity controls 20% of supply • HHI = 5 x (20)^2 = 2,000 • Ex 2: Market consisting of one 20,000 MW entity and four 7,500 MW entities • Big entity controls 40%, others 15% each • HHI = (40)^2 + 4 x (15)^2 = 2,500 • For electricity markets, some consider HHI of 2,000 as “workably competitive” Note: Taken from Shams Siddiqi presentation 10/16/2006

  8. Overview of the Competitiveness Constraints Test (CCT) Test Procedure 1, Constraint fails the competitive test if the ECI is:

  9. CCT test is to be performed • Annually • Monthly • Daily • Annual Competitiveness Test shall determine if a constraint is competitive or not for each month of the year (This information may be used to make recommendations on the status of constraints for the Annual CRR Auction as well as inputs to the Monthly CCT) • Monthly Competitiveness Test shall change the treatment of a Competitive Constraint to a non-competitive constraint for a particular month • Based on the set of the Competitive Constraints as determined in the Monthly Competitive Test, the Daily Test shall change the treatment of a Competitive Constraint to a non-competitive constraint for a particular day

  10. 6.5.7.3. (5) • The two-step SCED methodology referenced in paragraph (1) above is: • (a) The first step is to execute the SCED process to determine Reference LMPs. In this step ERCOT executes SCED using the full Network Operations Model while only observing limits of Competitive Constraints. Energy Offer Curves for all On-Line Generation Resources, whether submitted by QSEs or created by ERCOT under this section are used in the SCED to determine “Reference LMPs.” • The second step is to execute the SCED process to produce Base Points, Shadow Prices, and LMPs, subject to security constraints (including Competitive and Non-Competitive Constraints) and other Resource constraints. The second step must: • (i) Use Energy Offer Curves for all On-Line Generation Resources, whether submitted by QSEs or created by ERCOT. Each Energy Offer Curve must be capped at the greater of the Reference LMP (from Step 1) at the Resource Node or the appropriate Mitigated Offer Cap and bounded at the lesser of the Reference LMP (from Step 1) at the Resource Node or the appropriate Mitigated Offer Floor; and • (ii) Observe all Competitive and Non-Competitive Constraints.

  11. Contingency/limiting Transmission Element pairs 3.19 (1) Unless the Board approves changes, the “Competitive Constraints” are the contingency/limiting Transmission Element pairs that represent the Commercially Significant Constraints (CSCs) and Closely Related Elements (CREs), as those terms were defined in the ERCOT Protocols, immediately prior to Texas Nodal Market Implementation Date.

  12. Overview of the Competitiveness Constraints Test (CCT) 2. Constraint Competitiveness Test (CCT) TAC shall consider on an annual basis the results of the Constraint Competitiveness Tests (CCT) performed on each candidate constraint to determine if the constraint is “Competitive” or ”Non-Competitive”. For the first year of the Nodal Market, these constraints are the contingency/limiting Transmission Element pairs that represent the Commercially Significant Constraints (CSCs) and Closely Related Elements (CREs) and will be defined immediately prior to the Texas Nodal Market Implementation date. This phrase was added to CCT requirements document and approved by TPTF.

  13. If the CSCs are used as the initial constraints • ERCOT proposes that the CSC’s be disaggregated into individual line segments (constraints) for the CSC • The CSC limits will also need to be allocated to each constraint • Use contingencies out of TCM

  14. Constraints to be Tested in CCT • Protocol: each transmission constraint • Each constraint is a contingency/limiting transmission element pair • Contingency = Closely Related Element (CRE) • Limiting Transmission Element = Commercially Significant Constraint (CSC)

  15. Number of Transmission Lines: 5000 • Number of Contingencies: 2500 • Brute Force Setup • Number of transmission constraints to be tested = 5000 * (2500+1) = 12,505,000 Note: “1” represents base case • Impractical due to the large number of transmission constraints to be tested

  16. Practical Data Setup • Contingencies must be closely related to monitored element • A contingency, which is far away from a transmission line, will not cause violation on that transmission line. • Consequently, every transmission line does not have to be tested against all contingencies

  17. Example ckt 1 ckt 2 C B A F D G E

  18. CCT Constraint Data Setup To test A-B ckt 2

  19. Input Files for Annual CCT CCT001.PSE ~ CCT012.PSE (PSS/E Version 30) CCT001.CTG ~ CCT012.CTG CCT001.CNT ~ CCT012.CNT CCT001.RMP ~ CCT012.RMP  Input Files for Monthly CCT CCT001.PSE  (PSS/E Version) CCT001.CTG CCT001.CNT CCT001.RMP PSE – Planning model for monthly peak case used to auction on-peak CRRs CTG – Contingency list CNT – Constraint list RMP – Resource mapping to Decision Making Entity

  20. Format Definition of CCT00X.CTG 1. 2. 3. 4. 5. 6. 7. • 1 'SL_35_34_1 ' 1 • 'BRA' 1 0 ' ' 36 35 '1 ' 0 0 0.00 • -999 • -999 • -999 • -999 • -999 • First Line: FORMAT (I5, 1X, A32, 1X, I2) • Contingency Sequence # • Contingency Name • No Use • Second Line: FORMAT (A5,1X,I2,1X, I5,1X,A3,1X, I5,1X,I5,1X,A4,1X,I5,1X,I5,1X,F8.2) • Contingency Type: “BRA”, “GEN”, “LOA” • Contingency Operating Type: 1 = Outage • Generator or Load Bus # (PSS/E column 1 of Generator or Load Section) • Generator or Load ID (PSSE/E column 2 of Generator or Load Section) • From Bus # (Branch Only) • To Bus # (Branch Only) • Circuit ID • No use • No use • No use Third Line: FORMAT (I5) 1. End of Individual data (or separator) Fourth Line: FORMAT (I5) 1. End of Contingency section Fifth Line: FORMAT (I5) 1. End of Flow Gate section Sixth Line: FORMAT (I5) 1. End of Generic Constraint section Seventh Line: FORMAT (I5) 1. End of SPS section

  21. Format Definition of CCT00X.CNT • 0 'BASE CASE : STATION A - STATION B ' 10.0 • 1 2 1 • 0 • 18 'SL_1063_175_1 : CRLNW__PTENN__LN01 ' 1185.0 • 1072 183 • 0 • -9999 • First Line: FORMAT ( 1X, I5, 1X, A67, 1X, F7.1 ) • Contingency Sequence # in NDPXXX.CTG ( BASE CASE = 0 ) • Contingency Name (A32) and Constraint ID (A32) • Note: A67 = A32 “Contingency Name” + A3 “ : “ + A32 “Constraint ID” • Constraint Limit • Second Line: FORMAT ( 1X, I5, 1X, I5, 1X, A2 ) • From (Export) Bus # • To (Import) Bus # • Circuit ID • Third Line: FORMAT (1X, I5) • End of Individual data (or separator) • Fourth Line: FORMAT (1X, I5) • 1. End of Constraint Mapping File 1. 2. 3. 1. 2. 3. 4.

  22. Format Definition of CCT00X.RMP • 1 'N' • ‘ABC ' 0.5000 • ‘LMN ' 0.4000 • ‘XYZ ' 0.1000 • -9999 • First Line: FORMAT (1X, I5, 4X, A1) • Generator Sequence # in PSSE • Generator Type: N = Nuclear, C = Coal, L = Lignite, Other = blank • Second Line: FORMAT (7X, A32, 1X, F7.4) – repeated for each decision making entities • Entity Name • portion of the entity • Third Line: blank line • 1. End of Individual data (or separator) • Fourth Line: FORMAT (1X, I5) • 1. End of Resource Mapping File 1. 2. 2. 2. 3. 4.

More Related