Editing MicroMVDs for exchange requirements/Project setup MicroMVD

From Wiki.OSArch

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
{{Template:MVD_Documentation}}
 
 
The following [[Using MicroMVDs for exchange requirements|MicroMVD]] vocabulary can be used to ensure basic project metadata is set, as a minimum requirement for all BIM projects.
 
The following [[Using MicroMVDs for exchange requirements|MicroMVD]] vocabulary can be used to ensure basic project metadata is set, as a minimum requirement for all BIM projects.
  
Line 10: Line 9:
  
 
Scenario: Receiving a file
 
Scenario: Receiving a file
  * IFC data must use the "{schema}" schema
+
* The IFC file "{file}" must be provided
 +
  * IFC data must use the {schema} schema
  
 
Scenario: Exempt files
 
Scenario: Exempt files
 
  * The IFC file "{file}" is exempt from being provided
 
  * The IFC file "{file}" is exempt from being provided
  * No further requirements are specified because "{reason}"
+
  * No further requirements are specified because {reason}
  
 
Scenario: Project metadata is organised and correct
 
Scenario: Project metadata is organised and correct
* The project must have an identifier of "{guid}"
+
  * The project name, code, or short identifier must be "{value}"
  * The project name, code, or short identifier must be "{name}"
+
  * The project must have a longer form name of "{value}"
  * The project must have a longer form name of "{long_name}"
+
  * The project must be described as "{value}"
  * The project must be described as "{description}"
+
  * The project must be categorised under "{value}"
  * The project must be categorised under "{object_type}"
+
  * The project must contain information about the "{value}" phase
  * The project must contain information about the "{phase}" phase
 
  
 
Scenario: Project geometry is stored
 
Scenario: Project geometry is stored
 
  * The project must contain 3D geometry representing the shape of objects
 
  * The project must contain 3D geometry representing the shape of objects
 +
* The project must contain 3D geometry representing clearance zones
 +
* The project must contain 3D geometry representing the center of gravity of objects
 +
* The project must contain 3D geometry representing the object bounding boxes
 
</pre>
 
</pre>
  
Line 47: Line 49:
 
| You can write anything here to describe any reason.
 
| You can write anything here to describe any reason.
 
|-
 
|-
| <code>{guid}</code>
+
| <code>{value}</code>
| 28q3AgmxP5cepIweO5Of$o
+
| Foobar
| This is a 22 character GlobalId for a particular IFC element.
+
| Any text value you expect for a particular attribute or property.
|-
 
| <code>{name}</code>
 
| 123FOO
 
| A short project code or name used to uniquely identify the project, either specified by the client or the BIM author
 
|-
 
| <code>{long_name}</code>
 
| 123 Foo Street, Tower B Redevelopment
 
| The full project name used to uniquely identify the project, either specified by the client or the BIM author
 
|-
 
| <code>{description}</code>
 
| Redesign of southwest atrium of Tower B to a two-storey space with new interior fitout
 
| A description of what the project is about, to help clarify the project scope
 
|-
 
| <code>{object_type}</code>
 
| Commercial
 
| If the project is categorised as a particular arbitrary type, it may be described here. Example categories could be "Residential", "Retail", "Commercial", "Health" and "Defence". Alternatively, it could be categorised as "Civic", "Infrastructure".
 
|-
 
| <code>{phase}</code>
 
| A
 
| If the project is phased or staged, the phase or stage name may be placed here.
 
|}
 
 
 
=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: #ffd37f;" | ArchiCAD 23
 
| <code>GlobalId</code> cannot be overridden during export
 
| [[ArchiCAD project setup]] describes how to set these project attributes
 
|-
 
| [[File:BlenderBIM_Addon_logo.png|64x64px]]
 
| [[BlenderBIM Add-on]]
 
| style="background-color: #b6cca1;" | v0.0.200722
 
| style="background-color: #b6cca1;" | v0.0.200722
 
|
 
|
 
|-
 
| [[File:icon_FreeCAD.png]]
 
| [[FreeCAD]]
 
| style="background-color: #ffd37f;" | 0.19pre
 
| style="background-color: #ffd37f;" | 0.19pre
 
| <code>GlobalId</code> cannot be overridden during export. The project <code>Name</code> is not maintained during import.
 
|
 
|-
 
| [[File:Icon Revit.png|64x64px]]
 
| [[Autodesk Revit|Revit]]
 
| style="background-color: #fbb4a8;" | Revit 2019.2 IFC 8/5/2020
 
| style="background-color: #b6cca1;" | Revit 2019.2 IFC 8/5/2020
 
| During import, the project <code>GlobalId</code> is maintained, but all other metadata is lost.
 
| [[Revit project metadata]] describes how to set these project attributes
 
|-
 
| [[File:Tekla-logo.png|64x64px]]
 
| [[Tekla]]
 
|
 
|
 
|
 
|
 
 
|}
 
|}
 
[[Category:Model View Definitions (MVD)]] [[Category:Autodesk Revit]] [[Category:BIMTester]] [[Category:MicroMVD]]
 

Please note that all contributions to Wiki.OSArch are considered to be released under the Creative Commons Attribution-ShareAlike (see Wiki.OSArch:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Template used on this page: