IFC 4.3.2.20241204 (IFC4X3_ADD2) under development

4.1.4.1 Aggregation

An aggregation indicates an internal unordered part composition relationship between the whole structure, referred to as the "composite", and the subordinate components, referred to as the "parts". The concept of aggregation is used in various ways. Examples are:

  • Aggregation is used on building elements to indicate parts such as studs within a wall;
  • Aggregation is used on spatial elements to indicate a spatial structure such as a storey within a building;
  • Aggregation is used on systems to indicate subsystems such as branch circuits.

Aggregation is a bi-directional relationship, the relationship from the composite to its parts is called Decomposition, and the relationship from the part to its composite is called Composition.

The following diagram shows the generic classes and relationships used when applying this concept. In addition, concepts may have particular importance to common or standardised industry practices and scenarios. For these specific usage scenarios, the table below shows a recommended list of general usage patterns that users may adopt.

G IfcObjectDefinition IfcObjectDefinition 1. GlobalId [1:1] 2. OwnerHistory [0:1] 3. Name [0:1] 4. Description [0:1]      HasAssignments [0:?]      Nests [0:1]      IsNestedBy [0:?]      HasContext [0:1]      IsDecomposedBy [0:?]      Decomposes [0:1]      HasAssociations [0:?] IfcRelAggregates IfcRelAggregates 1. GlobalId [1:1] 2. OwnerHistory [0:1] 3. Name [0:1] 4. Description [0:1] 5. RelatingObject [1:1] 6. RelatedObjects [1:?] IfcObjectDefinition:IsDecomposedBy1->IfcRelAggregates:RelatingObject0
Figure 4.1.4.1.A

General Usage

ApplicableEntity
IfcObjectDefinition
Table 4.1.4.1.B

Edit on Github


Is this page difficult to understand? Let us know!