1. 1 Update from ERCOT Retail Market Services to RMS January 14, 2004

2. 2 –Texas Market Link (PRP phase 1) Update – Matt Mereness –Commercial Application Systems Upgrade Project - Dave Odle –Data Variance / SCR 727 Extract Update – Betty Day –EDIM Progress Reports – James Cohea Fast Trak Day to Day Issues Progress Report Fast Trak DEV Issues Progress Report Pre-Texas SET 1.5 Data Clean Up Progress Report On-Going Data Clean Up Update Customer Protection 814_08 Issue Update 867s received on Canceled Service Orders –NAESB 1.6 Migration Update - John Kassel –MIMO Stacking Solution Update – Glen Wingerd –Load Research Project Update - Raj Chudgar –Flight Test Update (0104) – Karen Bergman –Market Participant Survey - Scott Egger –CR Data Extract Variance Reporting - Karen Bergman Agenda / Presenters

3. 3 Texas Market Link ( PRP Phase 1)

4. 4 IT Update – Texas Market Link (Portal Replacement Project Phase 1) The new Portal/TML was launched 12/3/2003 after successful completion of market testing and stress/load testing, however, technical issues were encountered and the old Portal was reinstated. Post-mortem analysis has revealed a technical issue in the platform integration. Next steps are being discussed to resolve technical issues and to assess re-launch approach. –In the interim, any https://tml.ercot.com requests are being redirected to https://portal.ercot.com.

5. 5 Retail API Update

6. 6 IT Update ( API Issue and Redevelopment Efforts) API became corrupt/unrecoverable on 10/3/03 ERCOT Development team developed new API program to replace old functionality Released in three phases: –Download of Report Functions- released 11/11/03 –Find ESI Id and Find Transactions- released 12/8/03 –Find Market Participant Data & Winzip fix- released 12/16/03 Continue providing Weekly Updates on Retail Conference Call Reminder that the website URL for the API changed: –https://pi.ercot.com/servlet/piController

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

8. 8 CASUP Purpose Project Purpose: ERCOT Commercial Systems must be upgraded for software version support and compatibility. ERCOT considers this an opportunity to review current application performance, reliability, and extensibility. ERCOT will be evaluating if there are existing applications that better meet our functional needs and cost of ownership requirements. Desired Result: To improve ERCOT’s ability to provide reliable, scalable, highly available, and extensible commercial systems that enable timely and accurate responses to changing demands of the Texas Electric Market while over time reducing the total cost of ownership and operation.

9. 9 CASUP Approach Requirements Phase Business Requirements Technical Requirements RFQ Recommendation Vendor Shortlist RFP Phase RFP (if necessary) Vendor Selection (if replacement option is decided) Build Phase Either: Upgrade or Replace 10/16/033/31/04 ?? Current Phase

10. 10 CASUP Requirements Approach Requirements Phase Project Approach: Three deliverables: –Business Requirements Delivery –Technical Requirements Delivery –Recommendation (Upgrade/Replace) and Vendor Shortlist Delivery All three deliverables running in parallel Requirements phase to conclude 3/31/04

11. 11 CASUP Next Steps Vendor Demonstrations during January & February –ERCOT evaluations of demos –Cost/Benefit/Risk Analysis –Decision of Replace or Upgrade –Vendor Shortlist Creation Requirements –Business detailed requirements complete –Technical detailed requirements complete

12. 12 Data Variance / SCR 727 Extract Status

13. 13 ERCOT provided all extract files by the scheduled date of 12/19/03 Daily extract file posting began on 12/19/03 Two minor issues resolved: –Daily files for 12/7/03 and 12/8/03 posted out of order MPs processing according to the dates of the files were not impacted MPs processing according to the posting date were provided instructions on how to correct –Decimal precision on LSCHANNELCUTDATA records New extracts are provided with higher level of precision ERCOT recommends rounding of data by MPs to avoid any issue in comparing extract data to MP source data Incremental 2 LSCHANNELCUTDATA files formatted incorrectly (no decimal precision) – new data files provided SCR 727 Extract Status

14. 14 Board Resolution on True-Ups All true-ups for 2003 shall be delayed until market participants have a reasonable amount of time to load complete data extracts and analyze the data, and sufficient time to process any alleged variances as follows: (1)2003 True-Up Settlement Statements will begin no earlier than 120 days from the date that ERCOT provides the first complete SCR 727 data extracts related to 2003 to market participants, as determined by ERCOT, and (2)alleged data variances indicated in the extracts affecting 2003 True-Up Settlement Statements must be submitted to ERCOT in chronological order beginning 90 days from the date that ERCOT provides the first extract related to 2003. ERCOT has determined that complete data was provided to the Market by 1/1/04. True-Up Settlement Statements for 2003 will begin on May 1, 2004. A Settlement Calendar will be published to the ERCOT website.

15. 15 RMS Vote on DEV Timelines (10/16/03) A motion was made by Rob Bevill and seconded by Shannon Bowling to establish a 75 calendar day deadline for completion of each issue and each MP (including ERCOT) will complete the Data Extract Variance (DEV) Process in accordance with the timelines and other requirements of the DEV Manual. The motion was approved.

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

17. 17 FasTrak 2003 “Day to Day” Issue Stats (as of 01-07-04) Of the 276 In Progress, 91 are resolved and awaiting other party resolution check off Total ESI IDs worked in 2003 = 324,587 Of the 3,749 New and In Progress Non- ERCOT issues, 13 are for the year 2002 Number of ESI IDs not tracked

18. 18 FasTrak 2004 “Day to Day” Issue Stats (as of 01-07-04) Of the 130 In Progress, 62 are resolved and awaiting other party resolution check off Total ESI IDs worked to date since January 1, 2004 = 5,661 Number of ESI IDs not tracked

19. 19 FasTrak Data Extract Variance Issue Stats (as of 01-07-04) Of the 149 In Progress, 2 are resolved and awaiting other party resolution check off 2,123 issues classified as resolved or rejected in 2003 are excluded from the report per RMS direction 2,421 issues classified as resolved or rejected in 2003 are excluded from the report per RMS direction

20. 20 FasTrak ERCOT Initiated Issues Issue Stats (as of 01-07-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

21. 21 Pre TX Set 1.5 Data Clean Up RMS Directive Pre TX SET 1.5 Status Report

22. 22 Pre-TX Set 1.5 Data Clean Up Background: ERCOT identified “In Review”, “Scheduled” and “Canceled with Exception with Meter Reads” that were not completed from early 2002 to April 11, 2003. RMS Vote, July 17 th, 2003: Recommend RMS direct ERCOT to completely clean-up by August 13 th, 2003 the Pre-Tx Set 1.5 In Review, Scheduled and Cancel With Exception that have been identified and sent to the market participants which should include cancels with CR approvals. ERCOT will provide at August RMS full statistics involving market participants broken down per issue type. ERCOT is directed that if the TDSP provides file names, ERCOT will locate and re-process if it is a valid transaction. RMS directs the TDSPs and CRs to provide transactions or information necessary to achieve the completion of the data clean-up.

23. 23 Pre-TX Set 1.5 Data Clean Up

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

25. 25 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 then 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.

26. 26 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 Next Steps: ERCOT to coordinate corrective actions to TDSP ERCOT will continue to report progress at each RMS meting

27. 27 Ongoing Transaction Data Clean Up

28. 28 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

29. 29 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 still has approximately 35 either in progress or needing further clarification from TDSPs 41 FasTrak issues: ─27 Resolved (spanning 40 switches) ─13 In Progress (some dialog has occurred) ─1 Not Started (no feedback) Customer Protection Period and 814.08 (Phase 1 – Potentially Missing 08s)

30. 30 January 7, 2004 Status Customer Protection Period and 814.08 (Phase 1 – Potentially Missing 08s)

31. 31 Customer Protection Period and 814.08 (Phase 1 – Potentially Missing 08s)

32. 32 Other Status Items Matrix of FasTrak issues not yet resolved provided to RMS Chair/Vice Chair on Nov 6 th, Dec 4 th and Jan 6 th - included CR names ERCOT has “processed” all email exchanges related to FT issues as of 01/06/04 Concern that ERCOT is not being informed of “resolution” in some cases. Next Steps ERCOT to continue to escalate missing responses ERCOT to complete manual corrections related to Scenario 1 CRs and TDSPs make decisions on outstanding FasTrak issues and provide response to ERCOT via FasTrak and Email Customer Protection Period and 814.08 (Phase 1 – Potentially Missing 08s)

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

34. 34 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 ERCOT sent lists to 4 TDSPs and 12 CRs on 12/23-24/2003 requesting responses by COB 1-6-04 ERCOT received responses from all MPs except CPL Retail, Direct Energy, Entergy Solutions and WTU Retail ERCOT compiled the following matrix from the responses received Customer Protection Period and 814.08 (Phase 2 – Potentially Late 08s)

35. 35 January 7, 2004 Status Customer Protection Period and 814.08 (Phase 2 – Potentially Late 08s)

36. 36 Next Steps CRs to provide outstanding responses to ERCOT Once initial responses are received:  Scenario (1) - ERCOT to begin manual corrections – this will require input from the TDSP on their REP of record history  Scenario (2-7) - ERCOT to provide email information to CR’s and TDSP describing potential out-of-sync situations. CRs and TDSP to determine if further action is required and initiate FasTrak issues as needed  Scenario (8) - Considered in-sync with no further action required Customer Protection Period and 814.08 (Phase 2 – Potentially Late 08s)

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

38. 38 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. Volume: 867s received on Canceled Service Orders

39. 39 867s received on Canceled Service Orders

40. 40 Proactive Measure: ERCOT will compile transaction data related to the situation described above and on a weekly basis submit an ERCOT initiated FasTrak issue with the TDSP identified as the Resolving Party. The TDSP is to provide a response for each FasTrak line item within the issue spreadsheet: 1.The service orders are Canceled in the TDSPs system - the TDSP should update the FasTrak issue spreadsheet accordingly. No further action is necessary. 2.The service orders are Complete in the TDSPs system - identifying an out-of-sync condition with ERCOT. The TDSP would then initiate an effort to clear the out- of-sync condition. (see ERCOT proposal for resolving out-of-sync conditions) Timing and Implementation: ERCOT initiated this process on November 7, 2003 Each Friday thereafter, ERCOT has provided a list to the TDSPs via FasTrak containing data for 867s received against Canceled Service Orders for the previous seven days ERCOT is awaiting RMS direction for process completion 867s received on Canceled Service Orders

41. 41 Considerations for clean-up of Out-of-Sync Situations : CRs receive both completing and cancellation information on service orders and should initiate an inquiry to the TDSP any time they see both on the same service order (they should not wait for this process) Additionally, CRs who submit an enrollment transaction receive a Service Order extract identifying the ERCOT Siebel status of the transaction Use of a “modified” Inadvertent issue process has not been a great success in the missing 08 clean-up effort Precise rules allow for definitive understanding of how each Market Player will respond but does not circumvent the ability for ad-hoc corrections 867s received on Canceled Service Orders

42. 42 ERCOT Proposal for Handling Out-of-Sync Conditions : For: ▪ Canceled  Canceled by Customer Request  Canceled by Customer Objection  Unexecutable  Rejected by the TDSP Process: The TDSP will cancel the service order in their system. For:▪ Canceled Permit Not Received  Canceled with Exception Process: When TDSP indicates service order should be completed, ERCOT will locate and reprocess transactions identified as sent by the TDSP to complete a service order. (May require TDSP to re-send transaction) NOTE: FasTrak is the mechanism to handle exceptions to the above policy 867s received on Canceled Service Orders

43. 43 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 Next Steps ERCOT to discuss outstanding issue with TDSPs and determine resolution

44. 44 NAESB EDM v1.6 Update

45. 45 NAESB EDM v1.6 ERCOT Testing Status Current Progress:  Phase 1 - ERCOT and TDSP – Testing is complete  Phase 2 - ERCOT and CR – Scheduled to run from January 5 th through January 22 nd (Week of January 26 th reserved for any necessary rework…)  Issue on MIME Content-type – sent to TDTWG for resolution Future:  Phase 3 - TDSP and CR - Scheduled to begin February 16 th Note: Flight 0104 New CRs will be handled by existing third party service providers already certified on NAESB v1.6

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

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

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

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

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

51. 51 Progress –Working on Implementation Plan –Working on Post Implementation Success Criteria Market Coordination Team for the Solution to Stacking

52. 52 MP Progress Tracking –All Market Participants have been requested to provide a monthly status on their progress with the Stacking effort –Market Participants are being asked to provide their own status, no default to Service Provider status Large dependency on Business Rules Back end system modifications EDI changes relatively small –Progress will be reported through April, 2004 Market Coordination Team for the Solution to Stacking

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

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

55. 55 Market Coordination Team for the Solution to Stacking 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.

56. 56 Market Coordination Team for the Solution to Stacking Production Implementation Timeline Test Flight 7/23 2004 4/1 2004 5/17 2004 Production Implementation Date: 8/1/2004 10 weeks Draft of Implementation schedule and plan due 5/3 2004 Final of Implementation schedule and plan due Testing checkpoints at wks. 5 & 8 Connectivity 4/23 2004 Beginning of Test Flight

57. 57 Next Steps –Continue working with TTPT to develop test scripts MCT will review scripts being developed by Script Sub-Team –Continue to Track Market Participant Progress –Educational Seminars as requested –Develop Production Implementation Plan –Develop Transition Plan for Service Orders ‘In Flight’ –Develop Post-Implementation Success Criteria Market Coordination Team for the Solution to Stacking

58. 58 Load Research Update

59. 59 Updated LRS Project Timeline October – December 2003 January 2004 February 2004 -- Completion 1/15/04 TDSPs starts ordering IDRs 05/15/04—05/31/2004 Market test validation for IDR files – TDSP and CR 01/31/04 Install Load Research Software (current) 06/01/04 Start posting IDR data for CRs IDR Installation Complete at TDSPs - 6 months after sample set selection 12/05/03 Meeting with CRs & TDSP 1/15/04 TDSP validate samples and send installation schedule 01/31/04 Install Statistical Software (current) 02/04 Start receiving sample IDR data from TDSPs 1/31/04 Target for finalized sample selection 1/31/04 Finalized TDSP IDR installation schedule 10/16/03 Present timeline to RMS 10/08/03 Administer TDSP survey 10/23/03 Meeting #1 with TDSPs 11/06/03 Meeting #2 with TDSPs 11/17/03 TDSP IDR format agreement 12/1/03-1/15/2003 TDSP Handshake test for FTP replacement 11/15/03 Administer CR survey 1/5/04 Design and select TDSP samples 04/15/04 Complete Development for LRS solution at ERCOT 2/1/03-2/28/2003 CR Handshake test (on- going)

60. 60 LRS Project Updates Market Updates –A sign-up form has been sent to CRs and MOU/EC (Municipally- Owned Utilities and Electric Cooperatives) via ERCOT client reps. Due date is 1/31/2004 back to ERCOT client reps. Sign up for Day 1 data transmission MOU/EC can sign up for program AFTER day 1 and ERCOT will make data whole –LRS Project has created a web site under Load Profiling area on ERCOT main web page for LRS project information http://www.ercot.com/Participants/loadprofiling.htm –FAQ for LRS project has been created and posted on LRS web site ERCOT Updates –ERCOT software is currently being installed and tested –ERCOT development for LRS solution is currently on schedule

61. 61 LRS Project Information and Issues LRS Project Issues –Target sample design delivery has slipped from 1/5/2004 to 1/28/2004 (next PWG meeting) due to volume of analysis, as well as ERCOT staff working on higher priority tasks: IDR Threshold Analysis, Annual Validation, and Review of TDSP filings and participation in Price to Beat Hearings –1 TDSP outstanding to complete handshake test. Market Information –TDTWG and PWG endorsement of the following: TDSP –"All interval data IDR files for Load Profiling Sample purposes transmitted from TDSP to ERCOT will use FTP Replacement such as to not interfere in any way with mechanisms used to support ERCOT Billing and Settlement". –"TDTWG would like to recommend that the Market eventually move to one data transport mechanism to support all interval data IDR types of data files sent to ERCOT". CR: –"All interval data IDR files for Load Profiling Sample purposes transmitted from ERCOT to CR will use FTP Replacement such as to not interfere in any way with mechanisms used to support ERCOT Billing and Settlement". –"TDTWG would like to recommend that the Market eventually move to one data transport mechanism to support all interval data IDR types of data files sent from ERCOT".

62. 62 Flight 0104 Status Report

63. 63 Flight 0104 Status Report 8 new CRs signed up for Flight 0104 23 current CRs signed up to test the DNP script At the orientation meeting 12/3/04, ERCOT stressed that any new CR coming into Flight 0104 needs to recognize that they will need to have two efforts being performed in tandem –Working on Flight 0104 –Working on understanding the market changes that are coming for Flight 0504 V2.0 Solution to Stacking. ERCOT informed each new CR that they would be REQUIRED to test again in Flight 0504

64. 64 Market Participant Survey 2004

65. 65 Survey Objective Receive structured feedback on the perceptions and expectations of Market Participants Allow ERCOT to assess the organizational alignment between itself and the market it serves Receive feedback from multiple levels in the market Demonstrate that ERCOT is interested in listening to concerns and comments of Market Participants Ensure that ERCOT’s corporate culture includes the proper degree of service mentality

66. 66 Survey Development Process Selected market research firm – Opinion Dynamics Introduced firm to HR and Governance Committee – December meeting Interviewed 21 Market Participants from various levels for the development of the survey tool Received input from ERCOT officers and directors on the development of the survey tool Worked with ERCOT Client Services to identify targeted Market Participants for interviewing

67. 67 Firm Selection & Qualifications Sent RFP to four firms Used eight criteria for the selection process Selected Opinion Dynamics – Cambridge, Massachusetts –Pure market research firm –Has extensive experience in the utility sector –Has worked with NYISO for three years

68. 68 Project Plan

69. 69 What We Plan To Do With The Survey Output Present survey results to ERCOT Board, market committees, and ERCOT staff Identify patterns or themes associated with root causes Develop method to move the customer service “meter” to a higher level Establish a dialogue with Market Participants on prioritizing action items

70. 70 December Summary: CR Data Extract Variance Reporting

71. 71 December CR DEV Reporting 13 of 73 Competitive Retailers Reported Numbers by the due date for January (01/06/04). Numbers for February RMS (January Reports) are due by February 3, 2004. Goals for next month: –More CRs Reporting –ERCOT will break numbers out by TDSP

72. 72 Totals – All TDSPs

73. 73 Thank You