<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=iso-8859-1">
<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;}
/* 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:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{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:2060475161;
mso-list-type:hybrid;
mso-list-template-ids:-614815016 -329345518 67698691 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:Calibri;
mso-bidi-font-family:Calibri;}
@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:\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;}
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 Kumar,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Responses below <span style="color:red">in red and tagged with [NC] for those who aren’t seeing this with formatting</span>.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There’s some broader/overarching advice in the final paragraphs you might want to read first.<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>
<div>
<p class="MsoNormal"><span style="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@01D22B78.1A765C00"><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"> 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">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></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="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="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="Picture_x0020_3" src="cid:image002.png@01D22B78.1A765C00" alt="cid:image001.png@01D189AB.58634A10"></span><span style="color:#3A7A46"><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>Saurabh Kumar Srivastava via Equest-users<br>
<b>Sent:</b> Thursday, October 20, 2016 10:41 PM<br>
<b>To:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> [Equest-users] Removing Unmet Hours?<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Hey Guys!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">I was just removing the Unmet hours from my Proposed and Baseline Models and have encountered a few questions.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">It would be really nice if you could let me know the correct approach!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><u><span lang="EN-GB">Proposed Case<o:p></o:p></span></u></b></p>
<p class="MsoNormal"><span lang="EN-GB">- As the Proposed building has District Heating (hot water via Steam Meter) there are a lot of Unmet hours (approx. 5000)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:red">[NC] </span><span lang="EN-GB" style="color:red">Caution: This doesn’t make sense as a causality without further context. District steam should be capable of heating a building to comfort.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:red">Also observing: a magnitude of 5000 unmet hours (presumably all heating and coincident hours, by context) suggests you aren’t delivering ANY heat through a full season, or perhaps your thermostats are
asking for something unrealistic.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:red"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">- To design the radiators I've use Baseboard heating with Control as Thermostatic.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:red">[NC] </span><span lang="EN-GB" style="color:red">OK. I’d confirm in SV reports that you’re getting reasonable capacities if you aren’t already specifying – I’ve found the autosizing isn’t always reliable and I have
to hard-enter capacities at times.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">- Increased the Min Air flow ratio in the Zones of the VAV system to almost 0.9<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:red">[NC] </span><span lang="EN-GB" style="color:red">Pushing all terminal minimum airflows up to 0.9 sounds unrealistic to my experience for correctly applied VAV systems if you intend to model everything working properly…
It may be appropriate to raise the minimum for specific zones however exhibiting difficulties to help eQUEST distribute airflow when/where needed. Inputs for min airflow and max heating airflow ratios at the system (central) fan should also be considered.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">- Increased Throttling range to 5°R<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:red">[NC] </span><span lang="EN-GB" style="color:red">This can be counterproductive to reducing unmet hours in some cases. Rather than fiddle with this dial for a desired result, try to affirm and match actual controls/design.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">- Increased Reheat Delta T to 35°F<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:red">[NC] </span><span lang="EN-GB" style="color:red">d35 is within reason for reheat coils. Better to confirm against coil design/selections, as it can vary, but I wouldn’t be as concerned with this choice.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">There is no restraint on the amount of heat the building wants. Hence, I wish the building receives unlimited heating from the Hot Water(Purchased Heat),So whatever is the requirement ,it is sufficed by the Heating system.
<br>
This may lead to reduction in Heating Unmet hours.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:red">Your LOOP-OPERATION input (typically) determines whether heating is restricted when it’s called for by a system/coil (either due to temperature, scheduling, or some combination). Sounds like you want
DEMAND-ONLY or STANDBY, paired with a steam meter rather than a boiler.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">1)How can I do this, to reduce the Heating Unmet hours?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:red">[NC] </span><span lang="EN-GB" style="color:red">I
<u>think</u> you’re asking how you can check your suspicions that the loop is not delivering heat when needed. <o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span lang="EN-GB" style="font-family:Symbol;color:red"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-GB" style="color:red">Firstly, you’d probably see a warning/caution to this effect in the ATTN report if this were the case.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span lang="EN-GB" style="font-family:Symbol;color:red"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-GB" style="color:red">Secondly: Project & Site tab
</span><span lang="EN-GB" style="font-family:Wingdings">à</span><span lang="EN-GB" style="color:red"> Create an Hourly Report
</span><span lang="EN-GB" style="font-family:Wingdings">à</span><span lang="EN-GB" style="color:red"> Create a custom block for your HW loop (you might want to create a few if you have multiple HHW loops)
</span><span lang="EN-GB" style="font-family:Wingdings">à</span><span lang="EN-GB" style="color:red"> select the result options (tickboxes) to report on hourly coil loads, flows, and any of the loop operation flags that may help complete the picture. Also
create a block to track your steam meter’s output. </span><span lang="EN-GB" style="font-family:Wingdings;color:red">à</span><span lang="EN-GB" style="color:red"> Assign those blocks to the new report you made
</span><span lang="EN-GB" style="font-family:Wingdings;color:red">à</span><span lang="EN-GB" style="color:red"> Close the hourly results dialog, simulate, then export hourly results (File, Export, Hourly results)
</span><span lang="EN-GB" style="font-family:Wingdings;color:red">à</span><span lang="EN-GB" style="color:red"> You should be able to review exactly what’s being asked for vs. what’s being provided each hour of the simulation (I’d suggest doing some algebra
to find & quantify any differences – consider pump heating contributions while you’re at it).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><u><span lang="EN-GB">Baseline Case : System 7<o:p></o:p></span></u></b></p>
<p class="MsoNormal"><span lang="EN-GB">- As the VAV system is with Reheat, and the heating is through Hot water(Purchased heat).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">1)Would it be right to Keep Baseboard Heating using Hot water on to counter Unmet hours?<span style="color:red"><o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="color:red">[NC] </span><span lang="EN-GB" style="color:red">I might consider this as a “band aid fix” if I were running out of time on a deadline, but relative to “fixing” airside delivery this is likely to be detrimental to
your performance rating (energies associated with air movement and ventilation loads might be left unaccounted for). You’re better advised to strip baseboard heating out of your baseline and figure out how to get your airside heating operational.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Unmet hours is Approx 5000.<span style="color:red"><o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="color:red">[NC] </span><span lang="EN-GB" style="color:red">Sounds like you should fix your proposed case first and apply whatever changes are appropriate to your baseline – they’re both “broken” in a similar magnitude.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">- As per G3.1.3.12, The Min Air Flow ratio is to be 0.4<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">2)Can I increase it to counter Unmet Cooling and Heating hours?<span style="color:red"><o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="color:red">[NC] </span><span lang="EN-GB" style="color:red">Yes, but per above I would only advise this on a “spot” basis to address specific zones exhibiting unmet hours. Typically these are cases where eQUEST’s airflow sizing
routines don’t catch relatively high internal/skin loads for something like a corner office or corridor vestibule.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">As the Project Deadline is <b>28/10/16</b>. I really needed advice.<span style="color:red"><o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="color:red">[NC] </span><span lang="EN-GB" style="color:red">Block out any time you need for documentation to establish your “pencils down” point, and mark your calendar. If between here and that point you determine you’re
not likely to make it, communicate that you need more time/help/resources to those that need to hear it inside your company. Be advised there are independent consultants monitoring these lists & available for hire who could be a resource if engaged with enough
time before your deadline to review and catch up on your development efforts to-date.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:red"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:red">Focus on your Proposed case. Save a separate copy, and take a moment to reverse (or reconsider/research) any arbitrary tweaks you’ve made so far in the name of making unmet hours go away (thankfully
it looks like you’re in a good habit of self-documenting such edits). Your actual goal is to find and resolve the cause of the hours and those tweaks have a high probability of obfuscating the true causes. Document your reasoning and edits to facilitate
carrying those changes over to the Baseline model later.</span><span lang="EN-GB" style="color:red">
</span><span lang="EN-GB" style="color:red">My intuition/hunch is you need to carefully review where the unmet hours are occurring (everywhere? 1 or a few specific zones?). Also review thermostat schedules and application (don’t place thermostats where they
don’t exist) to be sure the calls for conditioning are reasonable. Also review system fan schedules & operation to ensure they’re responding to calls as they come.</span><span lang="EN-GB" style="color:red"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Please Feel Free to add any suggestion or approach strategies! :)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#7F7F7F;mso-fareast-language:EN-GB">Best Regards</span><span lang="EN-GB" style="mso-fareast-language:DA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#7F7F7F;mso-fareast-language:EN-GB"> </span><span lang="EN-GB" style="mso-fareast-language:DA"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#F04E23;mso-fareast-language:DA">Kumar
</span></b><span lang="EN-GB" style="mso-fareast-language:DA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
______________________________________________________________________<br>
This email has been scanned by the Symantec Email Security.cloud service.<br>
______________________________________________________________________<o:p></o:p></span></p>
</div>
<hr width="100%" size="2" align="left" noshade="" style="color:#8091A5; ">
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:gray">This message was scanned by Exchange Online Protection Services.
</span>
<hr width="100%" size="2" align="left" noshade="" style="color:#8091A5; ">
</body>
</html>