TDSP Recommendations for Improving IDR Data Loading intoLodestar -August 26, 2002Conf. Call

Prepared by James Cohea August 26, 2002 Page 1 of 4

Contents:

Page 1: Attendance record

Page 1: TDSP Recommendation/Problem Summary

Page 2: Action Item Summary List with updates

Page 3: Protocol Change proposal

Attendance Record:

Name / Company / Market Group / Email
1 / Gary Wariner / ERCOT / ERCOT /
2 / Jacqueline Mikus / ERCOT / ERCOT /
3 / James Cohea / ERCOT / ERCOT /
4 / Calvin Opheim / ERCOT / ERCOT /
5 / Ted Hailu / ERCOT / ERCOT /
6 / Karen Bergman / ERCOT / ERCOT /
7 / Kristi Hobbs / ERCOT / ERCOT /
8 / Silas M. Carson / Reliant Energy RRI / CR /
9 / Ed Skiba / Entergy / CR /
10 / Buddy Burr / ONCOR / TDSP /
11 / Eddie Marx / Utility Choice / CR
12 / Kyle Patrick / Relaint / AREP /
13 / Lori Smith / TNMP/First Choice / TDSP and AREP /
14 / Gary Spooner / TNMP/First Choice / TDSP and AREP
15 / James Dornan / TNMP/First Choice / TDSP and AREP
16 / Frank Billman / TNMP / TDSP
17 / Steve Bordelon / TNMP / TDSP
18 / Trina Ross / AEP / TDSP
19 / Charlie Backofen / AEP / TDSP /
20 / Alan Graves / AEP / TDSP /
21 / Steve Woo / Centerpoint / TDSP /
22 / Sonja Calhoun / Reliant Energy HLP / TDSP /
23 / A.J. Kubecka / Centerpoint / TDSP
24 / Meredith Lind / Centerpoint / TDSP /
Issue / TDSP Recommendation/Problem Summary
1 / Recommendation Summarized:
Allow 867_03 IDR consumption data to cross ESI ID Service History Record rows provided there is not a Move-in, Move-out, Retailer Switch, or Profile Change.
2 / Recommendations:
Part 1)Allow selective replacements of IDR data cuts
Part 2)Utilize an existing code in the 867_03 cancel and re-submit to indicate the data should not flow to lodestar.
3 / Recommendation:
Allow IDR data to load into Lodestar, even if there is a resulting gap. Provide a warning message to the TDSP, but do not reject the message.
4
Complete / Recommendation:
ERCOT should provide TDSPs with a view of the Lodestar usage data for each ESI for which the TDSP is the meter reading agent.
5 / Problem:
ERCOT does not always process all interval data in the order it is received, resulting in rejection of messages that were properly sent.
6 / Recommendation:
Modify the Production Report to provide a positive response for every LSE file loaded.
7 / Recommendation:
Modify Lodestar import validation process to disregard KVARH data (channel 3).
8 / Problem:
Processing of 867_03 Final for IDR data (only) prior to 867_04 Initial creates an incorrect stop date for the terminating transaction.
9 / Problem:
TDSP appear to be periodically sending invalid forwarding DUNS numbers in 867_03 transaction.

ACTION Item Summary:

Assigned to: / Issue Related to: / Action Item / Comments/Results
1a / Charlie Backofen,
Alan Graves / 1 / AEP to investigate standardizing on midnight as the cutoff time for all IDR 867_03s. / Charlie Backofen stated AEP will modify it’s IDR logic to standardize on stop times of 23:59:59. Expect to implement in October 2002.
1b / Lori Smith / 1 / TNMP to investigate standardizing on midnight as the cutoff time for all IDR 867_03s. / Assumption was made at 08-15 meeting that all of TNMP IDRs were being processed as requested when actually only the remotely read are being cut off at midnight. Programmatically processing of probe meters to cut off at midnight will require further analysis by TNMP
2a / RMS / 2 / RMS to assign to a task group to define details for adding an 867_03 “selective” replacement/restatement code to TX Set. / James Cohea to add line item to August 29th RMS meeting to request RMS create a task group to address adding an 867_03 “selective” replacement/restatement code to TX Set
3 / Susan Neel / 2 / Log request for TX SET to add a 867_03 code allowing ERCOT to bypass creation of .lse files for loading into Lodestar in cases where the ERCOT data will not change on cancel/rebills / Request logged by Susan Neel.
James Cohea to request this item be included in the scope of the Task group mentioned above.
4 / TDSPs / 9 / TDSPs to confirm forwarding DUNS numbers are correct and valid prior to sending 867_03s. /
  • ERCOT to send TDSP examples of incorrect duns numbers included in forwarding transactions.
  • TDSP to review and correct data files.

ERCOT Fixes Underway / The Items below are in the queue to be corrected and/or modified and will be released as soon as possible.
5 / ERCOT / 5 / ERCOT to correct problem with the sorting of IDR .lse fields and is modifying the sorting to:
  1. Transaction Type (Cancel /Original)
  2. ESI ID
  3. Start Date
/
  • In ERCOT test environment as of 08-26-2002.
  • ERCOT will notify TDSP when moved to production.

6 / ERCOT / 8 / ERCOT has initiated a system change to account for incorrect stop-times created by ERCOT for IDR 867_03 Finals.
Once fix is implemented, ERCOT will work with TDSPs to correct affected ESI IDs. /
  • In ERCOT test environment as of 08-26-2002.
  • ERCOT will notify TDSP when moved to production and request list of ESI ID needing data repair.

7 / ERCOT / 6 / ERCOT to add Unit of Measure identifier to production report. This has been identified as a defect and is being worked on now. /
  • In ERCOT test environment as of 08-26-2002. Awaiting database update from Lodestar to begin testing.
  • ERCOT will notify TDSP when moved to production.

8 / ERCOT / 6 / ERCOT has initiated internal process to correct the following problems with IDR data loading error reporting:
  • Gap date does not distinguish between estimated and actual data dates
  • 01 error message returned when 02 should be returned
  • Interval data rejected as missing ESI ID when ESI ID is actually NIDR
/
  • In ERCOT test environment as of 08-26-2002.
  • ERCOT will notify TDSP when moved to production.

9 / ERCOT / 3 / ERCOT to investigate modifying the Lodestar Validation Logic to allow loading of IDR data that would create gaps. /
  • ERCOT has initiated internal project to remove gap validation for IDR data loading (PR 20078-01). Implementation but this is contingent on TDSPs agreeing to protocol change requiring all IDR data to be submitted in full days – Start = 00:00:00 and stop = 23:59:59.
  • See information at the end of this summary related to the proposed Protocol changes

“Project” Related / The items below will be identified as enhancements inside a single project to be submitted for prioritization and funding. ERCOT project request will be created to include the items scoped below. TDSPs are urged to contact their appropriate committee representatives to “push” prioritization of the associated project.
A / 3 / When Lodestar validation logic is modified allow loading of IDR data that would create gaps, what additional validation are needed?. /
  • Additional validation logic may need to be added to ensure all IDR data starts at 00:00:00 and stops at 23:59:59.

B1 / 6 / ERCOT to add positive response row to IDR Production report for each .lse file loaded into lodestar.
B2 / 6 / Add additional error reporting to notify TDSP of transactions that don’t make it to the .lse creation phase. (such as duplicate transactions)
C / 7 / ERCOT to modify IDR loading logic to omit creation of .lse file for units of measure other than KWH. /
  • TDSP to disregard errors until exclusion logic implemented.

D / 5 / ERCOT and TDSPs to define enhancement required to IDR Data loading. (some options)
  1. Load transaction in the order they were received by the TDSP
  2. Create a pre-processor that goes through the .lse files and looks for cancels. If it finds cancels, look to see if the referenced original is in the file. If so, remove both transactions in the file. Then sort the file and process as normal

E / 1 / Research modifying IDR loading logic such that 867_03 data loading is allowed to cross ESI ID Service History Rows for select Service History items (such as Zip Code change). /
  • This requires additional definition and analysis to identify specific fields.

F / 2 / Institute 867_03 “selective” replacement process as part of TX SET version implementation
G / 2 / Institute 867_03 ERCOT .lse create bypass as part of TX SET version implementation

Proposed Protocol language modification (to be included in PRR that will be submitted by ERCOT in September):

10.9.2 TDSP Metered Entities

TDSPs will be required to ensure that the meters for which they are responsible comply with the standards for metering Facilities of the relevant Governmental Authority. In addition, IDRs used for settlement shall conform to the following:

(1)IDRs must be able to capture energy consumption in increments consistent with, or in fractions of, ERCOT defined settlement time interval (currently fifteen (15) minutes);

(2)Regardless of data retrieval method, interval data shall be provided on a schedule that supports the requirements of final settlement;

(3)IDRs must have battery or other energy-storage back-up to maintain time during power outages;

(4)IDRs must have time synchronization capability;

(5)Meter clocks used within ERCOT shall be maintained on a time reference that enables the TDSP to submit data on the Central Prevailing Time. The meter clock shall be synchronized to within at least +/- 5% of the settlement interval when compared to the National Institute of Standards and Technology (NIST) Atomic Clock;

(6)IDRs may record at increments less than ERCOT defined settlement and be aggregated to the appropriate settlement interval time block by the TDSP prior to the data being sent to ERCOT;

(7)New and replacement IDRs used for settlement must be able to capture energy in increments of five (5) minutes (excluding memory allocation). At market open they will be programmed to read at 15-minute intervals; and

(8)Settlement intervals will divide each hour in the following standard:

XX:00:01 through XX:15:00

XX:15:01 through XX:30:00

XX:30:01 through XX:45:00

XX:45:01 through XX:00:00

(9)For data submitted to ERCOT starting October 01, 2002, IDR data will contain only whole days with start times beginning at 00:00:00 and stop times ending at 23:59:59.