6.2.2.3 IfcDistributionSystemEnum

This enumeration identifies different types of distribution systems. It is used to designate systems by their function as well as ports of devices within such systems to restrict connectivity to compatible connections.

HISTORY  New enumeration in IFC4.

Enumerated Item Definitions:

Pipe-based systems and ports

Ports for pipes may be connected using IfcPipeSegment and IfcPipeFitting. Type objects for pipe segments and fittings (IfcPipeSegmentType and IfcPipeFittingType) that are not specific to a particular system type may have ports with PredefinedType of NOTDEFINED which indicates that occurrences of such objects may connect to any other pipe-based port (but not cable-based or duct-based). Upon connection to a device within a system, then such port should have its PredefinedType set to that of the connecting port.

EXAMPLE  An IfcPipeSegmentType may be designated as NOTDEFINED, as it may support hot water, cold water, or any other fluid. When an instance of a pipe is instantiated in a building, then it may be connected to any other pipe-based port (using either a pipe-based enumeration or NOTDEFINED). Upon connection within a building, then such port should be marked according to its use such as DOMESTICCOLDWATER.

Valid enumerations for pipes and related elements include:

NOTE  Drainage systems that receive sources from multiple types should be designated according to priority in the following order: RAINWATER, STORMWATER, DRAINAGE, SEWAGE, WASTEWATER, HAZARDOUS. For example, a WASTEWATER system may have SEWAGE as a source but not HAZARDOUS (in the absense of treatment equipment in between).

Duct-based systems and ports

Ports for ducts may be connected using IfcDuctSegment and IfcDuctFitting. Type objects for duct segments and fittings (IfcDuctSegmentType and IfcDuctFittingType that are not specific to a particular system type may have ports with PredefinedType of NOTDEFINED which indicates that occurrences of such objects may connect to any other duct-based port (but not pipe-based or cable-based). Upon connection to a device within a system, then such port should have its PredefinedType set to that of the connecting port.

EXAMPLE  An IfcDuctSegmentType may be designated as NOTDEFINED, as it may support air conditioning, recirculation, or exhaust. When an instance of a duct is instantiated in a building, then it may be connected to any other duct-based port (using either a duct-based enumeration or NOTDEFINED). Upon connection within a building, then such port should be marked according to its use such as AIRCONDITIONING.

Valid enumerations for ducts and related elements include:

NOTE  Ducts, equipment, and diffusers on the supply side (whether for heating, cooling, and/or air circulation) are considered AIRCONDITIONING; return air terminals, outside air intakes, ducts, and equipment for air that may be recirculated or exhausted are considered VENTILATION; return air terminals, ducts, and equipment for air that must be exhausted are considered EXHAUST.

Cable-based systems and ports

Ports for cables may be connected using IfcCableSegment and IfcCableFitting. Type objects for cable segments and fittings (IfcCableSegmentType and IfcCableFittingType that are not specific to a particular system type may have ports with PredefinedType of NOTDEFINED which indicates that occurrences of such objects may connect to any other cable-based port (but not pipe-based or duct-based). Upon connection to a device within a system, then such port should have its PredefinedType set to that of the connecting port.

EXAMPLE  An IfcCableSegmentType for CAT-5 wiring may be designated as NOTDEFINED, as it may support transporting telephone, audio-visual, generic data, or even power. When an instance of a cable is instantiated in a building, then it may be connected to any other cable-based port (using either a cable-based enumeration or NOTDEFINED). Upon connection within a building, then such port should be marked according to its use such as DATA.

Valid enumerations for cables and related elements include:

NOTE  Cable ports used for communication do not necessarily require physical connection; they may also take the form of wireless radio transmission.

Cable Carriers

Ports for cable carriers may be connected using IfcCableCarrierSegment and IfcCableCarrierFitting. Type objects for cable carrier segments and fittings (IfcCableCarrierSegmentType and IfcCableCarrierFittingType that are not specific to a particular system type may have ports with PredefinedType of NOTDEFINED which indicates that occurrences of such objects may connect to ports of any other cable-carrier based port. Valid enumerations for cable carriers are the same as that for cables, and may be asserted if ports of the contained cables are all of the same type.

XSD Specification:

 <xs:simpleType name="IfcDistributionSystemEnum">
  <xs:restriction base="xs:string">
   <xs:enumeration value="airconditioning"/>
   <xs:enumeration value="audiovisual"/>
   <xs:enumeration value="chemical"/>
   <xs:enumeration value="chilledwater"/>
   <xs:enumeration value="communication"/>
   <xs:enumeration value="compressedair"/>
   <xs:enumeration value="condenserwater"/>
   <xs:enumeration value="control"/>
   <xs:enumeration value="conveying"/>
   <xs:enumeration value="data"/>
   <xs:enumeration value="disposal"/>
   <xs:enumeration value="domesticcoldwater"/>
   <xs:enumeration value="domestichotwater"/>
   <xs:enumeration value="drainage"/>
   <xs:enumeration value="earthing"/>
   <xs:enumeration value="electrical"/>
   <xs:enumeration value="electroacoustic"/>
   <xs:enumeration value="exhaust"/>
   <xs:enumeration value="fireprotection"/>
   <xs:enumeration value="fuel"/>
   <xs:enumeration value="gas"/>
   <xs:enumeration value="hazardous"/>
   <xs:enumeration value="heating"/>
   <xs:enumeration value="lighting"/>
   <xs:enumeration value="lightningprotection"/>
   <xs:enumeration value="municipalsolidwaste"/>
   <xs:enumeration value="oil"/>
   <xs:enumeration value="operational"/>
   <xs:enumeration value="powergeneration"/>
   <xs:enumeration value="rainwater"/>
   <xs:enumeration value="refrigeration"/>
   <xs:enumeration value="security"/>
   <xs:enumeration value="sewage"/>
   <xs:enumeration value="signal"/>
   <xs:enumeration value="stormwater"/>
   <xs:enumeration value="telephone"/>
   <xs:enumeration value="tv"/>
   <xs:enumeration value="vacuum"/>
   <xs:enumeration value="vent"/>
   <xs:enumeration value="ventilation"/>
   <xs:enumeration value="wastewater"/>
   <xs:enumeration value="watersupply"/>
   <xs:enumeration value="userdefined"/>
   <xs:enumeration value="notdefined"/>
  </xs:restriction>
 </xs:simpleType>

EXPRESS Specification:

TYPE IfcDistributionSystemEnum = ENUMERATION OF (
AIRCONDITIONING,
AUDIOVISUAL,
CHEMICAL,
CHILLEDWATER,
COMMUNICATION,
COMPRESSEDAIR,
CONDENSERWATER,
CONTROL,
CONVEYING,
DATA,
DISPOSAL,
DOMESTICCOLDWATER,
DOMESTICHOTWATER,
DRAINAGE,
EARTHING,
ELECTRICAL,
ELECTROACOUSTIC,
EXHAUST,
FIREPROTECTION,
FUEL,
GAS,
HAZARDOUS,
HEATING,
LIGHTING,
LIGHTNINGPROTECTION,
MUNICIPALSOLIDWASTE,
OIL,
OPERATIONAL,
POWERGENERATION,
RAINWATER,
REFRIGERATION,
SECURITY,
SEWAGE,
SIGNAL,
STORMWATER,
TELEPHONE,
TV,
VACUUM,
VENT,
VENTILATION,
WASTEWATER,
WATERSUPPLY,
USERDEFINED,
NOTDEFINED);
END_TYPE;

Link to EXPRESS-G diagram EXPRESS-G diagram

Link to this page  Link to this page