1. 1 Update from ERCOT Retail Market Services to RMS March 18, 2004

2. 2 –MIMO Stacking Solution Update Glen Wingerd –Flight 0504 Update Karen Bergman –Flight 0104 Update Karen Bergman –SCR732 Update Karen Bergman –Texas Market Link (PRP phase 1) Update Matt Mereness –Commercial Application Systems Upgrade Project Kevin Judice –EDIM Progress Reports James Cohea Agenda / Presenters

3. 3 –EDIM Progress Reports Fast Trak Day to Day Issues Progress Report Fast Trak DEV Issues Progress Report On-Going Data Clean Up Update –NAESB 1.6 Migration Update –Load Research Project Update –CR Data Extract Variance Reporting Supporting Reports

4. 4 Move-In/Move-Out Market Solution to Stacking (Texas Set V.2.0)

5. 5 Agenda –Market Participant Progress Tracking –Educational Seminars –Next Steps –Implementation Plan Market Coordination Team for the Solution to Stacking

6. 6 MP Progress Tracking –All Market Participants have been requested to provide a monthly status on their progress with the Stacking effort –Additional questions were asked to identify known risk Have you identified any risks that will prevent your company from beginning testing on time (April 26 th )? Please describe any risk(s). Have you identified any risks that will prevent your company from implementing on time (August 1 st )? Please describe any risk(s). Response is required, non-responses will be reported to RMS. Non- response to the status will result in a default to the previous month’s status. Non-Response to the questions will indicate that no risks have been identified. –Progress including reporting of identified risks will be reported through April, 2004 Market Coordination Team for the Solution to Stacking

7. 7 ERCOT/TDSPs/Service Providers Market Coordination Team for the Solution to Stacking

8. 8 REPs Market Coordination Team for the Solution to Stacking

9. 9 Answers to Status Questions: –All Market Participants provided a status –75 of 76 indicated that no risks had been identified –1 of 76 reported a manageable issue Yes, we are currently in the process of selecting a new CIS vendor. The CIS vendor that we are currently in contract discussions with should be ready to begin testing on 4/26. The vendor has a status that they have previously reported to RMS and have other clients in the Texas market. Market Coordination Team for the Solution to Stacking

10. 10 Educational Seminars –31 Educational Seminars completed –Over 470 participants have attended Market Coordination Team for the Solution to Stacking

11. 11 Project Overview Summary of Changes: Manage customer expectations by accepting and processing all valid requests. Impact Level Efficiency Communication Competition Business Problem Existing NFI logic forces an unreasonable amount of dependency on labor intensive workarounds. Execution of workarounds are causing synchronization issues between market participants. Lack of synchronization leads to improper billing and mismanagement of customer expectations Solution All valid transactions will be accepted and processed based on a set of market rules. Drop notifications will be sent at a point in time where the proper recipient can be positively identified. Rule based cancellations are sent on a pre- determined timeline with enough time for the recipient to react.

12. 12 Next Steps/Progress –MCT reviewed the scripts developed by Script Sub-Team on 2/19/04 –Continue to Track Market Participant Progress –Post the Production Implementation Plan –Post the Transition Plan for Service Orders ‘In Flight’ –Develop Post-Implementation Success Criteria –Document and communicate changes to market reports and extracts Market Coordination Team for the Solution to Stacking

13. 13 Implementation Shutdown Overview Wednesday Midnight Thursday Noon Thursday Midnight Friday Noon Friday Midnight 6 hrs14 hrs6 hrs9 hrs1 am 9 pm6 hrs8 hrs6 hrs 814_01, 814_10, 814_16, 814_24 814_08, 814_12, 814_18, 814_26 8 hrs2 pm 867 7 hrs 5 pm 650_01 1 hr Legend CRsERCOTTDSPs = Conference Calls 814_20 9 pm6 hrs8 hrs6 hrs 814_PC 2 pm4 hrs Initiating 5 pm 1 hr 810, 650_04

14. 14 Conference Call Times Ten Planned Market Conference Calls –Wednesday July 28 th 5 p.m. –Thursday July 29 th 9 a.m. –Friday July 30 th 9 a.m. –Friday July 30 th 5 p.m. –Saturday July 31 st 9 a.m. –Saturday July 31 st 7 p.m. –Sunday August 1 st 9 a.m. –Sunday August 1 st 3 p.m. –Monday August 2 nd 9 a.m. –Tuesday August 3 rd 9 a.m.

15. 15 When bad things happen to a good plan… oAt the point that we arrive at conversion weekend, every market participant has: Provided monthly statuses Participated in migration conference calls Passed testing certification oThe inability of a Market Participant to successfully implement would not be a situation where a party failed to build their solution, but rather a situation where there is a technical problem with migrating to their production environment. oBased on this, it is the position of MCT that any issues on conversion weekend will be of the type that cause delays measured in hours not days. oAlthough it is a fundamental requirement for all MPs that they have a back-out plan, MCT does not envision an issue that would be a showstopper, but does believe there may be a possibility for delay.

16. 16 When bad things happen to a good plan… oIf any party cannot implement the stacking solution at any point between July 23 rd and August 1 st, the potential for delay will be discussed on an emergency conference call. oAs determined on the call, the affected parties will develop a plan for resolving the issue(s). oIf there is a migration issue announced prior to the “Go/No-Go”, a determination will be made to delay based on the estimated time of resolution (“Go” with a delay). oIf a “No-Go” is called (reverse migration may be necessary), the determination for a new migration date will be made based on the estimated time of resolution. oOnce a “Go” is called, there will be no turning back (no reverse migration). “Go” with delayMitigation ERCOTDelay < 72 hoursSafety Net TDSPDelay < 96 hoursSafety Net REPN/ASafety Net Version 1.6

17. 17 When bad things happen to a good plan…  Weather delay oFirst discussion of weather delay will take place on the Wednesday 5:00 PM conference call. oIf delay is not called on Wednesday, last opportunity for discussion of weather delay will take place on Friday 9:00 am conference call oIf delay is called, there are 2 possible results: Weather does not cause a significant impact on any active MPs. Delay is one week. Weather causes a significant negative impact on one or more active MPs. Delay may be more than one week.  ERCOT delay oDelay for entire market oREPs/TDSPs will use Safety Net to complete Move-Ins oSuspend Switches, Drop to AREPs, and Move-Outs oExecution of Plan “C” for Usage oMaximum of 72 hours (Thursday August 4 th )

18. 18 When bad things happen to a good plan…  TDSP delay oTDSP uses normal contingency plan for system outage for first 48 hours. oAfter 48 hours in TDSP territory experiencing delay: Use Safety Net to complete Move-Ins Suspend Switches, Drop to AREPs, Move-Outs, and DNP Execution of Plan “C” for Usage Maximum of 96 hours (Friday, August 9 th )  REP delay oDelay for that REP oFor first 72 hours, Use Safety Net to complete Move-Ins oFor a delay of more than 72 hours, the REP(s) with the delay(s) will have the option of reversing their migration and sending transactions in Version 1.6, but will not be allowed to continue using the Safety Net for non priority Move-Ins. (Date Changes will be rejected by ERCOT if the iteration counter is missing)

19. 19 Flight 0504 Update

20. 20 Market Participant Testing Orientation The deadline to register for participating in the Flight 0504, TX SET Version 2.0 Retail Market Testing is April 1, 2004, 5 p.m. CST. ERCOT will host a MANDATORY orientation meeting in preparation for Flight 0504, TX SET Version 2.0 Retail Market Testing. Audience: The orientation meeting is required for both current Market Participants operating in the Texas Retail Market as well as new Market Participants entering the Texas Retail Market. Since the testing approach has changed from previous flights, this meeting will be focused on the education of the testing scripts, testing procedures timeline, tools, and website that will be used during this test flight. Suggested audience would be the personnel involved with the day to day testing responsibilities for your company.

21. 21 Testing Tracks and Testing Relationships “Round Robin” Testing

22. 22 Testing Tracks for V 2.0 End-to-End Scripts Approved track names –All –Rotate –MOU/EC CR –New CR –AREP –CSA –TDSP

23. 23 Testing Tracks for V 2.0 End-to-End Scripts All –CRs would be split into groups (1, 2, 3) –Each group would execute all scripts in this track with at least 2, possibly 3 TDSP Rotate –A subset of CRs (or volunteers) would execute these scripts with all TDSPs MOU/EC CR –Any CR who signed up to test with a MOU/EC TDSP would execute all scripts in this track with the MOU/EC TDSP in the market –In addition, if the CR was signing up to do business in other than an MOU/EC TDSP territory, they would be assigned into a group to execute the V2.0/MIMO scripts New CR –All New CRs would execute all scripts in this track with whichever TDSP they signed up to do business in –In addition, a New CR would be assigned into a group to execute the V2.0/MIMO scripts

24. 24 Testing Tracks for V 2.0 End-to-End Scripts (continued) AREP –Each AREP would test these scripts with the TDSP they are the AREP for –In addition, an AREP would be assigned into a group to execute the V2.0/MIMO scripts CSA –Current and new CSA CRs would test this script (ERCOT will simulate the TDSP) TDSP –ERCOT will execute these scripts with all TDSPS

25. 25 Visually

26. 26 Testing Relationships ERCOT has committed to providing the following information to the market: –For all current CRs and TDSP in the market, ERCOT will provide the testing relationship list by Friday, March 26, 2004 This list will be sent to the PRIMARY testing contact for each CR and each TDSP that is listed on the Testing Signoff Worksheet It is important that the PRIMARY testing contact circulate to whomever in the Market Participant organization who needs to view it Market Participants will have a review period Monday, March 29 and Tuesday, March 30 If a Market Participant has issues with the testing relationships, they must be communicated back to ERCOT by 5pm on Tuesday, March 30, 2004

27. 27 Testing Relationships ERCOT will contact each party who has issues to work towards resolving the issue. ERCOT will provide a final testing relationships list (adding to the list any New CR or TDSP who are entering the market) by 5pm on Monday, April 5 th. Checklists will be created after the final testing relationships lists is delivered to the Market Participants.

28. 28 PUCT REP Certification Option 2 REPs Scripts that must be validated –STK06 (On cycle switch request conflicts with scheduled move in) –SCR31 (Competitive Metering) –SCR32 (old DNP01) –SCR33 (old RA001) –SCR34 (Service order reread, completion, usage, invoice) –SCR35 (off cycle switch on unmetered ESI ID, usage, cycle bill)

29. 29 What’s the deadline for Flight 0504? The deadline to register for participating in the Flight 0504 is April 1, 2004, 5 p.m. CST.

30. 30 Flight 0104 Update

31. 31 Flight 0104 Status Report The market is complete with Flight 0104 Issues to date: –Minor communication issues with the Disconnect for Non-Pay script. –RA001 script continues to be the longest script to complete (when the banks are involved…) Congrats to all for completing on schedule!

32. 32 SCR732 Update

33. 33 SCR 732 Update What is SCR732? Creation of project team to develop detailed system requirements for an enhanced FasTrak process. –SCR732 is expected to result only in a detailed set of system requirements. –After SCR732 is completed, another project will have to be approved if the identified changes to FasTrak are actually to be implemented. Scott Egger, Sr. Business Project Manager is assigned. ERCOT will host at least one meeting prior to April RMS to confirm objectives and kick-off the requirements gathering efforts. –Requirements will be gathered from two perspectives – internal and external. –ERCOT encourages MP to send FasTrak users to the requirements gathering meeting.

34. 34 Texas Market Link ( PRP Phase 1)

35. 35 IT Update – Texas Market Link (Portal Replacement Project Phase 1) Status: –TML is in the final stages of testing (iTest environment) Includes programmatic load testing and negative testing –TML did not exit iTest by March 2 Results in delay of TML Phase2 release, new date is TBD No impacts to MIMO project Next Steps: –Testing completion targeted for March 12 –ERCOT plans to bring TML online in parallel with Portal for limited Market IT-only testing in late March Plan to begin 10 days after ERCOT testing is complete Market testing/verification is to confirm connectivity and the co- existence of TML/Portal products (late-March) –Full parallel market access to TML and Portal planned for early April

36. 36 Commercial Application Systems Upgrade Project (CASUP) PR# 30082_02

37. 37 Ongoing Transaction Data Clean Up Clean-up Process Steps Completed Items – Next Steps Status Report

38. 38 Ongoing Transaction Data Clean Up Clean-up Process Steps: 1.ERCOT runs the query and defines the Action Items needed a)In-Review with Meter Read: Notify TDSP and request 814_04/25 then transaction will complete. (Date Range equals or greater than 07/01/01.) b)Scheduled No Meter Read: Notify TDSP and request 867 completing transaction. (Date Range equals or greater than 07/01/01.) c)Cancel With Exception (CWE) with Meter Read: Notify CR and TDSP and find out if they thought the transaction had completed. If so – take corrective action. (Date Range is 04/12/03 to 08/31/03.) d)Cancelled Permit Not Received with Meter Read: Notify CR and TDSP and find out if they thought the transaction had completed. If so – take corrective action. (Date Range is 04/12/03 to 08/31/03.) 2.ERCOT distributes the lists to MP who owe the follow-up action. 3.MP Responds and ERCOT coordinates the clean-up activities. 4.ERCOT to report Monthly to RMS.

39. 39 Ongoing Transaction Data Clean Up Completed Items : October 20, 2003: ERCOT sends out new lists to CRs and TDSPs October 29, 2003: TDSPs send analysis to CR November 4, 2003: CRs respond to TDSPs and coordinate final response to ERCOT RMS approved a target deadline of December 12 for completing this activity ERCOT provide updates and reminders to the TDSPs on an ad hoc basis when requested by the TDSP and each week prior to RMS ERCOT confirmed all outstanding items are being reported as part of the weekly Missing 867 Report that TDSPs receive on the portal Next Steps: Request RMS approval to roll the remainder of this project into the weekly Missing 867 Reporting and discontinue this reporting on Ongoing Transaction Data Clean-up

40. 40 Ongoing Transaction Data Clean Up

41. 41 Pro-Active Transaction Resolution Measures Summary - Overview

42. 42 Proactive Measures Summary MeasureMP Target ObjectiveValueDate Initiated 867 RCSO TDSPs Now (CRs Later) Identify instances where ERCOT has canceled a Service Order but TDSP has completed the service Order (out-of-sync) Identification and resolution of out-of-sync conditions very close to the time of creation of the out-of-sync condition 11/7/2003 & Weekly Thereafter Missing 867 TDSPsResolve missing 867 issues and complete or cancel service orders in a timely manner Shorten time service orders stay in a scheduled status and reduce Not-First-In rejects to CRs 2/18/2004 & Weekly Thereafter Pending CWE TDSPsGet service orders into scheduled status before they cancel by exception Accurate REP-of-record information, less out-of-sync conditions and fewer FasTrak issues 2/16/2004 & Daily Thereafter Mapping Status Rejects TDSPs and CRs MP correction and resend of transactions in a timely manner Facilitation of Market requests, Market requirements and fewer FasTrak issues 2/16/2004 & Daily Thereafter

43. 43 Missing 867 Report The Missing 867 Report will provide TDSPs information about Service Orders in a scheduled state for which ERCOT has not received an 867 completing transaction at least seven days after the scheduled meter read Weekly report provided to the TDSP Volume as of 3/3/04 Report: Missing 867 Report

44. 44 Pro-Active Transaction Resolution Measures 867s Received on Canceled Service Orders

45. 45 Situation ERCOT periodically receives 867_03 Finals and 867_04s for service orders that are Canceled in ERCOT systems. The Service Order Statuses that are considered Canceled are: Canceled (manually or concurrent processing), Canceled by Customer Request, Canceled by Customer Objection, Canceled Permit Not Received, Canceled with Exception, Unexecutable and Rejected by TDSP. This can indicate an out-of-sync condition between the TDSP and ERCOT. Current Mechanism for Handling 867 RCSO: Step 1: ERCOT produces 867RCSO data each Friday and submits an ERCOT initiated FasTrak to the TDSP Step 2: The TDSPs review the FasTrak line items and take one of the following actions: a) If the TDSP has cancelled the service order, note cancelled on the line in the FasTrak issue (Note: For Cancel by Customer Objection, the TDSP will honor the cancel in their systems) b) If the TDSP has completed the service order, they will establish a new day-to-day FasTrak issue and work with ERCOT to get ERCOT systems changed to complete also – in this case the TDSP will note the new FasTrak issue number in the line item of the original ERCOT initiated 867RCSO FasTrak issue Step 3: Once all line items within the ERCOT initiated 867RCSO FasTrak issue have been updated, the TDSP and ERCOT will close that issue. 867s received on Canceled Service Orders

46. 46 867s received on Canceled Service Orders

47. 47 867s received on Canceled Service Orders Completed Items ERCOT continues sending weekly FasTrak issues to TDSPs ERCOT modified process to omit 867 Cancels from reporting beginning with 2004 ERCOT met with each TDSP on 2/4/04 and 2/5/04 to determine a consensus direction for clearing out-of-sync ESI IDs 867RCSO process helped to identify two processing issues with two different TDSP since its inception Next Steps ERCOT to move from a FasTrak Initiated issue to an automated weekly portal report to the TDSP and the CR in April 2004

48. 48 Customer Protection and 814_08 Issue (Phase 1 – Potentially Missing 08s) Background and Completed Items Matrix and Progress Report Other Status Items and Next Steps

49. 49 Customer Protection Period and 814.08 (Phase 1 – Potentially Missing 08s) Background ERCOT has determined that there was an issue with the 814_08 manual-processing tool related to the cancel by customer objection process. While ERCOT systems were updated appropriately, 972 ESI IDs (spanning the August 2002 through July 2003 time frame) were identified where ERCOT has been unable to confirm that the TDSP was sent the 814_08 cancel. Completed Items Scenario 1 instances: ERCOT has completed synching with the TDSPs on all of these. 41 FasTrak issues: ─40 Resolved (spanning 95 switches) ─1 In Progress (some dialog has occurred) Matrix of FasTrak issues not yet resolved provided to RMS Chair/Vice Chair on 11/6/03, 12/4/0, 1/6/04, 1/30/04, 3/2/04 - included CR names. TAC discussion 3/4/04. ERCOT has “processed” all email exchanges related to FT issues as of 3/8/04 Next Steps ERCOT to continue to escalate missing responses CRs and TDSPs make decisions on outstanding FasTrak issues and provide response to ERCOT via FasTrak and Email

50. 50 March 8, 2004 Status Customer Protection Period and 814.08 (Phase 1 – Potentially Missing 08s)

51. 51 Customer Protection Period and 814.08 (Phase 1 – Potentially Missing 08s) Note Of the remaining 9 switches “In Progress”, they are all on one FT issue that is moving towards resolution. March 8, 2004 Status

52. 52 Customer Protection and 814_08 Issue (Phase 2 – Potentially Late 08s) Background Completed Items Next Steps

53. 53 Background Upon inception of Phase 1 of the ‘Potentially Missing 08s’, MPs requested an analysis of potentially late 08’s on Cancel by Customer Objection (CCO). ERCOT identified 264 instances of 08’s on CCOs that were sent to the TDSP at least two days after the end of the customer objection period where the TDSP rejected the cancel. These switch transactions span the August 2002 through November 2003 time frame. Upon direction from RMS at the December 2003 meeting, ERCOT sent list to each CR and TDSP involved in an attempt to quantify the true scope of out-of-sync conditions. Completed Items Received direction at 01-14-04 RMS meeting for MPs to honor the cancellation ERCOT created 30 FasTrak issues on 1-30-04 connecting both CRs and notified the TDSP and CRs via email of the RMS directive and the FasTrak issue 7 FasTrak Issue closed by CRs accounting for 22 Service Orders Next Steps 11 Issues/193 Service Orders show some response in FasTrak while 12 Issues/49 Service Orders have no update in FasTrak CRs review the remaining FasTrak issues and ensure they honored the Cancellation by Customer Objection TDSPs review email notification of the issues and ensure they honored the Cancellation by Customer Objection Customer Protection Period and 814.08 (Phase 2 – Potentially Late 08s)

54. 54 Linked-Address Issue Multiple ESI Ids Linked to a Single Service Address Record Background Counts Matrix Completed Items Next Steps

55. 55 Background On the 02/18/04 Retail Market Call, a CR reported a concern regarding discrepancies between ERCOT’s Portal and the TDSP’s customer information system. The CR provided specific example for ERCOT to research. Analysis, released by ERCOT on 3/8/04, has identified that linked service addresses were established in the ERCOT Siebel system based upon data provided during conversion in 2001. In these instances, a TDSP provided the same service address for multiple ESI IDs. During the conversion process, a single database record was created which linked a single service address to multiple ESI IDs. The Address Field components making up the address record in the ERCOT Siebel system are street name, Address Overflow, City, State, Country and Zip code. The current effect is that an 814_20 address change to any one of the address- linked ESI IDs effectively changes the address, in ERCOT’s system, of all ESI IDs linked to that same record. Approximately 11 percent of the ESI IDs in the ERCOT Siebel system are affected by this "linked address" issue. Linked-Service Address (Multiple ESI Ids Linked to a Single Service Address Record)

56. 56 TDSP Quantity Breakdown Linked-Service Address (Multiple ESI Ids Linked to a Single Service Address Record)

57. 57 Completed Items 3/8/04 - Information released to the Market during Retail Market Call 3/9/04 - Initial conference call with TDSPs to discuss issue and proposed process 3/10/04 - Retail Market Call additional information 3/12/04 - ERCOT provided TDSPs a list of all ESI IDs with linked-addresses 3/16/04 - Follow-up conference call with TDSPs to discuss process further - ERCOT had ad-hoc discussions with CRs 3/17/04 - Follow-up discussion with a CR - Follow-up at Retail Market Call to detail proposed process Linked-Service Address (Multiple ESI Ids Linked to a Single Service Address Record)

58. 58 Linked-Service Address (Multiple ESI Ids Linked to a Single Service Address Record) TDSP ERCOT CR Original Lists Compare Analyze & Summarize Results Mismatch List w/ Addresses “Fix” Address Database New List of all ESI IDs Compare Post Compare Results Mismatch List w/ Addresses Submit 814_20s Process 814_20 Receive 814_20 March 31 st April 2 nd Start April 12 th Retrieve and Compare March 12 th Market Meeting

59. 59 Next Steps Updates to be given at least once weekly on the Monday Retail Market Call and summarized at RMS until process is complete TDSP to compare address data ERCOT provided on 3/12/04 with their system address data and report to ERCOT by 3/31/04 any address mismatches – including TDSP address data ERCOT to analyze and compile address mismatch data received from TDSP and host market meeting on 4/8/04 to discuss further Market actions CRs to investigate how they handle the address data the TDSP provides in the 814_04 – which ERCOT send to the CR in 814_05 transaction ERCOT to determine a process to establish a one-to-one relationship between impacted ESI ID and service address record in the ERCOT Siebel system. Process initiation will begin 04/12/04 and will flow though the testing environment and a roll-out to production. ERCOT to provide TDSPs with a list of affected ESI IDs after final database fix TDSPs to compare final list to their system addresses and submit 814_20 address modification for any address mismatches Linked-Service Address (Multiple ESI Ids Linked to a Single Service Address Record)

60. 60 2003 Non-ERCOT FasTrak Issues Point of Concern Issue Activity Stats Table

61. 61 2003 “Day to Day” Non-ERCOT FasTrak Issue Stats (as of 03-09-04) Point of Concern The table below details outstanding 2003 Non-ERCOT Day-to-Day FasTrak issues (between CR & CR or CR & TDSP) Section 3.4/3.5 of the FasTrak Day-to-Day Policy-Procedure Manual requires a 7 day response to issues Issue Activity During the week of 3/1/04, ERCOT submitted lists of outstanding issues to the submitting MP’s main contact and cc’d the original submitters requesting they escalate these FasTrak issues to the escalation contacts identified in the FasTrak Contact listing Of the 1,522 New and In Progress Non- ERCOT issues, 202 are resolved and awaiting other party resolution check off 6 are for the year 2002 Number of ESI IDs not tracked

62. 62 Thank You

63. 63 Supporting Reports Section

64. 64 FasTrak Issue Status Day-to-Day Data Extract Variances (DEV) ERCOT Initiated Issues

65. 65 FasTrak 2003 “Day to Day” Issue Stats (as of 03-09-04) Of the 1 In Progress, 1 are resolved and awaiting other party resolution check off Total ESI IDs worked on 2003 issues = 324,544 Of the 1,522 New and In Progress Non-ERCOT issues, 202 are resolved and awaiting other party resolution check off 6 are for the year 2002 Number of ESI IDs not tracked

66. 66 FasTrak 2004 “Day to Day” Issue Stats (as of 03-09-04) Of the 333 New & In Progress, 131 are resolved and awaiting other party resolution check off Total ESI IDs worked to date since January 1, 2004 = 43,763 Of the 1,632 New & In Progress, 266 are resolved and awaiting other party resolution check off Number of ESI IDs not tracked

67. 67 FasTrak Data Extract Variance Issue Stats (as of 03-09-04) Note: Of the 265 New & In Progress ERCOT Issues, 45 are resolved and awaiting other party resolution check off

68. 68 FasTrak ERCOT Initiated Issues Issue Stats (as of 03-09-04) These are issue initiated by ERCOT to the TDSP or CR as a result of one of the following projects: –Customer Protection Period and 814.08 –867 Received on Canceled Service orders –5 new issue types to support Energy Aggregation Management Department issue process

69. 69 NAESB EDM v1.6 Update

70. 70 NAESB EDM v1.6 ERCOT Testing Status Current Progress:  Phase 1 - ERCOT and TDSP – Testing is complete  Phase 2 - ERCOT and CR – Testing is complete  Phase 3 - TDSP and CR – Testing is complete Future:  Additional “Connectivity Testing” one week prior to production implementation (ERCOT, TDSPs, CRs)

71. 71 NAESB EDM v1.6 ERCOT Testing Status Resolves:  If you are using a JAVA-based batch-browser which uses an old Certificate from Verisign that expired on January 7, 2004, you will need to get an update from the Certificate Store  ERCOT will not accept a Production Certificate that has not been issued by a Third Party Certificate Authority  All Market Participants must have SSL enabled  Use of GPG version 1.2.3

72. 72 NAESB EDM v1.6 ERCOT Testing Status - CRs 100% Complete75% - 99% Complete 50% - 74% Complete25% - 49% CompleteNot Yet Initiated

73. 73 NAESB EDM v1.6 ERCOT Testing Status – CRs cont. 100% Complete75% - 99% Complete 50% - 74% Complete25% - 49% CompleteNot Yet Initiated

74. 74 NAESB EDM v1.6 ERCOT Testing Status – CRs cont. 100% Complete75% - 99% Complete 50% - 74% Complete25% - 49% CompleteNot Yet Initiated

75. 75 NAESB EDM v1.6 ERCOT Testing Status - TDSPs 100% Complete75% - 99% Complete 50% - 74% Complete25% - 49% CompleteNot Yet Initiated

76. 76 NAESB EDM v1.6 Phase III CR-TDSP Testing Status “X” = Testing Complete ; “P” = Testing in Progress

77. 77 LRS Project Update

78. 78 LRS PROJECT INFORMATION Market Updates –Sample Design Completed on 2/9/2004, ~4000 sample sites for initial design –ERCOT resolving sample issues with TDSPs Cut off date of 3/12/2004 has been set for TDSPs to resolve issues Sample selection will be performed immediately thereafter –Load Research Sampling (LRS) web site initiated with postings of documented materials (including meeting minutes, rulings, etc.): http://www.ercot.com/Participants/loadresearchsampling.htm –CR signup to receive data from LRS program in progress 55 of 67 responses obtained to date. ERCOT Client Relations following up with outstanding CRs 21 out of 67 wish to receive data from LRS program –ERCOT in discussion with interested MUNIs/COOPs on exchanging load research data ERCOT Updates –ERCOT delivery system conceptual design complete –ERCOT tracking DB conceptual design complete –ERCOT hardware installation in-progress

79. 79 LRS PROJECT UPCOMING ACTIVITES March 12, 2004 conference call to update involved participants (TDSPs and CRs) of status and development for LRS Project March 15, 2004 CR handshake testing schedule to be released March 22, 2004 next LRS Project update meeting March 2004 and on-going TDSPs to submit installation schedules for meters based on site inspections April 2004 CR handshake testing May/June 2004 TDSPs to start “pilot” with ERCOT –Submitting meter readings –Obtaining responses for submitted data –Working with ERCOT Load Profiling Group to work out data errors –Weekly conference calls with TDSPs first line contacts

80. 80 February Summary: CR Data Extract Variance Reporting

81. 81 February CR DEV Reporting 8 of 73 Competitive Retailers Reported Numbers by the due date for February (02/03/04) Numbers for April RMS (March Reports) are due by April 2, 2004 Goals for next month: –More CRs Reporting –ERCOT will break numbers out by TDSP

82. 82 Totals

83. 83 Thank You