<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: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:"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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin-top:0in;
margin-right:0in;
margin-bottom:11.0pt;
margin-left:0in;
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-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
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;}
.MsoPapDefault
{mso-style-type:export-only;
margin-bottom:11.0pt;}
@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>Hello all!<o:p></o:p></p>
<p class=MsoNormal>I have been experimenting with converting Revit files to
eQuest .inp files through Green Building Studio and I have not had much luck so
far. I have read through the presentation that Glumac gave for BSUG and it
seems that their process is to recreate the building in Revit by tracing over a
CAD floor plan. They and many other sources have mentioned that you
should not try to just convert an Architect’s Revit file directly because
it is too complex.<o:p></o:p></p>
<p class=MsoNormal>Of course the very first thing that I tried was to do just
that and convert a small school that we did directly to .inp and it did not
work. Many things were missing… it was basically just a huge mess
and not would not work as a functional eQuest file.<o:p></o:p></p>
<p class=MsoNormal>So I have just tried following their instructions with
starting from scratch and building a new model by tracing the CAD plans of a
small field house that we are doing. I do have to say that creating the
model in Revit instead of eQuest was much easier, no counterclockwise tracing
and if you mess up things are very easy to fix. So after creating all the
walls, ceiling, floor and roof I created the spaces in Revit (I have been told
that these should transfer directly over to eQuest as Zones). When I
exported the gbxml file to GBStudio there were no problems noted with the file.<o:p></o:p></p>
<p class=MsoNormal>After using GBStudio to convert the file to a .inp file I
opened it in eQuest. It did not have any problems opening the file but boy
was it a mess. It created one zone for the entire building (obviously not
how I zoned it in Revit). All of the exterior walls for the plenum spaces,
the roof and some of the normal walls came in as Building Shades in eQuest.
All interior walls came into eQuest labeled as exterior walls (this may be a
result of the wall type that I selected in Revit which was just a generic 8”
wall). The floor did not come into eQuest at all. Basically the
overall shape of the building is there but many many things are missing.
You can see the picture below on the left is the Revit file while the one on
the right is the eQuest file. <o:p></o:p></p>
<p class=MsoNormal><img width=639 height=387 id="_x0000_i1027"
src="cid:image002.jpg@01CAAEF4.E30CA370"><img width=639 height=389
id="Picture_x0020_2" src="cid:image008.jpg@01CAAEF4.E30CA370"><o:p></o:p></p>
<p class=MsoNormal>Anyhow, if anyone has experience dealing with Revit to
eQuest conversion issues or has successfully completed a conversion without
problems I would love to hear from you! Hopefully this can start a good
conversation on whether or not trying to convert Revit files (even simplistic
ones) to eQuest is even worth trying. I must admit that I am still on the
fence but am leaning in the direction of it not being worth the trouble unless
I can figure out how to work out these issues.<o:p></o:p></p>
<p class=MsoNormal>Thanks in advance! <o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;text-autospace:
none'><span style='font-size:12.0pt;font-family:"Arial","sans-serif";
color:#00B011'>David P. Hostetter, E.I.T.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;text-autospace:
none'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>LEED AP<o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;text-autospace:
none'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>Project Engineer<o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;text-autospace:
none'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>Integrated Holistic Design, LLC.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>C:
(717) 799-0599<o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><img
width=131 height=59 id="Picture_x0020_1"
src="cid:image009.jpg@01CAAEF4.E30CA370" alt="ihd LOGO email smaller"></span><o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt'><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt'><u><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Pennsylvania
Office<o:p></o:p></span></u></p>
<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>180 W.
Airport Road</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif";
color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt'><span
style='color:#1F497D'>Lititz, PA 17543</span><span style='color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>(717)
406-8770</span><span style='color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt'><span
style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt'><u><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Washington
D.C. Office<o:p></o:p></span></u></p>
<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>2300 M
Street, NW<o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Suite
800<o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Washington
D.C., 20037<o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>(202)
416-1732</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif";
color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt'><span
style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D'>NOTICE:<br>
This e-mail transmission is intended only for the use of the individual or entity
named above and may contain information that is confidential, privileged,
and/or exempt from disclosure under applicable law. If you are not the intended
recipient, you are hereby notified that any review, disclosure, copying,
distribution, or other use of any of the information contained in this
transmission is strictly prohibited. If you have received this transmission in
error, please immediately notify the sender by e-mail at the above address and
delete it from your computer system; you should not copy the message or
disclose its contents to anyone. The content of the message and or attachments
may not reflect the view and opinions of the originating company or any party
it is representing. <o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>