1 / 42

Market Trials DAM/RUC/SASM

Market Trials DAM/RUC/SASM. Weekly Update. May 28, 2010. Antitrust Admonition. ANTITRUST ADMONITION

alaqua
Download Presentation

Market Trials DAM/RUC/SASM

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. Market TrialsDAM/RUC/SASM Weekly Update May 28, 2010 http://nodal.ercot.com 1

  2. Antitrust Admonition ANTITRUST ADMONITION ERCOT strictly prohibits Market Participants and their employees who are participating in ERCOT activities from using their participation in ERCOT activities as a forum for engaging in practices or communications that violate the antitrust laws. The ERCOT Board has approved guidelines for members of ERCOT Committees, Subcommittees and Working Groups to be reviewed and followed by each Market Participant attending ERCOT meetings. If you have not received a copy of these Guidelines, copies are available at the Client Relations desk. Please remember your ongoing obligation to comply with all applicable laws, including the antitrust laws. DISCLAIMER All presentations and materials submitted by Market Participants or any other Entity to ERCOT staff for this meeting are received and posted with the acknowledgement that the information will be considered public in accordance with the ERCOT Websites Content Management Operating Procedure. http://nodal.ercot.com 2

  3. Agenda • DAM/ RUC/SASM summary • QSE Activities for Next Week • General Reminders/Updates • Environment Report • Outages • Known Issues • Question and Answers / General Discussion • Appendix ERCOT asks that Market Participants log into the WebEx session using their company name and then their name. This will allow ERCOT to take roll-call offline. http://nodal.ercot.com 3

  4. Market Trials 2010 Roadmap http://nodal.ercot.com 4

  5. HRUC Overview for May 21 HRUC overview • ERCOT ran HRUC on May 21 at 4 pm and made 38 Resource commitments. • Similar results to the DRUC for the same Operating Day that we discussed on last week’s call. • Number of issues created solution that was not operationally approved http://nodal.ercot.com 5

  6. Submission Overview for May 24 DAM submission overview • 171 QSEs participated for Op Day 5/25 • Energy Bids in the range of 21,651 to 35,841 MW per hour • Cleared 18,180 to 25,935 MW per hour • Four major Load Zone prices ranged from $18.70 to $36.27 http://nodal.ercot.com 6

  7. Submission Overview for May 24 http://nodal.ercot.com 7

  8. RUC Overview for Operating Day 5/25 RUC overview for Op Day 5/25 • DRUC published 94 Resource commitments. • HRUC published 62 Resource commitments. • Not operationally approved based on operator experience. • Results were published to exercise market and ERCOT downstream systems (as described last week) • RUC clearing engine software results were consistent with input data • Status update on these issues will be discussed later http://nodal.ercot.com 8

  9. Submission Overview for May 25 Submission overview • 202 QSEs participated for Op Day 5/26 • Energy Bids in the range of 29,550 to 51,639 MW per hour • Cleared 23,527 to 34,405 MW per hour • Four major Load Zone prices ranged from $21.72 to $42.76. http://nodal.ercot.com 9

  10. Submission Overview for May 25 http://nodal.ercot.com 10

  11. RUC Execution Overview for Operating Day 5/26 RUC execution overview: • DRUC committed 104 Resources for Operating Day May 26 • HRUC committed 39 Resources for Operating Day May 26 • Not operationally approved based on operator experience. • Results were published to exercise market and ERCOT downstream systems (as described last week) • RUC clearing engine software results were consistent with input data • Status update on these known issues will be discussed later http://nodal.ercot.com 11

  12. Submission Overview for May 26 Submission overview • 203 QSEs participated for Op Day 5/27 • Energy Bids in the range of 27,813 to 50,794 MW per hour • Cleared 21,629 - 33,738 MW per hour • Four major Load Zone prices ranged from $24.12 to $39.62. http://nodal.ercot.com 12

  13. Submission Overview for May 26 http://nodal.ercot.com 13

  14. RUC Execution Overview for Operating Day 5/27 RUC execution overview: • DRUC committed 118 Resources for Operating Day May 27 • HRUC committed 107 Resources for Operating Day May 27 • Not operationally approved based on operator experience. • Results were published to exercise market and ERCOT downstream systems (as described last week) • RUC clearing engine software results were consistent with input data • Status update on these known issues will be discussed later http://nodal.ercot.com 14

  15. Submission Overview for May 27 Submission overview • 224 QSEs participated for Op Day 5/28 • Energy Bids in the range of 23,626 to 44,912 MW per hour • Cleared 20,093 - 31,775 MW per hour • Four major Load Zone prices ranged from $18.99 to $38.89. http://nodal.ercot.com 15

  16. Submission Overview for May 27 http://nodal.ercot.com 16

  17. RUC Execution Overview for Operating Day 5/28 RUC execution overview: • DRUC committed 114 Resources for Operating Day May 28 • (HRUC running today for Operating Day May 28) • Not operationally approved based on operator experience. • Results were published to exercise market and ERCOT downstream systems (as described last week) • RUC clearing engine software results were consistent with input data • Status update on these known issues will be discussed later http://nodal.ercot.com 17

  18. RUC Execution Overview for the week RUC Summary for the week: • ERCOT issues • Known issue regarding outages that close breakers • Phase shifters are not modeled in MMS • Work around is to change transformer parameters to operations value in the database • Continuing to look at data issues with line ratings, load distribution factors, breaker statuses • COP submission issues • Configurations that were OFF but could not be started because all the startup configurations were OUT • CC configuration LSL greater than aggregated step-up transformer rating • Multiple configurations ON • JOU resource statuses are not consistent or no COP submitted for one owner (considered OUT) • Inconsistency with zonal resource plan • COPs with HSL = 0 http://nodal.ercot.com 18

  19. DAM Execution Overview for the week DAM Summary for the week: • No issues seen from removal of guardrails • DAM running time has been good • Issue found with an incorrect contingency definition (one outage element wrong) • Prices had been extreme for Pearsall settlement points (swing from big positive to big negative) – not optimal solution at these points • Starting Wednesday, began excluding this contingency from the analysis until the definition is fixed http://nodal.ercot.com 19

  20. Next Week’s Activities Next week – Op Days are 6/2-6/5 DAM executing on 6/1-6/4 (no DAM on Memorial Day holiday) • No guardrails • Bids/offers should be reasonable • COPs shold reflect zonal throughout the week. We are requesting no COP updates as a result of nodal market processes. • Operational Scenarios: • On June 1, RMR Three-Part Offers will be used in DAM • RMR QSEs are requested to have COPs in the system (offline and available) • On June 3, simulate RUC failure; issue commitment/decommitment instructions through VDI • Note that the settlement of these RUC instructions will not occur during this operational scenario. We will repeat the scenario during August to capture the settlements of RUC instructions through VDI • This is a technical test wherein each QSE will receive one electronic VDI instruction http://nodal.ercot.com 20

  21. Next Week’s Activities DRUC executing on 6/1-6/4 after DAM HRUC and SASM executing on 6/1-6/4 • HRUC and SASM • HRUC will be executed on Tuesday, Wednesday, Thursday and Friday at 3 pm (target Operating Hours will be the balance of the Op Day) • SASM will be opened if needed based on system conditions http://nodal.ercot.com 21

  22. Next Week’s Activities Next week • Reminder that we transfer zonal outages to nodal every week on Monday • This transfer represents approximately 85% of the actual zonal outages • Again, next week ERCOT may do workarounds outside the normal business process to sidestep any issues that arise. Furthermore, we may approve the results of the RUC software even if the result is operationally unreasonable. The purpose of this is to exercise settlement and billing determinants related to RUC. http://nodal.ercot.com 22

  23. General Reminders/Updates • Network Model Update • Last data load was 5/24 • An updated settlement points and MP short name list was posted for the 5/24 load at http://nodal.ercot.com/readiness/markettrials/index.html • Next scheduled load is 6/1 http://nodal.ercot.com 23

  24. General Reminders/Updates • Currently, combined cycles have been restricted in market trials with regard to DAM/RUC consideration to the number of units in the train (discussed at stakeholder forum) • This is managed through TPO submittals and COP status (putting some configurations OUT) • Starting next week, QSEs can submit for any number of the registered configurations – no restriction • If causes issues, may need to reconsider http://nodal.ercot.com 24

  25. General Reminders/Updates • WRUC scheduled to start this week. • There is a defect that causes the results to be unable to publish. • Because of this, we will not run WRUC until the week of 6/28 after the fix is delivered to the nodal production environment (targeted for 6/25). • Reminder that when we start running WRUC, QSEs will need to have their COPs in the system 7 days in advance of the Operating Day • External Interfaces Specification v1.19L was scheduled for 5/28 but was moved to 6/11 http://nodal.ercot.com 25

  26. Support Metrics http://nodal.ercot.com 26

  27. Day-to-day operations summary: Planned / Unplanned Outages Outages • Planned Outages • 05/28/2010 01:30 P.M. – 2:30 P.M. • Software patches are being deployed for the CDR (reporting) application and may result in slight interruption with report availability during the outage window. • Unplanned Outages • 05/24/2010 08:00 A.M. – ONGOING. • Performance degradation with Bidset response notifications have been noted throughout the week. Root cause has been identified to a network I/O block associated with some of the QSE notification listeners resulting in extended latency in the delivery cycles. • 05/24/2010 08:00 A.M. – 05/24/2010 03:00 P.M • Load Ratio share data was unavailable via the external web service’s market information interface. • 05/27/2010 01:00 P.M. – 05/27/2010 02:30 P.M • MIS users experienced display problems with portlet and image alignment on various pages of the MIS. http://nodal.ercot.com 27

  28. Environment Report-Known Issues Full DAM/RUC/SASM known issues list will post every Friday night at http://nodal.ercot.com/readiness/markettrials/dam/index.html New DAM/RUC/SASM known issues • Day-ahead self-commitment logic not working for combined cycles – if different CC configurations are self-committed for different hours, DAM is not properly handling the CC as self-committed. • Currently RUC is only considering start time when the Resource is initially offline based on EMS at the time of the RUC study, and not when they are initially online. ERCOT will adjust this so that RUC will not commit Resources until the startup/notification time is met. • Phase 2 validation issue: when transactions exist in the system that do not cover all 24 hours but have identical values for every hour that is part of the transaction, the system is filling in the interior hours for the whole time period and evaluating those hours in Phase 2. If there is an issue, all the hours are canceled. So far this has only affected CRR Offers but could potentially affect AS Offers, Energy Only Offers, Energy Bids, and PTP Obligation Bids. Workaround is to add/subtract .1MW from some hours so that the hours do not have identical values. http://nodal.ercot.com 28

  29. Environment Report-Known Issues Updated MIS known issues • The two reports were enabled last week but experienced posting issues. These are available currently, but only under the Reports and Extracts Index. They will be available in their portlet (Grid->Generation->Reliability Unit Commitment) in June. • NP5-751-CD, Daily RUC Committed or Decommitted Resources • NP5-752-CD, Hourly RUC Committed or Decommitted Resources http://nodal.ercot.com 29

  30. Summary of DAM/RUC/SASM market trials Past few weeks of trials for DAM/DRUC/HRUC/SASM have had the objectives of ramping-up: - Ensuring connectivity and successful communications with markets (bids/offers/awards) - Exercising the mechanics of markets based on operational and market data - Responding to market questions on clearing behavior (hundreds of emails) - Tuning of software At this point no significant core application issues have been discovered (i.e., clearing engines and optimizations) ERCOT is transitioning to focus on quality of solution. To do so…. - ERCOT is focusing on operational data (breaker status, load distribution factors, ratings, RARF data, TSP data) - Need MPs to focus on realistic Resource data (zonal resource plans = COPs) and Resource Offers (start-up costs) - ERCOT is developing tools/scripts to measure and report data quality and solution Going forward: - Focus on quality will supersede timelines (i.e., may re-run DAM/RUC late to get better solution) • In short-term need COPs to reflect actual plans (to compare with zonal) • On Friday 5/21, ERCOT ran a DRUC (outside supported days) with COPs overwritten by ERCOT staff that mirrored zonal resource plans. The software recommended 12 unique resource commitments - More communication between ERCOT and MPs to address submission/data issues - This call is transitioning from reporting results to reporting issues and resolution path http://nodal.ercot.com 30

  31. Q&A Q&A / Open Forum http://nodal.ercot.com 31

  32. Appendix Appendix • Pre- and post-DAM reports • Special Topics http://nodal.ercot.com 32

  33. Other Note: • All transactions will be supported. • Trade submission and confirmation (Energy, Capacity and AS Trades) may be exercised at this time. • DAM notifications will be active. • Phase 2 Validation process will be active and supported. • QSE transactions that do not follow the guidelines are subject to cancellation at ERCOT’s discretion. • ERCOT may run DAM on non-supported days. No QSE participation is requested, and ERCOT staff will not be available to answer questions regarding the outputs of these non-supported processes. • CRR information from the market trials auction will be integrated into the market system. CRR Offers (by NOIEs) must contain CRR IDs from this auction in order to be valid. http://nodal.ercot.com 33

  34. Supplemental Materials http://nodal.ercot.com 34 Slide 34

  35. Report Postings Posted by 6 am: • Ancillary Services (AS) Plan • Load Ratio Shares (these will be static based on Zonal production data as of October 16, 2009) * • AS Obligations * • Wind Generation Resource Power Potential (WGRPP) forecast * and Aggregated WGRPP forecast • List of all Settlement Points and the mapping to Electrical Buses • Load forecasts for ERCOT system, Weather Zones and Load Zones • Load forecast distribution factors • Distribution Loss Factors and forecasted Transmission Loss Factors • Weather assumptions * Denotes MIS Certified reports http://nodal.ercot.com 35

  36. Report Postings Posted after each DAM: • Awards (AS Offers, Energy Offers, DAM Energy-Only Offers, DAM Energy Bids, CRR Offers, and PTP Obligation Bids) * • DAM Clearing Price for Ancillary Services (MCPC) • Day-Ahead hourly Settlement Point Prices (SPPs) • Day-Ahead hourly Locational Marginal Prices (LMPs) • Shadow Prices • Quantity of AS Offers • Aggregated AS Offer Curve • Total quantity of energy (in MWh) bought and sold in DAM See DAM Handbook for a list of all DAM/RUC/SASM reports available starting in Phase 4.0 - http://nodal.ercot.com/readiness/markettrials/dam/index.html. See MIS Handbook for a comprehensive list of reports available - http://nodal.ercot.com/readiness/markettrials/mis/index.html. * Denotes MIS Certified reports http://nodal.ercot.com 36

  37. Special Topics Phase 2 Validation reports and process • Phase 2 validation re-evaluates all submitted transactions at 7 am in the day-ahead with updated information, such as AS Obligation, CRR ownership, credit limits, etc. • If there is a validation error, ERCOT will cancel the transaction • We send a notification that a Phase 2 report is available for a particular transactions type, and notification containing the cancellation for the transaction. • You can query for the Phase 2 report via web service or on the Reports page of the Market Manager in order to view the reason for the cancellation. • Correct and resubmit prior to 10 am. • Note that submissions are locked out during the Phase 2 process, which is currently taking about 15 minutes to complete. http://nodal.ercot.com 37

  38. Special Topics Day-Ahead Self Commitment DAM clearing engine treats your TPO differently if you submit Startup and Minimum Energy (SU/ME) costs as $0 vs. NULL • If you submit with SU/ME as $0, DAM engine treats this as a normal offer where the QSE is not requesting SU/ME to be covered. HSL/LSL constraints will be respected. Also, if you are selected for an online Ancillary Service, you will also be awarded at least LSL on your offer curve. • If you submit with SU/ME as NULL, DAM engine is signaled to ignore the HSL/LSL constraints for the resource. In this scenario, the offer curve submitted will start at 0 MW and go to the max MW quantity desired – again, DAM will ignore LSL/HSL constraints. If the offer curve submitted doesn’t start at 0 MW, it will be extended to 0 MW by DAM. If the resource is selected for Ancillary Services, no requirement to also award TPO at LSL (since no LSL constraint honored in this case). http://nodal.ercot.com 38

  39. Special Topics Day-Ahead Self Commitment The purpose of the NULL: It allows a QSE to use part of a Resource to serve its own load, and then offer in the rest to the DAM and enable the offer to be co-optimized with its AS Offer. Example: A Resource has 100 MW LSL and 400 MW HSL, and the QSE has already committed 300 MW of the Resource through some other mechanism. The QSE wishes to offer the remaining 100 MW, which would otherwise be ignored due to the 100 MW LSL. Then going into real-time, so QSEs will need to update their TPO to cover the full capacity of the resource, from LSL to HSL, rather than from 0 MW. To do that if the resource is awarded in the DAM, the QSE must provide a reason code, which is DSCM. This functionality came about due to TPTF subgroup on the issue. It has not yet been added to the protocols but will during our protocol traceability/cleanup effort. http://nodal.ercot.com 39

  40. Special Topics Bid/Offer efficiencies • ERCOT has identified efficiencies in Bid/Offers submission with regard to the format of submission • This applies to all transaction that use a Bid ID or an Offer ID (Energy Only Offers, Energy Only Bids, PTP Obligation Bids, and CRR Offers) • Preference is for QSEs to submit the same Bid/Offer ID for each hour in the submission, versus submitting a different Bid/Offer ID for every hour. The market system treats the submission the exact same way, regardless of which format is used • Using the preferred format will optimize DAM system performance • For xml examples detailing this issue, please view a document that will be posted along with this presentation on the calendar page at http://www.ercot.com/calendar/2010/04/20100409-MT • This was discussed at NATF 4/6, we send an email to the nodal technical contacts that we have on file for all QSEs, and we will add it to the External Interfaces Specification http://nodal.ercot.com 40

  41. Special Topics JOUs and COP consistencies • In DAM, if the different owners of the jointly-owned unit have submitted conflicting COP statuses for the current day, online statuses will overwrite offline statuses when DAM is determining the initial condition of the unit (i.e., is the unit online or offline at the start of the next operating day). • In RUC, if the different owners have conflicting COP statuses for the next operating day: • If any owner has OUT status for any hour then the unit is considered OUT. • If all owners have submitted a COP, and at least one of them has an online status in a particular hour then the resource status for the unit is online (unless any owner has OUT) http://nodal.ercot.com 41

  42. Special Topic – Jointly Owned Units JOUs are modeled as a single physical unit • DAM uses the separate logical resources when evaluating energy and ancillary services, but Network Security Monitoring (NSM), which is a sub-process of DAM, must consider the physical unit. • http://nodal.ercot.com/docs/pd/ida/wp/sgrm/IDA041_White_Paper_for_Split_Generation_Resource_Modeling_v1.doc JOUs offering into DAM • Owners offer their share into the DAM separately, but the physical unit must be committed together • All owners have to offer in the unit (energy or AS) to the DAM or else it cannot be committed to any owner (one exception for a self-commitment scenario described below). DAM must make a commitment decision about the physical unit, which it cannot do without offers from all the owners. • Self-commitment examples (assume three owners) – remember that self-committing by submitting Startup and Minimum Energy Costs as ‘NULL’ (leaving them out of the submission altogether rather than submitting zeroes) signals the DAM software that it doesn’t need to make a commitment decision and to ignore resource constraints. • If two owners self-commit (startup/minimum energy costs are NULL) and the other submits nothing, the unit can be awarded without making a commitment decision. • If one owner self-commits, another submits a TPO with startup/minimum energy costs, and the third submits nothing, the unit cannot be awarded • If one owner self-commits, and the other two submit TPOs with startup/minimum energy costs, the unit can be awarded after making a commitment decision based on the resource constraints and the submitted startup/minimum energy costs. • Note that if self-committed, do not submit an OFFNS offer. That offer negates the self-commitment and the DAM software will not consider it as a self-committed resource (since the QSE is requesting ERCOT to evaluate the unit offline) http://nodal.ercot.com 42

More Related