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

2. 2 Objectives Provide Update from Previous RMS issues Review ERCOT proposal for Market Notification of System Changes Information on PTB Synchronization Plan Information on Enhanced MP EDI Reporting Effort

3. 3 Update on Previous RMS Issues Portal Performance and Stability Status of Loading TDSP Meter Read Data Information on PTB Synchronization Plan Information on Enhanced MP EDI Reporting Effort

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

5. 5 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 –Showing a very promising improvement –Starting Last Thursday, and Excluding the weekend and Monday, our error rate has been below 3% –Our error rate today (4/30) up to this point is below 1% –Monday is not included because of issues relating to the Lodestar migration over the weekend, which created more errors than are typical –4/25 - 2%, 4/26 3%, 4/27 4%, 4/29 25%, 4/30 less than 1 % Additional Architecture change in progress

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

7. 7 IDR Meter Usage Report (as of 4/30/02) Percent of IDR accounts received by ERCOT since August 95% or better expected

8. 8 NIDR Meter Usage Report (as of 4/30/02) Percent of NIDR accounts received by ERCOT since August 95% or better expected

9. 9 Market Notification System Changes ERCOT Proposed Policy –As part of ongoing Commercial Application Systems maintenance, ERCOT will provide written notification to the Market of all production system changes that have the potential to impact market systems. ERCOT will notify the market up to 10 business days in advance of the change, when possible, noting that for emergency changes, we will notify in advance if practical.

10. 10 ERCOT System Changes Returned expiration of switch transaction back to 20 days was implemented last week. Automated 867 loading and enhanced error reporting to be implemented this week EDI files must contain a single type of transaction, will begin rejecting mixed files (814s and 867s together) in mid May ERCOT will implement outbound edi file size limits (less than 20 Mg) based on number of transaction per file in mid May

11. 11 Questions

12. 12 PTB Synchronization Plan Based on a market presentation to RMS on April 2nd and information provided by market participants, there is currently a market issue with the rep of record getting out of synch between ERCOT and various MP 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. This plan will focus on the PTB (Price to Beat) ESI Ids The objective of this project is to provide a plan to; 1) quantify the number of ESI Ids that are at issue, and 2) document the steps required to synchronize the rep of record in all systems ESI Ids as MPs are addressing the Non-PTB (Over 1 MW) ESI Ids through another process.

13. 13 PTB Synchronization Plan Business Objectives: To quantify the current situation on ESI IDs where the rep of record is out of synch between the MPs – TDSPs, ERCOT, and CRs. Document a plan and approach to perform a technical analysis of the differences. Document the impact of the “safety net” on the market gap. Document the business support and decisions needed to implement a resolution to the gap; including: criteria to resolve differences, date issues like meter read, and include assessment of customer impacts. Document “potential” wholesale impacts on existing gaps and impacts if gaps continue. Develop and recommend an on-going process to synchronize the Rep of record once this plan is complete.

14. 14 PTB Synchronization Plan - Next Steps Market supports plan with RMS and TAC approval. Appropriate technical and business resources are assigned. The quantity is identified and technical process developed to synch the ESI Ids. The causes can be identified and documented. Business decisions to apply corrections can be made in a timely manner. Report through RMS

15. 15 Questions

16. 16 Trading Partner Transaction Reports ERCOT implemented daily EDI transaction reports for all market participants in October, 2001 Reports purpose was to provide information to the MP on all files received and posted to MPs mailboxes. Reports delivered to FTP Reports folder Reports include file and transaction information for 24 hour period previous day Reports provide MP with data to verify daily processing

17. 17 Trading Partner Transaction Reports Current MP Report is a PDFCurrent MP Report is a PDF Report shows inbound and outbound file level informationReport shows inbound and outbound file level information File name as sentFile name as sent File size as encryptedFile size as encrypted File sent/received timeFile sent/received time Report shows transactional activityReport shows transactional activity ISA control numberISA control number GS control numberGS control number ST countST count Transaction type and Texas set suffix (if available).Transaction type and Texas set suffix (if available). FA Sent flag (Y,N)FA Sent flag (Y,N) FA received flag (Y, N)FA received flag (Y, N) FA status flag (R, A)FA status flag (R, A)

18. 18 Trading Partner Transaction Reports Based on requests from MPs, ERCOT is proposing enhancing MP reports to provide additional information By adding Transaction ID, process can be modified to provide same date and time stamp information for the transaction initiator for times sent and received to processing TP –Example – Switch A from CR to ERCOT, then ERCOT to TDSP and received back at ERCOT.

19. 19 FTPFTP INITIATINGENTITY 814 data out 814 data in ArchiveArchive FTPFTP PGPPGP ArchiveArchive PFPF PGPPGP All report points SeeBeyondSeeBeyond SIEBELSIEBEL PFPF TCHTCH  Life Cycle data will span several days  CSV files will contain data  Based on only 3 rd party matching and GPID  Reports will be pushed once a day and report for the previous day

20. 20 MsgBMsgB INITIATINGENTITY 814 data out 814 data in ArchiveArchive MsgBMsgB PGPPGP ArchiveArchive PFPF PGPPGP FTP Replacement – Impact All report points SeeBeyondSeeBeyond SIEBELSIEBEL PFPF TCHTCH  The Message Broker plug-in has no impact on reporting life cycles  Provides secure guaranteed delivery  Provides reliable transport  Provides logs for both ERCOT and MPs  Provides methods for MPs to retrieve archived data at will.

21. 21 Market Reports - Next Steps ERCOT will work with MPs to refine requirements for enhanced reporting Based on input, ERCOT will develop the new functionality Plan to deploy enhanced MP Reports in under 45 days

22. 22 Questions