<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" 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:ds =
"http://www.w3.org/2000/09/xmldsig#" xmlns:xsi =
"http://www.w3.org/2001/XMLSchema-instance" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3492" name=GENERATOR>
<STYLE>@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Verdana;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: "Arial","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle18 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
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 vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=596362817-27082009><FONT face=Arial
color=#0000ff size=2>I've definitely noticed the anomaly, and I have definitely
had a difficult time running loads because of it.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=596362817-27082009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=596362817-27082009><FONT face=Arial
color=#0000ff size=2>The way I have compensated for this is by assigning a
temperature set point to the plenum. eQuest seems to not consider any load going
across the roof and into space because it seems that the entire roof load is
assigned to the return air stream for the "Loads" portion of DOE2. If the
plenum is the same temperature as the space, no heat transfer can occur,
obviously.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=596362817-27082009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=596362817-27082009><FONT face=Arial
color=#0000ff size=2>By assigning the plenum a temperature, however, eQuest does
calculate heat gain/loss and such gain/loss is shown on the loads report as an
adjacent surface but NOT roof load. I've actually setup parametric runs where a
different plenum temperature is used each month based upon a calculation that I
run outside of eQuest calculating my plenum temp considering the roofing
materials and amount of return air passing through the plenum. I've also
included in my estimate how much heat comes off the lights. It seems to me
to be the only work-around to this rather mysterious problem, and makes running
loads in eQuest very convoluted, IMHO.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=596362817-27082009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=596362817-27082009><FONT face=Arial
color=#0000ff size=2>In short, with roof load being assigned to the return air,
the only way you can account for a roof load in a space load calc is to tell
eQuest what temperature the plenum is. You have to do that outside of eQuest,
unless somebody has figured out a way to do it another way.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=596362817-27082009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=596362817-27082009><FONT face=Arial
color=#0000ff size=2>Thanks,</FONT></SPAN></DIV>
<DIV class=Section1>
<P style="MARGIN: 0in 0in 0pt"><B><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana">Gary</SPAN></B><B><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana"> Schrader</SPAN></B><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana"> <BR>Engineer I<BR><BR><B>TAC</B>
<BR>16011 College Boulevard, Suite 212<BR>Lenexa, KS 66219</SPAN></P>
<P style="MARGIN: 0in 0in 0pt"><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana"></SPAN> </P>
<TABLE class=MsoNormalTable cellSpacing=0 cellPadding=0 border=0>
<TBODY>
<TR>
<TD
style="PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; PADDING-TOP: 0in">
<P class=MsoNormal><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana">Direct:</SPAN></P></TD>
<TD
style="PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; PADDING-TOP: 0in">
<P class=MsoNormal><SPAN style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana">+1
</SPAN></P></TD></TR>
<TR>
<TD
style="PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; PADDING-TOP: 0in">
<P class=MsoNormal><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana">Fax:</SPAN></P></TD>
<TD
style="PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; PADDING-TOP: 0in">
<P class=MsoNormal><SPAN style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana">+1
913-469-0206</SPAN></P></TD></TR>
<TR>
<TD
style="PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; PADDING-TOP: 0in">
<P class=MsoNormal><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana">Mobile</SPAN><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana">:</SPAN></P></TD>
<TD
style="PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; PADDING-TOP: 0in">
<P class=MsoNormal><SPAN style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana">+1
913-217-8068</SPAN></P></TD></TR>
<TR>
<TD
style="PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; PADDING-TOP: 0in">
<P class=MsoNormal><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana">Email:</SPAN></P></TD>
<TD
style="PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; PADDING-TOP: 0in">
<P class=MsoNormal><SPAN style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana"><A
href="mailto:Gary.Schrader@tac.com">Gary.Schrader@tac.com</A></SPAN></P></TD></TR>
<TR>
<TD
style="PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; PADDING-TOP: 0in">
<P class=MsoNormal><SPAN
style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana">Web:</SPAN></P></TD>
<TD
style="PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; PADDING-TOP: 0in">
<P class=MsoNormal><SPAN style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana"><A
href="http://www.tac.com/">www.tac.com</A></SPAN></P></TD></TR></TBODY></TABLE>
<P class=MsoNormal><B><I><SPAN style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana">TAC
is becoming Schneider Electric on October 1, 2009</SPAN></I></B></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana">Notice:
This email message, together with any attachments, contains information of TAC,
which may be confidential, proprietary, copyrighted and/or legally privileged.
This email is intended solely for the use of the individual or entity named on
the message. If you are not the intended recipient, and have received this
message in error, please immediately return by email and then delete
it.</SPAN></P></DIV>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> equest-users-bounces@lists.onebuilding.org
[mailto:equest-users-bounces@lists.onebuilding.org] <B>On Behalf Of </B>Craig
Simmons<BR><B>Sent:</B> Thursday, August 27, 2009 12:20 PM<BR><B>To:</B>
equest-users@lists.onebuilding.org<BR><B>Subject:</B> Re: [Equest-users] Roof
Conduction - Where are you?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">I
recently noticed this as well and decided to revive this thread to see if anyone
has insight. How do the roof conduction loads translate to HVAC
loads?<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Based
on the models I’ve run it’s obvious that roof conduction is being accounted for
on the HVAC side and it appears to be about the right magnitude. However, added
roof conduction loads to the plenum do not translate to any added space loads
or building loads in the LS-x reports. Does anyone have insight on how
eQuest is handling them and why they do not show up in space or building loads
reports?<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Thank
you in advance.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Craig
Simmons, LEED AP<o:p></o:p></SPAN></P>
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 9pt; COLOR: green; FONT-FAMILY: 'Verdana','sans-serif'">The
Green Engineer, LLP</SPAN></B><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> Eckwahl, Tom
[mailto:TEckwahl@karpinskieng.com] <BR><B>Sent:</B> Thursday, July 23, 2009 9:29
AM<BR><B>To:</B> equest-users@lists.onebuilding.org<BR><B>Subject:</B>
[Equest-users] Roof Conduction - Where are
you?<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">My baseline building
energy usage is much lower than expected and in trying to track down the cause
I’ve found that the “Building Peak Load Components” lists no roof heat gain or
heat loss. I did find that there is a gain/loss located in the upper floor
plenum and it’s shown in the “Space Peak Load Components”.
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Is the plenum not
considered part of the building? I’m concerned that the plenum walls and
roof are not being included in the energy modeling run.<o:p></o:p></SPAN></P>
<P class=MsoNormal
style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN lang=EN
style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Arial','sans-serif'">Thomas
N. Eckwahl<BR>Project Engineer, Mechanical</SPAN><SPAN lang=EN
style="COLOR: navy"><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt; mso-margin-top-alt: auto"><SPAN
lang=EN
style="FONT-SIZE: 13.5pt; COLOR: red; FONT-FAMILY: 'Arial','sans-serif'">karpinski<BR></SPAN><SPAN
lang=EN
style="FONT-SIZE: 7.5pt; COLOR: black; FONT-FAMILY: 'Arial','sans-serif'">ENGINEERING</SPAN><o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P></DIV></BODY></HTML>