Buildz is very pleased to welcome back Joe Kendsersky for more posts full of tips and best practices in Revit. This will be a series of four posts dealing with importing and managing geometry from Rhinoceros, McNeel and Associate’s popular nurbs modeling platform. Joe works at Autodesk as a Customer Success Engineer for Revit Architecture. He is trained as an architect and joined Revit Technology in 2000, and subsequently Autodesk in 2002. Joe is a wealth of information about what it going on in offices as well as what is being developed in the factory.
The purpose of this series of posts is to cover some of the different workflow options between Autodesk Revit Architecture & Rhino and discuss topics that we should take into consideration when using both applications.
First, let’s make a general differentiation between both programs:
Rhino is a tool that specializes in free-form, non-uniform rational B-spline (NURBS) modeling and has gained a lot of popularity in the architectural community because of the Grasshopper plug-in for computational design – allowing designers to analyze and quickly iterate several building form options.
Autodesk Revit Architecture is a tool designed to integrate BIM, were building elements (walls, floors, roofs) have relationships between with other. In Revit we are assembling an entire project as it were going to be built, documenting it, leveraging the ability to quantify components and, most importantly, making real time design changes.
Choices you have to make:
Which tool is best to use and when? Can both tools work together? What should someone start off with when beginning a project? It comes down to what the users’ design goals are and what they are trying to accomplish. You could imagine several different scenarios such as creating specific family components (furniture, curtain wall elements) in Rhino to be scheduled in Revit or making a building form in Rhino to host and associate building elements (wall, floors) in Revit or even exporting the context of a Revit project to model specific elements like a complex roof in Rhino to then be re-imported into Revit. Both of these applications can work well together side by side as long as the team knows what they are trying to accomplish.
Here is a brief example of using Revit and Rhino together. The image below represents a free form exterior building envelope created in Rhino.
The geometry from Rhino can be used in Revit Architecture – the image below is a exported .sat file from Rhino inserted into a Revit Mass family template.
Finally, in Revit Architecture we can load the Mass Family geometry into a project and associate building elements (walls, floors) to the Rhino geometry, document the design and quantify components.
In the next post, we’ll discuss some different workflow scenarios between Autodesk Revit Architecture & Rhino and how we can leverage the power of both tools.