1 / 23

Agenda

Texas Nodal CRR Requirements Overview of Requirements for TPTF Shawna Jirasek and Beth Garza September 11, 2006. Agenda. Overview Requirements Sections General Auction Allocation Bilateral Market Data Exchange Conceptual System Design Overview. Overview.

dewey
Download Presentation

Agenda

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. Texas NodalCRR Requirements Overview of Requirements for TPTFShawna Jirasek and Beth GarzaSeptember 11, 2006 http://nodal.ercot.com 1

  2. Agenda • Overview • Requirements Sections • General • Auction • Allocation • Bilateral Market • Data Exchange • Conceptual System Design Overview http://nodal.ercot.com 2

  3. Overview • CRR Team is led by Shawna Jirasek and Beth Garza. • This presentation highlights areas of interest or contention in the CRR Requirements • The entire CRR Requirements Document is presented for approval • The September 2005 protocols used as a baseline for these protocols but changes resulting from the August 2006 approved version and the in-flight NPRRs are noted. • The CRR Conceptual System Design is provided in draft and is not yet set for approval. http://nodal.ercot.com 3

  4. General Requirements Defining CRRs http://nodal.ercot.com 4

  5. General Requirements Defining CRRs http://nodal.ercot.com 5

  6. General Requirements CRR System http://nodal.ercot.com 6

  7. General Requirements CRR System http://nodal.ercot.com 7

  8. General Requirements CRR System http://nodal.ercot.com 8

  9. General Requirements Modeling CRRs http://nodal.ercot.com 9

  10. General Requirements Additional areas of interest Timing of posting to the MIS will be as identified in the protocols and will be configurable within the CRR System. Time of use blocks will be configurable; meaning that the hours and descriptions can be adapted in the future. http://nodal.ercot.com 10

  11. Auction Requirements Bidding in the Auction http://nodal.ercot.com 11

  12. Auction Requirements Optimizing the Auction http://nodal.ercot.com 12

  13. Auction Requirements Optimizing the Auction http://nodal.ercot.com 13

  14. Auction Requirements Optimizing the Auction http://nodal.ercot.com 14

  15. Allocation Requirements Allocation Process http://nodal.ercot.com 15

  16. Allocation Requirements Allocation Process http://nodal.ercot.com 16

  17. Bilateral Market Requirements Bilateral Process http://nodal.ercot.com 17

  18. Bilateral Market Requirements Allocation Process http://nodal.ercot.com 18

  19. Bilateral Market Requirements Additional areas of interest • Bilateral Trading of not less than one-day (by time of use) granularity • If a day(s) is bilaterally traded, then the month may not be offered into subsequent monthly or annual auctions. http://nodal.ercot.com 19

  20. Supplementary Requirements • The monthly auction optimization must complete within 80 hours • The CRR System must be capable of accepting 30,000 bids per auction • The CRR System shall be available at minimum 24/7 during auction bidding/offering and optimization and 0600 to 2000 during all other business days • The CRR System will create a 23 hour day for Spring Daylight Savings Time and a 25 hour day for Fall Daylight Savings Time http://nodal.ercot.com 20

  21. Conceptual System Design Selected Nexant iHedge Solution • Web-based, integrated tool • Driven by Calculation Subsystem • Built on Database Subsystem and Data Interface Subsystem • Interacts with users through Market User Interface (MUI) and Market Operator Interface (MUI) • Interface with other systems will depend on program architecture design but the vendor will provide the CRR System ‘end points’ http://nodal.ercot.com 21

  22. Conceptual System Design http://nodal.ercot.com 22

  23. Conceptual System Design Key Assumptions • 24-hour blocks will be managed as 3 separate time of use blocks • Smallest granularity of bilateral markets will be the time of use per day • Auction-wide credit limits will be imposed • MW will be expressed in tenths (0.1 MW) • The network model used for the CRR System will be a PSS/E data base in RAWD format • Modeling activity will consider contingencies, outages, non-thermal constraints • ERCOT will use an integration layer bus wherever possible but will have point to point interfaces as a fallback • The system will be able to function with the following maximum dimensions: Buses 7,500; Branches 10,000; Contingencies 2000; Sources and Sinks 2000; PTP bids and offers 30,000; Flowgates 40 http://nodal.ercot.com 23

More Related