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. |
− |
| |
− | <pre>
| |
− | Feature: Project setup
| |
− |
| |
− | In order to ensure quality of the digital built environment
| |
− | As a responsible digital citizen
| |
− | We expect compliant OpenBIM deliverables
| |
− |
| |
− | Scenario: Receiving a file
| |
− | * IFC data must use the "{schema}" schema
| |
− |
| |
− | Scenario: Exempt files
| |
− | * The IFC file "{file}" is exempt from being provided
| |
− | * No further requirements are specified because "{reason}"
| |
− |
| |
− | Scenario: Project metadata is organised and correct
| |
− | * The project must have an identifier of "{guid}"
| |
− | * The project name, code, or short identifier must be "{name}"
| |
− | * The project must have a longer form name of "{long_name}"
| |
− | * The project must be described as "{description}"
| |
− | * The project must be categorised under "{object_type}"
| |
− | * The project must contain information about the "{phase}" phase
| |
− |
| |
− | Scenario: Project geometry is stored
| |
− | * The project must contain 3D geometry representing the shape of objects
| |
− | </pre>
| |
− |
| |
− | You can fill out the variables using the guide below.
| |
| | | |
| {| class="wikitable" | | {| class="wikitable" |
− | ! Variable | + | ! Test definition |
− | ! Example | + | ! Justification |
− | ! 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>{reason}</code> | + | | <code>Given the IFC file "{file}"</code> |
− | | we don't need it | + | | An IFC-SPF file is the expected format for a project. |
− | | You can write anything here to describe any reason.
| |
| |- | | |- |
− | | <code>{guid}</code> | + | | <code>Then the file should be an {schema} file</code> |
− | | 28q3AgmxP5cepIweO5Of$o | + | | Project data must conform to a client-nominated schema. The <code>{schema}</code> may be IFC2X3 or IFC4 in general. |
− | | This is a 22 character GlobalId for a particular IFC element.
| |
| |- | | |- |
− | | <code>{name}</code> | + | | <code>Then the project has a Name attribute with a value of "{value}"</code> |
− | | 123FOO
| + | | A project must have a name given to it. |
− | | 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> | + | | <code>Then the project has a LongName attribute with a value of "{value}"</code> |
− | | 123 Foo Street, Tower B Redevelopment | + | | A project generally also has a longer name associated with it. |
− | | The full project name used to uniquely identify the project, either specified by the client or the BIM author
| |
| |- | | |- |
− | | <code>{description}</code> | + | | <code>Then the project should have geolocation data</code> |
− | | Redesign of southwest atrium of Tower B to a two-storey space with new interior fitout | + | | This checks for geolocation according to the buildingSMART recommendation in IFC2X3 and the native elements in IFC4. |
− | | A description of what the project is about, to help clarify the project scope
| |
| |- | | |- |
− | | <code>{object_type}</code> | + | | <code>Given there is at least one IfcSite element</code> |
− | | Commercial | + | | Most projects have a site. |
− | | 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> | + | | <code>Then there is an IfcSite element with a Name attribute with a value of "{value}"</code> |
− | | A
| + | | If a site exists, it typically has a name. |
− | | 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
| + | | <code>Given there is at least one IfcBuilding element</code> |
− | ! Export
| + | | Most projects have a building. |
| |- | | |- |
− | | [[File:Icon ArchiCAD.jpg|64x64px]]
| + | | <code>Then there is an IfcBuilding element with a Name attribute with a value of "{value}"</code> |
− | | [[ArchiCAD]]
| + | | If a building exists, it typically has a name. |
− | | 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]]
| |