Meeting Summary - 01/13/2025 OWG Meeting

Grid Monitor AI
01/13/2025

<h2><span style="font-weight: 400;"><img src="/storage/docs/2025/01/2025-01-13_OWG_hero.png" /></span></h2> <h2><a href="/sharing/?token=2357206a-54e5-4280-98b5-4bd47ad7e304"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;"> 1 - Antitrust Admonition R. Floyd</span></h2> <h2><a href="/sharing/?token=8b33c443-4bec-49c8-9687-0bca49694ea5"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;"> 2 - ERCOT Updates and System Operation Report ERCOT Staff</span></h2> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Peak demand for December 2024 was 65,429 Megawatts.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">For perspective, the all-time December peak was 74,525 Megawatts on December 23rd, 2022, during winter storm Elliott.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">No new wind, solar, or renewable penetration records were set for December.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">No questions were raised in response to the update.</span></li> </ul> <h2><a href="/sharing/?token=530ab3a3-8634-4760-9db3-5ebf4b341044"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;"> 3 - Texas Reliability Entity Report Texas RE Staff</span></h2> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">A notice was issued regarding the EOP-12 standard, which hasn't been receiving high ratings (around the 40th percentile).</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Due to a deadline imposed by FERC to file the standard by the end of March, the NERC board invoked its authority to expedite the process.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The standards committee will hold special sessions to finalize the language requirements for the EOP-12 standard.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">A public comment period will be held, followed by a special board meeting in the first week of March to meet the filing deadline.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">ERCOT participants are encouraged to monitor the ERCOT website for updates on the comment period to provide feedback.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Upcoming events include a Webex on NERC and ERCOT reliability assessments on the 21st and a Webex on the interregional transfer capability study on the 29th.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">A quarterly board and MRC meeting is scheduled for February 19th.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">A polar vortex is expected to impact the area starting potentially as early as Sunday, bringing cold weather.</span></li> </ul> <h2><a href="/sharing/?token=e7fbdddf-07c8-41c4-8601-3d2b425a840a"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;"> 4 - NPRR1070 Planning Criteria for GTC Exit Solutions &ndash; Tabled. No updates required at this time R. Floyd</span></h2> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">NPRR1070 has been tabled for a while with no updates.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Active work is ongoing on comments and revisions for NPRR1070 due to the implementation of NPRR1247 and other associated PGRRs.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Progress is being made, and comments are expected to be submitted soon.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Item will remain tabled pending further comments.</span></li> </ul> <h2><a href="/sharing/?token=1745a46b-9de4-4adc-8143-ac5d9d688817"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;"> 5 - NPRR1238 Voluntary Registration of Loads with Curtailable Load Capabilities Golden Spread &ndash; Joe Wilson</span></h2> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The team is preparing to file comments for NPRR1238, with a plan to have feedback ready by the next meeting.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The comments focus on three main areas: definition, QSE destination, and VECL deployment.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">It was suggested to relocate the protocol section to better highlight the ineligibility of ERCOT's ERS program participants to be VECL.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Concerns were raised about the current language allowing frequent QSE designation changes, suggesting a 45-day notification period to align with the update timeline.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">For VECL deployment, the team is considering using a group-based approach, similar to the Non-Spin and ERS systems, based on real-time conditions.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The proposed language includes provisions for disconnecting VECL remotely and ensuring no impact on non-VECL customers.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">There's a suggestion to provide real-time demand data and deployment instructions to ERCOT for situational awareness.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Recommendations were made to remove certain proposed requirements, such as the QSE load share table and 20% ramping down limit, due to the real-time data availability.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The team agreed to prepare and share documents related to these comments prior to the next meeting.</span></li> </ul> <h2><a href="/sharing/?token=b03a2616-21ae-409a-aa10-2754f0d25e1a"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;"> 6 - NOGRR265 Related to NPRR1238, Voluntary Registration of Loads with Curtailable Load Capabilities Golden Spread &ndash; Joe Wilson</span></h2> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Registration process for VECL was discussed, including the ability to register or deregister at any time.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Concerns raised about the feedback loop and notification process for registration changes.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Real-time data provision by VECLs is expected for better consumption awareness and deployment.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Condition of service for VECLs was emphasized, suggesting a perpetual registration requirement.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Need for a feedback mechanism involving entities like TSPs was highlighted due to current gaps in tracking entities.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">A formal agreement involving multiple parties (customer, QSE, TDSP) is required for application submission.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Comments and suggestions requested to improve the process and address any issues.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Discussion on moving out of VECL highlighted, encouraging further thought and resolution by the next meeting.</span></li> </ul> <h2><a href="/sharing/?token=d015eef2-51f2-4ed0-8913-98e89ef2dee3"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;"> 7 - OWG Leadership Nominations R. Floyd</span></h2> <ul> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Tyler Springer, the co-chair from last year, agreed to remain as last chair if OWG approves.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Rickey Floyd agreed to remain as chair if OWG supports the decision.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The position of a hot list sub-chair is deemed unnecessary for OWG moving forward.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The chair and last chair are considered capable of handling the hot list responsibilities.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Proposal to not include a hot list sub-chair for 2025 and manage updates through the standard leadership process.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">No additional comments or nominations for OWG leadership were raised.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">General consensus reached in agreement with the current leadership structure and removal of the hot list sub-chair role.</span></li> <li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Recommendation to be presented at the next month's ROS meeting.</span></li> </ul> <h2><a href="/sharing/?token=59926f55-aaa8-407e-bed3-4c7d88dcb276"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;"> 8 - Other Business R. Floyd</span></h2>