<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:"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";}
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 WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Hi Cole,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><br>Wizard-level system/zone assignments are not the most intuitive thing. Whenever in doubt, the best thing to do is to try one option, then finish the wizards and observe the results in detailed view (look to the airside component tree).<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'>Your method sounds good. The zone groups dialog does override the percent-based allocations if you define something new (i.e. this group of spaces under one system is 100% office).<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 wind up with one system serving a bank of 5 adjacent offices, or 5 separate systems, or no new systems depends on the “system per…” option for the system you select in the custom zone dialog dropdown… (“unintuitive” is the kindest word I’ve come up with anyway ^_^)! Play around with that to achieve what you need. Note that a typical VAV system should look like one “system” in the component tree over all its child zones, with the individual terminal units defined at the zone/space level.<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'>eQuest can handle many unique profiles (the upper limit per project is more than 1,000), so you could easily model the “flow” of children as you describe. That said, the wizards will only generate one set of schedules (occupancy and otherwise) per shell, and your control over that output is limited – you are describing a “post-wizard” task right 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'>Funday-Monday!<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="Picture_x0020_1" src="cid:image001.jpg@01CC5B64.7E0648A0" 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-size:12.0pt;font-family:"Stylus BT","sans-serif";color:#2D4D5E'>NICK CATON, P.E.</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'>SENIOR ENGINEER<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:7.5pt;color:#CC9900'><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, suite 200<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>Cole Hudson<br><b>Sent:</b> Friday, August 12, 2011 4:47 PM<br><b>To:</b> equest-users@lists.onebuilding.org<br><b>Subject:</b> [Equest-users] Basic Question Regarding HVAC Zoning<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I only want to make sure I’m going about this in the correct manner. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The project I’m using to teach myself this program is a largish elementary school. I’ve made a few models with simplified zoning, and they worked alright. I wanted to graduate to custom zoning, with system types that might better reflect our typical design (Parallel VAV in classroom blocks, single zone VAV in cafeteria/gym, etc). <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I traced my CAD file for the envelope and preliminary zoning plan, and set up a couple air-side systems (all in the DD wizard). I skipped over the “area allocation” dialog, because I discovered that the “zone groups” dialog allows you to override area allocations per zone group. So, I set up a classroom zone group, and added each classroom zone to it, an office zone group, etc… I changed the area allocation in the zone group dialog for each zone group to reflect the zone usage. At this point, does eQuest pretty much ignore entire building area allocation numbers in the formal “area allocation” dialog, because I have custom allocation profiles set up for each zone group? I did this because the unless I’m mistaken, eQuest only allows you to assign systems to zone <i>groups</i>, not individual zones. The model is coming up short, and this method of zone/system assignment just seems wrong to me. Am I doing this correctly? <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Related question: does eQuest allow you to set up occupancy profiles for each zone, so that occupancy diversity (flow of children from classrooms to cafeteria, etc) can be modeled?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thank you guys. Lurking the list for past couple weeks has been very informative. Have a good weekend. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>Cole Hudson, E.I.T.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt'>Stridde Callins & Associates, Inc.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt'>342 S. Navigation Blvd.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt'>Corpus Christi, TX 78405<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt'>Tel: (361) 883-9199</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:9.0pt'>Cell: (361) 876-0560<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt'>Fax: (361) 883-9177 <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal style='text-align:justify'><span style='font-size:7.5pt'>**CONFIDENTIALITY NOTICE: Information contained in this email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, and have received this communication in error, please contact the sender by reply email and destroy all copies of the original message. Thank you.**</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>