LRS Update Meeting LRS Participants and Profiling Working Group October 27, 2005.

LRS Update Meeting

LRS Participants and

Profiling Working Group

October 27, 2005

2

Agenda

Process update Sample Point Reconciliation Interval Data Validation – TDSP’s Interval Data File Delivery – CR’s

Action Plan

3

Sample Point Reconciliation

Sample point installation summary report Summary of primary and replacement

points installed by TDSP, profile type, weather zone, and stratum number

Status indicates if cell is fully installed, no. of points to install and whether replacements are available.

CSV file sent to TDSP’s

4


TDSP_ID PROFILEGROUP WZCode STRATUMSERVICE VOLTAGE TotReqSampCount TotalSamplePtsInstalled Status

A BUSLOLF South 3 S 31 8 23 Pt to InstallA BUSNODEM SCent 1 S 4 3 1 Pt to InstallA BUSNODEM South 2 S 31 11 20 Pt to InstallA BUSNODEM South 2 S 31 30 1 Pt to InstallA BUSNODEM South 3 S 31 12 19 Pt to InstallA RESHIWR South 2 17 16 1 Pt to InstallA RESHIWR South 3 17 15 2 Pt to InstallA RESLOWR South 3 23 22 1 Pt to InstallA RESLOWR West 1 4 3 1 Pt to InstallA BUSMEDLF North 2 S 3 2 1 Pt to Install

Sample point installation Summary Report

Only TDSP’s with outstanding installs were sent this report however any TDSP can request this report.

5

LRS Sample Point Replacement Guidelines

Once an (LRS) IDR has been installed, a sample point may be replaced for the following reasons:

Unsafe conditions / vicious animals Demolition / service removed / ESI ID status changed to Inactive De-energized for 6 or more consecutive months after IDR installed Competitively-owned NIDR meter is to replace (LRS) IDR at Premise ESI ID’s Profile Type is out of scope (e.g., BUSIDRRQ, NMLIGHT,

NMFLAT) Customer request for (LRS) IDR removal Premise switches to OMR The sample is terminated or refreshed by ERCOT.

ERCOT LRS documents can be found at: http://www.ercot.com/Participants/loadresearchsampling.htm

6


Interval data cuts were compared with ‘ValidIDRCut’ events from the tracking log. Existing cuts and events have been reconciled.

Queries to detect LRS database inconsistencies such as: Recorder ID is active, sample point has

been removed Recorder install date is earlier than

Sample Point start date (excluding TXUED legacy sample points.)

7

Interval Data Validation

October 1, 2004 00:00 was chosen as the start of the analysis period because approx. 80 % of the IDR installations were complete at this time.

The analysis start date may move until enough validated data is available to perform the analysis.

Most validation reports begin with this date/time. Data prior to this time has been retained but will not

be validated and loaded into C/S LodeStar.

8


9


The following validations are performed prior to loading into C/S LodeStar. Received LS file cuts with no recorder in the

LRS Recorder table Valid recorders with no data received Recorder indicated as removed but still receiving

data Cuts that are overdue or contain gaps. Look for Service History changes in Profile Type,

Weather Zone or Status (de-energized greater than 6 months.)

10

LS Cuts with No Installed Rec

Rec ID File Name Interval nterval File transfer Date IN LSFile Start Dt End Dt 1 TDSP_200411230925.ls 25OCT04:08:46 23NOV04:01:00 23NOV2004:15:16:07 1 TDSP_200501240107.ls 22DEC04:01:31 24JAN05:01:00 24JAN2005:15:15:47 1 TDSP_200412270036.ls 23NOV04:01:01 22DEC04:01:30 27DEC2004:15:15:30 1 TDSP_200502220045.ls 24JAN05:01:01 22FEB05:00:30 22FEB2005:15:15:20 1 TDSP_200504250106.ls 24MAR05:01:01 25APR05:00:30 25APR2005:15:15:31 1 TDSP_200503240104.ls 22FEB05:00:31 24MAR05:01:00 14APR2005:16:43:56 1 TDSP_200505250158.ls 25APR05:00:31 25MAY05:01:00 25MAY2005:15:15:33 1 TDSP_200507061205.ls 25MAY05:01:01 02JUL05:00:45 06JUL2005:15:15:55 1 TDSP_200507260110.ls 02JUL05:00:46 26JUL05:01:00 26JUL2005:15:15:40 1 TDSP_200508240806.ls 26JUL05:01:01 24AUG05:01:00 24AUG2005:15:15:35 1 TDSP_200509301426.ls 24AUG05:01:01 27SEP05:01:00 30SEP2005:15:16:00 2 TDSP_200410151108.ls 30SEP04:11:16 01OCT04:09:00 15OCT2004:15:15:51 2 TDSP_200410151108.ls 13SEP04:16:46 30SEP04:11:15 15OCT2004:15:15:51 2 TDSP_200410151108.ls 30AUG04:01:01 13SEP04:16:45 15OCT2004:15:15:51 3 TDSP_200501101353.ls 04JAN05:11:31 10JAN05:08:30 11JAN2005:15:15:41 3 TDSP_200501310038.ls 10JAN05:08:31 31JAN05:00:15 31JAN2005:15:15:41 3 TDSP_200501310038.ls 10JAN05:08:31 31JAN05:00:15 31JAN2005:15:15:41 3 TDSP_200503020651.ls 31JAN05:00:16 02MAR05:00:15 02MAR2005:15:15:29 3 TDSP_200504010054.ls 02MAR05:00:16 01APR05:00:30 14APR2005:16:45:24 3 TDSP_200505020045.ls 01APR05:00:31 02MAY05:00:30 02MAY2005:15:15:34 3 TDSP_200506030626.ls 02MAY05:00:31 02JUN05:01:15 03JUN2005:15:15:23 3 TDSP_200507010735.ls 02JUN05:01:16 01JUL05:01:00 01JUL2005:15:15:26 3 TDSP_200508030026.ls 01JUL05:01:01 02AUG05:01:15 03AUG2005:15:15:23

11

Recorders with No Interval Data

ESIID Recorder Id Install Date Removal Date 85352 152429 08JUN2004:00:00:00 19AUG2004:00:00:00 102884 152721 01JUN2003:00:00:00 . 106784 152868 01JUN2003:00:00:00 . 122306 158722 03AUG2005:00:00:00 . 122922 158745 23AUG2005:00:00:00 . 123514 154182 09SEP2004:00:00:00 10SEP2004:00:00:00 96318 155083 09AUG2004:00:00:00 10AUG2004:00:00:00 96694 158457 02OCT2004:00:00:00 . 96894 158521 30SEP2004:00:00:00 . 97492 158489 17SEP2004:00:00:00 . 97650 158497 19AUG2004:00:00:00 . 97770 158500 01OCT2004:00:00:00 . 84046 156358 12NOV2004:00:00:00 . 77224 158751 22SEP2005:00:00:00 . 78200 156362 19NOV2004:00:00:00 . 78826 156363 30NOV2004:00:00:00 . 79312 156365 01NOV2004:00:00:00 . 78382 158750 21SEP2005:00:00:00 . 80846 156369 02NOV2004:00:00:00 . 81448 158748 07SEP2005:00:00:00 . 77708 158729 08AUG2005:00:00:00 .

12

LRS Overdue Data Report ESIID Recorder Id Stop Date Days Overdue of Last Cut

76322 153526 24MAY05:08:45 153.1 _________________________________________________________ 76638 153904 07JUL05:09:00 109.1 _________________________________________________________ 76656 153908 09SEP05:10:45 45.1 _________________________________________________________ 76668 153899 26AUG05:10:45 59.1 _________________________________________________________ 76678 158601 06SEP05:11:15 48.0 _________________________________________________________

13

LRS Gap Report ESIID Recorder Id Gap Begin Date Gap End Date Gap Days

76622 154430 04FEB05:09:01 14JUL05:23:59 160.6 ____________________________________________________________________________ 84882 152508 22DEC04:11:31 24JAN05:23:59 33.5 25JAN05:00:01 25JAN05:12:45 0.5 ____________________________________________________________________________ 85142 153528 21DEC04:12:16 24JAN05:13:45 34.1 ____________________________________________________________________________ 85146 153984 24JUN05:18:01 25JUL05:23:59 31.2 26JUL05:00:01 26JUL05:15:45 0.7 ____________________________________________________________________________ 113010 154738 15NOV04:00:16 14DEC04:01:00 29.0 16AUG05:00:16 21SEP05:01:15 36.0 ____________________________________________________________________________

14

Sample Maintenance Report

See Excel handout.

15


C/S LodeStar is used. Interval Data is input (D110) Validation tests are run (X210) Outage, Zero, and NonNormal messages that

are below the tolerance levels do not cause a cut invalid status so these messages are deleted.

The time intervals covered by the Zero messages are compared with the corresponding status in the ESI ID Service History table. The zero messages with a corresponding active status are retained.

Output simplified messages to Excel file.

16

C/S LodeStar Time Conventions

LS file header record date format is: "MMDDYYhhmm".

C/S LodeStar rounds the Start Time down by 1 minute and adds "00" seconds. For example, an input cut start time of 09/16/04 12:50 results in a LodeStar time of 09/16/04 12:49:00.

The cut end time is set at 1 sec before the interval end time so the end time seconds are "59". For example, an input cut end time of 11/12/04 14:00 results in a LodeStar time of 11/12/04 13:59:59.

17

Validation Tests

Internal and External Validation Current Tolerances for Internal Validation

ENERGY 0.98 1.02 (Energy Discrepancy Test) OUTAGE 96 (Uncorrected Power Outages Test) NON-NORMAL 15 (Non-Normal Intervals Test) ZERO 288 (Zero Intervals Test) SPIKE 10 50% (Spike Intervals Test) HIGH 999.99 1 (High Interval Demand Test) LOW 0 (Low Interval Demand Test)

18


Internal,TDSPNoCBHCA10021,10032789400841590,11/15/04-00:00:00,11/18/04-08:29:59, (INTERNAL) ENERGY DIFFERENCE (M - I): 21044.593 RATIO (M/I): 1.668

Outages,TDSPNo,CBHSA10013,10032789442773231,11/18/04-09:00:00,11/30/04-13:14:59, OUTAGES: 216 @ 11/18/04-09:14:59

Spike,TDSPNO,CBLSA10091,10032789487888760,11/23/04-11:30:00,12/29/04-15:14:59, SPIKE: 1 @ 12/27/04-08:29:59

Zeros,TDSPNo,CBLSA10141,10032789414456080,10/04/04-15:30:00,11/03/04-14:44:59, ZEROS: 1488 @ 10/15/04-13:59:59

Sample of Validation Report

19

Validation Tests

Energy Discrepancy Test The cut’s energy usage based on its meter

readings is compared with the energy usage calculated from the interval data values. If the cut fails the energy discrepancy test, the following validation message is written.

(INTERNAL) ENERGY DIFFERENCE (M - I): 70904.634 RATIO (M/I): 1.604

20

Validation Tests

Uncorrected Power Outages Test The number of consecutive intervals with status

codes = ‘1’ must not exceed the limit specified by the OUTAGE parameter in the Validation Environment File. If the number of consecutive uncorrected power outages exceeds the limit, the test fails and the following validation message is written.

OUTAGES: nnnn @ 09/22/04-14:29:59 where nnnn is the number of consecutive uncorrected power outages.

21

Validation Tests

Number of Intervals Test The actual number of data intervals in a cut must

correspond to the difference between the cut’s start-time and stop-time. If the expected number of intervals does not equal the recorded number of intervals, the test fails and one of the following validation messages is written.

(INTERNAL) COMPUTED STOP TIME: 12/27/04-12:29:59 4 INTERVAL(S) SHORT

(INTERNAL) COMPUTED STOP TIME: 01/01/05-02:59:59 12 INTERVAL(S) LONG

22

Validation Tests

Non-Normal Intervals Test The number of consecutive intervals with non-

normal status codes must not exceed the limit specified by the NON-NORMAL parameter.

A non-normal status code is defined as a value of ‘2’ to ‘9’. If the number of consecutive non-normal status codes exceeds the limit, the test fails and the following validation message is written.

NON-NORMAL: nn @ 06/28/04-00:14:59 Where nn is the number of non-normal intervals

23

Validation Tests

Spike Intervals Test The cut must not include any abnormally high

peaks or “spikes”. Both the number of peaks to be averaged within a cut and a percentage not to be exceeded are defined by the SPIKE parameter. If the spike test fails, the following validation message is written.

SPIKE: 1 @ 10/27/04-10:14:59 1 @ 10/27/04-09:59:59

24

Validation Tests

High Interval Demand Test The number of intervals with an abnormally high

demand must not exceed the limit defined by the HIGH parameter in the Validation Environment File. If the HIGH test fails, the following validation message is written.

HIGH DEMAND: 10 @ 08/24/04-17:59:59 24 @ 08/25/04-16:14:59 7 @ 08/26/04-1

25

Validation Tests

Low Interval Demand Test The number of intervals with an abnormally low

demand must not exceed the limit defined by the LOW parameter the Validation Environment File. If the LOW test fails, the following validation message is written.

LOW DEMAND: 10 @ 08/24/04-17:59:59

26

Validation Tests

Zero Intervals Test The number of consecutive intervals in a cut

whose values are 0.0 may not exceed a limit specified by the ZERO parameter. If the ZERO test fails, the following validation message is written.

ZEROS: 672 @ 08/09/04-13:14:59

27

Validation Tests

Current tolerances for External Validation Time 15 15 (Recording Period Match Up Test) Meter 2 1 (Meter Reading Match-Up Test)

28

Validation Tests

Recording Period Match Up Test The stop-time of the current cut and the start-time of the

following cut must be within the underlap (gap) and overlap tolerances specified on the TIME parameter. If the stop-time of the current cut is less than the start-time of the following cut an underlap exists and the following validation message is written to the validation message file.

(EXTERNAL) TIME UNDERLAP: 3974 INTERVAL(S) If the stop-time of the current cut is greater than the start-

time of the following cut and they do not fall within the same interval, an overlap exists and the following validation message is written.

(EXTERNAL) TIME OVERLAP: 3974 INTERVAL(S)

29

Validation Tests

Meter Reading Match-Up Test If meter readings exist for the cut series, the meter-stop-reading

of the current cut and the meter-start-reading of the following cut must be within the underlap and overlap tolerances specified in the METER parameter. If the meter-stop-reading of the current cut is less than the meter-start-reading of the following cut, an underlap exists. If the size of the underlap is greater than the limit specified in the METER parameter, the cut fails and the following validation message is written.

(EXTERNAL) METER UNDERLAP: x UNITS where x = size of the underlap. If the meter-stop-reading of the current cut is greater than the

meter-start-reading of the following cut, an overlap exists. If the size of the overlap is greater than the limit specified in the METER parameter, the cut fails and the following validation message is written.

(EXTERNAL) METER OVERLAP: x UNITS where x = size of the overlap.

30

Validation Tests

Merge Attribute Match-Up Test The unit-of-measure and seconds-per-interval

fields for the current cut must be equal to the corresponding fields for the following cut. If either of these fields is not equal, the cut fails the test and one or more of the following validation messages are written.

(EXTERNAL) UNIT OF MEASURE DISCREPANCY

(EXTERNAL) SECONDS-PER-INTERVAL DISCREPANCY: n1 FOLLOWED BY n2

31

Validation Discussion

Suggestions to improve the reports? Frequency to receive reports? (i.e.

weekly, monthly, quarterly) Would the TDSP’s prefer the validation

reports in quarterly pieces or everything at once?

Other issues?

32

ERCOT First Contacts

AEP – Bill Boswell (512) 248-3169 [email protected]

CenterPoint – Diana Ott (512) 248-3934 [email protected]

TXU ED – Ron Hernandez (512) 248-6523 [email protected]

Sharyland and TNMP – Adrian Marquez (512) 248-3915 [email protected]

Nueces – Theresa Werkheiser (512) 248-6551 [email protected]

33

Interval Data File Delivery – CR’s

Only cuts that pass internal and external validation are delivered

Current data covers period from 10/01/04 to approximately 12/31/04.

No totalized cells are included in the current data Both CSV and LSE formatted files delivered to CR

mailboxes. Environment file delivered that links the encrypted

Recorder_Id's (used in the interval data files) to the sample point cell specified by Profile Type, Weather Zone, Stratum, and Service Voltage

All three files have been pre-pended with the CR DUNS+4 and the delivery date/time.

34


As a prerequisite for receiving LRS files from ERCOT, each CR will have downloaded the current FTP Replacement client with an updated digital certificate

Use FTP Replacement protocol (ReceiveALL) to download files

Call ERCOT Help Desk if you have problems (512) 248-6800

35


Normal Day (4 placeholder commas at end of record)AEFG4567,20040422,96,0.21,0.2,0.19,0.18,0.17,0.17,0.16,0.16,~~~~~,0.19,0.31,0.3,0.29,0.28,0.27,0.26,0.25

,,,,

Spring DST Day (8 placeholder commas at end of record)ABCD12345,20040404,92,0.22,0.22,0.21,0.2,0.2,0.19,0.19,0.18,~~~~~,0.29,0.29,0.28,0.27,,,,,,,,

Fall DST Day (0 placeholder commas at end of record)AKLM4567,20041031,100,0.22,0.21,0.2,0.2,0.19,0.19,0.18,0.18,~~~~~,0.31,0.31,0.3,0.29,0.28,0.27,0.25,0.24

,0.24,0.23,0.24,0.23

First Day of Cut (‘n’ placeholder commas at beginning of record based on cut start time)

ANOP1234,20004112,96,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,0.13,0.2,0.2,0.2,~~~~~,0.37,0.36,0.36,0.35,0.33,0.32,0.31,0.3,,,,

Last Day of Cut (‘n’ placeholder commas at end of record based on cut stop time)AQRS4567,20041221,96,0.21,0.21,0.2,0.2,0.19,0.19,0.18,0.18,~~~~~,0.06,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

CSV Format

36


154357,100104,96,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,0.06,0.695,0.145,0.17,0.13,0.12,0.12,0.1,0.18,0.17,0.18,0.77,0.07,0.855,0.13,0.955,0.885,0.445,1.035,1.23,0.685,0.97,1.63,0.95,2.135,2.19,1.855,1.8,2.16,1.58,2.165,1.38,1.895,1.265,1.86,1.175,1.86,1.27,1.575,1.69,1.205,1.825,1.09,1.11,1.735,1.15,1.03,1.36,1.315,0.975,1.135,1.575,0.985,0.86,1.355,1.235,0.675,,,,

154357,102904,96,1.025,0.83,0.595,0.84,0.95,0.685,0.38,0.84,0.26,0.67,0.74,0.23,0.785,0.24,0.855,0.265,0.815,0.235,0.8,0.22,0.76,0.2,0.82,0.24,0.845,0.33,0.62,0.34,0.43,0.765,0.6,1.275,2.055,0.895,0.875,0.275,0.85,0.53,0.615,0.96,0.33,1.005,0.785,0.495,0.905,0.91,0.41,0.945,1.105,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

Sample of Actual Data – CSV Format

* Each row contains data for a 24 hour day (except DST days.)

* Start and end interval times are positional

37


.LSE file format .LSE file format is also a .CSV format .LSE file format documentation will be sent if

requested

00000001,154357,1,20041001094500,20041029121459,Y,Y00000002,1517.0,3903.1,1.0,0.0,0.005,0.0,900,1,0,-1,,,00000003,00000004,20051013115925000,M10000000,0.0599999986589, ,,0.69499998446554, ,,0.144999996759, ,,0.1699999962002, ,,0.12999999709427, ,,0.11999999731779, ,,0.119999997

Sample of Actual Data – LSE Format

38

Action Plan

Based on the analysis start date of October 1, 2004, we are closing-in on 1 year of data.

Immediate tasks: Continue to build and document processes Load replacement cuts Build LodeStar CNTL files to totalize 100% sampled cells Build CNTL files to move validated cuts to ELDB Build analysis CNTL and ENV files

Next steps: Current profile model assessments by Profile Type and

Weather Zone Sample design and sample point selection for Round 2 Build new profile models.

39

Action Plan

Early December: Schedule a conference call to discuss on-going data validation and delivery issues

End of 2005: Resolve all data issues covering 1 year of data.

03/31/06: Analysis of current profile models complete.

04/30/06: Sample Point selection for round 2 complete.

06/30/06: Complete profile model building.

This Action Plan is contingent upon ERCOT and the TDSP’s resolving data validation issues by year end.

LRS Update Meeting LRS Participants and Profiling Working Group October 27, 2005.

Documents

Transcript of LRS Update Meeting LRS Participants and Profiling Working Group October 27, 2005.