<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=iso-8859-1">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
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.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.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1558395993;
mso-list-type:hybrid;
mso-list-template-ids:-176099174 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
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=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Sasa, <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'>In response to your query I’ve provide some comments in
the same order.<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=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>1)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>TRACE cannot credibly model a double skin façade. Any
reasonable reviewer should challenge the use of this software in this
application (it has many strengths that can serve you elsewhere). There are
other tools that would be more appropriate such as Energy+, IES-VE, TRNSYS, and
various combinations of these using bulk air flow models in conjunction (we’ve
even used CONTAM, TRNSYS, eQUEST together).<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>2)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>You’re probably best off modeling the PV window as a window
using its published performance values (SHGC, u-value, Tvis) and using another
tool to assess the output of the PV, which can be easily applied in the LEED
template as a renewable energy credit.<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>3)<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>You should definitely not treat the typical floor as a single
zone. This is not an appropriate way to model a typical high rise. You can
simplify based on zone/space characteristics, but distinct thermal zone types
(space utilization, perimeter vs core, orientation) should be modeled
separately. What you may choose to do would be to model the ground floor, top
floor, and typical floors in between, with each of the same type of typical floor
zone areas modeled together (i.e. all west façade perimeter office zones
modeled as one very long floor area and wall area, all interior restrooms
modeled as one large restroom, etc.). This is possible since TRACE is
non-geometric. However, I would go back to my response to #1 if a double skin façade
is being incorporated into the design.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><br>
Regards,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Paul <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>
<table class=MsoNormalTable border=0 cellpadding=0 width=474 style='width:355.5pt'>
<tr>
<td width=167 valign=top style='width:125.25pt;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#660000;
text-transform:uppercase'>Paul Erickson</span></b><b><span style='font-size:
9.0pt;font-family:"Calibri","sans-serif";color:#333333'> </span></b><span
style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#333333'>LEED®
AP <br>
</span><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#1F497D;text-transform:uppercase'>Sustainable Practice Leader</span><span
style='font-size:9.0pt;font-family:"Calibri","sans-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><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";
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='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#660000'>AEI</span></b><span
style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#333333'> |
AFFILIATED ENGINEERS, INC. <br>
5802 Research Park Blvd. | Madison, WI 53719<br>
<br>
</span><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";
color:#660000'>P: 608.236.1112 | F: 608.238.2614</span><span
style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#333333'> <br>
</span><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";
color:#660000'><a href="mailto:perickson@aeieng.com"><span style='color:#660000;
text-decoration:none'>perickson@aeieng.com</span></a> | </span><b><span
style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#660000'><a
href="http://www.aeieng.com"><span style='color:#660000;text-decoration:none'>www.aeieng.com</span></a></span></b><span
style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#333333'>
<o:p></o:p></span></p>
</td>
</tr>
</table>
<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'><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"'>
bldg-sim-bounces@lists.onebuilding.org
[mailto:bldg-sim-bounces@lists.onebuilding.org] <b>On Behalf Of </b>Sasa Pantic<br>
<b>Sent:</b> Monday, November 16, 2009 10:13 AM<br>
<b>To:</b> Bldg-sim_2<br>
<b>Subject:</b> [Bldg-sim] TRACE-double facade and PV systems?<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0>
<tr>
<td valign=top style='padding:0in 0in 0in 0in'>
<p class=MsoNormal style='margin-bottom:12.0pt'>Dear all,<br>
<br>
I would kindly ask for an information please regarding TRACE v. 4.1.1; v
6.2.4<br>
<br>
1) How can I trick TRACE to handle double facades with an imposed airflow in
the air gap?<br>
2) Any idea on how to model semi transparent PV window along with electricity
generated?<br>
3) Any general advise on modeling 56 story building using TRACE
for LEED compliance in EA section? e.g. should I consider zone-by-zone
approach with defining all envelope, HVAC systems or treat typical floor as a
single zone , perhaps?<br>
<br>
<br>
Any feedback is greatly appreciated.<br>
Thanks, Sasa<o:p></o:p></p>
</td>
</tr>
</table>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p>
</div>
</body>
</html>