<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 12 (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:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Stylus BT";
panose-1:2 14 4 2 2 2 6 2 3 4;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
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";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:546645261;
mso-list-type:hybrid;
mso-list-template-ids:1735918808 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Nathan is quicker on the draw =). Here’s my response as assembled prior to his flying finish – I think I get through his bullets 1 + 2, and I’ve nothing to add to his answers for 3 & 4:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">This is not a knock on anyone, but I advise at the outset to take GBCI review commentary with a grain of salt, particularly when it concerns means/methods specific to eQuest or any given software package.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">My baseline models normally include manually entered efficiencies and autosizing capacities (cooling, heating, airflow) – I do not see anything wrong in that. I am further personally unaware of any 90.1-baseline
approach that relies on utilizing eQuest defaults for cooling/heating/fan efficiencies – to my knowledge there is no direct correlation between what eQuest wizards suggest for default efficiencies and any particular vintage of 90.1. I understand these should
all be manually entered, after performing separate baseline fan power and efficiency calculations per 90.1 appendix G. My preference (and I think, the normal) is to use kW/CFM inputs for fans over the motor efficiency option.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">If you aren’t sure how to verify the effects of overriding manually entered heating/cooling/fan efficiencies, then I hesitate to recommend any course of action before pursuing that understanding first. Otherwise
you can only be shooting in the dark. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">An informed course of action, in an auditing role, would involve reviewing or better performing the calculations yourself from scratch for Pfan and corresponding cooling/heating efficiencies, then comparing your
results against what the modeler assembled and input, thus identifying and correcting any faults directly.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">LEED baseline requirements never shift to anything more strict than the appropriate vintage of 90.1. You can choose, at your option, to reference and document compliance with “qualifying energy codes” for EAp2
if I recall the present template language correctly, but nothing mandates doing so over 90.1. If a team should choose to design a building to meet/exceed 90.1-2010 or Title 24, that does not mean a LEED v3 baseline is anything better or more stringent than
as prescribed in 90.1-2007.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">~Nick<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D"><img width="119" height="37" id="_x0000_i1026" src="cid:image002.jpg@01CD48B2.88BBF3D0" alt="cid:489575314@22072009-0ABB"></span><b><span style="font-family:"Stylus BT","sans-serif";color:#2D4D5E"><o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-family:"Stylus BT","sans-serif";color:#2D4D5E"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Stylus BT","sans-serif";color:#2D4D5E">NICK CATON, P.E.</span></b><b><span style="font-size:12.0pt;font-family:"Stylus BT","sans-serif";color:#2D4D5E"><o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:7.5pt;color:#CC9900">SENIOR ENGINEER<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:7.5pt;color:#CC9900"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">Smith & Boucher Engineers</span><span style="font-size:7.5pt;font-family:"Times New Roman","serif";color:#CC9900"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">25501 west valley parkway, suite 200<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">olathe, ks 66061<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">direct 913.344.0036<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">fax 913.345.0617<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="www.smithboucher.com" title="blocked::www.smithboucher.com"><span style="font-size:10.0pt">www.smithboucher.com</span></a></span><u><span style="font-size:10.0pt;color:blue">
</span></u><span style="color:#1F497D"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> equest-users-bounces@lists.onebuilding.org [mailto:equest-users-bounces@lists.onebuilding.org]
<b>On Behalf Of </b>Nathan Miller<br>
<b>Sent:</b> Tuesday, June 12, 2012 3:38 PM<br>
<b>To:</b> 'Laura Howe, RCE'; equest-users@lists.onebuilding.org<br>
<b>Subject:</b> Re: [Equest-users] Revert efficiencies to autosize from detailed?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Laura, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Many questions here, so I will try to respond succinctly to each, but forgive me if I am a little short on details.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">eQUEST WILL NOT default to the proper 90.1 baseline efficiency or fan power for your systems. You need to look up the appropriate EER (or COP, or whatever) and convert it to the proper EIR (unitless)
efficiency to input in eQUEST. However, to further complicate things, if the 90.1 baseline efficiency includes system fan-power, you need to separate out that fanpower from the EIR rating and input the fanpower separately. There has been much discussion of
this even in the past week on the forums, so I recommend doing some searches for “separating fan power” or the like.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Yes, use the defined 90.1 Appendix G baseline even if local code is more stringent. Consider it a nice little bonus of working on projects with strict energy codes.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">3)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">System 4 (PSZ-HP) should have constant volume fans. You are taking a penalty if they were made variable speed in the baseline.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">4)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">You can edit the project name by opening the .inp file in a text editor, and changing the “Title” field. Then save the .inp, reopen in eQUEST and it should be good to go.
<o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="color:#1F497D"><img border="0" width="653" height="397" id="Picture_x0020_1" src="cid:image003.png@01CD48B2.88BBF3D0"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="margin-top:1.0pt"><b><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#632423">Nathan Miller, PE, LEED AP BD+C<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-top:4.0pt"><i><span style="font-size:8.0pt;font-family:"Verdana","sans-serif";color:black">Mechanical Engineer/Senior Energy Analyst<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-top:8.0pt;line-height:115%"><b><span style="font-size:8.0pt;line-height:115%;font-family:"Verdana","sans-serif";color:#632423">O
</span></b><span style="font-size:8.0pt;line-height:115%;font-family:"Verdana","sans-serif";color:black">206-285-7100</span><span style="font-size:8.0pt;line-height:115%;font-family:"Verdana","sans-serif";color:#BFAB7F">
</span><span style="font-size:8.0pt;line-height:115%;font-family:"Verdana","sans-serif";color:black">|
</span><b><span style="font-size:8.0pt;line-height:115%;font-family:"Verdana","sans-serif";color:#632423">D</span></b><span style="font-size:8.0pt;line-height:115%;font-family:"Verdana","sans-serif";color:#A50021">
</span><span style="font-size:8.0pt;line-height:115%;font-family:"Verdana","sans-serif";color:black">206-788-4577</span><span style="font-size:8.0pt;line-height:115%;font-family:"Verdana","sans-serif";color:#BFAB7F"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:3.0pt"><span style="color:#1F497D"><a href="http://www.rushingco.com/"><b><i><span style="font-size:8.0pt;font-family:"Verdana","sans-serif";color:#632423">www.rushingco.com</span></i></b></a><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a href="mailto:equest-users-bounces@lists.onebuilding.org">equest-users-bounces@lists.onebuilding.org</a> [<a href="mailto:equest-users-bounces@lists.onebuilding.org">mailto:equest-users-bounces@lists.onebuilding.org</a>]
<b>On Behalf Of </b>Laura Howe, RCE<br>
<b>Sent:</b> Tuesday, June 12, 2012 1:11 PM<br>
<b>To:</b> <a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a><br>
<b>Subject:</b> [Equest-users] Revert efficiencies to autosize from detailed?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">HI All-<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">While there are some posts similar to this issue, I want to ask the group for clarification for a slightly different application. Please bear with me for some assistance, I’d sure appreciate it!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I am working on someone else’s model that has had comments back from GBCI for a LEED project. The model came to me in detailed mode. They note that in the baseline model apparently non-90.1 baseline efficiencies were used. Looking at
the model, it does seem that the modeler manually entered efficiencies (they are in red) and they do not seem to be correct (even the GBCI comment notes this). They are less efficient than 90.1. In some of the similar threads on this topic, someone mentioned
that you can revert to autosizing by right clicking on the heating and cooling capacity and selecting “restore default”. Since the modeler did not manually input system size, just system efficiency (both cooling and heating hp eff, fan design kw/cfm and total
eff frac seem to be manually entered), my question is if I restore those efficiency values to default (using right clicking), will Equest use the proper efficiencies and I’m good to ho? I’ve done this, and it seems to work, although I’m not experienced enough
to truly verify this. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">When I compare the two models (original base and my reverted base) I do see where the power demand has dropped (SV-A), and none of the peak loads have changed (LS-A) but the equipment sizing (SV-A) has increased. This all seems correct,
do others think I am on track here? Using the correct methodology?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If I can also confirm another question, LEED specific. I understand 90.1 is the only appropriate base case for LEED even in Washington state, even if portions of their energy code are more stringent, correct? The requirement to achieve
a 10% reduction is how I think LEED addresses more stringent state codes so the base doesn’t need to be written specific to those (numerous) state codes. Correct? One comment from the client leads me to think that complying with WA code might explain the
difference in equipment efficiencies used in the base case, and even though it doesn’t add up I want to confirm my understanding.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Another issue that further confuses this is that the modeler apparently chose two of the systems to be variable speed (all are system type 4, constant volume in 90.1) and I’m not sure why. The original modeler is not available for questioning.
Any ideas? The VFD’s were applied to an office space and data/server room packaged heat pumps, but not a large storage space. Based on what I know right now, it seems those should be modeled constant volume. If I’m updating the base model, I think it makes
sense to correct this if the base incorrectly models a more efficient system.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Lastly, can anyone tell me how to change the project descriptor at the top left of the sim reports? It’s got some boilerplate name and it sure would be nice to have the filename show, or at least a single descriptor I can update in each
model run.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks so much-<o:p></o:p></p>
<p class="MsoNormal">Laura<o:p></o:p></p>
</div>
</body>
</html>