<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:"MS Mincho";
        panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"Stylus BT";
        panose-1:2 14 4 2 2 2 6 2 3 4;}
@font-face
        {font-family:"\@MS Mincho";
        panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.EmailStyle17
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='color:#1F497D'>Katherine,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>There was a very lengthy
discussion this week (perhaps misleading entitled “easy question”)
on this topic which I think will completely answer your question if you’ll
plug through it. I’ve copied it below as it’s not yet in the
archives ;).<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>I personally choose to always
use the actual window layout in both models as a matter of time-efficiency (you
have to plug it in once anyway), provided the overall glazing percentage is less
than 40%.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Without taking any sides, I’ll
share my general perspective – disregard it if you wish: In my
experience, time invested in more accurately modeling system/envelope behaviors
generally tends to yield better baseline performances. Taking the alternative
approach of exploiting the more hazily written passages of 90.1 to yield
similar performance improvements may be harder to justify later on.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>~Nick<o:p></o:p></span></p>
<div>
<p class=MsoNormal><span style='color:#1F497D'><img width=119 height=37
id="Picture_x0020_1" src="cid:image001.jpg@01CADD59.524DAAD0"
alt="cid:489575314@22072009-0ABB"></span><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'><o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'><o:p> </o:p></span></b></p>
<p class=MsoNormal><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'>NICK CATON, E.I.T.</span></b><b><span style='font-size:12.0pt;
font-family:"Stylus BT","sans-serif";color:#2D4D5E'><o:p></o:p></span></b></p>
<p class=MsoNormal><span style='font-size:7.5pt;color:#CC9900'>PROJECT ENGINEER</span><span
style='font-size:7.5pt;font-family:"Times New Roman","serif";color:#CC9900'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>25501 west
valley parkway<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>olathe ks 66061<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>direct 913
344.0036<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>fax 913
345.0617<o:p></o:p></span></p>
<p class=MsoNormal><i><span style='font-size:10.0pt;color:#2D4D5E'>Check out
our new web-site @ </span></i><span style='color:#1F497D'><a
href="www.smithboucher.com" title="blocked::www.smithboucher.com"><span
style='font-size:10.0pt'>www.smithboucher.com</span></a></span><u><span
style='font-size:10.0pt;color:blue'> </span></u><span style='color:#1F497D'><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
bldg-sim-bounces@lists.onebuilding.org
[mailto:bldg-sim-bounces@lists.onebuilding.org] <b>On Behalf Of </b>Katherine
Louman-Gardiner<br>
<b>Sent:</b> Friday, April 16, 2010 11:27 AM<br>
<b>To:</b> bldg-sim@lists.onebuilding.org<br>
<b>Subject:</b> [Bldg-sim] eQuest - ASHRAE Window Standars<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span lang=EN-CA>Hi<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-CA>I’m in the process of building an
eQuest model to compare to an AHRAE one. <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-CA>According to the ASHRAE guidelines, windows
must be distributed evenly along each of the four sides of the building.
Our building is a complex structure, with very different heating zones.
(We have a large garage that will not be heated/cooled to the same
temperature as the adjacent office space).<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-CA>It seems like we will gain an advantage
when comparing our proposed design to the ASHRAE one, by putting windows in an
area that won’t be heated as much. Has anyone encountered a similar
situation? How did you deal with it?<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-CA>Thank you,<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Katherine
Louman-Gardiner</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Mechanical
Engineer in Training</span><o:p></o:p></p>
<p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p>
</div>
</body>
</html>