Meeting Summary - 04/14/2025 CMWG Meeting

Grid Monitor AI
04/14/2025

<div class="news-image-container"><img src="/storage/docs/2025/04/4-14-CMWG-Hero.png" width="819" height="614" /></div> <h3><a href="/sharing/?token=bb6666a7-70e9-45ca-bd99-81a306c31e17"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">1 - Antitrust Admonition</span></h3> <h3><span style="font-weight: 400;">2 - Agenda Review</span></h3> <h3><a href="/sharing/?token=dac8dde2-495b-4ec9-a948-490fad421b6a"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">3 - CRR LTAS Performance Update</span></h3> <p><a href="/storage/docs/2025/04/CRR-CMWG_04142025.pdf"><span style="font-weight: 400;">CRR-CMWG_04142025.pdf</span></a></p> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Samantha Findley from ERCOT CRR market operations provided an update on transaction performance.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Updates were given on LTAS transactions, solution times, and proposed changes to the CRR auction limits table.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The recently added 2027 2nd6 Seq6 auction showed 123,000 total transactions, taking 203 hours (about 8.5 days) to complete.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">This duration is significantly higher compared to the previous Seq6 auction last fall with fewer transactions but took 157 hours to complete.</span></li> </ul> <h3><a href="/sharing/?token=c89c0562-96b0-4b92-93c2-0d9139733a7f"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">4 - NPRR1261 Transaction Table Update</span></h3> <p><a href="/storage/docs/2025/04/NPRR1261%20Transaction%20Table-CMWG_04142025.pdf"><span style="font-weight: 400;">NPRR1261 Transaction Table-CMWG_04142025.pdf</span></a></p> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Proposal to reduce the total transaction limit to 315k, per-TOU limit to 110k, and per account holder limit from 2,700 to 2,500 due to long runtime of the recent auction.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">First LTAS to use the new transaction limit table will be the 2025 2nd6 Seq1 auction.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The proposed reductions are based on data gathered from monthly LTAS evaluations and are not permanent.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Root causes of long run times are being examined with the vendor, and improvements will allow for adjusted numbers.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Discussion on the independent operation of each Time of Use (TOU) and linkage only between months, not between time of uses.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Quantity of option submissions are believed to contribute to long run times.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Hardware optimizations and potential cloud solutions are being explored to address performance issues, although there are internal cybersecurity constraints.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">ERCOT is considering the removal of multi-month bidding functionality and the introduction of an option pricing report.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Changes such as linking time of uses and de-linking months were discussed but would require significant code changes.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The possibility of hardware upgrades, such as from DDR3 to DDR4 RAM, is being pursued.</span></li> </ul> <h3><a href="/sharing/?token=3f6f4af2-ac97-4330-8696-bab5181976a4"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">5 - High LMPs observed on 2/19 discussion</span></h3> <p><a href="/storage/docs/2025/04/CMWG-Feb19-Issue-04142025-V2.pdf"><span style="font-weight: 400;">CMWG-Feb19-Issue-04142025-V2.pdf</span></a></p> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Stakeholders requested further information regarding the high LMPs observed on February 19, during a winter storm.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">An electrical bus associated with the Settlement Point RHESS2_ES1 with a very large helping shift factor on multiple constraints that were violated (at max shadow price), resulted in a very high LMP of over $28,000.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The LMP calculation (System Lambda &ndash; sum(SF*Shadow Price)) was explained, past discussion has focused on system conditions and operational questions.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Freddy Garcia explained in detail the control room's conditions during the winter storm and the multiple constraints faced, including planned outages in certain areas.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Freddy mentioned that on February 19, ERCOT's operators dealt with a significant number of constraints, with many exceeding emergency ratings that required additional studies to avoid cascading failures.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Blake Holt from LCRA inquired about possible solutions to minimize LMP impacts, suggesting the need for shared constraints to prevent excessive pricing.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Multiple stakeholders discussed optimization and pricing issues, noting similar challenges faced by other ISOs and RTOs.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Freddy Garcia and others highlighted the need for improved tools and procedures to better manage constraints without overloading operators.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Some stakeholders suggested reevaluating price and shadow price caps to prevent excessive LMPs or considering additional operational tools.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">For future discussions, further analysis on theoretical pricing, constraints handling, and potential procedural updates was suggested.</span></li> </ul> <h3><a href="/sharing/?token=3335530c-bbe7-4512-9584-943cb0943685"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">6 - Day Ahead Market (DAM) PTP Activity Update</span></h3> <p><a href="/storage/docs/2025/04/CMWG-PTP-and-PTPLO-Submissions-in-DAM.pdf"><span style="font-weight: 400;">CMWG-PTP-and-PTPLO-Submissions-in-DAM.pdf</span></a></p> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">PTP and PTPLO interval records have been identified as difficult for the DAM optimization engine to solve.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">High PTP interval record volumes have increased execution time.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Past measures to optimize DAM performance include limiting PTP submissions through SCR814, process changes, and hardware updates.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Ongoing studies focus on the PTP impact on DAM performance, with a proposal for submission fees.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Performance concerns are reemerging, with late solution postings and DAM reports becoming more likely.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Current submission limits include a maximum of 10,000 PTP interval submissions per counterparty.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">There are diminishing returns on process and hardware improvements without further volume management.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">A reevaluation of the correlation between unawarded PTPs and execution time is planned.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The issue of high PTP submissions could lead to operational inefficiencies that impact gas procurement and DAM operations.</span></li> </ul> <h3><a href="/sharing/?token=db40f7dd-894a-4b41-936e-da4663d390c6"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">7 - Granular Product type for Congestion Revenue Rights Time of Use (CRRTOU)</span></h3> <p><a href="/storage/docs/2025/04/Vistra-CRR-Solar-vs-Non-solar-TOU-Proposal.pdf"><span style="font-weight: 400;">Vistra-CRR-Solar-vs-Non-solar-TOU-Proposal.pdf</span></a></p> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">ERCOT presented a study on implementing more granular CRR TOU blocks to better align with market dynamics influenced by increased renewable energy, particularly solar.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The main reasons for this proposal include adapting to market changes and reducing auction processing time and computational costs.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Proposal to split current blocks into solar and non-solar hours based on seasonality, providing a more targeted product.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Observed increased variability in solar and non-solar hours impacts generation outputs and prices, presenting challenges in hedging positions.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The introduction of a metric called the Obligation Capture Rate (OCR) to assess the congestion variability.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Encouragement for market participants to consider obligation instead of option during auctions to improve efficiency.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Discussion on the feasibility of maintaining current 5x16 blocks while introducing new granular segments.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Feedback suggests ERCOT ISO products need to reflect the newer generation profiles without hindering traditional generators.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Clarification that changing from 5x16 to two separate products would not require system changes for years not yet auctioned but would remove existing TOUs.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Exploration of seasonal variation in TOU hours to accommodate different daylight patterns without complicating the system.</span></li> </ul> <h4><strong>Questions Raised:</strong></h4> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Clarification on whether the current 5x16 would be kept or replaced.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Consideration of solar hour variability across different seasons and its impact on TOU.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Potential for keeping 5x16 blocks and adding more granular options.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Questions around the practicality of tracking variable TOU hours by season or daylight changes.</span></li> </ul> <h4><strong>Next Steps:</strong></h4> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Considering a study on different TOU hours across seasons with possible NPRR submission.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">ERCOT to evaluate impacts and run an internal IA for changes after NPRR submission to PRS.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Collaboration between ERCOT and stakeholders on NPRR development.</span></li> </ul> <h3><a href="/sharing/?token=5fad7dae-07c6-47ea-bfce-536c59f487a9"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">8 - CMWG Approval of Changes to the CRR schedule</span></h3> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Discussion on whether changes to the CRR schedule need WMS approval or if ERCOT could adjust and update with a market notice.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Consideration of whether the current process delays the schedule or if adjustment is needed.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Conversation on the stability of the CRR activity calendar and whether WMS's approval is necessary.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Clarification that updates to the calendar might still be handled through market notices.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Proposal to potentially shift to a biannual approval process extending the calendar further out to reduce administrative burden.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Consensus that the current process mostly works without issues, serving as a formality.</span></li> </ul> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Agreement that the current CRR calendar approval process is not overly complicated.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Consideration of extending the calendar approval to a biannual process for efficiency.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Recognition that current practices don't result in significant feedback or changes requiring alterations.</span></li> </ul> <h3><a href="/sharing/?token=46eef2cf-a158-459b-98ef-61f2a64054ea"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">9 - RENA Update (Questions Only)</span></h3> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">No Questions were raised.</span></li> </ul> <h3><a href="/sharing/?token=a0e824ea-8703-473b-96fc-979706890ecd"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">10 - Other Business</span></h3> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Two action items were identified: NPRR1188 and issues with large LMP from February, both to be detailed in future meetings.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Discussion on the additional time of use for CRR auction with Vistra and ERCOT to analyze further steps.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Concerns raised about the running time issues with CRR and day-ahead markets in light of anticipated grid growth and increased demand.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Responsibilities for CRR time of use and market growth issues to be led by Vistra, with ERCOT providing support.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Potential introduction of PTP fees in CRR and day-ahead markets to handle runtime and market growth challenges.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Emphasis on keeping the market updated about CRR developments and ongoing discussions on handling market growth.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Past issues with day-ahead market delays linked to PTP transactions highlighted, indicating ongoing challenges.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Commitment to transparency in considering PTP fees for CRR and day-ahead markets.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Future studies and detailed feedback on time of use to be presented by stakeholders.</span></li> </ul> <p><span style="font-weight: 400;">&nbsp;</span></p> <p><br /><br /></p>