MIS LOG IN

SCR727

Summary

Title ESI-ID Service History & Usage Extracts
Next Group
Next Step
Status Approved

Action

Date Gov Body Action Taken Next Steps
No updates have been made to this issue.

Voting Record

Date Gov Body Motion Result
No updates have been made to this issue.

Background

Status: Approved
Date Posted: Dec 13, 2002
Sponsor: Reliant Energy
Urgent:
Sections:
Description: Service History Extract Within a REPs ESI ID Service History Extract, ERCOT would provide information regarding all the ESI IDs assigned to that REP, their service history with the current REP, their Load Profile and other characteristics necessary for the REP to be able to estimate load for settlement. This extract would also allow the TDSPs to validate the EDI documentation previously sent to ERCOT. The following is an example of the data elements that are required: ESI-ID INFORMATION (IDR & Non-IDR customers) CUSTOMER_ID ELECTRIC_SERVICE_IDENTIFIER START_TIME STOP_TIME TRANSACTION_DATE ESIID_SERVICE_HISTORY (IDR & Non-IDR customers) CUSTOMER__ID DISPATCHFL SERVICECODE METER_READER_CODE START_TIME T_AND_D_PROVIDER_CODE STOP_TIME REGIONCODE RETAIL_PROVIDER_CODE DISPATCHASSETCODE STATION_CODE STATUS PROFILE_CLASS_CODE ZIP LOSS_CODE POWER_GENERATOR_CODE TRANSACTION_DATE DISPATCH_TYPE Usage Extracts ERCOT will make available ESI ID Usage Extracts to provide REPs and TDSPs information to validate the actual usage ERCOT has received from TDSPs and uses for settlement. Within an Initial ESI-ID Usage Extract for a REP, ERCOT must provide all usage information loaded into ERCOT™s Settlement system for ESI IDs assigned to the REP from the date of the request through the earliest Trade Date requiring True-Up Settlement. A daily REP ESI ID Usage Extract would provide the usage information received by ERCOT and loaded into its Settlement system for a day. This extract would be used by the REP or TDSP to append to the REP Initial Usage Extract in order to compile a complete record of usage data existing in ERCO€™s Settlement system. The following is an example of the data elements that are required: ESIID_USAGE (Non-IDR Meter Information) CUSTOMER_ID TOTAL START_TIME ON_PEAK STOP_TIME OFF_PEAK BILLING_MONTH MDPK METER_READ_STATUS SPK USAGE_DAILY_AVERAGE GLOBPROCID TRANSACTION_DATE TIMESTAMP METER_TYPE IDR_USAGE_HEADER (IDR Meter Information) INTERVAL_DATA_ID DSTPARTICIPANT CUSTOMER_ID ORIGIN (Indicates Meter or Profiled) RECORDER ACCEPTREJECTSTATUS MARKET_INTERVAL DESCRIPTOR START_TIME TIMESTAMP STOP_TIME COUNT SECONDS_PER_INTERVAL TRANSACTION_DATE MEASUREMENT_UNITS_CODE IDR_USAGE_DATA (IDR Meter Information) INTERVAL_DATA_ID TRANSACTION_DATE TRADE_DATE 15 MINUTE INTERVAL READ VALUE (Meter Read value would show estimated and actual values)
Reason: The requested information will provide REPs with ESI-ID level data used within ERCOT™s settlement aggregation process. REPs can verify which meter values ERCOT used as actual usage or estimated usage within the settlement statement process. Currently, REPs receive only the aggregated Load Profile data within the QSE Load Extract. This data will also provide TDSPs a means to validate the EDI documentation previously sent to ERCOT.

Key Documents

Related Content