PropertyBreak¶
Overview¶
Concrete Class
RDL: PROPERTY BREAK (http://sandbox.dexpi.org/rdl/PropertyBreak)
An explicit indication of a change of piping properties.
Supertypes
Members¶
Data Properties¶
Name |
Multiplicity |
Type |
Ordered |
Unique |
|
|---|---|---|---|---|---|
0..1 |
no |
no |
A specialization indicating if the PropertyBreak is a composition break or not. |
||
0..1 |
no |
no |
A specialization indicating if the PropertyBreak is an insulation break or not. |
||
0..1 |
no |
no |
A specialization indicating if the PropertyBreak is a nominal diameter break or not. |
||
0..1 |
no |
no |
A specialization indicating if the PropertyBreak is a piping class break or not. |
This specification does not prescribe the use of PropertyBreaks whenever piping properties change. For example, consider a PipeReducer where, by definition, the nominal diameter is changed. According to the Proteus Specification, a new PipingNetworkSegment must begin immediately after the PipeReducer. This PipingNetworkSegment will have a different nominal diameter than the one before. Thus, the property break information is available without an explicit PropertyBreak. A PropertyBreak shall be used to emphasize such a change. In a Diagram, a PropertyBreak is typically visualized by a Core.Diagram.PropertyBreakShape.
A single PropertyBreak can indicate the change of several properties e.g., the nominal diameter and the piping class. It is recommended to avoid such PropertyBreaks that concern several properties. Instead, for each changed property a separate PropertyBreak should be used. These PropertyBreaks should then be connected with DirectPipingConnections. In a Diagram, each PropertyBreak can then be visualized by a separate Core.Diagram.PropertyBreakShape symbol. In case a diagram contains dedicated symbols for certain combinations of changed properties, it is still admissible to use a single PropertyBreak for these combinations.
CompositionBreak¶
Data Property
A specialization indicating if the PropertyBreak is a composition break or not.
Type: CompositionBreakClassification
Multiplicity: 0..1
Ordered: no
Unique: no
RDL: COMPOSITION BREAK SPECIALIZATION (http://sandbox.dexpi.org/rdl/CompositionBreakSpecialization)
Example¶
InsulationBreak¶
Data Property
A specialization indicating if the PropertyBreak is an insulation break or not.
Type: InsulationBreakClassification
Multiplicity: 0..1
Ordered: no
Unique: no
RDL: INSULATION BREAK SPECIALIZATION (http://sandbox.dexpi.org/rdl/InsulationBreakSpecialization)
Example¶
NominalDiameterBreak¶
Data Property
A specialization indicating if the PropertyBreak is a nominal diameter break or not.
Type: NominalDiameterBreakClassification
Multiplicity: 0..1
Ordered: no
Unique: no
Example¶
PipingClassBreak¶
Data Property
A specialization indicating if the PropertyBreak is a piping class break or not.
Type: PipingClassBreakClassification
Multiplicity: 0..1
Ordered: no
Unique: no
RDL: PIPING CLASS BREAK SPECIALIZATION (http://sandbox.dexpi.org/rdl/PipingClassBreakSpecialization)
Example¶
Example in DEXPI XML¶
<Object type="Plant/Piping.PropertyBreak">
<Data property="CompositionBreak">
<DataReference data="Plant/Enumerations.CompositionBreakClassification.NoCompositionBreak"/>
</Data>
<Data property="InsulationBreak">
<DataReference data="Plant/Enumerations.InsulationBreakClassification.InsulationBreak"/>
</Data>
<Data property="NominalDiameterBreak">
<DataReference data="Plant/Enumerations.NominalDiameterBreakClassification.NoNominalDiameterBreak"/>
</Data>
<Data property="PipingClassBreak">
<DataReference data="Plant/Enumerations.PipingClassBreakClassification.PipingClassBreak"/>
</Data>
</Object>