Editing MicroMVDs for exchange requirements/Model federation MicroMVD

The following [[Using MicroMVDs for exchange requirements|MicroMVD]] vocabulary can be used to ensure IFC elements belong to the correct IFC class.

<pre>
Feature: Model federation

In order to coordinate multiple models that are produced separately
For all model coordinators and recipients of the final built environment
The location of each model's origin point must be specifically set to a coordinated value

Scenario: Receiving a file
 * The IFC file "{file}" must be provided
 * IFC data must use the {schema} schema

Scenario: Ensure that an agreed datum for the project is in the right location
 * There is a datum element {guid} as an {ifc_class}
 * The element {guid} has a global easting, northing, and elevation of {number}, {number}, and {number} respectively
 * The element {guid} has a local X, Y, and Z coordinate of {number}, {number}, and {number} respectively
</pre>

You can fill out the variables using the guide below.

{| class="wikitable"
! Variable
! Example
! Description
|-
| <code>{file}</code>
| project.ifc
| The filename or path to any IFC file.
|-
| <code>{schema}</code>
| IFC4
| The schema version. At the moment, these are likely to be either IFC4 or IFC2X3.
|-
| <code>{guid}</code>
| 28q3AgmxP5cepIweO5Of$o
| This is a 22 character GlobalId for a particular IFC element.
|-
| <code>{ifc_class}</code>
| IfcSite
| This case insensitive text value must correspond to the full name of an IFC class. It is recommended for the purposes of this MicroMVD that this should be an IfcSite, or IfcBuilding, or other spatial element that all other objects are related to.
|-
| <code>{number}</code>
| 42
| Any valid number. Note that eastings, northings, and elevations, are not angular measures, such as latitude and longitude, but are instead based on a coordinate reference system. If global coordinates are specified, the element will be checked with its map conversion applied. If local coordinates are specified, CRS map conversions will not be specified.
|}


=Software guides=

{| class="wikitable"
!rowspan="2"|Icon
!rowspan="2"|Software
!colspan="2"|Certified Version
!rowspan="2"|Notes
!rowspan="2"|Guides
|-
! Import
! Export
|-
| [[File:Icon ArchiCAD.jpg|64x64px]]
| ArchiCAD
| style="background-color: #b6cca1;" | ArchiCAD 23
| style="background-color: #b6cca1;" | ArchiCAD 23
| See the [[Geolocation MicroMVD]] for caveats related to federating geolocated data.
| 
|-
| [[File:BlenderBIM_Addon_logo.png|64x64px]]
| [[BlenderBIM Add-on]]
| style="background-color: #b6cca1;" | v0.0.200829
| style="background-color: #b6cca1;" | v0.0.200829
|
|
|-
| [[File:icon_FreeCAD.png]]
| [[FreeCAD]]
| 
|
|
|
|-
| [[File:Icon Revit.png|64x64px]]
| [[Autodesk Revit|Revit]]
| style="background-color: #b6cca1;" | Revit 2020.2 IFC 8/5/2020
| style="background-color: #b6cca1;" | Revit 2020.2 IFC 8/5/2020
| Note: see the [[Revit geolocation]] guide for caveats related to checking global coordinates
| [https://thinkmoult.com/ifc-coordinate-reference-systems-and-revit.html IFC Coordinate Reference Systems and Revit] describes the relationship between Revit coordinates and IFC coordinates
|-
| [[File:Tekla-logo.png|64x64px]]
| [[Tekla]]
| 
| 
| 
| 
|}

[[Category:Model View Definitions (MVD)]] [[Category:BIMTester]] [[Category:MicroMVD]]