1 / 17

Load and ICAP Tag Determination Processes

Load and ICAP Tag Determination Processes. Demand Resources Group Meeting Sturbridge Host Hotel May 19, 2006 Carmel Gondek (NU) on Behalf of the NE Assigned Meter Readers. Overview. Load Determination Process ICAP Tag Determination Process Load Reconstitution. Background.

kimi
Download Presentation

Load and ICAP Tag Determination Processes

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. Load and ICAP Tag Determination Processes Demand Resources Group Meeting Sturbridge Host Hotel May 19, 2006 Carmel Gondek (NU) on Behalf of the NE Assigned Meter Readers

  2. Overview • Load Determination Process • ICAP Tag Determination Process • Load Reconstitution

  3. Background • ISO-NE settlement process requires Assigned Meter Readers (AMR) to provide information for settlement purposes • Hourly values for each asset in the settlement model • 24 values each day • Generation Assets • Tie Lines Assets • Load Assets • ICAP Tag values for each load asset in the settlement model • 1 value each day

  4. Load Determination – Step #1 • Determine Hourly Loads by Metering Domain • Sum of Hourly Generation, Tie Lines and Low Voltage PTF Losses • Example: • Generator #1 + 400 MWH • Generator #2 + 600 MWH • Generator #3 +1000 MWH • Generator #4 +1200 MWH • Tie Line #1 + 500 MWH • Tie Line #2 +1550 MWH • LV PTF losses - 50 MWH Hourly Load + 5200 MWH

  5. Load Determination – Step #2 • Determine Customer Hourly Loads Served • Use customer actual hourly interval data where available • Estimate or “profile” hourly usage where actual interval data aren’t available • Add customers’ non-PTF losses • Sum of customer loads must be equal to the load served as determined in Step #1 (i.e. 5200 MWH) • Aggregate customer loads to appropriate supplier and load asset • Example for one hour: • Supplier #1 + 1200 MWH • Supplier #2 + 1500 MWH • Supplier #3 + 2300 MWH • Supplier #4 + 200 MWH Supplier Loads 5200 MWH

  6. Load Determination Summary • The load estimation process results in an hourly consumption value for each retail customer • Process varies by utility • Data are not necessarily stored for each customer • Customers’ hourly values are aggregated by supplier and account for, on a daily basis, customer migration between suppliers • The sum of the hourly values must be reconciled to the load actually being served in each hour (i.e. 5200 MWH in this one hour example)

  7. ICAP Tag Determination • The load estimation process results in each customer having a consumption value for every single hour • Once a year ISO-NE informs the HP AMRs of the system peak hour for the previous year • HP must determine ICAP tags for each retail customer • The starting point for this process is the customers’ consumption at the hour of the NE system peak

  8. ICAP Tag Determination Continued • An ICAP tag is developed for each retail customer • These customer tags have some level of elasticity to account for changes in the system including: • Non-PTF losses • Estimation error • The addition of new customers • The loss of former customers

  9. ICAP Tag Determination Continued • The sum of all customer ICAP tags must equal the MWH served at the hour of peak (i.e. 5200 MWH) • If there is a Demand Response Program (DRP) event at the hour of the NE peak the load must be reconstituted • If 10% of load leaves the Metering Domain then the peak hour value is adjusted to reflect the loss of load • Customer tags are assigned each day to the supplier responsible for each customer load and reported to ISO in aggregate by load asset • Competitive supplier • Provider of last resort

  10. Example #1 Assumptions: - no change in customer/ supplier relationship - no change in number of customers from day of actual peak Supplier #1 + 1200 MWH Supplier #2 + 1500 MWH Supplier #3 + 2300 MWH Supplier #4 + 200 MWH Total Tag Value 5200 MWH Example #2 Assumptions: - one single customer with a 1 MWH tag changed supplier (from #2 to #1) - no change in number of customers from day of actual peak Supplier #1 + 1201 MWH Supplier #2 + 1499 MWH Supplier #3 + 2300 MWH Supplier #4 + 200 MWH Total Tag Value 5200 MWH ICAP Tag Determination Examples

  11. Example #3 Assumptions: - no change in customer/ supplier relationship - 1,000 of Supplier #3’s customers left the system (approximately 100 MWH) Supplier #1 + 1224 MWH Supplier #2 + 1529 MWH Supplier #3 + 2243 MWH Supplier #4 + 204 MWH Total Tag Value 5200 MWH ICAP Tag Determination Examples Continued

  12. ICAP Tag Determination Facts • The once a year process to determine ICAP tags for a single peak hour or “case” can take 3+ weeks for a large utility • Each additional “case” could take another additional 3+ weeks for a large utility • The daily process to determine the ICAP tag by asset for one “case” can take up to 1 hour for a large utility • Each additional “case” would take another additional hour for a large utility

  13. Load Reconstitution • Manual 20 requires that if a demand reduction event occurs at the time of the NE system peak loads must be reconstituted as follows: • Interrupted loads: • For customers whose ICAP tag is based on their actual metered load add back the value of the interruption • For customers whose ICAP tag is based on profiled load the interruption value is not added back -- these values are socialized • Manual 20 does not specifically address how to allocate Demand Response Program ‘generation’

  14. CL&P Load Reconstitution Facts • NE system peak occurred on July 27, 2005 HE 1500 • A Demand Response Program event occurred in CT at this particular hour requiring the reconstitution of load • In CL&P’s territory the event displaced 117 MWH • 27% or 32 MWH were assigned back to specific customers • 73% or 85 MWH were socialized (majority of this was generation and not customer demand reduction) • The load reconstitution process for CL&P took more than 100 hours

  15. Load Reconstitution Issues • Process Improvement is necessary • The load reconstitution process relies upon timely, accurate and complete retail customer information • The information gathered at time of enrollment in the DRP should include a data verification component by the utility • Rules addressing allocation/socialization of generation events should be developed

  16. Load Reconstitution Issues Continued • The subgroup to address multiple ICAP tag “cases” and load reconstitution needs to gather the input from all HP AMRs • Issue has been raised at the MRWG and AMRs have been encouraged to participate • Further design details need to be explored before one can fully determine the impacts of multiple ICAP tag “cases” and load reconstitution

  17. Questions?

More Related