update from ercot retail market services to rms january 14, 2004

1

Update from ERCOT Retail Market Services

to RMS

January 14, 2004

2

– Texas Market Link (PRP phase 1) Update – Matt Mereness – Commercial Application Systems Upgrade Project - Dave Odle – Data Variance / SCR 727 Extract Update – Betty Day – EDIM Progress Reports – James Cohea

• Fast Trak Day to Day Issues Progress Report • Fast Trak DEV Issues Progress Report • Pre-Texas SET 1.5 Data Clean Up Progress Report • On-Going Data Clean Up Update • Customer Protection 814_08 Issue Update • 867s received on Canceled Service Orders

– NAESB 1.6 Migration Update - John Kassel– MIMO Stacking Solution Update – Glen Wingerd – Load Research Project Update - Raj Chudgar– Flight Test Update (0104) – Karen Bergman – Market Participant Survey - Scott Egger– CR Data Extract Variance Reporting - Karen Bergman

Agenda / Presenters

3

Texas Market Link(PRP Phase 1)

4

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

• The new Portal/TML was launched 12/3/2003 after successful completion of market testing and stress/load testing, however, technical issues were encountered and the old Portal was reinstated.

• Post-mortem analysis has revealed a technical issue in the platform integration.

• Next steps are being discussed to resolve technical issues and to assess re-launch approach.– In the interim, any https://tml.ercot.com requests are being

redirected to https://portal.ercot.com.

5

Retail API Update

6

IT Update(API Issue and Redevelopment Efforts)

• API became corrupt/unrecoverable on 10/3/03

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

• Released in three phases:– Download of Report Functions- released 11/11/03– Find ESI Id and Find Transactions- released 12/8/03– Find Market Participant Data & Winzip fix- released 12/16/03

• Continue providing Weekly Updates on Retail Conference Call

• Reminder that the website URL for the API changed:– https://pi.ercot.com/servlet/piController

7

Commercial Application Systems Upgrade Project (CASUP)

PR# 30082_02

8

CASUP Purpose

Project Purpose:• ERCOT Commercial Systems must be upgraded for software version support

and compatibility. ERCOT considers this an opportunity to review current application performance, reliability, and extensibility.

• ERCOT will be evaluating if there are existing applications that better meet our functional needs and cost of ownership requirements.

Desired Result: • To improve ERCOT’s ability to provide reliable, scalable, highly available, and

extensible commercial systems that enable timely and accurate responses to changing demands of the Texas Electric Market while over time reducing the total cost of ownership and operation.

9

CASUP Approach

Requirements Phase

Business RequirementsTechnical Requirements

RFQRecommendationVendor Shortlist

RFP Phase

RFP (if necessary)

Vendor Selection (if replacement option is decided)

Build Phase

Either:Upgrade

orReplace

10/16/03 3/31/04? ?

Current Phase

10

CASUP Requirements Approach

Requirements Phase Project Approach:

• Three deliverables:– Business Requirements Delivery

– Technical Requirements Delivery

– Recommendation (Upgrade/Replace) and Vendor Shortlist Delivery

• All three deliverables running in parallel

• Requirements phase to conclude 3/31/04

11

CASUP Next Steps

• Vendor Demonstrations during January & February– ERCOT evaluations of demos

– Cost/Benefit/Risk Analysis

– Decision of Replace or Upgrade

– Vendor Shortlist Creation

• Requirements – Business detailed requirements complete

– Technical detailed requirements complete

12

Data Variance / SCR 727 Extract Status

13

• ERCOT provided all extract files by the scheduled date of 12/19/03

• Daily extract file posting began on 12/19/03

• Two minor issues resolved:– Daily files for 12/7/03 and 12/8/03 posted out of order

• MPs processing according to the dates of the files were not impacted

• MPs processing according to the posting date were provided instructions on how to correct

– Decimal precision on LSCHANNELCUTDATA records

• New extracts are provided with higher level of precision

• ERCOT recommends rounding of data by MPs to avoid any issue in comparing extract data to MP source data

• Incremental 2 LSCHANNELCUTDATA files formatted incorrectly (no decimal precision) – new data files provided

SCR 727 Extract Status

14

Board Resolution on True-Ups

All true-ups for 2003 shall be delayed until market participants have a reasonable amount of time to load complete data extracts and analyze the data, and sufficient time to process any alleged variances as follows:

(1) 2003 True-Up Settlement Statements will begin no earlier than 120 days from the date that ERCOT provides the first complete SCR 727 data extracts related to 2003 to market participants, as determined by ERCOT, and

(2) alleged data variances indicated in the extracts affecting 2003 True-Up Settlement Statements must be submitted to ERCOT in chronological order beginning 90 days from the date that ERCOT provides the first extract related to 2003.

ERCOT has determined that complete data was provided to the Market by 1/1/04.

True-Up Settlement Statements for 2003 will begin on May 1, 2004.

A Settlement Calendar will be published to the ERCOT website.

15

RMS Vote on DEV Timelines (10/16/03)

A motion was made by Rob Bevill and seconded by Shannon Bowling to establish a 75 calendar day deadline for completion of each issue and each MP (including ERCOT) will complete the Data Extract Variance (DEV) Process in accordance with the timelines and other requirements of the DEV Manual.

The motion was approved.

16

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

17

FasTrak 2003 “Day to Day”Issue Stats (as of 01-07-04)

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

• Total ESI IDs worked in 2003 = 324,587

STATUS 12/11/2003 1/7/2004

New 10 2 0.01%

In Progress (w/ERCOT) 98 77 0.55%

In Progress (w/TDSP) 127 103 0.73%

In Progress (w/CR) 115 96 0.68%

Resolved 11,766 12,823 91.33%

Rejected 852 940 6.69%

Total 12,968 14,041

12/11/03 1/7/04

New 1,908 2,045 31.33%

In Progress 1,473 1,704 26.11%

Resolved 2,107 2,661 40.77%

Rejected 94 117 1.79%

Total 5,582 6,527

Issue CountsNon-ERCOT

ERCOTIssue Counts Issues as a

% of Total

Issues as a% of Total

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

• Number of ESI IDs not tracked

18

FasTrak 2004 “Day to Day”Issue Stats (as of 01-07-04)


• Total ESI IDs worked to date since January 1, 2004 = 5,661

• Number of ESI IDs not tracked

Issue Counts

STATUS 1/7/2004

New 13 5.28%

In Progress (w/ERCOT) 12 4.88%

In Progress (w/TDSP) 57 23.17%

In Progress (w/CR) 61 24.80%

Resolved 86 34.96%

Rejected 17 6.91%

Total 246

Issue Counts

1/7/04

New 75 50.68%

In Progress 67 45.27%

Resolved 5 3.38%

Rejected 1 0.68%

Total 148

Non-ERCOT

ERCOTIssues as a% of Total

Issues as a% of Total

19

FasTrak Data Extract VarianceIssue Stats (as of 01-07-04)


• 2,123 issues classified as resolved or rejected in 2003 are excluded from the report per RMS direction

STATUSService History Usage

TotalIssues

Issues% of Total

New 2 0 2 1.27%

In Progress (w/ERCOT) 10 0 10 6.33%

In Progress (w/TDSP) 24 0 24 15.19%

In Progress (w/CR) 115 0 115 72.78%

2004 Resolved 1 0 1 0.63%

2004 Rejected 1 5 6 3.80%

Total 153 5 158

Service History Usage

TotalIssues

Issues% of Total

New 2 6 8 8.25%

In Progress 55 33 88 90.72%

2004 Resolved 0 1 1 1.03%

2004 Rejected 0 0 0 0.00%

Total 57 40 97

Non-ERCOT (CR to TDSP)

ERCOT

• 2,421 issues classified as resolved or rejected in 2003 are excluded from the report per RMS direction

20

FasTrak ERCOT Initiated Issues Issue Stats (as of 01-07-04)

• 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

STATUS 12/11/2003 1/7/2004

New 16 15 18.29%

In Progress (w/ERCOT) 23 26 31.71%

In Progress (w/TDSP) 9 4 4.88%

In Progress (w/CR) 0 1 1.22%

Resolved 14 36 43.90%

Rejected 0 0 0.00%

Total 62 82

ERCOT InitiatedIssue Counts Issues as a

% of Total

21

Pre TX Set 1.5 Data Clean Up• RMS Directive• Pre TX SET 1.5 Status Report

22

Pre-TX Set 1.5 Data Clean Up

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.

23

Pre-TX Set 1.5 Data Clean Up

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

01/07/2004

In Review AEP - - 0 0 0 0 0 0 0

CNP - - 0 0 0 0 0 0 0

Oncor - - 6 0 0 0 0 0 0

TNMP - - 6 0 0 0 0 0 0

Total 16,188 207 12 0 0 0 0 0 0

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

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

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

TNMP - - 994 2,186 418 127 95 82 78

Shrylnd - - - 8 - 0 0 0 0

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

CWE AEP - - 31 31 0 0 0 0 0

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

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

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

24

Ongoing Transaction Data Clean Up• Clean-up Process Steps• Completed Items – Next Steps• Status Report

25

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.

26


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

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

• ERCOT provide updates and reminders to the TDSPs on an ad hoc basis when requested by the TDSP and each week prior to RMS

Next Steps:

• ERCOT to coordinate corrective actions to TDSP

• ERCOT will continue to report progress at each RMS meting

27


Oct-03 Nov-03 Dec-03 1/7/04 Oct-03 Nov-03 Dec-03 1/7/04

In Review AEP 0 0 0 0 CWE AEP 3 2 1 1

CNP 0 0 0 0 w/Meter CNP 31 27 0 0

with Oncor 18 0 0 0 Data Oncor 37 37 4 0

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

Read TNMP 5 0 0 0 as "Need to TNMP 4 4 2 1

Total 26 2 0 0 Complete" Total 83 70 7 2

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

CNP 937 104 6 0 w/Meter CNP 53 52 0 0

without Oncor 2,753 1,679 1,136 579 Data Oncor 46 46 0 0

completing Shrylnd 2 2 0 0 Identified Shrylnd 0 0 0 0

meter read TNMP 832 280 257 226 as "Need to TNMP 0 0 0 0

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

28

Customer Protection and 814_08 Issue

(Phase 1 – Potentially Missing 08s)

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

29

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• Scenario 1 instances: ERCOT still has approximately 35 either in progress

or needing further clarification from TDSPs• 41 FasTrak issues:

─ 27 Resolved (spanning 40 switches)─ 13 In Progress (some dialog has occurred)─ 1 Not Started (no feedback)

Customer Protection Period and 814.08 (Phase 1 – Potentially Missing 08s)

30

TDSPLosing

CRGaining

CRTotal

Instances

CR Claiming

ESI ID Suggested Action CompletedIn

Progress

1 Completed Completed Completed 481 Gaining CRERCOT manually correct

rep of record history 448 33

2 Completed Canceled Completed 18 Both CRsERCOT create modified

inadvertent issue 10 8

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 0 Totals 875 97Recent info - need to categorize 0Total Sent to Market 972

January 7, 2004 Status


31

Sce-nario

TotalInstances Count % Count % Count % Count %

1 474 0 0% 400 84% 440 93% 448 95% 332 18 1 6% 3 17% 6 33% 10 56% 83 13 0 0% 2 15% 2 15% 3 23% 104 8 0 0% 1 13% 1 13% 1 13% 75 8 1 13% 3 38% 5 63% 5 63% 36 38 0 0% 3 8% 12 32% 12 32% 267 19 3 16% 4 21% 6 32% 9 47% 108 387 387 100% 387 100% 387 100% 387 100% No Action

392 40% 803 83% 859 88% 875 90% 97

0

0972

InProgress (01-07-04)

11-12-03Completed

10-15-03Completed

12-4-03Completed

Unable to categorize response

Recent info - need to categorize

Total

01-07-04Completed


32

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

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

01/06/04 • 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 related to Scenario 1 • CRs and TDSPs make decisions on outstanding FasTrak issues and provide

response to ERCOT via FasTrak and Email


33

Customer Protection and 814_08 Issue

(Phase 2 – Potentially Late 08s)

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

34

BackgroundUpon inception of Phase 1 of the ‘Potentially Missing 08s’, MPs requested an analysis of potentially late 08’s on Cancel by Customer Objection (CCO). ERCOT identified 264 instances of 08’s on CCOs that were sent to the TDSP at least two days after the end of the customer objection period where the TDSP rejected the cancel. These switch transactions span the August 2002 through November 2003 time frame. Upon direction from RMS at the December 2003 meeting, ERCOT sent list to each CR and TDSP involved in an attempt to quantify the true scope of out-of-sync conditions.

Completed Items• ERCOT sent lists to 4 TDSPs and 12 CRs on 12/23-24/2003 requesting

responses by COB 1-6-04• ERCOT received responses from all MPs except CPL Retail, Direct

Energy, Entergy Solutions and WTU Retail• ERCOT compiled the following matrix from the responses received

Customer Protection Period and 814.08 (Phase 2 – Potentially Late 08s)

35

TDSPLosing

CRGaining

CRTotal

Instances

CR Claiming

ESI ID Suggested Action CompletedIn

Progress

1 Completed Completed Completed 13 Gaining CRERCOT manually correct

rep of record history 0 13

2 Completed Canceled Completed 4 Both CRsERCOT create modified


3 Completed Completed Canceled 0 No CRERCOT create modified


4 Completed Canceled Canceled 0 Losing CRERCOT create modified


5 Canceled Completed Completed 1 Gaining CRERCOT create modified


6 Canceled Canceled Completed 3 Both CRsERCOT create modified


7 Canceled Completed Canceled 2 No CRERCOT create modified


8 Canceled Canceled Canceled 27 Losing CR No action necessary 27 0Missing response 214 Totals 27 23Total Sent to Market 264

January 7, 2004 Status


36

Next Steps

• CRs to provide outstanding responses to ERCOT

• Once initial responses are received:

Scenario (1) - ERCOT to begin manual corrections – this will require input from the TDSP on their REP of record history

Scenario (2-7) - ERCOT to provide email information to CR’s and TDSP describing potential out-of-sync situations. CRs and TDSP to determine if further action is required and initiate FasTrak issues as needed

Scenario (8) - Considered in-sync with no further action required


37

Pro-Active Transaction Resolution Measures

867s Received on Canceled Service Orders

38

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 12/31/03 12/19/03 12/12/03 12/5/03 11/28/03 11/21/03 11/14/03 11/7/03Cancelled 254 10 47 27 15 33 38 71 13Customer Request 64 1 55 3 1 2 1 1 0Customer Objection 309 21 97 94 24 18 21 21 13Permit Not Received 123 15 13 16 12 15 23 23 6Cancelled w/ Exception 19 1 2 2 2 2 0 8 2Rejected by TDSP 83 1 56 4 5 12 2 2 1Unexecutable 91 7 46 2 6 10 8 9 3Grand Total 943 56 316 148 65 92 93 135 38

39


TDSP Total 12/31/03 12/19/03 12/12/03 12/5/03 11/28/03 11/21/03 11/14/03 11/7/03AEP 127 12 23 23 9 12 10 34 4CenterPoint 237 16 31 20 18 34 34 67 17ONCOR 287 14 166 11 14 26 32 16 8Sharyland 17 2 2 2 3 3 0 2 3TNMP 275 12 94 92 21 17 17 16 6Grand Total 943 56 316 148 65 92 93 135 38

TDSP Total

Cancelledby TDSP(In-Sync)

Completedby TDSP

(Out-of-Sync)Awaiting TDSP

ResponseAEP 127 9 51 67CenterPoint 237 164 73 0ONCOR 287 187 100 0Sharyland 17 0 8 9TNMP 275 275 0 0Grand Total 943 635 232 76

40

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


41

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

42

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


43


Completed Items

• ERCOT continues sending weekly FasTrak issues to TDSPs

• ERCOT modified process to omit 867 Cancels from reporting beginning with 2004

Next Steps

• ERCOT to discuss outstanding issue with TDSPs and determine resolution

44

NAESB EDM v1.6Update

45

NAESB EDM v1.6 ERCOT Testing Status

Current Progress:

Phase 1 - ERCOT and TDSP – Testing is complete

Phase 2 - ERCOT and CR – Scheduled to run from January 5th through January 22nd

(Week of January 26th reserved for any necessary rework…)

Issue on MIME Content-type – sent to TDTWG for resolution

Future:

Phase 3 - TDSP and CR - Scheduled to begin February 16th

Note: Flight 0104 New CRs will be handled by existing third party service providers already certified on NAESB v1.6

46

NAESB EDM v1.6 ERCOT Testing Status - CRs

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

Market Participant Design Build Internal Testing Phase II Phase III

ADS

· Calpine Pow er 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 Pow er Co

· Creed Pow er Co

· Fire Fly Elec

· Just Energy Tx

· Hino Electric

· MS Retail Dev Corp

· Mutual Energy CPL

· Mutual Energy SWEPCO

· Mutual Energy WTU

· New Mexico Natural Gas

· Polr Pow er LP/ ME TX

· Proviron Energy

· RP –Direct Energy Bus Svcs

· RP – Energy America Multi Family

· Texas Wholesale Energy

· TriEagle Energy

· Utility Choice Elec

· VarTec Energy Inc.

47

NAESB EDM v1.6 ERCOT Testing Status – CRs cont.



ECT/Systrends

· APS Energy

· Occidental Pow er

· Pedernales Electric Coop, Inc.

· Texas Commercial Energy

· Tenaska

· Tenaska-Oxy Pw r Rep Svcs LP

· TOPS I

· TPS I

· TPS II

· TPS III

Energy Services Group

· Accent Energy Texas LLC

· ACN Energy

· AMPRO Energy

· Andeler Corp

· ANP Pow er Direct

· BP Energy Company

· Cirro Group

· Dynegy Energy Services

· Exelon Pow er Services

· ExxonMobil Pow er & Gas

· MPow er Retail Energy

· Sempra Energy

· Strategic Energy

· Tara Energy, Inc

· Tractebel Energy Marketing

· Tractebel Energy Services

48

NAESB EDM v1.6 ERCOT Testing Status – CRs cont.



First Choice Power

Green Mountain Energy

· Multi Family

Intelysis Inc.

· AmeriPow er LLC

· APN StarFirst LP

· ECONnergy Energy Co

· Energy West

· Liberty Pow er Corp

· NM Energy of Texas (Nordic)

· Pilot Pow er Group Inc.

· Rio Grande Pow er LLC

· Usave Energy

· Vega Resources

Pegasus Star

Reliant

· Reliant_Retail

· Reliant_Energy_Solutions

· StarEn Pow er, LLC

· StarEn Pow er, 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

49

NAESB EDM v1.6ERCOT Testing Status - TDSPs


Market 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

50

Move-In/Move-Out Market Solution to Stacking (Texas Set V.2.0)

51

• Progress– Working on Implementation Plan

– Working on Post Implementation Success Criteria

Market Coordination Team for the Solution to Stacking

52

• 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


53

• ERCOT/TDSPs/Service Providers


54

• REPs


55


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.

56


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

57

• 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

– Develop Production Implementation Plan

– Develop Transition Plan for Service Orders ‘In Flight’

– Develop Post-Implementation Success Criteria


58

Load Research Update

59

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 (current)

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 Statistical Software (current)

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

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)

60

LRS Project Updates

• Market Updates– A sign-up form has been sent to CRs and MOU/EC (Municipally-

Owned Utilities and Electric Cooperatives) via ERCOT client reps. Due date is 1/31/2004 back to ERCOT client reps.

• Sign up for Day 1 data transmission• MOU/EC can sign up for program AFTER day 1 and ERCOT

will make data whole– LRS Project has created a web site under Load Profiling area on

ERCOT main web page for LRS project information• http://www.ercot.com/Participants/loadprofiling.htm

– FAQ for LRS project has been created and posted on LRS web site

• ERCOT Updates– ERCOT software is currently being installed and tested– ERCOT development for LRS solution is currently on schedule

61

LRS Project Information and Issues

• LRS Project Issues– Target sample design delivery has slipped from 1/5/2004 to 1/28/2004 (next PWG

meeting) due to volume of analysis, as well as ERCOT staff working on higher priority tasks: IDR Threshold Analysis, Annual Validation, and Review of TDSP filings and participation in Price to Beat Hearings

– 1 TDSP outstanding to complete handshake test.• Market Information

– TDTWG and PWG endorsement of the following:• TDSP

– "All interval data IDR files for Load Profiling Sample purposes transmitted from TDSP to ERCOT will use FTP Replacement such as to not interfere in any way with mechanisms used to support ERCOT Billing and Settlement".

– "TDTWG would like to recommend that the Market eventually move to one data transport mechanism to support all interval data IDR types of data files sent to ERCOT".

• CR:– "All interval data IDR files for Load Profiling Sample purposes transmitted

from ERCOT to CR will use FTP Replacement such as to not interfere in any way with mechanisms used to support ERCOT Billing and Settlement".

– "TDTWG would like to recommend that the Market eventually move to one data transport mechanism to support all interval data IDR types of data files sent from ERCOT".

62

Flight 0104 Status Report

63

Flight 0104 Status Report

• 8 new CRs signed up for Flight 0104

• 23 current CRs signed up to test the DNP script

• At the orientation meeting 12/3/04, ERCOT stressed that any new CR

coming into Flight 0104 needs to recognize that they will need to have

two efforts being performed in tandem

– Working on Flight 0104

– Working on understanding the market changes that are coming for Flight

0504 V2.0 Solution to Stacking.

• ERCOT informed each new CR that they would be REQUIRED to test

again in Flight 0504

64

Market ParticipantSurvey 2004

65

Survey Objective

• Receive structured feedback on the perceptions and expectations of Market Participants

• Allow ERCOT to assess the organizational alignment between itself and the market it serves

• Receive feedback from multiple levels in the market

• Demonstrate that ERCOT is interested in listening to concerns and comments of Market Participants

• Ensure that ERCOT’s corporate culture includes the proper degree of service mentality

66

Survey Development Process

• Selected market research firm – Opinion Dynamics

• Introduced firm to HR and Governance Committee – December meeting

• Interviewed 21 Market Participants from various levels for the development of the survey tool

• Received input from ERCOT officers and directors on the development of the survey tool

• Worked with ERCOT Client Services to identify targeted Market Participants for interviewing

67

Firm Selection & Qualifications

• Sent RFP to four firms

• Used eight criteria for the selection process

• Selected Opinion Dynamics – Cambridge, Massachusetts– Pure market research firm

– Has extensive experience in the utility sector

– Has worked with NYISO for three years

68

Project Plan

December January FebruaryTask Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7Send letter to 21 market participantsDepth interviews and Focus Groups with ERCOTSurvey sample developmentDepth interviews with Market ParticipantsModular Internet Survey Design and DevelopmentERCOT staff, HR and Governance Review of Modular Internet Survey

February MarchWeek 8 Week 9 Week 10 Week 11 Week 12 Week 13 Week 14

ERCOT staff, HR and Governance Review of Modular Internet SurveyField Internet Survey to market participantsReceive completed surveysAnalysis and reporting

AprilWeek 15 Week 16 Week 17

Analysis and reportingPresentation of findings to ERCOT

69

What We Plan To Do With The Survey Output

• Present survey results to ERCOT Board, market committees, and ERCOT staff

• Identify patterns or themes associated with root causes

• Develop method to move the customer service “meter” to a higher level

• Establish a dialogue with Market Participants on prioritizing action items

70

December Summary:CR Data Extract Variance Reporting

71

December CR DEV Reporting

• 13 of 73 Competitive Retailers Reported Numbers by the due date for January (01/06/04).

• Numbers for February RMS (January Reports) are due by February 3, 2004.

• Goals for next month:– More CRs Reporting

– ERCOT will break numbers out by TDSP

72

Totals – All TDSPs

On Time

Resulted in

Change Late

Resulted in

Change On Time

Resulted in

Change Late

Resulted in

Change On Time

Resulted in

Change Late

Resulted in

Change On Time

Resulted in

Change LateResulted

in Change

New (December)

.18% .11% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0%

Existing (Prior to December)

0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 45.61% 0%

Resolved w/in 75 days

.11% 0% 0% 0% 0% 0% .19% .11% 0% 0% 0% 0% 0% 0% 0% 0%

Resolved >75 days

0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 52.66% 52.66%

Total Submitted

.18% .11% 0% 0% 0% 0% 1.55% .85% 0% 0% 0% 0% 0% 0% 98.27% 52.66%

NON-ERCOT ERCOT

Service History ESI IDs Usage Non IDR ESI IDs Usage IDR ESI IDs LSE Relationship ESI IDs

73

Thank You

update from ercot retail market services to rms january 14, 2004

Documents

issue update

ercot commercial systems

ercot retail market

texas electric market

update customer protection

progress report ongoing

technical issues

parallelrequirements