IFC 4.3.x development

6.1.3.1 IfcBeam

Change log

IFC4

additionsattributes PredefinedType
additionswhere_rulesCorrectPredefinedType
additionswhere_rulesCorrectTypeAssigned

IFC4X1

modificationswhere_rules CorrectTypeAssigned definitionChanged from (sizeof(IsTypedBy) = 0) or ('ifc4.ifcbeamtype' in typeof(self\IfcObject.IsTypedBy[1].RelatingType)) to (sizeof(IsTypedBy) = 0) or ('ifc4x1.ifcbeamtype' in typeof(self\IfcObject.IsTypedBy[1].RelatingType))

IFC4X2

modificationswhere_rules CorrectTypeAssigned definitionChanged from (sizeof(IsTypedBy) = 0) or ('ifc4x1.ifcbeamtype' in typeof(self\IfcObject.IsTypedBy[1].RelatingType)) to (sizeof(IsTypedBy) = 0) or ('ifc4x2.ifcbeamtype' in typeof(self\IfcObject.IsTypedBy[1].RelatingType))

IFC4X3_RC3

modificationssupertype Changed from IfcBuildingElement to IfcBuiltElement
modificationswhere_rules CorrectTypeAssigned definitionChanged from (sizeof(IsTypedBy) = 0) or ('ifc4x2.ifcbeamtype' in typeof(self\IfcObject.IsTypedBy[1].RelatingType)) to (sizeof(IsTypedBy) = 0) or ('ifc4x3_rc3.ifcbeamtype' in typeof(self\IfcObject.IsTypedBy[1].RelatingType))

6.1.3.1.1 Semantic definitions at the entity

An IfcBeam is a horizontal, or nearly horizontal, structural member that is capable of withstanding load primarily by resisting bending. It represents such a member from an architectural point of view. It is not required to be load bearing.

NOTE  Definition according to ISO 6707-1: structural member for carrying load(s) between or beyond points of support, usually narrow in relation to its length and horizontal or nearly so.

NOTE  The representation of load-bearing beams in a structural analysis model is provided by subtypes of IfcStructuralMember (with IfcStructuralCurveMember being mostly applicable) as part of an IfcStructuralAnalysisModel.

NOTE  For any other longitudinal structural member, not constrained to be predominately horizontal nor vertical, or where this semantic information is irrelevant, the entity IfcMember should be used.

The camber of a beam may be defined by assigning a StructuralCurveMember with displacement coordinates. Multiple sets of camber ordinates may be provided that are qualified by the particular load case, where full dead load would typically be used for fabrication, and other scenarios used for other loading conditions such as during construction.

There are two entities for beam occurrences:

  • IfcBeamStandardCase used for all occurrences of beams, that have a profile defined that is swept along a directrix. The profile might be changed uniformly by a taper definition along the directrix. The profile parameter and its cardinal point of insertion can be fully described by the IfcMaterialProfileSetUsage. These beams are always represented geometricly by an 'Axis' and a 'SweptSolid' or 'AdvancedSweptSolid' shape representation (or by a 'Clipping' geometry based on the swept solid), if a 3D geometric representation is assigned. In addition they have to have a corresponding IfcMaterialProfileSetUsage assigned.

    NOTE  Model view definitions and implementer agreements may further constrain the applicable geometry types, for example, by excluding tapering from an IfcBeamStandardCase implementation.* IfcBeam used for all other occurrences of beams, particularly for beams with non-uniformly changing profile sizes along the sweep, or beams having only 'AdvancedBrep', 'Brep', 'SurfaceModel', or 'Tessellation' geometry. NOTE  Model view definitions and implementer agreements may impose the use of IfcBeam in all cases by excluding IfcBeamStandardCase from scope of the model view. HISTORY  New entity in IFC1.0

6.1.3.1.1 Attributes

# Attribute Type Description
IfcRoot
1 GlobalId IfcGloballyUniqueId Assignment of a globally unique identifier within the entire software world.
2 OwnerHistory OPTIONAL IfcOwnerHistory Assignment of the information about the current ownership of that object, including owning actor, application, local identification and information captured about the recent changes of the object,

> NOTE  only the last modification in stored - either as addition, deletion or modification.

> IFC4 CHANGE  The attribute has been changed to be OPTIONAL.
3 Name OPTIONAL IfcLabel Optional name for use by the participating software systems or users. For some subtypes of IfcRoot the insertion of the Name attribute may be required. This would be enforced by a where rule.
4 Description OPTIONAL IfcText Optional description, provided for exchanging informative comments.
IfcObjectDefinition
HasAssignments SET [0:?] OF IfcRelAssigns FOR RelatedObjects Reference to the relationship objects, that assign (by an association relationship) other subtypes of IfcObject to this object instance. Examples are the association to products, processes, controls, resources or groups.
Nests SET [0:1] OF IfcRelNests FOR RelatedObjects References to the decomposition relationship being a nesting. It determines that this object definition is a part within an ordered whole/part decomposition relationship. An object occurrence or type can only be part of a single decomposition (to allow hierarchical strutures only).

> IFC4 CHANGE  The inverse attribute datatype has been added and separated from Decomposes defined at IfcObjectDefinition.
IsNestedBy SET [0:?] OF IfcRelNests FOR RelatingObject References to the decomposition relationship being a nesting. It determines that this object definition is the whole within an ordered whole/part decomposition relationship. An object or object type can be nested by several other objects (occurrences or types).

> IFC4 CHANGE  The inverse attribute datatype has been added and separated from IsDecomposedBy defined at IfcObjectDefinition.
HasContext SET [0:1] OF IfcRelDeclares FOR RelatedDefinitions References to the context providing context information such as project unit or representation context. It should only be asserted for the uppermost non-spatial object.

> IFC4 CHANGE  The inverse attribute datatype has been added.
IsDecomposedBy SET [0:?] OF IfcRelAggregates FOR RelatingObject References to the decomposition relationship being an aggregation. It determines that this object definition is whole within an unordered whole/part decomposition relationship. An object definitions can be aggregated by several other objects (occurrences or parts).

> IFC4 CHANGE  The inverse attribute datatype has been changed from the supertype IfcRelDecomposes to subtype IfcRelAggregates.
Decomposes SET [0:1] OF IfcRelAggregates FOR RelatedObjects References to the decomposition relationship being an aggregation. It determines that this object definition is a part within an unordered whole/part decomposition relationship. An object definitions can only be part of a single decomposition (to allow hierarchical strutures only).

> IFC4 CHANGE  The inverse attribute datatype has been changed from the supertype IfcRelDecomposes to subtype IfcRelAggregates.
HasAssociations SET [0:?] OF IfcRelAssociates FOR RelatedObjects Reference to the relationship objects, that associates external references or other resource definitions to the object.. Examples are the association to library, documentation or classification.
IfcObject
5 ObjectType OPTIONAL IfcLabel The type denotes a particular type that indicates the object further. The use has to be established at the level of instantiable subtypes. In particular it holds the user defined type, if the enumeration of the attribute PredefinedType is set to USERDEFINED.
IsDeclaredBy SET [0:1] OF IfcRelDefinesByObject FOR RelatedObjects Link to the relationship object pointing to the declaring object that provides the object definitions for this object occurrence. The declaring object has to be part of an object type decomposition. The associated IfcObject, or its subtypes, contains the specific information (as part of a type, or style, definition), that is common to all reflected instances of the declaring IfcObject, or its subtypes.

> IFC4 CHANGE  New inverse relationship, change made with upward compatibility for file based exchange.
Declares SET [0:?] OF IfcRelDefinesByObject FOR RelatingObject Link to the relationship object pointing to the reflected object(s) that receives the object definitions. The reflected object has to be part of an object occurrence decomposition. The associated IfcObject, or its subtypes, provides the specific information (as part of a type, or style, definition), that is common to all reflected instances of the declaring IfcObject, or its subtypes.

> IFC4 CHANGE  New inverse relationship, change made with upward compatibility for file based exchange.
IsTypedBy SET [0:1] OF IfcRelDefinesByType FOR RelatedObjects Set of relationships to the object type that provides the type definitions for this object occurrence. The then associated IfcTypeObject, or its subtypes, contains the specific information (or type, or style), that is common to all instances of IfcObject, or its subtypes, referring to the same type.

> IFC4 CHANGE  New inverse relationship, the link to IfcRelDefinesByType had previously be included in the inverse relationship IfcRelDefines. Change made with upward compatibility for file based exchange.
IsDefinedBy SET [0:?] OF IfcRelDefinesByProperties FOR RelatedObjects Set of relationships to property set definitions attached to this object. Those statically or dynamically defined properties contain alphanumeric information content that further defines the object.

> IFC4 CHANGE  The data type has been changed from IfcRelDefines to IfcRelDefinesByProperties with upward compatibility for file based exchange.
IfcProduct
6 ObjectPlacement OPTIONAL IfcObjectPlacement Placement of the product in space, the placement can either be absolute (relative to the world coordinate system), relative (relative to the object placement of another product), or constraint (e.g. relative to grid axes). It is determined by the various subtypes of IfcObjectPlacement, which includes the axis placement information to determine the transformation for the object coordinate system.
7 Representation IfcProductDefinitionShape Reference to the representations of the product, being either a representation (IfcProductRepresentation) or as a special case a shape representations (IfcProductDefinitionShape). The product definition shape provides for multiple geometric representations of the shape property of the object within the same object coordinate system, defined by the object placement.
ReferencedBy SET [0:?] OF IfcRelAssignsToProduct FOR RelatingProduct Reference to the IfcRelAssignsToProduct relationship, by which other products, processes, controls, resources or actors (as subtypes of IfcObjectDefinition) can be related to this product.
PositionedRelativeTo SET [0:1] OF IfcRelPositions FOR RelatedProducts
ReferencedInStructures SET [0:?] OF IfcRelReferencedInSpatialStructure FOR RelatedElements
IfcElement
8 Tag OPTIONAL IfcIdentifier The tag (or label) identifier at the particular instance of a product, e.g. the serial number, or the position number. It is the identifier at the occurrence level.
FillsVoids SET [0:1] OF IfcRelFillsElement FOR RelatedBuildingElement Reference to the IfcRelFillsElement Relationship that puts the element as a filling into the opening created within another element.
ConnectedTo SET [0:?] OF IfcRelConnectsElements FOR RelatingElement Reference to the element connection relationship. The relationship then refers to the other element to which this element is connected to.
IsInterferedByElements SET [0:?] OF IfcRelInterferesElements FOR RelatedElement Reference to the interference relationship to indicate the element that is interfered. The relationship, if provided, indicates that this element has an interference with one or many other elements.

> NOTE  There is no indication of precedence between IsInterferedByElements and InterferesElements.

> IFC4 CHANGE New inverse relationship.
InterferesElements SET [0:?] OF IfcRelInterferesElements FOR RelatingElement Reference to the interference relationship to indicate the element that interferes. The relationship, if provided, indicates that this element has an interference with one or many other elements.

> NOTE  There is no indication of precedence between IsInterferedByElements and InterferesElements.

> IFC4 CHANGE New inverse relationship.
HasProjections SET [0:?] OF IfcRelProjectsElement FOR RelatingElement Projection relationship that adds a feature (using a Boolean union) to the IfcBuildingElement.
HasOpenings SET [0:?] OF IfcRelVoidsElement FOR RelatingBuildingElement Reference to the IfcRelVoidsElement relationship that creates an opening in an element. An element can incorporate zero-to-many openings. For each opening, that voids the element, a new relationship IfcRelVoidsElement is generated.
IsConnectionRealizationSET [0:?] OF IfcRelConnectsWithRealizingElements FOR RealizingElementsReference to the connection relationship with realizing element. The relationship, if provided, assigns this element as the realizing element to the connection, which provides the physical manifestation of the connection relationship.
ProvidesBoundaries SET [0:?] OF IfcRelSpaceBoundary FOR RelatedBuildingElement Reference to space boundaries by virtue of the objectified relationship IfcRelSpaceBoundary. It defines the concept of an element bounding spaces.
ConnectedFrom SET [0:?] OF IfcRelConnectsElements FOR RelatedElement Reference to the element connection relationship. The relationship then refers to the other element that is connected to this element.
ContainedInStructure SET [0:1] OF IfcRelContainedInSpatialStructure FOR RelatedElements Containment relationship to the spatial structure element, to which the element is primarily associated. This containment relationship has to be hierachical, i.e. an element may only be assigned directly to zero or one spatial structure.
HasCoverings SET [0:?] OF IfcRelCoversBldgElements FOR RelatingBuildingElement Reference to IfcCovering by virtue of the objectified relationship IfcRelCoversBldgElement. It defines the concept of an element having coverings associated.
HasSurfaceFeatures INVALID Reference to the IfcRelAdheresToElement relationship that adheres a IfcSurfaceFeature to an element. An element can incorporate zero-to-many surface features in one relationship.
IfcBuiltElement
IfcBeam
9 PredefinedType OPTIONAL IfcBeamTypeEnum Predefined generic type for a beam that is specified in an enumeration. There may be a property set given specificly for the predefined types.

> NOTE  The PredefinedType shall only be used, if no IfcBeamType is assigned, providing its own _IfcBeamType.PredefinedType_.

> IFC4 CHANGE The attribute has been added at the end of the entity definition.

6.1.3.1.2 Entity inheritance

dot_inheritance IfcBeamStandardCase IfcBeamStandardCase IfcBeam IfcBeam IfcBeamStandardCase->IfcBeam IfcBuiltElement IfcBuiltElement IfcBeam->IfcBuiltElement IfcBuiltElement_children 29 more... IfcBuiltElement_children->IfcBuiltElement IfcElement IfcElement IfcBuiltElement->IfcElement IfcElement_children 10 more... IfcElement_children->IfcElement IfcProduct IfcProduct IfcElement->IfcProduct IfcProduct_children 8 more... IfcProduct_children->IfcProduct IfcObject IfcObject IfcProduct->IfcObject IfcObject_children 5 more... IfcObject_children->IfcObject IfcObjectDefinition IfcObjectDefinition IfcObject->IfcObjectDefinition IfcContext IfcContext IfcContext->IfcObjectDefinition IfcRoot IfcRoot IfcObjectDefinition->IfcRoot IfcTypeObject IfcTypeObject IfcTypeObject->IfcObjectDefinition IfcPropertyDefinition IfcPropertyDefinition IfcPropertyDefinition->IfcRoot IfcRelationship IfcRelationship IfcRelationship->IfcRoot

6.1.3.1.3 Definitions applying to General Usage

6.1.3.1.3.1 Axis 3D Geometry

The axis representation can be used to represent the system length of a beam that may extent the body length of the beam.

NOTE  The 'Axis' is used to locate the material profile set, if the material association is of type IfcMaterialProfileSetUsage.

The following additional constraints apply to the 'Axis' representation, if an IfcMaterialProfileSetUsage is provided and the 'Body' shape representation has the RepresentationType: 'SweptSolid':

 

Axis
EXAMPLE  As shown in Figure 76, the axis shall be defined along the z axis of the object coordinate system. The axis representation can be used to represent the system length of a beam that may extent the body length of the beam.

Figure 198 — Beam axis representation

 
Axis
EXAMPLE  As shown in Figure 77, the axis representation shall be used to represent the cardinal point as the offset between the 'Axis' and the extrusion path of the beam. The extrusion path is provided as IfcExtrudedAreaSolid.ExtrudedDirection and should be parallel to the 'Axis' and the z axis. It has to be guaranteed that the value provided by IfcMaterialProfileSetUsage.CardinalPoint is consistent to the IfcExtrudedAreaSolid.Position.

Figure 199 — Beam axis cardinal point

 
Items Identifier Type
'IfcBoundedCurve''Axis' 'Curve3D'

6.1.3.1.3.2 Body AdvancedBrep Geometry

An IfcElement (so far no further constraints are defined at the level of its subtypes or by view definitions) may be represented as a single or multiple boundary representation models, which include advanced surfaces, usually refered to as NURBS surfaces. The 'AdvancedBrep' representation allows for the representation of complex free-form element shape.

NOTE  View definitions or implementer agreements may restrict or disallow the use of 'AdvancedBrep' geometry.

6.1.3.1.3.3 Body AdvancedSweptSolid Geometry

The following additional constraints apply to the 'AdvancedSweptSolid' representation type:

6.1.3.1.3.4 Body Brep Geometry

Any IfcElement (so far no further constraints are defined at the level of its subtypes) may be represented as a single or multiple Boundary Representation models (which are restricted to be faceted Brep's with or without voids). The Brep representation allows for the representation of complex element shape.

 

Brep representation
EXAMPLE  As shown in Figure 150, the Brep representation is given by an IfcShapeRepresentation, which includes one or more items, all of type IfcFacetedBrep. In some cases it may be useful to also expose a simple representation as a bounding box representation of the same complex shape.

Figure 150 — Building element body boundary representation

 

6.1.3.1.3.5 Body CSG Geometry

Any IfcElement (so far no further constraints are defined at the level of its subtypes) may be represented a CSG primitive or CSG tree. The CSG representation allows for the representation of complex element shape.

NOTE  View definitions or implementer agreements may restrict or disallow the use of 'CSG' geometry.

6.1.3.1.3.6 Body Clipping Geometry

The following additional constraints apply to the 'Clipping' representation type:

  • Solid: see 'SweptSolid' geometric representation
  • Profile: see 'SweptSolid' geometric representation
  • Extrusion: see 'SweptSolid' geometric representation
  • Boolean result: The IfcBooleanClippingResult shall be supported, allowing for Boolean differences between the swept solid (here IfcExtrudedAreaSolid) and one or several IfcHalfSpaceSolid (or its subtypes).

Figure 201 illustrates use of IfcBooleanClippingResult between an IfcExtrudedAreaSolid and an IfcHalfSpaceSolid to create a clipped body.

clipped beam

Figure 201 — Beam clipping

6.1.3.1.3.7 Body SurfaceModel Geometry

Any IfcElement (so far no further constraints are defined at the level of its subtypes) may be represented as a single or multiple surface models, based on either shell or face based surface models. It may also include tessellated models.

 

surface model
EXAMPLE  As shown in Figure 149, the surface model representation is given by an IfcShapeRepresentation, which includes a single item which is either an IfcShellBasedSurfaceModel, or an IfcFaceBasedSurfaceModel. In some cases it may also be useful to expose a simple representation as a bounding box representation of the same complex shape.

Figure 149 — Element surface model representation

 

6.1.3.1.3.8 Body SurfaceOrSolidModel Geometry

Any IfcElement (so far no further constraints are defined at the level of its subtypes) may be represented as a mixed representation, including surface and solid models.

6.1.3.1.3.9 Body SweptSolid Geometry

The following additional constraints apply to the 'SweptSolid' representation type:

Figure 200 illustrates the 'SweptSolid' geometric representation. There are no restrictions or conventions on how to use the local placement (black), solid of extrusion placement (red) and profile placement (green).

standard beam

Figure 200 — Beam swept solid

Figure 201 illustrates the use of non-perpendicular extrusion to create the IfcExtrudedAreaSolid.

non-perpendicular extrusion

Figure 201 — Beam non-perpendicular extrusion

6.1.3.1.3.10 Body Tessellation Geometry

Any IfcElement (so far no further constraints are defined at the level of its subtypes) may be represented as a single or multiple tessellated surface models, in particular triangulated surface models.

6.1.3.1.3.11 Box Geometry

bounding box
EXAMPLE  Any IfcElement may be represented by a bounding box, which shows the maximum extend of the body within the object coordinate system established by the IfcObjectPlacement. As shown in Figure 148, the bounding box representation is given by an IfcShapeRepresentation that includes a single item, an IfcBoundingBox.

Figure 148 — Building element box representation

 

6.1.3.1.3.12 Classification Association

Any object occurrence or object type can have a reference to a specific classification reference, i.e. to a particular facet within a classification system.

6.1.3.1.3.13 CoG Geometry

The 'CoG', Center of Gravity, shape representation is used as a means to verify the correct import by comparing the CoG of the imported geometry with the explicily provided CoG created during export.

6.1.3.1.3.14 Element Composition

6.1.3.1.3.15 Element Projecting

6.1.3.1.3.16 Element Voiding

6.1.3.1.3.17 FootPrint Geometry

Identifier Type
'FootPrint' 'GeometricCurveSet'
'FootPrint' 'Annotation2D'

6.1.3.1.3.18 Identity

IfcRoot assigns the globally unique ID. In addition it may provide for a name and a description about the concept.

6.1.3.1.3.19 Mapped Geometry

Any IfcElement (so far no further constraints are defined at the level of its subtypes) may be represented using the 'MappedRepresentation'. This shall be supported as it allows for reusing the geometry definition of a type at all occurrences of the same type. The results are more compact data sets.

The same constraints, as given for 'SurfaceOrSolidModel', 'SurfaceModel', 'Tessellation', 'Brep', and 'AdvancedBrep' geometric representation, shall apply to the IfcRepresentationMap.

6.1.3.1.3.20 Material Profile Set

The material information of the IfcBeam is defined by IfcMaterialProfileSet or as fallback by IfcMaterial, and it is attached either directly or at the IfcBeamType. In this case, the material information does not allow to construct a shape by applying the profile definition to the axis representation, to enable this parametric definition, the IfcMaterialProfileSetUsage has to be used instead.

6.1.3.1.3.21 Material Profile Set Usage

The Material Profile Set Usage defines the assignment of an IfcMaterialProfileSetUsage to the IfcBeamType providing a common profile definition to all occurrences of this IfcBeamType. Beams with composite profile can be represented by refering to several IfcMaterialProfile's within the IfcMaterialProfileSet that is referenced from the IfcMaterialProfileSetUsage.

Material profile set and usage
EXAMPLE  Figure 196 illustrates assignment of IfcMaterialProfileSetUsage and IfcMaterialProfileSet to the IfcBeam as the beam occurrence and to the IfcBeamType. The same IfcMaterialProfileSet shall be shared by many occurrences of IfcMaterialProfileSetUsage. This relationship shall be consistent to the relationship between the IfcBeamType and the IfcBeam.

Figure 196 — Beam profile usage

 
Cardinal point usage
EXAMPLE  Figure 197 illustrates alignment of cardinal points.
NOTE  It has to be guaranteed that the use of IfcCardinalPointEnum is consistent to the placement of the extrusion body provided by IfcExtrudedAreaSolid.Position
NOTE  The cardinal points 8 (top centre) and 6 (mid-depth right) are assigned according to the definition at IfcCardinalPointReference

Figure 197 — Beam cardinal points

 
Material profile set and usage
EXAMPLE  Figure 198 illustrates assignment of a composite profile by using IfcCompositeProfile for geometric representation and several IfcMaterialProfile's within the IfcMaterialProfileSet.

Figure 198 — Beam composite profiles

6.1.3.1.3.22 Object Predefined Type

6.1.3.1.3.23 Object Typing

RelatingType
'IfcBeamType'

6.1.3.1.3.24 Object User Identity

An attribute Name and optionally Description can be used for all subypes of IfcObject. For those subtypes, that have an object type definition, such as ifcBeam - IfcBeamType, the common Name and optionally Description is associated with the object type.

6.1.3.1.3.25 Product Geometric Representation

The geometric representation of any IfcProduct is provided by the IfcProductDefinitionShape allowing multiple geometric representations. It uses the Product Placement concept utilizing IfcLocalPlacement to establish an object coordinate system, within all geometric representations are founded.

NOTE  A detailed specification of how to apply the local placement and which shape representaions are applicable is provided at the level of subtypes of IfcProduct and is further determined by the model view definition and implementer agreements.

6.1.3.1.3.26 Product Local Placement

The object placement for any subtype of IfcElement is defined by the IfcObjectPlacement, either IfcLocalPlacement or IfcGridPlacement, which defines the local object coordinate system that is referenced by all geometric representations of that IfcElement.

HasPlacement
'IfcLocalPlacement'
'IfcLocalPlacement'

6.1.3.1.3.27 Product Placement

The Product Placement establishes the object coordinate system and is required, if a geometric shape representation is provided for this product.

6.1.3.1.3.28 Property Sets for Objects

PsetName
'Pset_BeamCommon'
'Pset_ConcreteElementGeneral'
'Pset_PrecastConcreteElementFabrication'
'Pset_PrecastConcreteElementGeneral'
'Pset_ReinforcementBarPitchOfBeam'
'Pset_EnvironmentalImpactIndicators'
'Pset_EnvironmentalImpactValues'
'Pset_Condition'
'Pset_ManufacturerOccurrence'
'Pset_ManufacturerTypeInformation'
'Pset_ServiceLife'
'Pset_Warranty'

6.1.3.1.3.29 Property Sets with Override

Any object occurrence can hold property sets, either directly at the object occurrence as element specific property sets, or at the object type, as type property sets. In this case, the properties that are provided to the object occurrence are the combinations of element specific and type properties. In case, that the same property (within the same property set, is defined both, in occurrence and type properties, the property value of the occurrence property overrides the property value of the type property.

6.1.3.1.3.30 Quantity Sets

QsetName
'Qto_BeamBaseQuantities'

6.1.3.1.3.31 Revision Control

Ownership, history, and merge state is captured using IfcOwnerHistory.

6.1.3.1.3.32 Spatial Containment

The IfcBeam, as any subtype of IfcBuildingElement, may participate alternatively in one of the two different containment relationships:

  • the Spatial Containment (defined here), or
  • the Element Composition.
RelatingStructure
'IfcBuildingStorey'
'IfcBuilding'
'IfcSite'

6.1.3.1.4 Formal representations

ENTITY IfcBeam
 SUPERTYPE OF (ONEOF
	(IfcBeamStandardCase))
 SUBTYPE OF (IfcBuiltElement);
	PredefinedType : OPTIONAL IfcBeamTypeEnum;
 WHERE
	CorrectPredefinedType : NOT(EXISTS(PredefinedType)) OR
 (PredefinedType <> IfcBeamTypeEnum.USERDEFINED) OR
 ((PredefinedType = IfcBeamTypeEnum.USERDEFINED) AND EXISTS (SELF\IfcObject.ObjectType));
	CorrectTypeAssigned : (SIZEOF(IsTypedBy) = 0) OR
  ('IFC4X3_DEV.IFCBEAMTYPE' IN TYPEOF(SELF\IfcObject.IsTypedBy[1].RelatingType));
END_ENTITY;