What? Why? Who? How? When?¶
What data do you need from whom for your planning?
Determine what you need from each party involved in the project.
How must this data be described?
What quality should the geometry correspond to?
What information do you need from the counterpart?
Which model view definition is used for the application?
For data exchange, we recommend the MVD CoordinationView for IFC 2x3.
For IFC 4, the MVD DesignTransferView is recommended.
An MVD (Model View Definition) defines a subset of the IFC specification (IFC schema). This subset focuses on the requirements (exchange requirements) of the creator and recipient of the information. The requirements are elicited on the basis of an IDM (Information Delivery Manual)1.
An IDM defines the scope and type of an information requirement that must be needed or delivered by the project participants at a specific point in time (process) (exchange requirements).
With an exact definition of the exchange requirements in the project team, models can be exchanged efficiently and integrated into the planning process.
The respective contents are divided into subject models (Derived from the reference model). Check the models for their content (geometry, information). At the beginning of the project, a zero point, the storey structure as well as the planning procedure (processes) must be defined.
IFC types relevant to timber construction¶
Example table - the scope of the data depends on the project
For the exchange of recesses, BuildingElementProxy's with the ObjectType ProvisionForVoid is required.
|IfcCovering||Only if necessary for construction|
|IfcCurtainWall||as one volume (no geometric layers)|
|IfcDoor||"order" the opening (opening element) of the door. Check the dimension of the opening with care.|
|IfcSlab||as one volume (no geometric layers)|
|IfcWall||as one volume (no geometric layers)|
|IfcWindow||in most cases it is the opening and not the window that is relevant.|
|IfcOpeningElement||Check the dimension of the opening with care.|