Pipe Stress Interface
XML Schema
XML Schema
: Basic Concepts
Basic Concepts
The PSI parsing mechanism steps through a series of branches in the sequence of the stress pipe.
Note:
A stress pipe is a collection of branches which do not need to belong to the same real pipe.
The AVEVA E3Dâ„¢ pipe structure is as follows:
A pipe is a collection of two ended segments called branches. In the example below there are two branches, the horizontal segment including the tee, bend and two flanges. The second branch is from the tee to the flange. A pipe may contain multiple branches.
Branches have a start and end point known as the head and tail. These define position, direction and many other attributes that define the branch.
The simplest form of a branch is one which runs directly from head to tail with no components other than the tube between them. Most branches do have components and these are contained in a list which exists below the branch, as shown below:
A branch can be summarised as a two ended container for components.The only important rule is that the components must be in sequence, in line and face in the correct direction. Individual branch components are defined in a piping catalogue and selected from a pipe specification. The list of components may be any of the following:
FLAN
Flange
ELBO
Elbow
TEE
Tee
REDU
Reducer
VALV
Valve
ATTA
Attachment Point
PCOM
Piping Component
FBLI
Blind Flange
BEND
Bend
OLET
Olet
COUP
Coupling
INST
Instrument
CAP
Cap
GASK
Gasket
FILT
Filter
WELD
Weld
CROS
Cross
UNIO
Union
VTWA
Three Way Valve
CLOS
Closure
TRAP
Trap
LJSE
Lap Joint Stub End
FTUB
Fixed Tube
VFWA
Four Way Valve
SHU
Standard Hook Up
Some of the listed types are obvious but others are less so, this not important for the xml description.
Components within a branch must have at least two connection points, called PPoints which define the component length and position. A tee and other multi-way components with other connection points which are connected to other branches.
The following is the pipe represented as a stress group showing the node numbers which appear in CAESAR.
What Goes in the .xml file
The body of the xml file is essentially a list. Every PPoint is listed, but only those with Node numbers are transferred to the CII file. The output contains other values but this list contains the essential attributes required to understand the concept.
Seq
NodeNo
Type
RefNo
Point
PPoint
Bore
Radius
Rigid
East
North
Up
1
BRAN
=676/3060
1
1
80mm
0.000
START
-2000mm
13800mm
0.000mm
2
10
FLAN
=676/3061
1
1
80mm
0.000
-2000mm
13800mm
0.000mm
3
20
FLAN
=676/3061
2
2
80mm
0.000
END
-2050mm
13800mm
0.000mm
4
TEE
=676/3062
1
1
80mm
0.000
-2913mm
13800mm
0.000mm
5
TEE
=676/3062
3
3
80mm
0.000
-2999mm
13800mm
86mm
6
30
TEE
=676/3062
0
0
80mm
0.000
-2999mm
13800mm
0.00mm
7
TEE
=676/3062
2
2
80mm
0.000
-3085mm
13800mm
0.00mm
8
40
FLAN
=676/3063
1
2
80mm
0.000
START
-3949mm
13800mm
0.0mm
9
FLAN
=676/3063
2
1
80mm
0.000
-3999mm
13800mm
0.0mm
10
GASK
=676/3064
1
1
80mm
0.000
-3999mm
13800mm
0.0mm
11
GASK
=676/3064
2
2
80mm
0.000
-4001mm
13800mm
0.0mm
12
FLAN
=676/3065
1
1
80mm
0.000
-4001mm
13800mm
0.0mm
13
50
FLAN
=676/3065
2
2
80mm
0.000
END
-4051mm
13800mm
0.0mm
14
BEND
=676/3066
1
1
80mm
210.00
-4790mm
13800mm
0.0mm
15
60
BEND
=676/3066
0
0
80mm
210.00
-5000mm
13800mm
0.0mm
16
BEND
=676/3066
2
2
80mm
210.00
-5000mm
13800mm
210mm
17
70
FLAN
=676/3067
1
2
80mm
0.000
START
-5000mm
13800mm
450mm
18
FLAN
=676/3067
2
1
80mm
0.000
-5000mm
13800mm
500mm
19
90
BRAN
=676/3060
2
2
80mm
0.000
END
-5000mm
13800mm
500mm
20
100
BRAN
=676/3068
1
1
80mm
0.000
-2999mm
13800mm
0.00mm
21
110
FLAN
=676/3069
1
2
80mm
0.000
START
-2999mm
13800mm
536mm
22
FLAN
=676/3069
2
1
80mm
0.000
-2999mm
13800mm
586mm
23
130
BRAN
=676/3068
2
2
80mm
0.000
END
-2999mm
13800mm
586mm
1974 to current year.
AVEVA Solutions Limited and its subsidiaries. All rights reserved.