<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: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: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:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Futura Md BT";}
@font-face
{font-family:"Futura Lt BT";}
/* 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.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:12.0pt;
font-family:"Times New Roman",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:12.0pt;
font-family:"Times New Roman",serif;}
p.yiv0859404471msonormal0, li.yiv0859404471msonormal0, div.yiv0859404471msonormal0
{mso-style-name:yiv0859404471msonormal0;
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;}
p.yiv0859404471msonormal, li.yiv0859404471msonormal, div.yiv0859404471msonormal
{mso-style-name:yiv0859404471msonormal;
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;}
p.yiv0859404471msochpdefault, li.yiv0859404471msochpdefault, div.yiv0859404471msochpdefault
{mso-style-name:yiv0859404471msochpdefault;
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;}
p.yiv0859404471msonormal1, li.yiv0859404471msonormal1, div.yiv0859404471msonormal1
{mso-style-name:yiv0859404471msonormal1;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.yiv0859404471msonormal01, li.yiv0859404471msonormal01, div.yiv0859404471msonormal01
{mso-style-name:yiv0859404471msonormal01;
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;}
p.yiv0859404471msochpdefault1, li.yiv0859404471msochpdefault1, div.yiv0859404471msochpdefault1
{mso-style-name:yiv0859404471msochpdefault1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Times New Roman",serif;}
span.yiv0859404471msohyperlink
{mso-style-name:yiv0859404471msohyperlink;}
span.yiv0859404471msohyperlinkfollowed
{mso-style-name:yiv0859404471msohyperlinkfollowed;}
span.yiv0859404471emailstyle18
{mso-style-name:yiv0859404471emailstyle18;}
span.yiv0859404471emailstyle19
{mso-style-name:yiv0859404471emailstyle19;}
span.yiv0859404471emailstyle20
{mso-style-name:yiv0859404471emailstyle20;}
span.yiv0859404471emailstyle21
{mso-style-name:yiv0859404471emailstyle21;}
span.yiv0859404471msohyperlink1
{mso-style-name:yiv0859404471msohyperlink1;
color:blue;
text-decoration:underline;}
span.yiv0859404471msohyperlinkfollowed1
{mso-style-name:yiv0859404471msohyperlinkfollowed1;
color:purple;
text-decoration:underline;}
span.yiv0859404471emailstyle181
{mso-style-name:yiv0859404471emailstyle181;
font-family:"Calibri",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
span.yiv0859404471emailstyle191
{mso-style-name:yiv0859404471emailstyle191;
font-family:"Calibri",sans-serif;
color:black;
font-weight:normal;
font-style:normal;}
span.yiv0859404471emailstyle201
{mso-style-name:yiv0859404471emailstyle201;
font-family:"Calibri",sans-serif;
color:black;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.yiv0859404471emailstyle211
{mso-style-name:yiv0859404471emailstyle211;
font-family:"Calibri",sans-serif;
color:black;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle36
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:black;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle37
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle38
{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:1830780849;
mso-list-type:hybrid;
mso-list-template-ids:549205246 1902271690 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{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:level3
{mso-level-number-format:bullet;
mso-level-text:;
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:;
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:;
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:;
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:;
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 bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I commonly explore the incremental savings and costs of layering occupancy sensors alongside DCV. When you are already providing new lighting occupancy sensors, the extra
incremental costs/labor can be attractive because you can cross-coordinate disciplines and consider the sensor hardware/installation labor a sunk cost to perform double-duty between lights and terminal boxes.
<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">DCV (CO2) sensors and “box occupancy sensor” savings, while interrelated, are NOT THE SAME THING! They can be complementary, but are definitely interactive ECM scope (cutting
into each other’s savings potential) so don’t assume the savings of one in isolation adds up with the savings of the other in isolation. If this isn’t intuitive, I’ll try explaining box occ. sensor savings through the rest of this email, but advise googling
the fundamentals behind DCV sensors immediately after reading this (so my contribution doesn’t need to be twice as long)!<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">A differentiated pair of Zonal MIN-FLOW-SCH schedules can easily “push” the terminal boxes from a minimum flow rate fraction determined by design ventilation calculations down
to ZERO(*). A few caveats:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">(*) Think hard about what “ZERO” really means:
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Courier New""><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If you tell a terminal box’s damper actuator to fully close but the central fan upstream is still pushing/pressurizing air behind it… there will be non-zero leakage
around the damper and through the box seams. I think a few percentage points is probably a fair ballpark for new spec-grade equipment (like 5% of design), unless your specification/review happens to lock down on this metric.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Courier New""><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If we’re talking existing/old boxes, short of measurements to prove me otherwise I might assume leakage around 10-15% of design however to cover myself.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Courier New""><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Not every mechanical designer responsible for answering calls re: comfort will permit near-zero flow during regularly occupied hours in their controls sequencing.
Be cognizant this can be an energy vs. comfort pain-point and be sure you’re on the same page with your design team / owner.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Courier New""><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If you’re reading this far and thinking “Nick, I want to shunt off power to my terminal boxes entirely!” … bear with me and stick around for my thoughts regarding
hotel rooms.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Allowing the boxes to drop way down without also providing a setback temperature during those periods may not look so attractive: MIN-FLOW-SCH only permits lower
minimums, not maximum flows. If your controls specification/installation is up to snuff, you’ll want to also specify a new set of zonal thermostat schedules (HEAT-TEMP-SCH, COOL-TEMP-SCH) alongside the new zonal MIN-FLOW-SCH to pull back the conditioning
needs during the same unoccupied hours.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Consider potential for “warmup/drift” comfort issues during generally occupied hours. I make a point for terminal occ sensors to not set back temperatures quite
as aggressively during normal occupancy hours as would be appropriate overnight.<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">A very analogous but instructively distinct situation is hotel rooms, where you see local hotel room HV&C shut entirely off during untenanted periods. Similar core concepts,
similar technical approach. Major difference is that you will sometimes see the unitary equipment entirely shut off instead of set back, making the rooms literally unconditioned/unventilated when not in occupancy. Great for energy and reducing operating
costs, but can make for musty/off-smells during hotel stays – I’d think <u>really</u> hard about applying that approach in other commercial building occupancies where it isn’t already normal/standard practice for the given region.<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">Rounding back to the other half of the original query: how many hours you should model to determine savings, that depends first on the point of your model. I think there
are 2 effective tiers of effort:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If you’re doing LEED or compliance modeling, then it would be
<u>easiest</u> to follow the % reductions prescribed for lighting occupancy sensors, between 10 and 15% depending on project size.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If you’re interested in estimating the “actual” savings (to inform whether this is a wise/responsible recommendation to make for your clients’ dollars), then toss
those prescriptions aside and <i>think</i> about the actual likely human occupancy behavior through the day/evening for the spaces in question.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Courier New""><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The correct % of unoccupied hours could be much higher/lower than 15% on a case by case and building by building basis.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Courier New""><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I’m not advocating a unique set of thermostat/fan schedules per zone, but it isn’t much extra effort to determine and document the answer for the building in-aggregate
to create & apply a uniform set of schedules. <o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Courier New""><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Zones/systems with extremely different usage might benefit from a unique set however.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Courier New""><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Same advice applies to DCV explorations.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in"><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"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">~Nick<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;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@01D29E6B.FE0E3940"><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"> 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="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">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="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><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="_x0000_i1025" src="cid:image002.png@01D29E6B.FE0E3940"><!--[if gte mso 9]><xml>
<o:OLEObject Type="Embed" ProgID="PBrush" ShapeID="_x0000_i1025" DrawAspect="Content" ObjectID="_1551188832">
</o:OLEObject>
</xml><![endif]--><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>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<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>Michael Mantai via Equest-users<br>
<b>Sent:</b> Thursday, March 16, 2017 11:00 AM<br>
<b>To:</b> Manuela Mengue <mmengue@dagherengineering.com>; John Aulbach <jra_sac@yahoo.com>; 'equest-users@lists.onebuilding.org' <equest-users@lists.onebuilding.org><br>
<b>Subject:</b> Re: [Equest-users] HVAC Occupancy Sensors<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I’ve never tried to account for this in a model, although we’ve had several projects connect HVAC to occupancy sensors. I’m wondering if you could adjust the zone min. airflow
setpoint to the lower unoccupied setpoint for 10% of the occupied hours, to kind of match the 10% reduction in LPD per Appendix G. If the zone temperature setpoint is also reset based on the occupancy sensor, it seems like you could also adjust the temperature
setpoint schedules in eQuest to the lower/higher unoccupied settings for 10% of the occupied hours. My guess is this would have negligible effect on energy savings, but maybe not.<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>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:"Calibri",sans-serif;color:black">From:
</span></b><span style="font-family:"Calibri",sans-serif;color:black">Equest-users <<a href="mailto:equest-users-bounces@lists.onebuilding.org">equest-users-bounces@lists.onebuilding.org</a>> on behalf of Manuela Mengue via Equest-users <<a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a>><br>
<b>Reply-To: </b>Manuela Mengue <<a href="mailto:mmengue@dagherengineering.com">mmengue@dagherengineering.com</a>><br>
<b>Date: </b>Thursday, March 16, 2017 at 10:59 AM<br>
<b>To: </b>John Aulbach <<a href="mailto:jra_sac@yahoo.com">jra_sac@yahoo.com</a>>, "'equest-users@lists.onebuilding.org'" <<a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a>><br>
<b>Subject: </b>Re: [Equest-users] HVAC Occupancy Sensors<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">John,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">See Appendix G – Table G3.2 (2) Occupancy sensor for Non-24h and <5000 ft2.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">My question pertained to the HVAC component which achieves additional savings for installing occupancy sensors.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Best regards,</span><o:p></o:p></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Futura Md BT";color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Futura Md BT";color:black">Manuela Mengue</span><o:p></o:p></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Futura Lt BT";color:black">Design Engineer</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><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><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"> John Aulbach [<a href="mailto:jra_sac@yahoo.com">mailto:jra_sac@yahoo.com</a>]
<br>
<b>Sent:</b> Thursday, March 16, 2017 10:38 AM<br>
<b>To:</b> Manuela Mengue <<a href="mailto:mmengue@dagherengineering.com">mmengue@dagherengineering.com</a>>; 'equest-users@lists.onebuilding.org' <<a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a>><br>
<b>Subject:</b> Re: [Equest-users] HVAC Occupancy Sensors</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Verdana",sans-serif">Somewhere, in the mysteries of space, I have always been told to use 15% less lighting for the proposed case for occupancy sensors. I am unsure of the source. ASHRAE ??</span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Verdana",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Verdana",sans-serif">John R. Aulbach, PE</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Verdana",sans-serif"> </span><o:p></o:p></p>
</div>
<div id="yahoo_quoted_0322054808">
<div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Verdana",sans-serif">On Thursday, March 16, 2017, 6:02:34 AM PDT, Manuela Mengue via Equest-users <</span><a href="mailto:equest-users@lists.onebuilding.org"><span style="font-size:13.5pt;font-family:"Verdana",sans-serif">equest-users@lists.onebuilding.org</span></a><span style="font-size:13.5pt;font-family:"Verdana",sans-serif">>
wrote:</span><o:p></o:p></p>
</div>
<div>
<div id="yiv0859404471">
<div>
<div>
<p class="yiv0859404471msonormal"><span style="font-size:13.5pt;font-family:"Verdana",sans-serif;color:black">Hi all,</span><o:p></o:p></p>
<p class="yiv0859404471msonormal"><span style="font-size:13.5pt;font-family:"Verdana",sans-serif;color:black"> </span><o:p></o:p></p>
<p class="yiv0859404471msonormal"><span style="font-size:13.5pt;font-family:"Verdana",sans-serif;color:black">Has anyone succeeded to model HVAC occupancy sensors in eQuest? In this project, supply air from AHU units feed into VAV boxes in classrooms. The VAV
boxes modulate airflow in accordance to occupancy sensor readings. The ASHRAE Table G3.2 allows us to take credit for lighting controls, however, I could not find guidance on HVAC occupancy sensors for energy models. My first approach would be to adjust occupancy
levels in Proposed (how?), but this raises another question: doesn’t LEED require to use the same schedules in Proposed and Baseline?</span><o:p></o:p></p>
<p class="yiv0859404471msonormal"><span style="font-size:13.5pt;font-family:"Verdana",sans-serif;color:black"> </span><o:p></o:p></p>
<div>
<p class="yiv0859404471msonormal" style="background:white"><span style="font-size:13.5pt;font-family:"Verdana",sans-serif;color:black">Thanks in advance for your suggestions,</span><o:p></o:p></p>
<p class="yiv0859404471msonormal" style="background:white"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:black"> </span><o:p></o:p></p>
<p class="yiv0859404471msonormal" style="background:white"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:black">Manuela Mengue</span><o:p></o:p></p>
<p class="yiv0859404471msonormal" style="background:white"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:black">Design Engineer</span><o:p></o:p></p>
</div>
<p class="yiv0859404471msonormal"><span style="font-size:13.5pt;font-family:"Verdana",sans-serif"> </span><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Verdana",sans-serif">_______________________________________________<br>
Equest-users mailing list<br>
</span><a href="http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org" target="_blank"><span style="font-size:13.5pt;font-family:"Verdana",sans-serif">http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org</span></a><span style="font-size:13.5pt;font-family:"Verdana",sans-serif"><br>
To unsubscribe from this mailing list send a blank message to </span><a href="mailto:EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG"><span style="font-size:13.5pt;font-family:"Verdana",sans-serif">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</span></a><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal">_______________________________________________ Equest-users mailing list
<a href="http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org">
http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org</a> 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>
<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>