<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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";}
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;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>My responses/thoughts are below in </span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:red'>red.</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hope that helps!<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>~Nick<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><img width=119 height=37 id="Picture_x0020_1"
src="cid:image001.jpg@01CB96C5.095D3C20" alt="cid:489575314@22072009-0ABB"></span><b><span
style='font-size:11.0pt;font-family:"Stylus BT","sans-serif";color:#2D4D5E'><o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Stylus BT","sans-serif";
color:#2D4D5E'><o:p> </o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Stylus BT","sans-serif";
color:#2D4D5E'>NICK CATON, E.I.T.</span></b><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'><o:p></o:p></span></b></p>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Calibri","sans-serif";
color:#CC9900'>PROJECT ENGINEER<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>Smith & Boucher Engineers</span><span style='font-size:7.5pt;
color:#CC9900'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>25501 west valley parkway<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>olathe ks 66061<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>direct 913 344.0036<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>fax 913 345.0617<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
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;font-family:"Calibri","sans-serif";color:blue'> </span></u><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<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"'> pranita kothuru
[mailto:pranita.kothuru@gmail.com] <br>
<b>Sent:</b> Wednesday, December 08, 2010 9:28 AM<br>
<b>To:</b> Nick Caton<br>
<b>Cc:</b> John Aulbach; equest-users<br>
<b>Subject:</b> Re: [Equest-users] Systems /Zoning question.<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>All/Nick -<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>I thank you all for the valuable input. It cleared
some of my doubts but also created more.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>I am not clear with zones, zone groups and assigning HVAC's
to zone groups. If I have 70 apartments, each apartments is one zone, i group
all these apartments into one zone group and assign the PTAC unit I have
created.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Does assigning the PTAC to the zone group mean that each
zone within the zone group is assigned to one PTAC unit?<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:red'>That depends entirely on whether your PTAC is defined as ‘system
per zone’ or ‘system per site’ etc… not by what’s
in the zone group screen. I found this unintuitive myself when I first
encountered it, but the zone group screen’s system assignment pulldown
does not mean you do or don’t wind up with one system in that
group. The question is easily explored if you simply finish the wizards
and observe what’s generated by eQuest under the different options.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:red'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:red'>As an aside, for a building with this many systems/zones, you should
probably consider whether you can use a floor multiplier for the 2<sup>nd</sup>
and 3<sup>rd</sup> floors</span><span style='color:red'> to reduce the sheer
size of the model.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal>Screen 13 and 14 in DD wizard seem to be conflicting. I
entered all the data on screen 13 for the whole building. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>But after I group my zones on screen 14 the activity area
allocation uses the percentages on screen 13 for each zone group.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>I am attaching screen shots of screen 13 and 14.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='color:red'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:red'>Screen 13 sets the default values and the available occupancy types
for screen 14. Any different percentages entered in 14 override screen 13
for the corresponding zone group. I tend to only use screen 13 to define
the occ. types I need, then use screen 14 to say a given zone group is “100%
office” or “90% corridor, 10% restroom” and so on.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal>Please advise on the above questions.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Thanks for all the advise.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>Pranita.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>On Tue, Dec 7, 2010 at 5:22 PM, Nick Caton <<a
href="mailto:ncaton@smithboucher.com">ncaton@smithboucher.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Pranita et al,</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>In this situation, you must either (A)
define separate zones to define the multiple systems as they exist, or (B)
stick to your guns (assumption of thermal equivalency), and further “lump
together” the individual PTAC’s as large,
“combined-equivalent” systems.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>The first option would allow you to more
easily specify the systems as they exist – individually and independent
in operation of each other, will be more accurate if indeed the units have
differing loads on an hourly basis, as John is cautioning, and will render any
concerns of whether the assumption that the individual zones are thermally
equal moot. </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal>If I have 70 apartments do I have to create 70 PTAC(Could I
use Zone groups here). <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Does the zone groups option assign each zone within the
group one system each (of the system which is assigned to the zone group)<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <span style='color:red'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='color:red'>You should only have to create one
system type in the wizard – eQuest can create all 70 individual systems
if you ‘choose system per zone.’ Zone groups exist primarily
to help you assign/refine occupancy types, exhaust (if any) and assign a corresponding
system type. Whether you end up with one or multiple systems is
determined in the first screen of the HVAC system dialogs. Again,
finishing the wizards and observing the results (look to the components tree
under the air side systems tab) will be the fastest way for you to grasp the
possibilities if this isn’t crystal clear ;).<o:p></o:p></span></p>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>If you are concerned that the
“multiple systems in one zone” is critical for accuracy, you can
always define the adjoining internal partitions as air walls to thermally
connect the adjacent spaces (indirectly the corresponding zonal PTAC systems
will work together to handle the combined spaces’ loads). This
seems to match the real-world behavior you’re seeking to model.</span><o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>How could I assign mutliple systems to one zone?<o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:red'>You cannot do this directly. I’m describing a method to
get around that fact – define two zones, each with it’s own system,
then define or revise the connecting partition to an ‘air’ wall to effectively
connect the two zones thermally, making them behave together as one. I
think this will effectively allow the multiple systems work in tandem to handle
the combined loads.<o:p></o:p></span></p>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>The second option will actually be
harder for you (the modeler) in the long run, as you must average-together /sum
the units’ parameters to come up with an equivalent collective system
– efficiency/capacity/scheduling/etc… if the validity of the
“thermally equivalent” assumption is questionable, so is the
decision to have their systems to act as one – it’s your call.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Combining zones for thermal equivalency
is a great technique when it saves you work and time, but the approach
sometimes can result in more work than would otherwise be required in the long
run. If/when actual system zoning is readily available at the wizard
development stage of my models, I personally tend to use that information when
defining zones, unless I’m certain the flexibility/accuracy benefits
offered by a more zonally-accurate model will be unnecessary.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>~Nick</span><o:p></o:p></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D;border:solid windowtext 1.0pt;padding:
0in'><img border=0 width=119 height=37 id="_x0000_i1025"
src="cid:image002.jpg@01CB96C5.095D3C20"
alt="Image removed by sender. cid:489575314@22072009-0ABB"></span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:11.0pt;color:#2D4D5E'> </span></b><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:11.0pt;color:#2D4D5E'>NICK CATON, E.I.T.</span></b><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:7.5pt;color:#CC9900'>PROJECT ENGINEER</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#2D4D5E'>Smith & Boucher Engineers</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#2D4D5E'>25501 west valley parkway</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#2D4D5E'>olathe ks 66061</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#2D4D5E'>direct 913 344.0036</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:#2D4D5E'>fax 913 345.0617</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'><a href="http://www.smithboucher.com/"
target="_blank" 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><o:p></o:p></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'> <a
href="mailto:equest-users-bounces@lists.onebuilding.org" target="_blank">equest-users-bounces@lists.onebuilding.org</a>
[mailto:<a href="mailto:equest-users-bounces@lists.onebuilding.org"
target="_blank">equest-users-bounces@lists.onebuilding.org</a>] <b>On Behalf Of
</b>John Aulbach<br>
<b>Sent:</b> Tuesday, December 07, 2010 3:27 PM<br>
<b>To:</b> pranita kothuru; equest-users<br>
<b>Subject:</b> Re: [Equest-users] Systems /Zoning question.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Pranita:<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Careful
about "all units have the same thermodynamic conditions". End rooms
have two exposures where those in the facing directions have one.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>John R. Aulbach, PE, CEM</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>Senior Energy Engineer</span><o:p></o:p></p>
<div>
<div>
<div class=MsoNormal><span style='color:#17365D'>
<hr size=2 width="30%" noshade style='color:#17365D' align=left>
</span></div>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-variant:small-caps;color:navy'>Partner</span><span
style='font-variant:small-caps;color:green'> </span><span style='font-variant:
small-caps;color:#006600'>Energy</span></b><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>1990 E. Grand Avenue, El Segundo, CA 90245<br>
W: 888-826-1216, X254| D: 310-765-7295 | F: 310-817-2745</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a
href="http://www.ptrenergy.com/" target="_blank">www.ptrenergy.com</a><span
style='color:#1F497D'> </span><a href="mailto:%7C%20jaulbach@ptrenergy.com"
target="_blank">| jaulbach@ptrenergy.com</a><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt'>
<hr size=1 width="100%" align=center>
</span></div>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><b><span
style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'>
pranita kothuru <<a href="mailto:pranita.kothuru@gmail.com" target="_blank">pranita.kothuru@gmail.com</a>><br>
<b>To:</b> equest-users <<a href="mailto:equest-users@lists.onebuilding.org"
target="_blank">equest-users@lists.onebuilding.org</a>><br>
<b>Sent:</b> Tue, December 7, 2010 12:41:53 PM<br>
<b>Subject:</b> [Equest-users] Systems /Zoning question.</span><o:p></o:p></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hello
All -<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I
am modeling a multifamily 4 floors buildings in eQuest. I created seperate
zones for corridors and living spaces. My living spaces have PTAC units and
corridors have seperated HVAC system.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>In
DD wizard screen 1 what do I have to choose for 'System Per area'. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>All
the living spaces were zoned as one big zone (considering that all units
have same thermodynamic conditions).<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>If I
choose system per zone, this can be wrong because I have more than one PTAC
units in that given zone(as several apats were clubbed to be in one zone).<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Please
advice.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br
clear=all>
<br>
-- <o:p></o:p></p>
</div>
<p style='margin:0in;margin-bottom:.0001pt'><b><span style='color:#006600'>-
Pranita </span></b><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'> <o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class=MsoNormal><br>
<br clear=all>
<br>
-- <o:p></o:p></p>
<p style='margin:0in;margin-bottom:.0001pt'><b><span style='font-family:"Calibri","sans-serif";
color:#006600'>- Pranita </span></b><o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p>
</div>
</body>
</html>