Frame

Meeting Summary - 12/06/24 CMWG Meeting

Grid Monitor AI
12/06/2024

<h2><img src="/storage/docs/2024/12/20241206%20WMWGHero.png" width="865" height="644" /></h2> <h2><a href="/sharing/?token=94c9c6f8-ed1d-4dd9-985a-b36747590272">▶️</a>1 - Antitrust Admonition - Alex Miller</h2> <h2><a href="/sharing/?token=1b0bf8e6-d7a6-479a-9df5-8c8231306d50">▶️</a>2 - Agenda Review - Alex Miller</h2> <h2><a href="https://dash3.gridmonitor.com/sharing/?token=cfc01bf8-fb3f-4312-bcb5-ff4de19b9d89">▶️</a>3 - CRR Technology Update - Sreenivas Badri</h2> <a href="/storage/docs/2024/12/ercot-cmwg-2024-12-06-crr-technology-update.pdf">ercot-cmwg-2024-12-06-crr-technology-update.pdf</a> <ul> <li style="font-weight: 400;" aria-level="1">Sreenivas Badri presented on the CRR technology roadmap and IT updates, focusing on hardware changes.</li> <li style="font-weight: 400;" aria-level="1">He discussed the high-level CRR application architecture, performance issues, and the enhancements made to address those issues, like increasing the number of CPUs from 16 to 28.</li> <li style="font-weight: 400;" aria-level="1">Based on testing, 28 CPUs were found to provide optimal performance due to limitations with DDR4 memory configuration; adding more CPUs didn't yield performance gains.</li> <li style="font-weight: 400;" aria-level="1">Future plans include a POC with DDR5 memory configuration, which is expected to improve performance by 30% and could allow for more CPUs.</li> <li style="font-weight: 400;" aria-level="1">ERCOT is exploring cloud-based solutions for potentially better hardware configurations to enhance CRR auction performance.</li> <li style="font-weight: 400;" aria-level="1">The ERCOT cloud foundation project is in progress and is expected to be completed by late Q2 next year, paving the way for cloud migrations.</li> <li style="font-weight: 400;" aria-level="1">The CRR system's key drivers for updates include upgrading the Oracle database and containerization of CRR applications.</li> <li style="font-weight: 400;" aria-level="1">A tentative CRR tech refresh is scheduled for Q1 2026, with the possibility of leveraging cloud technologies.</li> <li style="font-weight: 400;" aria-level="1">Stakeholders raised questions about the complexity of the CRR optimization problem and possible alternatives to current constraints, including multimonth constraints that add to the complexity.</li> <li style="font-weight: 400;" aria-level="1">Additional inquiries about containerization, CRR array sizes, and vendor alternatives were raised and addressed.</li> <li style="font-weight: 400;" aria-level="1">There was significant interest in periodic updates on the technology roadmap and its impact on CRR auction performance.</li> </ul> <h2><a href="/sharing/?token=edda5715-4918-4ea9-aab8-8c5d91193887">▶️</a>4 - CRR LTAS Update/Transaction Limits - Samantha Findley</h2> <a href="/storage/docs/2024/12/crr-cmwg_12062024.pdf">crr-cmwg_12062024.pdf</a> <ul> <li style="font-weight: 400;" aria-level="1">Historical solution times and transactions were discussed to provide insight into current performances and past performances.</li> <li style="font-weight: 400;" aria-level="1">Transaction Adjustment Periods affected auction capacities due to lower transaction quantities.</li> <li style="font-weight: 400;" aria-level="1">A test was conducted to evaluate the optimization of a large number of transactions; it completed within the target timeframe.</li> <li style="font-weight: 400;" aria-level="1">Future tests are planned to ensure the posting and delivery from CRR application to downstream systems are effective for large transaction volumes.</li> <li style="font-weight: 400;" aria-level="1">Two proposed NPRRs were introduced: removing multi-month bidding functionality and an option pricing report.</li> <li style="font-weight: 400;" aria-level="1">Studies showed removing multi-month bid functionality could improve optimization efficiency and time savings.</li> <li style="font-weight: 400;" aria-level="1">Currently, market participants submit credit for each TOU, with credit constraints spanning across all TOUs.</li> <li style="font-weight: 400;" aria-level="1">Discussion on removing multi-month functionality noted changes in participant behavior and transaction handling.</li> <li style="font-weight: 400;" aria-level="1">A minimum bid quantity of 1 MW was proposed to align CRR with the day-ahead market and improve process efficiencies.</li> <li style="font-weight: 400;" aria-level="1">Concerns were raised about potential limitations, participant adjustments, and the long-term auction sequence bid limits.</li> <li style="font-weight: 400;" aria-level="1">Discussion on the potential impact on auction outcomes and the necessity of future studies to quantify these impacts.</li> <li style="font-weight: 400;" aria-level="1">Details of the draft NPRR language changes were shared, with emphasis on improving CRR auction performance.</li> <li style="font-weight: 400;" aria-level="1">Noted the importance of understanding limitations and future testing to ensure all systems can handle higher transaction volumes.</li> </ul> <h2><a href="/sharing/?token=e2775904-3fdd-46bd-91d5-3029686833b7">▶️</a>5 - NTE Update–ERCOT Operational Concerns Related to IRR Telemetry and Curtailment Logic - Freddie Garcia</h2> <ul> <li style="font-weight: 400;" aria-level="1">Freddie Garcia introduces Luis Hinojosa to discuss concerns related to NTE (Not to Exceed) introduction affecting frequency control due to poor IRR telemetry.</li> <li style="font-weight: 400;" aria-level="1">SCR819 introduced NTE logic to improve GTC management. However, it highlighted issues with IRR telemetry and curtailment causing control problems.</li> <li style="font-weight: 400;" aria-level="1">Resources are providing inaccurate telemetry due to poor RTPP (Real-Time Power Potential) calculations causing frequency drags, regulation exhaustion, and manual operator actions.</li> <li style="font-weight: 400;" aria-level="1">Examples were shared illustrating problems such as unrealistic HSL (High Sustained Limit) changes and poor curtailment logic among resources.</li> <li style="font-weight: 400;" aria-level="1">Issues are not isolated to specific regions or GTCs, affecting grid control broadly.</li> <li style="font-weight: 400;" aria-level="1">ERCOT started sending RFIs to address these issues. Of 61 resources addressed, only 17 have implemented corrective actions.</li> <li style="font-weight: 400;" aria-level="1">Sources of concern include delayed responses with some fixes projected as far out as 2025. Immediate action is needed.</li> <li style="font-weight: 400;" aria-level="1">Efforts to address this include RFIs to more resources, with requests for accurate RTPP calculations across fleets.</li> <li style="font-weight: 400;" aria-level="1">Ongoing control challenges include time error issues not seen since 2016 and increased operator intervention to maintain grid stability.</li> <li style="font-weight: 400;" aria-level="1">Concerns were correlated with high levels of curtailment under NTE, impacting regulation availability and reserve calculations.</li> <li style="font-weight: 400;" aria-level="1">Consideration of reverting to tailored curtailment signals exists but NTE is currently providing some operational benefit.</li> <li style="font-weight: 400;" aria-level="1">Upcoming changes concern readiness for RTC and IRR automatic qualification for non-spin and ECR responsibility.</li> <li style="font-weight: 400;" aria-level="1">Discussions on resolution strategies continue with plans to improve resource response and communication about the urgency of corrective actions.</li> <li style="font-weight: 400;" aria-level="1">Stakeholders appreciate ERCOT's transparency and are committed to facilitating resolution efforts quickly.</li> </ul> <h2><a href="/sharing/?token=602c883f-243b-4a66-8c4a-1d87dd515253">▶️</a>6 - NPRR1214 Reliability Deployment Price Adder Fix to Provide Locational Price Signals, Reduce Uplift and Risk - Discussion</h2> <ul> <li style="font-weight: 400;" aria-level="1">Discussion centered on NPRR1214, focusing on reliability deployment and locational price signals.</li> <li style="font-weight: 400;" aria-level="1">Draft comments have been posted, with continued collaboration between ERCOT staff and sponsors to address remaining concerns.</li> <li style="font-weight: 400;" aria-level="1">The current draft may undergo further changes before finalization.</li> <li style="font-weight: 400;" aria-level="1">Main changes involve updates to settlement protocols, specifically the introduction of a settlement point level price adder.</li> <li style="font-weight: 400;" aria-level="1">The price adder name and variable have been updated to avoid conflicts in the settlement system.</li> <li style="font-weight: 400;" aria-level="1">Changes also include the addition of subscripts to indicate the settlement point level adder.</li> <li style="font-weight: 400;" aria-level="1">New paragraphs added to protocols to detail the settlement point level value and corresponding meter prices.</li> <li style="font-weight: 400;" aria-level="1">Clarification made that the price adder can be both positive and negative, with necessary adjustments made in corresponding protocol language.</li> <li style="font-weight: 400;" aria-level="1">There was confusion about whether the original or modified design should apply to hub prices.</li> <li style="font-weight: 400;" aria-level="1">Work was done to ensure clarity on whether a system-wide or settlement point level should be used for hub prices.</li> <li style="font-weight: 400;" aria-level="1">The language of the draft has not yet gone through internal review at ERCOT.</li> <li style="font-weight: 400;" aria-level="1">Stakeholders expressed appreciation for the transparency and thorough analysis provided in the draft.</li> <li style="font-weight: 400;" aria-level="1">Next steps involve filing the draft with WMS after it undergoes the internal ERCOT review process.</li> <li style="font-weight: 400;" aria-level="1">The group did not express immediate concerns, allowing the current draft to proceed subject to any future changes.</li> </ul> <h2><a href="/sharing/?token=3f3f6b09-3d42-4735-828d-f4d9efafa705">▶️</a>7 - Placeholder for WMS Referrals - tbd12/4 - Tbd</h2> <ul> <li style="font-weight: 400;" aria-level="1">No additional referrals received from WMS.</li> <li style="font-weight: 400;" aria-level="1">WMS agreed with recommendations from the last meeting on parking lot items.</li> <li style="font-weight: 400;" aria-level="1">Continuation of discussions on GTC transparency and impacts to congestion concerns is expected.</li> <li style="font-weight: 400;" aria-level="1">Specific focus noted on the GTCs as the root problem in the system.</li> <li style="font-weight: 400;" aria-level="1">The smaller load zones issue introduced by the IMM is removed from the parking lot for now.</li> </ul> <h2><a href="/sharing/?token=28e502c1-1b63-4e8c-a61e-838ce8746199">▶️</a>8 - RENA Update - QuestionsOnly - ERCOT</h2> <a href="https://ercot-control-docs.s3.us-west-2.amazonaws.com/05/rena_report_september_2024_cmwg.pdf">RENA Report September</a> <ul> <li style="font-weight: 400;" aria-level="1">Opportunity for participants to ask questions about the RENA Update.</li> </ul> <h2>▶️9 - Other Business - Alex Miller</h2> <h3><a href="/sharing/?token=0ea3a17f-5465-4db5-bb29-ec444cdd7d84">▶️</a>9.1 - 2025 Leadership</h3> <ul> <li style="font-weight: 400;" aria-level="1">2025 leadership nominations needed for January CMWG meeting.</li> <li style="font-weight: 400;" aria-level="1">Looking for one additional volunteer for the leadership team.</li> <li style="font-weight: 400;" aria-level="1">Interested individuals should contact through the email provided on the CMWG page.</li> </ul> <h2>10 - Adjourn</h2> <ul> <li style="font-weight: 400;" aria-level="1">The meeting adjourned.</li> </ul>