Meeting Summary - 01/14/2025 Texas SET Meeting

▶️ 1 - Antitrust Admonition

▶️ 2 - Election

▶️ 2.1 - Chair

• Nominee for the 2025 Texas set chair is Kyle Patrick.
• Kyle Patrick accepts the nomination.
• Opportunity offered for alternative candidates, none put forth.
• Kyle Patrick confirmed as chair for 2025.

▶️ 2.2 - Vice Chairs

• Nominations for co-vice chairs were discussed.
• Stephen Wilson and Monica Jones were nominated for the two positions.
• Both Stephen Wilson and Monica Jones accepted the nominations.
• No alternative nominations were proposed.
• Stephen Wilson and Monica Jones were congratulated on their roles as co-chairs for the year.

▶️ 3 - Introductions/Agenda Review

• Plan to manage time effectively due to overlapping meetings (TDTMS).

▶️ 4 - ERCOT Updates

▶️ 4.1 - Flight 0225

• Market notice was originally sent on December 4th.
• Final reminder notice to be sent on January 22nd.
• Application deadline for the flight is tomorrow (January 15th).
• Sign up deadline is January 29th.
• Activity begins on February 4th.
• Transactions are scheduled to begin on February 24th.
• Flight is scheduled to conclude on March 7th.
• Contingency period ends on March 14th.
• As of yesterday (January 13th) at 10 AM, 2 new CRs and 8 existing CRs have registered for the flight.
• More applications from new CRs are expected.
• Update on registrations will be provided at the next meeting.

▶️ 5 - Open Issues

▶️ 5.1 - TXSET150 Issue

• Reviewed use of the A13 reject code.
• Concerns about the manual review required when the A13 code is received.
• Potential for more efficient processing with an optical reject code.
• Implementation of TXSET 5.0 introduced new reject codes, resolving the issue.
• Discussion on updating the key document with the resolution.
• Agreement to close the issue with TXSET 5.0 implementation.

▶️ 5.2 - TXSET149 Issue

• TXSET149 raised issues that were scheduled for revision in 2020.
• The speaker acknowledged being responsible for some initial aggressive recommendations.
• Desired outcome was to revise the current CSA validation process and request Texas SET review, but a suggestion would be for MVO process to be separated from CSA CR switch
• Suggestion to rework language to suggest that CSA process improvements with Texas SET 5.0 makes original recommendations unnecessary.
• Agreement that while the original requested resolution was not implemented, a satisfactory solution was achieved.
• Acknowledgement to mark the issue as addressed and resolved.

▶️ 6 - TEXAS SET 5.0 Discussion

▶️ 6.1 - Testing/Scripts

• There was a discussion about ensuring mandatory data elements are explicit and present in the EDI.
• The optional data fields not being tested in scripts was highlighted; they need to be tested to ensure correct interpretation by receivers.
• Testing all optional data in a test environment is crucial to prevent failures in production.
• Specific mention of problems with the power outage data element and similar issues in production.
• Discussion emphasized that supposedly optional fields like IA and CR, as well as REF-MSL, should be required in testing to prevent inconsistencies.
• Debate on whether all scripts should have the same success criteria or if focus should be on the IBANK script.
• Understanding was that IBANK will be the forward-going script for new entrants and could be modified as necessary.
• Testing for all data elements within PER-PO, including phone number and email, was deemed necessary to identify potential issues.
• Suggestions were made to add notes in scripts for clarity, stating that all elements are required for testing but optional in production.
• Future modifications to FlighTrak were discussed and an understanding was reached to aim for implementation in the June flight.
• There was a consensus to modify the IBANK script and extend the changes to applicable sections for consistent testing, noting that this will not apply to the current flight cycle.

▶️ 6.2 - Production Issues

• Some discussion on startups and the usage of IAs and CRs as they are expected to function smoothly.
• Kathryn Thurman’s initiative as Market Coordination Team (MCT) lead was recognized for her leadership, and the MCT has been sunsetted.
• SET is responsible for addressing production problems. Matters that are not urgent will be part of ongoing discussions for future enhancements.
• Rob Bevill raised a question about the archival of documents from the MCT page; it was clarified that documents will remain in place, but the MCT is now inactive.
• The group discussed ways to simplify access to documents for new members by reducing navigation steps.
• Kathy had an information-related query but not a production issue. She later provided guidance on accessing the Texas SET and updating the change control log as it was incomplete.
• Shannon Carter mentioned that any production issues have been resolved with the respective market partners, and global issues would likely have been identified by now.
• Discussion on production issues wrapped up with no further urgent matters identified.

▶️ 6.3 - FlighTrak

Discussion on FlighTrak needed to be covered, focusing on two separate conversations: general FlighTrak and FlighTrak guide for auto flight testing.

• Carrie Bivens requested additional discussion on documenting and defining out-of-flight testing scenarios, highlighting the lack of detailed existing documentation.
• The TMTP was mentioned, with suggestions to include more requirements from TDSPs and ERCOT in the documentation.
• Potential revisiting of requirements needed for bank changes and various scenarios, such as service providers exiting the market, was discussed.

▶️ 6.4 - TMTP

• Discussion on the need for market participants to coordinate out of flight testing with 10 business days notice.
• Conversation on updating TMTP documentation for various scenarios.
• Need for more detailed requirements for TDSP processes.
• Mention of testing scenarios such as system failures, disaster recovery, and cybersecurity.
• Historical context of flexible testing methodologies since 2019.
• Plan to revisit TMTP section 8.2 and other related sections.
• Discussion on improving the FlighTrak tool.
• Concerns about FlighTrak's performance during a major release.
• Necessity for possible updates to FlighTrak and cost considerations.
• Consideration of staggered start dates for easing system loads.
• Training and participant engagement before go-live emphasized as crucial.
• Ideas included dress rehearsals and semi-formalized processes for testing before official flights.
• Retail Market Test Environment (RMTE) availability for ongoing testing highlighted.
• Challenges with disengaged participants creating bottlenecks in testing processes.
• Suggestion of mandatory pretesting to address issues with unengaged participants.
• Call for a coordinated effort to use RMTE more effectively.

▶️ 7 - Other Business

• Kathy Scott Discusses a draft ODBRR for TDSP(s) Production Pre-Verification Testing.
• Discussion on issues related to DUNS+4 assignments and potential risks due to lack of recent testing before moving to production.
• Concerns raised regarding DUNS waiting too long on the shelf before being activated could lead to unforeseen issues.
• Interest in developing language to allow flexibility for TDSPs to require additional pre-production verification testing.
• Consideration of possible inclusion of requirements in revised TMTP documentation and approval process.
• Discussion on handling timelines and notification processes for transitioning DUNS+4 into production.
• A suggestion to potentially move OBDRR language into the retail market guide to streamline processes.
• Raised awareness of other change controls for clarity and reconciliation in transactions.

▶️ 8 - Goals and Accomplishments

• Maintain boilerplate goals for 2025, including updating procedures, supporting review changes for TMTP, analyzing issues, and monitoring testing.
• Remove redundant elements; specifically, remove 'for a release' to simplify goals around supporting Texas SET 5.0.
• Monitor mass transition preparedness testing with discussion anticipated.
• Accomplishments included reviewing and crediting change controls, addressing two RMGRRS, and all flights—specifically Flight 1025.
• Itemize accomplishments related to orientation, training, and collaboration on training sessions.
• Discussed the need to monitor go-live activities across applications.
• Consider possible in-person meetings; suggested virtual meetings for Jan 18th and 19th, with potential in-person starting in April.
• Potentially have back-to-back meetings with TDTMS for logistics ease.
• Consideration of travel schedules and co-locating meetings with PWG, TDTMS, and SET for convenience.
• Ensure there's no overlap with local events like South by Southwest when planning in-person meetings.
• Plan to distribute a draft of accomplishments and goals to team members for reviews and additions.

▶️ 9 - Adjourn