MicroMVDs for exchange requirements/Excavation MicroMVD

From Wiki.OSArch
< MicroMVDs for exchange requirements
Revision as of 00:49, 4 November 2020 by Moult (talk | contribs) (Created page with "The following MicroMVD vocabulary can be used to ensure that the model captures data relevant to bulk excavation works during con...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The following MicroMVD vocabulary can be used to ensure that the model captures data relevant to bulk excavation works during construction.

Feature: Excavation

In order to evaluate costs and construction sequencing of excavation work
For cost planners and construction planners
Excavation volumes must be present in 3D with relevant metadata

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

Scenario: Bulk excavation volumes must be present
 * At least one excavation volume is present.
 * Excavation volumes must be uniquely named from the following list:
  | Name   |
  | {name} |
 * All excavation volumes must be assigned to a material, named from the following list of possible materials:
  | Name            |
  | {material_name} |
 * All excavation volume materials must be broken down into its constituents
 * All excavation volume materials must store the material density
 * All excavation volume materials must store the bulking factor as a property called BulkingFactor in a custom property set called uMVD_MaterialExcavation

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.
{guid} 28q3AgmxP5cepIweO5Of$o This is a 22 character GlobalId for a particular IFC element.