IFC 4.3.0.1 (IFC4X3) development

4.3.4.1 Element Type Predefined Type

If a custom value is needed to describe a physical object type, the attribute ElementType may be used to define such custom type, where the PredefinedType is set to USERDEFINED.

Physical element types may be further identified via the Tag attribute. This is a human readable identifier such as an element or item number. While there is no restriction on usage of such tags, it is recommended the Tag is unique within it's containing scope.

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 tables below shows a recommended list of general usage patterns that users may adopt.

G IfcElementType IfcElementType 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:?] 5. ApplicableOccurrence [0:1] 6. HasPropertySets [1:?]      Types [0:1] 7. RepresentationMaps [1:?] 8. Tag [0:1]      ReferencedBy [0:?] 9. ElementType [0:1] IfcLabel_0 IfcLabel IfcElementType:ElementType1->IfcLabel_0:IfcLabel0 IfcLabel_1 IfcLabel IfcElementType:Tag1->IfcLabel_1:IfcLabel0
Figure 4.3.4.1.A

General Usage

ApplicableEntity
IfcElementType
Table 4.3.4.1.B

Edit on Github


Is this page difficult to understand? Let us know!