<p><span style="font-weight: 400;"><img src="/storage/docs/2024/04/TXSET.png" width="569" height="428" /></span></p>
<p> </p>
<p><span style="font-weight: 400;"><a href="/sharing/?token=e178651a-8b71-4dae-b62a-0cd4dfefffc9" target="_blank" rel="noopener">4</a> - Technical Advisory Committee Update - John Schatz</span></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">RMGRR177 was approved.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">RMS ROS, and WMS 2024 goals were approved </span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Lubbock update was provided and there were no questions, indicating satisfaction with Lubbock's transition progress</span></li>
</ul>
<p><span style="font-weight: 400;">TAC meeting centered around significant discussion on NOGRR245, with multiple failed ballots, eventually passing as recommended by ROS in the 9/14/23 ROS Report as amended by the 3/22/24 Joint Commenters 2 comments as revised by TAC</span></p>
<p><span style="font-weight: 400;">5 - ERCOT Updates - David Michelsen</span></p>
<p><span style="font-weight: 400;"><a href="/sharing/?token=010ddebb-2b6b-4f01-b7e6-82a8dcfff372" target="_blank" rel="noopener">5.1</a> - Flight Update - David Michelsen</span></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Update on flight 0224: Working with one Competitive Retailer (CR) and one TDSP to complete banking script, regular communications ongoing</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Upcoming flight:, sign up deadline on May 1, connectivity begins on May 7, contingency runs through 6/21</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Flight 0924 (Texas set 5.0): Application deadline on 7/3, sign up deadline at the end of July, connectivity begins on 8/6</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;"> All CRs must pass this flight test - need to verify information, update specifications before starting the flight</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Market notice sent out on 03/20, maintaining eligibility to participate in the retail market moving forward</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Flight 0924 scheduled to conclude on 10/04, moving into production in early November</span></li>
</ul>
<p><span style="font-weight: 400;"><a href="/sharing/?token=38d62135-c0e5-49eb-ab1c-bfcf0bd5b049" target="_blank" rel="noopener">5.2 </a>- Retail Projects Update - David Michelsen</span></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Retail API update: Data fix for key date value</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Anticipated implementation date: April 25th, brief outage expected for the update</span></li>
</ul>
<p><span style="font-weight: 400;"><a href="/sharing/?token=74ba3b44-d9c4-4e32-98e1-0e39f6bfad15" target="_blank" rel="noopener">5.3</a> - IT Report - Mick Hanna</span></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Service availability for March did not meet SLA targets due to a manual error causing an outage for approximately 93 minutes.</span></li>
</ul>
<p><span style="font-weight: 400;"><a href="/sharing/?token=ce4b1b2b-1735-48b4-a600-5756fe6c9c9e" target="_blank" rel="noopener">5.4</a> - ERCOT Developer Portal Review - Mick Hanna</span></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">ERCOT Developer Portal went live on the 28th, featuring applications, API specs, and a discussion forum.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Applications currently include EWS, Market Track, Public API, and NAESB. API specs feature the same applications, replacing NAESB with Retail API.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;"> No clear timeline yet on Web Services Description Language (WSDL) file for Texas Set 5.0</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">A commitment was made to arrange a meeting for API users to address concerns and explore potential solutions, aiming for the end of April.</span></li>
</ul>
<p><span style="font-weight: 400;"><a href="/sharing/?token=3bee38c9-515b-43a1-817f-31f28c9b0f78" target="_blank" rel="noopener">6</a> - NPRR1212 - Randy Roberts</span></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">NPRR1212 and PGRR114 are linked RRs that clarify relationship between DSPs and REs in terms of providing ESI IDs before the RE can start consuming load</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Consensus to move NPRR1212 to the combo ballot with an attached motion that RMS endorse NPRR1212 as recommended by PRS in the 03/20/24 PRS comment.</span></li>
</ul>
<p><span style="font-weight: 400;"><a href="/sharing/?token=ba40c4c3-92a5-4eb5-849e-704c7a1ede54" target="_blank" rel="noopener">6.1</a> - PGRR114 - Randy Roberts</span></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">There was consensus to endorse PGRR114 as recommended by ROS in the 03/07/24 ROS report via the combo ballot</span></li>
</ul>
<p><span style="font-weight: 400;"><a href="/sharing/?token=e8e03cdb-724a-4240-8300-df6d68e9c20b" target="_blank" rel="noopener">7</a> - Combo Ballot - John Schatz</span></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">NPRR1212 - To endorse as recommended by PRS in the 03/20/24 PRS report</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">PGRR114 - To endorse a recommended by ROS in the 03/07/24 ROS report</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Motion carries with two abstentions, STEC and APG&E marked as abstention due to absent representative</span></li>
</ul>
<p><span style="font-weight: 400;"><a href="/sharing/?token=fcd7add6-7821-4be0-8dfc-4557908fbe58" target="_blank" rel="noopener">8</a> - Lubbock Power & Light - Clint Gardner</span></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Lubbock Power and Light's transition to a TDSP is complete</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;"> LP&L working through issues related to metering and continues to make progress addressing those</span></li>
</ul>
<p><span style="font-weight: 400;"><a href="/sharing/?token=b641b4ae-4abe-4cf1-b8e5-25f4e41d9173" target="_blank" rel="noopener">9 </a>- Lubbock Retail Integration Task Force - Sheri Wiegand</span></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Discussed the transition stacking logic, removed on March 4, to accommodate true move-ins and choice transactions.</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Have made progress addressing issues related to transition to competitive REPs taking over billing, multiple ESI IDs for the same address not all enrolling with the same REP and addressing low meter read rates associated with a server crash during 3/4-3/19 </span></li>
</ul>
<p><span style="font-weight: 400;"><a href="/sharing/?token=e9b0d099-a410-46ae-9ea9-7050beacdd74" target="_blank" rel="noopener">12</a> - Other Business - John Schatz</span></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">John Schatz provided an update on the latest cybersecurity measures implemented by ERCOT </span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Discussed the potential impact of cybersecurity breaches on grid reliability and the measures taken to mitigate these risks</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Highlighted the need for continued vigilance and investment in cybersecurity to safeguard ERCOT operations</span></li>
</ul>