<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:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" 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=utf-8">
<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:"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:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",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.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:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The
<i>simplest </i>approach (in the interest of your own time) may be to define for the cafeteria/gym a “combined” system schedule that ensures the operating hours and ventilation delivery is satisfied for both areas.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Otherwise, I think you
<b><u>should</u></b> be able to safely interpret G3.1.1.b exceptions when the occupancy/process loads/schedules differ significantly from the rest of
<b><u>the same floor</u></b>. That isn’t the exact wording in 90.1, but if I were your reviewer I think this fits the spirit / intent for such exceptions. Worst case scenario is your reviewer disagrees, and you’re later pushed into the first suggestion to
combine those cases, resulting in a larger baseline system with broadly worse unitary efficiencies, helping your performance rating if anything.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">~Nick<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#3A7A46"><img width="722" height="9" style="width:7.5208in;height:.0937in" id="Picture_x0020_1" src="cid:image001.png@01D2579E.120B85C0"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#3A7A46">Nick Caton, P.E., BEMP</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;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"> 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="font-size:11.0pt;font-family:"Calibri",sans-serif;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">E </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;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></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:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><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="font-size:11.0pt;font-family:"Calibri",sans-serif;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="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#3A7A46"><img border="0" width="722" height="49" style="width:7.5208in;height:.5104in" id="Picture_x0020_3" src="cid:image002.png@01D2579E.120B85C0" alt="cid:image001.png@01D189AB.58634A10"></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#3A7A46"><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Equest-users [mailto:equest-users-bounces@lists.onebuilding.org]
<b>On Behalf Of </b>Beran Gurtekin Celik via Equest-users<br>
<b>Sent:</b> Friday, December 16, 2016 10:54 AM<br>
<b>To:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> [Equest-users] ASHRAE 90.1 baseline HVAC system interpretation<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Hi all,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I am puzzled with the interpretation of Ashrae 90.1-2007 G3.1.1 where is says each floor shall be modeled with a separate HVAC system.
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">My proposed building is a 4 story office building with 3 floors office and a first floor consisted of cafeteria, kitchen and gym. Office floors have one system per floor and the first floor has three systems for each specific area. My baseline
is using system 6 for the typical office floors. I am trying to interpret the G3.1.1 for the first floor. If I combine all those areas into one system their occupancy schedules, HVAC schedules, OA rates etc are all different and if I use one system, the schedules
will not match the proposed. The kitchen qualifies for exception b due to thermal loads, so I will use a single zone system for that area. I am wondering how I should approach the gym and cafeteria. Can I use two systems in the baseline for those areas? They
do not fall into exception b since their schedules and loads do not differ significantly from other spaces (office spaces) but they do differ from each other and using one system for those two different usage areas brings the dilemma of using a different schedule
from the proposed building. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Any insights will be greatly appreciated.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Beran<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"><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>
</div>
</div>
</div>
<p class="MsoNormal"><br>
______________________________________________________________________<br>
This email has been scanned by the Symantec Email Security.cloud service.<br>
______________________________________________________________________<o:p></o:p></p>
</div>
</body>
</html>