The decomposition relationship, IfcRelDecomposes, defines the general concept of elements being composed or decomposed. The decomposition relationship denotes a whole/part hierarchy with the ability to navigate from the whole (the composition) to the parts and vice versa.
Decompositions may be constrained by requiring both, the whole and its parts, to be of the same type - thus establishing a nesting relationship. Or they may require some form of physical containment, thus establishing special types of aggregation relationships.
NOTE There are two special names for decomposition, which are linguistically distinguished, nesting and aggregation. The subtypes of IfcRelDecomposes will introduce either the nesting or aggregation convention (see IfcRelNests and IfcRelAggregates).
EXAMPLE A cost element is a nest of other cost elements. Or a structural frame is an aggregation of beams and columns. Both are applications of decomposition relationship.
Decompositions imply a dependency, i.e. the definition of the whole depends on the definition of the parts and the parts depend on the existence of the whole. The decomposition relationship can be applied in a recursive manner, i.e. a decomposed element can be part in another decomposition. Cyclic references have to be prevented at application level.
HISTORY New entity in IFC1.5, it is a generalisation of the IFC2.0 entity IfcRelNests.
IFC4 CHANGE The differentiation between the aggregation and nesting is determined to be a non-ordered or an ordered collection of parts. The attributes RelatingObject and RelatedObjects have been demoted to the subtypes.
|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.|
IfcRoot assigns the globally unique ID. In addition it may provide for a name and a description about the concept.
Ownership, history, and merge state is captured using IfcOwnerHistory.
ENTITY IfcRelDecomposes ABSTRACT SUPERTYPE OF (ONEOF (IfcRelAdheresToElement ,IfcRelAggregates ,IfcRelNests ,IfcRelProjectsElement ,IfcRelVoidsElement)) SUBTYPE OF (IfcRelationship); END_ENTITY;