In brief
- IFC2x3 Coordination View 2.0 is described as the certified and most widely supported MVD in both Archicad and Revit.
- In the IFC4 schema, Coordination View splits into Reference View and Design Transfer View.
- Revit's IFC Export Setup screen has separate tabs such as Space Boundaries, Level of Detail and Property Sets.
- In Archicad, export can be done via three different commands: Save as, Merge to IFC Model, and Publisher.
IFC (Industry Foundation Classes) files are an open data format that enables model sharing between architectural, structural and mechanical disciplines. However, which data an IFC file contains is determined by the selected Model View Definition (MVD). According to the official help documentation of Archicad and Revit, choosing the wrong MVD can result in missing geometry during coordination meetings, lost parameters, or files that cannot be opened by the receiving software. This guide summarizes the MVD options and export steps defined in both software's documentation.
What is a Model View Definition, and why does it matter?
According to Graphisoft's definition, an MVD defines a legal subset of the IFC schema and provides implementation guidance for all IFC concepts used within that subset (classes, attributes, relationships, property sets, quantity definitions). In other words, an MVD answers the question "what information is in this file, and what isn't." Choosing the wrong MVD can cause problems such as elements becoming non-editable due to BREP geometry, lost parameters, or the receiving software not supporting the schema.
Which MVD is used when?
The table below summarizes the main MVDs defined in Archicad and Revit documentation and their intended uses.
| MVD | Schema | Purpose |
|---|---|---|
| Coordination View 2.0 | IFC2x3 | The most widely supported coordination format between architecture, structural and MEP; certified in Archicad for both import and export |
| Coordination View (Surface Geometry) | IFC2x3 | A simplified BREP-based subset for visualization and clash detection; parameters are lost and elements become non-editable |
| Basic FM Handover View | IFC2x3 | Space/equipment list for facility management handover; forms the basis for COBie documentation |
| IFC4 Reference View | IFC4 | One-directional reference model sharing; change requests are forwarded to the original author |
| IFC4 Design Transfer View | IFC4 | Supports adding, deleting, moving and modifying interdependent elements; not suitable for round-trip exchange |
| GSA Concept Design BIM 2010 | IFC2x3 | For additional property set requirements of public institutions such as the US GSA and Norway's Statsbygg |
Revit documentation also lists IFC2x3 COBie 2.4 Design Deliverable View as the format required for the UK's 2016 public sector Level 2 BIM mandate.
IFC export steps in Archicad
According to Graphisoft documentation, there are three separate export paths in Archicad:
File › Save as— exports the entire project or filtered content into a new IFC file.File › Interoperability › IFC › Merge to IFC Model— adds the selected content into an existing IFC file coming from another discipline. Important note: merging does not overwrite any element in the existing file; if an element with the same GlobalId exists, the added element is merged in with a new GlobalId.Document › Publisher— publishes views into one of the IFC formats; a different Translator can be selected for each Publisher item to produce recipient-specific output.
In all three methods, the process is managed by an IFC Translator for Export, and an MVD is selected during export. After export is complete, checking the file in a free IFC viewer such as Solibri Model Viewer, Tekla BIMsight or DDS-CAD Viewer (or by reopening it in Archicad) is a good practice recommended by the documentation.
Revit's IFC Export Setup options
The main tabs affecting export in Revit's IFC Export Setup Options screen are:
General: IFC version (MVD selection), phase to export, file type (IFC, IFC XML, Zipped IFC).
Space Boundaries: None, 1st level, or 2nd level options. 2nd level divides space boundaries relative to the opposing spaces and also covers thermal properties; preferred in projects requiring energy analysis.
Additional Content: How linked files are exported (as a separate IFC, within the same IFCProject, or within the same IFCSite), and filtering of elements visible in the view.
Property Sets: Whether Revit-specific property sets, IFC common property sets, and base quantities are included.
Level of Detail: Four levels from Extra Low to High; higher levels produce larger but more accurate BREP and profile representations.
Implications for architecture and archviz workflows
For offices sharing files between architecture, structural and MEP disciplines, the most critical choice is between Coordination View 2.0 and IFC4 Reference/Design Transfer View. Revit documentation explicitly states that the IFC4 schema is not supported by all applications; therefore, this schema should not be chosen without confirming that the receiving software supports IFC4. On the archviz side, it should be kept in mind that models exported with the Surface Geometry (BREP) format become non-editable; if a reference model is sufficient for visualization, this option can reduce file size, but parametric editing should not be expected on the return trip.
Common mistakes
Choosing IFC4 Reference View or Design Transfer View without asking the recipient about their software; some applications don't support this schema.
Using the Merge to IFC Model command to transfer changes from one version of the same file to another; Graphisoft documentation specifically states this is not suitable for that purpose.
Leaving the Space Boundaries level as "None" in Revit when energy analysis is required.
Sending the exported file for sharing without checking it in an IFC viewer first.
Sources
3 sourcesSource texts are not republished; short quotes are marked, everything else is our own summary and commentary.
In most offices in Turkey, IFC exchange is still handled with a "let's pick whatever format works" mentality; yet the MVD choice directly determines who sees what data in a coordination meeting. In particular, choices made without understanding the difference between Design Transfer View and Reference View can lead to situations where the engineer cannot edit the model or parameters are lost.
Getting these settings right—without requiring any significant hardware or license cost—prevents hours of "why won't the model open" email exchanges. Asking the other party about their software version before using IFC4 is, in particular, the cheapest precaution that offices most often skip.
Frequently asked questions
Which IFC MVD is most widely supported in Archicad?
According to Graphisoft documentation, IFC2x3 Coordination View 2.0 is the MVD that Archicad is certified for in both import and export, and it is the most widely supported.
What is the difference between IFC4 Design Transfer View and Reference View?
Reference View is for one-directional reference sharing, with change requests forwarded to the original author; Design Transfer View supports adding, deleting and modifying interdependent elements, but is not suitable for round-trip model exchange.
What does the Merge to IFC Model command do in Archicad?
This command adds the selected content into an existing IFC file coming from another discipline, does not overwrite existing elements, and merges elements with the same GlobalId using a new GlobalId; according to the documentation, this command is not suitable for transferring changes from one version of the same file to another.
