1 Update from ERCOT Retail Market Services to RMS December 11, 2003.

1

Update from ERCOT Retail Market Services

to RMS

December 11, 2003

2

Texas Market Link(PRP Phase 1)

IT Update

3

IT Update – Texas Market Link(Portal Replacement Project Phase 1)

• Portal was re-launched as planned on December 3 after successful completion of market testing and stress/load testing, however, issues were encountered and the old Portal was reinstated during the early hours of the next morning.

– TML was online for 10 hours from Dec 3 7:20pm through Dec 4 5:15am the next morning.

– Users were able to access the new TML system during that time– During the brief operation, TML experienced web service issues that

created technical issues in the background, but did not impact Market Operations.

– An IT decision to revert back to the old Portal was made and executed at 5:15am to minimize operational risk.

– Market notified by Client Relations that morning.

• Post-mortem analysis is underway to identify the issues and to assess the next re-launch approach.

• Any tml.ercot.com requests are being redirected to portal.ercot.com.

4

Retail API Update

5

IT Update(API Issue and Redevelopment Efforts)

• API became corrupt/unrecoverable on October 3

• ERCOT Development team has developed new API program to replace old functionality

• Planned Release Steps:– Download of Report Functions- released November 11 (this week)

• Delivery was on schedule• Some issues with unzipping files (2 companies using a Java program)

– Find ESI Id and Find Transactions- target December 5– Find Market Participant Data- target December 12

• Continue providing Weekly Updates on Retail Conference Call

• Reminder that the website URL for the API changed:– https://pi.ercot.com/servlet/piController – (old address was pi.ercot.com)

6

Data Variance/SCR 727 Extract Update

7

FasTrak Issue Status• Day-to-Day• Data Extract Variances (DEV)• ERCOT Initiated Issues

8

FasTrak 2003 “Day to Day”Issue Stats (as of 12-04-03)

• Of the 350 In Progress, 119 are resolved and awaiting other party resolution check off

• Total ESI IDs worked to date since January 1, 2003 = 2,852,895

• ERCOT would like to complete and close out all 2003 issues by January 31, 2004

STATUSIssueCount

Issues as a% of Total

New 10 0.08%

In Progress (w/ERCOT) 98 0.76%

In Progress (w/TDSP) 127 0.98%

In Progress (w/CR) 115 0.89%

Resolved 11,766 90.73%

Rejected 852 6.57%

Total 12,968

IssueCount


New 1,908 34.18%

In Progress 1,473 26.39%

Resolved 2,107 37.75%

Rejected 94 1.68%

Total 5,582

Non-ERCOT

ERCOT

• Of the 3,381 New and In Progress Non- ERCOT issues, 13 are for the year 2002

• Number of ESI IDs not tracked

9

FasTrak Data Extract VarianceIssue Stats (as of 12-04-03)

• Of the 276 In Progress, 29 are resolved and awaiting other party resolution check off

STATUSService History Usage

TotalIssues

Issues% of Total

New 7 0 7 0.32%

In Progress (w/ERCOT) 64 1 65 2.97%

In Progress (w/TDSP) 55 0 55 2.51%

In Progress (w/CR) 157 0 157 7.16%

Resolved 566 3 569 25.96%

Rejected 1,307 32 1,339 61.09%

Total 2,156 36 2,192

Service History Usage

TotalIssues

Issues% of Total

New 2 7 9 0.36%

In Progress 53 20 73 2.94%

Resolved 385 601 986 39.65%

Rejected 554 865 1,419 57.06%

Total 994 1,493 2,487

Non-ERCOT (CR to TDSP)

ERCOT

10

FasTrak ERCOT Initiated Issues Issue Stats (as of 12-04-03)

STATUSIssueCount


New 16 25.00%

In Progress (w/ERCOT) 23 35.94%

In Progress (w/TDSP) 9 14.06%

In Progress (w/CR) 0 0.00%

Resolved 14 21.88%

Rejected 2 3.13%

Total 64

ERCOT Initiated • These are issue initiated by ERCOT to the TDSP or CR as a result of one of the following projects:– Customer Protection Period and

814.08– 867 Received on Canceled

Service orders

11

Pre TX Set 1.5 Data Clean Up

• RMS Directive• Pre TX SET 1.5 Status Report

12

Pre-TX Set 1.5 Data Cleanup

Background:ERCOT identified “In Review”, “Scheduled” and “Canceled with Exception with Meter Reads” that were not completed from early 2002 to April 11, 2003.

RMS Vote, July 17th, 2003:Recommend RMS direct ERCOT to completely clean-up by August 13th, 2003 the Pre-Tx Set 1.5 In Review, Scheduled and Cancel With Exception that have been identified and sent to the market participants which should include cancels with CR approvals. ERCOT will provide at August RMS full statistics involving market participants broken down per issue type. ERCOT is directed that if the TDSP provides file names, ERCOT will locate and re-process if it is a valid transaction. RMS directs the TDSPs and CRs to provide transactions or information necessary to achieve the completion of the data clean-up.

13

Pre-TX Set 1.5 Data Cleanup

Mar-03 Jun-03 Jul-03 Aug-03 Sep-03 Oct-03 Nov-03As of

12/04/2003

In Review AEP - - 0 0 0 0 0 0

CNP - - 0 0 0 0 0 0

Oncor - - 6 0 0 0 0 0

TNMP - - 6 0 0 0 0 0

Total 16,188 207 12 0 0 0 0 0

Scheduled AEP - - 2,953 1,883 57 25 2 1

no completing CNP - - 1,215 530 93 10 0 0

meter read Oncor - - 991 2,039 1,413 765 522 425

TNMP - - 994 2,186 418 127 95 82

Shrylnd - - - 8 - 0 0 0

Total 23,030 11,038 6,153 6,646 1,981 927 619 508

CWE AEP - - 31 31 0 0 0 0

w/ Meter Data CNP - - 694 697 620 251 0 0

Identified as Oncor - - 624 624 4,365 72 72 72

as "Need TNMP - - NR NR 260 2 2 2to Complete" Total Na 1,618 1,349 1,352 5,245 325 74 74

14

Ongoing Transaction Data Clean Up

• Clean-up Process Steps• Completed Items – Next Steps• Status Report

15

Ongoing Transaction Data Clean-up

Clean-up Process Steps:

1. ERCOT runs the query and defines the Action Items needed a) In-Review with Meter Read: Notify TDSP and request 814_04/25

then transaction will complete. (Date Range equals or greater than 07/01/01.)

b) Scheduled No Meter Read: Notify TDSP and request 867 completing transaction. (Date Range equals or greater then 07/01/01.)

c) Cancel With Exception (CWE) with Meter Read: Notify CR and TDSP and find out if they thought the transaction had completed. If so – take corrective action. (Date Range is 04/12/03 to 08/31/03.)

d) Cancelled Permit Not Received with Meter Read: Notify CR and TDSP and find out if they thought the transaction had completed. If so – take corrective action. (Date Range is 04/12/03 to 08/31/03.)

2. ERCOT distributes the lists to MP who owe the follow-up action.3. MP Responds and ERCOT coordinates the clean-up activities.4. ERCOT to report Monthly to RMS.

16

Ongoing Transaction Data Clean-up

Completed Items :

• October 20, 2003: ERCOT sends out new lists to CRs and TDSPs

• October 29, 2003: TDSPs send analysis to CR

• November 4, 2003: CRs respond to TDSPs and coordinate final response to ERCOT

• ERCOT received responses from all TDSPs except Sharyland by November 7th

• RMS approved a target deadline of December 12 for completing this activity

Next Steps:

• ERCOT to coordinate corrective actions to TDSP

• ERCOT will continue to report progress at each RMS meting

17

Ongoing Transaction Data Cleanup

Original Count 11/11/03 12/4/03

Original Count 11/11/03 12/4/03

In Review AEP 0 0 0 CWE AEP 3 2 1

CNP 0 0 0 CNP 31 27 0

with Oncor 18 0 0 w/ Meter Data Oncor 37 37 4

Meter Read Shrylnd 3 2 0 Identified as Shrylnd 8 NR 0

TNMP 5 0 0 as "Need TNMP 4 4 2

Total 26 2 0 to Complete" Total 83 70 7

Scheduled AEP 2,432 277 179 CPNR AEP 149 46 16

CNP 937 104 6 CNP 53 52 0

without Oncor 2,753 1,679 1,136 w/ Meter Data Oncor 46 46 0

completing TNMP 832 280 257 Identified as Shrylnd 0 0 0

meter read Shrylnd 2 2 0 as "Need TNMP 0 0 0

Total 6,956 2,342 1,578 to Complete" Total 248 144 16

18

Customer Protection and 814_08 Issue

• Background and Completed Items• Matrix and Progress Report• Other Status Items and Next Steps

19

BackgroundERCOT has determined that there was an issue with the 814_08 manual-processing tool related to the cancel by customer objection process. While ERCOT systems were updated appropriately, 972 ESI IDs (spanning the August 2002 through July 2003 time frame) were identified where ERCOT has been unable to confirm that the TDSP was sent the 814_08 cancel.

Completed Items• All Scenario 1 instances that could be worked have been worked.

ERCOT still has approximately 35 that need further clarification from TDSPs

• 41 FasTrak issues:─ 20 Resolved (spanning 32 switches)─ 20 In Progress (some dialog has occurred)─ 3 Not Started (no feedback)

Customer Protection Period and 814.08

20


TDSPLosing

CRGaining

CRTotal

Instances

CR Claiming

ESI ID Suggested Action CompletedIn

Progress

1 Completed Completed Completed 474 Gaining CRERCOT manually correct

rep of record history 440 34

2 Completed Canceled Completed 18 Both CRsERCOT create modified

inadvertent issue 6 12

3 Completed Completed Canceled 13 No CRERCOT create modified


4 Completed Canceled Canceled 8 Losing CRERCOT create modified


5 Canceled Completed Completed 8 Gaining CRERCOT create modified


6 Canceled Canceled Completed 38 Both CRsERCOT create modified


7 Canceled Completed Canceled 19 No CRERCOT create modified


8 Canceled Canceled Canceled 387 Losing CR No action necessary 387 NAUnable to categorize response 2 Totals 859 106Recent info - need to categorize 5Total Sent to Market 972

December 04, 2003 Status

21


Scenario

TotalInstances Count % Count % Count %

1 474 0 0% 400 84% 440 93% 342 18 1 6% 3 17% 6 33% 123 13 0 0% 2 15% 2 15% 114 8 0 0% 1 13% 1 13% 75 8 1 13% 3 38% 5 63% 36 38 0 0% 3 8% 12 32% 267 19 3 16% 4 21% 6 32% 138 387 387 100% 387 100% 387 100% No Action

392 40% 803 83% 859 88% 106

Unable to categorizeresponse 2Recent infoneed to categorize 5Total 972

12-4-03Completed In

Progress (12-4-03)

11-12-03Completed

10-15-03Completed

22

Other Status Items• Matrix of FasTrak issues not yet resolved provided to RMS Chair/Vice

Chair on Nov 6th and Dec 4th - included CR names• ERCOT has “processed” all email exchanges related to FT issues as of

12/4/03 • Concern that ERCOT is not being informed of “resolution” in some

cases.

Next Steps• ERCOT to continue to escalate missing responses• ERCOT to complete manual corrections by related to Scenario 1 • CRs and TDSPs make decisions on outstanding FasTrak issues and

provide response to ERCOT


23

Pro-Active Transaction Resolution Measures

867s Received on Canceled Service Orders

24

SituationERCOT periodically receives 867_03 Finals and 867_04s for service orders that are Canceled in ERCOT systems. The Service Order Statuses that are considered Canceled are: Canceled (manually or concurrent

processing), Canceled by Customer Request, Canceled by Customer Objection, Canceled Permit Not Received, Canceled with Exception, Unexecutable and Rejected by TDSP. This can indicate an out-of-sync condition between the TDSP and ERCOT.

Volume:

867s received on Canceled Service Orders

Cancel Type Total 11/28/03 11/21/03 11/14/03 11/7/03Cancelled 155 33 38 71 13Customer Request 4 2 1 1 0Customer Objection 73 18 21 21 13Permit Not Received 67 15 23 23 6Cancelled w/ Exception 12 2 0 8 2Rejected by TDSP 17 12 2 2 1Unexecutable 30 10 8 9 3Grand Total 358 92 93 135 38

25


TDSP Total 11/28/03 11/21/03 11/14/03 11/7/03AEP 60 12 10 34 4CenterPoint 152 34 34 67 17ONCOR 82 26 32 16 8Sharyland 8 3 0 2 3TNMP 56 17 17 16 6Grand Total 358 92 93 135 38

TDSP Total

Cancelledby TDSP(In-Sync)

Completedby TDSP

(Out-of-Sync)Awaiting TDSP

ResponseAEP 60 4 34 22CenterPoint 152 81 37 34ONCOR 82 10 46 26Sharyland 8 0 0 8TNMP 56 0 0 56Grand Total 358 95 117 146

26

Proactive Measure:• ERCOT will compile transaction data related to the situation described

above and on a weekly basis submit an ERCOT initiated FasTrak issue with the TDSP identified as the Resolving Party.

• The TDSP is to provide a response for each FasTrak line item within the issue spreadsheet:1. The service orders are Canceled in the TDSPs system - the TDSP should

update the FasTrak issue spreadsheet accordingly. No further action is necessary.

2. The service orders are Complete in the TDSPs system - identifying an out-of-sync condition with ERCOT. The TDSP would then initiate an effort to clear the out-of-sync condition. (see ERCOT proposal for resolving out-of-sync conditions)

Timing and Implementation:• ERCOT initiated this process on November 7, 2003 • Each Friday thereafter, ERCOT has provided a list to the TDSPs via

FasTrak containing data for 867s received against Canceled Service Orders for the previous seven days

• ERCOT is awaiting RMS direction for process completion


27

Considerations for clean-up of Out-of-Sync Situations :• CRs receive both completing and cancellation information on service

orders and should initiate an inquiry to the TDSP any time they see both on the same service order (they should not wait for this process)

• Additionally, CRs who submit an enrollment transaction receive a Service Order extract identifying the ERCOT Siebel status of the transaction

• Use of a “modified” Inadvertent issue process has not been a great success in the missing 08 clean-up effort

• Precise rules allow for definitive understanding of how each Market Player will respond but does not circumvent the ability for ad-hoc corrections


Cancel Reason Cancel ProcessCancelled CR requested with TDSP approval, Concurrent Processing, TDSP requested

Customer Request CR submitted 814_08 to ERCOT and TDSP responded with 814_09 Accept

Customer Objection Customer canceled switch via objection process, per Protocol

Permit Not Received Transaction timed out in ERCOT systems, per Protocol

Cancelled w/ Exception Transaction timed out in ERCOT systems, per Protocol

Rejected by TDSP TDSP responded to 814_03/24 from ERCOT with 04/25 reject, cancel per ProtocolUnexecutable TDSP responded with an 814_28 09, cancelled per Protocol

28

ERCOT Proposal for Handling Out-of-Sync Conditions :

For: ▪ Canceled Canceled by Customer Request Canceled by Customer Objection Unexecutable Rejected by the TDSP

Process: The TDSP will cancel the service order in their system.

For: ▪ Canceled Permit Not Received Canceled with Exception

Process: When TDSP indicates service order should be completed, ERCOT will locate and reprocess transactions identified as sent by the TDSP to complete a service order. (May require TDSP to re-send transaction)

NOTE: FasTrak is the mechanism to handle exceptions to the above policy


29

NAESB EDM v1.6 Update

30

NAESB EDM v1.6 Background & Progress

Background:• NAESB EDM v1.6

– July 08, 2002 RMS votes to approve:• Data transport change from GISB EDM v1.4 to NAESB EDM v1.6 • Target GISB EDM v1.4 Retirement date – Q1, 2004• TDTWG would create Market Survey necessary for project planning for timing and

readiness of project testing and implementation• Testing and migration would be coordinated with Market Test Flights

– October 01, 2003• Market Survey completed and results submitted to Market Participants• Testing and migration timelines finalized and coordinated with Market Test Flights and

Move-In/Move-out Stacking Solution efforts

– October 16, 2002 RMS votes to approve:• NAESB EDM v1.6 testing approach and migration timeline

Progress:• Phase 1: ERCOT and TDSP – in progress• Phase 2: ERCOT and CR – not started• Phase 3: TDSP and CR - not started

31

NAESB EDM v1.6 ERCOT Testing Status

100% Complete 75% - 99% Complete 50% - 74% Complete 25% - 49% Complete Not Yet Initiated

TDSPMarket Participant Design Build Internal Testing Phase I Phase III

ADS Entergy Gulf States

Center Point

ECT / Systrends Pedernales - IOU

Pedernales - MUNI

Logica AEP Texas Central Co. AEP Texas North Co. AEP Texas North Co. SPP SWEPCO

ONCOR

ESG Nueces Elec Coop San Patricio Elec

TNMP

32



CRMarket Participant Design Build Internal Testing Phase II Phase III

ADS Calpine Power Mgt Entergy Retail GEXA Nueces Elec Coop – CR Direct Energy

Certain Energy

Constellation_New_Energy

EC Power Int Inc AEP_TX_Com & Ind Retail Alliance Power Co Creed Power Co Fire Fly Elec Just Energy Tx Hino Electric Mutual Energy CPL Mutual Energy SWEPCO Mutual Energy WTU New Mexico Natural Gas Polr Power LP/ ME TX Proviron Energy RP –Direct Energy Bus Svcs RP – Energy America Multi Family TriEagle Energy Utility Choice Elec VarTec Energy Inc.

33



CR cont.Market Participant Design Build Internal Testing Phase II Phase III

ECT/Systrends APS Energy Occidental Power Texas Commercial Energy Tenaska Texas Commercial Energy Pedernales Electric Coop, Inc.

Energy Services Group ACN Energy AMPRO Energy Andeler Corp ANP Power Direct BP Energy Company Cirro Group Dynegy Energy Services Exelon Power Services ExxonMobil Power & Gas MPower Retail Energy Sempra Energy Strategic Energy Tara Energy, Inc Tractebel Energy Marketing Tractebel Energy Services

First Choice Power

Green Mountain Energy Green Mountain Energy Multi Family

34


CR cont.Market Participant Design Build Internal Testing Phase II Phase III

Intelsys Inc. Energy West Liberty Power Corp NM Energy of Texas (Nordic) Pilot Power Group Inc. Usave Energy

Pegasus Star

Reliant Reliant_Retail Reliant_Energy_Solutions StarEn Power, LLC StarEn Power, LLC-LNR

TXU TXU_Energy Services TXU_SESCO TXU Energy Trading TXU_Assurance_ Polr_Large TXU_Assurance_ Polr_Small TXU_Assurance_ Polr_Resi

XERS (Xcel_Energy)

Spark Energy


35

NAESB EDM v1.6 Issues

Issues:1. NAESB EDM v1.6 Standards Compliance

• MIME content-type in the payload, e.g. “Content-Type:application/EDI-X12”. Is an identifier that follows the recommendation of Internet Standards RFC 1767, for “MIME Encapsulation of EDI Data” . TDTWG made this an optional not used element which in not optional in the NAESB EDM v 1.6 Standard as published by the NAESB organization.

• Issue has been sent to TDTWG for discussion and resolution at the December 10th, 2003 meeting.

36

Questions ?

37

MIMO Stacking Solution Update

38

• Progress– Delivered ERCOT Exception Processing Procedures– New NFI Statistics

• Feb 1, 2003 through Oct 31, 2003• Average 384 / day

Market Coordination Team for the Solution to Stacking

39

• Educational Seminars


MP Type Total MP Attended

Educational Seminar

Only Service Provider attended

Educational Seminar

No Exposure to Educational

Seminar REP 68 44 17 7

TDSP 6 5 1 0

Not Yet Certified REP 7 2 4 1

Not Yet Certified TDSP 2 0 2 0

Service Provider 6 4 N/A 2

Totals 89 55 24 10

40

• MP Progress Tracking– All Market Participants have been requested to provide a

monthly status on their progress with the Stacking effort– Market Participants are being asked to provide their own

status, no default to Service Provider status• Large dependency on Business Rules• Back end system modifications• EDI changes relatively small

– Progress will be reported through April, 2004


41

• MP Progress Tracking– **Graph goes here**


42

Project Overview

Summary of Changes:Manage customer expectations by accepting and processing all valid requests.

Imp

act

Lev

el

Efficiency

Communication

Competition

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.

43

Solution to Stacking

Production Implementation Timeline

Test Flight

7/232004

4/12004

5/172004

Production Implementation

Date:8/1/2004

10 weeks

Draft of Implementation

schedule and plan due

5/32004

Final of Implementation

schedule and plan due

Testing checkpoints

at wks. 5 & 8Connectivity

4/232004

Beginning of Test Flight

44

• Next Steps– Continue working with TTPT to develop test scripts

• MCT will review scripts being developed by Script Sub-Team

– Continue to Track Market Participant Progress– Educational Seminars as requested

• Five currently scheduled– Develop Production Implementation Plan– Develop Transition Plan for Service Orders ‘In Flight’– Develop Post-Implementation Success Criteria


45

Thank-you

46

Load Research Project Update

47

Load Research Sampling ProjectHigh Level Summary

• PUCT Order 25516 purpose: “This rule is necessary to facilitate retail competition in the ERCOT area. Since a large number of customers’ wholesale obligations are settled based on load profiles, it is imperative that the profiles be as accurate as possible.... More accurate profiles will enhance the retail market by providing for more accurate settlements.”

• ERCOT will create Load Profiles for each point in the sample matrix (including TDSP, rate type, weather zone, TDSP rate class, voltage type) based on sample points defined by ERCOT and installation by TDSPs

• TDSPs will install IDRs on all agreed sample points for the Load Research Sampling project (can be cost based IDRs that are already installed).

• ERCOT will make Load Profile data available to REPs and participating Muni/Co-ops (included is customer class, TDU service area, weather zone, and interval usage)

• ERCOT/TDSPs will NOT provide any customer identification information (including ESIID, address, etc) to REPs and participating Muni/Co-ops.

• ERCOT will work with the market to develop processes and procedures for Load Research Sampling Project (including IDR meter replacements, VEE standards, data transport method, data file types, data frequency)

48

UPDATED LRS PROJECT TIMELINE

October – December 2003

January 2004

February 2004 -- Completion

1/15/04TDSPs starts ordering IDRs

05/15/04—05/31/2004Market test validation for IDR files – TDSP and CR

01/31/04Install Load Research Software

06/01/04Start posting IDR data for CRs

IDR Installation Complete at TDSPs -6 months after sample set selection

12/05/03Meeting with CRs & TDSP

1/15/04TDSP validate samples and send installation schedule

01/31/04Install SAS

02/04Start receiving sample IDR data from TDSPs

1/31/04Target for finalized sample selection

1/31/04Finalized TDSP IDR installation schedule

10/16/03Present timeline to RMS

10/08/03Administer TDSP survey

10/23/03Meeting #1 with TDSPs

11/06/03Meeting #2 with TDSPs

11/17/03TDSP IDR format agreement

12/1/03-1/15/2003TDSP Handshake test for FTP replacement (on-going)

11/15/03Administer CR survey

1/5/04Design and select TDSP samples

04/15/04Complete Development for LRS solution at ERCOT

2/1/03-2/28/2003CR Handshake test (on-going)

49

LRS PROJECT UPDATES

• Market Decisions for LRS Project– Incoming IDR files (load profile data) from TDSPs will be in .LS

format

– Incoming IDR data will be transported by FTP Replacement protocol (TDTWG recommendation)

– Completion of IDR installations by TDSPs could take up to 6 months from sample selection decision

– ESIID with meter number information will be provided from TDSPs to ERCOT by a .CSV template

– A daily Ack/Nack summary report should be generated by ERCOT for all inbound IDR information for each TDSP

50

LRS PROJECT NOTES AND ISSUES

• Target design and select TDSP samples date has slipped from 11/20/2003 to 1/5/2004 (target). Slip due to hardware and software constraints

• Time period from initial TDSP design sample to finalized sample selection will be used to review sample selection data, review viability for IDRs in the field, and TDSPs sample selection confirmation

• Each TDSP will provide an installation schedule for IDR meters (1/31/2004), and installation shall be an on-going process for 6 months post sample design selection

• Target IDR installation complete date based on TDSP IDR installation dependencies and finalized sample design. Additional constraint due to Direct Load Control Project not currently taken into account (project currently on hold pending PUC approval)

51

Flight 1003 Status Report

52


• Flight completed ahead of schedule

• Lessons learned will be reviewed with TTPT

• Feedback on competitive metering scripts was

provided to COMET working group.

Modifications were made for upcoming Flight

0104.

53


54


• Market Orientation meeting held 12/3/03

• Disconnect for Non-Pay script is going to be available in

both the Flight 0104 and Flight 0504 to prepare for

proposed June 1, 2004 date.

• ALL CRs in the market will need to test the Disconnect for

Non-Pay script.

• Deadline for sign up for Flight 0104 is Wednesday,

December 17, 2003, 5pm CST

55

Questions ?

1 Update from ERCOT Retail Market Services to RMS December 11, 2003.

Documents

Transcript of 1 Update from ERCOT Retail Market Services to RMS December 11, 2003.