CustomHeatExchanger

Overview

Class

A custom HeatExchanger, i.e., a HeatExchanger that is not covered by any of the other subclasses of HeatExchanger (AirCoolingSystem, ElectricHeater, PlateHeatExchanger, SpiralHeatExchanger, ThinFilmEvaporator, or TubularHeatExchanger).

Supertypes

Attributes (data)

Name

Multiplicity

Type

DesignPower

0..1

NullablePower

DesignRotationalSpeed

0..1

NullableRotationalFrequency

DesignShaftPower

0..1

NullablePower

NumberOfPlates

0..1

NullableInteger

PlateHeight

0..1

NullableLength

PlateWidth

0..1

NullableLength

TemaStandardType

0..1

NullableString

Attributes (composition)

Name

Multiplicity

Type

Rotor

0..1

HeatExchangerRotor

TubeBundle

0..1

TubeBundle

Implementation in Proteus Schema

The class is implemented as a Proteus XML element with RDL reference.

Tag: <Equipment>

RDL reference: CUSTOM HEAT EXCHANGER

ComponentClass: CustomHeatExchanger

Example

Implementation in Proteus Schema

<Equipment
    ID="customHeatExchanger1"
    ComponentClass="CustomHeatExchanger"
    ComponentClassURI="http://sandbox.dexpi.org/rdl/CustomHeatExchanger" ...>
  ...
</Equipment>

DesignPower

Attribute (data)

The power for which the CustomHeatExchanger is designed.

Multiplicity: 0..1

Implementation in Proteus Schema

The attribute is implemented as a DEXPI generic attribute for physical quantities.

RDL reference: DESIGN POWER

Name: DesignPower

DesignRotationalSpeed

Attribute (data)

The rotational speed for which the CustomHeatExchanger is designed.

Multiplicity: 0..1

Implementation in Proteus Schema

The attribute is implemented as a DEXPI generic attribute for physical quantities.

Name: DesignRotationalSpeed

DesignShaftPower

Attribute (data)

The shaft power for which the CustomHeatExchanger is designed.

Multiplicity: 0..1

Implementation in Proteus Schema

The attribute is implemented as a DEXPI generic attribute for physical quantities.

RDL reference: DESIGN SHAFT POWER

Name: DesignShaftPower

NumberOfPlates

Attribute (data)

The number of plates in the CustomHeatExchanger.

Multiplicity: 0..1

Implementation in Proteus Schema

The attribute is implemented as a DEXPI generic attribute for integer values.

RDL reference: NUMBER OF PLATES

Name: NumberOfPlates

PlateHeight

Attribute (data)

The height of the plates in the CustomHeatExchanger.

Multiplicity: 0..1

Implementation in Proteus Schema

The attribute is implemented as a DEXPI generic attribute for physical quantities.

RDL reference: PLATE HEIGHT

Name: PlateHeight

PlateWidth

Attribute (data)

The width of the plates in the CustomHeatExchanger.

Multiplicity: 0..1

Implementation in Proteus Schema

The attribute is implemented as a DEXPI generic attribute for physical quantities.

RDL reference: PLATE WIDTH

Name: PlateWidth

Rotor

Attribute (composition)

The rotor of the CustomHeatExchanger.

Multiplicity: 0..1

Opposite multiplicity: 0..1

Implementation in Proteus Schema

The attribute is implemented using the XML hierarchy of the Proteus file: The element for the attribute value (a HeatExchangerRotor) is a child of the <Equipment> element for the attribute owner (a CustomHeatExchanger).

Example

Implementation in Proteus Schema

<Equipment
    ID="customHeatExchanger1"
    ComponentClass="CustomHeatExchanger"
    ComponentClassURI="http://sandbox.dexpi.org/rdl/CustomHeatExchanger" ...>
  ...
  <Equipment
      ID="heatExchangerRotor1"
      ComponentClass="HeatExchangerRotor"
      ComponentClassURI="http://sandbox.dexpi.org/rdl/HeatExchangerRotor" ...>
    ...
  <Equipment />
  ...
<Equipment />

TemaStandardType

Attribute (data)

The type of the CustomHeatExchanger according to the Tubular Exchanger Manufacturers Association, Inc. (TEMA, http://www.tema.org). This is a three-letter code.

Multiplicity: 0..1

Implementation in Proteus Schema

The attribute is implemented as a DEXPI generic attribute for string values.

Name: TemaStandardTypeAssignmentClass

TubeBundle

Attribute (composition)

The tube bundle of the CustomHeatExchanger.

Multiplicity: 0..1

Opposite multiplicity: 0..1

Implementation in Proteus Schema

The attribute is implemented using the XML hierarchy of the Proteus file: The element for the attribute value (a TubeBundle) is a child of the <Equipment> element for the attribute owner (a CustomHeatExchanger).

Example

Implementation in Proteus Schema

<Equipment
    ID="customHeatExchanger1"
    ComponentClass="CustomHeatExchanger"
    ComponentClassURI="http://sandbox.dexpi.org/rdl/CustomHeatExchanger" ...>
  ...
  <Equipment
      ID="tubeBundle1"
      ComponentClass="TubeBundle"
      ComponentClassURI="http://data.posccaesar.org/rdl/RDS415259" ...>
    ...
  <Equipment />
  ...
<Equipment />