<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=utf-8">
<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: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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"AvantGarde Bk BT";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:#3333FF;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:#3333FF;}
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";
color:#3333FF;}
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";
color:#3333FF;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:#3333FF;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
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:57367115;
mso-list-type:hybrid;
mso-list-template-ids:-309454064 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:352920236;
mso-list-type:hybrid;
mso-list-template-ids:-1725904850 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1: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 l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1: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 l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1: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 l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l2
{mso-list-id:1436245277;
mso-list-type:hybrid;
mso-list-template-ids:1288326504 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
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 bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">All,<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">On the issue of fan sizing, here is what I have observed:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><u><span style="color:#1F497D">There are two ways to oversize (or undersize) the air handler to match the installed capacity.<o:p></o:p></span></u></b></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l2 level1 lfo3"><![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">Input airflow under block cooling airflow: Create Systems
</span><span style="font-family:Wingdings;color:#1F497D">à</span><span style="color:#1F497D"> Advanced<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l2 level1 lfo3"><![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">Input coil capacity percentage with Capacity Units of “% of design capacity by adjusting airflow”<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">Both of these do indeed make the unit larger, and they do this by increasing the airflow for each room by a proportional amount. This gets the fan the right size, but adds extra capacity on a room basis that
does not exist. Then Trace uses this extra capacity in the hourly analysis. <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">Actual numbers from one air handler on a current project:<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">No oversizing:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo4"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Block CFM = 11,453 CFM (from Load-Airflow Summary report)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo4"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Sum of Peaks = 11,469 CFM (from Load-Airflow Summary report)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo4"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Fan size = 11,453 CFM (Equipment Energy Consumption Report)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo4"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><b><span style="color:#1F497D">Peak hourly airflow = 10,570 CFM (from Visualizer)<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Manually input block airflow to match scheduled capacity:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo4"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Block CFM = 15,000 CFM (from Load-Airflow Summary report) – manually input<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo4"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Sum of Peaks = 15,000 CFM (from Load-Airflow Summary report)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo4"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">Fan size = 15,000 CFM (Equipment Energy Consumption Report)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo4"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><b><span style="color:#1F497D">Peak hourly airflow = 11,469 CFM (from Visualizer)<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">When I manually input the block airflow it did increase the fan size, but when looking at the hourly results the actual hourly airflows increased as well since each room was given a proportional increase in CFM
capacity to get to the right unit capacity. This extra capacity would be used for periods when the load exceeds the actual capacity for a short duration: cool down or when OA conditions are more extreme than used for the load calculation (design weather <>
hourly weather data). Thus you cannot set the unit capacity separate from the room capacity in Trace (as far as I can tell). This partly solves the problem of getting the fan the right size, but the added capacity can have an unintended impact of cooling
energy use or on fan power by allowing the room by room airflow to be higher than the actual system.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><u><span style="color:#1F497D">The overall impact of the consequences of oversizing each room may not be significant, but you can run the model with and without a manual input for fan block airflow and see the impact on cooling, heating
and fan power.</span></u></b><span style="color:#1F497D"> This does allow you to exactly match the unit CFM in Trace model which should keep the LEED reviewer happy.<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">See below for screen shots of inputs (for oversized system) and Equipment Energy Consumption Report excerpt for oversized and non-oversized air handler in Trace. It does show the expected fan power savings for
the oversized fan.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><img width="434" height="428" id="_x0000_i1033" src="cid:image007.png@01CFE245.23954680"><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"><img width="669" height="294" id="Picture_x0020_2" src="cid:image008.png@01CFE246.EA467D70"><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"><img width="884" height="375" id="_x0000_i1031" src="cid:image009.png@01CFE248.2A9F7650"><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<table class="MsoNormalTable" border="0" cellpadding="0" width="474" style="width:355.5pt">
<tbody>
<tr>
<td width="167" valign="top" style="width:125.25pt;padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal" style="line-height:105%"><b><span style="font-size:10.0pt;line-height:105%;color:#660000;text-transform:uppercase">Scott Parker</span></b><span style="font-size:9.0pt;line-height:105%;color:#333333"> PE<br>
LEED AP BD+C <br>
</span><span style="font-size:10.0pt;line-height:105%;color:black;text-transform:uppercase">Mechanical</span><span style="font-size:9.0pt;line-height:105%;font-family:"Times New Roman","serif";color:#333333"><o:p></o:p></span></p>
</td>
<td width="10" valign="top" style="width:7.5pt;padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal" style="line-height:105%"><span style="font-size:9.0pt;line-height:105%;color:#333333"> <o:p></o:p></span></p>
</td>
<td width="283" valign="top" style="width:212.25pt;padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal" style="line-height:105%"><b><span style="font-size:9.0pt;line-height:105%;color:#660000">AEI</span></b><span style="font-size:9.0pt;line-height:105%;color:#333333"> | AFFILIATED ENGINEERS, INC. <br>
1414 Raleigh Road, Suite 305 | Chapel Hill, NC 27517<br>
<br>
</span><span style="font-size:9.0pt;line-height:105%;color:#660000">P: 919.419.9802 | F: 919.419.9803</span><span style="font-size:9.0pt;line-height:105%;color:#333333"> <br>
</span><span style="font-size:12.0pt;line-height:105%;font-family:"Times New Roman","serif";color:#1F497D"><a href="mailto:sparker@aeieng.com"><span style="font-size:9.0pt;line-height:105%;font-family:"Calibri","sans-serif";color:#660000;text-decoration:none">sparker@aeieng.com</span></a></span><span style="font-size:9.0pt;line-height:105%;color:#660000">
| </span><span style="font-size:12.0pt;line-height:105%;font-family:"Times New Roman","serif";color:#1F497D"><a href="http://www.aeieng.com/"><b><span style="font-size:9.0pt;line-height:105%;font-family:"Calibri","sans-serif";color:#660000;text-decoration:none">www.aeieng.com</span></b></a></span><span style="font-size:9.0pt;line-height:105%;color:#333333">
<o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><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 #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:windowtext">From:</span></b><span style="color:windowtext"> Dahlstrom, Aaron [mailto:ADahlstrom@in-posse.com]
<br>
<b>Sent:</b> Tuesday, October 07, 2014 1:44 PM<br>
<b>To:</b> Craig Gann; Scott Parker; Steve Jacobs; 'Caballero, Catalina'; trace-users@lists.onebuilding.org<br>
<b>Subject:</b> RE: [Trace-users] Load Calcs vs Energy Model for LEED<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:windowtext">Scott/Craig –
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:windowtext">I have two ideas that might help get a workaround – it may not work on every system type, but it did on a FPVAV system I just experimented with:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="font-size:12.0pt;color:windowtext"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:12.0pt;color:windowtext">To address Scott’s issue re: a the difference between block load and sum of peak zone CFMs, Trace offers an option to size the fan (and/or the main cooling coil) based on the sum
of the peak airflows, rather than the block airflow. On the “Create Systems” dialog, “Advanced…” button there are fields that allow you to modify the parameter used to determine the fan size and the coil size (as below). Changing these from “block” to “peak”
changed the flow of the “Tutorialtrc.trc” file from 16160 cfm sum of peaks / 13778 block cfm to 16160 sum of peaks / 16160 block CFM.<o:p></o:p></span></p>
<p class="MsoListParagraph"><img border="0" width="382" height="318" id="_x0000_i1025" src="cid:image001.jpg@01CFE243.8AFC4AF0"><span style="font-size:12.0pt;color:windowtext"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="font-size:12.0pt;color:windowtext"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:12.0pt;color:windowtext">On the Create Systems – Heating and Cooling Over-rides tab, the main cooling coil can be oversized by a specific percentage “by adjusting airflow.” I believe this would allow you
to maintain the same discharge air temp and modify the system airflow as desired. It may not offer unconstrained combinations of leaving air temp, coil capacity, and system airflow, since Trace is auto calculating entering air conditions, but it may offer
you an additional degree of freedom to get close at the system level:<o:p></o:p></span></p>
<p class="MsoListParagraph"><img border="0" width="480" height="343" id="_x0000_i1026" src="cid:image002.jpg@01CFE243.8AFC4AF0"><span style="font-size:12.0pt;color:windowtext"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:windowtext">There may be unexpected consequences that make these ideas less than the best for your specific situations – but it seems like I’m able (at least in this case) to get the fan CFM to match
the scheduled CFM, even if the load calc block load would show a different total CFM.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:windowtext">Hope this helps,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:windowtext"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="line-height:150%;text-autospace:none"><b><span style="font-size:9.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:gray">Aaron Dahlstrom, PE, LEED® AP</span></b><span style="color:windowtext"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:150%;text-autospace:none"><b><span style="font-family:"AvantGarde Bk BT";color:#17365D">In P</span></b><b><span style="font-family:"AvantGarde Bk BT";color:#619428">o</span></b><b><span style="font-family:"AvantGarde Bk BT";color:#17365D">sse</span></b><span style="font-size:9.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:gray">
– </span><span style="font-size:8.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:gray">A subsidiary of</span><span style="font-size:9.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:gray">
</span><b><span style="font-size:9.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:#CC0000">AKF</span></b><span style="font-size:9.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:gray">| 1500 Walnut Street, Suite 1414, Philadelphia,
PA 19102 </span><span style="color:windowtext"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:150%;text-autospace:none"><span style="font-size:9.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:gray">d: 215-282-6753| m: 267-507-5470| In Posse: 215-282-6800| AKF: 212-354-5656</span><span style="color:windowtext"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:9.0pt;font-family:"Verdana","sans-serif";color:gray">e:
<a href="mailto:ADahlstrom@in-posse.com">ADahlstrom@in-posse.com</a> | in posse web:
<a href="http://www.in-posse.com/">www.in-posse.com</a> | akf web: </span><span style="font-size:9.0pt;font-family:"Verdana","sans-serif";color:windowtext"><a href="www.AKFGroup.com">www.AKFGroup.com</a></span><span style="color:windowtext"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Times New Roman","serif";color:gray"> </span><span style="font-size:12.0pt;color:windowtext"><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";color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> Trace-users [<a href="mailto:trace-users-bounces@lists.onebuilding.org">mailto:trace-users-bounces@lists.onebuilding.org</a>]
<b>On Behalf Of </b>Craig Gann<br>
<b>Sent:</b> Tuesday, October 07, 2014 12:55 PM<br>
<b>To:</b> Scott Parker; Steve Jacobs; 'Caballero, Catalina'; <a href="mailto:trace-users@lists.onebuilding.org">
trace-users@lists.onebuilding.org</a><br>
<b>Subject:</b> Re: [Trace-users] Load Calcs vs Energy Model for LEED<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">I communicated with CDS about this a couple of months ago. It's a royal pain in the @#$ to do this! What you have to do is go to the rooms and manually enter the CFM for each room such that it totals up to the
desired CFM at the system level. This means you have to first figure out which rooms are assigned to each system then figure out how much to change each room CFM such that it totals to what you want then print out the calculated room CFM values. Not easy if
you have hundreds of rooms. I wound up putting it all in Excel so I could figure out a room CFM multiplier that changed each room CFM by the percentage needed. It took me a half day to mess with this and is a major deficiency in the Trace software IMHO.<br>
<br>
Regards,<br>
<br>
Craig J. Gann, P.E.; LEED AP<o:p></o:p></p>
<div>
<p class="MsoNormal">On 10/7/2014 11:18 AM, Scott Parker wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="color:#1F497D">I agree that the proposed system model should have the same capacity as the actual equipment. However, the challenge is that when you fix the leaving air temperature of the air handler (which matches typical
design) then Trace does not allow any method for fixing the air handler CFM capacity.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><u><span style="color:#1F497D">For example, below I have just listed some numbers for reference to illustrate the point:</span></u></b><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Sum of Peaks = 19,458 CFM</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Block load = 18,902 CFM (actual maximum hourly airflow in Trace will typically be even less than this value)</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">AHU size = 20,000 CFM (scheduled on plans)</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">AHU size in trace = block load (18,902 CFM) – no way to force it to be 20,000 CFM.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Therefore, when the air handler (in Trace) is at 18,902 CFM it is at peak fan power (i.e. top of fan curve). However, it actually is already part way down the true fan curve since the unit is scheduled for 20,000
CFM. If you use the theoretical fan laws, then the fan power at 18,902 CFM is 84% of the scheduled break horsepower - (18,902/20,000)^3 = 0.84 -- even though the fan is operating at 94.5% of peak fan power.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">If anyone has a work around for this I would like to hear it. For me I have had to manually change the kW/CFM value to match the actual scheduled fan at the block airflow calculated in Trace.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<table class="MsoNormalTable" border="0" cellpadding="0" width="474" style="width:355.5pt">
<tbody>
<tr>
<td width="167" valign="top" style="width:125.25pt;padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal" style="line-height:105%"><b><span style="font-size:10.0pt;line-height:105%;color:#660000;text-transform:uppercase">Scott Parker</span></b><span style="font-size:9.0pt;line-height:105%;color:#333333"> PE<br>
LEED AP BD+C <br>
</span><span style="font-size:10.0pt;line-height:105%;color:black;text-transform:uppercase">Mechanical</span><o:p></o:p></p>
</td>
<td width="10" valign="top" style="width:7.5pt;padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal" style="line-height:105%"><span style="font-size:9.0pt;line-height:105%;color:#333333"> </span><o:p></o:p></p>
</td>
<td width="283" valign="top" style="width:212.25pt;padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal" style="line-height:105%"><b><span style="font-size:9.0pt;line-height:105%;color:#660000">AEI</span></b><span style="font-size:9.0pt;line-height:105%;color:#333333"> | AFFILIATED ENGINEERS, INC. <br>
1414 Raleigh Road, Suite 305 | Chapel Hill, NC 27517<br>
<br>
</span><span style="font-size:9.0pt;line-height:105%;color:#660000">P: 919.419.9802 | F: 919.419.9803</span><span style="font-size:9.0pt;line-height:105%;color:#333333"> <br>
</span><span style="font-size:12.0pt;line-height:105%"><a href="mailto:sparker@aeieng.com"><span style="font-size:9.0pt;line-height:105%;color:#660000;text-decoration:none">sparker@aeieng.com</span></a></span><span style="font-size:9.0pt;line-height:105%;color:#660000">
| </span><span style="font-size:12.0pt;line-height:105%"><a href="http://www.aeieng.com/"><b><span style="font-size:9.0pt;line-height:105%;color:#660000;text-decoration:none">www.aeieng.com</span></b></a></span><span style="font-size:9.0pt;line-height:105%;color:#333333">
</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><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> Trace-users [<a href="mailto:trace-users-bounces@lists.onebuilding.org">mailto:trace-users-bounces@lists.onebuilding.org</a>]
<b>On Behalf Of </b>Steve Jacobs<br>
<b>Sent:</b> Tuesday, October 07, 2014 11:13 AM<br>
<b>To:</b> 'Caballero, Catalina'; <a href="mailto:trace-users@lists.onebuilding.org">
trace-users@lists.onebuilding.org</a><br>
<b>Subject:</b> Re: [Trace-users] Load Calcs vs Energy Model for LEED<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Your proposed inputs need to match what is actually being installed in the building. If they are installing oversized equipment, you need to model oversized equipment. The model will account for part load efficiencies.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="color:#1F497D">-</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">Steve</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></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""> Trace-users [<a href="mailto:trace-users-bounces@lists.onebuilding.org">mailto:trace-users-bounces@lists.onebuilding.org</a>]
<b>On Behalf Of </b>Caballero, Catalina<br>
<b>Sent:</b> Tuesday, October 7, 2014 9:04 AM<br>
<b>To:</b> <a href="mailto:trace-users@lists.onebuilding.org">trace-users@lists.onebuilding.org</a><br>
<b>Subject:</b> [Trace-users] Load Calcs vs Energy Model for LEED</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Hello experts,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">We <span style="font-size:10.0pt">recently received comments back from LEED and one of the comments says the following:
</span><o:p></o:p></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt"> </span></i><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><i><span style="font-size:10.0pt;color:#444444">It appears the equipment capacities (fan volume, fan power, cooling capacity, etc.) for the HVAC systems in the Proposed model</span></i><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><i><span style="font-size:10.0pt;color:#444444">are inconsistent with the equipment capacities in the actual design when comparing the LEED Energy Performance Summary Report</span></i><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><i><span style="font-size:10.0pt;color:#444444">to the mechanical schedules provided for PIf4: Schedule and Overview Documents</span></i><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><i><span style="font-size:10.0pt;color:#444444">G3.1.10 in the Proposed building column requires that the Proposed model reflect all HVAC systems at actual equipment capacities</span></i><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><i><span style="font-size:10.0pt;color:#444444">and efficiencies. The HVAC equipment capacities cannot be autosized in the Proposed model. Revise the Proposed model to reflect</span></i><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><i><span style="font-size:10.0pt;color:#444444">all HVAC systems at actual equipment capacities. In addition, update Table 1.4.7B, and provide a revised LEED Energy Performance</span></i><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><i><span style="font-size:10.0pt;color:#444444">Summary Report and the System Enterd Values reports for the Proposed model reflecting the changes. Further, if the equipment</span></i><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><i><span style="font-size:10.0pt;color:#444444">capacities and efficiencies are based on updated mechanical schedules and/or HVAC submittal sheets, provide the updated</span></i><o:p></o:p></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;color:#444444">mechanical schedules and/or HVAC submittal sheets.</span></i><o:p></o:p></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;color:#444444"> </span></i><o:p></o:p></p>
<p class="MsoNormal"><span style="color:red">The only question that I have is why would they require for the airflows, to be exactly the same, to the original load calculations when the load calculations looks for the worst case scenario (using ashrae basic
envelope, lighting, values), while the energy model looks for the most energy efficient model (actual installed envelope, occupancy, etc). It make sense that they are looking for something similar but it’s definitely not going to match the capacities and or
airflows, (load calcs tend to be oversized).</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:red"> </span><o:p></o:p></p>
<p class="MsoNormal">I would greatly appreciate your opinion.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Thanks.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-size:9.0pt">Catalina Caballero</span></b><span style="font-size:9.0pt">. AIA. Assoc., LEED GA.</span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><i><span style="font-size:9.0pt">Sustainability Coordinator</span></i><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><i><span style="font-size:9.0pt"> </span></i><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-size:9.0pt">Johnson, Avedano, Lopez, Rodriguez & Walewski Engineering Group, Inc.</span></b><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:9.0pt">Engineering for High Performance Buildings.</span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><i><span style="font-size:9.0pt">MEPF - BIM - LEED - Cx</span></i><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:9.0pt"><br>
2510 NW 97 Ave, Ste 220, Miami, FL 33172.</span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-size:9.0pt">P:</span></b><span style="font-size:9.0pt"> 305.594.0660 <b>Ext:</b> 217
</span><span style="font-size:9.0pt;color:black">Ӏ</span><span style="font-size:9.0pt">
<b>F: </b>305.594.0907 </span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><u><span lang="IT" style="font-size:9.0pt"><a href="http://www.jalrw.com"><span style="color:black">www.jalrw.com</span></a></span></u><span lang="IT" style="font-size:9.0pt">
</span><span style="font-size:9.0pt">| <a href="ccaballero@jalrw.com%20"><span style="color:black">ccaballero@jalrw.com</span></a>
</span><o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" align="left" style="border-collapse:collapse">
<tbody>
<tr>
<td valign="top" style="padding:0in 7.5pt 3.75pt 0in"></td>
</tr>
</tbody>
</table>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:9.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><a href="http://www.facebook.com/jalrw" target="_blank"><span style="text-decoration:none"><img border="0" width="26" height="28" id="Picture_x0020_1" src="cid:image003.png@01CFE243.8AFC4AF0" alt="Facebook"></span></a> <a href="http://www.linkedin.com/company/johnson-avedano-lopez-rodriguez-&-walewski-engineering-group-inc./" target="_blank"><span style="text-decoration:none"><img border="0" width="26" height="28" id="Picture_x0020_14" src="cid:image004.png@01CFE243.8AFC4AF0" alt="LinkedIn"></span></a>
<a href="https://www.twitter.com/JALRW/" target="_blank"><span style="text-decoration:none"><img border="0" width="26" height="28" id="Picture_x0020_3" src="cid:image005.png@01CFE243.8AFC4AF0" alt="Twitter"></span></a> <a href="https://plus.google.com/u/0/b/112470263254966771834/112470263254966771834/posts" target="_blank"><span style="text-decoration:none"><img border="0" width="25" height="28" id="Picture_x0020_4" src="cid:image006.png@01CFE243.8AFC4AF0" alt="Google Plus"></span></a>
<o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"> <o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify;text-autospace:none"><span style="font-size:7.0pt">This email and any files transmitted with it are confidential and intended solely for the addressee.</span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify;text-autospace:none"><span style="font-size:7.0pt">If you are not the named addressee you should not disseminate, distribute, copy, or alter this email.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:7.0pt">Please consider the environment before printing this email.</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Trace-users mailing list<o:p></o:p></pre>
<pre><a href="http://lists.onebuilding.org/listinfo.cgi/trace-users-onebuilding.org">http://lists.onebuilding.org/listinfo.cgi/trace-users-onebuilding.org</a><o:p></o:p></pre>
<pre>To unsubscribe from this mailing list send a blank message to <a href="mailto:TRACE-USERS-UNSUBSCRIBE@ONEBUILDING.ORG">TRACE-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:windowtext">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.
<o:p></o:p></span></p>
</div>
</body>
</html>