<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=iso-8859-1">
<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: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";}
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:12.0pt;
font-family:"Times New Roman","serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
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:48917588;
mso-list-type:hybrid;
mso-list-template-ids:-1720124362 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;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
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="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 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'>To anyone who hasn’t explored the </span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>eQuest
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>import function yet – You gotta try this! <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'>This oft-overlooked feature is</span><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> a huge timesaver, and
can make cutting in work from previous projects a breeze</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> once
you’ve wrapped your mind around the concept</span><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>. I’ve
made </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>and attached </span><span style='font-size:11.0pt;font-family:
"Calibri","sans-serif";color:#1F497D'>2 quick example files to walk anyone
through</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> it</span><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>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Unzip the example projects I’ve attached.</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> <o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Open either the WEST project or the EAST project.<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Switch to detailed</span><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> edit</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>mode i</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>f I
forgot to save it that way (</span><span style='font-size:11.0pt;font-family:
"Calibri","sans-serif";color:#1F497D'>oops!) – a good point though: you can’t
do this until after the wizards.</span><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>4.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Click File </span><span style='font-size:11.0pt;font-family:
Wingdings;color:#1F497D'>à</span><span style='font-size:11.0pt;font-family:
"Calibri","sans-serif";color:#1F497D'> Import File…<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>5.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Browse to and select the other project</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>’s
.inp file</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> (EAST or WEST)<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>6.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Follow the dialogues – </span><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>eQuest</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> will
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>check</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> for identically named items so as not to overwrite anything
without your</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> explicit knowledge</span><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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Special note: </span><span style='font-size:11.0pt;font-family:
"Calibri","sans-serif";color:#1F497D'>In these quick examples, I used the new </span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>(as
of eQuest version 3.64) </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>prefix functions in the wizards to </span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>ensure</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> each
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>project</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> ha</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>s</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> unique </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>and easily identifiable </span><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>component names starting with
WST or EST, so </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>there should be zero conflicts. </span><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>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>7.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Check out the 3D view tab – your project now includes both
buildings</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>!</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>8.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Check out the component tree and notice how everything is
clearly organized as staring with either EST or WST<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'>If you</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> should </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>ever create a custom schedule/system/construction/et</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>c.
that </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>you’d like to import into future projects, </span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>or if
you want to draw something from a past project, isolate</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> th</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>at</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> work
in </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>the source-project’s </span><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>.inp file, save th</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>at</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> text
as a new, small</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>er</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> .inp file, and you’re ready to import! </span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>When importing,
eQuest will organize all components into the same sections of the target-project’s
.inp file, so don’t worry about keeping everything in perfect order in
your “snippet” .inp’s. Just remember to retain everything up
to the “..” after each component. </span><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>It’s</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> also</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>
advisable to rename any saved components like this with some kind of unique</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>/identifiable
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>name to avoid “same-name”</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>
conflicts</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> during import.<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'>There you have it! Go forth and start a reference library of
things you’ll use more than once if you haven’t already! If you’re
in a pay-it-forward mood, consider sharing any gems with the group at large –
it’s a great way to make friends ;).<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'>Ciao,<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@01CB6A20.0DD45CB0" 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</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><i><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#2D4D5E'>Check out our new web-site @ </span></i><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"'> Pasha
Korber-Gonzalez [mailto:pasha.pkconsulting@gmail.com] <br>
<b>Sent:</b> Tuesday, October 05, 2010 9:53 AM<br>
<b>To:</b> Nick Caton<br>
<b>Cc:</b> Jeremy Poling; eQUEST Users List<br>
<b>Subject:</b> Re: [Equest-users] LEED-parking garage question/advice needed<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Hi Nick,<br>
<br>
I can't remember how long you've been modeling, but your advice exudes
'knowledge beyond your years.' At least from my perspective, I
didn't think I could have it a win-win situation for this project, but I like
your approach.<br>
<br>
Also, thanks for pointing out the idea of garages being nothing more than
building shades & process/ltg loads I hadn't thought of
inputting the "idea" of the garage as building shades. :)<br>
<br>
Importing the separate models into one later on seems daunting & tedious,
but with the separate-to-one approach I guess it can always be an option that I
decide later if it seems necessary, or for comparative purposes & a chance
at a sensitivity analysis...<br>
<br>
I always appreciate the multitude of intelligent answers and supportive comments
from fellow simulators on this list. Now we can keep moving forward until
the next hurdle.<br>
<br>
Thanks,<br>
Pasha :)<o:p></o:p></p>
<div>
<p class=MsoNormal>On Tue, Oct 5, 2010 at 10:31 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='font-size:11.0pt;color:#1F497D'>A few extra thoughts,</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 line with Jeremy’s suggestion
regarding a campus model being a useful approach… Perhaps you can have
your cake and eat it too? </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 new (3.64) wizard screens have a new
input field for each shell that allow you to assign custom prefixes suffixes to
each shell – if you utilize this while making separate files (prefix each
group of shells with N#,E#,S#, W#), and make a point to define your geometries
from a holistic CAD reference, I’ll bet you can end up with 4 distinct
files that will all import cleanly into each other when all’s said and
done as a final step… you’d want to continue the nomenclature when
defining things in detailed mode of course.</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'>I haven’t submitted but one garage
for LEED, but I’m of the opinion any unconditioned garage isn’t
anything more complicated than a collection of building shades and/or process /
external lighting loads to an eQuest modeler! To Kristy’s cautions,
one can easily define multiple exterior lighting loads (up to 10 I think)
– with distinct magnitudes and/or scheduling… allowing you to model
interior/perimeter and daytime/nighttime controls. Photocell scheduling
functions are available for perimeter lighting as well.</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'>Pasha, it’ll ultimately come down
to how you want to move forward, but 4 separate models sounds like it might
work for you: Each would feature distinct component prefixes and building
shades mimicking the entire garage, but external lighting/process loads representing
a quarter of the garage. When the time comes that a campus model is
desireable for whatever reason, you can delete the garage-shades in models 2,3
and 4, and import into #1, then modify your exterior loads to ensure
you’re modeling the full garage.</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'>If you desire extra accuracy in the
separate models, you may want to consider creating some building shades to
represent the other 3 buildings – but you’d want to delete those
later when importing the files together for a campus model...</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>
<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'><img border=0 width=119 height=37
id="_x0000_i1025" src="cid:image001.jpg@01CB6A20.0DD45CB0"
alt="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'>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'><i><span
style='font-size:10.0pt;color:#2D4D5E'>Check out our new web-site @ </span></i><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>
<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 style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;
border-color:-moz-use-text-color -moz-use-text-color'>
<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>Pasha Korber-Gonzalez<br>
<b>Sent:</b> Tuesday, October 05, 2010 9:05 AM<br>
<b>To:</b> Jeremy Poling<br>
<b>Cc:</b> eQUEST Users List<o:p></o:p></span></p>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt'><br>
<b>Subject:</b> Re: [Equest-users] LEED-parking garage question/advice needed<o:p></o:p></span></p>
</div>
</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;margin-bottom:12.0pt'>Thanks
Jeremy,<br>
<br>
I wasn't aware of the 5-year metering requirement for Energy Star...that does
help me 'accept' the advice for the model a bit more. However, it still
doesn't sit right with me to split a buiding amongst several model files for
the same reason that you mentioned about disproportionate sim results.<br>
<br>
I liked your observations for the finished model--thanks for sharing your
experience on that. I also like the idea of doing a separate model for
the garage itself with the approach of keeping all the models in separate
files, but I think I will have to reconsider the multi-files approach versus
inputting all 5 structures into one model file. hmmmm......<br>
<br>
pkg<o:p></o:p></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On
Tue, Oct 5, 2010 at 9:53 AM, Jeremy Poling <<a
href="mailto:jpoling@epsteinglobal.com" target="_blank">jpoling@epsteinglobal.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'>As a note, the USGBC reviewer’s
advice is in line with the requirements of Energy Star for detached buildings
on a campus with shared parking: for separate buildings on a campus, the
parking area (surface and/or garage) must be divided between the buildings when
entered into Portfolio Manager. If this is a LEED 2009 project and the
owner plans to comply with the 5-year metering requirement via Energy Star,
setting up the model in that manner will make it consistent with the mandatory
minimum M&V requirements. I’m not sure what led to the decision
to model each building in a separate PD2 file (other than scheduling of the
design work meaning Building 4’s model won’t be needed for some
time after Building 1’s model is done), but it might provide some benefit
to model the campus in one file. I would think this would be true in 2
specific cases:</span><o:p></o:p></p>
<p style='margin-left:38.25pt'><span style='font-size:11.0pt;font-family:Symbol;
color:#1F497D'>-</span><span style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;color:#1F497D'>If there is a single meter
covering all campus electrical use (not uncommon for campuses), allowing the model
to calculate a coincident demand for cost purposes that might be lower than the
sum of the demands for the four separate model</span><o:p></o:p></p>
<p style='margin-left:38.25pt'><span style='font-size:11.0pt;font-family:Symbol;
color:#1F497D'>-</span><span style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;color:#1F497D'>Credit for daylighting is
being pursued and there is a potential for one of the buildings to shade
another, making the combined model file more conservative on energy savings
from daylighting than the four individual models</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'>I have done a split PD2 file approach on
a model before and while it made sense when it was setup and the project was
small (10K SF total), responding to comments was more difficult. For
example, if there was some error in the baseline U-Value then each model file
would have to be corrected individually instead of changing the wall type in a
single model (4 changes instead of 1). Just some thoughts to consider.</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'>I would partially agree with the
reviewer, though – the parking garage needs to be part of the model and
with a split model you would have to put the parking garage into each of the
four models. I probably would have taken a slightly different approach,
though – If the campus is not modeled in a single model, the parking
garage should be modeled on its own, with the resulting energy divided between
the four models proportionate to the number of spaces allocated to each
building or the proposed occupancy of each building, since those are the
factors that determine how much of the garage each building would use.</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>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt;color:#C75B12'>JEREMY R. POLING, PE, LEED AP</span></b><span
style='font-size:10.0pt;color:#1F497D'><br>
</span><span style='font-size:8.0pt;color:gray'>Associate Vice President,</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><span
style='font-size:8.0pt;color:gray'>Senior Sustainability Analyst<br>
Strategic Services<br>
<i>Site Solutions | Operations | Sustainability</i></span><span
style='font-size:10.0pt;color:#1F497D'><br>
<br>
</span><b><span style='font-size:10.0pt;color:#C75B12'>EPSTEIN</span></b><span
style='font-size:10.0pt;color:#1F497D'><br>
</span><span style='font-size:8.0pt;color:gray'>Architecture<br>
Interiors<br>
Engineering<br>
Construction</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><i><span
style='font-size:8.0pt;color:green'>Epstein is a firm believer in
sustainability. We ask that you please consider the environment before printing
this e-mail.</span></i></b><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 windowtext 1.0pt;padding:3.0pt 0in 0in 0in;
border-color:-moz-use-text-color'>
<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>Walson, Kristy<br>
<b>Sent:</b> Tuesday, October 05, 2010 8:21 AM<br>
<b>To:</b> 'Pasha Korber-Gonzalez'; eQUEST Users List<br>
<b>Subject:</b> Re: [Equest-users] LEED-parking garage question/advice needed</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='font-size:11.0pt;color:#1F497D'>Hi Pasha,</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'>Having modeled a few parking garages in
various software at this point, I also do not agree with the LEED representative's
suggestion. In my experience, parking garages typically have daylighting
controls to turn off perimeter lights during the day. This would be tough
for a simulation program to model without creating a separate building for the
parking garage. I know you said that the parking garage would not be
utilizing any ECM's, but I like to leave my options open in case an owner comes
back and decides that the payback is well worth the money spent up-front for
controls.</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'>If you end up incorporating the lighting
as a bulk load on the electrical meter at each building, just remember that
you'll need 2 bulk loads - one for daytime garage lighting and one for night
time exterior lighting. If you're sure they won't be adding ECM's at a
later date, then I think the bulk load idea will work. Just be sure to
spend some time on your lighting schedule because the lighting savings seen
between the baseline and proposed models for a parking garage can be
significant and you don't want to lose any of this benefit. Good luck!</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'><b><span
style='font-size:11.0pt;color:#1F497D'>Kristy Walson, PE, LEED AP</span></b><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><i><span
style='font-size:10.0pt;color:#333333'>Mechanical Engineer / Sustainable Design</span></i><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 style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;
border-color:-moz-use-text-color'>
<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>Pasha Korber-Gonzalez<br>
<b>Sent:</b> Tuesday, October 05, 2010 9:13 AM<br>
<b>To:</b> eQUEST Users List<br>
<b>Subject:</b> [Equest-users] LEED-parking garage question/advice needed</span><o:p></o:p></p>
</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'>Hi,<br>
<br>
I would like to get a few opinions from some fellow simulators on a modeling
approach for a LEED project. Please share your opinion/advice if
you are interested.<br>
<br>
Project: Four separate buildings that surround an open-air
parking garage structure (all above grade.)--Location is Miami, FL<br>
Intent: All Four buildings (as a whole project) are going for
LEED certification. Each building will be modeled in it's own .pd2 file
as the simulator would prefer to manage the models in this manner versus using
a campus modeling approach in a single .pd2 file.<br>
<br>
USGBC recommendations where that the parking garage should be divided (or
split) into four pieces and 1/4 of the parking garage should be included with
the buildings in each of the separate model files.<br>
<br>
The ISSUE is this: My simulation gut instinct is telling me that
this is a really bad way to include the energy use of a parking garage in a
project model....(I was actually shocked that this was the advice from a LEED
representative.) So I am trying to advise my colleague that
it might be better to not include the actual parking structure (i.e. separate
shell) in each model, but to calculate the lighting use (on a schedule of
operation) for the parking garage lighting and then simply add in that energy
as a kW input on a separate meter and assign a ltg operating schedule to
it. With this approach it would be easier to take the advice
of the LEED folks and input 1/4 of the installed kW in each of the separate
model files, rather than wasting time with building in (& managing) another
shell in each model file. (FYI-there are no other ECM's that will
be accounted for in the parking garage.)<br>
<br>
<br>
What do you think of this approach? Do you think that it is
significant and important to include the "physical" presence of the
parking garage in each of the model files? What approach would you
take?<br>
<br>
Thanks for your time as always...<br>
<br>
Pasha :)<o:p></o:p></p>
</div>
</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>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>