<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: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:10.0pt;
font-family:"Arial","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;}
span.emailstyle17
{mso-style-name:emailstyle17;
font-family:"Arial","sans-serif";
color:black;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Jen, Julia,<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'>I’m sorry but I strongly disagree with this e-mail. One must
read and understand ASHRAE 62.1 first to understand how to use Trace for that
calculation. Trace will work properly but you need to know the procedure.
There is some trial and error but it still is as fast as or faster than
manually performing all the ASHRAE 62.1 calculations. Critical rooms may
require some manual adjustment or features like setting the max Z factor can be
very helpful. There is a PDF on the Trane web site I strongly recommend you
download that explains the process pretty well. You can also call the help
desk for guidance.<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 baseline energy usage can and often does increase when the
ASHRAE 62.1 calculation is properly applied because the presence of critical
zones with high occupant density, like conference rooms, will set the OA
percentage for an entire AHU. All the rooms fed by that AHU will have that
same OA percentage and thus some rooms will receive more OA than a simple
calculation (as is done by "Sum Room OA Reqs" on the advanced systems
tab). This increase in OA will increase the energy consumption. If you
selectively over air the critical zones to lower the OA percentage at the AHU,
which is the accepted procedure, then the supply air will increase leading to
increased fan and reheat energy.<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'>This ASHRAE 62.1 feature and the DCV calculation is one of the
best advantages that Trace has over other programs like Equest that cannot do
the ASHRAE 62.1 calculation properly. The Trace program can both design and
model HVAC system OA requirements properly. It also can be used to properly
design and model DOAS units including capturing the sensible and latent cooling
provided. I have not seen any program that can model DCV or OA better than
Trace if you use it properly. <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'>I have used Trace to document DCV savings in LEED project
submissions without difficulty. It just needs to be used properly.<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'>Rick<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 style='text-autospace:none'><span style='font-size:8.0pt;
color:black'>R I C H A R D E L L I S O N</span><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:black'><br>
</span><span style='font-size:8.0pt;color:black'>PE, BEMP, CEM, CEA, CTAB,
CBEP, LEED AP <o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;
color:black'>Manager Energy and Modeling</span><span style='font-family:"Calibri","sans-serif";
color:black'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;color:black'>Southland
Industries<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;color:black'>22340 Dresden
Street, Suite 177<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;color:black'>Dulles, VA 20166<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;color:black'>Office:
703.834.5570<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;color:black'>Direct:
703.834.2438<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;color:black'>Fax: 703.834.5572<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-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-family:"Tahoma","sans-serif"'>
trace-users-bounces@lists.onebuilding.org
[mailto:trace-users-bounces@lists.onebuilding.org] <b>On Behalf Of </b>Julia
Beabout<br>
<b>Sent:</b> Monday, August 30, 2010 9:20 AM<br>
<b>To:</b> Jen Redington; trace-users@lists.onebuilding.org<br>
<b>Subject:</b> Re: [Trace-users] Demand Controlled Ventilation<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal>Hi Jen,<br>
I agree. That does sound fishy. Generally, I do not use the DCV
control feature within Trace to calc my energy savings from DCV. Some
LEED reviewers have questioned using it as well. It's not that the
algorithm is not correct its just that applying it to a real project can be
tricky and require some level of judgment that the software doesn't know
about. Similarly, I rarely use the ASHRAE 62 calc capabilities in Trace
to simulate that calc. Except of the simplest of situations the calc can
be thrown off very easily. One room can throw off the whole calc, so some
judgment and adjustment is needed ....in my experience, it frequently take more
time to comb through the calcs to figure out which spaces are throwing off the
calc than to estimate the savings via other means. I still estimate both
with in Trace so it doesn't count as an exceptional calculation for LEED but I
don't use Trace's built in routines to do it.<br>
<br>
For DCV, based on the occupancy schedules for the spaces with DCV, I calc and
make an adjusted OA schedule for those spaces. This is actually a lot
less work and easier than it sounds.<br>
Similarly, for the ASHRAE 62 calc, I do it on a spreadsheet and then force that
cfm value at the system level in Trace (System level, Options Tab, Advanced
options button). If you have a VAV system that needs an ASHRAE 62 calc
and you are using DCV in some spaces, then you will need to adjust the system
level OA schedule to reflect the DCV. <br>
<br>
You can check to see that the program is bringing the correct OA cfm and adjust
the schedule as needed by reviewing the cfms via the View Reports, Analysis
tab, Graph Profiles and Energy button. Once there, In the view menu, turn
on the "settings" menu and switch to the "table"
view. Then you can navigate the settings on the left side of the screen
to get Trace to display the cfms of the AHU/system(s) in question. (You
could also use this viewing feature to review what Trace did with the OA cfm
when you used the automatic DCV and/or ASHRAE 62 calc within Trace to help find
clues as to what's going on and if indeed Trace is simulating those features
and the OA cfm correctly). <br>
<br>
Again, the manual adjusted schedules and forced cfm method may sound difficult
and like a lot of work, but it's not really. Once you do it once, you're
done. And, it gives you a confidence level that Trace is simulating the
OA cfm correctly. <br>
<br>
Hope that helps.<br>
Julia<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-family:"Tahoma","sans-serif"'>
<hr size=1 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-family:
"Tahoma","sans-serif"'>From:</span></b><span style='font-family:"Tahoma","sans-serif"'>
Jen Redington <redington@vitetta.com><br>
<b>To:</b> trace-users@lists.onebuilding.org<br>
<b>Sent:</b> Mon, August 30, 2010 8:15:32 AM<br>
<b>Subject:</b> [Trace-users] Demand Controlled Ventilation</span><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<div>
<p class=MsoNormal><span style='color:black'>I am doing an energy model for
LEED and added demand controlled ventilation to several spaces in both the
design and baseline models. This doubled my energy cost savings for the
project. The space heating gas use went down 25% in the design model but
doubled in the baseline model. I can’t see any reason why the baseline energy
use would increase, and the savings in the design case seem a little
unrealistic since DCV is only being used in some spaces. Any ideas what
could be wrong? Any one else have any similar issues?</span><o:p></o:p></p>
<p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:black'>Thanks,</span><o:p></o:p></p>
<p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:black'>Jen Redington</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>