Update on the script pack to be posted on Thursday for the 0625 flight, taking into account the IOU script since Nueces did not want changes for the MOU.
Flight 0625 is expected to be light with current applications; only six have started or completed registrations, including new and existing CR changes.
The script update will be posted to the ERCOT website after successful testing, expected by Thursday or Friday.
Minimal changes to the script instructions mainly affect IBANK 01 scripts regarding conditional use for TDSPs and power outage segments.
TDSPs using the MSL segment currently limited to CenterPoint and TNMP.
Discussion on ensuring new representatives can identify script requirements easily.
One abstention from OPEC consumer segment. Misunderstanding is likely the reason for abstention. No significant opposition. Passed successfully.
TXSETCC852 – Clarifications of Friday Disconnect for Non-Payments
One abstention on TXSETCC852 due to disagreement with disconnecting customers for nonpayment in general. Not specific to the day of the week. Passed successfully.
Both change controls were approved despite individual abstentions.
Changes to section 8.2 were proposed for clarity on procedures regarding out-of-flight testing requests.
The need for a ten-day notice period was highlighted to coordinate the out-of-flight testing with market participants rather than stating a hard date.
There was a discussion about ensuring the ten-day notice is clear and not confused with the switch date notice.
Clarification was sought on whether changes should be communicated before system changes and to coordinate with all market participants.
Section 8.2 addresses territory, bank, and EDI provider changes but does not apply to NAESB system changes.
Comments were made on concerns with section 8.2.1 about adding new territory during out-of-flight tests indicating that it might be more suitable during flight testing.
Service provider and bank changes were noted as typically allowed for out-of-flight tests, with bank changes not requiring flight track registration.
Discussion on potentially moving section 8.2.1 or removing it due to the need for more scripts in territory changes.
Emergency change procedures for service providers are addressed in section 8.3, questioning whether changes should occur in-flight unless emergencies arise.
There was a back-and-forth on the intent and historical context of certain sections, indicating a need for further clarification.
