<!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 content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19019"><!--[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: Wingdings;
}
@font-face {
font-family: Wingdings;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Verdana;
}
@font-face {
font-family: MS Shell Dlg;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
LI.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
DIV.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
H5 {
FONT-FAMILY: "Times New Roman","serif"; MARGIN-LEFT: 0in; FONT-SIZE: 10pt; MARGIN-RIGHT: 0in; mso-style-priority: 9; mso-style-link: "Heading 5 Char"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
P.MsoBodyText {
FONT-FAMILY: "Times New Roman","serif"; MARGIN-LEFT: 0in; FONT-SIZE: 12pt; MARGIN-RIGHT: 0in; mso-style-priority: 99; mso-style-link: "Body Text Char"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
LI.MsoBodyText {
FONT-FAMILY: "Times New Roman","serif"; MARGIN-LEFT: 0in; FONT-SIZE: 12pt; MARGIN-RIGHT: 0in; mso-style-priority: 99; mso-style-link: "Body Text Char"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
DIV.MsoBodyText {
FONT-FAMILY: "Times New Roman","serif"; MARGIN-LEFT: 0in; FONT-SIZE: 12pt; MARGIN-RIGHT: 0in; mso-style-priority: 99; mso-style-link: "Body Text Char"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
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 {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
LI.MsoAcetate {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
DIV.MsoAcetate {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; FONT-SIZE: 8pt; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
P.MsoListParagraph {
MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt; mso-style-priority: 34
}
LI.MsoListParagraph {
MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt; mso-style-priority: 34
}
DIV.MsoListParagraph {
MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt; mso-style-priority: 34
}
SPAN.EmailStyle17 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: personal
}
SPAN.EmailStyle18 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal-reply
}
SPAN.BalloonTextChar {
FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text"; mso-style-name: "Balloon Text Char"
}
SPAN.Heading5Char {
FONT-WEIGHT: bold; mso-style-priority: 9; mso-style-link: "Heading 5"; mso-style-name: "Heading 5 Char"
}
SPAN.BodyTextChar {
mso-style-priority: 99; mso-style-link: "Body Text"; mso-style-name: "Body Text Char"
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.WordSection1 {
page: WordSection1
}
OL {
MARGIN-BOTTOM: 0in
}
UL {
MARGIN-BOTTOM: 0in
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050">
<o:colormenu v:ext="edit" fillcolor="none" strokecolor="#c00000" />
</o:shapedefaults></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 dir=ltr align=left><SPAN class=834305816-30032011><FONT color=#0000ff
size=2 face=Arial>I would also add here that you can sign the OA for the
system either based on "Sum of Zone OA" or "Set by Critical
Zone".</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=834305816-30032011><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=834305816-30032011><FONT color=#0000ff
size=2 face=Arial>When you size using "Set by Critical Zone" the system OA will
be greater than the sum of the zone OA requirements to compensate for the
diversity in the OA requirements of the zones.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=834305816-30032011><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=834305816-30032011><FONT color=#0000ff
size=2 face=Arial>Kamel Haddad</FONT></SPAN></DIV>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left><SPAN
class=834305816-30032011><FONT color=#0000ff size=2
face=Arial> </FONT></SPAN></DIV>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left><SPAN
class=834305816-30032011> </SPAN></DIV>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
</DIV>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left><FONT size=2
face=Tahoma><B>From:</B> equest-users-bounces@lists.onebuilding.org
[mailto:equest-users-bounces@lists.onebuilding.org] <B>On Behalf Of </B>Jeremy
Poling<BR><B>Sent:</B> March 30, 2011 12:38<BR><B>To:</B> brians@murraypc.com;
equest-users@lists.onebuilding.org<BR><B>Subject:</B> Re: [Equest-users]
Modeling DOAS with a dummy zone<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">Brian,<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">First: here’s what the help file
says about how the system comes up with OSA flows:<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Times New Roman','serif'; BACKGROUND: #316ac5; COLOR: white; FONT-SIZE: 10pt">OA-FROM</SPAN></B><B><SPAN
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 10pt">-SYSTEM<o:p></o:p></SPAN></B></P>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt">Takes the U-name
of the system that supplies dehumidified make-up air either directly, or through
the corridor, to apartments or hotel rooms. Make sure that minimum outside air
of a make-up air system assigned to the corridor matches the sum of the minimum
outside air flow rate of the apartments or hotel rooms. In the input, define the
make-up air system prior to the apartment or hotel room system. Several Error
and Warning messages are present to prevent incorrect simulations and only
simple sizing calculations are available for <SPAN
style="BACKGROUND: #316ac5; COLOR: white">OA-FROM</SPAN>-SYSTEM referenced
SYSTEMs. In previous versions of DOE-2.2 (before 44c) and 2.1E, if a
SYSTEM had an <SPAN
style="BACKGROUND: #316ac5; COLOR: white">OA-FROM</SPAN>-SYSTEM specified, the
referencing SYSTEM value for MIN-OUTSIDE-AIR was reset to the MIN-OUTSIDE-AIR of
the referenced <SPAN
style="BACKGROUND: #316ac5; COLOR: white">OA-FROM</SPAN>-SYSTEM; this has been
removed and replaced with the action as described next. The sum of the <SPAN
style="BACKGROUND: #316ac5; COLOR: white">OA</SPAN> requirements for all SYSTEMs
that reference an <SPAN
style="BACKGROUND: #316ac5; COLOR: white">OA-FROM</SPAN>-SYSTEM is used to set
the referenced <SPAN
style="BACKGROUND: #316ac5; COLOR: white">OA-FROM</SPAN>-SYSTEM value for
MIN-OUTSIDE-AIR, SUPPLY-FLOW as well as adjust the referenced <SPAN
style="BACKGROUND: #316ac5; COLOR: white">OA-FROM</SPAN>-SYSTEM directly served
ZONE maximum and minimum flows for both heating and cooling. Additionally
the referenced <SPAN
style="BACKGROUND: #316ac5; COLOR: white">OA-FROM</SPAN>-SYSTEM has its
calculated/specified cooling (total and sensible), heating, and preheat
capacities adjusted if its SUPPLY-FLOW was increased. If the referenced
<SPAN style="BACKGROUND: #316ac5; COLOR: white">OA-FROM</SPAN>-SYSTEM and its
ZONEs have sufficient minimum <SPAN
style="BACKGROUND: #316ac5; COLOR: white">OA</SPAN> specified (greater than that
required by the referencing SYSTEMs) no adjustments are made. If any
adjustments are made a warning is issued that informs the user of the
adjustments and recommends the project be re-run with the values in the input
corrected. Also, errors are issued (and the simulation terminated) if the
referenced <SPAN style="BACKGROUND: #316ac5; COLOR: white">OA-FROM</SPAN>-SYSTEM
is either an incorrect type (a zonal system or a system that cannot have outside
air) or the referenced <SPAN
style="BACKGROUND: #316ac5; COLOR: white">OA-FROM</SPAN>-SYSTEM is not placed
into the input file before all referencing SYSTEMs.<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"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">There could also be a couple of
places causing the system OSA to exceed the sum of the zone OSA for each system,
depending on how you set the model up:<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P style="TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1"
class=MsoListParagraph><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol; COLOR: #1f497d"><SPAN
style="mso-list: Ignore">-<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN style="COLOR: #1f497d">If your project has
a specified elevation greater than 0 then eQuest will be correcting airflows for
elevation. ASHRAE Fundamentals directs that if you’re less than 1,000 ft
above sea level you can usually ignore elevation effects on CFM values,
therefore if that applies you can zero out that value (see
below)<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P style="MARGIN-LEFT: 0.5in" class=MsoNormal><!--[if gte vml 1]><v:rect id="_x0000_s1027" style='position:absolute;left:0;text-align:left;margin-left:66.75pt;margin-top:149.3pt;width:167.25pt;height:19.5pt;z-index:2' filled="f" strokecolor="#c00000" strokeweight="6pt" /><![endif]--><![if !vml]><SPAN
style="Z-INDEX: 2; POSITION: absolute; MARGIN-TOP: 195px; WIDTH: 231px; HEIGHT: 35px; MARGIN-LEFT: 85px; LEFT: 0px; mso-ignore: vglayout"><IMG
src="cid:834305816@30032011-083C" width=231 height=35
v:shapes="_x0000_s1027"></SPAN><![endif]><IMG id=Picture_x0020_1
src="cid:834305816@30032011-0843" width=542 height=408><SPAN
style="COLOR: #1f497d"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P style="TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1"
class=MsoListParagraph><![if !supportLists]><SPAN
style="FONT-FAMILY: Symbol; COLOR: #1f497d"><SPAN
style="mso-list: Ignore">-<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN></SPAN><![endif]><SPAN style="COLOR: #1f497d">If you’re looking at
the proposed model, make sure you don’t have any sizing factors in place for the
system (unless you intend to run the calculations that
way).<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P style="MARGIN-LEFT: 0.5in" class=MsoNormal><!--[if gte vml 1]><v:rect id="_x0000_s1026" style='position:absolute;left:0;text-align:left;margin-left:66.75pt;margin-top:276.05pt;width:167.25pt;height:19.5pt;z-index:1' filled="f" strokecolor="#c00000" strokeweight="6pt" /><![endif]--><![if !vml]><SPAN
style="Z-INDEX: 1; POSITION: absolute; MARGIN-TOP: 364px; WIDTH: 231px; HEIGHT: 35px; MARGIN-LEFT: 85px; LEFT: 0px; mso-ignore: vglayout"><IMG
src="cid:834305816@30032011-083C" width=231 height=35
v:shapes="_x0000_s1026"></SPAN><![endif]><SPAN style="COLOR: #1f497d"><IMG
id=Picture_x0020_2 src="cid:834305816@30032011-084A" width=1052
height=658></SPAN><SPAN style="COLOR: #1f497d"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<DIV>
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: #1f497d; FONT-SIZE: 7.5pt">Jeremy
R. Poling, PE, LEED AP+BDC</SPAN></B><SPAN
style="COLOR: #1f497d"><BR><BR></SPAN><SPAN
style="COLOR: #1f497d"><o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">
equest-users-bounces@lists.onebuilding.org
[mailto:equest-users-bounces@lists.onebuilding.org] <B>On Behalf Of </B>Brian
Smith<BR><B>Sent:</B> Wednesday, March 30, 2011 11:13 AM<BR><B>To:</B>
equest-users@lists.onebuilding.org<BR><B>Subject:</B> [Equest-users] Modeling
DOAS with a dummy zone<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">Thanks for your replays to my
email, it was very much appreciated. I tried modeling the doas system with a
dummy zone and OA from system. While looking at my Air side reports I found that
the DOAS system OSA equaled the sum OSA from each zone in each system (fine
that’s logical). But each system has its own OSA total which is larger than the
sum of OSA requirements of its zones (not sure why). Whether I model a doas
dummy or not the individual system still require the same amount of OSA.
Therefore with the dummy air totals added to the system air totals my building
needs more OSA and consumes more BTU’s. Not sure what all this means but It
would seem bad? Any insights, does this sound right? This makes me think if I
could eliminate this Dummy Doas system and zones, and work in the components of
DOAS into the other systems I would at least find a different result, but
right?<o:p></o:p></SPAN></P>
<P class=MsoNormal><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>Brian Smith, <SPAN style="FONT-SIZE: 10pt">Mechanical Design
Engineer</SPAN><o:p></o:p></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt">Murray & Associates,
P.C.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 9pt">T/907.780.6151
F/907.780.6182</SPAN><SPAN
style="FONT-FAMILY: 'MS Shell Dlg'; FONT-SIZE: 9pt"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 9pt"><A
href="www.murraypc.com">www.murraypc.com</A><o:p></o:p></SPAN></P>
<P class=MsoNormal><o:p> </o:p></P></DIV></BODY></HTML>