Issue 2007-I073

1. Issue 2007-I073 MVOs being cancelled prior to receiving 814_04 for MVI

2. Issue • Currently, it seems that ERCOT is canceling 814_24 Move-outs after receiving the 814_03 transaction for ‘MOVE OUT CANCELLED DUE TO AN INCOMING MOVE IN’.  ERCOT did not wait to receive the 814_04 transaction before sending the Non-Response driven Cancel.  The issue with this is that the 814_03 contains the “Requested Date”, where as the 814_04 contains the actual “Scheduled Date”.  Since the Scheduled date and the requested date could differ, this leaves the losing CR with added days of being the Rep of Record.  CenterPoint Energy would like to request that ERCOT should use the 814_04 transaction as the trigger to send the Cancel opposed to the 814_03.  This would allow a greater accuracy for when the MVI is scheduled, especially in the event of a change of the requested date for the MVI.

3. MIMO Rule – ERCOT Operating Rule 3 • In order to determine the appropriate recipient of notification transactions, and to properly execute customer requests, ERCOT may reject certain new initiating transactions that potentially could interfere with pending orders due for completion. However, there are some new transactions that are of such importance, that they should over-ride the pending transaction. Therefore, initiating transactions received after 11:00 pm the evening before 2 business days prior (5 business days prior for switches) to the scheduled meter read date of a pending order and prior to the scheduled meter read date would be analyzed upon receipt. If the requested date on such new transaction is prior to or equal to the scheduled meter read date on the pending transaction but not back-dated, either the new transaction will be rejected back to the initiating REP, or in some circumstances, the pending order will be cancelled.

4. MIMO Rule continued • The graph and table, below, should be referenced as to how this rule will be applied and utilized.If the TDSP receives a Move-In on the day of the Move-Out and the Move-In is requesting the same day and they have the ability to stop the Move-Out, they can complete the Move-Out unexecutable and use the Move-In as a Force-Move-Out.

5. MVO Data • Move Outs Cancelled for ERCOT Operating Rule 3 have a cancel code of A81. • 2,459 MVOs were cancelled for A81 in September (trumped by a received MVI)

6. MVI Data • 2,459 MVOs trumped • 2,414 (98%) of the MVIs Completed • 45 (2%) of the MVIs were Cancelled • Did the MVI MRD = MVO SMRD? • Yes – 1,534 (62%) • No – 925 (38%)

7. MVI Data • Of the 925 where the dates did not match, how far apart were they? • 199 (8%) were 1 day later • 43 (2%) were 2 days later • 129 (5%) were between 2 and 10 days • 9 (0%) were between 10 and 20 days

8. MVI Data • That leaves 545 (22%). What happened to those? • 45 (2%) are the MVIs that were cancelled • 500 (20%) have the MVI completing before the MVO SMRD.

9. Rep Data • 2,459 MVOs trumped by MVIs • 1,225 (50%) MVI Rep DID equal MVO Rep • 1,234 (50%) MVI Rep did NOT equal MVO Rep So half the time the Rep should have been able to manage what was happening to their orders.

10. Results • Number of customers who may have been impacted • 45 (2%) from the cancelled MVIs (unsure how long before they might have been moved out) • 199 (8%) were 1 day later • 43 (2%) were 2 days later • 129 (5%) were between 2 and 10 days • 9 (0%) were between 10 and 20 days • Total MVOs received by ERCOT in September - 121,389

11. Results • Total MVOs received by ERCOT in September - 121,389 • Number of customers who may have been impacted out of entire population of MVOs • 45 (.037%) from the cancelled MVIs (unsure how long before they might have been moved out) • 199 (.164%) were 1 day later • 43 (.035%) were 2 days later • 129 (.106%) were between 2 and 10 days • 9 (.007%) were between 10 and 20 days