Export IFC to REVIT problems

[alfie hope]

Anybody having a massive headache sharing info with Revit using consultants? IFC exports view nicely in Solibri and Navisworks but data goes missing once imported into Revit.

This is a revit problem, granted (and so says Vectorworks), but it is still a problem for design teams when it comes to sharing info.

The elements which go missing are those which are custom 3d solids such as extrudes for fittings/pinboards, boxings etc. Even when given IFC data they don't translate into Revit. This means that we are having difficulty getting the M&E guys to line up electrical sockets nicely..

Has anybody found a way of getting around this? I've tried other export options but IFC seems to be the most stable, despite its problems..

[Jeffrey W Ouellette]

Have you tried converting the Extrudes to Generic Solids and then export them that way?

You could run a test by taking one problematic object from the project, in a blank file, and place multiple instances of it. In each instance, change the geometric representation (e.g. Extrude, Generic Solid, NURBS, 3D Polys). Then export via IFC.

Part of the problem is that Revit is trying to convert the IFC objects into native Revit data structures and the implementation of its geometry kernel isn't very flexible, at the moment. It has difficulty taking some valid types of geometry descriptions and making them fit the Revit ecosystem.

You can help, by "dumbing down" the file for them.

[Peter van der Elst]

We also had problems exporting to Revit. The main problem we had was that Revit didn't create holes in the walls for the windows and doors. Also the windows and doors were drawn on a higher location. Since a contractor here really wanted us to deliver either Revit or compatible files, we had a separate office draw our 3d building again in Revit (we won't buy Revit!! :-) ). I hope these problems can be solved in the short run either by Nemetschek or Autodesk... But I can try dumbing down the file for a test, although this would not be the correct way (and it will take time to give every ifc object a new ifcformat.

[Jeffrey W Ouellette]

Peter,

I wouldn't go so far as to dumb down everything. Autodesk does have to suck it up and improve their IFC import. While progress is slow, they are working on it.

We've had success with Walls, Doors, and Windows, though it is touchy. Revit doesn't like "flipped" Doors and Windows. It is easy to do in Vectorworks, flipping a Door/Window around after placement, and we export it and the transformation info, but Revit has difficulty resolving this operation.

It is an issue both sides are aware of.

Walls at different levels appear to be the result of conflicts with height settings determined by instance or style, especially when using heights set automatically by layers/stories, especially with top and bottom offsets. Again, it is valid information written, but not handled well by Revit, at this time.

[brian-rwc]

the more that Nemtschek becomes aware of the issues of importing IFC data into Revit maybe they could offer a "safe mode" overlay option for Vectorworks Architect that will warn you or prevent you from creating geometry in a manner Revit "does not like" or cannot process very well.

Even though the compatibility issue may be more the fault of Revit than Vectorworks, Revit is the one creating the de-facto standards so Nemetschek doesn't really have a choice other than to comply.

I think many people would welcome this feature as insurance against future file coordination problems. Regardless of how many improvements Nemetschek makes to it's software it will always be seen at fault if Revit cannot import the data correctly and it will continue to lose market share to Autodesk. I know that's not the way it should be in an ideal world but that's just the way it is. For Nemetschek's sake it could actually help safeguard against the migration of users from Vectorworks to Revit.

This is something that could simply be a checkbox option under Vectorworks Preferences. It would also be nice to have a "Internal Audit Function" to warn of potential compatibility issues prior to exporting to IFC format. There could be 2 different error checks. One that just checks for IFC compatibility another for IFC/Revit compatibility.