90 likes | 207 Vues
PWG COPS UPDATE. December 16, 2013. Annual Validation Completed for 2013. MARKET BENEFITS Provides more actual usage for initial settlement 28% of ERCOT load is currently measured through IDR meters 80% of that load must be estimated in initial settlement
E N D
PWG COPS UPDATE December 16, 2013
Annual Validation Completed for 2013 PWG COPS update 12/16/13
MARKET BENEFITS • Provides more actual usage for initial settlement • 28% of ERCOT load is currently measured through IDR meters • 80% of that load must be estimated in initial settlement • Allows for more granular interval data to assess • UFE allocation • Losses • Allows daily access versus monthly access to interval data by customers and REPs • Provides for customer access to historical usage requests without needing to contact the TDSP • Allows expedited switch and move-in/move-out timelines AMS vs IDR meters PWG COPS update 12/16/13
Market Hurdles Recommended to be Studied by PWG • How can data transmission be changed to minimize the impact to REP billing systems? Interval data sent on both the LSE files and 867s for IDR Required meters? • Will the 700 kW threshold be used to determine if TDSPs will bill using 4CP demand? • How will REPs know their customer is being billed on 4CP? Profile changes? TDSP Rate codes? • What ERCOT Protocols and Guides should to be revised ? • Will IDR customers be charged the Advanced Metering Cost Recovery Factor? By Legislation the Answer is No. • Can pulses be installed on AMS meters for customer energy management systems? • Can customers and REPs who currently download data directly from the meter continue to do so with AMS meters? Will the SMT be adequate? AMS vs IDR meters PWG COPS update 12/16/13
Detail slides following show questions raised and feedback from the webex group discussion Questions? APPENDIX: slides 6 - 9 PWG COPS update 12/16/13
Review language to allow the TDSP to manage the profile assignment process. (For example, a new premise with an AMS meter could be initially assigned IDR.) The initial thought was NIDR is required. Further review concludes the TDSP can initially assign NIDR or IDR. The Decision Tree currently assigns the initial Profile Type based on Weather Zone. It is recommended that this assignment be maintained. • How is a premise with a Meter Data Type of “IDR” handled in the IDR Requirements report. The IDR requirement process evaluates all ESI IDs that are currently “NOT” BUSIDRRQ. • How is a BUSIDRRQ data submission processed. The 15 min interval data for AMS ESIIDs is sent in an LSE file (non-TX set transaction). The TDSPs also, to assist in REP billing, send in a monthly NIDR read (TX set 867_03) which ERCOT also loads but is not used in settlement. Those monthly reads also help with the completion of service orders. (i.e. 867_03 finals.) Responses to Action Items from the 10/29 Call PWG COPS update 12/16/13
What is the percent change between Initial and Final Settlement readings for BUSIDRRQ? See the following charts. (“BUSIDRRQ Charts.xlsx” is included as a Key Document. This document includes the data and charts). Responses to Action Items from the 10/29 Call PWG COPS update 12/16/13
Competitive BUSIDRRQ – Initial vs. Final Percent Difference = (Total IDR @ Initial – Total IDR @ Final) / Total IDR @ Final PWG COPS update 12/16/13
Competitive BUSIDRRQ – Initial vs. Final PWG COPS update 12/16/13