IfcDistributionSystem

Natural language names
haustechnische Anlage
Distribution System
Système de distribution
Change log
ItemSPFXMLChangeDescription
IFC2x3 to IFC4 4.0.0.0
    IfcDistributionSystemADDED
IFC2x3 to IFC4 4.0.0.0
    IfcDistributionSystemADDED
IFC4x2 to IFC4x3_RC1
    IfcDistributionSystem
      ServicesFacilitiesADDED
Semantic definitions at the entity
Entity definition

A distribution system is a network designed to receive, store, maintain, distribute, or control the flow of a distribution media. A common example is a heating hot water system that consists of a pump, a tank, and an interconnected piping system for distributing hot water to terminals.
The group IfcDistributionSystem defines the occurrence of a specialized system for use within the context of building services or utilities for built facilities.
Important functionalities for the description of a distribution system are derived from existing IFC entities:

HISTORY New entity in IFC4.

Attribute definitions
#AttributeTypeCardinalityDescription G
6LongNameIfcLabel? Long name for a distribution system, used for informal purposes. It should be used, if available, in conjunction with the inherited Name attribute.\X\0D
NOTE  In many scenarios the Name attribute refers to the short name or number of a distribution system or branch circuit, and the LongName refers to a descriptive name.
X
7PredefinedTypeIfcDistributionSystemEnum? X
Inherited definitions from supertypes
Entity inheritance IfcDistributionCircuit IfcSystem IfcGroup IfcObject IfcObjectDefinition IfcRoot
Attribute inheritance
#AttributeTypeCardinalityDescriptionG
IfcRoot
1GlobalIdIfcGloballyUniqueId Assignment of a globally unique identifier within the entire software world. X
2OwnerHistoryIfcOwnerHistory? 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.
X
3NameIfcLabel? 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. X
4DescriptionIfcText? Optional description, provided for exchanging informative comments. X
IfcObjectDefinition
HasAssignmentsIfcRelAssigns
@RelatedObjects
S[0:?]Reference to the relationship objects, that assign (by an association relationship) other subtypes of IfcObject to this object instance. Examples are the association to products, processes, controls, resources or groups. X
NestsIfcRelNests
@RelatedObjects
S[0:1]References to the decomposition relationship being a nesting. It determines that this object definition is a part within an ordered whole/part decomposition relationship. An object occurrence or type can only be part of a single decomposition (to allow hierarchical strutures only).
IFC4 CHANGE  The inverse attribute datatype has been added and separated from Decomposes defined at IfcObjectDefinition.
X
IsNestedByIfcRelNests
@RelatingObject
S[0:?]References to the decomposition relationship being a nesting. It determines that this object definition is the whole within an ordered whole/part decomposition relationship. An object or object type can be nested by several other objects (occurrences or types).
IFC4 CHANGE  The inverse attribute datatype has been added and separated from IsDecomposedBy defined at IfcObjectDefinition.
X
HasContextIfcRelDeclares
@RelatedDefinitions
S[0:1]References to the context providing context information such as project unit or representation context. It should only be asserted for the uppermost non-spatial object.
IFC4 CHANGE  The inverse attribute datatype has been added.
X
IsDecomposedByIfcRelAggregates
@RelatingObject
S[0:?]References to the decomposition relationship being an aggregation. It determines that this object definition is whole within an unordered whole/part decomposition relationship. An object definitions can be aggregated by several other objects (occurrences or parts).
IFC4 CHANGE  The inverse attribute datatype has been changed from the supertype IfcRelDecomposes to subtype IfcRelAggregates.
X
DecomposesIfcRelAggregates
@RelatedObjects
S[0:1]References to the decomposition relationship being an aggregation. It determines that this object definition is a part within an unordered whole/part decomposition relationship. An object definitions can only be part of a single decomposition (to allow hierarchical strutures only).
IFC4 CHANGE  The inverse attribute datatype has been changed from the supertype IfcRelDecomposes to subtype IfcRelAggregates.
X
HasAssociationsIfcRelAssociates
@RelatedObjects
S[0:?]Reference to the relationship objects, that associates external references or other resource definitions to the object.. Examples are the association to library, documentation or classification. X
IfcObject
5ObjectTypeIfcLabel? The type denotes a particular type that indicates the object further. The use has to be established at the level of instantiable subtypes. In particular it holds the user defined type, if the enumeration of the attribute PredefinedType is set to USERDEFINED. X
IsDeclaredByIfcRelDefinesByObject
@RelatedObjects
S[0:1]Link to the relationship object pointing to the declaring object that provides the object definitions for this object occurrence. The declaring object has to be part of an object type decomposition. The associated IfcObject, or its subtypes, contains the specific information (as part of a type, or style, definition), that is common to all reflected instances of the declaring IfcObject, or its subtypes.
IFC4 CHANGE  New inverse relationship, change made with upward compatibility for file based exchange.
X
DeclaresIfcRelDefinesByObject
@RelatingObject
S[0:?]Link to the relationship object pointing to the reflected object(s) that receives the object definitions. The reflected object has to be part of an object occurrence decomposition. The associated IfcObject, or its subtypes, provides the specific information (as part of a type, or style, definition), that is common to all reflected instances of the declaring IfcObject, or its subtypes.
IFC4 CHANGE  New inverse relationship, change made with upward compatibility for file based exchange.
X
IsTypedByIfcRelDefinesByType
@RelatedObjects
S[0:1]Set of relationships to the object type that provides the type definitions for this object occurrence. The then associated IfcTypeObject, or its subtypes, contains the specific information (or type, or style), that is common to all instances of IfcObject, or its subtypes, referring to the same type.
IFC4 CHANGE  New inverse relationship, the link to IfcRelDefinesByType had previously be included in the inverse relationship IfcRelDefines. Change made with upward compatibility for file based exchange.
X
IsDefinedByIfcRelDefinesByProperties
@RelatedObjects
S[0:?]Set of relationships to property set definitions attached to this object. Those statically or dynamically defined properties contain alphanumeric information content that further defines the object.
IFC4 CHANGE  The data type has been changed from IfcRelDefines to IfcRelDefinesByProperties with upward compatibility for file based exchange.
X
IfcGroup
IsGroupedByIfcRelAssignsToGroup
@RelatingGroup
S[0:?]Reference to the relationship IfcRelAssignsToGroup that assigns the one to many group members to the IfcGroup object.
IFC4 CHANGE  The cardinality has been changed from 1..1 to 0..? in order to allow the exchange of a group concept without having already group members assigned. It now also allows the use of many instances of IfcRelAssignsToGroup to assign the group members. The change has been done with upward compatibility for file based exchange.
X
IfcSystem
ServicesBuildingsIfcRelServicesBuildings
@RelatingSystem
S[0:1]Reference to the building spatial structure via the objectified relationship IfcRelServicesBuildings, which is serviced by the system. X
ServicesFacilitiesIfcRelReferencedInSpatialStructure
@RelatedElements
S[0:?]X
IfcDistributionSystem
6LongNameIfcLabel? Long name for a distribution system, used for informal purposes. It should be used, if available, in conjunction with the inherited Name attribute.\X\0D
NOTE  In many scenarios the Name attribute refers to the short name or number of a distribution system or branch circuit, and the LongName refers to a descriptive name.
X
7PredefinedTypeIfcDistributionSystemEnum? X
Definitions applying to General Usage

 Instance diagram


Concept usage

Property Sets for Objects

The Property Sets for Objects concept template applies to this entity as shown in Table 232.

PsetNameProperties
Pset_DistributionSystemCommon
TemplatePropertyNameValue
Single ValueReferenceIfcIdentifier

Table 232 — IfcDistributionSystem Property Sets for Objects



Aggregation

The Aggregation concept template applies to this entity as shown in Table 233.

Table 233 — IfcDistributionSystem Aggregation



Group Assignment

The Group Assignment concept template applies to this entity as shown in Table 234.

IsGroupedRelatedObjectsDescription
Indicates devices that are part of the system, where any ports of the same PredefinedType are considered part of the system implicitly.

Table 234 — IfcDistributionSystem Group Assignment

For the most common case of an IfcDistributionElement subtype containing ports of a particular PredefinedType that all belong to the same distribution system, the IfcDistributionElement is assigned to the IfcDistributionSystem via the IfcRelAssignsToGroup relationship, where IfcDistributionPort's are implied as part of the corresponding system based on their PredefinedType. An IfcDistributionElement may belong to multiple systems, however only one IfcDistributionSystem of a particular PredefinedType.

For rare cases where an IfcDistributionElement subtype contains ports of the same PredefinedType yet different ports belong to different systems, alternatively each IfcDistributionPort may be directly assigned to a single IfcDistributionSystem via the IfcRelAssignsToGroup relationship, where the PredefinedType must match. Such assignment indicates that the IfcDistributionSystem assigned from the IfcDistributionPort overrides any such system of the same PredefinedType assigned from the containing IfcDistributionElement, if any.

Additionally, an IfcDistributionSystem may in turn be assigned to an IfcDistributionPort indicating the host or origination of the system using IfcRelAssignsToProduct.

EXAMPLE  A gas-powered hot water heater may have three ports: GAS, DOMESTICCOLDWATER, and DOMESTICHOTWATER. The heater is a member of two systems (GAS and DOMESTICCOLDWATER), and hosts one system (DOMESTICHOTWATER) at the corresponding port.

Figure 269 illustrates a distribution system for an electrical circuit.

"Instance diagram for electrical circuit"

Figure 269 — Distribution system assignment



mvdXML Specification
<?xml version="1.0" encoding="utf-8"?>
<ConceptRoot xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" uuid="afe1b96a-7618-4ce7-8b0f-fb6d9546f3d0" name="IfcDistributionSystem" applicableRootEntity="IfcDistributionSystem">
 <Applicability>
  <Template ref="49e4352b-1839-4446-82ec-24d742768f1e" />
  <TemplateRules operator="and">
  </TemplateRules>
 </Applicability>
 <Concepts>
  <Concept uuid="11816ae1-f077-4e15-997b-5bac26230c79" name="Property Sets for Objects">
   <Template ref="f74255a6-0c0e-4f31-84ad-24981db62461" />
   <TemplateRules operator="and">
    <TemplateRule Parameters="PsetName[Value]=&apos;Pset_DistributionSystemCommon&apos;" />
   </TemplateRules>
  </Concept>
  <Concept uuid="283ea9eb-dbd3-448c-afad-3303fd84c942" name="Aggregation">
   <Template ref="02eefcc6-b26c-4f20-9c7c-c30ae74eb9a9" />
   <TemplateRules operator="and">
    <TemplateRule Description="Indicates electrical subsystems within the system." />
    <TemplateRule Description="Indicates electrical circuits within the system." />
   </TemplateRules>
  </Concept>
  <Concept uuid="d7d0722e-99d6-45dc-b2b9-78948910f1d7" name="Group Assignment">
   <Template ref="f567967f-5493-44d9-ac51-937c09ac2583" />
   <TemplateRules operator="and">
    <TemplateRule Description="Indicates devices that are part of the system, where any ports of the same PredefinedType are considered part of the system implicitly." />
    <TemplateRule Description="Indicates port that is explicitly part of the system, which overrides any system assignment of the containing device." />
   </TemplateRules>
  </Concept>
 </Concepts>
</ConceptRoot>
Concept inheritance

#ConceptTemplateModel View
IfcRoot
IdentitySoftware IdentityGeneral Usage
Revision ControlRevision ControlGeneral Usage
IfcObjectDefinition
Classification AssociationClassification AssociationGeneral Usage
IfcObject
Object User IdentityObject User IdentityGeneral Usage
Object Predefined TypeObject Predefined TypeGeneral Usage
Object TypingObject TypingGeneral Usage
Property Sets with OverrideProperty Sets with OverrideGeneral Usage
IfcDistributionSystem
Property Sets for ObjectsProperty Sets for ObjectsGeneral Usage
AggregationAggregationGeneral Usage
Group AssignmentGroup AssignmentGeneral Usage
Formal representations
XML Specification
 <xs:element name="IfcDistributionSystem" type="ifc:IfcDistributionSystem" substitutionGroup="ifc:IfcSystem" nillable="true"/>
 <xs:complexType name="IfcDistributionSystem">
  <xs:complexContent>
   <xs:extension base="ifc:IfcSystem">
    <xs:attribute name="LongName" type="ifc:IfcLabel" use="optional"/>
    <xs:attribute name="PredefinedType" type="ifc:IfcDistributionSystemEnum" use="optional"/>
   </xs:extension>
  </xs:complexContent>
 </xs:complexType>
EXPRESS Specification
ENTITY IfcDistributionSystem
 SUPERTYPE OF(IfcDistributionCircuit)
 SUBTYPE OF (IfcSystem);
  LongName : OPTIONAL IfcLabel;
  PredefinedType : OPTIONAL IfcDistributionSystemEnum;
END_ENTITY;

Link to EXPRESS-G diagram EXPRESS-G diagram

Link to this page  Link to this page