1 / 11

ESI ID SERVICE HISTORY AND USAGE DATA EXTRACT

This system allows Market Participants to extract ESI ID level data for transparency, reconciliation, shadow settlement systems, and reducing disputes, aiding in resolving data variances.

branscome
Download Presentation

ESI ID SERVICE HISTORY AND USAGE DATA EXTRACT

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. ESI ID SERVICE HISTORY ANDUSAGE DATA EXTRACT SYSTEM CHANGE REQUEST (SCR 727) February 24, 2003

  2. Purpose of the Extract • Provide data transparency to TDSPs and LSEs for ESI ID level data that ERCOT utilizes in market settlement. • Allows Market Participants to compare ERCOT data to their internal source system data • Market Participant can identify data variances and raise issues to the appropriate party for resolution • Provide Market Participants with the ability to develop shadow settlement systems. • Should reduce settlement disputes since data variances should be reconciled prior to True-up settlement • Allows entities to close-the books after True-up settlement

  3. What is a Service History Extract? • Data record rows which contain the characteristics associated with a given ESI ID for a specific time period that is used by ERCOT for data aggregation and settlement purposes • Record Start Time • Record Stop Time • LSE Code (Retailer, CR, AREP, NOIE) • TDSP Service Area Code • MRE Code • Profile Id • Station Code • Distribution Loss Factor Code • Region Code • ESI ID Status • & data elements associated to ESI IDs registered as Load Resources Note: See the Data Definition Language (DDL) document for specific naming convention and data elements

  4. What is a Usage Extract? • Data record rows which contain usage data that has been submitted by the TDSP/MRE for each ESI ID and has successfully passed validation loaded into ERCOT’s Lodestar system • CR will receive all records where they were REP of Record for time period associated to the usage record • TDSP will receive all records where they were TDSP of Record for time period associated to the usage record • Interval Data Recorders (IDR): record rows include each interval between the start and stop times of the meter read with a separate data row for each trade day included in the 867_03 • Non-Interval Data Records (Non-IDR): • Non-Demand: Record rows containing the energy consumption value between the start and stop dates of the meter read • Demand: The above record rows plus record rows containing a single demand value established between the start dates and stop dates of the meter read

  5. Identifies Manual Data Corrections ESIID_Delete ESIIDSERVICEHIST_Delete ESIIDUSAGE_Delete LSCHANNELCUTHEADER_Delete ESI ID Extract Database Structure Interval Data Records Entity Name and Duns ESIID Existence , Entity Relationships & Settlement Characteristics LSCHANNELCUT DATA TDSP ESIID ESIID SERVICE HISTORY LSCHANNELCUT HEADER REP MRE LSCHANNELCUT STATUS PGC Non-Interval Usage Records ESIIDUSAGE Station to UFE and CM Zone Mapping STATION SERVHIST CMZONE

  6. Initial Historical Data Extracts • Data record row files will be created for each TDSP, LSE (and MRE where they are different for the TDSP or LSE) for all ESI ID Service History record rows where they are identified as the TDSP, LSE, or MRE. • Usage history provided beginning with any record that crosses 7/31/2001. • Associated tables and incremental updates to support the ESI ID Service History records • TDSP, REP, MRE, PGC, Station Service History and CM Zone tables

  7. Daily Incremental Update Extracts • Capture updates/changes that were loaded to ERCOT’s Lodestar system for the previous day’s processing and which were subsequently captured in the Data Archive. • Example: Monday’s updates/changes to Lodestar that are captured in Data Archive on Tuesday morning, will be posted to the ERCOT Portal on Wednesday. • Daily incremental extracts will be posted by 9:00 a.m. each day, seven days a week Monday Tuesday Wednesday Changes & Updates to Lodestar Changes Captured In Data Archive For Monday Extracts Produced for Monday

  8. Data Extract Delivery • Historical ESI ID Service History and Usage Data Extract • ERCOT Portal (Reports Explorer/Market Participant folder) • Requires MP to have Digital Certificate • CD(s) (overnight delivery) • Incremental daily update extracts • ERCOT Portal (Reports Explorer/Market Participant folder) • Requires MP to have Digital Certificate • ERCOT retains 30-days of history on the Portal

  9. Market Participant’s Responsibilities • Receive Data Definition Language (DDL) • Create relational database for extract data • Create “comparison tool” • Reconcile data extract information with internal system records • Download historical data extract and sequential daily incremental update extracts • Identify variances and report per defined mechanisms • TDSPs and CRs • Submit data extract variances via FasTrak (http://fastrak.ercot.com) • No less than 30 days prior to scheduled resettlement date • Two types of variances for ERCOT resolution: • ESI ID Service History data extract variances • ESI ID usage data extract variances • Non-ERCOT (CR/TDSP) data extract variances: • ESI ID attributes (profile ID, loss factor code, station assignment, etc.) • Non-Opt In Entities (NOIEs) • Submit data extract variances via “Create Service Request” – ERCOT Portal

  10. SCR 727 Implementation Plan Market Participants Valid Variances Existing Transactional Db Variances Identified 6 Compare Tool DDL 3 5 1 2 Variances To Be Resolved MP to MP MP 727 Db NOIEs TDSPs & CRs 1 4 MP to ERCOT Portal FasTrak DDL Initial & Daily Extracts ERCOT

  11. Timing of Key Events • February 5th-20th …… Extract development • February 18th ………. Market notification of SCR 727 • February 18th ………. DDL distributed and posted to ERCOT Portal • February 21st ……….. “Technical” conference call • February 24th-27th ….. Creation of TDSP and LSE initial historical ESI ID Service History and Usage data extracts • February 27th ………. “Technical” conference call – 10:00 a.m. • March 3rd …………... Implementation – initial historical extracts posted to the ERCOT Portal, or CD with the initial historical extract will be sent to the applicable TDSPs and LSEs • March 3rd ………….. Incremental daily ESI ID Service History and Usage update extracts from the day the initial historical extract was pulled through 3/1/03 will be posted to the ERCOT Portal • March 4th ………….. Begin regular posting process to the ERCOT Portal of daily incremental ESI ID Service History and Usage update extracts • March 4th ………….. “Business” Conference Call – 1:00 p.m. • March 14th ………… TDSPs and CR to submit data extract variance requests for January 01 & 02, 2002

More Related