Configure Load Bearing System (FP)

Overview

This functional part is aimed at identification of the load bearing system(s), i.e. existing architectural information must be appropriately re-structured to specify all load-bearing elements. Typically it is done in early design stages and helps to derive structural analysis models for calculation and dimensioning. Since there is no specific class within IFC to capture load bearing systems, the generic class IfcSystem is used instead. For the definition of a load bearing system, which typically fulfills a specific task such as bearing of lateral loads, all building elements needed to carry this type of loads shall be contained in the system.

Note: IfcSystem inherits a couple of kernel concepts such as unique identification, owner history, name and others. Consequently, the functional part is to some extend similar to other functional parts.

Results

A system defining a load bearing structure, which contains (via grouping) all load-bearing elements needed to fulfill this function.

Information Needed	Entity/Pset/Functional Part	Man	Rec	Opt
Set the global unique identifier	IfcSystem.GlobalId --> IfcGloballyUniqueId
Apply the owner history	IfcSystem.OwnerHistory --> fp_apply_owner_history
Specify the name of the system. Note: There are no agreements for name settings. Since a human readable identification is typically used in the structural analysis domain, this attribute shall be used for this purpose. Thus, this value should have a meaningful name.	IfcSystem.Name --> IfcLabel
Specify a description for the connection. Note: There are no agreements for providing a description. However, it can provide significant information for later project stages, particularly in terms of providing an insight into a designers intent that remains available for later review and refinement. Thus, it is recommended to set this value with some explaining text.	IfcSystem.Description --> IfcText
Specify the type of the system. Note: To identify the system as a load-bearing system the name should be defined as 'load-bearing system'.	IfcSystem.ObjectType --> IfcLabel where value of IfcL:abel = 'load-bearing system
Define the relationship that assigns load-bearing building elements to the load-bearing system. Note: A structural analysis model should group IfcBuildingElement (or subtypes) only.	IfcSystem.IsGroupedBy --> fp_assigns_to_group(building element)
Define the relationship that services a building or a building storey	IfcSystem.ServicesBuildings --> fp_services_building (building, building storey)

IFC Entities Required

• IfcObject
• IfcObjectDefinition
• IfcRoot
• IfcGroup
• IfcSystem

IFC Datatypes Required

• IfcGloballyUniqueId
• IfcLabel
• IfcText

IFC Functions Required

-

IFC Property Sets Required

-

IDM Functional Parts Required

• fp_apply_owner_history
• fp_services_building
• fp_assigns_to_group

EXPRESS-G

EXPRESS Schema

SCHEMA FP_CONFIGURE_LOAD_BEARING_SYSTEM;

  TYPE IfcGloballyUniqueId = STRING (22) FIXED;
  END_TYPE;

  TYPE IfcLabel = STRING;
  END_TYPE;

  TYPE IfcText = STRING;
  END_TYPE;

  ENTITY IfcObject
    ABSTRACT SUPERTYPE
    SUBTYPE OF(IfcObjectDefinition);
      ObjectType : OPTIONAL IfcLabel;
  END_ENTITY;

  ENTITY IfcObjectDefinition
    ABSTRACT SUPERTYPE
    SUBTYPE OF(IfcRoot);
  END_ENTITY;

  ENTITY IfcRoot
    ABSTRACT SUPERTYPE;
      GlobalId     : IfcGloballyUniqueId;
      Name         : OPTIONAL IfcLabel;
      Description  : OPTIONAL IfcText;
      OwnerHistory : fp_apply_owner_history;
    UNIQUE
      UR1 : GlobalId;
  END_ENTITY;

  ENTITY fp_apply_owner_history;
  END_ENTITY;

  ENTITY IfcGroup
    SUBTYPE OF(IfcObject);
    INVERSE
      IsGroupedBy : fp_assigns_to_group FOR RelatingGroup;
  END_ENTITY;

  ENTITY IfcSystem
    SUBTYPE OF(IfcGroup);
    INVERSE
      ServicesBuildings : SET [0:1] OF fp_services_building FOR RelatingSystem;
  END_ENTITY;

  ENTITY fp_services_building;
      RelatingSystem : IfcSystem;
  END_ENTITY;

  ENTITY fp_assigns_to_group;
      RelatingGroup : IfcGroup;
  END_ENTITY;

END_SCHEMA;

ifcXML Schema

ifcXML version of this schema is not presently available

EXAMPLES

<Include examples of functional paart usage. Attach and include diagrams where necessary>