← All use cases

Base slab (Rough)

ARC-SLAB-BASE

Rough dimensions according to structural engineering for base slabs in design development and permitting stages.

Description

  • Coarsely dimensioned base or raft slab according to the structural concept.
  • Used for coordination between architecture and structural engineering, not for execution planning.

Modelling guidelines

  • Model as a simplified volume; split at component boundaries.
  • Do not model reinforcement, foundation details, or layer build-ups.
  • Early: concept via sketches as structural sketch in the architecture model; verify exclusion zones from the structural engineer.
  • Later: align the same components with Reference in the structural model as well.
  • Use an IfcMaterial that corresponds to the actual material class.

Attributes

Name Description Unit
ObjectType

Marks the base slab.

Allowed values

  • BASESLAB - base slab
PredefinedType

Marks the base slab.

Allowed values

  • BASESLAB - base slab
LoadBearing

Pset_SlabCommon

Marks the element as a load-bearing component in the architecture model.

Allowed values

  • TRUE - load-bearing element
GrossVolume

Qto_SlabBaseQuantities

Gross volume of the modelled base slab.

Status

Pset_SlabCommon

Element status for coordination on existing buildings.

Allowed values

  • NEW - new
  • EXISTING - existing
  • DEMOLISH - to demolish
  • TEMPORARY - temporary
ElementStatus

ePset_ElementStatus

Element status for coordination on existing buildings.

Allowed values

  • NEW - new
  • EXISTING - existing
  • DEMOLISH - to demolish
  • TEMPORARY - temporary

Note

  • IFC2x3 substitute for Status.
CostInterface

ePset_Cost

Cost interface of the component - base building or tenant fit-out.

Allowed values

  • GAB - base building (client / landlord)
  • MAB_{Mietername} - tenant fit-out, e.g. MAB_Migros
AwardInterface

ePset_Cost

Award package of the component by three-digit BKP code - so interfaces between contractor packages become visible.

Allowed values

  • See value list BKP award package - e.g. 211, 221, 244.
PlanningInterface

ePset_Cost

Planning interface of the component by three-digit BKP code - so responsibilities between planning disciplines become visible.

Allowed values

  • See value list BKP planning package - e.g. 091, 092, 094.
BelowTerrain

ePset_Cost

Marks whether the component is below terrain.

Allowed values

  • TRUE - below terrain
  • FALSE - above terrain
EbkpH

ePset_Cost

eBKP-H classification according to SN 506 511 - derivable from IsExternal, LoadBearing, and BelowTerrain.

Allowed values

  • C01.03 - base slab

Contact

abstract ag

Imprint · Picassoplatz 4, 4052 Basel