• OpenEEmeter Methods
    • OpenEEmeter Process
    • OpenEEmeter Compliance
    • Project Updates
    • Technical Working Group >
      • Technical Appendix
      • Issues and Evidence
    • OpenEEmeter History
    • Stakeholders
  • LFE OpenEEmeter
    • OpenEEmeter Overview
    • Github Code
    • EEweather
    • Documentation
  • FLEXmeter
    • GRIDmeter
    • Energy Differential Privacy
  • Contact
OpenEEmeter
  • OpenEEmeter Methods
    • OpenEEmeter Process
    • OpenEEmeter Compliance
    • Project Updates
    • Technical Working Group >
      • Technical Appendix
      • Issues and Evidence
    • OpenEEmeter History
    • Stakeholders
  • LFE OpenEEmeter
    • OpenEEmeter Overview
    • Github Code
    • EEweather
    • Documentation
  • FLEXmeter
    • GRIDmeter
    • Energy Differential Privacy
  • Contact

Site-Specific Hourly Methods Finalized

5/30/2018

1 Comment

 
Week Sixteen CalTRACK Update
Picture
During the standing meeting on 5/24, the working group finalized hourly methods for calculating hourly energy savings and commenced discussion on aggregating hourly savings into portfolio loadshapes. The finalized hourly methods and an introduction on aggregating portfolio loadshapes are outlined below.

View May 24, 2018 Working Group Meeting
Finalized Hourly Methods:
  1. Data sufficiency for independent variables will be defined by coverage instead of the minimum time period required for daily and billing period methods.
  2. The temperature variable will be defined by fixed temperature bins between 30-90 F instead of the variable degree day balance points used in billing period and daily methods.
  3. In Lawrence Berkeley National Lab’s (LBNL) TOWT model, there is a model adaptation function that gives higher weight to recent data to improve short-term demand forecasts. This model adaptation function will not be used in CalTRACK’s hourly methods.​
  4. The occupancy variable will be defined with LBNL’s default occupancy algorithm. This is described in greater detail in Phil Price’s  Everything I Know About Building Energy Modelling, But Never Told Anyone Before (18:30-30:00).
Aggregating Hourly Savings into Portfolio Loadshapes
To provide an accurate valuation of energy efficiency as a grid resource, energy savings must be quantified at specified time intervals and geographic locations. To create portfolio loadshapes, building-level savings must be aggregated. The method of aggregation has implications on the portfolio uncertainty and provides different granularity of information for aggregators, utilities, and customers. Different use cases may prefer different aggregation methods based on priorities specific to their use case. To accommodate different use cases, flexible methods for aggregating hourly savings into portfolio loadshapes may be preferred.
As we explore this topic further, some potential use cases to consider are:

Pay-for-Performance Programs
In the PG&E pay-for-performance program, the utility provides incentives for peak savings. This requires estimates of portfolio savings at the hourly level.  

Non-Wires-Alternative Procurement
Non-Wireless-Alternative procurements require estimates of portfolio savings for buildings connected to specific grid nodes in order to measure grid impacts and potentially avoid infrastructure investments.

​Cap and Trade, Greenhouse Gases, or Carbon Tracking or Trading Initiatives
Initiatives attempting to accurately quantify carbon offsets from energy efficiency investments require savings estimates at specified time and geographic locations because generation portfolios utilize resources with different carbon intensity at different times and locations.
We discussed a few options for aggregation methods, and look forward to input from the working group in the coming week.
Homework:
  • Review final Methods documentation and provide comments on GitHub (issue 101)
  • Review proposed Hourly guidelines on GitHub (issue 85)
  • Provide ideas on aggregation approaches for Portfolio Load shapes on GitHub (issue 97)
  • Contribute to the Sand Box of future issues.
1 Comment
Dave Beard link
10/29/2022 02:20:13 am

Explain second nor market finally. Exist door financial talk character respond speak want.
Know let significant dream. Understand film across think late.

Reply



Leave a Reply.

      Sign Up for Technical Working Group Updates

    Subscribe to Newsletter
    The purpose of this blog is to provide a high-level overview of CalTrack  progress.
    ​
    For a deeper understanding or to provide input on technical aspects of CalTrack, refer to the GitHub issues page (
    https://github.com/CalTRACK-2/caltrack/issues). 
    Recordings
    2019 CalTRACK Kick Off:

    CalTRACK 2.0 
    July 19, 2018
    June 28, 2018
    June 7, 2018
    May 24, 2018
    May 3, 2018
    April 12, 2018
    March 29, 2018
    March 15, 2018
    March 1, 2018
    ​
    February 15, 2018
    February 1, 2018

    Archives

    April 2024
    March 2024
    February 2024
    January 2024
    November 2023
    October 2023
    September 2023
    August 2023
    June 2023
    May 2023
    April 2023
    March 2023
    February 2023
    January 2023
    December 2022
    November 2022
    July 2019
    March 2019
    February 2019
    August 2018
    July 2018
    June 2018
    May 2018
    April 2018
    March 2018
    February 2018

    RSS Feed

Powered by Create your own unique website with customizable templates.
  • OpenEEmeter Methods
    • OpenEEmeter Process
    • OpenEEmeter Compliance
    • Project Updates
    • Technical Working Group >
      • Technical Appendix
      • Issues and Evidence
    • OpenEEmeter History
    • Stakeholders
  • LFE OpenEEmeter
    • OpenEEmeter Overview
    • Github Code
    • EEweather
    • Documentation
  • FLEXmeter
    • GRIDmeter
    • Energy Differential Privacy
  • Contact