[Equest-users] In case of not knowing building orientation, how we get a relatively accurate total energy consumption?

Nicholas Caton ncaton at catonenergy.com
Sun Dec 13 19:39:06 PST 2015


Assuming orientation is truly ‘unknowable:’



For some building designs, orientation does not play a meaningful role
using metrics like total annual energy costs/consumption. For other
building designs, it is a bigger deal.  I would advise you to first perform
a “sensitivity analysis” by comparing the results of a variety of
orientation possibilities (after the rest of your model development is
complete).



Then, when you present your results you could for example present the
lowest result and inform: “actual energy consumption may rise up to XX% if
building orientation is not optimized.”



~Nick



*NICK CATON, P.E.*
*Owner*



*Caton Energy Consulting*
  306 N Ferrel

  Olathe, KS  66061

  office:  785.410.3317

www.catonenergy.com



*From:* Equest-users [mailto:equest-users-bounces at lists.onebuilding.org] *On
Behalf Of *Qi Jin
*Sent:* Sunday, December 13, 2015 7:40 PM
*To:* equest-users at lists.onebuilding.org
*Subject:* [Equest-users] In case of not knowing building orientation, how
we get a relatively accurate total energy consumption?



Hello Dear All,

I have a question about building orientation in eQUEST model. I don't know
building orientation and set the azimuth to be 0 as the baseline model.



The question is *in case of we don't know building orientation, how do we
get a relatively accurate total energy consumption?*



I found that someone simulated energy modeling under four building
orientations, including 0, 90, 180, and 270. Energy consumption of four
cases were averaged which was considered as the actual energy consumption.



Can anyone give me some ideas about this issue? Your help would be greatly
appreciated!



Thanks,

Frank
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20151213/898641ac/attachment-0002.htm>


More information about the Equest-users mailing list