<div class="news-image-container"><img src="/storage/docs/2025/04/20250422RTCBTFHero.png" width="800" height="594" /></div>
<h3> </h3>
<h3><a href="/sharing/?token=6015717b-e281-4139-9705-48f97313b85a"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">1 - Anti-trust Admonition</span></h3>
<h3><a href="/sharing/?token=e7bb9400-eba7-47e8-9012-4dfde088e76e"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">2 - RTCBTF Update</span></h3>
<p><a href="/storage/docs/2025/04/2_RTCBTF_Update_04222025.pdf"><span style="font-weight: 400;">2_RTCBTF_Update_04222025.pdf</span></a></p>
<h4><a href="/sharing/?token=3edcfe7c-2b41-4800-9327-7cb1b9c4b86f"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">2.1 - Update on NPRRs at Board</span></h4>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Reviewed the old issues list with positive progress shown; more items marked as completed.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Acknowledgment of TAC and board approval for NPRR1268, NPRR1269, and NPRR1270, scheduled for commission consideration on May 15.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Development of new aggregated ORDC curve, AS demand curves, and proxy offer logic is underway.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Discussion on the state of charge duration parameter is planned; another revision anticipated for the June Board meeting.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Emphasis on ongoing market trials and planning for load frequency control (LFC) tests through April, May, and June.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Preparations for the go-live transition plan expected, including potential parallel data submissions and dual model day-ahead runs.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Consideration of protocol exemptions for LFC testing and go-live transition.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Acknowledgment of approved NPRRs and upcoming focus on state of charge discussions.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Clarification NPRR for June 18 regarding settlement corrections to align with protocols.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Highlighting NFRC telemetry updates requiring maintenance of specific data attributes for NERC evaluations.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Offer bid structure cleanup in progress, addressing monotonically non-increasing language on bids.</span></li>
</ul>
<h4><a href="/sharing/?token=bb873657-adad-4cfa-a521-69a3cf22bbc1"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">2.2 - Update on Scorecard</span></h4>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">TAC meetings scheduled for May leading to a June board meeting, and for August leading to a September board meeting.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">No other board meetings until the meeting in December, after going live.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">No changes in the market trial sequence; handbooks provide guidance on market submissions, telemetry startup, and open loop scheduling.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Final reviews for open loop scheduling and QSE telemetry test, initial reviews for closed loop LFC test and day ahead.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">New market trials and tech support folders available on the RTCBTF homepage.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Plan to add four more training videos before the next meeting.</span></li>
</ul>
<h4><a href="/sharing/?token=42d44f32-a730-4f3b-b804-753e72ddc6f1"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">2.3 - Update on Weekly WebEx Market Trials (Market Notice sent 4/16)</span></h4>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Market trials will use a central location for key documents like handbooks and technical details, located on the RTCBTF homepage.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The RTCB@ercot.com mailbox is operational and is managed to ensure quick responses.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Training videos are planned to aid in the market trials process.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">ERCOT engaged with the demand side working group for load resource participation training.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">A special session with the demand side working group was conducted with a focus on their participation in market trials.</span></li>
</ul>
<h4><a href="/sharing/?token=6cc97b54-0b67-4e18-935f-affc785628b2"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">2.4 - Operator Training Seminar Update</span></h4>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Operator training seminars have been conducted every Wednesday for the past month.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The seminars cover RTC basics and operations, with a focus on telemetry changes.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">600-800 operators have participated in the training at the T4 control center in Taylor.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Training sessions will conclude next Wednesday, with a focus on technical details related to RTC.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Preparation for formal market trials starting May 5th was discussed.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">A market notice was sent on March 13 to ensure market participants were aware of upcoming market trial activities.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">A 100% response rate was achieved for confirming readiness for the trials.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">A second notice was sent regarding mandatory real-time co-optimization and battery market trials for all QSEs with resources starting May 5.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Market trial schedules and expectations from May through October were outlined for participants.</span></li>
</ul>
<h4><a href="/sharing/?token=97aac420-2c30-4af3-b558-7b8c9f65722c"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">2.5 - Model Schedule Posted</span></h4>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Model load information is being posted to the RTCBTF homepage.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Network model, EMS system, and market management system topology were discussed.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">New resources and their display on the model load schedule were mentioned.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Highlighted the posting of the model schedule as a housekeeping item.</span></li>
</ul>
<h3><a href="/sharing/?token=5fde5e56-7e8a-4593-b567-026a04f96646"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">3 - State of Charge / AS Duration Discussion</span></h3>
<p><a href="/storage/docs/2025/04/3_RTCTF_Duration_Requirements_Topic_Update_v6.pdf"><span style="font-weight: 400;">3_RTCTF_Duration_Requirements_Topic_Update_v6.pdf</span></a></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">A presentation was given on the analysis updates regarding Non-Spin resources, specifically online Non-Spin resources, and how they were being deployed.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">It was noted that the analysis did not change the initial recommendation to recommend that Non-Spin duration lasts at least 4 hours.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Online Non-Spin capacity must be offered at a minimum of $75 per megawatt hour as per the protocols, with this capacity being available to SCED for deployment as needed.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">An estimation was conducted to evaluate the deployment of online Non-Spin resources by SCED.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Historical data from 06/01/2018 to 03/27/2025 was analyzed, showing that 81% of events had a duration of four hours or more.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Questions were raised regarding the impact of different price floors on the event patterns and on the reliability determination.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">A discussion was held on a specific date's analysis where forecast errors led to extended deployment of Non-Spin capacity.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Nitika Mago presented that the deployment patterns are driven by weather events and forced outages, which are difficult to forecast accurately.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Clarifications were made regarding the adjustments to battery state of charge calculations and their implications for the reliability need analyses.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">It was concluded that the information shared did not change the existing recommendation but highlighted the usage of Non-Spin capacity during system demands.</span></li>
</ul>
<h4><a href="/sharing/?token=d1e15aff-5612-4a37-9f5a-f4c7d03ad9bd"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">3.1 - Draft NPRR</span></h4>
<p><a href="/storage/docs/2025/04/3_XXXNOGRR-01-Related-to-NPRRXXX-Ancillary-Service-Duration-during-Real-Time-Co-Optimization-04XX25.pdf"><span style="font-weight: 400;">3_XXXNOGRR-01-Related-to-NPRRXXX-Ancillary-Service-Duration-during-Real-Time-Co-Optimization-04XX25.pdf</span></a></p>
<p><a href="/storage/docs/2025/04/3_XXXNPRR-01-Ancillary-Service-Duration-Under-Real-Time-Co-optimization-04DD25.pdf"><span style="font-weight: 400;">3_XXXNPRR-01-Ancillary-Service-Duration-Under-Real-Time-Co-optimization-04DD25.pdf</span></a></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The draft NPRR includes additional sections for clarity on qualification and monitoring criteria.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Key changes introduced include adjusting durations in various sections with acronyms established for consistency.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">In reliability unit commitment, a new paragraph includes a 60-minute duration for energy and ancillary services, excluding RRS provided using fast frequency response with a 15-minute duration.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Changes include replacing a 15-minute duration with 30 minutes in regulation and responsive reserve.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Adjustments also seen in monitoring criteria, replacing 15 minutes with 30, and ECRS criteria changed from two hours to one hour.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Discussion on the impact of Non-Spin resource qualification and ECRS.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Nitika Mago addressed the revisions focusing on regulation updates and ERCOT’s intention to file the NPRR.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Stakeholder comments emphasized the importance of ensuring market stability and considerations for evolving reserve durability.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Concerns raised regarding state of charge (SOC) limits and how language applies to breakdown scenarios.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Further inquiries included how the NPRR aligns with security constraints and socioeconomic dispatch parameters, ensuring it doesn’t violate max/min SOC limits.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Clarification provided that adjustments are needed when transitioning from a combo model to a single model concerning ESR registration.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Queries about the impact of the NPRR changes on day-ahead market ancillary services.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Stakeholders invited to provide further comments or proposals before the next session, with potential for additional sessions based on feedback.</span></li>
</ul>
<h3><a href="/sharing/?token=f84e2b87-622e-4743-a281-d41778fd8314"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">4 - Market Readiness</span></h3>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Discussion focused on the handbooks, with emphasis on transparency regarding recent modifications.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Acknowledgment of feedback loop necessity in case of issues with handbook updates.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Nathan Smith assisted in correcting handbook information regarding AS capability fields.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The field is not new but rather an adjustment from a single value to a megawatt value.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Clarification on telemetry checkout language to reflect that not all checkouts are complete but telemetry verification is recognized as success.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The language around telemetry verification has been softened to align with current progress and understanding.</span></li>
</ul>
<h4><a href="/sharing/?token=f8cbaed3-c5bf-43e1-9411-c7b6096a8548"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">4.1 - Review Handbook #3- Open Loop SCED (Round 3-Final)</span></h4>
<p><a href="/storage/docs/2025/04/4_RTCB_Market_Trials_Handbook_3_OpenLoop_RTC_SCED_04182025_FINAL.pdf"><span style="font-weight: 400;">4_RTCB_Market_Trials_Handbook_3_OpenLoop_RTC_SCED_04182025_FINAL.pdf</span></a></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Specific sections of the handbook are marked in green to indicate completion by ERCOT; this helps to show what the QSE needs to accomplish.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Section three of the handbook is crucial and has been discussed in past meetings.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">ERCOT will run RTC SCED in the market trials environment using market submissions and telemetry, with published prices and dispatch information.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Introduction of 'non-monitored operating days' where QSEs submit real-time offers with 80%-120% cost representation. Participation is not enforced but expected to improve market results.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">NPRR1058 allows all resources to update offers during the operating hour, with a mandatory reason in the text field for changes.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">SCED-generated capacity prices will be published by interval on ERCOT.com; reports must be downloaded as no dashboards or specific displays will be provided.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">SCED operations will occur on business days, specifically Tuesdays and Thursdays from 9 to 5, which provides a regular schedule for participants.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The handbook is being finalized and flagged as complete, but changes can be made if necessary.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">There was a question about schema changes for recent code requirements; it was clarified that the reason field is already part of submissions and will be validated during the operating period.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The same update logic for energy offer changes will apply to AS offer submissions, pending confirmation.</span></li>
</ul>
<h4><a href="/sharing/?token=fe9e579f-24aa-4e7b-9ae2-9a7a93d4d216"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">4.2 - Review Handbook #4- QSE Telemetry Tests (Round 3-Final) Abhi Masanna Gari</span></h4>
<p><a href="/storage/docs/2025/04/4_RTCB_Market_Trials_Handbook_4_QSE-Telemetry-Tests_04182025_FINAL.pdf"><span style="font-weight: 400;">4_RTCB_Market_Trials_Handbook_4_QSE-Telemetry-Tests_04182025_FINAL.pdf</span></a></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Presented the proposed final version of the QSE telemetry tests.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Tweaked the handbook for better clarity and specificity.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Discussed the parallel test window running alongside the open loop schedule.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Emphasized the need for accurate telemetry to support the market solution.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Outlined the coordination of individual QSE tests on selected resources for point-to-point telemetry checkout.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Clarified that QSE tests don't involve the whole fleet, only selected resources.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Set test times to Tuesday and Thursday, nine to five.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Open to observed or self tests, with ERCOT in knowledge of the tests.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Clarified that CLRs will not require additional tests.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Mentioned forms, sheets, and expectations will be provided as the process progresses.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Plans to put the finalized document on the website.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Discussion involving Nathan Smith and Dave Maggio on energy offer curves and the ability to update ancillary service offers.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Clarified the distinction between energy offers under NPRR1058 and RTCTF discussions.</span></li>
</ul>
<h4><a href="/sharing/?token=cb2c7193-fde1-4b07-8c32-320788bc918a"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">4.3 - Review Handbook #5- Close-Loop LFC Tests (Round 1-Initial)</span></h4>
<p><a href="/storage/docs/2025/04/4_RTCB_Market_Trials_Handbook_5_ClosedLoop_LFC_DRAFT_04182025.pdf"><span style="font-weight: 400;">4_RTCB_Market_Trials_Handbook_5_ClosedLoop_LFC_DRAFT_04182025.pdf</span></a></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Introduction of a new frequency control test from September to October, described as challenging.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Proposal of a two-hour test with QSE participation, ensuring reliable RTC SCED dispatch and frequency control without significant operational disruption.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">ERCOT to provide a minimum of ten business days advanced notice before test dates, with tests conducted to prevent frequency issues.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Details on managing transition risk through parallel production systems and binding RTC SCED during tests.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Minimizing the risk of significant redispatch through guardrails requiring QSEs to enter identical energy offer curves for both current and RTC systems.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Specific instructions for AS responsibilities: $0 offers for resources carrying responsibilities and $2,000/megawatt for others.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Consideration of current duration requirements over RTC during LFC tests for ESRs with response AS responsibility.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Telecom assumptions for QSEs and possible test run LFC to ensure QSE offers and telemetry are functioning prior to main tests.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Detailed test execution phases involving gradual QSE transition to RTC control, minimizing frequency swings during the test’s two-hour window.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Clarification on AS trades or changes within the test window, ensuring QSE can update offers as needed.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Financial settlements during tests based on current system prices, exempting base point deviation charges to prevent penalties.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Dispute conditions limited to financial harm instances, with criteria based on protocol 6.6.9(4)</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Discussion on potential repeat of the test twice if needed, with adjustments based on findings.</span></li>
</ul>
<h4><strong>Key Participants</strong></h4>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">ERCOT representatives introducing and explaining the test process.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Q&A from attendees like Ned Bonskowski, Dave Maggio, and Chris Espinosa providing additional inquiries on operational details.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Questions addressing specific scenarios like AS responsibility shifts and telemetry requirements.</span></li>
</ul>
<h4><strong>Next Steps</strong></h4>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Take feedback back to respective teams and provide additional questions or concerns in the next round of discussions.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Refine clarifications on AS offer protocols and test logistics prior to next meeting.</span></li>
</ul>
<h4><a href="/sharing/?token=4138c792-4d42-4ad9-8d03-cf2d6ce000df"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">4.4 - Review Handbook #6- Day-Ahead Market Tests (Round 1-Initial)</span></h4>
<p><a href="/storage/docs/2025/04/4_RTCB_Market_Trials_Handbook_6_DayAheadMarket_DRAFT_04182025.pdf"><span style="font-weight: 400;">4_RTCB_Market_Trials_Handbook_6_DayAheadMarket_DRAFT_04182025.pdf</span></a></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><strong>Voluntary Day-Ahead Market</strong></li>
<ul>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">The day-ahead market is voluntary post-RTC go live.</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Day-ahead market participation is encouraged but not mandatory in readiness metrics.</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Ancillary services (AS) are expected to have a liquid market.</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">The market will open to all QSEs, not just the existing participants.</span></li>
</ul>
<li style="font-weight: 400;" aria-level="1"><strong>Market Participation</strong></li>
<ul>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">QSEs can test market submissions like energy bids and AS offers.</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Specific transactions for energy storage can be submitted.</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Resource-specific AS offers can be submitted.</span></li>
</ul>
<li style="font-weight: 400;" aria-level="1"><strong>ESRs and Market Testing</strong></li>
<ul>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">ESR (energy storage resources) names updated in the system.</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">ESRs are available in RTCB environment for testing.</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Questions about inclusion and updating of ESR lists were discussed.</span></li>
</ul>
<li style="font-weight: 400;" aria-level="1"><strong>Market Trials and Advisory Obligations</strong></li>
<ul>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Day-ahead market tests are advisory with no binding commitments.</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Details about AS scheduling limits were clarified.</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Adjustment period is separate and not linked to closed loop tests.</span></li>
</ul>
<li style="font-weight: 400;" aria-level="1"><strong>Upcoming Sandbox and Reports</strong></li>
<ul>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Publicly available sandbox data to be discussed at a later point.</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Reports update planned for upcoming meetings.</span></li>
</ul>
<li style="font-weight: 400;" aria-level="1"><strong>Closing Remarks and Follow-ups</strong></li>
<ul>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Finalization of handbook items discussed.</span></li>
<li style="font-weight: 400;" aria-level="2"><span style="font-weight: 400;">Feedback on day-ahead market and closed loop testing to be sought in next meeting.</span></li>
</ul>
</ul>
<h3><a href="/sharing/?token=0df452fc-98be-40c4-9b4a-acaf84ad057f"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">5 - Review 3 New Training Modules</span></h3>
<h4><a href="/sharing/?token=e8e52f90-f1de-4ae8-aec7-da133b8cd40b"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">5.1 - Day-Ahead Market Training</span></h4>
<p><a href="/storage/docs/2025/04/5_RTCB_DAM_Training_v04182025.pdf"><span style="font-weight: 400;">5_RTCB_DAM_Training_v04182025.pdf</span></a></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Overview of day-ahead market changes in the RTC+B era compared to current operations.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Reminder of the day-ahead market timeline which remains unchanged, including AS obligations and incentive service demand curves.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Introduction of three different AS submissions: AS only (new), resource specific, and self-arrangement.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">No minimum obligation for AS submissions; advisory and final AS obligations calculated using LSE's load ratio share.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Shift in AS demand curve structure, moving away from an AS penalty cost structure to using AS demand curves in RTC.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">AS insufficiency process modifications where insufficiency may lead to market reopening for additional offers.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Introduction of AS only offers in RTC without resource ties, limited to specific AS types, and subject to a new credit exposure calculation.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Resource specific offers to continue with some modifications, and a new optimization focus on AS demand curves.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Self-arrangement can't exceed advisory obligation in RTC, and negative self-arrangements treated as price takers.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Energy Storage Resources (ESRs) to have a single model incorporating charging/discharging, and no ESR offline reserves allowed.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Training outcomes to be seen in September/October with ERCOT publishing AS obligation reports.</span></li>
</ul>
<h4><span style="font-weight: 400;">Questions</span></h4>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Clarification on AS insufficiency process in RTC and its interaction with pricing.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Clarification on the role of SASM in relation to real-time co-optimization.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Potential for earlier testing of AS obligation reports for integration purposes.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Further illustration on the co-optimization of resource specific and AS only offers.</span></li>
</ul>
<h4><span style="font-weight: 400;">Next Steps</span></h4>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Address the implementation details of new AS only offers and their market impacts.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Further clarification on the functional differences between day-ahead and real-time operations for battery resources.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">ERCOT to consider publishing AS obligation reports sooner for testing integration.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Continuing market training focusing on other key topics like battery operations in the day-ahead market.</span></li>
</ul>
<h4><a href="/sharing/?token=8546ed83-7f73-4e1c-b634-d67f5d68bc91"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">5.2 - Battery Training</span></h4>
<p><a href="/storage/docs/2025/04/5_RTCBTF_Battery-Overview-Training-4-22-25-as-of-4-17-25-1830.pdf"><span style="font-weight: 400;">5_RTCBTF_Battery-Overview-Training-4-22-25-as-of-4-17-25-1830.pdf</span></a></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Overview of the progress and future integration of battery energy storage systems into the ERCOT system.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Increase in battery energy storage capacity from less than 200 megawatts in 2019 to over 11,000 megawatts today, with expectations of reaching 18,000 by the end of the year.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Duration of batteries in the system mainly consists of one-hour duration batteries, with a future trend towards longer duration batteries.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Implementation of real-time co-optimization where more ancillary services are expected to be provided by batteries.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Introduction to new NPRRs that support the transition such as NPRR1014, NPRR1204, NPRR1236 and the cleanup NPRR1246.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Details about the single model approach which includes registration, qualification, modeling, and telemetry as a single resource.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Modification of setpoint deviation calculation with tighter tolerance requirements being implemented.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Procedures for submission of energy bid offer curves and real-time management in the day-ahead and real-time markets.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">RUC processes including DRUC and HRUC will be used to ensure enough capacity in future hours and how state of charge information will be utilized.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Deployment factors will simulate potential AS deployment used for future RUC calculations.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Discussion on how deployment factors are determined and how they can impact the market participants' operations.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Multiple questions were raised and answered about deployment factors, tolerances, and operating procedures.</span></li>
</ul>
<h4><a href="/sharing/?token=34a2181e-7f9d-4b42-8057-13c884f25b39"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">5.3 - RTC Spreadsheet Tool and Examples</span></h4>
<p><a href="/storage/docs/2025/04/RTC_RealTime_Market_Simulator_April-RTCBTF.pdf"><span style="font-weight: 400;">RTC_RealTime_Market_Simulator_April-RTCBTF.pdf</span></a></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Presentation used a simple model to illustrate price formation under RTC using different scenarios.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Ray Lee and the market analysis team were acknowledged for their contribution.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The presentation focuses on illustrating changes in outputs with RTC such as clearing prices, base points, and awards.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Simulation tool for scenarios is available on the RTC+B web page for download.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">SCED system overview: designed to provide the lowest cost set of resources to meet energy needs, with reserve pricing added outside optimization.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">RTC reflects scarcity of energy and ancillary services and factors ancillary service costs directly into LMPs.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Three scenarios presented: optimal allocation of ancillary services, transmission congestion management, and system scarcity impact.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Importance of making resources indifferent regarding capacity use for energy vs. ancillary services was emphasized.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Example scenarios demonstrated how RTC prioritizes the need to serve load and ensures operating profit consistency for resources.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">RTC can alleviate congestion by adjusting ancillary service awards and managing costs effectively.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">During tight conditions, RTC prioritizes energy over ancillary services and factors penalty costs.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Indifference in operating profit maintained irrespective of capacity use is essential.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Confirmation that offer cap remains at $5k in day-ahead but reduces to $2k for energy and ancillaries in real-time.</span></li>
</ul>
<h3><a href="/sharing/?token=ac44709c-789f-4919-ade1-d33c25bf8ff0"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">6 - TWG Updates/Questions</span></h3>
<p><a href="/storage/docs/2025/04/6_RTCBTF_Reports_CDR_PD_04182025.pdf"><span style="font-weight: 400;">6_RTCBTF_Reports_CDR_PD_04182025.pdf</span></a></p>
<h4><a href="/sharing/?token=b565dca5-f80e-4e7d-b150-751d78d2eac1"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">6.1 - Reports Update</span></h4>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Discussion on the timing and phases of report deliveries.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Reports will be delivered in multiple phases: no new reports on May 5, but introduction of wave one and wave two groups.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Group One involves open loop testing reports including RTC energy prices, binding constraints, adders, and market clearing prices for ancillary services.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Group Two involves closed loop testing, with seven additional reports and 11 new CDR reports available in September.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Some reports could be moved up to July for integration testing.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Reports are categorized as existing, modified, or new, with some changes not affecting the data itself.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The complete inventory includes around 95 reports, detailing when each will be released and any associated changes.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Dashboards and XSD files also discussed; XSDs available by October 15 for integration building.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The ERCOT reporting inventory tool, EMIL, was mentioned as a resource for tracking reports.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">No significant changes in graphic/dashboard elements except for a few modifications.</span></li>
</ul>
<h3><a href="/sharing/?token=2caac6f0-3464-46e0-ae2b-72fd1a3c3b2c"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">7 - Other Business</span></h3>
<h4><a href="/sharing/?token=eb2887c0-0ec4-4ee7-92c7-5348e2cafb3c"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">7.1 - Next Steps on HEN Proposal related to underlying AORDC Calculations</span></h4>
<p><a href="/storage/docs/2025/04/7_HEN_Appropriate-Parameters-for-the-AORDC.pdf"><span style="font-weight: 400;">7_HEN_Appropriate-Parameters-for-the-AORDC.pdf</span></a></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Shams Siddiqi clarified that the HEN proposal does not seek to change the AORDC curve shape.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">The proposal suggests using unaltered ORDC μ and σ for AORDC calculations.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Critique of the current process as cumbersome and based on regression fit that undervalues MCPC.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Advocated for using current ORDC hourly statistics for μ and σ.</span></li>
<li style="font-weight: 400;" aria-level="1">Current AORDC uses μ* and σ*, which are seen as incorrect proxies.</li>
<li style="font-weight: 400;" aria-level="1">Shortcomings of the option two ORDC adder formula lead to undervaluing of reserves.</li>
<li style="font-weight: 400;" aria-level="1">Using unaltered ORDC statistics could correct inadvertent price suppression.</li>
<li style="font-weight: 400;" aria-level="1">No system changes required, just a manual update of parameters.</li>
<li style="font-weight: 400;" aria-level="1">Could potentially address the missing money problem in current market pricing.</li>
<li style="font-weight: 400;" aria-level="1">Some members are cautious about implementing significant changes before RTC go live.</li>
<li style="font-weight: 400;" aria-level="1">Concerns over how these changes interact with future market design and reliability standards.</li>
<li style="font-weight: 400;" aria-level="1">Need for broad analysis and simulations to understand full market impact.</li>
<li style="font-weight: 400;" aria-level="1">Potential for an NPRR submission to facilitate further study.</li>
<li style="font-weight: 400;" aria-level="1">Possible escalation to TAC and other bodies for higher-level discussion.</li>
<li style="font-weight: 400;" aria-level="1">Some participants suggested considering this alongside broader market design changes post-RTC implementation.</li>
</ul>
<h3><a href="/sharing/?token=e83e50cc-0798-4983-b502-1a6c52ee0625"><span style="font-weight: 400;">▶️</span></a><span style="font-weight: 400;">8 - Adjourn</span></h3>