Element classes MicroMVD
The following MicroMVD vocabulary can be used to ensure Industry Foundation Classes (IFC) elements belong to the correct IFC class.
Feature: Element classes
In order to correctly identify objects
As any interested stakeholder filtering objects for a particular purpose
All IFC elements must belong to the appropriate IFC class
Scenario: Ensure all IFC type elements use the correct IFC class
* The element "{guid}" is an "{ifc_class}"
* The element "{guid}" is an "{ifc_class}" only
* The element "{guid}" is further defined as a "{predefined_type}"
* The element "{guid}" should not exist because "{reason}"
You can fill out the variables using the guide below.
| Variable | Example | Description |
|---|---|---|
{guid} | 28q3AgmxP5cepIweO5Of$o | This is a 22 character GlobalId for a particular IFC element. |
{ifc_class} | IfcWall | This case insensitive text value must correspond to the full name of an IFC class. |
{predefined_type} | BEAM | This case insensitive text value must correspond to the predefined type of an IFC class, or a custom object type. |
{reason} | we don’t need it | You can write anything here to describe any reason. |
Software guides
| Icon | Software | Certified Version | Notes | Guides | Import | Export |
|---|---|---|---|---|---|---|
![]() | ArchiCAD | ArchiCAD 23 | ArchiCAD 23 | |||
![]() | Bonsai | v0.0.200829 | v0.0.200829 | |||
| FreeCAD | 0.19pre | 0.19pre | ||||
| Revit | Revit 2020.2 IFC 8/5/2020 | Revit 2020.2 IFC 8/5/2020 | For import, opening an IFC does not retain any element class information. Linking IFCs do retain this information. For export, some Revit family categories have restrictions on which element classes they can be exported to, and the user cannot override it. | Refer to Revit and IFC classes | ||
![]() | Tekla |


