Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reporting to isolate envelope deployment #413

Open
jtlangevin opened this issue Aug 26, 2024 · 2 comments
Open

Reporting to isolate envelope deployment #413

jtlangevin opened this issue Aug 26, 2024 · 2 comments
Assignees
Milestone

Comments

@jtlangevin
Copy link
Collaborator

jtlangevin commented Aug 26, 2024

When HVAC and envelope measures are packaged together, efficient-captured energy use results do not specifically breakout the portion of homes/buildings in each year that have envelope and HVAC upgrades deployed together vs. those that are not yet due for the envelope upgrades and have only deployed HVAC improvements – these are all lumped into one whole. However, we need to be able to explicitly track the deployment of HVAC-only vs. HVAC+envelope packages for such measures to allow the appropriate measure/hourly savings shape assignments in the B-SS workflow that disaggregates annual/state results from Scout to the hourly and county-levels.

Proposed approach:

  • Within ecm_prep, for a given envelope/HVAC package measure, track the percentage of total efficient-case energy use for that measure that reflects homes with both HVAC and envelope upgrades deployed.
  • Include new reporting based on this percentage in ecm_prep.json as a complement to efficient-captured reporting variable, efficient-captured-envelope where the latter represents the HVAC energy in efficient-captured that is consumed in homes that have also deployed whatever envelope upgrades are included in the given measure package by the given year. (This variable would only be present for HVAC/envelope packages, and would otherwise not be reported.)
    • 'markets' -> [adopt scenario] -> 'mseg_out_break' -> 'energy' -> 'efficient-captured'
    • 'markets' -> [adopt scenario] -> 'mseg_out_break' -> 'energy' -> 'efficient-captured-envelope'
  • Carry this variable through to relevant reporting from run reporting variables:
    • 'Markets and Savings (by Category)' -> [adopt scenario] -> 'Efficient Energy Use, Measure (MMBtu)'
    • 'Markets and Savings (by Category)' -> [adopt scenario] -> 'Efficient Energy Use, Measure-Envelope (MMBtu)'
@mcpigman
Copy link

So we're assuming that if you do the envelope upgrade you also replace the equipment? I think it's a reasonable assumption but just want to make sure I'm understanding correctly.

@jtlangevin
Copy link
Collaborator Author

jtlangevin commented Sep 6, 2024

We represent the two in a decoupled way - envelope upgrades occur on their own cycle, as do HVAC equipment upgrades. But in the packaging we map the former's energy use impacts to the latter's adoption, such that HVAC equipment stock is the anchor and adopted either with or without a parallel envelope measure simultaneously in place.

jtlangevin added a commit that referenced this issue Oct 25, 2024
Follows approach suggested in issue #413.
jtlangevin added a commit that referenced this issue Oct 28, 2024
Follows approach suggested in issue #413.
jtlangevin added a commit that referenced this issue Oct 28, 2024
Follows approach suggested in issue #413.
jtlangevin added a commit that referenced this issue Nov 14, 2024
Follows approach suggested in issue #413.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants