9/20/2007

DEWGSCR 727 ESIID Service History & Usage Extract Re-Baseline Follow Up

Jackie AshbaughERCOT

29/20/2007

SCR 727 Extract Re-Baseline Summary

• PR 50024_01 SCR 727 Phase II (SCR 740) is in “Closing” status• Defects were logged as 3 SIRs

– Extract refresh and counts web services– De-aggregation web service– Turn on XML output feature

• The Re-Baseline web service will only be available one time per year per MP and will be re-evaluated during ERCOT I-Test

– Performance and ability to deliver will be reassessed at this time• Once the Re-Baseline web service is in production, the current SCR 727 Historical

Data Request process will be discontinued (data files back to 2003)– Requests for missed files (one-offs), similar to LOAD, GEN, etc. will continue to be

accepted

39/20/2007

ERCOT SCR 727 Re-baseline Survey

• Considerations and Questions for the extract re-baseline web service implementation:

• What is the minimal amount of the service history and usage data for ESIIDs owned by MP needed? Today, MPs have service history and usage for ESIIDs they own from 7/31/2001 to current.

– 12 months of ESIID usage is needed for data aggregation to shadow settle

• **Note: If the date range for the amount of data that ERCOT provides in the re-baselines is changed, there would be a change on the daily extract to provide inserted/deleted/changed data for the same date range.

• Do you have any concerns with the amount of data that would have to be downloaded and/or uploaded?

• How often should the amount of data that ERCOT is providing via web services and extracts be evaluated by DEWG?

Updated Note: Annual Validation for Load Profiles takes a variable amount of usage data to calculate 18-22 months. (Applies to TDSPs only)

49/20/2007

ERCOT SCR 727 Re-baseline Survey Results

• Would not request re-baseline– 1 market participant

• 18-24 months of data– 1 market participant

• 18 months of data– 5 market participants

• 24 months of data– 2 market participant to match the historical data in their systems

• 2003 trade dates to current– 1 market participant

• July 2001 trade dates to current– 1 market participant

Note: Includes feedback from 3 TDSPs and 8 LSEs.

59/20/2007

SCR 727 Extract 18 Month Re-baseline Example

• Consider using a static number of days instead of a month range that has a variable number of days (i.e. 540 days)

• In the case that the Re-baseline goes back 18 months:– LSEs and TDSPs receive:

• ESIID records for ESIID Service History records received.• All dimensional tables. These are also available via the Publice Reference Data

Extract in the Report Explorer public folder.• IDR and NIDR Usage applicable to the ESIID Service History records provided that

apply to the operating days where EU.STOPTIME > (SYSDATE – 540)• ESIID Service History records for you as the REP of RECORD or TDSP will be provided

where– ESH.STARTTIME < SYSDATE– ESH.STOPTIME > (SYSDATE – 540)

» null STOPTIMEs are evaluated as SYSDATE

69/20/2007

ESIID Service History Examples with 9/17/2007 request date

• In Example 1:– Rep “A” and TDSP “999” would receive the ESH

row. The StartTime is prior 540 days, but the range of ownership includes dates within the last 540 days.

– Usage would only be received for where the STOPTIME >(SYSDATE – 540)

• In Example 2:– Rep “A” would receive nothing. – Rep “B” would receive 10/25/06 – 2/4/07. – Rep “C” would receive 2/9/2007 – null.– TDSP “999” would receive all rows from

1/2/2004 forward.– Usage would only be received for where the

STOPTIME >(SYSDATE – 540) as it applies to the MP relationship on the ESH rows

• In Example 3:– Rep “A” would receive the 1/1/03 – 4/15/06 and

10/25/06 – 2/4/07 rows. – Rep “C” would receive the 2/9/07 – null row.– TDSP “999” would receive all rows from 1/1/03

forward.– Usage would only be received for where the

STOPTIME >(SYSDATE – 540) as it applies to the MP relationship on the ESH rows

Example 1:      

StartTime StopTime Rep Status TDSP

1/1/2003 null A A 999

Example 2:      

StartTime StopTime Rep Status TDSP

1/1/2003 1/1/2004 A A 999

1/2/2004 10/24/2006   D 999

10/25/2006 2/4/2007 B A 999

2/5/2007 2/8/2007   D 999

2/9/2007 null C A 999

Example 3:      

StartTime StopTime Rep Status TDSP

1/1/2003 4/15/2006 A A 999

4/16/2006 10/24/2006   D 999

10/25/2006 2/4/2007 A A 999

2/5/2007 2/8/2007   D 999

2/9/2007 null C A 999

79/20/2007

Questions?