A key action item involves updates and edits to the flight script workbook which were executed during a 'class session'. These edits were sent to Paul Yockey as agreed upon but faced pushback from some TDSPs not planning to use MSL.
Discussion around optional attributes in tests resulted in consensus to treat these attributes as optional during testing based on TDSP's production functionality.
Oncor raised concerns about making certain attributes mandatory, which were originally introduced as optional with the 5.0 system update.
Various stakeholders emphasized the importance of testing CR's functionality rather than TDSP functionality in environments where attributes are optional.
Discussions about reworking script language to reflect conditional use of optional attributes and address discrepancies.
Change control log reviews were conducted, with updates now reflected on relevant ERCOT websites, including MCT links.
Proposals for OBDRR amendments were discussed with tasks assigned for drafting and reviewing documents.
Action Items:
Reword current scripts to reflect conditional usage of optional attributes during testing.
Continue discussions between ERCOT and stakeholders about the practicalities of optional testing data across TDSPs.
Jordan Troublefield to work with Kathy Scott on finalizing OBDRR updates, incorporating market rules, and progressing towards PUCT approval.
Review and potentially integrate the TMTP document within the retail market guide.
Next Steps:
Stakeholders will refine and propose script language changes to accommodate optional testing attributes based on TDSP capabilities.
Once draft revisions are made, Kathy Scott and Jordan Troublefield will further discuss OBDRR progress and potential retail market guide implications.
Further explore SAC code utilization and documentation methods among utilities.
Connectivity testing started on 02/04/2025, with day one transactions beginning next Monday (02/24/2025). The flight is scheduled to conclude on March 7, with contingency concluding on March 14.
11 new CRs are testing, including four DUNS+4 CRs. 23 existing CRs are testing; 20 are for service provider change, two for adding territories, and one for adding CSA.
Discussion on whether the number of CRs testing for service provider change is unusually high.
Review of Flight Test Scripts Workbook changes made in previous meeting.
Discussion on the need for CRs to test three data elements for the PER-PO segment, with considerations on whether it's required or optional.
Clarification that the ERCOT system verifies at least one data element is populated, not all three, and no manual verification is feasible for each transaction.
Debate on the necessity of programming segments not used in production.
Decision to note usage of PER-PO and REF-MSL segments if CRs or TDSPs use them in production, using 'conditional' status.
Consideration of adding info on which TDSPs are using certain segments to help CRs plan better.
Request for confirmation from AEP and Lubbock on their use of segments.
Texas SET consensus on script updates, allowing for further nuances to be noted if needed.
Revision of the TMTP with a focus on Section 8.2 concerning out-of-flight testing.
Discussion centered around clarifying what constitutes an out-of-flight test, its timing, and whether certain periods, like December and January, should be blocked out for such tests.
Several participants expressed a need for clearer guidelines for out-of-flight tests, particularly the discretion given to utilities in handling these requests.
There was criticism about the phrasing of some guidelines, specifically relating to business day definitions and advanced notice requirements.
It was highlighted that significant testing, like bank changes, does not always need to go through formal flight tracking processes.
There is an acknowledgment of the challenges faced by TDSPs due to resource constraints during out-of-flight windows.
The possibility of establishing a subgroup to address changes in Section 8.2, especially regarding current timelines and requirements, was proposed.
Suggestions were made to conduct the overall document revision in person to facilitate better collaboration and ensure comprehensive updates.
Kathy Scott mentioned that Heather Fails has already started drafting language changes for Section 8.2, indicating ongoing work by the joint TDSPs.
A proposal for a future in-person meeting to collectively review and edit the TMTP document was discussed, aiming for wider participation and effective dialogue.
The March 11 meeting is likely to be canceled due to lack of significant agenda items and scheduling conflicts with spring breaks.
Potential next meeting dates discussed were in April, with a suggestion to have a sub-team meeting early in the month and a full working group meeting on April 22.
Other groups like PWG and TDTMS have also decided to cancel their March meetings and reschedule for April.
Consideration of coordinating with other events and holidays, like Easter and South by Southwest, was discussed to avoid conflicts.
There was agreement to cancel the March 11 meeting and focus on coordinating meetings around April 22.
Discussion on the feasibility of in-person meetings versus Webex due to logistics and preferences for less frequent in-person meetings.
The strategy involves pairing meetings in person each month, rather than all three groups meeting in person concurrently.
Coordination with leadership of other working groups is ongoing to schedule a meeting in early April.
Discussion about timing and necessity of testing, particularly concerns raised by Tyler about testing before the flight and balancing existing needs versus new ones.
Limited availability of test systems presents challenges; only one test system is currently being used.
