Difference between revisions of "MicroMVDs for exchange requirements/Project setup MicroMVD"

From Wiki.OSArch
Line 17: Line 17:
  
 
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 "{name}"
 
  * The project name, code, or short identifier must be "{name}"
 
  * The project must have a longer form name of "{long_name}"
 
  * The project must have a longer form name of "{long_name}"
Line 25: Line 26:
 
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 48: Line 46:
 
| we don't need it
 
| we don't need it
 
| You can write anything here to describe any reason.
 
| You can write anything here to describe any reason.
 +
|-
 +
| <code>{guid}</code>
 +
| 28q3AgmxP5cepIweO5Of$o
 +
| This is a 22 character GlobalId for a particular IFC element.
 
|-
 
|-
 
| <code>{name}</code>
 
| <code>{name}</code>
Line 68: Line 70:
 
| A
 
| A
 
| If the project is phased or staged, the phase or stage name may be placed here.
 
| 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
 +
|- style="background-color: #b6cca1;"
 +
|
 +
| [[BlenderBIM Add-on]]
 +
| v0.0.200722
 +
|
 +
|
 +
|
 +
|-
 +
|
 +
| [[FreeCAD]]
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|
 +
| ArchiCAD
 +
|
 +
|
 +
|
 +
|
 +
|-
 +
|
 +
| Revit
 +
| 2019.2
 +
|
 +
|
 +
|
 
|}
 
|}

Revision as of 00:37, 10 August 2020

The following MicroMVD vocabulary can be used to ensure basic project metadata is set, as a minimum requirement for all BIM projects. 

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
 * The IFC file "{file}" must be provided
 * 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

You can fill out the variables using the guide below.

Variable Example Description
{file} project.ifc The filename or path to any IFC file.
{schema} IFC4 The schema version. At the moment, these are likely to be either IFC4 or IFC2X3.
{reason} we don't need it You can write anything here to describe any reason.
{guid} 28q3AgmxP5cepIweO5Of$o This is a 22 character GlobalId for a particular IFC element.
{name} 123FOO A short project code or name used to uniquely identify the project, either specified by the client or the BIM author
{long_name} 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
{description} 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
{object_type} 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".
{phase} A If the project is phased or staged, the phase or stage name may be placed here.

Software guides

Icon Software Certified Version Notes Guides
Import Export
BlenderBIM Add-on v0.0.200722
FreeCAD
ArchiCAD
Revit 2019.2
Retrieved from "https://wiki.osarch.org/index.php?title=MicroMVDs_for_exchange_requirements/Project_setup_MicroMVD&oldid=680"