140 likes | 283 Views
4-CP Discussion. October 16,2002 Retail Market Subcommittee Austin, Texas. Protocol References. 9.8 Transmission Billing Determinant Calculation
E N D
4-CP Discussion October 16,2002 Retail Market Subcommittee Austin, Texas
Protocol References 9.8 Transmission Billing Determinant Calculation ERCOT will provide the market with the determinants defined below to facilitate billing of Transmission access service. ERCOT will not be responsible for billing, collection or dispersal of payments associated to Transmission access service. 9.8.1 ERCOT shall calculate and provide to Market Participants via MIS the following data elements annually to be used by TDSP’s as billing determinants for Transmission access service. This data shall be provided by December 01 of each year. This calculation shall be made in accordance with the requirements of the PUCT. The data used to perform these calculations shall come from the same system(s) used to calculate settlement-billing determinants used by ERCOT: 1. The 4-Coincident Peaks (4-CP) for each TDSP, as applicable. 2. The ERCOT average 4-CP. 3. The average 4-CP for each TDSP, as applicable, coincident to the ERCOT average 4-CP. Average 4-CP is defined as “the average Settlement Interval coincidental MW peak occurring during the months of June, July, August, and September.” Settlement Interval MW coincidental peak is defined as “the highest monthly 15 minute MW peak for the entire ERCOT Transmission Grid as captured by the ERCOT settlement system.”
Quantity Conversion & Sum by TDSP • For each load cut, there are 96 interval of MWH data • Unique combinations of LSEGUFE for the 4CP trade dates • 949 in August • 1,121 in September Quantity Conversion consists of converting the MWH data into KW KW = MWH X 4 X 1000 • LSEGUFE Load Cuts are Summed by TDSP for the peak interval. • Note: Cuts where the Lodestar LSE Code equals a DC Tie name were • omitted from the TDSP totals.
Load Profile Code: Distribution Loss Factor Code (A-E or T) UFE Settlement Zone Congestion Management Zone Lodestar TDSP Code: (1 = RELIANT) Lodestar QSE Code: (14 = RELIANT) Lodestar LSE Code: (1 = RELIANT LSE) Load Segment Cut Type: LSEGUNADJ = Base Load values LSEGDL = Base Load + Distribution Losses LSEGTL = Base Load + Distribution Losses +Transmission Losses LSEGUFE = Base Load + DL + TL + UFE Data Cut Definitions
Versus Lodestar TDSP to 4 CP Entity Mapping 126 Unique TDSPs in Lodestar 77 Load Entities in 4 CP Submissions • Lodestar TDSPs are mapped to the corresponding 4-CP Load Entity Listing. • KW Per Lodestar TDSP is summed per mapping. • Complete mapping list is included in ERCOT filing with PUC
Secure Aggregation Load Cut Data for 4 CP Trade Days Select Peak Interval and Convert MWH to KW Sum KW per Lodestar TDSP (Omitting DC Ties) Sum Lodestar TDSPs to 4CP Entity List Compile 4 Months data into Average 4CP for PUC Filing Process Summary Determine Time of Peak for each 4 CP Month
August 15th @ 16:30 September 7th @ 16:30 • 433.02 MWH • 1,732,080 KW • 414.85 MWH • 1,659,400 KW Energy is allocated to load cuts in competitive TDSP service areas based upon UFE allocation mechanism in Section 11 of Protocols. UFE Data
What’s New with the Resettlement Data? Less Estimation • 100% of IDR Data was Present • 99+% or Non-IDR Data was Present Data Modifications • Corrections to NOIE Wholesale Points • Removal of ESI IDs created in error • Removal of Substation ESI IDs • Correction to Generation Site Data New Peak Day Revealed for August • New Peak is August 15th @ 4:30 PM • (Previous August peak was August 22nd @ 4:45 PM)
Comparison of August Data (March ’02 data VS October ’02 Data) 0.0% Change For The Remaining 70 Entities
Comparison of Sept 7th Data (March ’02 data VS October ’02 Data) 0.0% Change For The Remaining 72 Entities
Comparison of March ‘02 Filing to October ‘02 Filing 0.0% Change For The Remaining 72 Entities