Difference between revisions of "MicroMVDs for exchange requirements/Quantity take-off MicroMVD"

From Wiki.OSArch
Line 1: Line 1:
WIP:
+
The following [[Using MicroMVDs for exchange requirements|MicroMVD]] vocabulary can be used to ensure that data is present for basic dimensional quantity take-off.
  
Walls
+
* Concrete material: "Concrete" in IfcMaterial.Category
 +
* Concrete construction method: Pset_ConcreteElementGeneral.ConstructionMethod
 +
* Strength class: Pset_ConcreteElementGeneral.StrengthClass
 +
* Compressive strength: IfcMaterial.Pset_MaterialConcrete.CompressiveStrength
  
* In-situ concrete: Length, Height, NetVolume, GrossSideArea
+
<pre>
* Precast concrete: Length, Width, Height, GrossSideArea
+
Feature: Quantity take-off
* Block: Length, Width, Height, GrossSideArea
+
 
* Partition: Length, Width, Height, GrossSideArea
+
In order to cost elements
* Other: Length, Width, Height, GrossSideArea
+
For cost planners
 +
All elements need to have dimensional and cost-significant metadata assigned
 +
 
 +
Scenario: All concrete elements are named and contain data
 +
* All concrete elements must be assigned to a concrete material
 +
* All concrete elements must have their construction method assigned
 +
* All concrete elements must have their strength class assigned
 +
* All concrete materials must have their compressive strength assigned
 +
 
 +
Scenario: All concrete element data must be in a standardised form
 +
* All concrete elements must have their construction method assigned with one of the following values:
 +
  | Value  |
 +
  | In-situ |
 +
  | Precast |
 +
  | {value} |
 +
* All concrete elements must have their strength class assigned with one of the following values:
 +
  | Value  |
 +
  | N      |
 +
  | S      |
 +
  | {value} |
 +
* All concrete materials must have their compressive strength assigned with one of the following values:
 +
  | Value    |
 +
  | 20000000  |
 +
  | 25000000  |
 +
  | 32000000  |
 +
  | 40000000  |
 +
  | 50000000  |
 +
  | 65000000  |
 +
  | 80000000  |
 +
  | 100000000 |
 +
  | {value}  |
 +
 
 +
Scenario: All blockwork walls are identifiable
 +
* All blockwork walls must be assigned to a block material
 +
 
 +
Scenario: All partition walls are identifiable
 +
* All partition walls must be assigned to a partition material
 +
 
 +
Scenario: All walls must have dimensional quantities
 +
* All in-situ concrete walls must have a Length, Height, NetVolume, and GrossSideArea quantity
 +
* All precast concrete walls must have a Length, Width, Height, and GrossSideArea quantity
 +
* All blockwork walls must have a Length, Width, Height, and GrossSideArea quantity
 +
* All partition walls must have a Length, Width, Height, and GrossSideArea quantity
 +
* All other walls must have a Length, Width, Height, and GrossSideArea quantity
 +
</pre>
 +
 
 +
You can fill out the variables using the guide below.
 +
 
 +
{| class="wikitable"
 +
! Variable
 +
! Example
 +
! 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.
 +
|}
  
 
Slabs
 
Slabs

Revision as of 01:59, 16 June 2021

The following MicroMVD vocabulary can be used to ensure that data is present for basic dimensional quantity take-off.

  • Concrete material: "Concrete" in IfcMaterial.Category
  • Concrete construction method: Pset_ConcreteElementGeneral.ConstructionMethod
  • Strength class: Pset_ConcreteElementGeneral.StrengthClass
  • Compressive strength: IfcMaterial.Pset_MaterialConcrete.CompressiveStrength
Feature: Quantity take-off

In order to cost elements
For cost planners
All elements need to have dimensional and cost-significant metadata assigned

Scenario: All concrete elements are named and contain data
 * All concrete elements must be assigned to a concrete material
 * All concrete elements must have their construction method assigned
 * All concrete elements must have their strength class assigned
 * All concrete materials must have their compressive strength assigned

Scenario: All concrete element data must be in a standardised form
 * All concrete elements must have their construction method assigned with one of the following values:
   | Value   |
   | In-situ |
   | Precast |
   | {value} |
 * All concrete elements must have their strength class assigned with one of the following values:
   | Value   |
   | N       |
   | S       |
   | {value} |
 * All concrete materials must have their compressive strength assigned with one of the following values:
   | Value     |
   | 20000000  |
   | 25000000  |
   | 32000000  |
   | 40000000  |
   | 50000000  |
   | 65000000  |
   | 80000000  |
   | 100000000 |
   | {value}   |

Scenario: All blockwork walls are identifiable
 * All blockwork walls must be assigned to a block material

Scenario: All partition walls are identifiable
 * All partition walls must be assigned to a partition material

Scenario: All walls must have dimensional quantities
 * All in-situ concrete walls must have a Length, Height, NetVolume, and GrossSideArea quantity
 * All precast concrete walls must have a Length, Width, Height, and GrossSideArea quantity
 * All blockwork walls must have a Length, Width, Height, and GrossSideArea quantity
 * All partition walls must have a Length, Width, Height, and GrossSideArea quantity
 * All other walls must have a Length, Width, Height, and GrossSideArea quantity

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.

Slabs

  • In-situ concrete: Width, Length, Depth, Perimeter, GrossArea, GrossVolume
  • Precast concrete: Width, Length, Depth, Perimeter, GrossArea, GrossVolume
  • Other: GrossArea

Column

  • Concrete: Length, OuterSurfaceArea, GrossVolume
  • Steel: Length, OuterSurfaceArea, GrossVolume, GrossWeight
  • Other: Length, OuterSurfaceArea, GrossVolume, GrossWeight

Beam

  • Concrete: Length, GrossVolume
  • Steel: Length, OuterSurfaceArea, GrossVolume, GrossWeight
  • Other: Length, GrossVolume

Other

  • Footings: Length, Width, Height, GrossSurfaceArea, GrossVolume
  • Railings: Length
  • Piles: Length, OuterSurfaceArea, GrossVolume, GrossWeight
  • Openings: Width, Height, Depth, Area, Volume
  • Stair flights: Length, GrossVolume
  • Structural members: Length, OuterSurfaceArea, GrossVolume, GrossWeight
  • Reinforcement bar: Length, Weight
  • Reinforcement mesh: Length, Width, Weight
  • Curtain wall panels: GrossArea
  • Window: Area
  • Duct segments: Length, OuterSurfaceArea, GrossWeight
  • Pipe segments: Length, OuterSurfaceArea, GrossWeight

Steel

painting type:

- none
- architectural paint
- fire resistant painting

grade - 250 - 300 - 350 - 400 - 450

brick wall

finish: - none - render - paint

block walls

thickness: - 90 - 190 - 390

core filled: - none - 1.2m - full height

load bearing: - yes - no

stiffeners (if not modeled): - yes - no

reo bars: - yes - no

partition walls

plasterboard layer: - impact resistant (yes / no) - moisure resistant (yes / no) - fire rated (yes / no)

Pset_WallCommon.LoadBearing – True/False Pset_WallCommonAcousticRating – Rw / Rw + Ctr Pset_WallCommon.FireRating -/-/-