<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=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
/* 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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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:107314919;
mso-list-type:hybrid;
mso-list-template-ids:926162892 -1118504172 67698703 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;
mso-fareast-font-family:"Yu Gothic";
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1
{mso-list-id:2115637786;
mso-list-type:hybrid;
mso-list-template-ids:1543414330 -1118504172 -1118504172 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;
mso-fareast-font-family:"Yu Gothic";
mso-bidi-font-family:"Times New Roman";}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;
mso-fareast-font-family:"Yu Gothic";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hi Daric,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I do not know of any special output reports which divide the loads or capacities for spaces/zones/systems involving multipliers, but everything else you’ve written has my head nodding as expected behavior. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Speaking to “this feels screwy” (and bravo, by the way! I think as a rule most energy modelers don’t talk about their feelings nearly as much as they should):<o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">The nuances for working with multipliers are not always straightforward, but intelligently interpreting/dividing the resulting energy draws should feel comfortable as an approach,
for the model-builder at a minimum.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">If it helps, consider a thought exercise going in the reverse direction: What if
<u>you</u> modeled …<o:p></o:p></li></ul>
<ul style="margin-top:0in" type="disc">
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level2 lfo2">A single-zone gym to your most stringent personal standards, and
<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level2 lfo2">This gym has a single auto-sized AHU, and<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level2 lfo2">We then wanted to answer question: How big does this single system need to be if we want it to double the size of the gym for a planned future expansion. You’re to utilize the current
model, we’ll assert <u>everything</u> will be identical to the first gym, and we’ll ignore the fact that there are probably real-world advantages to having 2 systems and duplicating the original design.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level2 lfo2">Would you feel compelled to create an entirely separate copy of everything within your model (spaces, surfaces, zones, systems…), then assign to a common meter and add everything up
to determine the new single system size… or could you also feel equally/more comfortable spending less time by leveraging a multiplier-based approach?<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level2 lfo2">There isn’t a “right” answer (you can arrive at the same result either way), but hopefully this helps to illustrate the usefulness and comfort level we should be able to assign to
the technique.<o:p></o:p></li></ul>
</ul>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Acknowledging: It CAN seem screwy to other parties who you may not have the time/resources/patience to educate on the matter. I empathize.
<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Acknowledging: I’ve completed a couple projects (2 to memory) under LEED involving multipliers in the final proposed and baseline case. With that experience, I would avoid it if
at all possible – there’s just too much of a rats nest that develops in correctly and clearly determining/documenting baseline system inputs.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">If you need the final product to have no multipliers in sight, consider that it’s very possible (with some time investment – this is a process) to develop a model WITH multipliers
up to the last possible point (before building final documentation / prescriptive stuff, or before you need a pretty 3D picture for a report or something), then converting back to NO multipliers in detailed mode. Here’s a step-through:<o:p></o:p></li></ul>
<p class="MsoNormal"><b><u><o:p><span style="text-decoration:none"> </span></o:p></u></b></p>
<p class="MsoNormal"><b><u>HOW TO SPLIT UP A SHELL WITH MULTIPLIERS<o:p></o:p></u></b></p>
<ul style="margin-top:0in" type="disc">
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1">Save a separate copy – you can always start over or roll back!<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1"><u>Create new floors/shells:<o:p></o:p></u>
<ul style="margin-top:0in" type="square">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level3 lfo1">Switch the multiplier at the floor input back to 1<o:p></o:p></li></ul>
</li></ol>
</ul>
<p class="MsoNormal" style="margin-left:2.0in"><img width="616" height="288" style="width:6.4166in;height:3.0in" id="Picture_x0020_6" src="cid:image006.png@01D41916.DE56C370"><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<ol style="margin-top:0in" start="2" type="1">
<ul style="margin-top:0in" type="square">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level3 lfo1">Set a user-default for window specification type to ‘Composite’<o:p></o:p></li></ul>
</ol>
</ul>
<p class="MsoNormal" style="margin-left:2.0in"><img width="751" height="360" style="width:7.8229in;height:3.75in" id="Picture_x0020_8" src="cid:image003.png@01D41917.345317B0"><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<ol style="margin-top:0in" start="2" type="1">
<ul style="margin-top:0in" type="square">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level3 lfo1">Duplicate the entire floor and all of its components from the interface by right-clicking the floor in the component tree. Tick only the first box. Linking vs. copying will retain
some of the benefits of multipliers, in keeping your input file much lighter in geometry-related inputs to load. For sanity I like to advise always linking from the same original component – don’t link from other linked copies. :<o:p></o:p></li></ul>
</ol>
</ul>
<p class="MsoNormal" style="margin-left:2.0in"><img width="586" height="275" style="width:6.1041in;height:2.8645in" id="Picture_x0020_9" src="cid:image005.png@01D41917.345317B0"><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<ol style="margin-top:0in" start="2" type="1">
<ul style="margin-top:0in" type="square">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level3 lfo1">Click OK in the following prompt listing the new stuff without renaming anything<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level3 lfo1">Take note of the Space number range corresponding to this floor on a notepad – you’ll need this shortly. In this example, I’d note Floor 4 = new Spaces 19 through 24:<o:p></o:p></li></ul>
</ol>
</ul>
<p class="MsoNormal" style="margin-left:2.0in"><img width="156" height="140" style="width:1.625in;height:1.4583in" id="Picture_x0020_10" src="cid:image008.png@01D41917.345317B0"><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<ol style="margin-top:0in" start="2" type="1">
<ul style="margin-top:0in" type="square">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level3 lfo1">Adjust the new floor Z-value to get the identical floor OFF the original – this isn’t just for aesthetics, you’re also avoiding self-shading issues with the windows by doing so.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level3 lfo1">Rinse and repeat<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level3 lfo1">Do NOT rename anything at this stage, if you feel so-compelled. Will make the later steps easier.<o:p></o:p></li></ul>
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1">Save: At this stage the model will not simulate, as we need to create new systems/zones and make those associations. I do recommend however making a new save as we’re at another
good “rollback” state if you should encounter any stability problems.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1"><u>Create new Systems/Zones<o:p></o:p></u>
<ul style="margin-top:0in" type="square">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level3 lfo1">In this case I recommend sticking to “Copy” vs Linking. Linking systems/zones has caused me problems more often than not in personal experience, so I err towards avoiding them. Again
note only the first tick box is checked:<o:p></o:p></li></ul>
</li></ol>
</ul>
<p class="MsoListParagraph" style="margin-left:2.0in"><img width="622" height="230" style="width:6.4791in;height:2.3958in" id="Picture_x0020_11" src="cid:image004.png@01D4191A.B23C08F0"><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<ol style="margin-top:0in" start="4" type="1">
<ul style="margin-top:0in" type="square">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level3 lfo1">Click OK in the following prompt listing the new stuff without renaming anything<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level3 lfo1">You’ll immediately be prompted to assign a SPACE to each new ZONE. The dropdown will contain an abbreviated SPACE list containing only SPACEs which have no ZONE assignment. NOT ticking
the second box in the prior steps means that you will have as shown here a “Zone 19” to assign to “Space 19.”
<o:p></o:p></li></ul>
</ol>
</ul>
<p class="MsoListParagraph" style="margin-left:1.5in"><img width="421" height="183" style="width:4.3854in;height:1.9062in" id="Picture_x0020_12" src="cid:image007.png@01D4191D.7E1CCE30"><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<ol style="margin-top:0in" start="4" type="1">
<ul style="margin-top:0in" type="square">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level3 lfo1">After finishing your first instance of this, cross-reference with aid of your “floor contains spaces X through Y” record, and make sure the zones and spaces are correctly sequenced.
If you need to adjust the pattern (because in development you revised the wizard-generated sequence in the INP file), you can map out for future systems what goes to what in sequence (i.e. assign the 2<sup>nd</sup> space to the 1<sup>st</sup> zone, etc.).<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level3 lfo1">It’ll make sense at this stage to name the new HVAC system to something like “Floor 4 AHU”<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level3 lfo1">If applicable (depends on system type), assign a new control zone to the new system that’s actually on the same floor.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level3 lfo1">Rinse and Repeat<o:p></o:p></li></ul>
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1">Simulate to confirm everything is running. Pat yourself on the back.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1">If you must, now would be the time to rename everything… poor unfortunate soul!<o:p></o:p></li></ol>
</ul>
<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>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#3A7A46"><img width="726" height="9" style="width:7.5625in;height:.0937in" id="Picture_x0020_1" src="cid:image001.png@01D41911.E5A45E80"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-family:"Arial",sans-serif;color:#3A7A46">Nick Caton, P.E., BEMP</span></b><span style="color:#3A7A46"><o:p></o:p></span></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="724" style="width:543.0pt;border-collapse:collapse">
<tbody>
<tr>
<td width="230" valign="top" style="width:172.3pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#626469"> Senior Energy Engineer</span><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#1F497D"><br>
</span><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#626469"> Regional Energy Engineering Manager<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#626469"> Energy and Sustainability Services</span><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#1F497D"><br>
</span><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#626469"> Schneider Electric</span><span style="color:#1F497D"><o:p></o:p></span></p>
</td>
<td width="291" valign="top" style="width:218.3pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#57B069">D </span><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#626469">913.564.6361
</span><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#1F497D"><br>
</span><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#57B069">M </span><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#626469">785.410.3317
</span><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#1F497D"><br>
</span><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#57B069">F </span><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#626469">913.564.6380</span><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#1F497D"><br>
</span><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#57B069">E </span><span style="color:#1F497D"><a href="mailto:nicholas.caton@schneider-electric.com"><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#626469">nicholas.caton@schneider-electric.com</span></a><o:p></o:p></span></p>
</td>
<td width="203" valign="top" style="width:152.4pt;padding:0in 0in 0in 0in">
<p class="MsoNormal" align="right" style="text-align:right"><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#626469">15200 Santa Fe Trail Drive<br>
Suite 204<br>
Lenexa, KS 66219<br>
United States</span><span style="color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr style="height:4.0pt">
<td width="724" colspan="3" valign="top" style="width:543.0pt;padding:0in 0in 0in 0in;height:4.0pt">
<p class="MsoNormal" style="mso-line-height-alt:4.0pt"><span style="color:#3A7A46"><img border="0" width="722" height="49" style="width:7.5208in;height:.5104in" id="_x0000_i1038" src="cid:image002.png@01D41911.E5A45E80"><!--[if gte mso 9]><xml>
<o:OLEObject Type="Embed" ProgID="PBrush" ShapeID="_x0000_i1038" DrawAspect="Content" ObjectID="_1592824950">
</o:OLEObject>
</xml><![endif]--><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Equest-users [mailto:equest-users-bounces@lists.onebuilding.org]
<b>On Behalf Of </b>Daric Adair via Equest-users<br>
<b>Sent:</b> Wednesday, July 11, 2018 9:12 AM<br>
<b>To:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> [Equest-users] eQuest Floor Multipliers & HVAC System(s)<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">All;<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Have a multistory building, hoping to use floor multipliers, but running into a issues understanding the HVAC simulation. For a 10 story building, with floor multipliers, I get a ground/bottom floor, top floor, and 8 middle floors. All
good. With “system per floor” HVAC design I am getting 3 systems – bottom, top and a middle one that is far bigger than the other two.<o:p></o:p></p>
<p class="MsoNormal">If I disable the multipliers and model all 10 floors, also with system per floor, there are now 10 HVAC systems. The (auto-sized) total CFM, capacity, etc. are
<i>roughly,</i> but not exactly, the same for the full building with the multipliers.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So, this leads me to believe that with multipliers eQuest is simulating 3 HVAC systems; without multipliers it is simulating 10. Can anyone validate?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I understand that the middle 8 floors will ideally have the same loads (no outside shading or other factors – ideal exercise here); and thus that the single large system is roughly the same as the 8 individual systems totaled. But explaining
this to the untrained (and potentially stubborn…) leaves me wanting confirmation. Is there a detailed report that reports what a single middle floor HVAC system would need CFM/capacity wise? (SV-A for a single middle floor)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Which leads to a second question. If modeling Proposed/real systems with multipliers, should the air flow, capacity, etc of those to be summed before input to eQuest? This just ‘feels’ screwy.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks in advance.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal" style="background:white"><b><span style="font-family:"Arial",sans-serif;color:#383A35;text-transform:uppercase">DARIC R ADAIR</span></b><span style="font-size:7.0pt;font-family:"Arial",sans-serif;color:#383A35;text-transform:uppercase"> PE,
CEM, BEMP </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#383A35"><br>
Mechanical Engineer, Energy Analyst <br>
<br>
</span><b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#008C15;text-transform:uppercase">Henderson Engineers</span></b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#383A35"><br>
8345 Lenexa Drive, Suite 300 | Lenexa, KS 66214<br>
<b><span style="text-transform:uppercase">Tel</span></b> (913) 742-5530 <br>
<a href="mailto:daric.adair@hendersonengineers.com"><span style="color:#383A35">daric.adair@hendersonengineers.com</span></a><br>
<br>
<a href="http://www.hendersonengineers.com/"><span style="font-size:8.0pt;color:#008C15;text-transform:uppercase">hendersonengineers.com</span></a><br>
<br>
</span><b><span style="font-size:7.0pt;font-family:"Arial",sans-serif;color:#383A35;text-transform:uppercase">Licensed in</span></b><span style="font-size:7.0pt;font-family:"Arial",sans-serif;color:#383A35;text-transform:uppercase"> KS</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#383A35"><br>
<br>
</span><b><span style="font-size:7.0pt;font-family:"Arial",sans-serif;color:#383A35;text-transform:uppercase">Sending me large files? Please use
<a href="https://apps.hendersonengineers.com/FileShare/Upload?to=daric.adair@hendersonengineers.com">
<span style="color:#008C15">Henderson File Share</span></a> | TX ID #F-001236</span></b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#383A35"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray"><br>
This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. This communication represents the originator's personal views and opinions, which do not necessarily reflect
those of Henderson Engineers, Inc. If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing,
or copying of this email is strictly prohibited. If you received this email in error, please immediately notify
<a href="mailto:administrator@hendersonengineers.com">administrator@hendersonengineers.com</a>.<br>
</span><br>
______________________________________________________________________<br>
This email has been scanned by the Symantec Email Security.cloud service.<br>
______________________________________________________________________<o:p></o:p></p>
</div>
</body>
</html>