<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;
        mso-fareast-language:EN-US;}
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
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0cm;
        margin-right:0cm;
        margin-bottom:0cm;
        margin-left:36.0pt;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;
        mso-fareast-language:EN-US;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
span.EmailStyle19
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
span.EmailStyle20
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
span.EmailStyle22
        {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:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
/* List Definitions */
@list l0
        {mso-list-id:948464804;
        mso-list-type:hybrid;
        mso-list-template-ids:2020135836 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level2
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level3
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l0:level4
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level5
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level6
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l0:level7
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level8
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level9
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l1
        {mso-list-id:1041442948;
        mso-list-template-ids:675706582;}
ol
        {margin-bottom:0cm;}
ul
        {margin-bottom:0cm;}
--></style></head><body lang="EN-GB" link="#0563C1" vlink="#954F72"><div class="WordSection1"><p class="MsoNormal"><span style="color:#1f497d">Hi Nicholas,</span></p><p class="MsoNormal"><span style="color:#1f497d"> </span></p><p class="MsoNormal"><span style="color:#1f497d">Thanks much for your valuable response! I will be looking into your possible solutions, however I tried point #3 myself before just to check the possibilities and have found that it  could be problematic, especially if you have multiple other systems also to be added to the same zone. It’s a tedious task. </span></p><p class="MsoNormal"><span style="color:#1f497d"> </span></p><p class="MsoNormal"><span style="color:#1f497d">Regards,</span></p><p class="MsoNormal"><span style="color:#1f497d"> </span></p><p class="MsoNormal"><span style="color:#1f497d">Tanya</span></p><p class="MsoNormal"><span style="color:#1f497d"> </span></p><div><div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal"><b><span lang="EN-US" style="mso-fareast-language:EN-GB">From:</span></b><span lang="EN-US" style="mso-fareast-language:EN-GB"> Nicholas Caton [mailto:<a href="mailto:Nicholas.Caton@se.com">Nicholas.Caton@se.com</a>] <br><b>Sent:</b> 07 July 2020 16:49<br><b>To:</b> Tanya Soji <<a href="mailto:tanya.soji@quantumesco.com">tanya.soji@quantumesco.com</a>><br><b>Cc:</b> <a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a><br><b>Subject:</b> RE: [Equest-users] Assign 2 systems to the same zone</span></p></div></div><p class="MsoNormal"> </p><p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA">Hi Tanya!</span></p><p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA"> </span></p><p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA">There is a long-standing limitation with doe2/eQuest in not permitting more than one system per zone, however in recent years, this rule has been relaxed a bit.</span></p><p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA"> </span></p><p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA">If you treat your AHU as a DOAS system (responsible for delivering ventilation air), then you can have a DOAS + another system technically servicing the same zone.  This does require building your model using the doe2.3 engine.</span></p><p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA"> </span></p><p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA">If a DOAS circumstantially will not work however, and you wish to model 2 or more systems servicing the same zone, there remains a couple long-standing “workarounds” I’ve seen promoted in this community:</span></p><ol style="margin-top:0cm" start="1" type="1"><li class="MsoNormal" style="mso-list:l0 level1 lfo3"><span lang="EN-US" style="mso-fareast-language:JA">The targeted zone can be split into 2 or more air-wall sharing spaces, geometrically considering where the thermostats for the various systems actually lie and (if skin loads are in play) which system is intended to handle specific space loads. Changing up model geometries is totally possible, but can be a more involved proposition post-wizards.  I recommend newer energy modelers to move back to wizards if they aren’t too far past the line of detailed mode edits.</span></li><li class="MsoNormal" style="mso-list:l0 level1 lfo3"><span lang="EN-US" style="mso-fareast-language:JA">The presence of a second system can sometimes be approximated through cleverly tweaking one system and adding zonal baseboards or zonal heating/cooling coils, if applicable.  This can require sacrificing some degree of capacity for independent system operation, but in some cases is a totally fair representation in terms of model accuracy.</span></li><li class="MsoNormal" style="mso-list:l0 level1 lfo3"><span lang="EN-US" style="mso-fareast-language:JA">I’ve seen a couple cases where the modeler chose to duplicate the associated space/zone, assign its internal loads (like lights/ plug loads) to “ghost” meters (to prevent double counting those energies), then assign a second system to the duplicated zone.  This can be problematic relative to the other options presented, in that you’re missing any opportunity to capture the interactivity between the systems.  In some cases however, you might not want to model interactivity… just consider that one systems’ controlling thermostat may be affected by space heating/conditioning performed “by others.”</span></li></ol><p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA"> </span></p><p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA">I hope this is helpful! </span></p><p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA"> </span></p><p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA">~Nick</span></p><p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA"> </span></p><div><p class="MsoNormal"><span lang="EN-US" style="font-family:"Arial",sans-serif;color:#3a7a46"><img width="624" height="8" id="Picture_x0020_1" src="cid:image001.jpg@01D65858.C502F500"></span></p><p class="MsoNormal"><b><span lang="EN-US" style="font-family:"Arial",sans-serif;color:#3a7a46">Nick Caton, P.E., BEMP</span></b><span lang="EN-US" style="color:#3a7a46"></span></p><table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="0" style="width:543.0pt;border-collapse:collapse"><tr><td width="230" valign="top" style="width:172.3pt;padding:0cm 0cm 0cm 0cm"><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#626469">  Senior Energy Engineer</span></p><p class="MsoNormal" style="text-indent:4.5pt"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#626469">  Energy and Sustainability Services</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#1f497d"><br></span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#626469">  Energy Performance Contracting </span><span style="font-size:9.0pt;color:#1f497d"></span></p></td><td width="16" valign="top" style="width:11.8pt;padding:0cm 0cm 0cm 0cm"><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#57b069">D  </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#1f497d"><br></span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#57b069">M  </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#1f497d"><br></span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#57b069">E  </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#1f497d"><br></span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#57b069">  </span><span style="font-size:9.0pt;color:#1f497d"> </span></p></td><td width="275" valign="top" style="width:206.5pt;padding:0cm 0cm 0cm 0cm"><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#626469">913 . 564 . 6361</span></p><p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#626469">785 . 410 . 3317</span></p><p class="MsoNormal"><u><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#626469"><a href="mailto:nicholas.caton@se.com"><span style="font-family:"Calibri",sans-serif;color:#626469">nicholas.caton@se.com</span></a></span></u><span style="font-size:9.0pt;color:#1f497d"></span></p></td><td width="203" valign="top" style="width:152.4pt;padding:0cm 0cm 0cm 0cm"><p class="MsoNormal" align="right" style="margin-bottom:12.0pt;text-align:right"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#626469">15200 Santa Fe Trail Drive<br>Suite 204<br>Lenexa, KS 66219</span><span style="font-size:9.0pt;color:#1f497d"></span></p></td></tr><tr style="height:4.0pt"><td width="724" colspan="4" valign="top" style="width:543.0pt;padding:0cm 0cm 0cm 0cm;height:4.0pt"><p class="MsoNormal" style="mso-line-height-alt:4.0pt"><span style="color:#3a7a46"><img border="0" width="722" height="49" id="Picture_x0020_2" src="cid:image002.png@01D65858.C502F500"></span></p></td></tr></table><p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA"> </span></p></div><p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:JA"> </span></p><div><div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal"><b><span lang="EN-US" style="mso-fareast-language:JA">From:</span></b><span lang="EN-US" style="mso-fareast-language:JA"> Equest-users <<a href="mailto:equest-users-bounces@lists.onebuilding.org">equest-users-bounces@lists.onebuilding.org</a>> <b>On Behalf Of </b>Tanya Soji via Equest-users<br><b>Sent:</b> Tuesday, July 7, 2020 6:30 AM<br><b>To:</b> <a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a><br><b>Subject:</b> [Equest-users] Assign 2 systems to the same zone</span></p></div></div><p class="MsoNormal"><span lang="EN-US"> </span></p><p><span style="color:red">[External email: Use caution with links and attachments]</span></p><div class="MsoNormal" align="center" style="text-align:center"><span style="mso-fareast-language:JA"><hr size="2" width="100%" align="center"></span></div><p> </p><div><p class="MsoNormal"><span style="color:#002060">Hi everyone, </span></p><p class="MsoNormal"><span style="color:#002060"> </span></p><p class="MsoNormal"><span style="color:#002060">I just wanted a small clarification on the Air-side HVAC systems. </span></p><p class="MsoNormal"><span style="color:#002060"> </span></p><p class="MsoNormal"><span style="color:#002060">How does  eQuest go about assigning two different HVAC systems (AHUs & Package units in my case) to the same zone??</span></p><p class="MsoNormal"><span style="color:#002060"> </span></p><p class="MsoNormal"><span style="color:#002060">It does not let me add the same zones to the second system (Package units). </span></p><p class="MsoNormal"><span style="color:#002060"> </span></p><p class="MsoNormal"><span style="color:#002060">Regards,</span></p><p class="MsoNormal"><span style="color:#002060"> </span></p><p class="MsoNormal"><span style="color:#002060">Tanya </span></p><p class="MsoNormal" style="margin-bottom:12.0pt"><span style="mso-fareast-language:JA"><br>______________________________________________________________________<br>This email has been scanned by the Symantec Email Security.cloud service.<br>______________________________________________________________________</span></p><div><p class="MsoNormal"><span style="mso-fareast-language:JA">This e-mail is from Eurostar Group. is intended solely for the person to whom it has been addressed. It should not be used by anyone else. It may contain confidential and/or legally privileged information. If you are not the intended recipient, you are notified that any use, distribution, transmission, printing, copying, dissemination or any action in reliance on it is strictly prohibited. If you have received this email erroneously, please delete this message and notify the sender.</span></p></div><div><p class="MsoNormal"><span style="mso-fareast-language:JA">The recipient acknowledges that Eurostar Group /subsidiaries/ associated companies, are unable to exercise control or ensure or guarantee the integrity of/over the contents of the information contained in e-mail transmissions and further acknowledges that any views expressed in this message are those of the individual sender and no binding nature of the message shall be implied or assumed unless the sender does so expressly with due authority of Eurostar Group.  If the recipient thinks that any part of this email transgresses any law of the land, he/she I shall immediately alert Eurostar Group, by mailing their specific concern on <a href="mailto:compliance@eurostargroup.com" target="_blank">marketing@eurostargroup.com</a> Needless to reiterate that Consequently,  Eurostar does not take any liability whatsoever, for any such transgressions.</span></p></div></div></div></body></html>

<br>
<div>This e-mail is from Eurostar Group. is intended solely for the person to whom it has been addressed. It should not be used by anyone else. It may contain confidential and/or legally privileged information. If you are not the intended recipient, you are notified that any use, distribution, transmission, printing, copying, dissemination or any action in reliance on it is strictly prohibited. If you have received this email erroneously, please delete this message and notify the sender.</div><div>The recipient acknowledges that Eurostar Group /subsidiaries/ associated companies, are unable to exercise control or ensure or guarantee the integrity of/over the contents of the information contained in e-mail transmissions and further acknowledges that any views expressed in this message are those of the individual sender and no binding nature of the message shall be implied or assumed unless the sender does so expressly with due authority of Eurostar Group.  If the recipient thinks that any part of this email transgresses any law of the land, he/she I shall immediately alert Eurostar Group, by mailing their specific concern on <a href="mailto:compliance@eurostargroup.com" target="_blank">marketing@eurostargroup.com</a> Needless to reiterate that Consequently,  Eurostar does not take any liability whatsoever, for any such transgressions.</div>