1. Rob Connell May 29, 2002 Retail Sub-Committee Update

2. 2 Objectives Update on PTB Synchronization Plan –Status on synchronizing the CR of record Provide Update from Previous RMS issues –Portal Performance and Changes –IDR / Non IDR Meter Usage Reports –867-03 Forwarding Updates Information on Enhanced MP EDI Reporting Effort

3. 3 PTB Synchronization Plan To address the current market issue with the rep of record getting out of synch between ERCOT, TDSP and CR systems. The transition to AREP process identified some of these, and the Move In and Move Out “safety net” processes, market gaps and various system issues have caused many more. The objectives of this project are to provide a plan to; –Identify the size of the problem –Provide root causes and options for correcting (if available) –Develop and implement a technical plan to synchronize databases The Non-PTB (Over 1 MW) ESI Ids are being addressed through another process.

4. 4 Market Synchronization Update RMS synchronization plan was approved at TAC unanimously Kick off Conference Call meeting took place 5/21 a) Minutes distributed 5/22 Most TDSPs and CRs have identified at least one business and one technical contact to work with ERCOT All parties agreed to action plan: a)Each MP will ensure internal/provider systems are synchronized b)A test run will occur to ensure queries and file layout are correct c)This test run begins on May 29 th and will complete by June 7 th

5. 5 PTB Synchronization Plan - Next Steps Market continues to support plan with appropriate technical and business resources being assigned. Test files will be processed by ERCOT and finalize format and comparison programs verified. ERCOT will work with MPs to correct any file format issues. Pull together a detailed project plan to evaluate differences at a point in time and document steps required to correct Full data send/analysis will take place once test run is complete Report through RMS

6. 6 Questions

7. 7 Portal Performance History (Find ESI IDs) May 29, 2002 Total hits per week Unsuccessful hits

8. 8 Portal Performance Items Mux E Way fix from Seebeyond on week of 3/30 –Saw a temporary 7 % improvement Moved Portal E Ways to New Hardware week of 4/13 –Saw a temporary 10 % improvement Added components (threads) on 4/25 –Showed some very promising improvements Additional Architecture change was made 5/21 –Removed TCH component competing with batch transactions –Seeing a 30% improvement in errors –Also added “heartbeat” functionality to verify EAI every minute Looking at 2 additional improvements currently being tested –Moving Siebel queries directly to Oracle –Improvements in redundancy for find transactions Future options also being evaluated –Additional redundant paths for Portal transactions –Continue to analyze errors and respond

9. 9 Questions

10. 10 IDR Meter Usage Report (data submitted 8 weeks following Trade date)

11. 11 IDR Meter Usage Report (as of 5/28/02) Percent of IDR accounts received by ERCOT since August * NOTE: ERCOT (and REPs) may have received additional non-sequential data (i.e, February data before January data). ERCOT rejects all meter reads that introduce gaps in the database 95% or better expected 63%

12. 12 NIDR Meter Usage Report Percent of NIDR accounts received by ERCOT since August 95% or better expected

13. 13 Questions

14. 14 867-03 Forward Update Data Provided on Existing MP Reports will allow reconciliation

15. 15 867-03 Forward Update ERCOT Data for May 1 to May 26, 2002 –5,557,189 Usage transactions received at ERCOT –99.91% forwarded, 5,551,739 transactions –5,776 Not forwarded due to invalid forwarding Duns numbers

16. 16 867-03 Forwards – Sample Timings RUN_DATETRANS_TYPETPTNER_IDTRANS_NOTransaction Mapping StatusSIID CPL to ERCOT (AES is FWD Receiver) - Inbound Time of Processing 2:20 PM 5/1/2002 ERCOT to AES - Outbound Time of Processing 3:22 PM 5/1/2002 5/1/2002 3:22:02 PM867_038797234681000946160330020020430221752521940Accept10032789481815780 5/1/2002 2:20:51 PM867_03007924772946160330020020430221752521940Accept10032789481815780 TNMP to ERCOT (REL RETAIL is FWD Receiver) - Inbound Time of Processing 7:53 AM 5/2/2002 ERCOT to REL RETAIL - Outbound Time of Processing 8:13 AM 5/2/2002 5/2/2002 8:13:16 AM867_0379953091520020502867000033Accept10400514015920001 5/2/2002 7:53:06 AM867_0300792944120020502867000033Accept10400514015920001 REHLP to ERCOT (CALPINE is FWD Receiver) - Inbound Time of Processing 9:48 PM 5/3/2002 ERCOT to CALPINE - Outbound Time of Processing 10:16 PM 5/3/2002 5/3/2002 10:16:10 PM867_031127108761000REL86703A20020501202634Accept1008901000140140013100 5/3/2002 9:48:53 PM867_03957877905REL86703A20020501202634Accept1008901000140140013100 CPL to ERCOT (CORAL POWER is FWD Receiver) - Inbound Time of Processing 11:30 PM 5/4/2002 ERCOT to CORAL POWER - Outbound Time of Processing 11:44 AM 5/4/2002 5/4/2002 11:44:50 AM867_039375172661000944084541020020503223704326835Accept10032789412332150 5/4/2002 11:30:05 AM867_03007924772944084541020020503223704326835Accept10032789412332150 CPL to ERCOT (DYNEGY is FWD Receiver) - Inbound Time of Processing 12:56 PM 5/10/2002 ERCOT to DYNEGY - Outbound Time of Processing 2:20 PM 5/10/2002 5/10/2002 2:20:41 PM867_03009924445943008693020020509230139716714Accept10032789483089721 5/10/2002 12:56:53 PM867_03007924772943008693020020509230139716714Accept10032789483089721

17. 17 867-03 Forwarding ERCOT believes we are forwarding all 867s that have forwarding information provided ERCOT provides 867 forwarding information on the current MP reports to facilitate reconciliation ERCOT samples of turn around time are well within protocols Next Steps –Should point to point 867 continue? –If MPs believe ERCOT is not properly forwarding 867-03s, provide Examples for ERCOT to check

18. 18 Questions

19. 19 Questions