<HTML dir=ltr><HEAD>
<META content="text/html; charset=unicode" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 9.00.8112.16421">
<STYLE><!--
font-face
{font-family:"Cambria Math";}
font-face
{font-family:Calibri;}
font-face
{font-family:Tahoma;}
font-face
{font-family:Verdana;}
font-face
{font-family:"AvantGarde Bk BT";}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{
font-family:"Calibri","sans-serif";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{
font-size:10.0pt;}
div.WordSection1
{page:WordSection1;}
--></STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr id=idOWAReplyText54174>
<DIV dir=ltr><FONT color=#000000 size=2 face=Arial>Have you thought about using a "user input function" to define the EIR? I haven't used one this way yet, but there are a few examples out there in the help info. In theory, you could setup a logic statement that checks the capacity and uses the EIR value appropriate for that size system. I'd be willing to discuss the idea with you guys, but there'll be a certain amount of "if at first you don't succeed..." involved to figure out the right code to grab the system capacity.</FONT></DIV>
<DIV dir=ltr><FONT size=2 face=Arial></FONT> </DIV>
<DIV dir=ltr><FONT size=2 face=Arial>I've been playing more with user input functions after seeing some examples of powerful ways they can remove some of the repetitive changes. For example, for single-zone systems, you could theoretically program eQuest to auto-calculate the OA based on ASHRAE 62.1 requirements and the zone area and population. You could probably do it for multi-zone systems also, but that gets into the complexity level of the ASHRAE 62.1 spreadsheet and it is probably less time to just do the calcs in the spreadsheet and input the results.</FONT></DIV>
<DIV dir=ltr><FONT color=#000000 size=2 face=Arial></FONT> </DIV></DIV>
<DIV dir=ltr id=idSignature77069>
<DIV><FONT color=#000000 size=2 face=Arial>
<DIV>
<DIV style="MARGIN: 0in 0in 0pt" class=MsoNormal><B><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; FONT-SIZE: 7.5pt">Jeremy R. Poling, PE, LEED AP+BDC</SPAN></B><SPAN><BR></SPAN></DIV></DIV></FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> equest-users-bounces@lists.onebuilding.org on behalf of Dahlstrom, Aaron<BR><B>Sent:</B> Tue 5/17/2011 10:31 PM<BR><B>To:</B> Bishop, Bill; equest-users@lists.onebuilding.org<BR><B>Subject:</B> Re: [Equest-users] Appendix G Baseline Systems 1 and 2 efficiency<BR></FONT><BR></DIV>
<DIV>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN style="FONT-SIZE: 12pt">Bill:</SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 12pt"></SPAN> </P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 12pt">Your procedure sounds very similar to ours.</SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 12pt"></SPAN> </P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 12pt">Beyond the simple automation of a spreadsheet, and dual monitors to copy data from SIM to XLS quickly, we haven’t found any quicker ways to skin this cat.</SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 12pt"></SPAN> </P>
<DIV>
<P style="LINE-HEIGHT: 150%" class=MsoNormal><B><SPAN style="LINE-HEIGHT: 150%; FONT-FAMILY: 'Verdana','sans-serif'; COLOR: gray; FONT-SIZE: 9pt">Aaron Dahlstrom , PE, LEEDŽ AP</SPAN></B></P>
<P style="LINE-HEIGHT: 150%" class=MsoNormal><B><SPAN style="FONT-FAMILY: 'AvantGarde Bk BT','sans-serif'; COLOR: #17365d">In P</SPAN></B><B><SPAN style="FONT-FAMILY: 'AvantGarde Bk BT','sans-serif'; COLOR: #619428">o</SPAN></B><B><SPAN style="FONT-FAMILY: 'AvantGarde Bk BT','sans-serif'; COLOR: #17365d">sse</SPAN></B><SPAN style="LINE-HEIGHT: 150%; FONT-FAMILY: 'Verdana','sans-serif'; COLOR: gray; FONT-SIZE: 9pt"> – </SPAN><SPAN style="LINE-HEIGHT: 150%; FONT-FAMILY: 'Verdana','sans-serif'; COLOR: gray; FONT-SIZE: 8pt">A subsidiary of</SPAN><SPAN style="LINE-HEIGHT: 150%; FONT-FAMILY: 'Verdana','sans-serif'; COLOR: gray; FONT-SIZE: 9pt"> </SPAN><B><SPAN style="LINE-HEIGHT: 150%; FONT-FAMILY: 'Verdana','sans-serif'; COLOR: #cc0000; FONT-SIZE: 9pt">AKF</SPAN></B><SPAN style="LINE-HEIGHT: 150%; FONT-FAMILY: 'Verdana','sans-serif'; COLOR: gray; FONT-SIZE: 9pt">| 1500 Walnut Street, Suite 1414, Philadelphia, PA 19102 </SPAN></P>
<P style="LINE-HEIGHT: 150%" class=MsoNormal><SPAN style="LINE-HEIGHT: 150%; FONT-FAMILY: 'Verdana','sans-serif'; COLOR: gray; FONT-SIZE: 9pt">d: 215-282-6753| m: 267-507-5470| In Posse: 215-282-6800| AKF: 215-735-7290</SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: gray; FONT-SIZE: 9pt">e: ADahlstrom@in-posse.com | in posse web: <A href="http://www.in-posse.com/">www.in-posse.com</A> | akf web: <A href="http://www.akfgroup.com/">www.akfgroup.com</A></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: gray; FONT-SIZE: 9pt"></SPAN> </P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: gray; FONT-SIZE: 9pt"></SPAN> </P></DIV>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Times New Roman','serif'; COLOR: gray; FONT-SIZE: 9pt"></SPAN><SPAN style="FONT-SIZE: 12pt"></SPAN> </P>
<DIV>
<DIV style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=MsoNormal><B><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> equest-users-bounces@lists.onebuilding.org [mailto:equest-users-bounces@lists.onebuilding.org] <B>On Behalf Of </B>Bishop, Bill<BR><B>Sent:</B> Tuesday, May 17, 2011 3:43 PM<BR><B>To:</B> equest-users@lists.onebuilding.org<BR><B>Subject:</B> [Equest-users] Appendix G Baseline Systems 1 and 2 efficiency</SPAN></P></DIV></DIV>
<P class=MsoNormal> </P>
<P class=MsoNormal>Appendix G Baseline Systems 1 (PTAC) and 2 (PTHP) have cooling efficiencies (and for PTHP, heating efficiencies) that vary with cooling capacity per Table 6.8.1D. Since each thermal block is modeled with its own system, you can end up modeling as many as 100 or more systems per project. For LEED projects (or other App. G models), I have been calculating and manually entering values for cooling EIR for every single system, based on capacities reported in the SV-A reports. I factor in the unique fan power (per G3.1.2.9) for each system and remove its contribution from the efficiency, since fan power is included in EER and needs to be separated per G3.1.2.1. Once you enter efficiency for each system, just about any change you make in the model changes the supply flow rate and/or system capacities, which means you need to redo all the efficiency calculations.</P>
<P class=MsoNormal> </P>
<P class=MsoNormal>Does this method seem correct?</P>
<P class=MsoNormal>Has anyone figured out a way to automate this process? (And by “automate”, I don’t mean give it to the intern.)</P>
<P class=MsoNormal> </P>
<P class=MsoNormal>Thanks,</P>
<P class=MsoNormal>Bill</P>
<P class=MsoNormal> </P>
<P class=MsoNormal><IMG id=Picture_x0020_1 border=0 alt="Signature in jpg form" src="image001.jpg" width=496 height=123></P>
<P class=MsoNormal> </P></DIV><BR clear=all>This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail. E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered without the knowledge of the sender or the intended recipient. If you are not comfortable with the risks associated with e-mail messages, you may decide not to use e-mail to communicate with In Posse. </DIV></BODY></HTML>