1. 1 Update from ERCOT Retail Market Services to RMS March 20, 2003

2. 2 Retail Market Update Topics –GISB 1.4 Update –Market Participant Testing Flight Test V1.5 Overview –Texas Set Version 1.5 –ERCOT Data Transparency –Move-In/Move-Out Task Force

3. 3 Data Transport in the Texas Market GISB 1.4 Update

4. 4 Review of Transport Options FTP - Currently primary option for all MPs to ERCOT –No guaranteed delivery, some security concerns HTTPS – ERCOT replacement for FTP –Guaranteed delivery, improved security GISB 1.4 – Primary option for MPs on point to point –Guaranteed delivery, same security issues as FTP GISB 1.6 – Primary transport for 2004 Texas market –Guaranteed delivery and improved security

5. 5 ERCOT Testing/Migration Team ERCOT team working closely with MPs on connectivity and GISB 1.4 EDM testing Testing schedules and issues being addressed at Texas Data Transport Working Group based on market rules ERCOT Team includes: –Clay Katskee Connectivity Test Coordinator - Primary –Nagaraju (Naga) Valasagandla – Secondary –Dave Farley Manager Transaction Services (IT) –Adam Martinez Project Manager (IT)

6. 6 GISB EDM 1.4 Migration Status Production Migrations in progress –1 MP in production –4 MP scheduled for migration Testing with Market Participants In Progress –21 MPs have completed testing with no issues –32 MPs have completed testing with issues identified –11 MPs are in process of testing – 3 MP testing delayed due to architecture issue Issues Impacting MP Testing include: –Improper use of MP log on and password –File naming conventions not followed ERCOT to allow “.payload” 03-22-03 –Use of non unique file names ERCOT will compensate by appending unique prefix

7. 7 Next Steps Migration to production will be coordinated with individual MPs after successful completion of testing ERCOT is working with the MPs and TDTWG to identify and resolve issues ERCOT may not be able to resolve issues that are contrary to market rules or those that compromise system performance and proper market reporting MPs that cannot complete testing can stay with FTP until GISB 1.6 can be implemented or test the HTTPS solution for data transport

8. 8 Market Participant Testing Flight Test V1.5 Overview RMS 3/20/03

9. 9 As of 3/20 10:30 am Frame 04 – Market Moved to Frame 04 on 3/19/03 Day 1 – 3/19 Day 2 – 3/20 Day 3 – 3/21 Day 4 – 3/24 On 3/11/03 - Recommended that we reduce the number of days in the next 3 frames Frame 03 - 4 days instead of 5 (Mar 13 - Mar 18) - done Frame 04 - 4 days instead of 5 (Mar 19 - Mar 24) Frame 05 - 4 days instead of 5 (Mar 25 - Mar 28) Frame 06 - should be caught back up, 5 days per frame again Flight V1.5 – End to End Testing Progress

10. 10 Frame 04 status as of 3/20/03 CRs – 14/43 reported they’ve sent >50% of files for Frame 04 19/43 reported they’ve received >50% of files for Frame TDSPs – 4/4 reported they’ve started sending & receiving files for Frame 04 ERCOT – dependant on CR & TDSP to process transactions for Frame 04 Flight V1.5 – End to End Testing Progress

11. 11 Frame 00 Recap: TDSP – all green. CR – 42/43 green. –1 CR still red due to delays on RA001, valid status ERCOT – green Moved to Frame 01 on schedule on 2/24/03. Frame 01 Recap: TDSP – all green CR – all green ERCOT – green – need to update checklist Moved to Frame 02 on 3/6/03. Flight V1.5 – End to End Testing Progress

12. 12 Frame 02 Recap: TDSP – 3/6 green. –Rest have delays due to RA001 script. CR – 29/43 green. –Remainder have delays due to RA001 script or straggling transaction. Moved to Frame 03 on 3/14/03. Frame 03 Recap: TDSP – 4/6 green –All have reported complete, behind on checklist updates CR – 42/43 green –1 outstanding, TDSP, ERCOT & CR working to resolve Moved to Frame 04 on 3/19/03 2:30 pm Flight V1.5 – End to End Testing Progress

13. 13 RA001 script – TDSP sends multiple invoices totaling to $10 or less to CR. CR initiates live payment thru Bank. Remittance advice may travel with payment via Bank or separately (point-to- point) via GISB. TDSP refunds the dollar amount to CR within 30 days of end of test. RA001 script is scheduled for Frames 00, 01, 02, 06 & 07. Expect to have some delays due to banks. All TDSP have identified CRs who are behind schedule on the RA001 script. Flight Admin has also been in contact with each. Flight V1.5 – RA001 script overview

14. 14 Flight V1.5 - ETOD Testing Progress Frame 1 – complete Frame 2 – complete – market caught up with end-to-end testing. Frames are now progressing together. Frame 3 – complete Frame 4 – in progress Frame 5 – files posted Frame 6 – files posted Frame 7 – no files needed Flight Admin reached out to the ETOD TDSPs for additional files (to follow SR script logic – matching 867/810s)

15. 15 Flight V1.5 – Lessons Learned End to End scripts –Script improvements (RA001, frame timing) –Frame timing – education to all MP that transactions should be sent in first ½ of frame, so that response transactions can be sent second ½ of frame –BGN02 – education to all MP and better understanding of the validation done by different systems –Number of resources working at each MP site – did all parties staff appropriately? ETOD scripts –MP following end to end scripts, and not following requirements of ETOD scripts (dates, specific codes) –Files posted earlier TTPT team will have a ‘Lessons Learned’ session with Market at conclusion of flight test.

16. 16 Flight V1.5 - Notes Reminder – the market flight test progresses as fast as the slowest participant. Flight administrator will work closely with all market participants to assist and keep all market participants on the proposed schedule. Proposed schedule is one frame per week.

17. 17 Keep Things in Perspective Why do we test? –To ensure Market Processes are successfully tested according to testing criteria, procedures established by TTPT, ERCOT and market protocols A walk down memory lane –Past flights…

18. 18 Flight 3801- V1.3 Flight 1001- V1.4 Flight V1.5 AEP112339 Centerpoint132542 Entergy61113 ONCOR122842 Sharyland056 TNMP92034 Nueces/SP001 51112177 Comparison to Past Flights

19. 19 Comparison to Past Flights Total transactions – Flight 3801 – V1.3 –6940 –Expected end date – 9/5/01 –Actual end date – 9/21/01 Total transactions – Flight 1001 – V1.4 –12,350 –Expected end date – 11/23/01 –Actual end date – 12/03/01 Total transactions – Flight V1.5 –23,456 –Frame 5 expect to start 3/24 and end 3/28/03 (on schedule) –Frame 6 expect to start 3/31 and end 4/4/03 (on schedule) –Frame 7 expect to start 4/7 and end on 4/11/03 (on schedule)

20. 20 Texas Set V.1.5 Presented by: Dave Odle

21. 21 V1.5 Coordination Team – tentative conference call on 2/28 – Last task! –V1.5 Team face to face meetings are completed. –Original TASKS conceived when teamed was created in May, 2001: Increase Communication in the market for V1.5 - tremendous improvement and continuing. Establish Market Project Timeline and plan - Complete Establish clear understanding of V1.5 requirements - Complete –Numerous accomplishments Created the V1.5 website for transparency and open communication. Created the Version 1.5 mailbox for more discreet issue resolution. Created some extremely helpful documentation for everyone's use (thanks to all who did this). Worked through difficult and convoluted requirements and reached resolution on all of them. Worked through all V1.5 requirements (change controls), one by one, for clear understanding and expectation. Created the project timeline and critical milestone dates (flight testing, migration, etc.) Created the production implementation plan down to the last conference call. Pointed out the "what if's" and identified risk mitigation methods. Continuing efforts for Project Success. In Progress –Continue Efforts in open communication –Production Migration coordination –Flight Test coordination with the TTPT and ERCOT V1.5 Coordination Team Accomplishments/Goals

22. 22 Project Status Summary Exolink provides EDI services for: Republic, Calpine, Entergy Retail, Entergy Disco, GEXA Systrends provides EDI services for: Sheryland, Tenaska, Occidental, TCE EC Power provides EDI services for: AEP A-REP, SmartEnergy, Just Energy ESG provides EDI service provider for: ACN Energy, Cirro Group, Coral Energy Markets, Dynegy, Sempra Energy Solutions, Tractebel Energy Markets, UBS Warburg, Tara Energy

23. 23 Project Status Summary as of 2/20/03 DESIGN BUILD INTERNAL TEST 25%50%75% 25%50% 75% ERCOT Reliant Energy Retail TXU ES Logica Simplified Nueces San Patricio Green Mountain Exolink TNMP (TDSP) Certain Power (POLR) First Choice Power Republic XERS (Xcel Energy) ESG AEP A-Rep Sharyland Systrends TCE Tenaska/Occidental ONCOR EC Power Entergy Retail AEP TDSP Center Point Spark Energy LP Utility Choice Electric STEC Retail Constellation ASP ES = Flight Test Frame 1

24. 24 Implementation Plan Objectives –Ensure all parties know the status of the implementation effort AT ALL TIMES! –Minimize down time –Work as a team

25. 25 Initiating Transactions Shut-down Timeline 6 hrs14 hrs 6 hrs CRERCOTTDSPERCOTCR 1 am7 am 9 pm Thursday, April 10th 9 pm3 am Friday, April 11th Noon Step 1 Step 2b Step 3Step 4 Step 2aStep 5

26. 26 Sub-Initiating Transactions Shut-down Timeline CRERCOTTDSPERCOTCR 9 pm3 am 6 hrs 3 am11 am 8 hrs Thursday, April 10th 11 am5 pm 6 hrs Friday, April 11th Step 1Step 2b Step 2a Step 3 Step 4

27. 27 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_20, 814_26 8 hrs2 pm 867 7 hrs 5 pm 810 1 hr 650 Initiating will cease on Friday at 2 pm, 650 Responses will cease on Friday at 6 pm 814_PC will cease on Friday at 5 pm, 814_PD will cease Friday at 6 pm Legend CRsERCOTTDSPs = Conference Calls

28. 28 Conference Call Schedule during Migration Wednesday @ 5 PM –Initiating Transaction status/ CR processing status Thursday @ 9 AM –Initiating transactions completed/ERCOT confirms 1 AM cut-off/TDSP & CR processing health and status. Friday @ 9 AM –Sub-initiating transaction processing/ERCOT confirms Thursday 9 PM cut-off/TDSP & CR processing health and status. Friday @ 5 PM –TDSP & CR to confirm 650, 810, & 814 PtP cut-offs and processing/ERCOT to provide 867 processing status Saturday @ 9 AM –ERCOT & TDSP to report status of Migration Saturday @ 7 PM –ERCOT declares (if possible) “go/no-go”/TDSP & CR to report status Sunday @ 9 AM –TDSP & CR provide status of migration/ERCOT fall back for declaration of “go/no go” Sunday @ 3 PM –ERCOT provides time it will begin accepting V1.5 transactions/TDSP & CR provide status- decision of having another conference call.

29. 29 Next Steps Meetings for V1.5 Coordination team have concluded. Our next conference call will be held on March 28 th with the Flight Test Administrator and the TTPT to establish Flight Test status. –March 28 th (Tuesday) – Conference Call. Follow up meeting will be scheduled post April 11 th for a lessons learned analysis.

30. 30 ERCOT Data Transparency – ETS –

31. 31 ERCOT Data Transparency (PR# 30136)ETS / GISB (PR# 30136) –Implemented on March 4, 2003 –Successfully processed first MP file on March 6, 2003 (PR# 20060)ETS / TX Set 1.5 (PR# 20060) –Design and Migration documentation complete –Integration testing will start on March 25, 2003 –Implementation to coincide with TX Set 1.5 project

32. 32 ERCOT Data Transparency (PUC# 20124)Performance Measures (PUC# 20124) –Queries built for sample report –Verification underway on sample report data –Manual report generation to be done for Q1 PUC reports –Automated reporting should be available for Q2 PUC reports (PR# 30054)ERCOT Data Transparency (PR# 30054) –Further analysis required as a result of SCR727 implementation

33. 33 RMS Update on Move-In / Move-Out Task Force

34. 34 Solution to Stacking All Move-Ins, Switches, and Drop to AREPs are rejected for Not First In Move-In sent to ERCOT requesting a date of 5/16 4/29 5/16 TDSP completes Move-In TDSP sends Final and Initial read to ERCOT With the current way the market handles Move-Ins, no Move- In, Switch, or Drop to AREP transactions can be processed while a Move-In is pending. A landlord wanting to do work on a premise between tenants does not have an automated method of energizing the premise, the Safety Net must be used.

35. 35 Solution to Stacking Move-Out sent to ERCOT requesting a date of 5/16 4/295/16 Move-Out scheduled for 5/16 With the current way the market handles Move-Ins and Move- Outs, if a Move-In is cancelled, the premise could be de- energized prematurely. Move-In sent to ERCOT requesting a date of 5/10 5/10 Move-In scheduled for 5/10 Move-In cancelled by submitting CR Move-Out date automatically changed to 5/10 to align with Move-In Premise de-energized 6 days prior to the date the customer requested. Move-Out completed at TDSP

36. 36 Move-Out sent to ERCOT requesting a date of 5/16 4/295/16 Move-Out scheduled for 5/16 The solution to stacking uses rules to ensure that regardless of the order that transactions are received, all valid transactions will be worked at the appropriate time. Move-In sent to ERCOT requesting a date of 5/10 Solution to Stacking Move-In sent to ERCOT requesting a date of 5/05 5/10 Move-In scheduled for 5/10 Move-In for 5/10 cancelled by CR Move-Out automatically cancelled for ‘Not REP of Record’ 5/05 Move-In scheduled for 5/05 Move-In for 5/05 completed at TDSP Move-In requesting 5/05 changes REP of Record to new REP without de-energizing inappropriately

37. 37 Solution to Stacking Background on NFI rejects Existing Market Design  Current market design does not support multiple non-sequential transactions on an ESI ID. Volumes encountered  February 1 st through 20 th – 3.2% (300 per day) Safety – Net Manual workarounds  Relieves the effects to the customer from NFI rejects.  Causes out-of-sync system conditions.  Causes higher costs and higher potential for mistakes.  Increases quantity of orphan accounts. (increase of UFE)  Requires backdated transactions, which causes additional NFIs, out-of-sync conditions, and more manual workarounds for the TDSPs. Same CR point-to-point initiatives  Relieves the effects to the customer from NFI rejects for those transactions.  Requires that the TDSPs handle multiple non-sequential transactions.  Causes out-of-sync conditions if TDSP is not handling multiple non-sequential transactions.

38. 38 Solution to Stacking Study Approach Other market designs  ERCOT ‘Mother ship’ concept  JIT (Just in Time)  Centralized scheduling with delayed notification to ERCOT  Centralized database design Changes to existing design  Building the ability to handle multiple non-sequential transactions within the current market structure. Cost and schedule restraints of all market participants

39. 39 Solution to Stacking Proposed Design A method that allows CRs, ERCOT, and TDSPs to accept (and process) multiple, non-sequential transactions concurrently on a single ESI ID. Requires new business rules to sequence multiple transactions. May require system changes for all market participants Benefits expected  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

40. 40 Solution to Stacking 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. Summary of Changes: Manage customer expectations by accepting and processing all valid requests. Impact Level Efficiency Communication Competition

41. 41 Solution to Stacking Next Steps High Level Requirement Development and Approval  Definition being established by MIMO Task Force  Distribution to market for evaluation and comment period  Comments reviewed by MIMO Task Force  Market Educational Seminar sponsored by MIMO Task Force  High Level Requirements approval by RMS Build Phase  Timeline for implementation approval by RMS  Texas SET will be engaged in helping to develop implementation guide changes necessary to support solution  Checkpoints and Market Coordination meetings established Testing and Implementation  TTPT will be engaged in developing appropriate market testing guidelines