Project participants, for instance, architects, construction engineers, facilities managers, have different responsibilities, knowledge, and needs in terms of creating and using data.
Such data are shared with other project participants allowing them to perform their tasks. As I wrote in the previous articles (https://bimcorner.com/everything-worth-knowing-about-the-ifc-format/ ) the recommended solution when working with many involved parties is to use the IFC format. From previous posts on this format
From previous posts on this format ( The secrets of the IFC Schema Part 1 , Part 2 and Part 3) you could also learn that the IFC is a huge structure of interconnected elements and attributes along with the mutual relationships they share. This format, still in the most popular 2X3 version, features 653 standardized classes with definitions, including… about 12000 properties. As you can see, it’s a huge amount of information. Hence, the question arises, do we export this huge amount of information every single time we export to IFC? How to filter it? Which one should we choose?
The answer is Model View Definition – MVD.
1. What is Model View Definition (MVD)?
The IFC schema structure is modular and includes elements for specific domains, such as Architecture, Structural Analysis, Electrical Installation, etc.
IFC aims to create an interface among various tools to exchange information. However, not each program has an internal data schema that stores all specific classes in each domain. Let us remind that there are about 12000 of them.
Think, for example, of Tekla Structures modeling software. It doesn’t include data about the humidifier (IfcHumidifierType) or the occupant (IfcOccupant). Such information may be useful for creating a simulation of the building’s climate and energy balance or evacuation simulation, thus it isn’t included in the program.
It should, therefore, be clarified which subset of all IFC schema data is needed during the exchange for a specific application. In other words, which information needs to be filtered from the entire IFC schema.
Such subsets of data can be defined by analyzing the general schema of IFC in smaller “packages”, namely the MVD. They define the user requirements for necessary information. The MVD describes which objects, representations, relationships, concepts, and attributes are necessary for the project participant and the application to perform the requested task.
The Model View Definition also specifies which part of the IFC schema is implemented by a given program.
The developers of each software can choose the list of IFC classes, which support IFC import and export features. It means they can create their own Model View Definitions.
It’s important to realize that in fact, every IFC export feature in every program is based on the MVD.
2. Examples of MVD
The most common type of MVD for IFC version 2×3 is the Coordination View. The Coordination View is a filtered version of the full IFC schema. It’s also created to coordinate the project among multiple users and disciplines in the project. Eventually, it’s one of the main IFC applications in BIM technology.
Official buildingSmart MVD’s for IFC 2×3
Get free resources and articles, straight to your inbox!
Keep your skills up-to-date with our newsletter. No spam, just knowledge.
Liked the post? Share it!
Lots of time and effort go into creating all our articles and resources, we'd love if you'd spare a moment to share this one!
DO NOT MISS
Download our free guides:
- “5 steps to learn parametric modeling”
- “How to lead coordination meetings in an effective way”.