1. RMGRR058 Overview RMS Meeting – August 15, 2007

2. Background / Reference PUCT Substantive Rule 25.43(n)(8) Protocol 15.1.2.9.1 Customer Billing Contact Information All CRs participating in the Texas retail electric market shall provide, in accordance with the Retail Market Guide (RMG), current Customer billing contact information to ERCOT for use in the event of a Mass Transition. ERCOT shall retain the Customer data from the most recent submission, to be used in lieu of data from the exiting CR, in instances where the exiting CR does not provide data. When a Mass Transition occurs, ERCOT shall provide the gaining CRs with available Customer billing contact information for the ESI IDs the gaining CR will be obtaining through the Mass Transition event. RMG section 7.11.6 Customer Billing Contact Information File

3. What is the CBCI file process? Initially…requested at January RMS All CR’s are requested to send their CBCI file between July 15 th and August 1 st 2007 Ongoing… Twice a year (April & October) all CRs must submit a CBCI file for all ESI IDs served as of the submission date ERCOT will provide a confidential report to the PUCT providing information regarding the twice annual CBCI accepted files Each CR will also receive a copy of report (CR specific information) for their records

4. Communications InformationNotice Sent R-A062507-01 Other06/25/07, 4:28PM R-A062507-02 REMINDER07/13/07, 3:55PM Files to be sent July 15 th and August 1 st 2007 Week 1 submission – 14/15 files had <10% error rate Week 2 submission – 20/24 files had <10% error rate R-A062507-03 UPDATE7/26/07, 3:09PM Majority of questions from MPs started R-A062507-04 REMINDER/UPDATE7/27/07, 4:59PM ERCOT developed workaround for error files Week 3 submission – 35/69 files had <10% error rate R-A062507-05 UPDATE ERCOT developed FAQ GAP – did not communicate clearly about if CR not setup for connectivity, CR did not need to send file 7/30/07, 1:24PM

5. What issues uncovered during initial load? 1.Gap in the file layout for error records a)Lack of detail needed to troubleshoot errors in files 2.Gap in the understanding of how files were to be submitted a)If a submission for a single DUNS is split into more than one file, it will overwrite the previous file, not append b)If CR has no ESI IDs, file to be submitted with zero detail records

6. What changes are proposed? ERCOT submitted RMGRR058 Revises the record layout of the Error Records (ER1 and ER2) sent from ERCOT to the CR Adds clarification that one single file must be sent for each DUNS number. Corrects the label on the Report Name data elements on the Header records on File1, File2, and File3. Specifies the method of record termination for files sent from the CR to ERCOT. Addresses Gap 1.a Addresses Gap 2.a Clean Up / Clarification

7. What comments received? Joint CRs Comments to RMGRR058 Specifies that DUNS numbers that do not have active ESI IDs, the CR will not be required to submit a file Revises the record layout of the Summary Record to remove 1) the Total Number of IDT records and 2) the Total Number of NDT records Moves language from section 7.11.6.3 to 7.11.6.2 for clarification Removes language from section 7.11.6.2 & 7.11.6.3 that is already in the Appendix F6 Addresses Gap 2.b Clean Up / Clarification

8. What are next steps? RMS voted for urgent timeline via email (thank you!) RMS vote for RMGRR058 – August 15, 2007 TAC vote for RMGRR058 – September 6, 2007 BOD vote for RMGRR058 – September 18, 2007 If/when approved, ERCOT will manage work via SIR (code, test and migrate to production) prior to the next cycle of processing CBCI files in October 2007

9. Questions?