1 / 9

COPS ERCOT calculated interval data change explanation

This document discusses the challenges ERCOT faces in ensuring timely completion of data aggregation and the increasing system processing times. It also addresses the need for system efficiencies in the Nodal Market and the impact of missing AMS meter data on settlements. The document highlights the system changes needed and the failure of ERCOT to communicate effectively with the market regarding these changes.

jmastin
Download Presentation

COPS ERCOT calculated interval data change explanation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. COPSERCOT calculated interval data change explanation Jackie Ashbaugh / Don Tucker ERCOT 2/08/2011

  2. Issue – System Processing Performance issues with AMS • Struggling to ensure timely completion of data aggregation • Trends of System Processing Times Increasing and some spikes • Why be concerned with increasing system processing times • Completion of data aggregation process drives settlements • Looking for system efficiencies for Nodal Market • Timely issuing of settlements statements • Looked for drivers to increased processing times • Saving “c” cuts (the ERCOT calculated interval data for an ESI ID where no data is loaded)identified as time consuming production process • Estimate .02 seconds to save an interval data “c” cut to the database • 3.3 minutes per 10,000 • 33.3 minutes @ 100,000 • ~6 hours @1,000,000 • More AMS meters being deployed • increasing risks if AMS data is missing COPS Meeting

  3. Why a System Change? • Why stop producing “c” cuts for Nodal? • Concern of being able to complete data aggregation in Nodal if AMS meter data was missing • Requirement for timely completion of settlements and invoicing • Once a “c” cut is written to the database, when the data is loaded from the TDSP, there are two additional data records (delete and insert) written in ERCOT’s data replication process for long term data retention • Replication lag increases with a significant number of delete and insert records occurring within one day affecting the timeliness of data availability and extract postings COPS Meeting

  4. Market Communication & System Changes Needed • Why not write NPRR changing data submittal timeline for AMS? • TDSP’s already committed to providing data by initial settlement and to SMT Portal the day after the Operating Day • Missing data would be result of issues beyond their control • Why was the “c” cut turned off for nodal and left on for zonal? • Concerned about mitigation plan for 6 million AMS meters • Provide opportunity to communicate with the Market • ERCOT failed to discuss with the market and notice the market in a timely manner COPS Meeting

  5. What ERCOT did… • For Nodal settlements (Operating Days 12/1/2010 and forward), ERCOT data aggregation processes perform the calculation of the missing ESI ID interval data in memory and no longer saves the individual ESI ID calculated data. COPS Meeting

  6. Market Impacts • Interval data “c” cuts are provided in the Supplemental IDR Required Interval Data Extract and the Supplemental AMS Interval Data extract for all Operating Days prior to 12/1/2010 • “C” cuts could have been used by the market for: • Shadow settlement processes • Identify when TDSP loaded data was missing at ERCOT • Market Capabilities with posted data • To determine missing interval data at ERCOT, MPs have the ability to: • Query loaded extract data for no data loaded for a given Operating Day for active ESI IDs • Use the ESI ID Market Data Transparency Web Services • To determine if interval data was estimated for an ESI ID and proxy days was used in settlements: • Load Estimation Counts Report provides a total sum of ESI IDs that had calculated interval data during the settlement of the operating day • Public Reference Data Extract (PRDE) provides PROXYDAY table COPS Meeting

  7. Failure to Discuss and Communicate • ERCOT missed bringing this to COPS and SEWG for Discussion • Fully intended to discuss at SEWG • Discuss at and update COPS based on SEWG discussions • ERCOT missed the cutover step for sending 30 day market notification regarding this change • Market communications • 12/19/2010 – announcement made on Nodal stabilization market call • 12/20/2010 – market notice sent • 12/20/2010 – announcement made at SEWG • 1/4/2011 – addressed MP agenda item at NATF COPS Meeting

  8. 2010 Real Life Incident • October • Missing AMS data for initial settlements for 4 Operating Days • Over 1 million active AMS ESI IDs had no data loaded for initial settlement • Impacted settlements batch processing with long data aggregation run times • When the data was fixed by the MP, there was a significant lag in ERCOT’s data replication • Emergency workaround had to be developed and implemented to minimize market impacts • Three days of extract postings delayed and were out of Protocol for some extracts COPS Meeting

  9. Q&A COPS Meeting

More Related