MIMO/Stacking (Including Tx SET Version 2.0) Post Implementation Success Report

1. MIMO/Stacking(Including Tx SET Version 2.0)Post Implementation Success Report

2. Post Implementation Success Report Benefits Expected (as presented to RMS prior to implementation) • Significant reduction in NFI rejects • Significant reduction in need for Safety Net Move-Ins • Better manages customer expectations (Dates, billing, etc.) • Fewer backdated clean up efforts • Fewer Cancel/Re-bills • Helps keep systems in sync • Reduces UFE • Reduces transaction volume • Expedites connecting and billing the customers by the correct CR • Improves transaction reliability

3. Post Implementation Success Report Benefits Expected (grouped into 8 categories) • Significant reduction in NFI rejects • 7 statistics • Significant reduction in need for Safety Net Move-Ins • 6 statistics • Expedites connecting and billing the customers by the correct CR / Better manages customer expectations (Dates, billing, etc.) • 6 statistics • Fewer Cancel/Re-bills / Helps keep systems in sync • 4 statistics • Reduces UFE / Helps keep systems in sync • 2 statistics • Fewer backdated clean up efforts / Helps keep systems in sync • 4 statistics • Reduces transaction volume • 7 statistics • Improves transaction reliability • 2 statistics

4. Post Implementation Success Report Percent of NFI Rejects by Order Type 1.1.1 – Benefits 1,2,3,&7

5. Post Implementation Success Report Quantity of NFI Rejects by Order Type 1.1.2 – Benefits 1,2,3,&7

6. Post Implementation Success Report Quantity of All Rejects by Order Type Rejects for DUP – Duplicate and DOT – Duplicate Original Transaction Id have been removed 1.1.4b – Benefits 1,2,&7

7. Post Implementation Success Report Success Rate of Accepted Move-Ins Completion percentage of orders once they have been accepted – does not include rejected requests 1.3.2 – Benefits 1 & 8

8. Post Implementation Success Report Quantity of Backdated Move-In Requests Measures Move-Ins with a requested date that is earlier than the date the request is received by ERCOT 1.6.1 – Benefits 1,2,4,6,7, & 8

9. Post Implementation Success Report Quantity of Re-Bills on Final Usage Metrics for Move-Ins and Switches only 1.4.1 – Benefits 1,2,3, & 4

10. Post Implementation Success Report Cancelled with Exception Quantity of orders cancelled for A95 – Cancelled with Exception 2.2.2 – Benefits 3,4, & 6

11. Post Implementation Success Report Invalid ESI ID Rejects Quantity of Move-Ins rejected for A76 – Invalid ESI ID 2.1.2 – Benefits 7

12. Post Implementation Success Report Percent of Drop to AREPs with an 814_14 Percent of Drop to AREP orders where ERCOT generated an 814_14 Enrollment Request to the AREP 4.11.1b – Benefits 7

13. Post Implementation Success Report Percent of Move-Out to CSAs with an 814_22 Percent of Move-Out to CSA orders where ERCOT generated an 814_22 Enrollment Request to the CSA CR 4.12.1b – Benefits 7

14. Post Implementation Success Report Quantity of Orphan Accounts TDSPs provided quantity of Orphan Accounts at the end of each month 1.5.1 – Benefits 5

15. Post Implementation Success Report Quantity of Safety Nets Requested 1.2.1

16. Post Implementation Success Report Quantity of Safety Nets without EDI Quantity of orders where EDI was not received by the time the order was worked 1.2.1b

17. Post Implementation Success Report Concurrent Processing Concurrent processing of transactions was a major part of Stacking. The following details the occurrences of multiple service orders completing successfully – Benefits 1,2,3,4,& 6: • Multiple Move-Ins – 5810 occurrences • Drop to AREP prior to a Move-In - 302 occurrences • Drop to AREP prior to a Switch - 102 occurrences • Switch prior to a Move-In - 102 occurrences • Switch prior to a Move-Out - 73 occurrences • Multiple Switches – 44 occurrences • Drop to AREP prior to a Move-Out - 27 occurrences Orders were successfully processed concurrently a total of 6460 times in August and September

18. Post Implementation Success Report Other Stacking Stats: • There has been a 17.8% reduction in the average number of rejects for Move-Ins leapfrogging. (1.6.3) • The Move-Out retry is effective in allowing appropriate Move-Outs to be processed instead of being rejected. (4.1.1) • To ensure that Move-Outs and Drop to AREPs are properly authorized, ERCOT is canceling Move-Outs and Drop to AREPs at the evaluation window if the REP is no longer the REP of Record. (4.2.1 - Benefits 3, 5, &6) • August and September Volume – 1789 • ERCOT is successfully canceling Move-Outs when they are scheduled on the same day as a Move-In on the same ESI ID. This contributes to market synchronization. (4.4.1) • August and September volume - 5661

19. Post Implementation Success Report Other Stacking Stats (cont.): • Drop to AREPs are being successfully canceled when scheduled on the same ESI ID as a Switch with the same or later date. This is helping to enforce the customers right to choose. (4.5.1) • August and September Volume – 1836 • The new iteration counter is allowing REPs to submit multiple Date Changes on a single order and these are helping to ensure the customer is getting the last date they requested. (4.13.1) • Market participants are now electronically notified of Duplicate transactions. (4.14.1) • August and September Volume = 9313 • TDSPs are effectively rejecting backdated Move-Ins and Move-Outs that are not part of a coordinated back-office cleanup. (5.4.1) • August and September Volume = 1696

20. Post Implementation Success Report Action Items • Does RMS want statistics next month? • If so, are these adequate with October added, or are additional statistics desired?