Meeting Summary - 5/29/2025 TWG Meeting

▶️1 - Antitrust admonition

▶️2 - NERC Update – EMSWG

NERC-EMSWG-Update_TWG_May2025.pdf

• NERC EMS Working Group provided updates on dealing with communication failures between control centers.
• Highlighted collective efforts, particularly contributions from ERCOT and Sreenivas Badri.
• Discussed operational scenarios where system operators and primary EMS servers are in separate control centers, which can lead to issues if communication fails.
• Provided three real event cases of communication failures leading to system visibility loss and server conflicts.
• The lessons learned from these cases will be published soon, and feedback from members is encouraged to improve system resilience.
• Open for any questions and encourages cooperation in developing better practices.

▶️3 - Project Updates

PRS_May_2025_Project_Update_evpczm5ojo24.pdf

• Troy Anderson presented updates from the PRS slide deck.
• NPRR1253 was discussed and is on the agenda for later.
• Market notice information was addressed.
• Efforts are underway to clear systems for RTC+B live launch on December 5.
• A new program called MPIM is being developed with components having external changes.
• Four revision requests were made at PRS; NPRR1226, NPRR1238, and NPRR1267 were approved and sent to TAC. NPRR1214 was tabled.
• Annual review of aging projects related to revision requests was introduced.
• There are 50+ items on the aging revision request project list, with plans to address them in upcoming months.
• The last review ended with 58 items; currently, planning and completion have reduced this to a smaller list.
• 26 items are post RTC+B related changes and 13 new items approved by stakeholders need categorization.
• Discussion at TAC meeting regarding prioritization of ongoing work queues post RTC+B.
• There is a need to establish a plan of attack post RTC+B go-live for project prioritization.

▶️4 - RTC+B Updates

▶️4.1 - Program and RTCBTF Updates

RTCB_TWG_Update_05292025.pdf

• Market trials updates and task force updates will be presented to the group.
• Several market trials have begun, with a lot of significant green progress achieved after clearing some policy issues.
• Lingering issues include NPRR1282 regarding state of charge duration and NPRR1290 filed 5/28/2025 with regards to a cleanup, although these should not impact market system design.
• A frequently asked questions document was established to address inquiries, and more training videos are being added to the RTCBTF homepage.
• Sample settlement statements extracts have been posted for testing purposes.
• Work on the closed loop frequency control test and transition cutover plan is ongoing.
• Weekly phone calls are held for updates and Q&A sessions regarding market trials.
• Market trials include QSE connectivity tests, market submission tests, and telemetry setup and checkout.
• Scorecards track progress, with dimensions for connectivity, telemetry, and checkout, being updated regularly.
• Certain known issues and potential workarounds are highlighted, promising resolution post-migration.
• Questions and interactive sessions are encouraged, helping clarify procedures and expectations.
• It was confirmed that telemetry during tests does not require accurate live data.

▶️4.2 - Market Trial Testing Status and Telemetry check out process

ERCOT-TWG-2025-5-29-RTC-B-Market-Trial-Testing-Status.pdf

• The focus is on providing an update on the market trial submissions, telemetry checkout, and testing status.
• QSE submission and telemetry verification are currently in progress.
• Market participants are actively submitting into the Market Management System and the Outage Scheduler system.
• The goal is to submit at least one successful transaction during an eight-week period per resource type book QSE.
• Kevin McGarrahan discussed the QSE telemetry checkouts, indicating most submissions have been received.
• Contact will be made for missing submissions, and active modeling of submissions is underway.
• Submissions today will be included in the JUN ML3 production model load; urgent submission is encouraged due to the three-week lead time for modeling.
• Testing involves sampling a few resources in each QSE and using test values for telemetry points such as resource status and UDSP.
• Live telemetry values are already being submitted by some, which aids the testing process.
• Testing progress is tracked using scorecards.

• The market trial environment received a new release addressing all current issues, particularly user access role sync with the MOTE system.
• Issues related to user access role sync due to cross-environment challenges have mostly been resolved, with enhancements added.
• Participants experiencing connectivity or user authentication issues are advised to contact the RTC+B mailbox for assistance.
• Submission validation issues have been addressed, though testing continues.
• Participants may encounter credit violations/errors when submitting for the next day; it's suggested to submit for two days ahead.
• The next release is planned for June, but critical issues may prompt faster interventions.
• Participants' telemetry submissions are crucial for model loads, with deadlines stressed for completion.
• Ongoing scorecard tracking will ensure participants reach compliance, with a grace period for resolving issues.
• 95% of QSEs are expected to pass the current phase before transitioning to the next testing phase.
• The upcoming open loop testing phase will require parallel market submissions with telemetry from participants.
• Continuous testing and system readiness for the closed loop phase are encouraged.
• Monday morning meetings at 10 AM will update known issues; no standalone issue tracker exists.
• A mailbox is provided for questions and feedback regarding market trials.

▶️4.3 - Market Submissions/Reports/Notifications Updates

ERCOT-TWG-2025-05-29-RTC-B-Market-Trials-Market-Submissions-Testing.pdf

• Sruthi Hariharan covered slides 17 and 18 of the above presentation.
• Highlighted frequently asked questions about reports available during market trial.
• Market trials will allow participants to view day-ahead reports and obligations during the closed loop phase.
• During open loop testing, four specific reports will be published:
• SCED Shadow Prices and Binding Transmission Constraints - NP6-86-CD
• LMPs by Resource Nodes, Load Zones and Trading Hubs Market Trials - NP6-788-CD
• Modify Real-Time ORDC and Reliability Deployment Price Adders and Reserves by SCED Interval - NP6-323-CD
• Real-Time Clearing Prices for Capacity by SCED interval – NP6-332-CD
• ERCOT will not provide QSE specific settlement statements during market trials but has released generalized sample statements for day-ahead and real-time settlements.
• Sample statements and related training videos are available on the May 21 RTC+B task force meeting page.
• Updates on reports and settlement statements have been discussed in previous meetings.
• Continuous updates to the slide deck will be made for reference material related to market submissions.

▶️4.4 - ICCP Handbook updates

ERCOT-TWG-2025-5-29-RTC-B-ICCP-Telemetry-Modeling.pdf

RTCB_Market_Trials_Handbook_4_QSE_TelemetryTests.pdf

• Presentation by Tejaswi Potluri on ICCP Handbook updates and changes specific to RTC+B.
• Updates to the ICCP handbook, including some changes to RTC+B price adders.
• Highlighted necessary changes for the regulation up and down price adders in the ancillary service.
• Discussed requirements for the July 7 through August 29 open loop phase of testing.
• Discussion on expectations for market participants and ERCOT during this phase, including weekly calls and production quality data requirements, looking over Market Trials Handbook 4.
• Prerequisites include ICCP points modeled and checkout completed, and quality data flow demonstration.
• Expectations for resource status during test windows, specifically the ability to follow UDSP signals.
• Caution about changes needed for receiving and acting on UDSP signals.
• Emphasis on key points of the RTC construct being information only, focusing on set point telemetry.
• The scorecard process will continue during the testing phase.
• Last call for questions, which received no queries.
• Reiteration by Sreenivas Badri of importance for QSEs to set up back-end systems for open testing starting in July.
• The presentation concluded with a reference to the RTC+B mailbox for further questions.

▶️5 - TLS Certificate Lifetime Reduction – Implementation details

ERCOT-TWG-2025-05-29-TLS-Certificate-Lifetime-Reduction.pdf

• Informational item about CA/browser forum's schedule change for shortening TLS certificate lifetime.
• New maximum lifetime for TLS certificates will be 200 days starting next year.
• Shorter certificate lifetimes aim to improve the revocation process and enhance security.
• ERCOT faces operational impacts due to increased frequency of certificate creation.
• Manual processes involved in certificate creation need review.
• Impact on secure external web services used by market participants.
• ERCOT is aware of these changes and has started a project to review related impacts.
• An update on necessary changes and technology implementations will be reported by the end of the year.

▶️6 - CIM16 Schema Upgrade Project - status update

ERCOT-TWG-2025-05-29_CIM16_Upgrade_Project_Update.pdf

• ERCOT currently produces models with CIM10 schema since 2010 and will transition to CIM16 by Q1/Q2 2027.
• The conversion project started in August 2024 and will phase out SIM10 models after completion.
• Processes that read ERCOT's redacted model will need to adjust import functions for CIM16.
• Transmission companies must adapt to importing via CIM16 instead of CIM10.
• ERCOT will provide a redacted model and schema by end of Q3/Q4, aligned with a workshop on changes from CIM10 to CIM16.
• Parallel posting of CIM16 and CIM10 models will occur during the transition.
• ERCOT will set a future meeting cadence and communicate dates through market notices and meeting calendars.
• An email CIM16@ERCOT.com is available for queries regarding the upgrade.
• A mode system for transmission companies will open by the end of Q4 2026.
• A workshop is planned in the upcoming months to discuss changes and provide training for the transition.

▶️7 - SCR820 – Real-Time Operator Messaging Tool update

ERCOT-TWG-2025-05-29-SCR820-RT-Operator-Communication-System.pdf

• Preethi Meher from ERCOT's grid and market systems team presented.
• The SCR820 RTOC is a web-based tool to enhance real-time coordination between ERCOT and transmission operators, supporting bidirectional messaging and logging interactions.
• The tool addresses communication overload during emergencies, reducing reliance on phone calls.
• Key project accomplishments:
• Built a demo tool, received feedback from TOs, refined project requirements, finalized planning phase.
• Target completion and testing timelines:
• Internal ERCOT development/testing by January 2026,
• TOs/QCs testing from mid-February to mid-April 2026.
• Parallel operations in May 2026, full go live by June 2026.
• Features include communication views, predefined message templates, and monitoring capabilities for SOL exceedances. Access is controlled with digital certificates with roles like admin, read-only, and operator.
• Tool will be accessible via mis.ercot.com application library. Continual updates will be shared in future meetings.
• QSEs and TSPs need to prepare for changes and participate in detailed testing plans from February 2026.
• The tool supplements the current communication procedures, not replacing existing roles or operations.

▶️8 - NPRR1253 Technical Implementation Review with Example

ERCOT-TWG-2025-05-29-NPRR1253-Technical-Implementation.pdf

• Presentation of NPRR1253 updates by Subhan Shaik from ERCOT's grid and market applications team.
• NPRR1253 involves ERCOT providing system-level ESR charging megawatt and system demand data for market participants' 4-CP load calculations.
• Data will be available to participants via ICCP and public API.
• ICCP telemetry changes were implemented and went live on March 27, adding a new telemetry point for ESR charging megawatt.
• Public API is set to go live today, offering 4-second ESR charging megawatt and system demand values every 5 minutes.
• Market participants need to send requests to ERCOT's API to access data; JSON payload metadata specifications discussed.
• Two sources of data, ICCP and public API, provide 4-second instantaneous megawatt values, with 15-minute averages needing to be calculated by participants.
• MIS WSL report publishes 15-minute intervals of wholesale storage load megawatt-hours, often closely matching calculated values.
• Public API provides system demand and ESR charging megawatt samples every 4 seconds, available every 5 minutes with a 20-second offset.
• Recommendation to use ICCP or public API for accurate 4-CP load calculations due to synchronization of data sources and timestamps.
• Public API goes live today, with full dataset availability from midnight tomorrow.

▶️9 - Round Table Discussion

• No initial questions or comments from participants, moving directly into topics.
• Discussion on the recent implementation impact on ERCOT and implications for RTC+B beginning preparations.
• Emphasized importance of 4-CP intervals during summer months (June-September).
• Market participants showed interest in ERCOT's load charging doctrines and their impacts.
• Reports indicate changes to 4-CP intervals compared to market participants' expectations last summer.
• Clarification on the calculation of coincident peaks within settlement intervals, changes include additions and subtractions concerning energy transfers and wholesale loads.
• Post-RTC+B changes will involve settlement only energy storage systems and redefine wholesale load storage.
• No additional comments or questions from participants on this topic.
• Potential updates on 4-CP topics to ensure market readiness and proactive data dissemination.
• Plans to discuss details further and provide more information in future meetings.
• Future topics include updates on RTC+B moving into open loop testing and development of DPC automation tool requirements.
• Discussion on wrapping up DPC automation tool requirements and feedback submission from TOS for upcoming TWG meeting.
• Acknowledgment for meeting facilitation and participation.

▶️10 - Adjourn