MicroMVDs for exchange requirements/Project setup MicroMVD

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}

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.

Test definition	Justification
Given the IFC file "{file}"	An IFC-SPF file is the expected format for a project.
Then the file should be an {schema} file	Project data must conform to a client-nominated schema. The {schema} may be IFC2X3 or IFC4 in general.
Then the project has a Name attribute with a value of "{value}"	A project must have a name given to it.
Then the project has a LongName attribute with a value of "{value}"	A project generally also has a longer name associated with it.
Then the project should have geolocation data	This checks for geolocation according to the buildingSMART recommendation in IFC2X3 and the native elements in IFC4.
Given there is at least one IfcSite element	Most projects have a site.
Then there is an IfcSite element with a Name attribute with a value of "{value}"	If a site exists, it typically has a name.
Given there is at least one IfcBuilding element	Most projects have a building.
Then there is an IfcBuilding element with a Name attribute with a value of "{value}"	If a building exists, it typically has a name.