Retail Sub-Committee Update

Robert Connell June 14, 2002

2

Updates for RMS on June 14, 2002

• 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

• Status of ERCOT TCH Performance Issue

• Update on Enhanced MP EDI Reporting Effort

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

• RMS synchronization plan was approved at TAC unanimously– All MPs will participate

• Project was Kicked off on 5/21– Minutes distributed 5/22

.

4

Market Synchronization Update

I. Phases of project:

a) Complete an internal clean-up of systems

b) Complete a test run of data extracts from MPs

c) Complete a comparison of all records with date begin on or after April 1st

d) Categorize results and determine technical solution to synchronize records

II. Status:

a) ERCOT internal clean-up is in progress

a) Several data entry people are in the process of correcting Siebel data

b) 30,000 records have been identified with the TDSP as LSE as the CR of record

b) Test run is in progress

a) 100% of the TDSPs have submitted test files

b) 50% of CRs have submitted test files

c) Functional and technical review has been completed on all files submitted

d) Test run will complete June 21st

c) Full data comparison will begin June 28th

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

Questions

7

Portal Performance History (Find ESI IDs) May 29, 2002

Total hits per week

Unsuccessful hitsWeek By Week ESIID Hits Versus Errors

0

5000

10000

15000

20000

25000

W/E1/5

W/E1/12

W/E1/19

W/E1/26

W/E2/2

W/E2/9

W/E2/16

W/E2/23

W/E3/2

W/E3/9

W/E3/16

W/E3/23

W/E3/30

W/E4/6

W/E4/13

W/E4/20

W/E4/26

W/E5/4

W/E5/10

W/E5/18

W/E5/24

Week Ending

Hit

s

24% 14% 31% 22% 26% 28% 16% 5% 13%18% 11% 22% 9%13% 14% 25% 15% 14% 7% 9% 13%

8

Portal Performance Find ESI IDs) Week Ending 6/8/02

ESIID Success Versus Failure W/E 6/8/2002

0

500

1000

1500

2000

2500

3000

3500

4000

4500

Sunday Monday Tuesday Wednesday Thursday Friday Saturday

Hits

Errors

9

Portal Performance Find Transaction Week Ending 6/8/02

Find Transaction hits Versus Errors W/E 6/8/2002

0

500

1000

1500

2000

2500

3000

Sunday Monday Tuesday Wednesday Thursday Friday Saturday

Day of Week

Hits

Errors

10

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

• Implemented additional redundancy improvements 6/8– Improvements in redundancy (6) for find transactions– Limited the result set to 500 transactions

• Future options also being evaluated– Moving Siebel queries directly to Oracle– Additional redundant paths for Portal transactions– Continue to analyze errors and respond

11

Questions

12

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

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

Market CPL Reliant TNMP Oncor WTU

% ID

R in

Lod

esta

r

12-Oct-01

7-Dec-01

1-Feb-02

29-Mar-02

26-Apr-02

24-May-02

7-Jun-02

Expected

13

IDR Meter Usage Report (as of 6/13/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

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

8/3 8/17 8/31 9/14 9/28 10/12 10/26 11/9 11/23 12/7 12/21 1/4 1/18 2/1 2/15 3/1 3/15 3/29 4/12 4/26 5/10 5/24 6/7

Date

Per

cen

t

Market

CPL

Reliant

TNMP

Oncor

WTU

Expected

95% or better expected

66%

14

IDR Meter Usage Report (date through which 99% of data received)

CPL 26-Oct-01Reliant 12-Oct-01TNMP 23-Nov-01Oncor 14-Sep-01WTU 4-Jan-02Market 28-Sep-01

15

NIDR Usage Loaded

0.0%

10.0%

20.0%

30.0%

40.0%

50.0%

60.0%

70.0%

80.0%

90.0%

100.0%

CPL CPE TNMP Oncor WTU Market Expected

Market Participant

%

08/31/01

10/31/01

12/31/01

02/28/02

4/31/2002

06/11/02

16

Questions

17

ERCOT TCH System Issue

• ERCOT notified market June 6th technical call

• Provided written update on June 11th on slow down in our TCH system impacting 814s and 867-04s

Due to this slow down in processing over the past 7 days ERCOT has received 153,807 Initiating 814 transactions and has sent 53,911 814 response transactions leaving 99,896 transactions still to be processed. Additionally, ERCOT has received 378,853 814_20’s and has only been able to send 9,851 814_21 response’s which leaves 369,002 transactions still to be processed.

18

ERCOT TCH System Issue Resolved

• ERCOT resolved the TCH problem and reported to the market on technical call (2 PM 6/12) that we were processing normally again

• Agreed with market to process newest transactions first

During resumed processing, ERCOT processed over 111,000 transactions in 12 hours, all current transactions (last 2 days are processed) and expects to be fully caught up by Sunday 6/16.

• Forwarding 867-03s were not impacted, and 867 meter data being loaded to Lodestar was not affected.

• Internal Post Mortem has been conducted

19

Questions

20

Trading Partner Transaction Reports“Dark Side of the Moon” Files

• 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

21

FTPFTPFTPFTP

INITIATINGINITIATINGENTITYENTITY

814 data out814 data out

814 data in814 data in

ArchiveArchiveArchiveArchive

FTPFTPFTPFTP

PGPPGPPGPPGP

ArchiveArchiveArchiveArchive

2 3 4 5

PFPFPFPF

PGPPGPPGPPGP

6

All report points All report points

1

78

SeeBeyondSeeBeyondSeeBeyondSeeBeyond

SIEBELSIEBELSIEBELSIEBEL

PFPFPFPF TCHTCHTCHTCH

910

Life Cycle data will span several daysLife Cycle data will span several days CSV files will contain dataCSV files will contain data

Based on only 3Based on only 3rdrd party matching and GPID party matching and GPID

Reports will be pushed once a day and Reports will be pushed once a day and report for the previous dayreport for the previous day

22

Market Reports - Next Steps

• ERCOT has worked with MPs to refine requirements for enhanced reporting

• ERCOT has completed development of the new functionality

• Currently working on User guide for full explanation of the reports and how to use the data effectively

• Plan to deploy enhanced MP Reports in next 2 weeks

23

Questions

24

Questions