Speaker: Rob Bevil, TNMP Initially observed issues with validations in the power outage segment, including punctuation rules. However, these were resolved within a couple of weeks and no longer pose a problem.
Speaker: Kyle Patrick, NRG Discussion on whether the guide for the power outage segment was clear enough and acknowledged that initial confusion might have been caused by market circumstances and last-minute rulemaking.
Speaker: Sheri Wiegand, Vistra Reassured that the confusion around the power outage segment was not ongoing, and any initial errors have been resolved. Emphasized the importance of ensuring PCs (production change requests) remain hassle-free.
Speaker: Kathy Scott, CNP Noticed challenges with backdated move-ins and IA/CR indicators but clarified that these issues were isolated and not market-wide, suggesting they resulted from overlooked development considerations.
Speaker: Various Utilities Utilities including Centerpoint Energy, Oncor, and AEP confirm that the IA/CR code processes are functioning well as anticipated, and there are no significant systematic issues.
Speaker: Kyle & Sheri Agreed that RMTTF will address any confusion in training with revisions accommodating Texas SET 5.0 and SCR817 changes, ensuring clarity on transaction rejects and the encouragement for using IA codes.
Speaker: Kathryn Thurman, ERCOT Provided insights on the volume of IA and CR transactions in recent weeks, which are being tracked for alignment with historical averages.
Speaker: Stephen Wilson, Vistra ERCOT's reject numbers have stabilized, and producers are encouraged to continually check mapping statuses to avoid transaction issues with customers.
Speaker: Kyle Patrick, NRG Changes in the MIS interface were unexpected and came as a surprise, resulting in some confusion. There is ongoing discussion regarding feedback and potential adjustments.
TDSP and CR need to clarify if they are unable to support specific segments in testing ahead of time, possibly by obtaining waivers, if they aren’t going to send specified codes as a required prescription.
Scripts should clearly indicate optional segments to avoid confusion during testing.
Numerous rejections occurred in production due to failure in testing optional fields correctly.
Recommendation to revisit and possibly update the scripts used for testing to ensure clarity on optional fields.
Importance of having a test environment as close to production as possible was emphasized.
Observations that FlighTrak, while useful, isn't specifically designed for SET release testing and has room for improvement.
Need for tools and environments that facilitate additional testing outside of standard scripts.
Desire for more advanced access to test beds to better prepare for testing phases.
Consideration for a more coordinated communication process, such as a day-one call during large-scale testing, to quickly address issues or updates.
Suggestions to revisit the scripts prior to the next flight and make necessary updates post-February flight.
Discussion on the use of FlighTrak and ways to improve its accessibility and functionality for new and infrequent users.
Emphasized the need for users to refer to the available user guide for better navigation of FlightTrack.
