RMS UPDATE from ERCOT Retail Market Services July 8, 2002.

RMS UPDATE from ERCOT Retail Market Services

July 8, 2002

Retail Market Update

• Topics– Move IN and Move OUT– ERCOT Project Plan– Market Communications – Quick Recovery Team– Market Synchronization Activities

• Price to Beat and “A” Rep Cleanup

• Non-Price to Beat

• Resettlements

– FTP Replacement– “Dark Side of the Moon” – EDI Transaction Lifecycle Reports– TX Set 1.5– ESI ID Tracking System (ETS)– Portal Statistics– IDR Meter Reads

Move In and Move Out

Summary of Findings and Next Steps

Move In/Out Approach

• Identification of activities to improve the timeliness and accuracy of move In/Out transactions

– 7 Conceptual recommendations identified for follow up action…

– 2 Ideas

– 1 Proposal (same CR)

• Formalize project to develop TX Set Version 1.6 (Move In/Out Processing)– Convene Team to:

• Obtain existing market costs and deficiencies with Move In/Out Process including association of market impact with specific scenarios

• Develop detailed market requirements/specifications document for addressing full range of Move In/Out scenarios

• Develop preliminary time/cost estimates• Present findings – Make go/no-go decision• Develop request for information / request for quotation• Obtain revised time/cost estimates from vendors• Present revised findings – go/no-go decision• Develop market plan for development, testing, and Implementation

– Construct TX Set Version 1.6

– Conduct Testing TX Set Version 1.6

– Implement TX Set Version 1.6• Allow for potential “soft launch” to minimize market exposure• Provide contingency / back out plan

Move In and Move Out Recommendations (tactical)

• Conceptual Recommendations #1 Greater Transaction Visibility(John Kassel – ERCOT)

– ERCOT will develop a plan to provide visibility into the Transaction Life Cycle and ESI ID Life Cycle.

– MPs will provide their Portal requirements to ERCOT. ERCOT will combine the MPs’ requirements into a project scope of work and then seek market input into the final set of requirements.

– Consensus Achieved

• Conceptual Recommendation #2 Cancellation of Pending Switch (Cary Reed – AEP TDSP)

– MVI/MVO cancels pending Switch Transactions regardless of whether the MVI/MVO effective date is before or after the pending Switch effective date.

– Consensus Achieved

• Conceptual Recommendations #3 Holding MVI/MVO– CR Holds MVI/MVO Transaction for X-days before the actual MVI/MVO date. Current

market “rule” has a 14 business day window.– Current working group will define what “X-date” is.– Conceptual Recommendation can be implemented immediately once X-date is

defined, however it requires the CRs to “self-police” themselves on the X-date. – Long term solution would include a rejection message if the MVI/MVO was submitted

too early.– Majority Agreed with some not agreeing– NOT BEING PURSUED (Don Bender)

Move In and Move Out Recommendations (tactical)

• Conceptual Recommendation #4 Splitting MVI from Switch(Carl Grossardt – AEP Retail)

– ERCOT forwards 814_16 (MVI Request) to TDSP and does not translate them into an 814_03 (Switch Request).

– Only Switches will be translated into 814_03 (Switch Request).– CRs would receive a 814_05 (Enrollment Response) for both Switches and MVI.– CSAs need to be investigated.– Consensus Achieved

• Conceptual Recommendations #5 Safety Net MVI– Quick Response Team should research if improvements can be made such that an

814_16 (MVI Request) transaction can be processed putting the market model into motion.

– A potential Idea is for CRs send their Safety Net MVI to ERCOT using spreadsheets, CSV or other options as deemed appropriate. ERCOT updates their systems and transmits to the TDSPs.

– Consensus Achieved– NOT BEING PURSUED (Don Bender)

• Conceptual Recommendation #6 NFI Rejection Codes (Lan Conn – Entergy)

– NFI rejection text needs to clearly define the reason for NFI rejections.– ERCOT creates the appropriate logic to identify NFI situations and develop associated

NFI rejection codes/text.– Preliminary Draft “Straw man” due to ERCOT by 7/17– Consensus Achieved

Move In and Move Out Recommendations (tactical)

• Conceptual Recommendations #7 Expedite ESI ID (Dave Farley - ERCOT, Darrell Hobbs - Oncor)

– TDSPs and ERCOT to develop an expedited ESI ID creation process.

• Automate the separation and prioritization of 814_20 Create and Retire Transactions from 814_20 Change Transactions (Implement by 7/8)

• Darrell Hobbs to manage identification of key fields for subsequent separation of 814_20 Change transactions

• Preliminary Draft “Straw man” due to ERCOT by 7/17

– Consensus Achieved

Move In / Out - Idea #1Eliminate Initial Meter Reading Transaction

• ERCOT (John Kassel) will review elimination of the 867_04 (Initial Meter Reading) and using the 814_04 (Switch Response) to close the business process instance or other options as appropriate. (BPI).

Move In / Out - Idea #2 Relaxing NFI Logic

• ERCOT (John Kassel) will review the relaxation of NFI logic upon receipt of 814.04 instead of 867.04.

• This Idea would establish the business relationship for that ESI ID. This Idea does not affect the establishment of the relationship for settlement purposes. The effective relationship continues to be established via 867.04.

ERCOT Move In / Out Proposal Same CR MVI

• MVI/MVO working group explored this idea and made the following observations.

– Defer further action until ERCOT (John Kassel) reports to RMS on their discussions with TDSPs.

– The concept proposed by ERCOT would be interim and optional for any CRs. The proposal addresses current market operational problems with the volumes of MVI/MVO when the same CR is involved. If current market conditions change, this concept may not be viable.

Move In and Move Out

One plan will be developed that integrates all of the activities covered here

ERCOT Master Project Plan

Overview

ERCOT Master Project Plan

• Key In-flight & Feld Group Projects Identified– Master project plan established– Project worksheet established

• Status/Updates

• Targeted outcomes

• Resources required

• Next Steps…– Leverage ERCOT Steering Committee to:

• Ensure completeness of project list

• Establish priorities and dependencies

• Review resource requirements

– Provide Updates/Visibility on key market projects– Obtain Feedback from Market Participants– Present to ERCOT BOD and obtain support

Retail Market Communications

Overview

Retail Market Communications

• Objective– Provide proactive communications between ERCOT and Market Participants

• Progress– Twice Weekly Technical Conference Call

• Polled Market Participants on effectiveness and content

• New moderator and revamped agenda

• Agenda prepared and distributed prior to meetings

• Proactive status reporting by all Market Participants

• Minutes from each call distributed

• Follow-up on outstanding issues/questions addressed on next call

– Outcome: Positive feedback, increased participation, better communication among all participants

Retail Market Communications (Continued)

• ERCOT Retail Transaction Processing Updates– Proactive communication to all Market Participants when transaction

processing is adversely impacted – Updates distributed to retail client relations and registration contacts:

• Transactions affected

• Short description of the event/issue

• Identification of Market Participants affected

• Is the forwarding of 867_03 to CR affected?

• Detailed technical description of the event/issue

• ERCOT’s plan of action to resolve

• Follow up – when will ERCOT provide the next update

• Please provide feedback and suggestions on Retail Market Communications to:

– Nancy Hetrick 512-248-3875 [email protected]– Karen Bergman 512-248-3171 [email protected]

Quick Recovery Team

Progress Update and Next Steps

• Issue– Missing or Out of Sequence Transactions are Preventing CRs from Creating Accurate

and Timely Customer Bills

• Approach– Create a 30 Day Effort/Team Focusing ERCOT and Market Participant Resources to

Identify and Correct Missing/Incorrect Data

• Objectives– Improve Creation of Timely and Accurate Retail Bills

– Recover and Clean Up Historical Move In/Move Out Transactions and Switches

– Improve Monitoring and Visibility into Processing of Current Move In Transactions

– Investigate and Address Processing of IDR Usage Data

– Provide Reporting/Metrics on Activities Performed

Quick Recovery Team Update

• Number of ESI IDS Identified: 91,869– Resolved ESI 7,415– Analysis Begun on: 8,291– In Progress 32,751– New 43,412

Quick Recovery Team Update

1) Provide more equitable workload distribution

2) Take ownership in resolving ESI ID from start to finish – “the whole process”

3) Develop relationship and communication with Registration Analyst

4) Develop relationship and communication with CR/TDSP

5) Provide consistency and continuity for CR

6) Provide consistency and continuity in issue resolution

7) Focused priorities to ensure issues get worked according to CR needs

8) One point of contact for Management

9) Reduce impact of vacationing QRE Team Members

Quick Recovery Team Re-Structuring Objectives

David Gonzales•First Choice Power/•TNMP•Tractabel

Denise Taylor•Green Mountain•GEXA

Julie Doan•Republic•AES New Energy•Oncor

Aaron Saint•Reliant Retail Tiger Team Issue•Strategic Energy

Shelley Shumbera•ACN• Cirro• Commonwealth/Electric America•Dynegy•Cinergy•Reliant Retail Tiger Team Issue

Ken Corcoran•UCE•AEP•Reliant Retail Tiger Team Issue

Matt Haggerty•TXU-ES•Calpine •Reliant Retail Tiger Team Issue

Derek Paquette•AEP Retail• Tenaska•Sempra •Reliant Retail Tiger Team Issue

Barry Hall•XERS•Texas Commercial Energy •Coral•Entergy Solutions•Reliant Retail Tiger Team Issue

Re-Structured Quick Recovery Team Assignments

Dave Farley & Clay KatzkeeAssist with •Re-dropping Transactions•Ensuring Files were delivered successfully•Providing transmitted/received file names dates and times

Glen Wingerd•Loading QRE Submission Template to DB•Providing Queries/Reports from DB•Assist in troubleshooting resolution

Market Synchronization Activities

• Objective – Address market issues resulting in an out of sync “Rep of Record” between

ERCOT, TDSP, and CR systems for customers <1 MW

• Activities– Identify the scope/size of the discrepancies – Provide root causes and options for correcting (if possible)– Develop and implement a technical plan to synchronize databases

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

• Project was Kicked off on 5/21– Internal Synchronization Efforts for all MPs In Progress– Test files are being sent to ERCOT– Programs to Compare and report discrepancies are complete.

Market Synchronization - Price to Beat

• ERCOT internal synchronization is in progress– Corrections to Siebel and Lodestar data is in progress – This ERCOT internal synchronization process is 70% complete

• Test files and feedback on files in progress– All MPs are submitting test files– Technical review has been completed on all files submitted to date– Next round of test files will be reviewed next week

• Next Steps– Will schedule full run with MPs when

• Test files are accurate

• Internal synchronizations are substantially complete

– Meeting are being scheduled with MPs to agree on possible approaches to synchronize when the results of the comparison are analyzed

.

Market Synchronization - Price to Beat (continued)

Market Synchronization – Non Price to Beat

• Objective– Make necessary corrections to ensure that >1MW Customers were

switched on the correct date in January 2002

• Initial Statistics– Number ESI Ids (>1 MW) Identified by CR’s 1,011– Number in Sync ERCOT & TDSP 692– Number out of Sync ERCOT & TDSP 319

• Updated Statistics– Number out of Sync ERCOT & TDSP 91 – Number ESI Ids potentially requiring manual

backdating at ERCOT 236

• Progress– Contacted affected CR’s, Received a few responses– Overall Progress is Good– TDSPs working with Mike McCarty

Market Synchronization – Non Price to Beat (continued)

• Next Steps for CRs Working Directly with TDSPs– TDSPs and CRs reach agreement on the correct switch date– Submit any pertinent transactions (if applicable)– Notify ERCOT at all affected Market Participants are in agreement – Forward list of ESI Ids with agreed upon switch dates to Mike McCarty, ERCOT– ERCOT will make any necessary MANUAL changes in Siebel

• Timing Constraints– Resettlement process will begin on July 31, 2002– Any ERCOT system changes must be completed before July 31, 2002

ERCOT Board Resolution Regarding Re-Settlement(Background Information)

The ERCOT Board directed the ERCOT Staff to perform a one-time re-settlement of July 31, 2001 through the current Wholesale Settlement Statement published.  Such re-settlement will commence after ERCOT has successfully received and validated at least 99 percent of the IDR data from each Meter Reading Entity (MRE).  In addition, ERCOT would suspend future true-up settlements until the 99 percent IDR consumption data standard is met.  The true-up settlement timeline would be extended to a maximum of 12 months in cases where the IDR data threshold is not met.

In addition, TDSPs would be required to correct Load Profile ID assignments identified in the Initial Validation Process for Non-IDR ESI IDs retroactively to a meter read date prior to July 31, 2001. Such corrections shall be transmitted to ERCOT by June 15, 2002.

Passed on May 21, 2002

When to begin Re-Settlement of July 31,2001 through November 19, 2001 Trade Dates?

True-Up Settlement Already Performed

• Re-Settlement requirement is based upon Board Resolution

• Resolution Identified two components:

1. IDR Data Completeness 2. Profile ID Corrections

• Additional issues have been identified by Market Participants and ERCOT.

3. Retailer Synchronization Project

4. Resolution of outstanding disputes for OOMC

5. Lodestar to Siebel Mismatches

6. Corrections for NIDR missing or negative usage, incorrect region assignment and DLF Codes.

Re-settlement Kick-off Decision(Where True-Up Settlement Already Performed)

1. IDR Data Completeness – continuously monitored and kept in compliance

2. Profile ID Corrections – Refer to the Profile Working Group Update

3. Retailer Synchronization Project - Entities synching internal systems & sending test files to ERCOT – Entities having issues with creating test files

4. Resolution of outstanding disputes for OOMC – Pending approval by ERCOT Legal and processing of documentation by entities

6. Corrections for NIDR missing or negative usage, incorrect region assignment and DLF Codes

5. Lodestar to Siebel Mismatches – Synchronization is underway

To eliminate potential disputes, Re-settlement should take place only after resolution of the outstanding issues listed below.

(making this a “one-time resettlement” per the Board resolution)

Color of items below indicates status with respect to July 31, 2002

When to begin True-up Settlement of November 20, 2001 and forward Dates?

True-Up re-start is based upon meeting the IDR Data Threshold and the 12 month deadline to perform True-Up settlement as defined in:

a) Board Resolution to suspend True-Up settlement until IDR data threshold is reached

b) Protocol changes initiated by PRR 330

To eliminate potential disputes, True-Up Settlement should take place only after resolution of outstanding issues previously identified.

• The Protocol “12 month” deadline allows for re-starting True-Up Settlement as late as November 20, 2002.

• ERCOT expects to re-start True-Up settlement as soon as the data is received from all Market Participants

Synchronization activities going forward

• Currently Separate Projects/Activities Underway:– Price to Beat and “A” Rep clean up– Non-Price to Beat– Quick recovery effort and 20 Day expired– Daily work / “fix it” activities– Resettlements

• Synchronized Activities Characterized as:– Limited availability of personnel resources– Focused on individual issues and/or transactions– Limited cross project Interactions

• Next Steps are to Determine How Best to:– Address current pressing market needs – Leverage limited resources at both MP’s and ERCOT– Focus on the market as a whole– Prevent/Minimize future synchronization efforts

FTP Replacement

FTP Replacement Update

• Vision

• FTP Current State

• Future State

• Interim Steps

FTP Vision

ERCOT

CR TDSPGISB 1.4

FTPFTP

New CR&

NOIE

HTTPS

ERCOT

CR TDSPGISB 1.6

GISB 1.6GISB 1.6

NOIE

HTTPS

CURRENT FUTURE

Interim

ERCOT would need to maintain legacy interfaces over time as market migration occurs.

FTP Current State

• Existing FTP Solution between ERCOT and Market– Known security, reliability, and monitoring issues– Some have been worked around by MP’s and ERCOT in terms of the

reliability and monitoring– Seems to work now but a better solution is needed.

• GISB 1.4 in-place for CR-to-TDSP Interface (a.k.a. Point-to-Point)– Used in other markets

• FTP Replacement Part I (a.k.a. HTTPS)– Ready for production at ERCOT– Initial phase of project to replace FTP short-term & get to GISB/NAESB 1.6 in

the long-term– Closes GAPS around security, and reliability and provides increased

monitoring.– New CR’s and NOIE will be implemented on HTTPS going forward– Existing MP’s can migrate voluntarily– Market acceptance appears lacking for a major migration to this solution but

would entertain a GISB 1.4 and/or GISB/NAESB 1.6.

• FTP Replacement Part II (a.k.a. GISB/NAESB 1.6)– Long term effort and solution for the market

Future Vision

• GISB/NAESB 1.6 is standard interface at some point in the future

• Additionally, ERCOT would support HTTPS– FTP in it’s current state would be retired

• Expect one year or more for critical mass in terms of adoption and usage within the market

– Standard’s planned publish date is July 31 and factor in:• ERCOT, Vendor, and MP’s Home grown software development and test

• Market Testing and Certification Activities

• Market Migration Activities

• What can be done in the interim?

Interim FTP Replacement Options

1. HTTPS (a.k.a. FTP Replacement Part I)• Ready now • Relatively easy to implement for existing FTP user• Requires migration plan to move market

2. GISB 1.4• ERCOT would consider if date could be set to retire FTP• Relatively easy to implement and migrate• Requires migration plan

3. GISB 1.5• Not really viable given timing of 1.6 and current market use

4. GISB/NAESB 1.6 (a.k.a. FTP Replacement Part II)• Probably not an interim solution given all the moving parts• ERCOT needs to fund• Vendors and market participants need to plan and fund projects.

NOTE: TDTWG WILL SURVEY MARKET ON PREFERENCES AND READINESS RELATIVE TO THE ABOVE OPTIONS

ERCOT Proposal - FTP Replacement

• Continue with HTTPS implementation as needed for new CRs and NOIEs

• TDTWG would survey market on preference and estimate of readiness to support GISB/NAESB 1.6

• Implement GISB 1.4 at ERCOT within 60 days of necessary approval and funding

– Target FTP Retirement for April 1, 2003– Market participants would migrate to 1.4 under agreed to project plan

• Develop ERCOT and Market plan for GISB/NAESB 1.6– TDTWG Market Survey should give some indication of timing and readiness

for market adoption.– ERCOT would plan project accordingly to be ready for earliest adopter.– Testing and migration can be worked with TTPT– Target GISB 1.4 Retirement for Q1 2004.

0

20

40

60

80

100

Jul-0

2

Aug-0

2

Sep-0

2

Oct-0

2

Nov-0

2

Dec-0

2

Jan-0

3

Feb-0

3

Mar

-03

Apr-0

3

May

-03

Jun-

03

Jul-0

3

Aug-0

3

Sep-0

3

Oct-0

3

Nov-0

3

Dec-0

3

Jan-0

4

Pe

rce

nta

ge

of

Ma

rke

t P

art

icip

an

ts

FTP HTTPS GISB 1.4 NAESB 1.6

FTP

HTTPS

GISB 1.4

GISB/NAESB 1.6

Model Usage vs. Time Profilewith interim GISB 1.4

FTP Replacement - Next Steps

• ERCOT will continue with HTTPS implementation (Now)

• TDTWG will survey market for preference and estimate to complete on available options.

– Survey will be final July 12th

– Target results to be back August 8th.

• ERCOT will develop cost and schedule for GISB 1.4. (Target August 1)

• Approval to move forward by August 15th.

• Implement GISB 1.4 at ERCOT (Target October 1)

• Market Migration from FTP (Target October 1-April 1)

• Finalize GISB/NAESB 1.6 plan (Target November 15)

“Dark Side of the Moon” – Enhanced Transaction Reporting

“Dark Side of the Moon”

• What is “Dark Side of the Moon”– Means of Tracking Specific File and Transactional Lifecycle Activity

• Market Participant baseline Data – 3rd party routing for lifecycle tracking

• Market Participant in-Process – identifies files/transactions being processed

• Market Participant Forwarded – identifies the number of 867’s forwarded to other participants

– Data Delivered by 7am CST Daily – Data reported is from the Previous Day– Data Collected from FTP and PaperFree EDI Translator Logs

• Initial Report Creation/Delivery Started on June 19th 2002– User Guide Published on the ERCOT web site

• The ESI ID Tracking System (ETS) is being developed to provide improved/enhanced functionality to that provided by the “Dark Side Reports”

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

“Dark Side of the Moon” Reporting Points

ESI ID Tracking System (ETS)

ESI ID Tracking System (ETS)

• ETS Objectives– Provide Visibility into Failed Transactions

• Phase I focus on ERCOT internal use

• Enables early identification and reprocessing failed transactions

• Phase II to enable visibility by Market Participants into their own transactions

• Project Update– Project Kick-off Meeting 6/24– Detailed requirements gathering underway– System build phase scheduled to start 7/29– Estimated implementation date 11/1

Texas Set Version 1.5

TX Set Version 1.5 Background Information

• Objectives– Correct Market Gaps found in v 1.4 (Requirements 1,2,3,4,5,6,8,10 &12)– Add functionality to support Muni/Co-ops who have chosen to Opt In.

(Requirements 13,14,15,16,17,18 & 20)– Enhance ERCOT internal processing performance.

(Not required by TX SET but are recommended by ERCOT staff)

• Requirements

– Requirement 1 – Forwarding of Switch/Move-In Rejections to CRS

– Requirement 2 – Permits pending transactions ( 814_28/29)

– Requirement 6 – Add REF~1P to 814_24

– Requirement 7 – Add DTM to 814_13

– Requirement 8 --CR Cancellation of Pending Switch

– Requirement 9 – 814_27 Flow Change

– Requirement 10 – Permits Not Received

– Requirement 11 – Add Life Support Indicator to 814_20

– Requirement 12 - Pass customer information to TDSP

– Requirement 13, 14, 15, 16, 17, 18, & 20 - MUNI/COOP Elements

Removed due to MI/MO revisions• Reqmnt 3 • Reqmnt 4• Reqmnt 5

TX Set 1.5 Update

• Scope Established & Guides Published– Market focused, includes point to point transactions

• Initial Conference Call Conducted July 2

• Kickoff Meeting/Workshop scheduled for July 17 in Austin– Primary focus is to establish “market testing dates”– Key project phases will be established

(Design, Build, Internal Test, Market Test, Implementation)– Communication of market testing approach and requirements– Implementation considerations and contingencies– Project Management

• Master project plan to be established that incorporate all related ERCOT and MP activities

• Project calendar of meetings and key milestones will be established

• Master issues log to be created and maintained

• Follow up Meeting Tentatively Scheduled for August 5 in Austin

TX Set Version 1.5 Phases

6/17 8/5 TBD TBD TBD TBD

ERCOT is in the process of Conceptual Detail Design for all Requirements.

Current System Assessment is completed.

Design BuildInternal

TestMarket

TestImplement

Key date for Market Coordination

Retail Portal Performance

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

ESIID Success Versus Fai lure W/ E 6/ 29/ 2002

0

500

1000

1500

2000

2500

3000

3500

4000

Sunday Monday T uesday Wednesday T hur sday Fr iday Satur day

Hits

E r r or s

Portal Performance Find Transaction Week Ending 6/29/02

Find Transaction hi ts Versus Er rors W/ E 6/ 29/ 2002

0

500

1000

1500

2000

2500

3000

Sunday Monday T uesday Wednesday T hur sday Fr iday Satur day

Day of Week

Hits

E r r or s

Portal Performance Items

• 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% decrease in timeout 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 being evaluated– Moving Siebel queries directly to Oracle– Additional redundant paths for Portal transactions– Continue to analyze errors and respond

IDR Meter Data

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 6/21

Date

Per

cen

t

Market

CPL

CPE

TNMP

ONCOR

WTU

Expected

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

66%

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

TDSP 28-Jun-02CPL 7-Dec-01CPE 26-Oct-01TNMP 21-Dec-01ONCOR 14-Sep-01WTU 4-Jan-02Market 12-Oct-01