<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:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" 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 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:"Tms Rmn";
panose-1:2 2 6 3 4 5 5 2 3 4;}
@font-face
{font-family:"Tms Rmn";
panose-1:2 2 6 3 4 5 5 2 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";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoListNumber, li.MsoListNumber, div.MsoListNumber
{mso-style-priority:99;
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.MsoBodyText, li.MsoBodyText, div.MsoBodyText
{mso-style-priority:99;
mso-style-link:"Body Text Char";
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";}
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:12.0pt;
font-family:"Times New Roman","serif";}
span.BodyTextChar
{mso-style-name:"Body Text Char";
mso-style-priority:99;
mso-style-link:"Body Text";
font-family:"Times New Roman","serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:windowtext;}
span.EmailStyle26
{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:-120;
mso-list-type:simple;
mso-list-template-ids:-377448274;}
@list l0:level1
{mso-level-style-link:"List Number";
mso-level-tab-stop:.25in;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;}
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=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Just to add my two cents: the 1.08 is the sensible heat correction factor, Cs. ASHRAE Fundamentals 18.13 starts the discussion on when to correct for elevation by stating that “Because air passes through the equipment at a density close to standard for locations below about 1000 ft, the accuracy desired normally requires no correction.” Ironically, ASHRAE Fundamentals uses 1.1 instead of 1.08. 1.08 is the factor I remember from basic air conditioning coursework in college…<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>When I have applied this to eQuest, I usually zero out the elevation for altitudes less than 1000 ft above sea level and let eQuest correct elevations higher than that. As noted earlier in a somewhat indirect way, you don’t want to include this elevation correction twice, so if you are calculating CFM values outside of eQuest and fixing the supply air and outside air to those values then you don’t want eQuest subsequently applying the elevation correction a second time. If you are letting eQuest determine the air volumes then you should let the elevation factor stay, especially for elevations over 1000 ft. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The handbook briefly explains the reasoning behind this factor as being due to the mass-based thermodynamics equations having been converted to volume-based to make calculations easier. Since air is assumed to be an ideal gas, when you exceed 1000 ft in elevation you’ve changed atmospheric pressure enough that 1 CF of air no longer carries the same mass of air.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><b><span style='font-size:7.5pt;font-family:"Verdana","sans-serif";color:#1F497D'>Jeremy R. Poling, PE, LEED AP+BDC</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br><br></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";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>MattDubrovich@Eaton.com<br><b>Sent:</b> Friday, January 21, 2011 10:17 AM<br><b>To:</b> ncaton@smithboucher.com<br><b>Cc:</b> equest-users@lists.onebuilding.org<br><b>Subject:</b> Re: [Equest-users] Does eQUEST derate equipment for altitude?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Nick,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I skipped over a few details in the last email. The “1.08” is the typical sea level transfer factor in: Q=1.08*CFM*Delta_T. eQuest’s altitude factor is the sea level transfer factor over the site’s transfer factor which yields what I have seen called the CFM correction factor. For Denver that is: 1.08/0.89 = 1.21. There are lookups for what the appropriate factor is for your site’s elevation. From what I can tell, eQuest performs all of its calculations with a transfer factor of 1.08, and modifies the airflows at the end of process by multiplying by the site specific CFM correction factor. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><div><p class=MsoNormal style='margin-bottom:12.0pt'><b><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Matt Dubrovich, PE, CEM, BEMP <br></span></b><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Energy Solutions Group</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><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"'> Nick Caton <a href="mailto:[mailto:ncaton@smithboucher.com]">[mailto:ncaton@smithboucher.com]</a> <br><b>Sent:</b> Thursday, January 20, 2011 6:34 PM<br><b>To:</b> Dubrovich, Matt; <a href="mailto:cmg750@gmail.com">cmg750@gmail.com</a><br><b>Cc:</b> <a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a>; <a href="mailto:ktupper@rmi.org">ktupper@rmi.org</a><br><b>Subject:</b> RE: [Equest-users] Does eQUEST derate equipment for altitude?<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";color:#1F497D'>What a pain. =(<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Matt: <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>If the “coil upsizing factor” for altitude (1.08 in your example below?) is not derived from the site altitude as entered under ‘site properties,’ a much easier solution might be to identify where else the altitude is being from and entering a zero there… The site properties dialog pulls it from the weather file, right?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>DOE2 / eQuest developers: <o:p></o:p></span></p><p class=MsoListParagraph><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Is there any feasible possibility of adding an <u>option</u> in a future release/patch to turn altitude adjustments on/off? This might logically be located adjacent to the altitude input in the Site Properties dialog (I’d vote for default = off).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>~Nick<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><img border=0 width=119 height=37 id="Picture_x0020_1" src="cid:image002.jpg@01CBB95C.CBF51F00" alt="cid:489575314@22072009-0ABB"></span><b><span style='font-size:11.0pt;font-family:"Stylus BT";color:#2D4D5E'><o:p></o:p></span></b></p><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Stylus BT";color:#2D4D5E'><o:p> </o:p></span></b></p><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Stylus BT";color:#2D4D5E'>NICK CATON, E.I.T.</span></b><b><span style='font-family:"Stylus BT";color:#2D4D5E'><o:p></o:p></span></b></p><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Calibri","sans-serif";color:#CC9900'>PROJECT ENGINEER<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#2D4D5E'>Smith & Boucher Engineers</span><span style='font-size:7.5pt;color:#CC9900'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#2D4D5E'>25501 west valley parkway<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#2D4D5E'>olathe ks 66061<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#2D4D5E'>direct 913 344.0036<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#2D4D5E'>fax 913 345.0617<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";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;font-family:"Calibri","sans-serif";color:blue'> </span></u><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";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:MattDubrovich@Eaton.com">MattDubrovich@Eaton.com</a> <a href="mailto:[mailto:MattDubrovich@Eaton.com]">[mailto:MattDubrovich@Eaton.com]</a> <br><b>Sent:</b> Thursday, January 20, 2011 6:55 PM<br><b>To:</b> <a href="mailto:cmg750@gmail.com">cmg750@gmail.com</a>; Nick Caton<br><b>Cc:</b> <a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a>; <a href="mailto:ktupper@rmi.org">ktupper@rmi.org</a><br><b>Subject:</b> RE: [Equest-users] Does eQUEST derate equipment for altitude?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Unfortunately I think it might be more complicated than that; I wish it wasn’t. I have an old printout of an eQuest/DOE2 document called “Sizing Air-Side HVAC Systems” which steps through the calculation. I haven’t been able to figure out where I printed it from (help file?, dictionary? engineers manual?). <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>My take is that eQuest sizes coils based on sea level airflow. At the end of the calculation it simply multiples the needed sea level airflow by the altitude factor to account for altitude effects. Per Carol’s email, eQuest assumes any user entered flows are at sea level. This is frustrating because plans usually show airflows at site altitude, not sea level. We’ve tried Nick’s work-around which is to change the altitude to 0 and enter airflows per the drawings. This works on the airflow side but not the coil side. The coils are sized using the entered airflow x 1.08 so eQuest creates coils that are larger than what you actually have. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>What seems to be more correct is to keep the altitude specified and divide every airflow you enter into the model by the altitude factor. If you’re in Denver and want to model a 10,000 CFM fan, enter 10,000/1.21 into the supply CFM input. eQuest takes that number and multiplies it by 1.21. Every input with a “CFM” must be adjusted including exhaust, CFM/SF, etc. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><b><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Matt Dubrovich, PE, CEM, BEMP <br></span></b><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Energy Solutions Group</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","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-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:[mailto:equest-users-bounces@lists.onebuilding.org]">[mailto:equest-users-bounces@lists.onebuilding.org]</a> <b>On Behalf Of </b>Carol Gardner<br><b>Sent:</b> Thursday, January 20, 2011 1:22 PM<br><b>To:</b> Nick Caton<br><b>Cc:</b> <a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a>; Kendra Tupper<br><b>Subject:</b> Re: [Equest-users] Does eQUEST derate equipment for altitude?<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><div style='margin-left:.5in'><p class=MsoBodyText><span style='font-family:"Courier New"'>Nick/Kendra,</span><span style='font-family:"Tms Rmn","serif"'><o:p></o:p></span></p><p class=MsoBodyText><span style='font-family:"Courier New"'>The altitude factor effects the supply air and the outside air. The write up below suggests that one calculate both supply and outside air at sea level and then apply the altitude factor to it. In real life, however, the design engineer is calculating and specifying supply and outside air cfm that is already adjusted for the altitude and the altitude factor should simply be set at 1.0 in eQUEST.</span><span style='font-family:"Tms Rmn","serif"'><o:p></o:p></span></p><p class=MsoBodyText><span style='font-family:"Courier New"'>The excerpts below discuss the areas of eQUEST impacted by the altitude factor:</span><span style='font-family:"Tms Rmn","serif"'><o:p></o:p></span></p><p class=MsoBodyText><span style='font-family:"Courier New"'>N</span><span style='font-family:"Tms Rmn","serif"'>ote: the quantities in this report (SV-A) have been adjusted for <span style='color:white;background:#316AC5'>altitude</span> even though DOE-2 requires that any flows you enter in SYSTEMS be at sea level.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Tms Rmn","serif"'>1. </span>SUPPLY FLOW<br>is the calculated or user-specified supply flow for each zone. Only if you have specified a value for the ASSIGNED-FLOW keyword in the ZONE command will the value here correspond to your input. The ZONE keywords AIR-CHANGES/HR and FLOW/AREA will be accepted by SYSTEMS only if they are consistent with the user-supplied HEATING-CAPACITY and COOLING-CAPACITY and are equivalent to a flow larger than that of the exhaust from or the ventilation to the zone. The <span style='color:white;background:#316AC5'>ALTITUDE FACTOR</span> will be applied.<o:p></o:p></p></div><p class=MsoListNumber style='margin-left:.5in'><span style='font-family:"Tms Rmn","serif"'>5. </span>OUTSIDE AIR FLOW<br>reflects the user-specified outside air quantity entered at the zone level. If OUTSIDE-AIR-FLOW is specified, its value is multiplied by the <span style='color:white;background:#316AC5'>ALTITUDE FACTOR</span> and reported here. Otherwise the reported value is the maximum of the flow-equivalent values of OA-CHANGES and OA-FLOW/PER, multiplied by <span style='color:white;background:#316AC5'>ALTITUDE FACTOR</span>. For the actual amount of outside air delivered to the zone for central systems, see OUTSIDE AIR RATIO above.<o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>On Thu, Jan 20, 2011 at 10:49 AM, Nick Caton <<a href="mailto:ncaton@smithboucher.com">ncaton@smithboucher.com</a>> wrote:<o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;color:#1F497D'>Kenda,</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;color:#1F497D'>I’m curious as to whether you received any responses to the query below.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;color:#1F497D'>I have incorporated a practice of manually setting the site altitude in my eQuest models to “0,” because (1) as designers we do not specify equipment with CFM’s at sea level, it is already “corrected” for altitude in this sense, and (2) those who review models tend to miss the significance of the altitude factor in the SV-A reports and complain of incorrectly entered airflow rates.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;color:#1F497D'>I don’t know if this constitutes a “best practice,” but I know it is common to a number of the regular contributors to these lists besides myself. As it stands, current standards (90.1-2007) don’t have us “de-rate” or otherwise adjust required minimum SEER/EER values for altitude… so inversely it seem appropriate to remove the altitude variable when modeling for a performance rating… thoughts?</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;color:#1F497D'>~Nick</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;color:#1F497D;border:solid windowtext 1.0pt;padding:0in'><img border=0 width=119 height=37 id="Picture_x0020_3" src="cid:image003.jpg@01CBB95C.CBF51F00" alt="Image removed by sender. cid:489575314@22072009-0ABB"></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span style='font-size:11.0pt;color:#2D4D5E'> </span></b><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span style='font-size:11.0pt;color:#2D4D5E'>NICK CATON, E.I.T.</span></b><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:7.5pt;color:#CC9900'>PROJECT ENGINEER</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;color:#2D4D5E'>Smith & Boucher Engineers</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;color:#2D4D5E'>25501 west valley parkway</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;color:#2D4D5E'>olathe ks 66061</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;color:#2D4D5E'>direct 913 344.0036</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;color:#2D4D5E'>fax 913 345.0617</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;color:#1F497D'><a href="http://www.smithboucher.com/" target="_blank" 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><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'> <a href="mailto:equest-users-bounces@lists.onebuilding.org" target="_blank">equest-users-bounces@lists.onebuilding.org</a> [mailto:<a href="mailto:equest-users-bounces@lists.onebuilding.org" target="_blank">equest-users-bounces@lists.onebuilding.org</a>] <b>On Behalf Of </b>Kendra Tupper<br><b>Sent:</b> Thursday, September 02, 2010 1:53 PM<br><b>To:</b> <a href="mailto:equest-users@lists.onebuilding.org" target="_blank">equest-users@lists.onebuilding.org</a><br><b>Subject:</b> [Equest-users] Does eQUEST derate equipment for altitude?</span><o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>All,<o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I'm trying to get clarification on exactly how eQUEST handles the altitude above sea level that is entered in Site Parameters. My understanding is this affects the airflow sizing calculations for cfm, but does not change the hourly air density for all calculations. If that is correct, then the altitude only corrects the cfms at the zone and system level, but does not derate equipment efficiencies. So, if you were to enter the altitude above sea level, you should then enter your airflows at sea level, but enter all equipment efficiencies at the derated conditions for that altitude.<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Is that correct?<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Kendra Tupper, PE, LEED AP<br>Senior Consultant<br>Built Environment Team<br><br>Rocky Mountain Institute | T 303-567-8641 | F 303-245-7213 | <a href="http://www.rmi.org/" target="_blank">www.rmi.org</a><o:p></o:p></p></div></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><br>_______________________________________________<br>Equest-users mailing list<br><a href="http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org" target="_blank">http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org</a><br>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></div><p class=MsoNormal><br><br clear=all><br>-- <br>Carol Gardner PE<o:p></o:p></p></div></div></div></body></html>