IFC 4.4.0.0 build 20261005 (IFC4X4_DEV_20260525) ⚠ buildingSMART Working Draft. All content is under development.

  • Help suggest improvements
  • Get user or developer support

5.4.3.51 IfcRelConnectsWithRealizingElements

5.4.3.51.1 Semantic definition

IfcRelConnectsWithRealizingElements defines a generic relationship that is made between two elements that require the realization of that relationship by means of further realizing elements.

An IfcRelConnectsWithRealizingElements is a specialization of IfcRelConnectsElements where the connecting operation has the additional attribute of (one or many) realizing elements that may be used to realize or further qualify the relationship. It is defined as a ternary relationship.

The connection types for bridges include:

  • TrussJoint: Joint between truss members.
  • ExpansionJoint: Joint allowing movement, usually due to thermal expansion difference in structures, with DiscreteAccessory of type EXPANSION_JOINT_DEVICE as RealizingElement.
  • EmbeddedPartsJoint: Joint for auxiliary parts to structure, with appropriate RealizingElements, such as DiscreteAccessories of type ANCHORPLATE, BRACKET or SHOE.
  • ConstructionJoint: Joint for phasing of construction, typically in in-situ concrete structures.

5.4.3.51.2 Entity inheritance

5.4.3.51.3 Attributes

# Attribute Type Description
IfcRoot (4)
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.

3 Name OPTIONAL IfcLabel

An 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

An optional description, provided to exchange informative comments.

IfcRelConnectsElements (3)
5 ConnectionGeometry OPTIONAL IfcConnectionGeometry

The geometric shape representation of the connection geometry that is provided in the object coordinate system of the RelatingElement (mandatory) and in the object coordinate system of the RelatedElement (optionally).

6 RelatingElement IfcElement

Reference to a subtype of IfcElement that is connected by the connection relationship in the role of RelatingElement.

7 RelatedElement IfcElement

Reference to a subtype of IfcElement that is connected by the connection relationship in the role of RelatedElement.

Click to show 7 hidden inherited attributes Click to hide 7 inherited attributes
IfcRelConnectsWithRealizingElements (2)
8 RealizingElements SET [1:?] OF IfcElement

Defines the elements that realize a connection relationship.

9 ConnectionType OPTIONAL IfcLabel

The type of the connection given for informal purposes, it may include labels, like 'joint', 'rigid joint', 'flexible joint', etc.

Table A

5.4.3.51.4 Concept usage

Concept Usage Description
IfcRoot (2)
Revision Control General

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

Software Identity General

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

Click to show 2 hidden inherited concepts Click to hide 2 inherited concepts
Table B

5.4.3.51.5 Formal representation

ENTITY IfcRelConnectsWithRealizingElements
SUBTYPE OF (IfcRelConnectsElements);
RealizingElements : SET [1:?] OF IfcElement;
ConnectionType : OPTIONAL IfcLabel;
END_ENTITY;

5.4.3.51.6 References

Edit on Github

4 contributor(s): ArturTomczakDion MoultThomas KrijnenbSI-Bot
Last change: Improve definition split (#876) * bring back headers headers were previously removed by mistake, now bringing them back * add new lines and rename the tag add the word 'short' in it * unify newlines make exactly one newline before and two after the tag * resolving typos Because bringing back headers required to go back in time to previous version, I'm now re-resolving the issues: #861, #860, #856 by ArturTomczak on 2024-07-16T16:07:28+02:00

Is this page difficult to understand? Let us know!