<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:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[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 Definitions */
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@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:"Stylus BT";
panose-1:2 14 4 2 2 2 6 2 3 4;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:"MS Shell Dlg";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
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:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
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;
font-size:10.0pt;}
@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:892497259;
mso-list-type:hybrid;
mso-list-template-ids:1459622940 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{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="2050" />
</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='color:#1F497D'>Hey 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'>Attached are some select
conversations I’ve been involved in the past few years on this list –
they cover a range of topics regarding how to handle DOA systems –
recommended reading if you have the time/patience.<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'>As you may have gathered, there are
a few ways to skin the cat when it comes to DOAS in equest. You can boil
them all down to two basic approaches…<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'>Whether you need a dummy/space
zone depends on whether you will be modeling the system as a separate entity.
If you’ll read the attached, you’ll find I’m generally an
advocate of not doing that, but whether this is the way to go is ultimately a gut-check
and dependant on the behavior of the proposed systems you’re trying to
model:<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>Start by determining
exactly when how your DOAS’s fans, ERV components, and separate
pre-conditioning/defrost components (if any), operate. Determine whether
these things operate in sync with any served HVAC equipment or independently.<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>If the DOAS’s
fans and other components operate on largely the same schedule as the associated
other HVAC equipment, I would say to ignore the dummy zone concept and instead “split”
the DOAS into each associated unit (see attached discussion and more in the archives).
<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>If the DOAS operates
under a largely different schedule, or you if you can’t be sure, then I’d
suggest pursuing modeling the system independently, assigned to a dummy zone
(again, read up further on tips regarding dummy zones and how to use OA-FROM-SYSTEM).
If DCV is involved anywhere (CO2 sensors), be especially careful to understand
how that plays into your actual system, and read up on how exactly to deal with
that before getting started.<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'>Hopefully that gets you and
others started… do use the list archives, and ask specific questions if
you hit any deadends. <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'>It may comfort/discomfort you to
know that there’s probably more than one right answer out there ;).<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'>~Nick<o:p></o:p></span></p>
<div>
<p class=MsoNormal><span style='color:#1F497D'><img width=119 height=37
id="Picture_x0020_1" src="cid:image001.jpg@01CBDF52.24E01A50"
alt="cid:489575314@22072009-0ABB"></span><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'><o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'><o:p> </o:p></span></b></p>
<p class=MsoNormal><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'>NICK CATON, E.I.T.</span></b><b><span style='font-size:12.0pt;
font-family:"Stylus BT","sans-serif";color:#2D4D5E'><o:p></o:p></span></b></p>
<p class=MsoNormal><span style='font-size:7.5pt;color:#CC9900'>PROJECT ENGINEER<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>Smith &
Boucher Engineers</span><span style='font-size:7.5pt;font-family:"Times New Roman","serif";
color:#CC9900'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>25501 west
valley parkway<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>olathe ks 66061<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>direct 913
344.0036<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>fax 913
345.0617<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><a href="www.smithboucher.com"
title="blocked::www.smithboucher.com"><span style='font-size:10.0pt'>www.smithboucher.com</span></a></span><u><span
style='font-size:10.0pt;color:blue'> </span></u><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: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"'>
equest-users-bounces@lists.onebuilding.org
[mailto:equest-users-bounces@lists.onebuilding.org] <b>On Behalf Of </b>Brian
Smith<br>
<b>Sent:</b> Thursday, March 10, 2011 5:46 PM<br>
<b>To:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> [Equest-users] quick DOAS help<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Still trying to learn EQuest. For trying to model a DOAS
system I’ve been searching through the Archives and only finding tid bits
here are there (mostly about Dummy Spaces?). I was hoping if someone could take
just a few minutes and bullet some steps for how the best approximate this kind
of system<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks,<o:p></o:p></p>
<p class=MsoNormal>Brian Smith, <span style='font-size:10.0pt'>Mechanical
Design Engineer</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt'>Murray & Associates, P.C.<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:9.0pt'>T/907.780.6151
F/907.780.6182</span><span style='font-size:9.0pt;font-family:"MS Shell Dlg"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt'><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>