<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Steve-<br>
<br>
Here is a link to a paper published by PNNL discussing some
guidelines for converting building leakage rates at a known pressure
to energy model infiltration inputs. <br>
<br>
<a class="moz-txt-link-freetext" href="http://www.pnl.gov/main/publications/external/technical_reports/PNNL-18898.pdf">http://www.pnl.gov/main/publications/external/technical_reports/PNNL-18898.pdf</a><br>
<br>
It is written in the context of EnergyPlus, but eQUEST/DOE-2
includes the same infiltration model (AIR-CHANGE ->
AIR-CHANGES/HR). In my experience using this guideline, you'll have
to do some calculations of exterior wall area and perimeter zone
floor area to come up with the correct infiltration inputs for each
SPACE; keyword defaulting can come in handy for this task... Also,
this guideline doesn't go into depth on how to develop infiltration
schedules that reflect the design capacity and control of different
types of ventilation systems. Rather from what I gleaned, the
guideline is simply 1.0 when fans are off, and 0.25 when fans are
on. Finally, keep in mind that DOE-2 calculates a local wind speed
from weather file wind speed and SITE-PARAMETER inputs that describe
characteristics of both the weather station and the terrain local to
the building. These parameters (which I overlooked until
researching these infiltration models), do have an impact on the
calculation of hourly SPACE loads, since the local wind speed
calculation not impacts the wind-dependent infiltration model, but
also exterior (wall and window) film conductance.<br>
<br>
The authors acknowledges that the recommended model addresses only
"wind-driven" infiltration, so if stack-driven flow is a major
component in your building, you may want to figure out a way to
adjust your inputs/schedules to account for this; a combination of
AIR-CHANGES/HR and the other model input, INF-FLOW/AREA, could be
one approach for dealing with this. The DOE-2 Crack model does
attempt to account for stack driven flow, but this model is
sensitive to it's many, component-specific inputs, which are often
difficult to characterize.<br>
<br>
-David<br>
<pre class="moz-signature" cols="72">--
David Reddy
360 Analytics
Building Energy Analysis Consultants
mail: 12354 16th Ave NE, Seattle, WA 98125
office: 206.420.7918
mobile: 206.406.9856
web: <a class="moz-txt-link-abbreviated" href="http://www.360-Analytics.com">www.360-Analytics.com</a></pre>
<br>
<br>
On 4/13/2011 5:39 AM, Steve Burley wrote:
<blockquote
cite="mid:DA08134590DDEC4E88D68AB8122B369EBBBD39@sbs.CSA.local"
type="cite">
<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:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal">As part of the Estidama, the local ABU
Dhabi requirements, we are required to model “building air
leakage rates” on 2l/s/m² at 75Pa. Is it possible to model
this in equest? The help file would suggest so if
AIR-CHANGES/HR is used but this is corrected for wind speed.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Are the corrections held in the P-Inf and
C-Inf (perimeter and core infiltration?) schedules or are they
calculated during the simulation run?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Any help would be gratefully received.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Steve<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Equest-users mailing list
<a class="moz-txt-link-freetext" href="http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org">http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org</a>
To unsubscribe from this mailing list send a blank message to <a class="moz-txt-link-abbreviated" href="mailto:EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</a>
</pre>
</blockquote>
</body>
</html>