<!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: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 = ""><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.5848" name=GENERATOR><!--[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-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Stylus BT;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-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
}
P.MsoAcetate {
FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
LI.MsoAcetate {
FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
DIV.MsoAcetate {
FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
SPAN.BalloonTextChar {
FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text"; mso-style-name: "Balloon Text Char"
}
P.Normal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Arial","sans-serif"; mso-style-name: "[Normal]"
}
LI.Normal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Arial","sans-serif"; mso-style-name: "[Normal]"
}
DIV.Normal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Arial","sans-serif"; mso-style-name: "[Normal]"
}
SPAN.EmailStyle20 {
COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle21 {
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=163040020-25092009><FONT face=Arial
color=#0000ff size=2>I think you can just delete the walls and ceiling and be
okay</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=en-us><FONT face=Arial></FONT></SPAN> <BR><SPAN
lang=en-us><B><FONT face=Arial color=#0000ff size=2>John Grando</FONT><FONT
face=Arial size=2> </FONT><FONT face=Arial color=#0000ff size=2>LEED
AP</FONT></B></SPAN><SPAN lang=en-us><BR></SPAN><BR><SPAN lang=en-us><FONT
face=Arial> </FONT></SPAN> </P>
<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>Nick
Caton<BR><B>Sent:</B> Friday, September 25, 2009 3:58 PM<BR><B>To:</B>
equest-users@lists.onebuilding.org<BR><B>Subject:</B> [Equest-users] DOAS Dummy
Warnings - no problem?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">Hi
everyone,<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">I’ve got what I believe to be a
working preliminary model of a DOAS system. I’m following the DOAS concept
(prescribed by previous archived discussions) of creating a “dummy zone/shell”
to be served by the DOAS equipment. All terminal units are tied to the
DOAS via <U>OA-FROM-SYSTEM</U>. My DOAS is based on the system type SZRH
(“Single Zone Air Handler with HW reheat”). <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">This DOAS is assigned to a
1ft-cube “dummy shell” with a single zone, adiabatic ceiling/floor
constructions, wall constructions of U=.0001, and zeroed-out internal
loads. Conceptually, I believe the airflow for the DOAS should be
calculated as the hourly sum of all the terminal unit’s calculated OA
needs. <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">I’ve got three basic questions,
presented in order of (perceived) difficulty:<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">QUESTION
1)<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">As I’ve set my “dummy” zone’s
walls to U=0.0001, and of physically tiny dimensions, I don’t think there’s much
to worry about regarding heat gains/losses. In the interest of doing the
intuitively “right” thing however, is there a way to set their “surface type” as
adiabatic in the same way as roof and floor surfaces? Is perhaps the
cleanest way to deal with all three to create “adiabatic” constructions, and if
so how do you get around the error (see attached image) when you input
U=0?<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">QUESTION 2)
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">Every system (DOAS and terminal
units) currently has the <U>MIN-OA-METHOD</U> set as <U>FRACTION-OF-DESIGN</U>,
per the warning below. In reality, the hourly OA supplied by the DOAS will
be calculated by summing what is being called for by all of the terminal units,
which will be based on local DCV sensors in the return air path of each unit.
Unfortunately, setting any of the terminal units’ <U>MIN-OA-METHOD</U> to
the intuitive <U>DCV-RETURN-SENSOR</U> results in the following warning (typical
for each system):<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'">**WARNING**********************************************************************<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'">
EL1 Sys1 (FC)
(G.N1)
has a MIN-AIR-SCH, OA-CONTROL<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'">
other than FIXED and/or a MIN-OA-METHOD other than
FRACTION-OF-DESIGN<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'">
along with having a specified OA-FROM-SYSTEM. This may cause
incorrect<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'">
OA load/flow calculation for its OA-FROM-SYSTEM.<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">I’ve gathered that one approach
to this problem is to manually define the design airflow of the DOAS, based on
summing the critical case of OA required by digging through the reports (not
sure where to begin there), but is there any way of tricking eQuest into
correctly summing the hourly OA CFM required by all terminal units tied to the
DOAS, and then sizing the DOAS system based on that critical
sum?<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">QUESTION
3)<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">The following are the remaining
3 warnings, all referring to this “dummy zone</SPAN><SPAN
style="COLOR: #1f497d">:”</SPAN><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=Normal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'">**WARNING**********************************************************************<o:p></o:p></SPAN></P>
<P class=Normal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'">
Zone: EL2 Zn
(G.1)
has a design cooling<o:p></o:p></SPAN></P>
<P class=Normal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'">
temperature differential of only 1.0F. This<o:p></o:p></SPAN></P>
<P class=Normal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'">
may result in an extremely large design airflow.<o:p></o:p></SPAN></P>
<P class=Normal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'"><o:p> </o:p></SPAN></P>
<P class=Normal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'"> **WARNING**********************************************************************<o:p></o:p></SPAN></P>
<P class=Normal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'">
Zone: EL2 Zn
(G.1)
has a design heating<o:p></o:p></SPAN></P>
<P class=Normal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'">
temperature differential of only -1.0F. This<o:p></o:p></SPAN></P>
<P class=Normal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'">
may result in an extremely large design airflow.<o:p></o:p></SPAN></P>
<P class=Normal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'"><o:p> </o:p></SPAN></P>
<P class=Normal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'"> **WARNING**********************************************************************<o:p></o:p></SPAN></P>
<P class=Normal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'">
ZONE EL2 Zn
(G.1)
<o:p></o:p></SPAN></P>
<P class=Normal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'">
might have insufficient heating capability.<o:p></o:p></SPAN></P>
<P class=Normal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'">
Check that the SYSTEM or ZONE HEATING-CAPACITY plus this<o:p></o:p></SPAN></P>
<P class=Normal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'">
ZONEs BASEBOARD-RATING is adequate to maintain the ZONE<o:p></o:p></SPAN></P>
<P class=Normal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'">
specified DESIGN-HEAT-T for the calculated peak ZONE load<o:p></o:p></SPAN></P>
<P class=Normal><SPAN
style="FONT-SIZE: 8pt; COLOR: #c0504d; FONT-FAMILY: 'Courier New'">
(see LS-A or LS-B for the ZONE peak load.)<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">Which (if any) of these I should
be addressing/evaluating, considering the modeling function of this “dummy
zone?” In other words, can I ignore these and sleep well at night?
=)<o:p></o:p></SPAN></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><IMG id=Picture_x0020_1 height=37
alt=cid:489575314@22072009-0ABB src="cid:163040020@25092009-27E3"
width=119><B><SPAN
style="COLOR: #2d4d5e; FONT-FAMILY: 'Stylus BT','sans-serif'"><o:p></o:p></SPAN></B></P>
<P class=MsoNormal><B><SPAN
style="COLOR: #2d4d5e; FONT-FAMILY: 'Stylus BT','sans-serif'"><o:p> </o:p></SPAN></B></P>
<P class=MsoNormal><B><SPAN
style="COLOR: #2d4d5e; FONT-FAMILY: 'Stylus BT','sans-serif'">NICK CATON,
E.I.T.</SPAN></B><B><SPAN
style="FONT-SIZE: 12pt; COLOR: #2d4d5e; FONT-FAMILY: 'Stylus BT','sans-serif'"><o:p></o:p></SPAN></B></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 7.5pt; COLOR: #cc9900">PROJECT
ENGINEER</SPAN><SPAN
style="FONT-SIZE: 7.5pt; COLOR: #cc9900; FONT-FAMILY: 'Times New Roman','serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #2d4d5e">25501 west
valley parkway<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #2d4d5e">olathe ks
66061<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #2d4d5e">direct 913
344.0036<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #2d4d5e">fax 913
345.0617<o:p></o:p></SPAN></P>
<P class=MsoNormal><I><SPAN style="FONT-SIZE: 10pt; COLOR: #2d4d5e">Check out
our new web-site @ </SPAN></I><SPAN style="COLOR: #1f497d"><A
title=blocked::www.smithboucher.com href="www.smithboucher.com"><SPAN
style="FONT-SIZE: 10pt">www.smithboucher.com</SPAN></A></SPAN><U><SPAN
style="FONT-SIZE: 10pt; COLOR: blue"> </SPAN></U><SPAN
style="COLOR: #1f497d"><o:p></o:p></SPAN></P>
<P class=MsoNormal><o:p> </o:p></P></DIV><br clear=all> NOTICE OF CONFIDENTIALITY
This E-mail message and its attachments (if any) are intended solely for the use of the addressees hereof. In addition, this message and the attachments (if any) may contain information that is confidential, privileged and exempt from disclosure under applicable law. If you are not the intended recipient of this message, you are prohibited from reading, disclosing, reproducing, distributing, disseminating or otherwise using this transmission. Delivery of this message to any person other than the intended recipient is not intended to waive any right or privilege. If you have received this message in error, please promptly notify the sender by reply E-mail and immediately delete this message from your system.
</BODY></HTML>