|Elément de distribution|
|haustechnische Komponente (allgemein) |
This entity is a generalization of all elements
that participate in a distribution system. Typical examples
of IfcDistributionElement are (among others):
- building service elements within a heating systems
- building service elements within a cooling system
- building service elements within a ventilation system
- building service elements within a plumbing system
- electrical elements
- elements within a communication network
The IfcDistributionElement is further specialized in
the IFC model. Direct instantiation of
IfcDistributionElement without an assigned subtype of
IfcDistributionElementType provides the meaning of an
distribution element proxy.
HISTORY New entity in IFC1.5.
IFC4 CHANGE The entity is
marked as deprecated for instantiation - will be made
ABSTRACT in future releases.
Common Use Definitions
The following concepts are inherited at supertypes:
- IfcRoot: Identity, Revision Control
- IfcElement: Product Placement, Box Geometry, FootPrint Geometry, Body SurfaceOrSolidModel Geometry, Body SurfaceModel Geometry, Body Tessellation Geometry, Body Brep Geometry, Body AdvancedBrep Geometry, Body CSG Geometry, Mapped Geometry
The Object Typing concept applies to this entity as shown in Table 40.
Table 40 — IfcDistributionElement Object Typing
The IfcDistributionElement defines the occurrence of
any HVAC, electrical, sanitary or other element within a
distribution system. Common information about distribution
element types (or styles) is handled by subtypes of
IfcDistributionElementType (if present) may establish
the common type name, usage (or predefined) type, common
material, common set of properties and common shape
representations (using IfcRepresentationMap). The
IfcDistributionElementType is attached using the
relationship and is accessible by the inverse
The assignment of types to distribution element occurrences
is vital for providing the additional meaning, or ontology,
of the distribution element. Many specialized type are
defined in other schemas of this specification.
Property Sets for Objects
The Property Sets for Objects concept applies to this entity as shown in Table 41.
Table 41 — IfcDistributionElement Property Sets for Objects
The Quantity Sets concept applies to this entity.
The quantities relating to the IfcDistributionElement
are defined by the IfcElementQuantity and attached by
the IfcRelDefinesByProperties. A detailed
specification for individual quantities is introduced at the
level of subtypes of IfcDistributionElement.
The Spatial Containment concept applies to this entity as shown in Table 42.
Table 42 — IfcDistributionElement Spatial Containment
The IfcDistributionElement may participate in two
different containment relationships. The first (and in most
implementation scenarios mandatory) relationship is the
hierachical spatial containment, the second (optional)
relationship is the aggregation within an element
- The IfcDistributionElement is places within the
project spatial hierarchy using the objectified relationship
IfcRelContainedInSpatialStructure, referring to it by
its inverse attribute
of IfcSpatialStructureElement are valid spatial
containers, with IfcSpace being the default container.
- The IfcDistributionElement may be aggregated into
an element assembly using the objectified relationship
IfcRelAggregates, referring to it by its inverse
attribute SELF\IfcObjectDefinition.Decomposes. Any
subtype of IfcElement can be an element assembly, with
IfcElementAssembly as a special focus subtype. In this
case it should not be additionally contained in the project
i.e. SELF\IfcElement.ContainedInStructure should
XSD Specification: <xs:element name="IfcDistributionElement" type="ifc:IfcDistributionElement" substitutionGroup="ifc:IfcElement" nillable="true"/>
|HasPorts|| : ||
Reference to the element to port connection relationship. The relationship then refers to the port which is contained in this element.
IFC4 CHANGE The inverse attribute is deprecated. Relationship to ports, contained within the IfcDistributionElement is now realized by the inverse relationship NestedBy referencing IfcRelNests.
Link to this page