<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:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" 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";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1854105544;
mso-list-type:hybrid;
mso-list-template-ids:-284501316 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:1979799056;
mso-list-type:hybrid;
mso-list-template-ids:-1721436140 -42286368 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:"MS Mincho";
mso-bidi-font-family:"Times New Roman";}
@list l1:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="3074" />
</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=WordSection1><p class=MsoNormal><span style='color:#1F497D'>My take on the air partitions is that when the software is calculating the load for each zone it uses the air partition as the boundary for that zone, any heat transferred into or out of that zone through the boundary will come relatively easily from the adjacent zone, depending on the conditions in the adjacent zone. I think it is worth it to test your questions/scenarios, but with that in mind one could assume the following responses could be true.<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'>1. The zones will rapidly transfer energy, but it is finite and the zones should not fight each other to the extent that neither zone is satisfied. (Unless the equipment isn't sized to handle the heat transfer from a hot adjacent zone). The cold zone will steal some energy from the hot zone and the hot zone will lose some energy to the cold zone, based on thermal transfer through the shared air wall.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>2. The air wall is just another avenue for heat transfer between each zone. The System A cooling load should be larger than that of System B.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>3. If System A is not big enough than Zone A will be hotter and transfer more energy to Zone B, which would make Zone B warmer. So maybe next hours iteration would have less energy transferred because the del T is smaller?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>4. The larger space will have a larger air wall than the smaller spaces so it will transfer more energy through the air wall in its own world. You can only select one zone for the "next to" zone, this will keep from complicating the heat transfer calc. <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'>This is just my interpretation.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><b><span style='color:#1F497D'>Joe Fleming<o:p></o:p></span></b></p><p class=MsoNormal><i><span style='font-size:10.0pt;color:#333333'>E.I., LEED AP BD+C, BEMP<o:p></o:p></span></i></p><p class=MsoNormal><i><span style='font-size:10.0pt;color:#333333'>Mechanical Engineer I<o:p></o:p></span></i></p><p class=MsoNormal><span style='font-size:10.0pt;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='color:#006363'>TLC Engineering for Architecture<br></span></b><b><span style='font-size:10.0pt;color:#006363'>Your 2030 Challenge Partner</span></b><b><span style='color:#006363'><o:p></o:p></span></b></p><p class=MsoNormal><span style='font-size:10.0pt;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;color:#1F497D'>800 Fairway Drive, Suite 250<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;color:#1F497D'>Deerfield Beach, FL 33441-1816<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;color:#1F497D'><o:p> </o:p></span></p></div><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0><tr><td valign=bottom style='padding:0in 0in 0in 0in'><p class=MsoNormal align=right style='text-align:right'><span style='font-size:9.0pt;color:#333333'>phone: </span><span style='font-size:9.0pt;color:#555555'><o:p></o:p></span></p></td><td valign=bottom style='padding:0in 0in 0in 0in'><p class=MsoNormal><span style='font-size:10.0pt;color:#1F497D'>954-418-9096</span><span style='font-size:10.0pt;color:#1F497D'><o:p></o:p></span></p></td></tr><tr><td valign=bottom style='padding:0in 0in 0in 0in'><p class=MsoNormal align=right style='text-align:right'><span style='font-size:9.0pt;color:#333333'>fax: </span><span style='font-size:9.0pt;color:#555555'><o:p></o:p></span></p></td><td valign=bottom style='padding:0in 0in 0in 0in'><p class=MsoNormal><span style='font-size:10.0pt;color:#1F497D'>954-418-9296</span><span style='font-size:10.0pt;color:#1F497D'><o:p></o:p></span></p></td></tr><tr><td valign=bottom style='padding:0in 0in 0in 0in'><p class=MsoNormal align=right style='text-align:right'><span style='font-size:9.0pt;color:#333333'>direct: </span><span style='font-size:9.0pt;color:#555555'><o:p></o:p></span></p></td><td valign=bottom style='padding:0in 0in 0in 0in'><p class=MsoNormal><span style='font-size:10.0pt;color:#1F497D'>954-418-4591</span><span style='font-size:10.0pt;color:#1F497D'><o:p></o:p></span></p></td></tr><tr><td valign=bottom style='padding:0in 0in 0in 0in'><p class=MsoNormal align=right style='text-align:right'><span style='font-size:9.0pt;color:#333333'>website: </span><span style='font-size:9.0pt;color:#555555'><o:p></o:p></span></p></td><td valign=bottom style='padding:0in 0in 0in 0in'><p class=MsoNormal><span style='font-size:10.0pt;color:#1F497D'><a href="http://www.tlc-engineers.com">www.tlc-engineers.com</a><o:p></o:p></span></p></td></tr></table><p class=MsoNormal><span style='font-size:10.0pt;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><a href="http://www.tlc-engineers.com/"><span style='text-decoration:none'><img border=0 width=700 height=49 id="_x0000_i1026" src="cid:image002.gif@01CBBD60.58A59DB0" alt="http://www.tlc-engineers.com/images/TLC_Sig_Loc_Block.gif"></span></a><span style='color:#1F497D'><o:p></o:p></span></p><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"'> equest-users-bounces@lists.onebuilding.org [mailto:equest-users-bounces@lists.onebuilding.org] <b>On Behalf Of </b>Nick Caton<br><b>Sent:</b> Wednesday, January 26, 2011 12:49 PM<br><b>To:</b> equest-users@lists.onebuilding.org<br><b>Subject:</b> [Equest-users] What's in an Air Wall?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi everyone,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>A discussion on [bldg-sim] prompted me to bring up a topic that’s been bugging me in the “eQuest fundamentals” department… <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have a general understanding that eQuest does not fundamentally model airflow (specifically, convection of internal loads) between zones.<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>The DOE-2 entry for INT-WALL-TYPE says an internal “air” partition “ …designates a non-physical interior surface with no mass (i.e., an opening between spaces) across which convection can take place.”<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>A wizard-generated “air” internal partition has a construction with U-factor of 2.7… very conductive.<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]> To draw a conclusion – two zones connected with an “air” partition are “connected” thermally. In practice, the internal loads in one are “combined” with the other.<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>This means heat in one zone should travel to the other in a rapid fashion during the hourly simulation, until the space temperatures are identical between the two.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I hope my understanding thus far is correct, because from here I have some questions that dig at what’s going on under the hood:<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo4'><![if !supportLists]><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Imagine an air partition “connects” zones A and B. These zones have separate systems and separate thermostats with different setpoints. If zone A’s thermostat wants to be much warmer than zone B, is it possible the systems will “fight” each other and cause mutual unmet hours?<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo4'><![if !supportLists]><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>In the same setup, if Zone A is identical in geometry to Zone B, but has 2x the internal/external loads, does it follow that the system for System A will handle 2x the internal loads as System B, or are they summed and applied equally to the two systems on an hourly basis? <o:p></o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo4'><![if !supportLists]><span style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Is the “distribution of loads behavior” affected if Systems A & B are specified with different capacities and/or airflows? <o:p></o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo4'><![if !supportLists]><span style='mso-list:Ignore'>4.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>If one space is larger in area/volume than the other, does that affect how the collective loads are distributed to the corresponding systems?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have “exploited” air partition behavior in the past to get around the “one system per zone” rule (need two RTU’s serving that space? Just make an imaginary air wall!). However I want to be sure before I continue this practice or advise others to do the same that there aren’t any major potential pitfalls in how the loads/systems are distributed/affected…<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>~Nick<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><img border=0 width=119 height=37 id="Picture_x0020_1" src="cid:image003.jpg@01CBBD60.58A59DB0" alt="cid:489575314@22072009-0ABB"><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<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>Smith & Boucher Engineers</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><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><p class=MsoNormal><o:p> </o:p></p></div></body></html>