Switching from Revit

Over the past year, we have developed standards & protocols based on Autodesk Revit. We spent months creating models in Revit to be utilized on site. Our success at VDC can only be attributed to our hard work and excessive work hours, as well as our ability to develop workarounds. We have retooled existing databases software tools, so that they would sync with Revit.

Unfortunately, it seems that this has all been for nothing (not that we haven't learned a lot, though). In the past few months, we have found flaws in Revit that prevent us from completely implementing 4D and 5D the way we need to.

There is a bug relating to phasing & groups. I don't 100% understand it, but it prevents us from controlling the phase of objects within a group. This is problematic because we need to understand the timing of objects for both scheduling, procurement and cost engineering. This bug extends to instance parameters.

The second major issue is that certain parameters (specifically Assembly Code and Assembly Description) do not export from Revit to Navisworks for certain objects (it seems standard objects). This also affects our 4D implementation and makes it impossible for us to streamline 4D.

Someone else at Tocci put it much more eloquently that I have:

4D: Innovaya can receive the ball, but Revit can't throw.
4D: NavisWorks can receive the ball, but Revit can't throw.
5D: Innovaya can receive the ball, but Revit can't throw.

Autodesk is aware of all of these problems and is working on them (from what I've heard); however, they don't know the timing of a resolution.

So, instead of working on high priority projects this week, I'm going to evaluate Bentley and Graphisoft/Vico. The switch could happen in the very near future, so I need to be prepared to pick a new software platform.

4 comments:

Miguel Krippahl said...

This is one of the most amazing posts I have read in 2 years, about implementing BIM.

It rehabilitates my faith in the construction business.

Perceiving you have made a wrong move (not you personally Laura, my guess is you knew this from quite some time now, you a big company) and correcting your course, that is a logical move I have been expecting less and less in this business.

Companies go after the hype and the vendors babble, and never care to find out what really is the best for them.

From what I have seen, most of the methodologies you so painfully invented this last year will transit smoothly to the new platform. Most of BIM is not about software but about methods.

Anyway, I wish you the best of luck. And also, don´t let them make a hasty choice, remember where that got you last time...

David Haynes said...

Autodesk fixed this problem on 1/7/08. There is no need to jump ship. As you know Autodesk as also purchased Navisworks and has demonstrated a beta version of a material takeoff program to go with Revit.

Soon Navisworks and Revit will work well together and contractors will have a more integrated approach.

Scott Davis (Autodesk) said...

Laura,

What kind of assistance in these issues have you asked for/received from Autodesk? I know that Autodesk would dedicate some resources to help you through this tough time you are having.

If your company is dedicated to Navisworks, it would be the right move to find solutions with Autodesk since, as David Hayes says, Revit interoperablity with Navis will only get better now that Navis is an Autodesk product.

Stick it out with Revit and ask for help. We are here for you and we will help you through any difficulties you might be having.

Ben_Murphy said...

From Scott Davis:

"Revit interoperablity [sic] with Navis will only get better now that Navis is an Autodesk product."

Ha. If I have noticed one thing over the last 15+ years I have been using autodesk products, interoperability of their own products has never appeared to be a concern.

Reverse compatibility? Who needs that?