Systems

E3D Design IFC Export has support for basic IfcSystem entities. These IfcSystem instances have a name, but not a description or objecttype, and are included in the Ifc file if they are referenced by other Ifc instances. IfcSystem instances can be related to Ifc Spatial instances by IfcRelServicesBuildings instances and to instances of subtypes of IfcElement by IfcRelAssignsToGroup relationship instances.

In both cases these relationships are defined by a property named system in the AVEVA_EntityParameters PropertySet. As an ifc instance (spatial or otherwise) can be related to more than one yystem, multiple system-names can be included in the system property, separated by '|' (vertical bar) characters.

Example

An IfcBuilding might have its system property set to 'Heating systems|Air conditioning systems|Cold water systems|Hot water supply systems', and then IfcRelServicesBuilding instances will link those four IfcSystem instances to the IfcBuilding instance.

Non-spatial elements my similarly be part of one or more systems, again separated by '|' characters. As always, these string values come from expressions, which can be, for example:

• constant strings in the mapping, for example:

  'Cold water system|Hot water supply system'

• a UDA or other attributes set on the dabacon elements directly, for example:

  :EQUI_SUB_GROUP

• an expression involving other elements, for example:

  namn of pipe

  Note:
  Subsystems are not supported