Equipment

Overview

Abstract class

An apparatus or machine.

Supertypes

• ChamberOwner

• NozzleOwner

• TaggedPlantItem

• TransmissionDriver

Subtypes

• Agglomerator

• Agitator

• Blower

• Burner

• Centrifuge

• Compressor

• CoolingTower

• CustomEquipment

• Dryer

• ElectricGenerator

• Extruder

• Fan

• Feeder

• Filter

• HeatExchanger

• Heater

• Mill

• Mixer

• MobileTransportSystem

• Motor

• PackagingSystem

• ProcessColumn

• Pump

• Separator

• Sieve

• StationaryTransportSystem

• Turbine

• Vessel

• WasteGasEmitter

• Weigher

Attributes (data)

Name	Multiplicity	Type
EquipmentDescription	0..1	MultiLanguageString

Attributes (composition)

Name	Multiplicity	Type
DryingChambers	*	DryingChamber
Motors	*	MotorAsComponent
Mounts	*	Mount
SprayNozzles	*	SprayNozzle
TransmissionSystems	*	TransmissionSystem
Vents	*	EquipmentVent

Attributes (reference)

Name	Multiplicity	Type
DrivingTransmissionSystem	0..1	TransmissionSystem

Implementation in Proteus Schema

The class is implemented as a Proteus XML element with RDL reference. As Equipment is abstract, there is no RDL reference for the class itself; the RDL reference depends on the concrete subclass.

Tag: <Equipment>

ComponentClass: depending on subclass

ComponentClassURI: depending on subclass

Example

As Equipment is abstract, we consider Vessel as an arbitrary concrete subclass.

Implementation in Proteus Schema

<Equipment
    ID="vessel1"
    ComponentClass="Vessel"
    ComponentClassURI="http://data.posccaesar.org/rdl/RDS414674" ...>
  ...
</Equipment>

DrivingTransmissionSystem

Attribute (reference)

The TransmissionSystem that drives the Equipment. If given, it must be among the TransmissionSystems of the same Equipment.

Multiplicity: 0..1

Type: TransmissionSystem

Opposite multiplicity: 0..1

Implementation in Proteus Schema

The attribute is implemented using Proteus <Association> elements.

Association type for the attribute ower: "is driven by"

Opposite association type: "drives"

Example

Implementation in Proteus Schema

<Equipment
    ID="pump1"
    ComponentClass="Pump"
    ComponentClassURI="http://data.posccaesar.org/rdl/RDS327239" ...>
  ...
  <Association
    Type="is driven by"
    ItemID="transmissionSystem1" />
  ...
<Equipment />
...
<Equipment
    ID="transmissionSystem1"
    ComponentClass="TransmissionSystem"
    ComponentClassURI="http://data.posccaesar.org/rdl/RDS13105034" ...>
  ...
  <Association
    Type="drives"
    ItemID="pump1" />
  ...
<Equipment />

DryingChambers

Attribute (composition)

The DryingChambers of the Equipment.

Multiplicity: *

Type: DryingChamber

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 DryingChamber) is a child of the <Equipment> element for the attribute owner (an Equipment).

Example

As the owner type Equipment is abstract, we consider Vessel as an arbitrary concrete subclass.

Implementation in Proteus Schema

<Equipment
    ID="vessel1"
    ComponentClass="Vessel"
    ComponentClassURI="http://data.posccaesar.org/rdl/RDS414674" ...>
  ...
  <Equipment
      ID="dryingChamber1"
      ComponentClass="DryingChamber"
      ComponentClassURI="http://sandbox.dexpi.org/rdl/DryingChamber" ...>
    ...
  <Equipment />
  ...
<Equipment />

EquipmentDescription

Attribute (data)

A short description of the Equipment in natural language.

Multiplicity: 0..1

Type: MultiLanguageString

Implementation in Proteus Schema

The attribute is implemented as a set of DEXPI generic attributes for multi-language string values.

RDL reference: EQUIPMENT DESCRIPTION ASSIGNMENT CLASS

Name: EquipmentDescriptionAssignmentClass

AttributeURI: http://data.posccaesar.org/rdl/RDS2181987301

Example

As the owning class Equipment is abstract, we consider Vessel as an arbitrary concrete subclass.

Language	Value
de	Prozessgaskühler
en	process gas cooler

(MultiLanguageString with 2 SingleLanguageStrings)

Implementation in Proteus Schema

<Equipment
    ID="vessel1"
    ComponentClass="Vessel"
    ComponentClassURI="http://data.posccaesar.org/rdl/RDS414674" ...>
  ...
  <GenericAttributes Set="DexpiAttributes" ...>
    <GenericAttribute
      Name="EquipmentDescriptionAssignmentClass"
      AttributeURI="http://data.posccaesar.org/rdl/RDS2181987301"
      Format="string"
      Language="de"
      Value="Prozessgaskühler" />
    <GenericAttribute
      Name="EquipmentDescriptionAssignmentClass"
      AttributeURI="http://data.posccaesar.org/rdl/RDS2181987301"
      Format="string"
      Language="en"
      Value="process gas cooler" />
    ...
  </GenericAttributes>
  ...
</Equipment>

Motors

Attribute (composition)

The motors that are components of the Equipment.

Multiplicity: *

Type: MotorAsComponent

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 MotorAsComponent) is a child of the <Equipment> element for the attribute owner (an Equipment).

Example

As the owner type Equipment is abstract, we consider Vessel as an arbitrary concrete subclass.

Implementation in Proteus Schema

<Equipment
    ID="vessel1"
    ComponentClass="Vessel"
    ComponentClassURI="http://data.posccaesar.org/rdl/RDS414674" ...>
  ...
  <Equipment
      ID="motorAsComponent1"
      ComponentClass="MotorAsComponent"
      ComponentClassURI="http://sandbox.dexpi.org/rdl/MotorAsComponent" ...>
    ...
  <Equipment />
  ...
<Equipment />

Mounts

Attribute (composition)

The Mounts that are attached to the Equipment.

Multiplicity: *

Type: Mount

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 Mount) is a child of the <Equipment> element for the attribute owner (an Equipment).

Example

As the owner type Equipment is abstract, we consider Vessel as an arbitrary concrete subclass.

Implementation in Proteus Schema

<Equipment
    ID="vessel1"
    ComponentClass="Vessel"
    ComponentClassURI="http://data.posccaesar.org/rdl/RDS414674" ...>
  ...
  <Equipment
      ID="mount1"
      ComponentClass="Mount"
      ComponentClassURI="http://sandbox.dexpi.org/rdl/Mount" ...>
    ...
  <Equipment />
  ...
<Equipment />

SprayNozzles

Attribute (composition)

The SprayNozzles of the Equipment.

Multiplicity: *

Type: SprayNozzle

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 SprayNozzle) is a child of the <Equipment> element for the attribute owner (an Equipment).

Example

As the owner type Equipment is abstract, we consider Vessel as an arbitrary concrete subclass.

Implementation in Proteus Schema

<Equipment
    ID="vessel1"
    ComponentClass="Vessel"
    ComponentClassURI="http://data.posccaesar.org/rdl/RDS414674" ...>
  ...
  <Equipment
      ID="sprayNozzle1"
      ComponentClass="SprayNozzle"
      ComponentClassURI="http://data.posccaesar.org/rdl/RDS5855670" ...>
    ...
  <Equipment />
  ...
<Equipment />

TransmissionSystems

Attribute (composition)

The TransmissionSystems that are components of the Equipment.

Multiplicity: *

Type: TransmissionSystem

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 TransmissionSystem) is a child of the <Equipment> element for the attribute owner (an Equipment).

Example

As the owner type Equipment is abstract, we consider Vessel as an arbitrary concrete subclass.

Implementation in Proteus Schema

<Equipment
    ID="vessel1"
    ComponentClass="Vessel"
    ComponentClassURI="http://data.posccaesar.org/rdl/RDS414674" ...>
  ...
  <Equipment
      ID="transmissionSystem1"
      ComponentClass="TransmissionSystem"
      ComponentClassURI="http://data.posccaesar.org/rdl/RDS13105034" ...>
    ...
  <Equipment />
  ...
<Equipment />

Vents

Attribute (composition)

The EquipmentVents that are components of the Equipment.

Multiplicity: *

Type: EquipmentVent

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 (an EquipmentVent) is a child of the <Equipment> element for the attribute owner (an Equipment).

Example

As the owner type Equipment is abstract, we consider Vessel as an arbitrary concrete subclass.

Implementation in Proteus Schema

<Equipment
    ID="vessel1"
    ComponentClass="Vessel"
    ComponentClassURI="http://data.posccaesar.org/rdl/RDS414674" ...>
  ...
  <Equipment
      ID="equipmentVent1"
      ComponentClass="CasingVent"
      ComponentClassURI="http://data.posccaesar.org/rdl/RDS16766649" ...>
    ...
  <Equipment />
  ...
<Equipment />