[Equest-users] Revit to eQuest Through GBStudio: Anyone Having AnySuccess???

[Randy Williams]

We are experiencing the same issues with conversion.  It looked
promising in the instructions but is not working so far.  Did you use
Revit MEP when you traced in the file and created the zones?  At this
point we will probably have to go back to creating the zones in eQuest.
Please let us know if you find the magic key.

Randy Williams P.E.

Mechanical Project Engineer

AMC Engineers |Anchorage, Alaska

907.257.9100 |www.amc-engineers.com <http://www.amc-engineers.com/> 

Engineering Excellence

 

From: Dave Hostetter [mailto:daveh at ihd-llc.com] 
Sent: Tuesday, February 16, 2010 6:44 AM
To: equest-users at lists.onebuilding.org
Subject: [Equest-users] Revit to eQuest Through GBStudio: Anyone Having
AnySuccess???

 

Hello all!

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.

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.

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.

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. 

  

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.

Thanks in advance!  

David P. Hostetter,  E.I.T.

LEED AP

Project Engineer

Integrated Holistic Design, LLC.

C: (717) 799-0599

 

 

 

Pennsylvania Office

180 W. Airport Road

Lititz, PA  17543

(717) 406-8770

 

Washington D.C. Office

2300 M Street, NW

Suite 800

Washington D.C.,  20037

(202) 416-1732

 

NOTICE:
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. 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20100216/51189e46/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 22411 bytes
Desc: image001.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20100216/51189e46/attachment-0003.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 25563 bytes
Desc: image002.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20100216/51189e46/attachment-0004.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 2372 bytes
Desc: image003.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20100216/51189e46/attachment-0005.jpeg>