<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:w="urn:schemas-microsoft-com:office:word"><head><META content="text/html; charset=us-ascii" http-equiv="Content-Type">
<STYLE><!-- /* Style Definitions */ p.f036a8dc-3032-4b5a-bb2e-e92fc94f4c60, li.f036a8dc-3032-4b5a-bb2e-e92fc94f4c60, div.f036a8dc-3032-4b5a-bb2e-e92fc94f4c60, table.f036a8dc-3032-4b5a-bb2e-e92fc94f4c60Table {margin:0cm; margin-bottom:.0001pt;}div.Section1 {page:Section1;}--></STYLE>
<meta content="text/html; charset=us-ascii" http-equiv=Content-Type><meta content="Microsoft Word 12 (filtered medium)" name=Generator><!--[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:"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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 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";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas","serif";}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@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="1026" />
</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>
<P CLASS="f036a8dc-3032-4b5a-bb2e-e92fc94f4c60"><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Tip #3<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Here is another tip unrelated to the ones below. If you have multiple zones served by central systems, create all zones served by a system before creating zones served by another system. This bunches the zones together and makes it easier to assign systems later. Also, if you have a large building, you can go into the inp file and insert a new system above the group of zones it serves, then reopen the eQuest file without saving it. The system will then show up in eQuest with all the zones already assigned to it.<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'>For example, if a building has 25 zones on the east half of the building served by AHU1 and 25 zones on the west half served by AHU2, set the wizard to create one system per floor. Then, create all zones served by AHU1. They will be numbered 1 through 25 (Unless you change the default naming convention). Then, create all zones served by AHU2. They will be numbered 26 – 50. Once you enter the detailed edit mode, go into the inp file, copy the code for system1 and paste it above zone 26. Then, reopen eQuest without saving it. System 2 will show up with zones 26 – 50 assigned to it. If you have a large building, this can be a big time saver.<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'>Jeremy <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"'> Grammy [mailto:grammy.hkust@gmail.com] <br><b>Sent:</b> Wednesday, January 12, 2011 6:47 AM<br><b>To:</b> Nick Caton<br><b>Cc:</b> equest-users; Otto Schwieterman<br><b>Subject:</b> Re: [Equest-users] eQUEST Tips<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Nice idea, <span class=apple-style-span><span style='font-size:8.0pt;font-family:"Arial","sans-serif"'>Otto Schwieterman!</span></span><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span class=apple-style-span><span style='font-family:"Arial","sans-serif"'>I like your post but until now I have only merge inp file by the function of "import" in eQuest, which will be very useful when a huge building or a group of buildings are modeled.</span></span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span class=apple-style-span><u><span style='font-family:"Arial","sans-serif"'>Tips:</span></u></span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span class=apple-style-span><u><span style='font-family:"Arial","sans-serif"'>At the model beginning, all of the shell and air-side system need to be specified to make sure there will no duplicate name for any component in the model. This is not hard: just edit it in wizard model, both the shell and system. And also make sure the coordination is also correct with the real design. </span></u></span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span class=apple-style-span><u><span style='font-family:"Arial","sans-serif"'>There will be a most probability of duplicate name in water-side, so if the models do not share the same chilled / domestic / hot water loop, rename all of water side staff before merging the inp files.</span></u></span><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'><span class=apple-style-span><u><span style='font-family:"Arial","sans-serif"'>Before the merging, my suggestion is that editing or testing or debugging the model first, otherwise you will find that after merging the model becomes huge, very long time to run, and hard to edit, test, debug.</span></u></span><o:p></o:p></p></div><div><p class=MsoNormal>That's my tips ( not small ;) ), any corrections are welcome.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Regards,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Grammy<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Wed, Jan 12, 2011 at 6:48 AM, 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='color:#1F497D'>Great tip (and nice model)! </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>The ability to turn on/off 3D view surfaces is something I often catch myself forgetting when it could save me time – it’s also something I wish I knew about for my first few tricky models =).</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>A related timesaver/accuracy note comes to mind from a question brought up recently on the lists: </span><o:p></o:p></p><p><span style='color:#1F497D'>-</span><span style='font-size:7.0pt;color:#1F497D'> </span><span style='color:#1F497D'>A great/quick way to check and correct if exterior roof/floor surfaces are defined (incorrectly) in-between separate & stacked shells from the wizards is to go to the same location and turn off all items except Roofs and Floors. You can then quickly identify, highlight and remove any unwanted surfaces.</span><o:p></o:p></p><p><span style='color:#1F497D'>-</span><span style='font-size:7.0pt;color:#1F497D'> </span><span style='color:#1F497D'>I might intentionally do this in my own models when I have unique roofs on multiple levels and will plan to remove the unwanted “sandwiched” surfaces once in detailed in this fashion. </span><o:p></o:p></p><p><span style='color:#1F497D'>-</span><span style='font-size:7.0pt;color:#1F497D'> </span><span style='color:#1F497D'>Notice how if you hold ctrl to rotate/zoom the model, a reference wireframe pops up which can make it easy to verify where such surfaces should/shouldn’t be located. You don’t need to move the mouse for a quick reference.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>I like the idea of “share a quick timesaver/accuracy tip” – hope this picks up!</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='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='color:#1F497D;border:solid windowtext 1.0pt;padding:0in'><img alt="Image removed by sender. cid:489575314@22072009-0ABB" border=0 height=37 id="_x0000_i1025" src="cid:image001.jpg@01CBB240.DC0EF550" width=119></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span style='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='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='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='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>Otto Schwieterman<br><b>Sent:</b> Tuesday, January 11, 2011 3:34 PM<br><b>To:</b> <a href="mailto:equest-users@lists.onebuilding.org" target="_blank">equest-users@lists.onebuilding.org</a><br><b>Subject:</b> [Equest-users] eQUEST Tips</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><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>I would like to start a discussion about tips on how to create a better energy model with less time. This is an easy example but it does save time if you currently do not turn off the components.</span><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'>To make it easier to delete the extra exterior walls that are created between shells in eQUEST, go to the Project Properties and remove the roofs, ceilings and interior <span style='color:#1F497D'>walls.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='border:solid windowtext 1.0pt;padding:0in'><img alt="Image removed by sender." border=0 height=412 id="_x0000_i1026" src="cid:image002.jpg@01CBB240.DC0EF550" width=624></span><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'><span style='border:solid windowtext 1.0pt;padding:0in'><img alt="Image removed by sender." border=0 height=338 id="_x0000_i1027" src="cid:image003.jpg@01CBB240.DC0EF550" width=624></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#1F497D'>Otto</span><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><pre>________________________________________________________________________________________<o:p></o:p></pre><pre>Fanning/Howey Associates, Inc. intends to send this transmission (including any attachments) only to the<o:p></o:p></pre><pre>designated individual or entity. If you received this message in error, please notify the sender by replying<o:p></o:p></pre><pre>to the electronic mail (if electronic) or by telephone at the number indicated on this document.<o:p></o:p></pre><pre>Fanning/Howey Associates, Inc. has taken reasonable precautions to ensure no viruses are present in the<o:p></o:p></pre><pre>electronic mail. Fanning/Howey Associates, Inc., will not accept responsibility for any loss or damage arising<o:p></o:p></pre><pre>from the use of this electronic mail or attachments. Use, disclosure, dissemination, distribution, or reproduction<o:p></o:p></pre><pre>of this message by unintended recipients is not authorized and maybe unlawful. Any information included in<o:p></o:p></pre><pre>this transmission that is not related to contracts with our authorization, verbal or written, by Fanning/Howey<o:p></o:p></pre><pre>Associates, Inc. may not be covered by our professional liability insurance. <o:p></o:p></pre><pre> <o:p></o:p></pre></div></div></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><br>_______________________________________________<br>Equest-users mailing list<br><a href="http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org" target="_blank">http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org</a><br>To unsubscribe from this mailing list send a blank message to <a href="mailto:EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</a><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></P>
<P CLASS="f036a8dc-3032-4b5a-bb2e-e92fc94f4c60"><FONT COLOR="#808080" FACE="Verdana" SIZE="1">This email message, including any attachments, is for the sole use of the intended recipient and may contain confidential, proprietary, and/or privileged information, as well as content subject to copyright and other intellectual laws. If you are not the intended recipient, you may not disclose, use, copy, or distribute the email message or its attachments. If you believe you have received this email message in error, please contact the sender by reply email, immediately delete this email and destroy copies.</FONT></P></BODY></HTML>