Interoperability Downloads – Add-ins for Revit Structure 2013 and Revit MEP 2013

ArchiCAD Revit Interoperability

Interoperability and Collaboration seem to be on my mind recently. Just a few days ago I wrote about all those .dwgs we deal with, and before that I discussed the various file types ArchiCAD can import and export. It’s good advice, but figuring out how to juggle countless .dwgs and pdfs feels a little antiquated. What we all want are ways for smarter data exchange. Well GRAPHISOFT has just released the latest Add-ins for Revit Structure 2013 and Revit MEP 2013. So if your consultants are using Autodesk products instead of working natively in ArchiCAD like Riverstone Structural Concepts, these Add-ins will make your team more efficient.

What are these Add-ins?

These free Add-Ins improve the data exchange between ArchiCAD and Revit. They enable direct import of ArchiCAD IFC models and IFC model export to ArchiCAD. And they optimize Revit’s standard IFC import and export function. Basically Revit can handle IFC models without these Add-Ins, but the import/export functions will be much smoother with them.

Why is GRAPHISOFT developing components for Autodesk products?

ArchiCAD Revit InteroperabilityWhen the structural engineer imports an ArchiCAD IFC model, warning and/or error messages may appear about the limits of Revit’s capacity to read IFC data accurately (e.g., in importing ArchiCAD Zones and Grids). To help minimize these, the Revit Structure/MEP Add-In, called GRAPHISOFT ArchiCAD Connection, fixes a number of these known shortcomings in the standard open process. Also when exporting MEP elements from Revit MEP or AutoCAD MEP, they are converted to MEP Modeler elements.

GRAPHISOFT ArchiCAD Connection has two commands. The Improved IFC Import command post-processes a previously converted (imported) IFC file in Revit Structure/MEP and fixes a number of Revit Structure’s known shortcomings in IFC model conversion. The Export to ArchiCAD command directly exports and optimizes the IFC model data for use in ArchiCAD. ArchiCAD Connection has the following additional functions:

  • Import/export of Grid elements: Full conversion of (Ifc)Grid elements when exporting and importing to/from Revit Structure.
  • Import of ArchiCAD’s Zones: ArchiCAD Zones (IfcSpaces) imported as “Rooms” are displayed in correct position in Revit Structure.
  • Import of ArchiCAD’s Slabs: Imported load-bearing ArchiCAD Slabs are set to “Structural Floor” elements in Revit Structure.
  • Export of Beam/Column Profile definitions: The profile names exported from Revit are correctly converted to IFC format.
  • Additional fine tuning of slanted columns, ramps, etc. is done in Revit Structure.

ArchiCAD Revit Interoperability

Want MORE detail on the Data Exchange process with Revit Structure? Check this out. And here’s some additional info about Revit MEP.


ArchiCAD Revit InteroperabilityIt really all comes back to Open BIM. The future is for the collaborators. We can work smarter and make file exchange easier by improving how we model and organize our data in ArchiCAD. GRAPHISOFT can continue to develop the open qualities of ArchiCAD, further embedding IFC into the fundamentals of elements (as they have been doing over recent releases). Our industry as a whole can continue to push for open standards and interconnectivity. But sometimes it’s nice to offer extra ways to help out our consultants, allowing them to stay in their comfort zones.

Download the add-ins here

Graphisoft has been developing these Add-ins for a few years now. So if you’re working with consultants using older Autodesk projects, there are add-ins for Revit Structure and MEP going back to 2010. And Add-ins for AutoCAD MEP 2010/2009/2008. You can find the latest add-ins and these older add-ins here.


  1. David Lash

    The interoperability diagram you show here is confusing and unhelpful. It may be correct but that doesn’t make it the right way to communicate your message. The message communicated here is that the process is complex, is this really what you want to say?

  2. Jared Banks

    David, yeah that is a very confusing diagram, partially why I chose it; I was hoping to spark some conversation. The link above it for data exchange does explain what’s going on (though for the uninitiated that might not lessen the confusion too much).

    The difference between 2D and BIM Collaboration is a huge topic. And I hope to revisit it more in the future. Or better yet, link to people much better versed in it than me. For instance the BIM Manager at Bond BRyan:

    Your thoughts on this topic are very much welcome. Do you have a better diagram in mind? I’d be thrilled to do a follow up post that perhaps focuses on demystifying the interoperability process. Maybe something that starts with “does data exchange feel like this (diagram above)?” It doesn’t have to.” Interested in helping me put that together?

  3. Maciej

    This diagram does not make sense, as well as collaboration diagram of Tekla Structures. Someone who worked on it, he had no clue about architect-constructor collaboration.
    now finish the project BIM (complete!) architectural documentation made with structures IFC file, so I know what I say,
    but I do not have time to explain in English 🙂
    describes the process on my blog in “Project BIM in Practice” as long as the page in Polish 🙁

  4. Jared Banks


    I’m not quite sure I follow what you’re saying. That the interface with Tekla Structures is easier than with Revit Structures? As I mentioned in the comment above to David, the link does better explain the illustration. And coincidentally, I heard a Graphisoft BIM Implementation guy explain that diagram as part of a lecture he was giving at EcoBuild in Washington, DC this week. After hearing him talk, it does actually become pretty clear. Could I explain it myself now, probably not clearly enough to share! 🙂

  5. Maciej

    Here you have a diagram Tekla Structures-Archicad 20StepsTS & AC.jpg

    It’s very similar. A work varies tremendously!
    In Tekla Structures IFC file is loaded as a reference model which can then be converted to Tekla elements.
    The Revit IFC model is loaded otherwise. There is no conversion, elements of the model are more or less an immediately Revit elements.

    Continuous import-export IFC file between programs, destroys the file.

    ps. If you say that this workflow, is only part of lecture, this information should be everywhere. Because that workflow picture is misleading people.

  6. Maciej

    Next thing:

    as you may have noticed, no one can answer a question on forum:

    anyone has done the documentation of architecture using the construction IFC model?
    In other words, if someone was working on a REAL FULL BIM project?
    what is the problem, IFC export is set with the option of BREP (others are incomplete) after imports to the AC elements are as objects…
    of which is known can’t be done cross-section!
    helps only MORPH option, but we would lose all data, even GUID!
    if any had this problem?

  7. Jared Banks

    Maciej, the first link is broken. Can you repost it? Since Tekla and Graphisoft are both pushing OpenBIM it’s no surprise that they talk better with each other. As for your other question on the forum, again I’m not sure I fully understand. But there are lots of people who are successfully using IFC to exchange data between ArchiCAD and a whole range of other products. If you’re not already following Bond Bryan on Twitter, you definitely should. They are working hard to understand how to work with IFC.

    And in general watch info coming out of the UK since they are now one of the leaders of IFC and BIM collaboration.

  8. Maciej

    link already works,
    take a look at twitter


Submit a Comment

Your email address will not be published. Required fields are marked *