Settlement Timeline Workshop November 6, 2012

Agenda TDSP’s AMS Data Flow Overview AMS LSE Data Process Monthly 867_03 Process for AMS Meters TDSP’s Conventional IDR Data Flow Overview Conventional IDR Meter Process TDSP’s Non-AMS/Non-IDR Meter Reading Overview Non-AMS/Non-IDR Meter Process TDSP’s Unmetered Usage Overview Unmetered Usage Process Settlement Reduction Timeline TDSP’s Concerns and Potential Impacts TDSP’s Questions? Q&A

TDSP’s AMS Data Flow Overview Daily Register Read Interval Usage Data Data Collection Meter Data Management System (MDMS) “Daily 15-Minute Interval Data LSE Files” COLLECTOR Customer Information System (CIS) “867 Usage Processing” Daily 15-Minute Interval Data LSE Files SMT Transaction Management Systems and NASEB Server REPS Customers ERCOT “867 Usage Transactions” Retailers

AMS LSE Data Process Usage and reads are collected from AMS meters through an automated communications process by the TDSPs. Readings are processed in TDSP’s Meter Data Management Systems (MDMS) where intervals are identified as either Actual (A) or Estimated (E) usage data and are labeled as such in the daily LSE files. Estimates are mainly the result of communication failures while trying to retrieve data from the AMS meter, so in order to fill those missing intervals, also known as gaps, intervals are estimated to produce a LSE file with all 96 intervals filled with 15-minute interval usage. 96 intervals are the norm, but 92 Intervals or 100 Intervals are necessary for Spring and Fall changes in the Central Prevailing Time (CPT). Estimates may be replaced by actuals if actuals are available when the AMS meter is interrogated in subsequent request for usage data. High percentage of market’s LSE Interval Data is produced daily LSE Files containing 15-minute interval data are sent by the TDSPs to both ERCOT for Real Time Settlements (RTM) and Smart Meter Texas (SMT) for Customer’s and REP of Record’s use.

Monthly 867_03 Process for AMS Meters TDSPs provide both: LSE files that provide daily 15-minute interval data and Monthly summarized usage are based upon the TDSP’s cycle read schedules . The LSE file register readings from the prior and current month’s cycle readings are used to calculate consumption (usage) for the current month. Monthly cycle readings will indicate in the 867_03 TX SET transaction as Actual (A) or Estimated (E) and if readings are estimated a reason for estimate will be provided in the 867_03 transaction by the TDSP. Estimates in this case are mainly the result of communication failures while trying to retrieve data from the AMS meter, so in order to fill those missing intervals, also known as gaps an 867_03 Monthly Cycle Reading may be the result of an estimate. TDSPs will communicate these readings and usage to ERCOT and REPs of Record via the TX SET 867_03 Monthly Usage transaction where ERCOT will ONLY forward this transaction to the REPs of Record for their Customer’s invoicing since ERCOT uses the LSE data for settlements.

TDSP’s Conventional IDR Meter Data Flow Overview MV90 Systems Meter Called or Polled On Cycle Read Schedules Conventional IDR Meters or Telephone Lines or Field Polled at Meter IDR Usage and Billing System “867 Usage and Processing” 867_03 Monthly Cycle Interval Data Billing and Invoicing by REP 867_03 Monthly Cycle Interval Data Transaction Management Systems and NASEB Server Customers REPS ERCOT

Conventional IDR Meter Process TDSPs collect readings and usage from IDR meters through: Telephone/Dial-up Communications Meter Crews polling IDR meter at Premise Automated System Processes Readings are processed by TDSP’s MV90 Systems where intervals are either Actual (A) or Estimated (E) usage and are labeled as such once the monthly 867_03 TX SET transaction is created by IDR Usage and Billing systems. Again, estimates are mainly the result of communication failures while trying to retrieve data from the IDR meter, so in order to fill those missing intervals, also known as gaps, intervals are estimated to produce the 867_03 TX SET Monthly Usage transaction that contains all 2880 intervals filled with 15-minute interval data. All Conventional IDR readings and data are processed according to TDSP’s monthly cycle meter reading schedules. TDSPs will communicate these readings and data to ERCOT and REP of Records via the TX SET 867_03 Monthly Usage transaction for ERCOT’s Real Time Settlements and to REPs of Record for their Customer’s invoicing.

TDSP’s Non-AMS/Non-IDR Meter Reading Overview Customer Information System (CIS) Non-AMS or Non-IDR Meter types “867 Usage Processing” Field Read Meters according to TDSP’s On Cycle Meter Read Schedules 867_03 Monthly Cycle Readings & Usage 867_03 Monthly Cycle Readings & Usage Billing and Invoicing by REP Transaction Management Systems and NASEB Server “867 Usage Transactions” Customers REPS ERCOT

Non-AMS/Non-IDR Meter Process These meter types require meter readings to be preformed by field personnel at the premise. TDSPs use their Customer Information Systems (CIS) and/or Billing Systems to create TX SET 867_03 Monthly Usage transactions. Cycle readings are indicated in the 867_03 transaction as Actual (A) or Estimated (E) usage, if estimated a reason for estimate will be provided in the 867_03 transaction by the TDSP. In this case, estimates are mainly the result of meter access or inaccessible to field personnel. All NON-AMS or NON-IDR meter readings are processed according to TDSP’s monthly cycle meter reading schedules. TDSPs will communicate these readings and usage to ERCOT and REPs of Record via the TX SET 867_03 Monthly Usage transaction for ERCOT’s Real Time Settlements and to REPs of Record for their Customer’s invoicing.

TDSP’s Unmetered Usage Overview Database “ESI IDs Unmetered Services and Usage ” CIS and Billing System “867 Usage Processing” 867_03 Monthly Cycle Readings 867_03 Monthly Cycle Readings Billing and Invoicing by REP Transaction Management Systems and NASEB Server “867 Usage Transactions” Customers REPS ERCOT

Unmetered Usage Process Unmetered usage is based upon the type of unmetered services that is assigned to an ESI ID. TDSPs use their Customer Information Systems (CIS) and/or Billing Systems to create TX SET 867_03 Monthly Usage transactions. Unmetered ESI IDs are processed according to TDSP’s monthly cycle meter reading schedules. TDSPs will communicate this usage to ERCOT and REPs of Record via the TX SET 867_03 Monthly Usage transaction for ERCOT’s Real Time Settlements and to REPs of Record for their Customer’s invoicing

Settlement Time Reduction TDSP’s Concerns and Potential Impacts: Depending upon the reduction in settlement timelines may result in: A review of TDSP’s staffing and systems needs to support: LSE file exceptions where daily LSE 15-minute interval data failed to load and/or were rejected at ERCOT. AMS or Conventional IDR Data Collection failures. Maybe the result of a significant or catastrophe event. EPS meters that failed to communicate when ERCOT attempted to retrieve data. Maybe the result of telephone communication problems and out of TDSP’s control (i.e. telephone line failed).

TDSP’s Concerns and Potential Impacts: Depending upon the reduction in settlement timelines may result in: An increased risk to the market that less actual data may be available, and/or any corrections or updates where necessary to prior data, for AMS and Non-AMS, Conventional IDR, Unmetered and EPS premises.

TDSP’s Concerns and Potential Impacts: Conventional IDR meters continue to be processed by the TDSPs according to a monthly cycle read schedule through a different system than AMS meters and IDR meters were not included in TDSP’s PUCT approved AMS deployment plans. TDSPs’ AMS deployment plans for meters and systems did not include those meters already required by ERCOT to have IDR meters, this is consistent with PURA 39.107(h).

TDSP’s Questions? Is the goal of making changes to the settlement timeline only applies to Initial Settlements? Are there any ERCOT or Market plans to make changes to Final and True-up timelines and/or the current protocols requirements that apply to Final and True-up Settlements? In order to reduce market cost and impacts, could ERCOT evaluate what it would take to make changes to reducing their Settlement timelines that do not impact the TDSP’s current business processes and systems?

TDSP’s Questions(cont.)? Regardless of final decisions approved by the market concerning Settlement timeline changes, will ERCOT continue to support and apply Protocol’s Section 11.4. “Load Data Aggregation” when usage data is missing or unavailable as a Settlement’s fallback process? 11.4.1 Estimation of Missing Data The Data Aggregation System (DAS) will perform estimation of missing interval and non-interval retail Load meter consumption data for use in Settlement when actual meter consumption data is unavailable.

Questions and Answers?