MARS Advanced Metering – ERCOT Market Facing Changes Jackie Ashbaugh Manager Data Integrity and Administration 3/9/2009

2 867_03 Data Processing TX Set 867_03 transactions will continue to be used for submitting data to ERCOT for both NIDR and IDR (IDR required only) data –NIDR 867_03s for Advanced Metered ESIIDs will be used to complete Service Order requests –NIDR 867_03s are required to be sent to LSEs for billing use ESIIDs with a BUSIDRRQ profile type must continue to receive traditional 867_03 interval data transactions for usage loading and to complete Service Order requests (i.e. BUSIDRRQ_SOUTH_IDR_NWS_NOTOU) 867_03 data is loaded once per day during nightly batch process 867_03 interval data loads into the LSCHANNELCUTHEADER and LSCHANNELCUTDATA tables in the Settlement and Billing database MARS3/9/2009

3 Advanced Metering Interval Data Processing AMS ESIIDs will reflect an IDR meter type in the profile code but will not contain a BUSIDRRQ profile type code Interval data to be submitted via AMS LSE files Loading of AMS LSE files occurs throughout the day (still in design) Interval data loads into an AMS interval data table (still in design) in the Settlement and Billing database NIDR monthly reads via 867_03 must be submitted in addition to AMS data to satisfy the needs of REPS regarding monthly billing and retail service order activity (i.e. Switch, MVO, MVI, etc.) MARS3/9/2009

4 Changes to Reports 867_03 IDR & NIDR Activity Reports –Reports will be provided to TDSPs and any REP DUNS provided in N1SJ loops –Report accounts for each transaction submitted for loading to ERCOT –Report shall be distributed daily to Market Participant’s FTP sites (No change) –Report naming convention example: MPINFOHERE_867_IDR_ACTIVITY_YYYYMMDD_HHMMSS.csv AMS Interval Data LSE Activity Reports –Reports will be provided to TDSPs only –Report accounts for each transaction and file submitted for loading to ERCOT –Report shall be distributed via TML/MIS –Report naming convention and frequency of delivery will be dependant on solution design Missing Consumption Report –Will evaluate missing consumption for 38 days back based on the Profile Code for 867_03 NIDR data, 867_03 IDR data, and AMS LSE interval data IDR Requirement Report –Will evaluate based on NIDR meter type Profile Codes IDR Protocol Compliance Verification –Will evaluate BUSIDRRQ profiled ESIIDs only MARS3/9/2009

5 Changes to Reports - continued Load Estimation Counts Report –Presented by meter type and AMS IDR will be included in IDR meter type calculations Load Estimation Volumes Report –Presented by meter type and AMS IDR will be included in IDR meter type calculations MARS3/9/2009

6 Changes to Extracts ESIID Service History and Usage Extract (SCR727) will be modified to remove ESIID interval data –The following objects will no longer be provided: LSCHANNELCUTHEADER LSCHANNELCUTHEADER_DELETE LSCHANNELCUTDATA New supplemental extracts to be used in conjunction with the 727 extract will be available. I.Supplemental IDR Required Interval Data Extract This will include the LSCHANNELCUTHEADER, LSCHANNELCUTHEADER_DELETE, LSCHANNELCUTDATA for IDR required ESIIDs. II.Supplemental AMS Interval Data Extract This will include the AMS interval data tables equivalent to the IDR required data in the extract stated above. MARS3/9/2009

7 New Web Services Additional Web Services All are setup with the same required and optional fields as those in the IDR required web services Output file will be in the AM interval data format, which is different from IDR required in the LSCHANNELCUTHEADER and LSCHANNELCUTDATA format –Provide AMS interval data for a trade date Description: This data request is used to assist Market Participants in requesting the AMS interval data for owned ESIIDs/UIDESIIDs as of a particular point in time, for a particular trade date (Operating Day). –Provide ESIIDs where AMS interval data not loaded for a trade data Description: This data request is used to assist Market Participants in requesting a list of ESIIDs/UIDESIIDs that are profiled AMS and do not have AMS interval data loaded as of a particular point in time for a particular trade date (Operating Day). –Provide AMS interval data for ESIIDs I own Description: This data request is used to assist Market Participants in requesting the AMS interval data for owned ESIIDs/UIDESIIDs that are profiled AMS as of a particular point in time. MARS3/9/2009

8 Changes to Existing Web Services Modified Web Services on TML (name changes only) –Provide IDR usage data for a trade date Changed to: Provide IDR usage data for a trade date (IDR Required) Description: This data request is used to assist Market Participants in requesting the IDR Required interval data for owned ESIIDs/UIDESIIDs as of a particular point in time, for a particular trade date (Operating Day). –Provide ESIIDs where IDR usage data not loaded for a trade date Changed to: Provide ESIIDs where IDR usage data not loaded for a trade date (IDR Required) Description: This data request is used to assist Market Participants in requesting a list of ESIIDs/UIDESIIDs that are IDR Required and do not have interval data loaded as of a particular point in time for a particular trade date (Operating Day). –Provide all ESIID extract records Changed to: Provide all ESIID extract records (IDR Required) Description: This data request is used to provide Market Participants all ESIID data for owned ESIIDs. –Provide ESIID extract records for Logical Keys Changed to: Provide ESIID extract records for Logical Keys (IDR Required) Description: This data request is used to provide Market Participants logical key data of the ESIID extract for owned ESIIDs. MARS3/9/2009

9 Changes to Existing Web Services Removed Web Service from TML – Provide IDR transaction data for ESIIDs I own This service is not actively used by MPs and is driven by the tran_id. Modified Web Service on TML –Provide IDR usage data for particular ESIIDs I own Changed to: Provide IDR usage data for particular ESIIDs I own (IDR Required) Description: This data request is used to assist Market Participants in requesting the AMS interval data for owned ESIIDs/UIDESIIDs that are profiled AMS as of a particular point in time. Required fields: –Point in Time –Trade date range requesting 1-31 days of data –Channel (Load or Generation) –Output Results (Header or Header & Interval Data) –Output Format (CSV or XML) Optional field: –Upload file to provide ESIIDs to limit the request MARS3/9/2009

10 Market Aids/Tools MarkeTrak –IDR Data Extract Variances may be filed for both sources of IDR data –MarkeTrak User guide must be updated to reflect the re-purposing of the IDR DEV for either AMS LSE or 867_03 IDR data –No code changes to MarkeTrak are necessary. All required fields for the DEV can be provided regardless of the source of the IDR data ESIID WEB SERVICES – SCHEDULE DATA REQUEST –Updates will be made to the Market Data Transparency User Guide and XSDs to account for changes/additions to web services ESIID SERVICEHISTORY & USAGE EXTRACT (727) –Updates to ESIID Service History and Usage Extract User Guide and DDLs to include changes to extracts and how to use supplemental extracts Supplemental IDR Required Interval Data Extract Supplemental AMS Interval Data Extract AMS Interval Data LSE Activity Reports –Document will be created to outline and define the content of the AMS Interval Data LSE Activity Reports AMS Interval Data LSE Error Code Market Aid –Document will be created to define error codes used in the AMS Interval Data LSE Activity Reports MARS3/9/2009

11 QUESTIONS? MARS3/9/2009