Frame

Meeting Summary - 12/10/2024 - RMS Meeting

Grid Monitor AI
12/11/2024

<h2><img src="/storage/docs/2024/12/20241210RMS%20Hero.png" width="865" height="650" /></h2> <h2><a href="/sharing/?token=40821bde-c4c3-4ff1-a4ab-ea69b932c215">▶️</a> 1 - Antitrust Admonition John Schatz</h2> <h2><a href="/sharing/?token=47740da4-1f47-4912-866c-b6dbf13cc8e0">▶️</a> 2 - Agenda Review John Schatz</h2> <h2>3 - Not Discussed</h2> <h2><a href="/sharing/?token=734c3652-d1b5-4471-9459-6265f6e52693">▶️</a> 4 - New Protocol Revision Subcommittee PRS Referrals Vote John Schatz</h2> <h3><a href="/sharing/?token=c6d359a2-34a5-487d-9958-98c94156e00e">▶️</a> 4.1 - NPRR1259, Update Section 15 Level Response Language</h3> <ul> <li style="font-weight: 400;" aria-level="1">Motion to endorse NPRR1259 as revised by RMS added to the combo ballot</li> <ul> <li style="font-weight: 400;" aria-level="2">Overview of NPRR1259: It aims to align ERCOT's response time protocol with SLA strategy, ensuring there's no protocol violation during system outages.</li> <li style="font-weight: 400;" aria-level="2">The NPRR ensures timing requirements do not include duration of planned and approved ERCOT retail system outages.</li> <li style="font-weight: 400;" aria-level="2">Kathy Scott proposed modifications to ensure clarity about the approval process by the tax subcommittee for outages.</li> <li style="font-weight: 400;" aria-level="2">Participants agreed on revising language about planned and subcommittee-approved outages.</li> <li style="font-weight: 400;" aria-level="2">Consensus reached to move to a combo ballot with a motion to endorse NPRR1259 as revised by WMS.</li> <li style="font-weight: 400;" aria-level="2">While the NPRR alters the protocol slightly, there's no change in current practice since ERCOT doesn't normally request approval during retail business hours.</li> <li style="font-weight: 400;" aria-level="2">Discussion suggested aligning the changes with upcoming SLA conversation and year's release calendar.</li> </ul> </ul> <h2><a href="/sharing/?token=ce90ef8c-7190-4088-be27-202417c13d48">▶️</a> 5 - ERCOT Updates</h2> <h3><a href="/sharing/?token=b9fa9af6-6d1e-42a6-a2aa-9207ba267be8">▶️</a> 5.1 - Flight Update David Michelsen</h3> <a href="https://dash2.gridmonitor.com/storage/docs/2024/12/05-flight-testing-update-to-rms20241210.pdf">05-flight-testing-update-to-rms20241210.pdf</a> <ul> <li style="font-weight: 400;" aria-level="1">28 new CRS came in; one withdrew; only a few were brand new during 5.0 testing.</li> <li style="font-weight: 400;" aria-level="1">113 existing CRS retested for the flight 0924 for 5.0.</li> <li style="font-weight: 400;" aria-level="1">First heads up for the 2025 flight schedule sent.</li> <li style="font-weight: 400;" aria-level="1">Reminder set for January 25, 2025.</li> <li style="font-weight: 400;" aria-level="1">Application deadline on January 15, 2025.</li> <li style="font-weight: 400;" aria-level="1">Concerns raised about timeline due to holiday season; first flight of the year is critical.</li> <li style="font-weight: 400;" aria-level="1">Signup deadline January 29, 2025.</li> <li style="font-weight: 400;" aria-level="1">Connectivity testing to commence in early February and conclude by early March.</li> </ul> <h3><a href="/sharing/?token=edfb4477-20a7-471f-ba79-8c38d5727471">▶️</a> 5.2 - Retail Projects Update David Michelsen</h3> <ul> <li style="font-weight: 400;" aria-level="1">Project updates will be primarily driven by Texas SET and TDTMS.</li> <li style="font-weight: 400;" aria-level="1">The Texas 5.0 release was successful considering the scope and number of systems involved.</li> <li style="font-weight: 400;" aria-level="1">Ongoing issues are being tracked with known paths forward.</li> <li style="font-weight: 400;" aria-level="1">Effective communication and quick response times were highlighted as key factors.</li> <li style="font-weight: 400;" aria-level="1">Processing percentages were in excellent shape within a few days post-Go Live.</li> <li style="font-weight: 400;" aria-level="1">Further discussions are expected in upcoming working group sessions.</li> </ul> <h3><a href="/sharing/?token=5ca5a6ef-f934-45ff-8d19-68b79609a4ec">▶️</a> 5.3 - IT Report Mick Hanna</h3> <a href="https://dash2.gridmonitor.com/storage/docs/2024/12/05-ercot_it_report_december_2024_-_rms.pdf">05-ercot_it_report_december_2024_-_rms.pdf</a> <ul> <li style="font-weight: 400;" aria-level="1">Report on IT issues in November, including Texas upgrade and site failure on the 17th for retail and listserv, with other systems failing over on the 14th.</li> <li style="font-weight: 400;" aria-level="1">MarkeTrak performance metrics were significantly better than the 12-month average.</li> <li style="font-weight: 400;" aria-level="1">Noticed a major spike in MarkeTrak volume on October 24th, reaching 60,000 transactions in a day, compared to the usual 7,000.</li> <li style="font-weight: 400;" aria-level="1">Listed graph updates will show trending over time in upcoming reports.</li> <li style="font-weight: 400;" aria-level="1">Reported listserv activity with significant post and recipient numbers.</li> <li style="font-weight: 400;" aria-level="1">Single weather moratorium removal noted due to a potential cybersecurity system action.</li> <li style="font-weight: 400;" aria-level="1">Clarified changes and scheduling for future production releases, with emphasis on retail weekday releases happening on Thursdays after April.</li> <li style="font-weight: 400;" aria-level="1">Emphasized targeting system updates that can occur with minimal downtime and moving towards a no-downtime patching scenario.</li> <li style="font-weight: 400;" aria-level="1">Discussed changes with the SLAs and the approval of NPRR 1259 for relevant scheduling, which might affect schedule by April 2024.</li> <li style="font-weight: 400;" aria-level="1">Acknowledged cybersecurity needs driving new initiatives and improvements in system patching processes.</li> </ul> <h4><a href="/sharing/?token=69ef5577-ffc3-4116-8920-9d9890a42304">▶️</a> 5.3.1 - 2025 Retail and ListServ Market IT Services Service Level Agreement Possible Vote</h4> <ul> <li style="font-weight: 400;" aria-level="1">Motion to add 2025 Retail and ListServ Market IT Services SLA.v2 - to approve as revised by RMS to the combo ballot </li> <ul> <li style="font-weight: 400;" aria-level="2">Discussion on the Retail Analyst Serve Market IT Services SLA V2 changes, primarily updates to calendar dates from 2024 to current year.</li> <li style="font-weight: 400;" aria-level="2">Clarification needed on production releases: weekdays should occur on Wednesday and Thursday, and weekends on Sunday.</li> <li style="font-weight: 400;" aria-level="2">A specific focus was on the SLA changes related to NPRR 1259, which influences the SLA effective date and is expected to be approved by April 1st.</li> <li style="font-weight: 400;" aria-level="2">The suggestion to remove weekday releases for January, February, and March to minimize confusion due to pending NPRR 1259 approval.</li> <li style="font-weight: 400;" aria-level="2">Proposal to explicitly reference NPRR 1259 in the SLA to avoid misunderstandings.</li> <li style="font-weight: 400;" aria-level="2">The possibility of approving the SLA in January or with provisions post-April 1 was discussed, with an option to revisit if needed.</li> <li style="font-weight: 400;" aria-level="2">Agreement to remove weekday releases for January, February, and March and include reference to NPRR 1259.</li> <li style="font-weight: 400;" aria-level="2">Consideration of approving SLAs multiple times a year if necessary, noting precedence.</li> <li style="font-weight: 400;" aria-level="2">General consensus to take this SLA item to the combo ballot for approval as revised, with edits to be finalized.</li> </ul> </ul> <h4><a href="/sharing/?token=68dec65e-72fd-4c75-ae23-836df9af0716">▶️</a> 5.3.2 - 025 Market Data Transparency Service Level Agreement Possible Vote</h4> <ul> <li style="font-weight: 400;" aria-level="1">Motion to add 2025 Retail and ListServ Market IT Services SLA.v2 - to approve as revised by RMS to the combo ballot</li> <ul> <li style="font-weight: 400;" aria-level="2">Discussion on market data transparency SLA with no additional edits besides the ones on the table.</li> <li style="font-weight: 400;" aria-level="2">Confirmation was needed regarding approval dates.</li> <li style="font-weight: 400;" aria-level="2">Technical issues regarding screen sharing were sorted out.</li> <li style="font-weight: 400;" aria-level="2">Revisions to SLA included replacing R1, R2, and R3 with 'no release' as seen in previous versions.</li> <li style="font-weight: 400;" aria-level="2">Participants were shown a cleaned-up version of the SLA.</li> <li style="font-weight: 400;" aria-level="2">Request for consensus to move the SLA to combo ballot with an intention to approve the edited version.</li> <li style="font-weight: 400;" aria-level="2">Clarification that documents were available in both PDF and Word versions, facilitating edits.</li> <li style="font-weight: 400;" aria-level="2">Approval sought for both the retail SLA and market data SLA version 2 as revised by RMS.</li> <li style="font-weight: 400;" aria-level="2">Acknowledgments and gratitude expressed by participants for cooperation and patience.</li> </ul> </ul> <h2><a href="/sharing/?token=6d6234df-66a3-4653-9fe2-e1a568ad840e">▶️</a> 6 - New Part 1 Commissioning Checklist Requirement (NPRR1212/PGRR114) Kelly Brink</h2> <a href="https://dash2.gridmonitor.com/storage/docs/2024/12/06-new-part-1-commissioning-nprr1212-and-pgrr114.pdf">06-new-part-1-commissioning-nprr1212-and-pgrr114.pdf</a> <ul> <li style="font-weight: 400;" aria-level="1">Presentation about new gen site setup requirements, crossing between modeling and needing assistance from retail electric providers and TDSPS.</li> <li style="font-weight: 400;" aria-level="1">NPRR1212 effective as of 8.1 requires an ESI ID setup before consuming load at a site, to prevent load consumption without proper accounting.</li> <li style="font-weight: 400;" aria-level="1">Resource entities must coordinate with DSPs and retail energy providers to ensure attributes and ESI ID to LSE relationships are setup.</li> <li style="font-weight: 400;" aria-level="1">ERCOT planning guide updated to reflect this as part of requirements before Part 1 approval.</li> <li style="font-weight: 400;" aria-level="1">Part 1 approval is paused until ESI ID is correctly set up.</li> <li style="font-weight: 400;" aria-level="1">Information on attributes for ESI ID: business IDR required, non-weather sensitive profile code, and reviewing loss codes.</li> <li style="font-weight: 400;" aria-level="1">Exceptions for sites that do not require ESI IDs: WSL-only energy usage for charging batteries and generation sites behind NOE tie points.</li> <li style="font-weight: 400;" aria-level="1">Provided a list of transactions required from TDSPs and LSES.</li> <li style="font-weight: 400;" aria-level="1">No transactional responses required from NOE, need for direct communication for setup.</li> <li style="font-weight: 400;" aria-level="1">Causes of delays include lack of understanding of ESI ID setup requirements.</li> </ul> <ul> <li style="font-weight: 400;" aria-level="1">Raised awareness request for TDSPs about the requirement.</li> <li style="font-weight: 400;" aria-level="1">Encountered frequent market tracks from ERCOT requiring ESI ID setups.</li> <li style="font-weight: 400;" aria-level="1">Identified knowledge gaps within organizations due to growth in solar farms, wind farms, and battery storage.</li> <li style="font-weight: 400;" aria-level="1">Collaborated with ERCOT to address ongoing issues.</li> <li style="font-weight: 400;" aria-level="1">Acknowledged that all TDSPs face similar challenges.</li> </ul> <ul> <li style="font-weight: 400;" aria-level="1">Supported the assessment of data gaps and the need for ESI ID setups.</li> <li style="font-weight: 400;" aria-level="1">Suggested creating a checklist for SODGs to improve setup processes.</li> <li style="font-weight: 400;" aria-level="1">Mentioned issues with improper ESI ID setups causing delays.</li> </ul> <h2><a href="/sharing/?token=766e6305-b744-4ea9-b76b-7100ddbc4ec7">▶️</a> 7 - Combo Ballot Vote</h2> <ul> <li style="font-weight: 400;" aria-level="1">Motion to approve the combined ballot as presented carried unanimously.</li> </ul> <img src="https://dash2.gridmonitor.com/storage/docs/2024/12/Combo_Ballot_Details_RMS_Dec10.png" width="854" height="70" /> <img src="https://dash2.gridmonitor.com/storage/docs/2024/12/Combo_Ballot_Vote_RMS_Dec10.png" width="850" height="732" /> <h2><a href="/sharing/?token=eaec875d-df02-43ca-9f7c-7c3d3068f74b">▶️</a> 8 - Lubbock Retail Integration Task Force LRITF Sheri Wiegand</h2> <a href="https://dash2.gridmonitor.com/storage/docs/2024/12/08-lritf-update-20241210.pdf">08-lritf-update-20241210.pdf</a> <ul> <li style="font-weight: 400;" aria-level="1">Last task force meeting was mid-October with one weekly call since.</li> <li style="font-weight: 400;" aria-level="1">Discussion and updates were planned for the LRITF meeting later that afternoon.</li> <li style="font-weight: 400;" aria-level="1">Key topics to be discussed include decimals conversation post Texas SET 5.0 and Lubbock's reversioned LSE files.</li> <li style="font-weight: 400;" aria-level="1">Lubbock has gap retrieval in place, but manual push for revised LSC files is still required.</li> <li style="font-weight: 400;" aria-level="1">New Lubbock tariff went into effect on November 1st, with changes including delivery service fee and franchise fee adjustments.</li> <li style="font-weight: 400;" aria-level="1">DLS Distribution loss factors were thought to have improved; updates expected in the afternoon's meeting.</li> <li style="font-weight: 400;" aria-level="1">Stabilization issues being addressed include DNP 650.01 reconnect processing corrections and remediation for service charge errors.</li> <li style="font-weight: 400;" aria-level="1">Need for correction on overcharge of premium fee and double billing instances.</li> <li style="font-weight: 400;" aria-level="1">Problem with standalone 810s and remediation plans discussed.</li> <li style="font-weight: 400;" aria-level="1">Issues with 867 IDRs and missing bills being worked on, corrections detailed.</li> <li style="font-weight: 400;" aria-level="1">Upcoming corrections on backdated move-ins and issues with start and end reads.</li> <li style="font-weight: 400;" aria-level="1">MarkeTrak counts discussed with plans for updates in the afternoon meeting.</li> <li style="font-weight: 400;" aria-level="1">Lessons learned from transition to competitive market for future use with municipalities.</li> <li style="font-weight: 400;" aria-level="1">Overall progress includes successful transition of over 100,000 ESI IDs into competitive market, with Lubbock integrating well.</li> <li style="font-weight: 400;" aria-level="1">Smart Meter Texas integration remains the last major task, with updates expected from Chris.</li> <li style="font-weight: 400;" aria-level="1">No questions from attendees indicated satisfaction with updates and progress.</li> </ul> <h2><a href="/sharing/?token=61af188c-9e86-4d0a-b1dc-0bd98f3abf3e">▶️</a> 9 - Texas Data Transport and MarkeTrak Systems TDTMS Sheri Wiegand</h2> <a href="https://dash2.gridmonitor.com/storage/docs/2024/12/09-tdtms_update_12_10_2024.pdf">09-tdtms_update_12_10_2024.pdf</a> <ul> <li style="font-weight: 400;" aria-level="1">SCR817, part of Texaset 5.0, was a success with significant training sessions in September and October.</li> <li style="font-weight: 400;" aria-level="1">Tammy Stewart from ERCOT led effective training sessions with attendance of 163 and 225 participants.</li> <li style="font-weight: 400;" aria-level="1">There were three market notices sent to help handle inadvertent gain workflows and manage market tracks.</li> <li style="font-weight: 400;" aria-level="1">Notable improvements in Find ESI and Find Transaction views enhancing user experience.</li> <li style="font-weight: 400;" aria-level="1">The inadvertent gain and switch holds remain significant market track categories.</li> <li style="font-weight: 400;" aria-level="1">Discussions around reducing noise in market tracks to enhance efficiency.</li> <li style="font-weight: 400;" aria-level="1">SCR817 introduced changes like AMS LSC Dispute and Meter Cycle Change Request market tracks, now seeing activity.</li> <li style="font-weight: 400;" aria-level="1">Rescissions and market trends data indicated Rep #4 submitted over 50% of rescission market tracks.</li> <li style="font-weight: 400;" aria-level="1">Focus on enhancing the market track tool to drive efficiencies and reduce noise.</li> <li style="font-weight: 400;" aria-level="1">Discussion on aligning with PUCT rules and examining impacts of these changes on data trends and market efficiency.</li> <li style="font-weight: 400;" aria-level="1">Next TDTMS meeting scheduled for January 4th with further discussions on subtypes and data analysis.</li> </ul> <h2><a href="/sharing/?token=fb049d8c-0b40-49b5-afc2-e8b6e6536b14">▶️</a> 10 - Texas Standard Electronic Transaction Texas SET Working Group Kyle Patrick</h2> <a href="https://dash2.gridmonitor.com/storage/docs/2024/12/10-texas-set-update-12_24.pdf">10-texas-set-update-12_24.pdf</a> <ul> <li style="font-weight: 400;" aria-level="1">Reviewed Texas SET 5.0 test, prepared for upcoming 0225 flight.</li> <li style="font-weight: 400;" aria-level="1">Focused discussion on addressing production issues related to Texas SET 5.0.</li> <li style="font-weight: 400;" aria-level="1">Emphasized the importance of collecting all production-related issues in a common space.</li> <li style="font-weight: 400;" aria-level="1">Highlighted need for education on EIA code usage.</li> <li style="font-weight: 400;" aria-level="1">ERCOT led successful cutover calls, ensuring a smooth transition.</li> <li style="font-weight: 400;" aria-level="1">Potential improvement areas include better communication and early provisioning of the test bed.</li> <li style="font-weight: 400;" aria-level="1">Discussion on test scripts ensuring optional elements are also tested.</li> <li style="font-weight: 400;" aria-level="1">Considered improving tracking systems like FlighTrak for future releases.</li> <li style="font-weight: 400;" aria-level="1">Acknowledged team's efforts and successful execution in 2023, with plans for potential elections in 2025.</li> </ul> <h2><a href="/sharing/?token=e6f5d847-0d1a-4d5a-8a2c-93730c2f073d">▶️</a> 11 - Market Coordination Team MCT Kathryn Thurman</h2> The Market Coordination Team reported a successful release, which is now in production. <ul> <li style="font-weight: 400;" aria-level="1">No actual presentation was given as previous speakers, Sherry and Kyle, covered all necessary details.</li> <li style="font-weight: 400;" aria-level="1">It is foreseen that the Market Coordination Team may be sunset in January.</li> <li style="font-weight: 400;" aria-level="1">This potential sunsetting will be noted on the January RMS agenda.</li> </ul> <h2><a href="/sharing/?token=f9a69508-de5b-402b-8550-0f60859832a2">▶️</a> 12 - Profiling Working Group PWG Steve Pliler</h2> <a href="https://dash2.gridmonitor.com/storage/docs/2024/12/12-pwg_update_12_10_2024.pdf">12-pwg_update_12_10_2024.pdf</a> <ul> <li style="font-weight: 400;" aria-level="1">The conversion of profile types is ongoing, with most converted but some like EPS meters are not feasible for conversion.</li> <li style="font-weight: 400;" aria-level="1">TNMP aims to complete their conversion by Q2.</li> <li style="font-weight: 400;" aria-level="1">Annual validation is a significant topic, with discussions heading towards a face-to-face meeting for moving forward.</li> <li style="font-weight: 400;" aria-level="1">Considerations include whether to tweak or completely overhaul the current approach and explore automation opportunities.</li> <li style="font-weight: 400;" aria-level="1">A Word format recreation of the profile decision tree was presented for review.</li> <li style="font-weight: 400;" aria-level="1">Concerns were raised about lost progress on annual validation and low profile updates, emphasizing the need for frequent meetings.</li> <li style="font-weight: 400;" aria-level="1">The cost implications of annual validation for ERCOT and market participants were discussed.</li> <li style="font-weight: 400;" aria-level="1">There's a push for more frequent and perhaps in-person meetings to facilitate progress.</li> </ul> <h2><a href="/sharing/?token=1aa35b97-571b-4127-ad84-86b3da93bf43">▶️</a> 13 - Retail Market Training Task Force RMTTF Tomas Fernandez</h2> <ul> <li style="font-weight: 400;" aria-level="1">RMTTF is working on training programs for next year, aiming to complete them by January.</li> <li style="font-weight: 400;" aria-level="1">Training packages will be finalized with ERCOT's assistance before release.</li> <li style="font-weight: 400;" aria-level="1">Tentative release is planned for the second and third quarters of next year.</li> <li style="font-weight: 400;" aria-level="1">Co-chairs for next year have been elected and are returning: Tomas Fernandez, Melinda, and Debbie.</li> <li style="font-weight: 400;" aria-level="1">Next meeting scheduled for January 9th on WebEx.</li> <li style="font-weight: 400;" aria-level="1">No specific questions were raised during the report.</li> </ul> <h2><a href="/sharing/?token=01a7e02b-b181-4b47-bcdf-44894e2101c0">▶️</a> 14 - Other Business John Schatz</h2> <ul> <li style="font-weight: 400;" aria-level="1">Highlight of achievements: Texas SET 5.0 project and Lubbock's integration into the retail market.</li> <li style="font-weight: 400;" aria-level="1">Acknowledgment of challenges faced, such as overcoming hurdles and hiccups.</li> <li style="font-weight: 400;" aria-level="1">Specific gratitude expressed to CenterPoint Energy and individuals like Jordan, Susie, and her team for their contributions.</li> <li style="font-weight: 400;" aria-level="1">Mention of coping with natural events like Hurricane Burlap and maintaining market operations.</li> <li style="font-weight: 400;" aria-level="1">Inquiry about the upcoming demand response report from ERCOT, expected by year's end.</li> <li style="font-weight: 400;" aria-level="1">Request for clarification on demand response reports: number of participants and actual demand response volumes.</li> <li style="font-weight: 400;" aria-level="1">Concluded with a closing of the 2024 edition of WMS.</li> </ul> <h2><a href="/sharing/?token=94faee71-06f5-4871-918e-1933c7b686ab">▶️</a> 15 - Adjourn John Schatz</h2>