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

Use HPXML Zones in energy modeling #1715

Open
shorowit opened this issue May 16, 2024 · 0 comments
Open

Use HPXML Zones in energy modeling #1715

shorowit opened this issue May 16, 2024 · 0 comments
Labels
enhancement New feature or request priority low

Comments

@shorowit
Copy link
Contributor

shorowit commented May 16, 2024

Residential software tools generally describe buildings in two ways:

  1. Some describe the fraction of the building's heating/cooling load served by individual HVAC systems (which may be approximated by the fraction of conditioned floor area served or the fraction of total HVAC capacity)
  2. Some describe zones in a building, each of which is served by a single (?) HVAC system

Now that we support HPXML zones & spaces for design load (HVAC sizing) calculations, we could consider also using them in the energy model, in which case the heating/cooling fractions would not be used. While handling surfaces would be reasonably straightforward, other aspects (e.g., infiltration, ventilation, internal gains, etc.) would be more involved.

Note: If we did this, we would not revert to allowing an HVAC system to serve multiple conditioned zones (e.g., above-grade and below-grade zones, both served by a furnace), we moved away from that for good reasons. An HVAC system would only serve a single conditioned zone.

@shorowit shorowit added the enhancement New feature or request label May 16, 2024
@shorowit shorowit moved this from Triage to Backlog in OpenStudio-HPXML May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority low
Projects
Status: Backlog
Development

No branches or pull requests

1 participant