<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 14 (filtered medium)"><style><!--
/* Font Definitions */
@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;}
/* 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";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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;}
--></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=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Greg, it looks like it was all in the zoning. Designating the trouble areas with their own system allowed me to reduce the throttling range to a more reasonable number (I left it at 2</span><span style='color:#1F497D'>°</span><span style='color:#1F497D'>). Thanks for your help.<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'>I have a couple of other issues that I can’t figure out. Looking at the ES-D report, it looks like the virtual rate between the proposed and baseline case are different. Why would that be? Everything is set to the local energy company and nothing has been changed in the utility and economics tab. Not exactly sure what a virtual rate is to be honest. <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'>The other question I have is with regards to some energy usage showing up on the baseline model under pumps and aux. The baseline model does not have any pumps associated with it. Any thoughts on what exactly the auxiliary load is accounting for? <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'>Thanks again for your help.<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'>Travis<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'><o:p> </o:p></span></p><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"'> Greg Collins [mailto:GCollins@glumac.com] <br><b>Sent:</b> Tuesday, March 08, 2011 12:58 PM<br><b>To:</b> Travis Miller; equest-users@lists.onebuilding.org<br><b>Subject:</b> RE: [Equest-users] High throttling setting and KW/CFM calc<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>Travis,<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'>Bumping your throttling range up will definitely reduce your unmet cooling/heating hours, but it's not usually the correct approach to do so. You're basically saying that the system is trying to maintain 75°F in cooling (hypothetically), but the cooling demand is met as long as it's less than 75 + 8°F = 83°F. Is 83°F a comfortable temperature for your occupants? Probably not.<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'>I'd check to make sure you have adequate zoning by looking at the SS-R report and seeing if the unmet hours are similar between the spaces in your zone. What can happen is your system will maintain temperature in the control zone (where the thermostat is) and the other spaces can suffer. If all of the spaces have unmet hours, your system capacity might off. There are lots of things that could be wrong, but the reports are your best friend while troubleshooting..<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'>Regarding your kw/cfm calc - I didn't look at it, but the number looks reasonable if you're modeling a 90.1 baseline system. If you're modeling an actual design, you want to use the kW (from bhp) your fan is operating at during the design condition.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Greg Collins</span></b><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>GLUMAC | (949) 833-8190<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"'> Travis Miller [mailto:tmiller@dcengineering.net] <br><b>Sent:</b> Tuesday, March 08, 2011 11:14 AM<br><b>To:</b> equest-users@lists.onebuilding.org<br><b>Subject:</b> [Equest-users] High throttling setting and KW/CFM calc<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I am looking for a little help in trouble shooting a couple of setpoints on the attached model. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The first concern I have is my throttling setpoint. I have it 8 degrees right now. The reason for that was to eliminate unmet cooling hours. Is this a feasible approach? Is there something else that I should be looking at?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Second – Fan design KW/CFM – after reading through the archives I have figured out that I just need to restore the defaults in the static in WG box to allow the KW/CFM box to become active. Is the next step just to calculate the bhp for each unit per table G3.1.2.9, then calculate fan power from section G3.1.2.9? <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I did this for my first unit and got a value of .000768318 KW/CFM. This was for system S1 with a baseline “design” (from the air side summary report) CFM of 1,986 CFM. Does that seem like a reasonable #? I have attached my calc spreadsheet for reference, it is a little crude but I think it is correct. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks again in advance.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Travis<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>