<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:x="urn:schemas-microsoft-com:office:excel" 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=iso-8859-9">
<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:Consolas;
panose-1:2 11 6 9 2 2 4 3 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:12.0pt;
font-family:"Times New Roman","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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
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-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";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
.MsoChpDefault
{mso-style-type:export-only;}
@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=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>It’s
my feeling that it is within reason to make the assumption that hourly heat
transfer between conditioned floors is not necessary to model to achieve an
acceptable level of accuracy, in most cases. <o:p></o:p></span></p>
<p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Building
on this assumption, I <u>generally</u> select “no exterior exposure”
adiabatic roof and floor constructions for custom "per-floor" shells
with a shell immediately above or below. Adiabatic surfaces retain the
inter-floor thermal mass properties (they store heat on an hourly basis without
transferring heat to/from the associated plenum/space) while slashing the required
model inputs quite a bit.<o:p></o:p></span></p>
<p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>The
only times I would do otherwise are if:<o:p></o:p></span></p>
<p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>-
a space or level is unconditioned or will be conditioned to very different
setpoints (invalidating the above assumption) - in this case I might model
adiabatically initially but would edit/assign to be a properly-associated internal
partition in detailed edit, for those spaces only.<o:p></o:p></span></p>
<p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>-
a shell of a multi-story building has a mixture of exterior roof surfaces and
internal floor constructions on the same plane, in which case I will specify the
roof construction for the whole shell, then delete the "sandwiched"
roof surfaces between the floors in detailed edit.<o:p></o:p></span></p>
<p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Keep
in mind: You should not feel unequivocally 'forced' to create separate shells for
each differently zoned floor. While I also do this most of the time, we should
keep in mind that a repeating floor pattern (using a multi-story shell) is potentially
a MAJOR time saver and can justified from an accuracy standpoint in many cases:
Not every energy model is created with the intent to accurately model
historical consumptions to a tight degree, and if the end-goal is to inform the
design process and/or achieve LEED credits (90.1 models), a reasonably
"averaged" floor zoning pattern is fine where that can be achieved. The
90.1-2007 User's manual encourages such geometrical simplification and floor
multipliers where it makes sense, and gives guidelines for judiciously translating
HVAC zones into larger, combined thermal blocks.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><br>
~Nick<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><img width=119 height=37 id="Picture_x0020_1"
src="cid:image001.jpg@01CBC207.2071A730" alt="cid:489575314@22072009-0ABB"></span><b><span
style='font-size:11.0pt;font-family:"Stylus BT","sans-serif";color:#2D4D5E'><o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Stylus BT","sans-serif";
color:#2D4D5E'><o:p> </o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Stylus BT","sans-serif";
color:#2D4D5E'>NICK CATON, E.I.T.</span></b><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'><o:p></o:p></span></b></p>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Calibri","sans-serif";
color:#CC9900'>PROJECT ENGINEER<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>Smith & Boucher Engineers</span><span style='font-size:7.5pt;
color:#CC9900'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>25501 west valley parkway<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>olathe ks 66061<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>direct 913 344.0036<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>fax 913 345.0617<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
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;font-family:"Calibri","sans-serif";color:blue'> </span></u><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<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"'> equest-users-bounces@lists.onebuilding.org
[mailto:equest-users-bounces@lists.onebuilding.org] <b>On Behalf Of </b>Karen
Walkerman<br>
<b>Sent:</b> Tuesday, February 01, 2011 11:26 AM<br>
<b>To:</b> Rob Hudson<br>
<b>Cc:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> Re: [Equest-users] Modelling Floors with Different
InteriorConfigurations<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>I think what Rob meant is "adiabatic", which means
that there is no heat transfer across the surface. This is usually an
acceptable option for buildings where each space is maintained at the same, or
similar temperatures.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>--<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Karen<o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>2011/2/1 Rob Hudson <<a href="mailto:rdh4176@gmail.com">rdh4176@gmail.com</a>><o:p></o:p></p>
<p class=MsoNormal>There is an option when assigning your roof construction in
the wizard to make the space be below a conditioned space, and therefore ambient.
I have used this option before and it works beautifully. if you
need more information or a screenshot of what i am talking about let me know.<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>Rob<o:p></o:p></p>
<div>
<p class=MsoNormal>2011/2/1 Ömer Moltay <<a
href="mailto:omoltay@mimtarch.com" target="_blank">omoltay@mimtarch.com</a>><o:p></o:p></p>
<div>
<div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Dear All,<br>
<br>
We are encountering this problem all too often and would like to know if
anybody has a satisfactory solution. For example, in a two storey building, the
interior space configurations in each floor are considerably different, forcing
us to create two separate shells that sit on top of each other in eQuest
schematic wizard. However, when this is the case, eQuest treats each shell as a
separate building and place exterior surfaces (ie. Roofs) between floors
(instead of ceilings). The times it takes to manually convert these into
interior surfaces with the right intra-space relationships is way out of
reasonable limits.<br>
<br>
Is there a way to create a shell with floors that each have different interior
layouts (even different exterior footprints for that matter)?<br>
<br>
Thanks,<br>
<br>
Omer Moltay, LEED AP<br>
Mimta Ltd.<br>
<br>
<br>
-----<br>
Bu iletide virüs bulunmadı.<br>
AVG tarafından kontrol edildi - <a href="http://www.avg.com" target="_blank">www.avg.com</a><br>
Sürüm: 10.0.1204 / Virüs Veritabanı: 1435/3416 - Sürüm Tarihi: 01.02.2011<br>
<br>
_______________________________________________<br>
Equest-users mailing list<br>
<a href="http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org"
target="_blank">http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org</a><br>
To unsubscribe from this mailing list send a blank message to <a
href="mailto:EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG" target="_blank">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
<p class=MsoNormal><br>
<br clear=all>
<br>
-- <br>
Rob Hudson<o:p></o:p></p>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
_______________________________________________<br>
Equest-users mailing list<br>
<a href="http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org"
target="_blank">http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org</a><br>
To unsubscribe from this mailing list send a blank message to <a
href="mailto:EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</a><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>