PR30026 Resource ID (RID) Extract and Recorder Extract Data Extracts Working Group May 18, 2006 Laura Zotter ERCOT Market Operations D P O

Purpose of RID Extract  Provides MPs with Same Level of Granularity as Provided for Load  ESIID Data Allows MPs to Shadow Settle Their Load Volume - RID Data Allows MPs to Shadow Settle Their Generation Volume

Three Types of “RIDs”  ERCOT Polled Settlement (EPS) Data  Generator Site Data  NOIE Data  TDSP Read Generation Data  Generator Unit Telemetry Data (SCADA)

Who Receives the Extract  ERCOT Polled Settlement (EPS)Data  Generator Site Data —QSEs, Resource Entities (REs), & TDSPs  NOIE Data —QSEs, LSEs, & TDSPs  TDSP Read Generation Data  QSEs, REs, TDSPs & MREs (if not TDSP)  Generator Unit Telemetry Data  QSEs, REs, TDSPs

Recorder Extract  This extract provides interval data recorder information to entities that have no ownership rights to the data but have a justified business reason for receiving the data. Data may only be provided if it meets one of the conditions of Protocol Section – Exceptions.  Any of these four entities may receive recorder information:  QSEs, REs, TDSPs & MREs

Delivery Method  Consistent with Existing Extract Methodology  DDL Provided  Initial Extract of Dimensional and Transactional Data (excluding LSCHANNELCUT Header and Data)  Daily Process  Delivered to MP via TML  Packaged as.ZIP File with.CSV components  Counts Audit File Included

Timing of Delivery  Delivery Three Days After Data Imported Into Lodestar (Friday data is delivered on Monday)  EPS —Maximum of 9 Days After the Operating Day due to ERCOT Run78 Process  SCADA —Typically 4 Days After the Operating Day  TDSP Read —Dependent Upon Delivery of Data to ERCOT

General Notes  Delivery not Dependent on Data Completeness  Duplicates May Exist  Intraday Transactions Will be Delivered

Upcoming dates  6/1 – Internal go-live and beginning of stabilization period  6/22 – Information delivered to the market

Questions