update from ercot retail market services to rms may 15, 2003

1

Update from ERCOT Retail

Market Services

to RMS

May 15, 2003

2

Retail Market Update

Topics

– SCR 727 extract variance update

– Organizational update

– GISB migration update

– FasTrak seminar announcement

– Flight 0703 planning update

3

ESI ID Data ExtractVariance Process Update

• Current Events and Stats• ERCOT Initial Validation Process (SH)• ERCOT Issue Analysis/Correction Process (SH)• Current Issues• Potential Issues

4

ESI ID Data ExtractSCR727 Implementation Plan

ERCOT

DDL

MP to ERCOT1

Initial & Daily Extracts

4

Market Participants

DDL

MP 727 Db

Existing Transactional Db

Compare ToolVariancesIdentified

3

21

6

5

MP

to M

P

FasTrak

ValidVariances

VariancesTo Be

Resolved

Portal

NOIE

s

TDSPs & CRs

7&8

97&8

ERCOTIssues

MetricsReporting

5

ESI ID Data ExtractVariance Process Current Events

Timeline Activity

02-27-03 • Technical Conference call • Version 1.0 FasTrak Data Extract Variance Users Manual went operational• Version 1.0 FasTrak Spreadsheets went operational

03-04-03 • Business Conference Call

04-17-03 • TDSPs coordinated meeting to recommend change/additions to Manual and Spreadsheets

04-22-03 • Follow-up meeting coordinated by TDSPs

04-13-03 • 30 day prior to settlement of Jan 01,02 2002 - CRs and TDSPs to submit variance requests

05-10-03 • Business call to discuss implementation of revised User Manual and Spreadsheets

05-12-03 • Version 3.0 FasTrak Data Extract Users Manual and Version 2.0 Spreadsheets went operational

6

ESI ID Data ExtractStats (as of 05-15-2003)

• 149 total issues submitted to ERCOT affecting Jan’02 trade month– 8 are in progress with

ERCOT

– 25 are in progress with TDSP

– 116 are Resolved or Rejected

• 25 issues received in last week affecting Jan’02 trade month

STATUSService History Usage

TotalIssues

Issues% of Total

New 0 0 0 0.00%

In Progress (ERCOT) 21 0 21 8.43%

In Progress (w/TDSP) 26 0 26 10.44%

Resolved 56 2 58 23.29%

Rejected 127 17 144 57.83%

Total 230 19 249

Service History Usage

TotalIssues

Issues% of Total

New 9 1 10 1.89%

In Progress 83 158 241 45.47%

Resolved 15 119 134 25.28%

Rejected 35 110 145 27.36%

Total 142 388 530

ERCOT

Non-ERCOT (CR to TDSP)

7

ESI ID Data ExtractERCOT Initial Validation Process (LSE-SH)

VerifyServiceHistory

Variancerelated to

relationships

Note Reject withStandardized

Response

FasTrak

ValidSpreadsheetper DEVUM

Valid MPData

verification

ValidFasTrak

verification

DA - DataManagement

Team

Yes Yes Yes YesYes

NoNo No No No

CRRelationship

"TDSP asLSE"

Part ofMarket Sync

P 1,2,or4 Part1

VarianceRelationship+/- 2 days

RelationshipAssociatedto NPTB

CompressionRelated

PendingService Orders

Note Reject withStandardized

Response

Go toVariance Type

Decision Process

No No No No No No

Yes Yes Yes Yes Yes Yes

Refer toRegistration

for day-to-dayAnalysis

No

AcknowledgeReceipt of

FasTrak withinOne Day

Valid TradeMonth

verification

ValidDuplicate

Dataverification

Yes

No

A EDCB

Valid DateInformation

per VarianceType

verification

Rejected asInvalid

No

Yes

RejectSpreadsheet

and CloseFasTrak Issue

Yes

F

No

G

Acceptable Variance Check

LKJIH

Sanity Validation

8


Check Item Description

(A) Valid FasTrak verification

Variance type should be submitted to ERCOT FasTrak issue number matches spreadsheet

(B) Valid MP Data verification

Submitting entity matches submitting MP DUNS number in spreadsheet Only one submitting MP DUNS number per spreadsheet If submitter is LSE, submitter must match REPCODE

(C) Valid Trade Month verification

Submitting New Start Time, New Stop Time, STARTTIME, and/or STOPTIME must fall within indicated Trade Month Affected

(D) Valid spreadsheet per DEVUM

Spreadsheet is correct version and has correct column formats Requested Resolution is valid for Variance Issue For Variance Issue/Requested Resolution combination, all required fields are populated and in the correct format

(E)- Valid Duplicate Data verification

Based on ESIID, STARTTIME, and STOPTIME, no duplicate rows exist in spreadsheet

9



(F) Valid Date Information verification

If adding row, ensure New Start Time matches STARTTIME and/or New Stop Time matches STOPTIME If updating row, ensure New Start Time is more than 2 days different from STARTTIME and is prior to New Stop Time and/or STOPTIME. Ensure New Stop Time is more than 2 days different from STOPTIME and is after New Start Time and/or STARTTIME

(G) CR Relationship “TDSP as LSE”

Any changes with a New Start Time before 1/1/2002 cannot change an existing relationship associated with a TDSP as LSE TDSP as LSE cannot remove a relationship before 1/1/2002 (the TDSP as LSE can request to stop the relationship on or after 1/1/2002)

(H) Market Sync Comparison

Any changes with a New Start Time, New Stop Time, STARTTIME and/or STOPTIME between 4/1/2002 and 8/11/2002 cannot be associated to any ESIID identified in Market Sync as Priority 1,2, and 4 (part 1)Relationships created per Market Sync Priority 1, 2, and 4 (part 1) cannot be removed

10



(I) Variance Relationship +/- 2 days

Any changes with a New Start Time and/or New Stop Time cannot be within 2 days of STARTTIME and/or STOPTIME in Data Extract

(J) Relationship Associated to NPTB

Any changes with a New Start Time and/or STARTTIME between 12/19/2001 and 1/31/2002 cannot be associated to an identified Non-Price-to-Beat ESIID. Changes to the STARTTIME for removal of the relationships cannot be requested for NPTB ESIID, only STOPTIME may be altered

(K) Compression Related

Any request to make changes via a New Start Time or a New Start Time and New Stop Time may be identified as a compressed Lodestar row. Most MPs store relationships based on customer changes. Lodestar stores relationships more on CR changes and also holds other ESIID characteristic changes on same database table. Because of these differences, compression must be performed by all MPs prior to filing Data Extract variances

(L) Pending Service Orders

Any changes to an ESIID cannot have a pending (In Review or Scheduled) service order in Siebel associated with the submitting REP

11

Variance 3LSE relationship record in MP system

but not in ERCOT system

FromCommonElements

ResolvedClose out Issue

YesManually

complete SOand create

SI asneeded

Verify Data Flowto Lodestar

No

"Touch" ServiceInstance Rows

in Siebel(wait for S2L*5)

No Transactions will flow

Note ESIID andmark 'Unable to

complete'

YesSIconsecutive

?

NOIEESIID

Note ESIID andContact DataAggregation

team

GENSITEESIID

Yes Yes

No No Usage DateMatch for

RequestedDate

UsageLoaded forRequested

Date

Yes

No

Yes


complete'

CR(s) andTDSP Agree

to createrecord

No

No

MultipleCRs

Involved

Note ESIID andmark

'Requestedcorrectioncompleted'

A B C

D

E

F

GDA Manually correct

for De-energizedperiod in Lodestar

12

Variance 3LSE relationship record in MP system

but not in ERCOT system (A) GENSITE ESIID Because of its special nature, if an ESIID is determined to be a

GENSITE, the request will be redirected to a Data Aggregation analyst

(B) NOIE ESIID Because of its special nature, if an ESIID is determined to be a NOIE, the request will be redirected to a Data Aggregation analyst

(C) Usage Date Match for Requested Date

When adding a row, the New Start Time and (if applicable) New Stop Time must match a STARTTIME or STOPTIME of either Non-IDR or IDR Usage loaded at ERCOT. Determination for which to check is made based on the PROFILECODE of New MP Data

(D) Usage Loaded for Requested Date

If a Usage date does not match requested date, an additional check is performed to determine if Usage has been loaded for that requested date. Consideration is made for gap usage

(E) Multiple CRs Involved

A check is made to determine if the addition of the requested row impacts another CR(s)

(F) CR(s) and TDSP Agree to create record

If the CR(s) and/or the TDSP do not agree on the addition of the requested row, ESIID is marked with ‘Unable to complete’

(G) Manually correct/verify relationship at ERCOT

If the CR(s) and/or the TDSP agree to add the requested row, relationship is manually corrected and verified at ERCOT. Once completed, ESIID is marked with ‘Requested correction completed’

13

Variance 4LSE relationship record in ERCOT system

but not in MP system

Row Exists inSiebel andLodestar

FromCommonElements


YesTDSP

Agrees toremoverecord

No


complete'

Remove SIin Siebel

Cancel SO

GENSITEESIID

NOIEESIID


team

Yes Yes

No No

Yes

No

Note ESIID andmark


Note ESIID andmark


UsageLoaded forRemovalPeriod

A B

C

D

EF

DA Manually correctfor De-energized

period in Lodestar

14

(A) GENSITE ESIID Because of its special nature, if an ESIID is determined to be a GENSITE, the request will be redirected to a Data Aggregation analyst


(C) Row Exists in Siebel and Lodestar

A check is performed to determine if the row has already been removed at ERCOT

(D) Usage Loaded for Removal Period

A check is performed to determine if (and how much for Non-IDR) usage is loaded for removed period of time. This information is passed onto the TDSP for its consideration

(E) TDSP Agrees to remove record

If the TDSP does not agree to remove row, ESIID is marked with ‘Unable to complete’

(F) Manually correct/verify relationship at ERCOT

If the TDSP does agree to remove row, relationship is manually corrected and verified at ERCOT. Once completed, ESIID is marked with ‘Requested correction completed’

Variance 4LSE relationship record in ERCOT system

but not in MP system

15

Variance 5LSE relationship record in both systems

but has date issues

FromCommonElements


YesManually

complete SOand create

SI asneeded

Verify Data Flowto Lodestar

No

"Touch" ServiceInstance Rows

in Siebel(wait for S2L*5)

No Transactions will flow


complete'

Yes

SIconsecutive

?

NOIEESIID


team

GENSITEESIID

Yes Yes

No No Usage DateMatch for

RequestedDate

UsageLoaded forRequested

Date

Yes

No

Yes


complete'

CR(s) andTDSP Agree

to createrecord

No

No

MultipleCRs

Involved

Note ESIID andmark


A B C

D

E

F

G

DA Manually correctfor De-energized

period in Lodestar

16

(A) GENSITE ESIID Because of its special nature, if an ESIID is determined to be a GENSITE, the request will be redirected to a Data Aggregation analyst


(C) Usage Date Match for Requested Date

When changing a row, the New Start Time and (if applicable) New Stop Time must match a STARTTIME or STOPTIME of either Non-IDR or IDR Usage loaded at ERCOT. Determination for which to check is made based on the PROFILECODE of Extract

(D) Usage Loaded for Requested Date

If a Usage date does not match requested date, an additional check is performed to determine if Usage has been loaded for that requested date. Consideration is made for gap usage

(E) Multiple CRs Involved

A check is made to determine if the requested change row impacts another CR(s)

(F) CR(s) and TDSP Agree to create record

If the CR(s) and/or the TDSP do not agree on the requested change, ESIID is marked with ‘Unable to complete’

(G) Manually correct/verify relationship at ERCOT

If the CR(s) and/or the TDSP agree on the requested change, relationship is manually corrected and verified at ERCOT. Once completed, ESIID is marked with ‘Requested correction completed’

Variance 5LSE relationship record in both systems

but has date issues

17

ESI ID Data Extract Current Issues

1. Appears some MPs may not be loading daily extracts.• Some corrections requested already exist in ERCOT system.

2. Appears only a few MPs are using the extract as defined.• Or perhaps others have no issues.

3. Implementation of process and resolution procedures for LSE Record changes is taking longer than expected.

4. Some MP are just now submitting issues for Jan ’02. ERCOT will continue to work requests in trade month order.

5. Additional analysis for Large ESI IDs may benefit overall Market Settlements.

6. Variance requests during the Pilot Period (7-31-01 to 12-31-01).

– Market agreed that ERCOT should prioritize requests based upon trade dates that are being resettled.

– If any dates during pilot are to be resettled, Market would be notified, and then ERCOT would work those requests.

– Corrections crossing into 2002 should be dated to the applicable start date in 2001.

18

ESI ID Data Extract Potential Issues – for June RMS discussion

1. Multiple CR involvement - Record change request that crosses multiple CR records in ERCOT systema) Who owns responsibility for notification and reconciliation with TDSP

and CR(s)? b) What happens when one CR or more disagree?c) Acceptability of all CRs involved knowing who each other is?

2. LSE relationship record fixes for 2002 will be manuala) No 814 transactions will flowb) TDSPs will need to supply cancel/rebill transactions (810/867)

3. Completion of some CR requests will create de-energized periods in ERCOT systems where usage data existsa) Will Market Participants accept that usage will be UFE?b) What if usage exists and is really large?c) Is anyone responsible for “finding the correct CR” if completing another

CR request results in usage during a de-energized period?

19

ERCOT GISB 1.4 Update

RMS Meeting 05/15/03

20

GISB Migration Update

MONTH Production

GISB

Production

HTTPS

HOLD Ready GISB

Ready HTTPS

TOTAL

March 5 5 10

April 29 1 30

May 6 3 19 1 39

TOTAL 40 6 3 19 1 69

21

GISB Migration Update

• ERCOT has committed to work with all MPs to resolve issue surrounding GISB V1.4.

• A statement was put in the latest draft of the GISB EDM IMP Guide: – "Allowances: All reasonable attempts should be made to comply

with this section. Market Participant legacy systems that cannot meet the requirements of this section must contact ERCOT in order to be granted an exception. "

• All new TX SET 1.5 trading partners are being scheduled for migration.

• Flight 0703 will be first flight with GISB or FTP Replacement as the two options with ERCOT.

22

FasTrak Seminar Announcement

May 22, 2003

23

FasTrak Seminar 5/22/03

WHAT is the FasTrak Seminar?The FasTrak Business Group has created a Seminar to:• Relay the inception, evolution, and design of

FasTrak• Educate users on the functionality, design, and

extensibility of FasTrak• Suggest how best practices can optimize the

effectiveness of FasTrak• Discuss how enhancements to FasTrak can better

serve the user

24


WHO is the FasTrak Seminar for?

The FasTrak Seminar is open to:

• All FasTrak Users

• Business Managers

• Business Analysts

• RMS Participants

25


WHEN is the FasTrak Seminar?The FasTrak Seminar will be:

Thursday, May 22, 200310am – 3pm CST

ERCOT Taylor Control Center

Please RSVP by Monday, May 19, 2003 to Kerry Wariner ([email protected]) and Glen Wingerd ([email protected]).

26


Flight 0703 Planning Update

27

Flight 0703 Planning Update

Deadline for signup to the 0703 Flight is Thursday 5/22/03, 5pm CST.

TTPT Script sub-team made minor script revisions from the last flight.– Revisions were provided to ERCOT on 5/5/03. – ERCOT updated scripts and are now available online.– Any additional script revisions should be sent to Mike Woolsey at Oncor

([email protected])

• TTPT ETOD sub-team made recommendations for improvements to ETOD.– Short term improvements are in progress for 0703 Flight.– Long term improvements to ETOD are being reviewed by ERCOT and

TTPT team members. Where necessary, development projects will be created at ERCOT. Long term improvements will not be ready for this flight.

• Connectivity Testing kick off call – 6/9/03• Any requests for retesting are being asked to join the Flight 0703 for

best use of resources at MP companies and ERCOT.

28

ERCOT Market Services Organizational Update

Retail Market Subcommittee MeetingERCOT AustinMay 14, 2003

29

ERCOT Market ServicesERCOT Market ServicesMissionMission

Educate – members, staff and outside stakeholders about retail and wholesale market operations

Facilitate – issues resolution and market change process

Analyze – retail market performance, market segment business requirements, best practice opportunities

Communicate – between all stakeholders information important for improved market performance, while

respecting ERCOT’s role and the market’s requirement for confidentiality

30

ERCOT Market ServicesERCOT Market Services2004 Priorities2004 Priorities

•Implement improved transaction processes – MI/MO and others

•Identify and implement improved business processes and practices

•Build out retail protocols to institutionalize improvements

•Continue efforts to enhance transaction transparency for both initiating transactions and exception processing

31

ERCOT Market ServicesERCOT Market Services2004 Priorities2004 Priorities

•Build a retail market education and training program to meet the needs of market participants and improve market performance

•Establish a cash, forward market offering retail and wholesale MP’s more options, flexibility, transparency and liquidity

32

Richard GruberDirector of Market Services

(37 FTE)(1 Con)

Karen BergmanManager, Retail Market

Service and Testing(13 FTE, 1 Con)

Ted HailuManager, Wholesale

Market Services(14)

Dale GoodmanManager, MarketTransparency &

Reporting(4)

David Gonzales Acct.Manger (AM)

Jaime Brantley AM

Sherri Slagowski AM

Open FTE SAM.

Open FTE AM

Open FTE SAM

Open FTE SAM

Art Deller SAM

Bret Hunsucker SAM

Patrick Coon SAM

Pat Moast SAM

Bill Kettlewell AM

Lisa Sumruld AM

Leon Ricaud AM

Open FTE SAM

Tony Marsh AM

David Grussendorf ANLY

Mike McCarty

Denise Taylor

Mike Whitlock

Brian Shinners

Tim Frank

Mark Malinak

Contractor

Business ProjectMangement

Glen WingerdDavid OdleJohn KasselOpen FTEContractor

(5)

Kristi Hobbs LeadAcct. Manager

(LAM)

Retail Market Services and Testing Team

Suzette Wilburn,Lead Retail

Market Liaison

Susan Munson,Senior Retail

Testing Specialist

ERCOT Market Services (May ’02)ERCOT Market Services (May ’02)

33


Questions ?

update from ercot retail market services to rms may 15, 2003

Documents

ercot system variance

lse relationship record

mp system variance

ercot systemwho

lse record changes

date issues variance

implementation of process

variance requests