<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: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="" 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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
/* 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.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
p.Normal, li.Normal, div.Normal
{mso-style-name:"\[Normal\]";
margin:0in;
margin-bottom:.0001pt;
text-autospace:none;
font-size:12.0pt;
font-family:"Arial","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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:259486692;
mso-list-type:hybrid;
mso-list-template-ids:-1062843460 1444972636 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;
mso-fareast-font-family:"MS Mincho";
mso-bidi-font-family:"Times New Roman";}
@list l1
{mso-list-id:1275139636;
mso-list-type:hybrid;
mso-list-template-ids:-1393263906 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1: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'>I am revisiting this model and
never received a response, and I see another has run into the same warnings.
Reposting/rephrasing for any suggestions/input:<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'>In hindsight perhaps I can
phrase a simpler set of questions:<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:l1 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]><u><span style='color:#1F497D'>True or False</span></u><span
style='color:#1F497D'>: Is it simply impossible in eQuest to simultaneously use
OA-FROM-SYSTEM and either of the DCV ventilation control methods with the same
system. This appears to be the case.<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 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'>Based on #1, I seem
to be stuck being unable to modeling the savings from DCV at the zonal level (instead
forced to use fraction of design or the like for my min-OA method)…
<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.25in;text-indent:.25in'><span
style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='color:#1F497D'>But I’ve
got a crazy idea: For an alternative way to force DCV behavior, might I
define a set of MIN-AIR-SCHEDULE’s, using the zonal occupancy schedules
as a template, and multiply each fractional occupancy rate by the designed OA
ratio? This would be tied to an assumption that the C02 levels rise and
fall instantaneously with the occupancy, which I know is not true but may be an
acceptable approximation given #1.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><u><span style='color:#1F497D'>Example:</span></u><span
style='color:#1F497D'> A classroom has a daily schedule that looks like
this (this is for evening classes, if this looks odd):<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><i><span style='color:#1F497D'>"General
Classroom Occup Mon-Thu" = DAY-SCHEDULE-PD<o:p></o:p></span></i></p>
<p class=MsoNormal style='margin-left:.5in'><i><span style='color:#1F497D'>
TYPE =
FRACTION<o:p></o:p></span></i></p>
<p class=MsoNormal style='margin-left:.5in'><i><span style='color:#1F497D'>
VALUES = ( <b>0</b>,
&D, &D, &D, &D, &D, <b>0.2</b>, &D, &D, &D,
&D, &D, &D, <o:p></o:p></span></i></p>
<p class=MsoNormal style='margin-left:.5in'><i><span style='color:#1F497D'>
&D, &D, &D, <b>0.6</b>, <b>1</b>, &D, &D, &D, &D, <b>0.5</b>,
<b>0</b> )<o:p></o:p></span></i></p>
<p class=MsoNormal style='margin-left:.5in'><i><span style='color:#1F497D'>
..<o:p></o:p></span></i></p>
<p class=MsoNormal style='margin-left:.5in'><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='color:#1F497D'>With
the design OA flow being 60% of the design Supply Air flow for that terminal
unit, I create a new MIN-AIR-SCHEDULE multiplying through:<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><i><span style='color:#1F497D'>"General
Classroom MinAir Mon-Thu" = DAY-SCHEDULE-PD<o:p></o:p></span></i></p>
<p class=MsoNormal style='margin-left:.5in'><i><span style='color:#1F497D'>
TYPE =
FRACTION<o:p></o:p></span></i></p>
<p class=MsoNormal style='margin-left:.5in'><i><span style='color:#1F497D'>
VALUES = ( <b>0</b>,
&D, &D, &D, &D, &D, </span></i><b><i><span
style='color:red'>0.12</span></i></b><i><span style='color:#1F497D'>, &D,
&D, &D, &D, &D, &D, <o:p></o:p></span></i></p>
<p class=MsoNormal style='margin-left:.5in'><i><span style='color:#1F497D'>
&D, &D, &D, </span></i><b><i><span style='color:red'>0.36</span></i></b><i><span
style='color:#1F497D'>, </span></i><b><i><span style='color:red'>0.60</span></i></b><i><span
style='color:#1F497D'>, &D, &D, &D, &D, </span></i><b><i><span
style='color:red'>0.30</span></i></b><i><span style='color:#1F497D'>, <b>0</b>
)<o:p></o:p></span></i></p>
<p class=MsoNormal style='margin-left:.5in'><i><span style='color:#1F497D'>
..<o:p></o:p></span></i></p>
<p class=MsoNormal style='margin-left:.5in'><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='color:#1F497D'>For
this approach I would tightly control the OA present at each zone specifying
MIN-OUTSIDE-AIR and clearing out the zonal-level OA inputs.<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'>For reference - The system I am
trying to model is:<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-family:Symbol;color:#1F497D'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>Dedicated outside
air unit – HW/CHW coils, enthalpy recovery wheel, variable supply which effectively
sums the terminal fan coil’s call for OA over time. Conditioned OA
is supplied to VAV’s which modulate based on the terminal fan-coil’s
DCV sensor.<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-family:Symbol;color:#1F497D'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>Terminal units of
widely varying size: 4-pipe HW/CHW coils which handle essentially all the
internal/envelope loads, constant volume, local thermostat controlled, conditioned
OA from dedicated OA units ties into supply ductwork (not seen by the terminal fan
coil units). OA is modulated down to zero based on a CO2 sensor in return
path.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>For reference – I’m
trying to model the above using:<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-family:Symbol;color:#1F497D'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>Single Zone Reheat (SZRH)
for the DOAS, tied to a dummy zone<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-family:Symbol;color:#1F497D'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>4-pipe Fan Coil (FC)
for the terminal units, system per zone, 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'>~Nick<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span style='color:#1F497D'><img width=119 height=37
id="_x0000_i1026" src="cid:image001.jpg@01CACA10.D31B0010"
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</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><i><span style='font-size:10.0pt;color:#2D4D5E'>Check out
our new web-site @ </span></i><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>
<div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;
padding:0in 0in 1.0pt 0in'>
<p class=MsoNormal style='border:none;padding:0in'><span style='color:#1F497D'><o:p> </o:p></span></p>
</div>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<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>Jacob
Goodman<br>
<b>Sent:</b> Friday, December 18, 2009 3:24 PM<br>
<b>To:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> Re: [Equest-users] DOAS Dummy Warnings - no problem?<o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I saw your question on the warnings from your DOAS model and
didn't see any replies. I have some of those same warnings. <br>
<br>
**WARNING**********************************************************************<br>
EL1
Sys1 (PVVT) (G.SW1) has a
MIN-AIR-SCH, OA-CONTROL<br>
other
than FIXED and/or a MIN-OA-METHOD other than FRACTION-OF-DESIGN<br>
along
with having a specified OA-FROM-SYSTEM. This may cause incorrect<br>
OA
load/flow calculation for its OA-FROM-SYSTEM.<br>
<br>
Shows up for each zone the DOAS is supplying and so does:<br>
<br>
<br>
**WARNING**********************************************************************<br>
SYSTEM
EL1 Sys1 (PVVT) (T.C12)
has zero outside air for design calculations<br>
<br>
the second one seems normal since I put 0 cfm OA in the DD wiz before I went to
detailed edit mode, but I'm not sure about the first one. <br>
<br>
Hope your model turned out well, for both of our sakes.<br>
<br>
Thanks,<o:p></o:p></p>
<p class=MsoNormal>-- <br>
<br>
<b><span style='font-family:"Arial","sans-serif"'>Jacob Goodman </span></b><span
style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#666666'>, LEED
AP, Green Building Specialist </span><br>
<span style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#666666'>v:509.747.2179 f:509.747.2186 i:<a
href="http://www.lseng.com"><span style='color:#666666'>www.lseng.com</span></a></span><br>
<b><span style='font-family:"Arial","sans-serif";color:#6D928C'>L&S <span
style='letter-spacing:1.0pt'> Engineering Associates, Inc. </span></span></b><br>
<span style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#666666'>'High
Performance Design'</span> <o:p></o:p></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>
<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>Nick
Caton<br>
<b>Sent:</b> Friday, September 25, 2009 2:58 PM<br>
<b>To:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> [Equest-users] DOAS Dummy Warnings - no problem?<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<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 style='text-autospace:none'><span style='font-size:8.0pt;
font-family:"Courier New";color:#C0504D'>**WARNING**********************************************************************<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;
font-family:"Courier New";color:#C0504D'>
EL1 Sys1 (FC)
(G.N1)
has a MIN-AIR-SCH, OA-CONTROL<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;
font-family:"Courier New";color:#C0504D'>
other than FIXED and/or a MIN-OA-METHOD other than FRACTION-OF-DESIGN<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;
font-family:"Courier New";color:#C0504D'>
along with having a specified OA-FROM-SYSTEM. This may cause incorrect<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:8.0pt;
font-family:"Courier New";color:#C0504D'>
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:”<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:8.0pt;font-family:"Courier New";
color:#C0504D'>**WARNING**********************************************************************<o:p></o:p></span></p>
<p class=Normal><span style='font-size:8.0pt;font-family:"Courier New";
color:#C0504D'>
Zone: EL2 Zn
(G.1)
has a design cooling<o:p></o:p></span></p>
<p class=Normal><span style='font-size:8.0pt;font-family:"Courier New";
color:#C0504D'>
temperature differential of only 1.0F. This<o:p></o:p></span></p>
<p class=Normal><span style='font-size:8.0pt;font-family:"Courier New";
color:#C0504D'>
may result in an extremely large design airflow.<o:p></o:p></span></p>
<p class=Normal><span style='font-size:8.0pt;font-family:"Courier New";
color:#C0504D'><o:p> </o:p></span></p>
<p class=Normal><span style='font-size:8.0pt;font-family:"Courier New";
color:#C0504D'> **WARNING**********************************************************************<o:p></o:p></span></p>
<p class=Normal><span style='font-size:8.0pt;font-family:"Courier New";
color:#C0504D'>
Zone: EL2 Zn
(G.1)
has a design heating<o:p></o:p></span></p>
<p class=Normal><span style='font-size:8.0pt;font-family:"Courier New";
color:#C0504D'>
temperature differential of only -1.0F. This<o:p></o:p></span></p>
<p class=Normal><span style='font-size:8.0pt;font-family:"Courier New";
color:#C0504D'>
may result in an extremely large design airflow.<o:p></o:p></span></p>
<p class=Normal><span style='font-size:8.0pt;font-family:"Courier New";
color:#C0504D'><o:p> </o:p></span></p>
<p class=Normal><span style='font-size:8.0pt;font-family:"Courier New";
color:#C0504D'> **WARNING**********************************************************************<o:p></o:p></span></p>
<p class=Normal><span style='font-size:8.0pt;font-family:"Courier New";
color:#C0504D'>
ZONE EL2 Zn
(G.1)
<o:p></o:p></span></p>
<p class=Normal><span style='font-size:8.0pt;font-family:"Courier New";
color:#C0504D'>
might have insufficient heating capability.<o:p></o:p></span></p>
<p class=Normal><span style='font-size:8.0pt;font-family:"Courier New";
color:#C0504D'>
Check that the SYSTEM or ZONE HEATING-CAPACITY plus this<o:p></o:p></span></p>
<p class=Normal><span style='font-size:8.0pt;font-family:"Courier New";
color:#C0504D'>
ZONEs BASEBOARD-RATING is adequate to maintain the ZONE<o:p></o:p></span></p>
<p class=Normal><span style='font-size:8.0pt;font-family:"Courier New";
color:#C0504D'>
specified DESIGN-HEAT-T for the calculated peak ZONE load<o:p></o:p></span></p>
<p class=Normal><span style='font-size:8.0pt;font-family:"Courier New";
color:#C0504D'>
(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 border=0 width=119 height=37 id="Picture_x0020_1"
src="cid:image001.jpg@01CACA10.D31B0010" alt="cid:489575314@22072009-0ABB"><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</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><i><span style='font-size:10.0pt;color:#2D4D5E'>Check out
our new web-site @ </span></i><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>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>