Frame

Meeting Summary - 08/14/24 RTCBTF Meeting

Grid Monitor AI
08/16/2024

1 - Antitrust Admonition <a href="/sharing/?token=8a8c37e4-a00e-4d50-95df-41d2e27e6d1f">2</a> - RTCBTF Update and Issues Matt Mereness <ul> <li style="font-weight: 400;" aria-level="1"><a href="https://ercot-control-docs.s3.us-west-2.amazonaws.com/07/1_RTCBTF_Update_08142024.pptx">RTC+B program update</a></li> <li style="font-weight: 400;" aria-level="1">Current focus is on development, training, market trials, and sequencing to go live.</li> <li style="font-weight: 400;" aria-level="1">Plan to announce a go-live date by September</li> <li style="font-weight: 400;" aria-level="1">Expected at the end of 2025 at the earliest </li> <li style="font-weight: 400;" aria-level="1">Efforts are being made to avoid extending into 2026</li> </ul> <a href="/sharing/?token=17505d0e-40ef-4ade-b403-fe9120ac0283">2.1</a> - Re-aligning Issues List at Sept Meeting <ul> <li style="font-weight: 400;" aria-level="1">Discussed the development of the go-live sequence for the program in the next few weeks.</li> <li style="font-weight: 400;" aria-level="1">Integrated market readiness into the development plan, focusing on timelines, milestones, and deadlines for issue resolution.</li> <li style="font-weight: 400;" aria-level="1">Identified a need to prioritize policy-driven changes that may take up to six months.</li> <li style="font-weight: 400;" aria-level="1">Targeted mid-2025 for the initiation of market trials.</li> <li style="font-weight: 400;" aria-level="1">Flagged that the discussion on AS proxy offers was not ready for today but planned for the next meeting.</li> <li style="font-weight: 400;" aria-level="1">Focused on market readiness and settlements, leaving room for information on demand curves.</li> <li style="font-weight: 400;" aria-level="1">Planned a culling process to streamline and prioritize the issues list, currently containing about 20 items.</li> <li style="font-weight: 400;" aria-level="1">Developed clarifying NPRRs including a singular RTC (Real-Time Co-optimization) NPRR to capture baseline developments since 2019 and identify gaps found during business requirements.</li> <li style="font-weight: 400;" aria-level="1">Shared initial drafts of the NPRR revisions last month, filed with numbers and provided links.</li> <li style="font-weight: 400;" aria-level="1">Scheduled to review the NPRR revisions in the next two to three meetings.</li> </ul> <a href="/sharing/?token=87b54689-407c-4cdb-8ce2-9153d4f9e677">2.2</a> - Scope of RTC+B Program <ul> <li style="font-weight: 400;" aria-level="1">Introduced the RTC+B program for understanding and development in future meetings.</li> <li style="font-weight: 400;" aria-level="1">Key foundational documents include NPRR1007 through 1013 set in 2019-2020 and supporting documents like operating guide revisions and binding OBDR.</li> <li style="font-weight: 400;" aria-level="1">NPRR1204 involves state of charge, 1236 deals with RUC capacity short, and various clarifying NPRRs were discussed.</li> <li style="font-weight: 400;" aria-level="1">NPRR1000 related to Dynamically Scheduled Resources is being formally deleted to save testing time.</li> <li style="font-weight: 400;" aria-level="1">NPRR1054 removes the Oklaunion exemption settlement calculations transparently.</li> <li style="font-weight: 400;" aria-level="1">NPRR1172 includes changes to the RUC clawback.</li> <li style="font-weight: 400;" aria-level="1">Implementing sections of NPRR963 that overlap with NPRR1014 for 1014 to work fully, creating an interdependency.</li> <li style="font-weight: 400;" aria-level="1">NPRR1058 enables QSEs to update energy offer curves in real-time, going live next week.</li> <li style="font-weight: 400;" aria-level="1">Training for RTC+B is planned but not outlined; feedback on critical pieces is welcomed for a future update.</li> <li style="font-weight: 400;" aria-level="1">Specifics of RTC+B training are to be developed in the next few weeks. Update will be provided in next month’s meeting.</li> <li style="font-weight: 400;" aria-level="1">Clarification on whether the listed NPRRs are exhaustive for the RTC+B scope: Current list is what is known now, but updates will continue as necessary. ERCOT aims to minimize market changes to accommodate this scope. </li> </ul> Questions and Answers: Participant: Bill Barnes Question: Inquiry about the development and availability of an RTC+B training program for market participants. Response: Training is part of the project, with specifics to be anchored in the next few weeks. A detailed update on training will be provided in next month’s meeting. Participant: Chris Espinosa Question: Clarification on whether the listed NPRRs are exhaustive for the RTC+B scope. Response: Current list is what is known now, but updates will continue as necessary. ERCOT aims to minimize market changes to accommodate this scope. Next Steps: Discussion on NPRRs, simulator update, market submissions, market readiness, and the agenda for the next meeting in September. <a href="/sharing/?token=cba01c52-9597-4e31-81d8-9877172cb3ff">3</a> - Review RTC and ESR Clarifying Revision Requests for Market Questions Dave Maggio/Kenneth Ragsdale <ul> <li style="font-weight: 400;" aria-level="1">Discussion on revision requests for NPRR1245 and single model changes.</li> <li style="font-weight: 400;" aria-level="1">A niche topic related to settlements was identified and presented for NPRR1245.</li> </ul> <a href="/sharing/?token=96c820a4-c63f-48b4-881e-2e317b4765ec">3.1</a> - RTC- NPRR1245 <ul> <li style="font-weight: 400;" aria-level="1">Magie Shanks presented the DAM Omission Settlement <a href="https://ercot-control-docs.s3.us-west-2.amazonaws.com/08/3_DAM%2520Omission%2520Settlement_081424.pptx">update</a></li> <li style="font-weight: 400;" aria-level="1">While reviewing NPRR1245, an additional necessary edit was discovered.</li> <li style="font-weight: 400;" aria-level="1">In section 9.14.10, settlement procedures need to include real-time market clearing prices.</li> <li style="font-weight: 400;" aria-level="1">Current language assumes awards for AS are only physical, ignoring real-time reallocations.</li> <li style="font-weight: 400;" aria-level="1">Propose changes to settlement section to align with real-time market operations.</li> <li style="font-weight: 400;" aria-level="1">Changes will be submitted as comments for consideration at the September PRS.</li> <li style="font-weight: 400;" aria-level="1">Presentation included current workflow and proposed changes for ancillary services.</li> <li style="font-weight: 400;" aria-level="1">New proposal aligns price calculations between day-ahead and real-time markets.</li> </ul> <a href="/sharing/?token=7e8c23f1-1943-475c-b86c-2abc42069399">4</a> - Issue 3 - RTC Simulator Update verbal update only Raymund Lee <ul> <li style="font-weight: 400;" aria-level="1">Raymund Lee provided a quick update on the RTC SCED production scale tool.</li> <li style="font-weight: 400;" aria-level="1">System-wide limits (RSUF, RSFF, ECRSM) have been formulated.</li> <li style="font-weight: 400;" aria-level="1">Implemented logic for NCLRs to self-provide ancillary services, including validation logic.</li> <li style="font-weight: 400;" aria-level="1">Core formulation of the problem completed for the first phase.</li> <li style="font-weight: 400;" aria-level="1">Development done using small test cases; large scale testing and validation are upcoming.</li> <li style="font-weight: 400;" aria-level="1">Intern Luke Gutierrez created a visualization application for tool outputs.</li> <li style="font-weight: 400;" aria-level="1">The next steps include testing and validation on larger cases and resolving bugs.</li> <li style="font-weight: 400;" aria-level="1">Last meeting discussed the original slides for the simulator scope, confirming it as an ERCOT in-house tool to use ERCOT databases and rerun historical system solutions via RTC.</li> <li style="font-weight: 400;" aria-level="1">RTC task force has provided operating days for simulation runs; next phase involves running sample cases and presenting them back to the group.</li> </ul> <a href="/sharing/?token=65353b2a-4bcf-47c4-8421-81f02ff11afc">5</a> - Issue 9 - Explanation of Market Submission Interface Changes Nathan Smith <ul> <li style="font-weight: 400;" aria-level="1">Nathan Smith presented the <a href="https://ercot-control-docs.s3.us-west-2.amazonaws.com/07/Issue%25209-%2520RTC%2520B%2520Market%2520Submissions%2520Changes%2520slides.pptx">RTC+B Market Submission Changes</a> </li> <li style="font-weight: 400;" aria-level="1">Discussion on moving from "AS responsibility" to "AS capability" to represent a resource's total AS capacity available by AS type.  Changes in COP allowing negative values for ESRs to account for charging and discharging states.</li> <li style="font-weight: 400;" aria-level="1">Explanation of new "AS only offers" for the day-ahead market.</li> </ul> <img src="/storage/docs/2024/08/8.14%20RTBTF%201.png" width="594" height="448" /> <ul> <li style="font-weight: 400;" aria-level="1">Introduction of ESR energy bid offer curve for RTC+B, DAM, RUC, and SCED, allowing negative megawatt quantities for charging states.</li> <li style="font-weight: 400;" aria-level="1">Detailed discussion on resource-specific as offers and their applications in DAM, SASM, RUC, and SCED.</li> <li style="font-weight: 400;" aria-level="1">Modifications to the market manager submission UI, including new sub-tabs and drop-down options for DAMs.</li> <li style="font-weight: 400;" aria-level="1">Addition of three new parameters for ESRs: minimum state of charge, max state of charge, and round trip efficiency.</li> <li style="font-weight: 400;" aria-level="1">Changes to reports: removal of DAM AS insufficiency report and the SASM reports</li> <li style="font-weight: 400;" aria-level="1">Replacing DAM AS obligation with DAM Advisory AS Obligations. Adding DAM Final AS obligations report and DAM AS-only Offer Awards report</li> </ul> <img src="/storage/docs/2024/08/8.14%20RTBTF%202.png" width="594" height="446" /> <ul> <li style="font-weight: 400;" aria-level="1">Discussion on training needs: preference for modular training units with voice-over narration over comprehensive all-day events.</li> <li style="font-weight: 400;" aria-level="1">Suggestion to incorporate a bulletin board or FAQ system for addressing participant questions asynchronously.</li> </ul> 6 - Issue 10 - Market Readiness Matt Mereness <a href="/sharing/?token=492c83fe-5088-49c9-a622-f499e3fb97d2">6.1</a> - Final Review of Market Trials Plan <ul> <li style="font-weight: 400;" aria-level="1">Market Trials and Transition Planning <a href="https://ercot-control-docs.s3.us-west-2.amazonaws.com/14/Issue%25209_RTCB%2520Market%2520Trials%2520Plan_ERCOT_Redlines_071624%2520luminant.docx">Document</a></li> <li style="font-weight: 400;" aria-level="1">Matt Mereness explained market submissions and system setup timelines, including the planned go-live in May 2025.</li> <li style="font-weight: 400;" aria-level="1">July-August will involve SCED testing and telemetry checkout.</li> <li style="font-weight: 400;" aria-level="1">Control room tests will simulate real dispatch scenarios for 2 to 4 hours.</li> <li style="font-weight: 400;" aria-level="1">Luminant provided comments and noted the need for short technical workshops at each phase.</li> <li style="font-weight: 400;" aria-level="1">Clarifications on QSE attestation and request for at least ten business days advance notice for open or closed loop tests were discussed.</li> <li style="font-weight: 400;" aria-level="1">Discussion included avoiding settlement impacts during closed loop tests and allowing QSEs to test their systems during such tests.</li> <li style="font-weight: 400;" aria-level="1">Comments from Luminant suggested the need for more detailed internal testing, especially related to non-spin reserves.</li> <li style="font-weight: 400;" aria-level="1">ERCOT explained that closed loop tests aim to ensure reliability without financial settlements, suggesting disputes could be raised if financially harmed.</li> <li style="font-weight: 400;" aria-level="1">Monica Jha from Vistra expressed concerns about testing non-spin reserves during closed loop testing.</li> <li style="font-weight: 400;" aria-level="1">Dave Maggio from ERCOT clarified concerns and suggested further offline discussions to address them.</li> <li style="font-weight: 400;" aria-level="1">It was noted that QSE-specific functionalities might need separate testing closer to go-live.</li> </ul> <a href="/sharing/?token=39250785-7de5-4b7a-ba28-4dd0d9635e25">6.2</a> - Attestation <a href="https://ercot-control-docs.s3.us-west-2.amazonaws.com/14/RTC_QSE_Attestation_08142024.xlsx">Scorecard</a> going to Board <ul> <li style="font-weight: 400;" aria-level="1">Three main points of attestation:</li> <ul> <li style="font-weight: 400;" aria-level="2">Identify accountable executive.</li> <li style="font-weight: 400;" aria-level="2">Acknowledge ERCOT's interface specifications as of June 29, 2024.</li> <li style="font-weight: 400;" aria-level="2">Acknowledge goal to prepare for market trials as early as May 2025.</li> </ul> <li style="font-weight: 400;" aria-level="1">Intent was to gauge awareness of deadlines, not to commit to readiness</li> <li style="font-weight: 400;" aria-level="1">Scorecard status: Out of 106 entries, only one company (LCRA) is missing.</li> <li style="font-weight: 400;" aria-level="1">Yellow status for some in-progress PCs lacking resources but will need to build for both current and RTC systems.</li> <li style="font-weight: 400;" aria-level="1">LCRA flagged for modifying attestations, specifically omitting engagement for May 2025 market trials due to uncertainty.</li> <li style="font-weight: 400;" aria-level="1">Purpose of attestation emphasized as market readiness awareness.</li> <li style="font-weight: 400;" aria-level="1">Update on EMIL-related reports: New data products will be added and modifications shown in a report inventory.</li> <li style="font-weight: 400;" aria-level="1">Approximately 50 reports will be added, modified, or deleted.</li> </ul> 7 - Issue 18 - Placeholder for MPs Discussion of AS Demand Curves <ul> <li style="font-weight: 400;" aria-level="1">AS Demand Curves not discussed</li> </ul> <a href="/sharing/?token=624cc079-5ef5-4efb-ac43-164ad097ff3e">7.1</a> - Indifference Payment Required under RTC to avoid Incentive Incompatibility - Shams Siddiqi <ul> <li style="font-weight: 400;" aria-level="1">Shams Siddiqi introduced the issue of <a href="https://ercot-control-docs.s3.us-west-2.amazonaws.com/14/Indifference%2520Payment%2520under%2520RTC%2520081424.pptx">indifference payment</a> related to RTC design, initially thought to be resolved through NPRR1214.</li> <li style="font-weight: 400;" aria-level="1">RTC doesn't provide indifference payment related to Reliability Deployment Price Adder (RDPA) causing incentive incompatibility for resources.</li> <li style="font-weight: 400;" aria-level="1">Resources might chase higher RDPA prices instead of following their base points, leading to reliability concerns.</li> <li style="font-weight: 400;" aria-level="1">Currently, all resources with available capacity are paid the real-time RDPA ancillary service imbalance amount, creating unnecessary large payments.</li> <li style="font-weight: 400;" aria-level="1">Proposed indifference payment based on 0.5*ΔLMP*ΔMW between pricing run and dispatch run deltas to reduce incentives to chase prices</li> <li style="font-weight: 400;" aria-level="1">Implementation of NPRR1214 is suggested to be in phases, starting with a grid-wide indifference payment, then introducing locational price signals.</li> <li style="font-weight: 400;" aria-level="1">Recommends a further refinement to address AS award differences between the SCED pricing run and dispatch run</li> <li style="font-weight: 400;" aria-level="1">In their latest NPRR1214 comments, ERCOT proposed deferring the consideration of NPRR1214 until after RTC implementation, raising concerns about potential severe scarcity events.</li> <li style="font-weight: 400;" aria-level="1">Discussion included the need for tools to simulate RDPA price adders and look at the risk of not addressing the indifference payment issue.</li> <li style="font-weight: 400;" aria-level="1">Hunt Energy Network recommends pursuing NPRR1214 to implement the indifference payment with RTC implementation, or pursuing a new urgent NPRR to do the same.</li> </ul> <a href="/sharing/?token=d164e75f-4984-4a39-a778-694384130cc1">8</a> - Heads-up on Topics for September RTCBTF Meeting Matt Mereness <ul> <li style="font-weight: 400;" aria-level="1">Topics for September meeting include</li> <ul> <li style="font-weight: 400;" aria-level="2">Consolidation of list of issues to prioritize most important issues.</li> <li style="font-weight: 400;" aria-level="2">Further discussion of the scope of the RTC program.</li> <li style="font-weight: 400;" aria-level="2">Update on simulator.</li> <li style="font-weight: 400;" aria-level="2">Addressing the load frequency control tests during the market trails plan.</li> <li style="font-weight: 400;" aria-level="2">Development of RTC+B training</li> <li style="font-weight: 400;" aria-level="2">AS demand curves, which may potentially be discussed at board meeting next week</li> <li style="font-weight: 400;" aria-level="2">AS proxy parameters addressing how to set proxy offer prices</li> </ul> <li style="font-weight: 400;" aria-level="1">Planned a detailed process involving multiple meetings for setting proxy offer prices.</li> <li style="font-weight: 400;" aria-level="1">Sought feedback on data or analysis needed to inform proxy offer prices.</li> <li style="font-weight: 400;" aria-level="1">Education on the proxy process and its complexities planned.</li> <li style="font-weight: 400;" aria-level="1">Addressed clarifications and questions from attendees regarding proxy offers and related protocols.</li> </ul> 9 - Issue 8- Mapping of Bill Determinants to Extracts and Reporting for developing Shadow Settlement Magie Shanks <ul> <li style="font-weight: 400;" aria-level="1">Main goal is to outline the settlement changes under RTC+B.</li> </ul> <a href="/sharing/?token=ef0ea442-3449-4f28-b634-590fd15f1829">9.1</a> - Settlements and Billing Deep-Dive <a href="https://ercot-control-docs.s3.us-west-2.amazonaws.com/08/Issue%25208%2520-%2520RTC%2520B%2520Settlement%2520Overview.pptx">Settlement Changes Overview</a>: <ul> <li style="font-weight: 400;" aria-level="1">NPRRs Included in RTC+B Project:</li> <ul> <li style="font-weight: 400;" aria-level="2">NPRR1007-1013: Related to RTC implementation.</li> <li style="font-weight: 400;" aria-level="2">NPRR1014: Covers Single Model ESR.</li> <li style="font-weight: 400;" aria-level="2">NPRR1029: Focuses on Market Suspension for ESRs.</li> <li style="font-weight: 400;" aria-level="2">NPRR963: Addresses Set Point Deviation for ESRs, baseline for NPRR1014.</li> <li style="font-weight: 400;" aria-level="2">NPRR1054: Removes Oklaunion Exemption; cleans up Settlement System.</li> <li style="font-weight: 400;" aria-level="2">NPRR1172: Cleans up RUC Clawback Settlement.</li> <li style="font-weight: 400;" aria-level="2">NPRR1000: Eliminates Dynamically Scheduled Resources (DSR).</li> <li style="font-weight: 400;" aria-level="2">NPRR1236: RUC State of Charge considerations.</li> <li style="font-weight: 400;" aria-level="2">NPRR1245 & 1246: Clean-up NPRRs for RTC and ESR.</li> </ul> </ul> Day-Ahead Market (DAM) Changes: <ul> <li style="font-weight: 400;" aria-level="1">Day-Ahead Make-Whole Payment:</li> <ul> <li style="font-weight: 400;" aria-level="2">ESRs excluded from receiving these payments.</li> </ul> <li style="font-weight: 400;" aria-level="1">Day-Ahead Ancillary Service Payment & Charge:</li> <ul> <li style="font-weight: 400;" aria-level="2">New charge type for Ancillary Service Only Offers in DAM Settlement Statement.</li> </ul> <li style="font-weight: 400;" aria-level="1">Day-Ahead Congestion Revenue Rights:</li> <ul> <li style="font-weight: 400;" aria-level="2">New category for ESRs in pricing for settlement points.</li> </ul> </ul> Cost and Pricing Changes: <ul> <li style="font-weight: 400;" aria-level="1">Energy Offer Curve Cost Caps:</li> <ul> <li style="font-weight: 400;" aria-level="2">New category for ESRs, affecting DAM and Real-Time Market (RTM) settlements.</li> <li style="font-weight: 400;" aria-level="2">ESRs excluded from DAAIEC, impacting Make-Whole Payments.</li> </ul> </ul> Real-Time Market (RTM) Changes: <ul> <li style="font-weight: 400;" aria-level="1">Real-Time HDLO Energy Payment:</li> <ul> <li style="font-weight: 400;" aria-level="2">ESRs qualify for payment if directed to reduce power.</li> </ul> <li style="font-weight: 400;" aria-level="1">Set-Point Deviation:</li> <ul> <li style="font-weight: 400;" aria-level="2">Renamed from Base-Point Deviation; ESR-specific calculations for over/under performance.</li> </ul> <li style="font-weight: 400;" aria-level="1">Voltage Support Service Payments:</li> <ul> <li style="font-weight: 400;" aria-level="2">Updates include ESRs, with new intermediate calculations for ESRs.</li> </ul> <li style="font-weight: 400;" aria-level="1">Emergency Operations Payment:</li> <ul> <li style="font-weight: 400;" aria-level="2">Includes ESRs, adjusting for their charging side in emergency events.</li> </ul> <li style="font-weight: 400;" aria-level="1">Switchable Generation Make-Whole Payment:</li> <ul> <li style="font-weight: 400;" aria-level="2">Updated to include RT Ancillary Service (AS) Revenues.</li> </ul> <li style="font-weight: 400;" aria-level="1">Real-Time Ancillary Service Settlement:</li> <ul> <li style="font-weight: 400;" aria-level="2">New charges and payments based on AS Imbalance, AS Only Offers, and AS Trade Overages.</li> </ul> <li style="font-weight: 400;" aria-level="1">Real-Time Derated AS Capability Charge:</li> <ul> <li style="font-weight: 400;" aria-level="2">New charge type allocated on LRS basis for RT Derated payments.</li> </ul> </ul> Market Suspension and RUC Changes: <ul> <li style="font-weight: 400;" aria-level="1">Market Suspension Payment:</li> <ul> <li style="font-weight: 400;" aria-level="2">Includes ESR considerations, allowing submission of actual O&M rates.</li> </ul> <li style="font-weight: 400;" aria-level="1">Market Suspension Charge:</li> <ul> <li style="font-weight: 400;" aria-level="2">ESR load removed from LRS allocation for Market Suspension Charges.</li> </ul> <li style="font-weight: 400;" aria-level="1">RUC Make-Whole Payments and Clawback Charges:</li> <ul> <li style="font-weight: 400;" aria-level="2">ESRs excluded from RUCMW payments and RUC Clawback Charges.</li> <li style="font-weight: 400;" aria-level="2">Includes RT AS revenues in RUC Guarantee calculations.</li> </ul> <li style="font-weight: 400;" aria-level="1">RUC Decommitment Payment:</li> <ul> <li style="font-weight: 400;" aria-level="2">ESRs excluded from related Clawback Charges.</li> </ul> <li style="font-weight: 400;" aria-level="1">RUC Capacity Short:</li> <ul> <li style="font-weight: 400;" aria-level="2">ESRs included in QSE’s capacity calculation and shortfall determination.</li> </ul> </ul> Settlement Statements and Miscellaneous Invoices: <ul> <li style="font-weight: 400;" aria-level="1">Some charges related to DAM omissions will appear on miscellaneous invoices rather than on settlement statements.</li> <li style="font-weight: 400;" aria-level="1">No structural changes will be made to settlement statements; however, new or removed line items will be added.</li> <li style="font-weight: 400;" aria-level="1">Extracts will remain the same, but they will reflect new or removed bill determinants.</li> </ul> Handling of Removed Settlement Charges: <ul> <li style="font-weight: 400;" aria-level="1">Removed settlement charges will still appear on statements for final or true-up settlements, but new charge types will be updated for new operating days.</li> </ul> ESR Price Categories: <ul> <li style="font-weight: 400;" aria-level="1">ESRs previously included under the “Other” category are now assigned their own category, maintaining the same minimum and maximum prices (negative $20 and $100, respectively).</li> <li style="font-weight: 400;" aria-level="1">Any changes to these prices would require a new NPRR.</li> </ul> Settlement Changes for RTC and Non-RTC Related NPRRs: <ul> <li style="font-weight: 400;" aria-level="1">NPRRs not directly related to RTC or ESR will still be bundled and released with the RTC project.</li> <li style="font-weight: 400;" aria-level="1">Market trials are built to the current scope, and any new NPRRs impacting RTC will be adapted as needed.</li> </ul> Market Trials and Settlement Data: <ul> <li style="font-weight: 400;" aria-level="1">Settlement changes will go live with the RTC+B project, not during market trials, as shadow settlements won't be visible during trials.</li> <li style="font-weight: 400;" aria-level="1">There is a plan to release generic, non-QSE-specific settlement data at the beginning of next year to help market participants understand the impact of the changes.</li> </ul> Clarifications on Settlement and NPRR Errors: <ul> <li style="font-weight: 400;" aria-level="1">Future NPRRs flagged in the issues list are intended to correct errors in the language, not to change the functionality.</li> <li style="font-weight: 400;" aria-level="1">Generic statements and extracts will be shared with market participants to illustrate what post-RTC settlement artifacts will look like.</li> </ul> 10 - Adjourn